PlatformProcess maps
Process maps and SOPs
Map how each process runs, step by step, by role and system. The map is the SOP, and people and AI agents follow the same released revision.
- LiveProcess maps and SOPs
This is the CourageMFG editor, with example data. Your changes stay in your browser. Open it full screen
Things to try.
The example is order to ship: Rev A is in effect, and a Rev B draft hands sales order entry to an agent, with customer service checking each order before release.
Click a step
The panel shows who does it, where, and the instruction. Owner, KPI and control are under More details.
Press Enter, then type
Adds the next step and names it. Tab adds a decision. Drag a step to another lane.
Look at Enter sales order
Rev B moves it from customer service to the order entry agent. Compare marks what changed.
Pick Rush order
The map shows that scenario's path. Walk through it step by step.
Release Rev B
Releasing is the one approval. Document control files it, and the agent takes over order entry.
Ask Courage Chat
It proposes a change. You confirm, and it shows on the map as new.
Scenarios
One map. Every scenario.
A scenario is one path through the map: a stock order, a make-to-order order, a rush order. You choose its branch at each decision.
Each scenario has its own work instruction, built from the steps on its path. Each step's instruction is written once. All of them roll up into one SOP.
- LanesWho does the step: customer service, planning, the warehouse, or an AI agent.
- SystemsWhere it happens: a CourageMFG screen, a Business Central page, or by hand.
- Controls and KPIsWhat must be true, and how the step is measured.
- Work instructionsNumbered by step, like WI-SC-014-07, under the SOP's number.
People and agents follow the same procedure.
A lane is who does the work. Put a step in an agent lane and an AI agent does it, through CourageMFG and Business Central, as the step is written.
Agents follow the revision in effect
Never the draft. An agent takes over a step only when a person releases a revision that gives it that step.
Agents stop at a person's step
When the next step is in a person's lane, the agent stops and says who does it and what they need.
Handing off is a revision
Give a step to an agent, or back to a person, like any other change: move it to another lane, then release.
Document control
Released as a controlled document.
When the map is right, a person releases the next revision: A, B, C. Releasing is the one approval. The release goes into document control as the effective procedure, with what changed and who released it.
A released revision is kept as it was. It can't be changed or removed. People who don't edit the map see the revision in effect, with the draft one click away.
Kept simple
Each step is three things.
Who does it, where it happens, and how. Owner, KPI and control are there when you need them, under More details.
Write each instruction once, in plain words. It rolls up into the SOP and into each scenario's instruction, and it's what a person or an agent follows.
AI drafts the map. People release it.
Courage Chat and AI tools, through the CourageMFG MCP server, add steps, lanes, branches and scenarios to the draft, and read the released steps to do their part. Only a person releases a revision.
- A change from AI shows on the map as new or changed, for a person to check.
- An AI tool can't release a revision: the server refuses it.
Map one of your processes with us.
We'll connect CourageMFG to a copy of your Business Central, map one process with your team, and release it as your SOP.