Features at a glance.
From the document to the approved process and into daily work: what OpsCodex does, each with a link to the page that explains it.
OpsCodex is an AI-assisted BPMN governance platform for industrial and regulated enterprises — AI drafts processes from existing documents, people review and approve, deployed on-premise.
Jump to: Getting a process in · Draft and quality · Company rules · Variants and change · Process landscape · Review, approval and record · After approval · Publishing and integrations · Export · Operation and AI · Security and releases · What OpsCodex does not do
Getting a process in
| Feature | What it does |
|---|---|
| Documents | PDF, Word, PowerPoint, Excel, OpenDocument, plain text and Markdown, several files at once. AI BPMN generator → |
| Images and scans | Screenshots, scans, photos and drawn diagrams. A page reader turns tables and diagrams into structure. How it works → |
| Pasted text | Paste a description into a new process. It is kept as a source, so every element links to its passage. AI BPMN generator → |
| AI chat | Describe a process or a change. The AI proposes it as an edit to the model, and you accept or reject each proposal. How it works → |
| Existing models | Import BPMN 2.0, XMI (for example from Enterprise Architect) and draw.io files. BPMN details the editor does not show, such as properties and root-level definitions, are kept when the model is rebuilt, and lanes inside lanes are reported instead of flattened. |
| Drawing options | Settings the draft is guaranteed to follow, such as one pool or no lanes, and free-text instructions to the AI, kept apart from the source material. |
Draft and quality
| Feature | What it does |
|---|---|
| Inventory first | Roles, steps, decisions and data are listed with their quote before anything is drawn, and the model is checked against that list. How it works → |
| A second reading of who acts | A reader without AI lists everyone who may act in a source, by grammar and vocabulary; a role is missing from a draft only when both readings miss it. How it works → |
| A source for every element | Every element drafted from a document links to its passage, and program code checks the quote against the text. How it works → |
| Open questions | Assumptions, gaps and contradictions in the material become open questions. While one is open, approval stays locked. How it works → |
| Consistent models | Lanes, names, layout and BPMN XML are set by program code, so processes look alike and can be compared; no lane is left empty. How it works → |
| Independent triggers | A round that handles many cases at once, such as "every hour, the prescriptions due", or a party that arrives to do something starts a flow of its own instead of a step every case waits for. |
| Process Advisor | Checks the model against modelling rules and fixes a finding on a click. How it works → |
| Comparing processes | Compares two processes with AI, for example those of two sites: the elements are mapped, you accept or reject each difference, and a common version is drafted. How it works → |
| Decision tables and shared tasks | DMN decision tables and tasks defined once go through the same sign-off as processes. Governance → |
Company rules
| Feature | What it does |
|---|---|
| Rule registry | Your rules as versioned entries with severity, owner and scope (process category, business unit, legal entity, level); every process is checked against the rules that apply to it. |
| Checks without AI | Segregation of duties, mandatory steps, thresholds and structural checks, such as process size, reachability, a business object or IT system per task and lane names from a role catalogue, run in program code. |
| Rules in the review | The result is recorded when a version is sent to review, bound to its content, shown to reviewer and approver and kept in the evidence pack. A finding informs the decision; it does not block it. |
| Rules steer the draft | The AI reads the applicable rules before it draws; what the draft does not meet becomes an open question. |
| Rule sources | A rule can cite its source document; when that source is a linked SharePoint file and it changes, the rule is marked and its owner is notified. |
Variants and change
| Feature | What it does |
|---|---|
| Branches for sites and variants | Cut a branch from a master process for a site or a variant, with its own owner and its own approval. |
| Pull from master | Improvements to the master come into a branch as a three-way merge; conflicts are shown and decided one by one, decision tables row by row. |
| Merge back and compare | Merge a branch back into its source, compare the two side by side, diagram and fields, or discard the branch. |
| Impact of a change | A change is checked against linked processes, articles, tools and deliverables; each finding can be acknowledged or its owner notified. |
| Snapshots and clones | Save a named snapshot of a diagram and restore it later, or clone a process into an independent copy. |
Process landscape
| Feature | What it does |
|---|---|
| Process map | Your process landscape from level L0 to L3 as a map, coloured by status, with the links between processes. |
| Building blocks | Reusable BPMN fragments: any author can propose one, a library admin releases it, and others insert it into their diagram. |
| Deliverables | Each step lists the documents it produces and uses; the chain across processes is derived with warnings, and shared deliverables are defined once in a catalogue. |
| Tool registry | A register of your IT tools with vendor, link and external IDs such as a CMDB number; steps link to them, and portal and browser extension show them. |
| Knowledge articles | Articles and collections next to the processes, linked to individual steps; a slide deck or PDF can be imported as a draft article. |
Review, approval and record
| Feature | What it does |
|---|---|
| Six-eyes workflow | Author, reviewer and approver are different people, and that is enforced. An exception needs an administrator and a written justification, and carries its own status. Governance → |
| Review loop | The reviewer comments on the model and sends it back; the author fixes it, resolves the comment and resubmits, all on record. Governance → |
| Review queue | Reviewers and approvers see what is waiting on them and what is overdue. Governance → |
| History | Versions, workflow transitions and sign-offs in one timeline. Governance → |
| Append-only audit log | Every state change is written to a log the application cannot rewrite: the database rejects changes and deletions. Security & trust → |
| Signature and content hash | On request, every signature is confirmed with a password, and every approval decision carries a content hash. Governance → |
| Roles | Author, reviewer, approver, administrator, auditor and documentation editor; people see and do what their role allows. Security & trust → |
| Co-authors and the editing baton | Drafts are closed by default and the owner invites co-authors. One person edits at a time, a takeover needs consent, and nobody overwrites a newer version. |
| Notifications | In the app: review requests, decisions, changed sources and impact notices. |
| Evidence pack | One archive per released version: a PDF, a machine-readable record, a hash manifest, the approval chain with exceptions and reasons, the change reason, the diff, the rule result and the open questions. |
| Integrity re-check | One click recomputes the hash of every released decision and lists any that no longer match. |
After approval
| Feature | What it does |
|---|---|
| Process concierge | Employees ask in plain language and get answers only from approved processes, each naming the process and revision it came from. In daily work → |
| Work instructions and SOPs | Generated from the approved BPMN; when the process is re-approved, the instructions follow. In daily work → |
| Browser extension | The concierge right next to your ERP, MES or ticket system. In daily work → |
| Employee portal | Read-only and released versions only; open within your network or to signed-in users only. Security & trust → |
| AI assistants over MCP | Microsoft Copilot and other assistants read approved processes read-only, with revision, approver and approval date. Off by default, one token per client, every access logged. In daily work → |
| What people ask | Process owners see the topics people ask about most, without names; small groups are never shown. In daily work → |
| Feedback from the portal | Readers give feedback on a published process; the owner triages it, and accepting it starts a change branch in the normal approval cycle. |
Publishing and integrations
| Feature | What it does |
|---|---|
| Publish to SharePoint | An approved version is published as PDF to a SharePoint Online library, with its governance data in mapped columns; a new release replaces the file and marks the previous publication as superseded. |
| SharePoint files as sources | A source of a draft or a rule can point to a SharePoint file; OpsCodex notices when it changes and tells the owner. Nothing is written back. |
| Enterprise Architect | XMI files from Sparx Enterprise Architect import with a report of what was understood, carried over or lost. An add-in for Enterprise Architect sends a package to OpsCodex for review, fetches a process from the OpsCodex repository into EA, and brings approved updates into a linked package, with undo for the last update; it is available on request. |
Export
| Feature | What it does |
|---|---|
| BPMN 2.0 XML | Standards-conformant (OMG, ISO/IEC 19510) and readable by any conformant tool; engines such as Camunda import it as a starting structure. FAQ → |
| Other formats | SVG, PNG, PDF and draw.io; DMN for decision tables. |
| Your data, your exit | Your content is available for export at any time; on-premise, you control its deletion yourself. Security & trust → |
| PDF layouts | Design PDF layouts with themes, page masters and blocks and a live preview; a released layout version is frozen, so later changes never alter earlier exports. |
Operation and AI
| Feature | What it does |
|---|---|
| On-premise | Single-tenant in your environment: Docker Compose on one server, or a Helm chart in one Kubernetes namespace (non-root, Pod Security restricted). PostgreSQL and S3 storage come from your platform or run inside the release; your company CA is supported. For IT teams → |
| Without internet | Delivery as a handover archive with images, Helm chart, SBOMs and scan results; every image is signed. For IT teams → |
| Your AI model | A model server with an OpenAI-compatible interface on your own network, proven with Ollama and llama.cpp, or Anthropic, OpenAI, Google or Mistral under your own contract. For IT teams → |
| What is stored | By default, the text of prompts and answers is not stored, and your data is not used to train models. AI governance → |
| Planned updates | Nothing updates itself. The update screen shows whether a new release can be rolled back and whether it needs manual steps. For IT teams → |
| Sizing | 700 people at the same time in our load test, on one backend with two CPU cores; OpsCodex itself needs no GPU. For IT teams → |
| Modules and branding | Switch processes, governance, knowledge and portal on or off, and set your own name, logo and accent colour. |
| Masking before the AI | Email addresses, phone numbers and IBANs are masked before anything reaches the AI, on by default; the AI can also be switched off entirely. AI governance → |
| GDPR erasure | A person’s data is pseudonymised on request while the audit trail stays intact. |
Security and releases
| Feature | What it does |
|---|---|
| Sign-in | Local accounts with password rules following NIST SP 800-63B-4, and two-factor sign-in with an authenticator app, optional per person or required for everybody; single sign-on (OIDC, SAML) is in the works. Security & trust → |
| Encryption | TLS in transit; secrets such as AI provider keys encrypted with AES-256-GCM. Security & trust → |
| Release gate | Before every release: a cold start, a smoke test, a Trivy scan of every image and an OWASP ZAP attack; an SBOM for every image. Security & trust → |
| Release rhythm | About one release a quarter, nine months of fixes for high and critical vulnerabilities, a monthly patch day. Security & trust → |
| Sources of the free software | Every release carries the source code of the GPL, LGPL, AGPL and MPL components in its images, also inside the handover archive. |
| OWASP ASVS | A self-assessment at level 2, every requirement checked against code, tests and configuration. Security & trust → |
What OpsCodex does not do
| Feature | What it does |
|---|---|
| Process mining | OpsCodex does no process mining. What your event logs show is a different product category. Comparison → |
| Running processes | OpsCodex governs what a process is; execution engines such as Camunda run it from the exported BPMN. Comparison → |
| A free plan | No public free tier or self-service sign-up. You see OpsCodex in a one-hour demo on one of your own documents, then in a pilot. Evaluating OpsCodex → |
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.