Business Process Software
Living Business Processes
Business process management software is bought to stop the process from living in someone's head. A year later the suite has a diagram, the application has the real steps, and the two disagree. The diagram was the project. The code is what the customer hits. Business process management tools that only draw the process leave you with a second copy to maintain.
Order manager
ReceiveOrder
Ingest the order, validate line items, and confirm the SKUs are sellable.
Order manager
Verify paymentOrder
Confirm authorization; hold or decline anything the processor flags.
Warehouse lead
ReserveInventory item
Hold stock at the fulfilling location and trigger replenishment if it goes short.
Payment clears before stock moves. No stock is reserved until payment authorization has cleared.
Warehouse lead
PackShipment
Retrieve the items, verify quantities, and package for the carrier.
Warehouse lead
DispatchShipment
Generate the label, hand off to the carrier, and publish tracking to the order.
Only warehouse dispatches. Dispatch is the warehouse’s call. Support can ask; it cannot ship.
Customer support lead
ConfirmOrder
Verify carrier confirmation, close the order, and open the post-purchase follow-up.
The Drift
Take fulfillment. The diagram says payment is checked before stock moves. The service reserves inventory on the way into the queue, because that was the bugfix that shipped on a Friday. Both are "the process." Neither knows about the other. The next audit, the next agent, and the next hire all pick one.
In the process above, that rule is on the step it governs. Stock cannot be reserved until payment has cleared, and dispatch stays with the warehouse. The steps, the roles, and the work are the description the software is built from.
The Difference
A BPM suite runs the process on its own engine. DNA describes the process, and the systems you already run follow that description.
- A BPM suite draws the process and runs it on its own engine. Work items, timers, and human tasks live there. That is the right tool when the suite is the system of record for the work: case management, long-running approvals, a queue that has no other home.
- DNA models the process as data. The docs, the application, the workflow, and the agent read that one model. DNA does not execute long-running workflows on an engine of its own. It tells the systems you already run who may do what, and it keeps the description those systems are built from.
If you need a place where the work waits, buy a BPM engine. If the work already lives in your app and your agents, and the description of it keeps falling behind, the thing you are missing is the model.