Routing and operation card
Keep one approved, versioned description of how an item is made, so that orders, operators and inspections use the same steps and limits.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 9 questions
Routing definition The approved operations of an item and their order.
Versions and effectivity
Which routing version applies where and when.
Routing version
An approved version with its effectivity.
- Which routing version is effective for this item, plant and date?
- Who approved this routing version and on what basis?
- Which changes were made in this routing version compared with the previous one?
Alternatives
Alternative routings and work centers allowed for capacity or resource reasons.
- Which alternative routings or alternative work centers exist for this operation, and when may they be used?
Operation content What each operation requires and checks.
Operation requirements
Resources, parameters and checks of one operation.
Resources and skills
Work center, tools, qualifications and times.
- Which work center, tools and operator qualifications does this operation require?
- What setup and run times are planned for this operation?
Parameters and checks
Binding limits, guidance and inspection points.
- Which parameters of this operation are binding limits, with which units and ranges?
- Which inspection points are attached to this operation?
- Which work instruction documents belong to this operation, and which revision is current?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseMFG
- Industry
- Manufacturing
- Tags
- EM-MFG-02W-INDsubjectRoutingRoutingVersionOperationOperationParameterToolRequirement
What it is Filled
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.
Why it exists Filled
Keep one approved, versioned description of how an item is made, so that orders, operators and inspections use the same steps and limits.
Distinguishing features Filled
- A routing describes how to make an item, while the bill of materials describes what it is made of.
- Versions with effectivity are distinct from alternatives used for capacity or resource reasons.
- Binding parameters carry units and ranges, and guidance is marked separately.
- Inspection points link the routing to the quality inspection plan.
- Distinct from a generic process definition, a routing is tied to an item and a plant.
What robots and AI may and may not do Filled
Must not
- Approve or activate a routing version.
- Change binding parameters on an approved version.
- Present operator notes as approved instructions.
Only with a human decision
- A responsible manufacturing engineer must approve each routing version.
- Changes that affect product safety or regulatory filings require quality approval.
May
- Compare routing versions and list their differences.
- Flag binding parameters without units or ranges.
- Draft a routing change proposal for engineering review.
Moral aspects Filled
- Unclear instructions shift the blame for defects to operators.
- Skill requirements can exclude workers if they are set without a real need.
Who is affected
- Operators and setters
- Manufacturing and quality engineers
- End users of the product
Owners Filled
Steward
The lead manufacturing engineer who answers for how items are made.
Master systems
- Product lifecycle management system
- Manufacturing execution system
- ERP
Links to other meta-models Filled
neighbor
- EM-OPS-01
- EM-OPS-04
- EM-MFG-01
- EM-MFG-03
- EM-MFG-05
- EM-PEO-03
references
- WM-OBJ-018 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A routing is identified by item, plant and routing number, and each version by a version label.
- Each operation is identified by its sequence number within the routing version.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- Records list ordered operations with work centers, times and parameters.
- A routing must be distinguished from a bill of materials and from a generic process map.
Capabilities and actions required Filled
- The contour supports selection of the effective routing for a production order.
- The contour supports comparison of versions and traceability of changes.
Hazards and failure modes required Filled
- A wrong or outdated parameter limit can create unsafe or nonconforming product.
- Uncontrolled alternatives can bypass required inspection points.
Standards and interfaces optional Filled
- ISA publishes ISA-95, adopted internationally as IEC 62264, which models product definitions and process segments.
- ISO publishes ISO 10303 (STEP) for product data representation and exchange, including process plans.
Context of use required Filled
- The contour is used in discrete assembly, machining, batch and process manufacturing.
- In process industries the equivalent record is often called a master recipe.
Sources Filled
- 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
- ISA-95 Standard: Enterprise-Control System Integration - Checked live (HTTP 200) on 2026-10-21.
- ISO 9001:2015 Quality management systems - Requirements - Checked live (HTTP 200) on 2026-10-21.
Open 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?
- Settle the boundary and the reuse, extend or new decision against the current specifications.
- Confirm the semantic crosswalk, rights and source mastership.
- Choose immutable references and run fixture checks before claiming publication readiness.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-mfg-02/brief.json, ver-cy/world-models/card-supplements/em-mfg-02.json