Downtime and production performance
Explain where production time and output were lost, with reasons and reproducible figures, so that improvement work targets real causes.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 6 findings · 10 questions
Loss events This bundle records stops, speed losses and quality losses with their reasons.
Stops and losses
This layer records loss evidence and its treatment under declared calculation rules.
Downtime events
This finding records each stop and whether it contributes to availability loss.
- Which work center, start time, end time and reason does this downtime event record?
- How does this downtime event overlap planned production time, and which declared calculation rule determines its inclusion in or exclusion from availability loss?
Reason history
This finding preserves the original and revised reasons for a recorded loss.
- Who changed the reason in this loss record, when was it changed and what original reason was retained?
Speed losses
This finding records reduced output relative to the declared ideal rate.
- What interval, ideal rate, actual output and loss reason does this speed-loss record declare?
Quality losses
This finding records output treated as quality loss under the declared counting rules.
- What affected quantity, disposition, counting rule and loss reason does this quality-loss record declare?
Performance figures This bundle records reproducible indicators and the basis for comparing them.
Indicators
This layer records indicator values, calculation inputs and comparison assessments.
Indicator values
This finding identifies a calculated value and the rules and evidence supporting it.
- What indicator, value, work center scope and reporting period does this indicator record declare?
- Which formula version, input records, time boundaries, exclusions, ideal rates and counting conventions support this indicator value?
Comparability
This finding records whether explicitly identified performance records support a meaningful comparison.
- Which two plants, scopes, periods and indicator records does this comparison assessment identify, and how does it address differences in formulas, time boundaries, exclusions, ideal rates and counting conventions?
- Which production counts and scrap counts feed this shift report?
- Which maintenance work orders are linked to this downtime event?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseMFG
- Industry
- Manufacturing
- Tags
- EM-MFG-07W-INDsubjectDowntimeEventDowntimeReasonProductionCountPerformanceIndicatorShiftReport
What it is Filled
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.
Why it exists Filled
Explain where production time and output were lost, with reasons and reproducible figures, so that improvement work targets real causes.
Distinguishing features Filled
- Indicators are derived from recorded events and can be reproduced.
- Comparability depends on formula versions, time boundaries, exclusions, ideal rates and counting conventions.
- A planned stop within planned production time may count as an availability loss under the declared calculation rules.
- Stop, speed-loss and quality-loss reasons retain their change history.
- Maintenance work orders stay in the asset contour and are linked, not copied.
What robots and AI may and may not do Filled
Must not
- Change recorded reasons without keeping the original.
- Exclude a stop from availability loss solely because it was planned.
- Claim comparability from a shared formula version without assessing time boundaries, exclusions, ideal rates and counting conventions.
- Use indicators to rank individual workers without an approved purpose.
Only with a human decision
- Changes to reason code lists and indicator formulas need approval by the head of production.
- Use of performance data for personnel decisions needs an approved policy.
May
- Compute indicators from events using a stated formula version and declared calculation basis.
- Flag overlapping or unexplained stops.
- Summarize the top loss reasons for an identified period.
Moral aspects Filled
- Performance data can be used for intrusive monitoring of individual workers.
- Targets on indicators can push people to misreport stops.
Who is affected
- Operators and shift leaders
- Maintenance staff
- Plant management
Owners Filled
Steward
The head of production who answers for production performance reporting.
Master systems
- Manufacturing execution system
- Process data historian
- Enterprise asset management system
Links to other meta-models Filled
neighbor
- EM-MFG-03
- EM-MFG-01
- EM-OPS-03
- EM-DAT-05
- EM-PEO-07
references
- WM-SFT-017 - conceptual-candidate
- WM-DAT-010 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A downtime event is identified by work center, start time and a sequence number.
- An indicator value is identified by indicator, scope, period and formula version.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- Records show stop intervals with reasons, production counts and computed indicators.
- A downtime event must be distinguished from a maintenance work order and from an IT service incident.
Capabilities and actions required Filled
- The contour supports loss analysis, shift reporting and comparison of lines by stated formulas.
Hazards and failure modes required Filled
- Misleading indicators can drive wrong investment or staffing decisions.
- Pressure on figures can hide stops that matter for safety.
Standards and interfaces optional Filled
- ISO publishes ISO 22400 with definitions of key performance indicators for manufacturing operations management.
- ISA publishes ISA-95, adopted internationally as IEC 62264, which includes production performance information.
Context of use required Filled
- The contour is used on lines and work centers with recorded production counts.
- Data may come from automatic machine signals or manual shift reports.
Sources Filled
- ISO 22400: key performance indicators for manufacturing operations management
- ISA-95 / IEC 62264: production performance
- Lean manufacturing practice: loss categories and overall equipment effectiveness
- ISA-95 Standard: Enterprise-Control System Integration - Checked live (HTTP 200) on 2026-10-21.
- IEC 62264-1:2013 Enterprise-control system integration - Part 1: Models and terminology - Checked live (HTTP 200) on 2026-10-21.
Open 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?
- 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-07/brief.json, ver-cy/world-models/card-supplements/em-mfg-07.json