EM-MFG-01 · Subject model · W-IND
Production order and its execution
An authorized order to make a quantity of an item by a released routing and bill of materials version, with its release, operation confirmations, scrap and completion. Lots, stock and shipments belong to the inventory contours.
Partially published; research continues
Claude: initial-industry-contour-and-card-supplement; Grok: not-started.
Published results
The independent second-provider study, fixtures and the full research protocol remain open. Runtime promotion is governed by the package allocation holds.
Subject boundary and candidate types
- ProductionOrder
- OrderOperation
- OperationConfirmation
- MaterialConsumption
- ScrapRecord
- OrderCompletion
Deep research questions
- Which routing and bill of materials versions are frozen on the order at release?
- How are planned, confirmed, scrapped and completed quantities kept apart?
- When does a change of quantity or date create a revision rather than a new order?
Verifiable invariants
- A released order references exactly one routing version and one bill of materials version
- Good plus scrapped quantity never exceeds started quantity without a recorded reason
- An operation confirmation names the work center, the time and the confirming person or system
End-to-end acceptance scenario
On a synthetic order for 100 units, release it with frozen versions, confirm two operations with partial scrap, split the remainder into a second order and close both with consistent quantities.
Negative case
A sales order line is treated as the production order, so a change of the customer's date silently changes what the shop floor is making.
Approaches to compare
- ISA-95 / IEC 62264: production schedule, work order and production performance
- ISO 22400: key performance indicators for manufacturing operations management
- Manufacturing execution and ERP practice: order release, confirmation and closure
Candidates in the live catalogue
- WM-ACT-007 · Work Order · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-010 · Production Run · 1.0.0 · installable
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.