How MPTS thinks
Before learning the interface, it is important to understand
what is considered true in the system.
Ontology layer โ what happens
Production is described as a strict hierarchy:
- Product โ what is produced
- Operation โ a technological unit of work
- Step โ a part of an operation
- Action โ a concrete, observable action
If something affects the result, it must exist here.
Measurement layer โ how much it costs
Actions are described using:
- Microelements โ atomic movements and actions (based on the BES system)
- Factors โ quantitative and qualitative modifiers
From this, time and labor are calculated โ not entered manually.
Proof layer โ how it is proven
Not everything needs proof.
But when proof is required, it must be explicit.
Flow defines:
- when a state must be recorded,
- what exactly must be recorded,
- how products, batches, or serial numbers are linked.
Flow does not describe production.
It describes evidence.
Key rule
If Flow is removed,
and the production model stops making sense โ
the ontology is wrong.
MPTS keeps these layers separate on purpose.