Modelled, approved — and then forgotten.
Most process initiatives don’t fail in modelling. They fail the day after: the approved diagram lands in a repository, and the shop floor keeps working from a Word file last saved in 2023. Documentation nobody reads protects nobody.
From approved model into everyday work.
The approved process isn’t the end of the pipeline — it’s the single source for everything your teams see.
Ask, don’t search.
Your people ask in plain language: how do I escalate a supplier defect? They get the steps from the approved process. Answers come from governed models only — and each one names the process and revision it came from.
Instructions that can’t drift.
Work instructions and SOPs are generated from the approved BPMN itself. When the process changes and is re-approved, the instructions follow. Diagram and instruction stay in step, because one is generated from the other.
Answers where the work happens.
The concierge lives in a browser extension, right next to your ERP, MES or ticket system. No portal to remember, no second screen — ask while you work.
Your own assistants, such as Microsoft Copilot, read only the approved version, too.
OpsCodex publishes every approved process as a frozen version, and that is exactly what your AI assistants read over MCP, read-only. Every answer carries revision, approver and approval date, so the assistant can cite rather than claim.
See where processes are unclear.
Process owners see what people ask about most: by topic, without names, and small groups are never shown. When questions pile up around one step, that is a hint to model it more clearly.
Monday, 8:40. The audit question lands.
8:40 — The auditor asks for the approval chain on your complaints process. You run one query. By 8:41 it’s answered: author, reviewer, approver, timestamp, export hash. That question is settled.
14:15 — On the shop floor, someone asks the concierge how to escalate a supplier defect. They get the approved steps — not the 2023 PDF, not a colleague’s best guess.
Same source. Same truth. Every day — not just on audit day. Everything your teams see has passed the six-eyes workflow. One source of truth — from model to shop floor.
See OpsCodex on one of your own processes.
Bring a PDF, a slide deck or a messy SOP, or use our sample data. In one hour we run the process end-to-end — draft, approval, export — and the concierge answers questions on it. Afterwards you get the process and an analysis report.
“In our consulting projects we spent weeks working through interviews, and in the workshop everyone still described the same process differently. Gaps and overlaps surfaced late, and the approved version vanished into a repository. We built OpsCodex for the whole road: from the draft through optimisation to the work that follows.”
Tillmann Schatz · Product owner OpsCodex, Senior Manager at Mews PartnersOpsCodex is built by a team at Mews Partners.