- 4 minutes to read

Preserve Knowledge in a Living BPM

Most process diagrams are drawn once, for a project, and are out of date a few months later. Who owns the process, what the SLA is, and what to do when a step fails ends up in wikis, spreadsheets, and people's heads. A Nodinite BPM keeps that knowledge on the process model itself, and the model stays tied to the systems that run it: living documentation rather than a picture.

  • ✅ Description, owner, SLA, and other fields on the BPM and its Domains, with Custom Metadata
  • ✅ Runbooks and instructions one click away, as Knowledge Base Articles on the Resources behind each Service
  • ✅ Colors from live data: logged status per order, and Resource state per Service, so a stale drawing shows
  • ✅ The same model as an interactive Mapify graph or a Mermaid diagram you can export

The Business Context

The Order-to-Cash demo runs across four Domains: Sales, Planning, Logistics, and Finance. Each Domain has its own people, and the integrations between the Portal, ERP, WMS, and ERP-Finance were built by different teams at different times. New colleagues need to learn the process; experienced ones change roles or leave.

The Problem

A Visio or draw.io diagram doesn't know when a Service is renamed or a step is added, and nobody is reminded to update it. Ownership and SLAs live in a separate document, operating instructions in a third. A newcomer can't tell which of them is still true.

The Solution

The BPM is a Repository artifact built from the same Services your integrations log against and your Monitoring Agents watch. Knowledge is attached where people look for it:

BPM General tab with name, description, and an SLA Custom Metadata value of Gold
The General tab of the Order-to-Cash BPM: a Name, a Description, an optional Web Site, and a Custom Metadata field (SLA = Gold).

  • Description and Custom Metadata New 7.2 - State what the process is for, and record the owner, SLA, review date, or compliance notes on the BPM and on each Domain. See Custom Metadata Support.
  • Domains - The swimlanes name the department responsible for each step, and the same Domain is reused across BPMs.
  • Knowledge Base Articles - Click the lightbulb on a Service to reach the Knowledge Base Articles linked to its Resources, such as a restart procedure, the same way as from the Integration Landscape. See Integrated Monitoring.
  • Mapify and Mermaid New 7.10 - Open the BPM as a Mapify graph of everything it relates to, or as a Mermaid diagram to print or paste into other documentation.

What keeps it from going stale is that the colors come from data, not from the person who drew it:

BPM Designer with the Order-to-Cash swimlanes and lightbulbs on the Services (7.11)
The Order-to-Cash BPM in the Designer, with a lightbulb on each Service that has linked Resources.

In BPM Log Search, each step takes the color of the logged Log Status Code for the selected order. A step that never lights up, or a Service whose Resources no longer report, is a visible sign the drawing and reality have drifted apart.

The Results

  • Newcomers start from one page per process: the steps, the owning departments, the description, and links to the instructions.
  • Owner and SLA are visible to operations next to the process, not in a separate document.
  • Because nothing in the logging references the BPM, you can redraw it as the process changes without touching the integrations.

How This Scenario Uses Nodinite Features

  1. BPM Designer - Draw the process with Domains, steps, and Services
  2. Custom Metadata Support - Owner, SLA, and compliance fields on BPMs and Domains
  3. Knowledge Base Articles - Operating instructions linked to Resources, reached from the lightbulb
  4. Integrated Monitoring - Live Resource state behind each Service
  5. Mapify Rendering and Mermaid Rendering - Other views of the same model

Next Steps