EM-MFG-03 · Subject model · W-IND
Work center and production line
A unit of production capability: a work center, line or cell, its place in the plant hierarchy, capability, calendar and nominal capacity. Individual machines are assets in the asset contour.
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
- WorkCenter
- ProductionLine
- EquipmentHierarchyLevel
- WorkCenterCapability
- ProductionCalendar
- NominalCapacity
Deep research questions
- How does the work center hierarchy relate to the asset register and to cost centers?
- How is nominal capacity distinguished from available and planned capacity?
- When does replacing a machine change the work center identity?
Verifiable invariants
- A work center belongs to exactly one plant area at a time
- Nominal capacity states its unit and calendar basis
- Replacing an asset inside a work center keeps the work center identity
End-to-end acceptance scenario
On a synthetic plant with two lines and one shared cell, model the hierarchy, replace one machine, move the cell to another area and show which production orders and capacity figures change.
Negative case
A cost center is used as the work center, so two lines with one budget appear as one production resource.
Approaches to compare
- ISA-95 / IEC 62264: role-based equipment hierarchy
- IDTA Asset Administration Shell: description of equipment and its capabilities
- ISO 22400: availability and capacity indicators
Candidates in the live catalogue
- WM-OBJ-006 · Equipment / Machinery · 0.3.0-draft · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-BLT-006 · Facility · 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.