A platform without a method produces scattered automation.
The Dexon BPM V8 methodology formalises how you get from strategic intent to a process that executes and can be audited: the traceability chain, the metamodel with its integrity constraints, Objective-Driven Process Design, and a maturity model to know where the organization stands before promising where it will get to.
The principles
Six decisions that change the outcome of a BPM project
The objective governs the design →
The future process is not the current one optimised: it is the mechanism designed to maximise fulfilment of a verifiable objective. If the objective cannot be verified, the process is not approved.
The AS-IS is analysed with a limit →
Documenting the complete current state is the most common way to exhaust the budget before transforming anything. You analyse what prevents the objective, and you stop there.
Every exception is governed →
A normal path leading to an outcome plus informal exceptions somebody resolves by email is not a process: it is a process and a dark zone.
Conformance is queried, not debated →
Because every metamodel relationship is a real repository relationship, the question "does this process answer to a declared capability?" has an answer by query, not by committee.
Rigor follows exposure →
Rigor is decided process by process, by regulatory, financial or reputational exposure — not by size: the full method for what is critical or exposed, and a registered light version for low-exposure internal routines. Four conditions are never dropped: its place in the chain, a named owner, a criterion with a threshold and an indicator. The conformance checker evaluates each light process against its own minimum.
Start small, grow without remodelling →
You can start with two to five processes of one area, or with the service desk. Each process enters the traceability chain complete — capability, service, objective, indicator — so when the scope grows, what was built is already traced and nothing has to be remodelled.
The full development of the traceability chain, the metamodel and the seven phases of Objective-Driven Process Design lives on the approach page. See Executable Business Architecture →
The project
Five phases, each with a verifiable output
In projects of this nature the risk is not the technology: it is scope creep. That is why the output of the first phase is a signed scope, not an optimistic schedule.
| Phase | Stage | What happens | Output |
|---|---|---|---|
| 1 | Discovery | Processes, service catalogue, data model, groups, calendars and rules. | Signed scope |
| 2 | Configuration | Native processes parameterised on the BPMN engine, with no custom development. | Configured environment |
| 3 | Integrations | Directory, ERP, HR, monitoring and inventory, via REST API and ETL. | Tested interfaces |
| 4 | Testing | Factory, site and user acceptance testing, against criteria you define. | Acceptance |
| 5 | Stabilisation and handover | Support in operation and training to administer the platform without depending on the vendor. | Autonomy |
The declared goal
That you can change the platform without calling us
Knowledge transfer aims at your team creating new processes, adjusting flows, changing assistant scripts and building dashboards without raising a request.
And we do not say this out of generosity. If you depend on the vendor for every adjustment, the project gets expensive, the platform becomes a bottleneck and the model scales for neither party. That is the real argument behind a configurable engine: not a fashion, but what makes that autonomy possible.
Formal foundation
The V8 methodology draws on strategy and capability frameworks, academic BPM and process mining, ITIL 4 and COBIT, and process maturity models, with verified bibliography. It includes an ITIL interoperability chapter matching the twelve processes certified by PinkVERIFY.
The metamodel is formalised: objects, relationships, cardinalities and fifteen integrity constraints that make architectural conformance a demonstrable property.
See the certified processesThe methodology, in full
The complete framework — 23 chapters: traceability chain, formal metamodel with its fifteen integrity constraints, process objective specification, Objective-Driven Process Design and maturity model — with verified bibliography. Version 8, August 2026, English edition. And if you like, we walk the method through one of your processes.