EM-MFG-02 · Subject model · W-IND
Routing and operation card
The approved way to make an item: operations in sequence, work centers, setup and run times, parameters, tools, skills and inspection points, with versions and effectivity. The bill of materials and generic processes are separate 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
- Routing
- RoutingVersion
- Operation
- OperationParameter
- ToolRequirement
- SkillRequirement
- InspectionPoint
Deep research questions
- Which routing version applies to a given item, plant and date?
- How are alternative routings and alternative work centers kept apart from versions?
- Which operation parameters are binding limits and which are guidance?
Verifiable invariants
- Only an approved routing version can be used to release a production order
- Effectivity periods of versions for the same item and plant do not overlap
- Every binding parameter has a unit and a permitted range
End-to-end acceptance scenario
On a synthetic item made in two plants, approve routing version 2 for one plant with a new inspection point, keep version 1 effective in the other, and show which version each new production order uses.
Negative case
An operator's personal notes on a better setting are copied into the routing without review and become the binding limit.
Approaches to compare
- ISA-95 / IEC 62264: product definition and process segments
- ISO 10303 (STEP): representation of process plans
- Manufacturing engineering practice: routings, work instructions and control plans
Candidates in the live catalogue
- WM-OBJ-018 · Engineering Design / Product Definition · 0.3.0-research.1 · 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.