EM-MFG-07 · Subject model · W-IND
Downtime and production performance
Recorded stops, speed losses and quality losses of work centers with their reasons, and the performance figures derived from them, such as availability and overall equipment effectiveness. Maintenance work belongs to 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
- DowntimeEvent
- DowntimeReason
- ProductionCount
- PerformanceIndicator
- ShiftReport
Deep research questions
- Which reason code list is used, and who may change a recorded reason?
- How are planned stops excluded from availability?
- How are indicator formulas versioned so that periods stay comparable?
Verifiable invariants
- Downtime events of one work center do not overlap in time
- Each indicator value states its formula version and period
- A reason change keeps the original reason and who changed it
End-to-end acceptance scenario
For a synthetic line and one shift, record three stops including one planned stop, a speed loss and a scrap count, compute availability, performance and quality by a stated formula, and reproduce the result from the events.
Negative case
OEE is calculated with planned maintenance counted as a loss in one plant and excluded in another, and the two plants are ranked against each other.
Approaches to compare
- ISO 22400: key performance indicators for manufacturing operations management
- ISA-95 / IEC 62264: production performance
- Lean manufacturing practice: loss categories and overall equipment effectiveness
Candidates in the live catalogue
- WM-SFT-017 · Telemetry / Operational Signal · 0.1.0 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-DAT-010 · Time Series / Observation Collection · 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.