EM-OPS-01 · Subject model · W1
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.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- ProcessDefinition
- Procedure
- ProcessInstance
- ActivityExecution
- ProcessMethod
Deep research 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?
Verifiable invariants
- An execution references a version of the definition
- A deviation is recorded explicitly
- A BPMN diagram does not prove the actual path
End-to-end acceptance scenario
One process in two variants, a manual exception and a new procedure yield separate execution traces.
Negative case
Updating an instruction retroactively changes a completed process.
Approaches to compare
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
Candidates in the live catalogue
- WM-ACT-003 · Process / Workflow · 0.2.0-legacy · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-009 · Method / Procedure · 0.2.0-legacy · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.