Process, procedure and execution
Process definition, steps, procedure and a specific execution instance. A methodology sets the rules of work, not a new process instance.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 8 questions
Definition How a process is defined, in which version and variants.
Process and method
Definitions, procedures and methods as separate records.
Definition version
The versioned definition of a process and its variants.
- Which version of the process definition applies, and which variant?
- How do the variants differ, and when is each allowed?
Method versus process
A method sets rules of work; it is not a process instance.
- Is this record a method, a procedure, a process definition or an execution?
- Which procedure describes how a step is performed?
Execution What actually happened in a given run of the process.
Execution trace
Instances and their steps as actually performed.
Instance trace
The steps executed, linked to the definition version.
- Which definition version did this instance follow?
- Which tasks and events make up the actual path?
Deviations
Departures from the defined path, recorded explicitly.
- Where did the execution deviate from the definition?
- Who approved the manual exception, and why?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseOPS
- Industry
- Cross-industry
- Tags
- EM-OPS-01W1subjectProcessDefinitionProcedureProcessInstanceActivityExecutionProcessMethod
What it is Filled
Process definition, steps, procedure and a specific execution instance. A methodology sets the rules of work, not a new process instance.
Why it exists Filled
Process definition, steps, procedure and a specific execution instance. A methodology sets the rules of work, not a new process instance.
Distinguishing features Filled
- An execution points to the definition version it followed and keeps it after the definition changes.
- A diagram shows the intended path; only execution events show the actual one.
- Deviations are recorded as such, not absorbed into the definition.
- Distinct from work items, which track units of work rather than process steps.
What robots and AI may and may not do Filled
Must not
- Change a completed process retroactively by updating an instruction.
- Treat a process diagram as proof of how work was done.
- Hide a manual exception by editing the execution trace.
- Start or skip process steps that require a human approval.
Only with a human decision
- Approving a new version of a process definition.
- Authorising a manual exception to the defined path.
May
- Reconstruct the actual path of an instance from execution events.
- Compare executions against their definition version and list deviations.
- Report how often each variant and exception occurs.
Moral aspects Filled
- Execution traces can be used to monitor individual workers and need proportionate use.
- Retroactive edits destroy the record people rely on for accountability.
Who is affected
- Workers who execute the process
- Process owners
- Customers served by the process
Owners Filled
Steward
The head of operations who answers for how processes are defined and executed.
Master systems
- Business process management suite
- ERP
- Warehouse management system
- Product lifecycle management system
- Enterprise asset management system
Links to other meta-models Filled
neighbor
- EM-FAC-02
- EM-PRD-03
- EM-RSK-01
- EM-RSK-04
- EM-STR-03
- EM-TEC-05
- EM-WRK-01
references
- WM-ACT-003 - conceptual-candidate
- WM-ACT-009 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A definition is identified by process identifier and version; an execution by its instance identifier.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A definition has steps and variants; an execution has timestamps, actors and a path.
- Often confused with a work instruction document or a task in a tracker.
Capabilities and actions required Filled
- Conformance of executions to definitions can be checked.
- Process variants can be compared by frequency and outcome.
Hazards and failure modes required Filled
- Rewritten history when definitions are edited in place.
- Worker surveillance through fine-grained execution logs.
Standards and interfaces required Filled
- OMG BPMN 2.0, also published as ISO/IEC 19510, for process definitions.
- IEEE 1849 XES for event logs used in process mining.
- IEC 62264 for manufacturing operations processes.
Context of use required Filled
- Used in operations management, process mining and quality audits.
- Relevant wherever processes run in several variants with manual exceptions.
Sources Filled
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
- OMG Business Process Model and Notation 2.0.2 - Checked live (HTTP 200) on 2026-10-07.
- IDTA Asset Administration Shell specifications - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to distinguish a method, a model and an execution?
- How do process variants coexist?
- How is an execution event linked to a task?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-ops-01/brief.json, ver-cy/world-models/card-supplements/em-ops-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.