{"schema":"https://ver.cy/schemas/card/1.0.0","id":"EM-MFG-07","code":"em-mfg-07","url":"https://ver.cy/models/em-mfg-07/","name":"Downtime and production performance","alternateNames":[],"kind":"enterprise-contour","status":"published","version":"research-checkpoint","language":"en","classifiers":{"family":"Enterprise profiles","category":"Enterprise subject","entryKind":"subject","plane":"","domain":["Enterprise","MFG"],"industry":["Manufacturing"],"navPath":"","tags":["EM-MFG-07","W-IND","subject","DowntimeEvent","DowntimeReason","ProductionCount","PerformanceIndicator","ShiftReport"],"facets":{}},"whatItIs":"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.","purpose":"Explain where production time and output were lost, with reasons and reproducible figures, so that improvement work targets real causes.","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"loss-events","name":"Loss events","description":"This bundle records stops, speed losses and quality losses with their reasons.","layers":[{"id":"stops-and-losses","name":"Stops and losses","description":"This layer records loss evidence and its treatment under declared calculation rules.","findings":[{"id":"downtime-events","name":"Downtime events","description":"This finding records each stop and whether it contributes to availability loss.","questions":[{"text":"Which work center, start time, end time and reason does this downtime event record?","id":"stop-details"},{"text":"How does this downtime event overlap planned production time, and which declared calculation rule determines its inclusion in or exclusion from availability loss?","id":"availability-treatment"}]},{"id":"reason-history","name":"Reason history","description":"This finding preserves the original and revised reasons for a recorded loss.","questions":[{"text":"Who changed the reason in this loss record, when was it changed and what original reason was retained?","id":"reason-change"}]},{"id":"speed-losses","name":"Speed losses","description":"This finding records reduced output relative to the declared ideal rate.","questions":[{"text":"What interval, ideal rate, actual output and loss reason does this speed-loss record declare?","id":"speed-loss-basis"}]},{"id":"quality-losses","name":"Quality losses","description":"This finding records output treated as quality loss under the declared counting rules.","questions":[{"text":"What affected quantity, disposition, counting rule and loss reason does this quality-loss record declare?","id":"quality-loss-basis"}]}]}]},{"id":"performance-figures","name":"Performance figures","description":"This bundle records reproducible indicators and the basis for comparing them.","layers":[{"id":"indicators","name":"Indicators","description":"This layer records indicator values, calculation inputs and comparison assessments.","findings":[{"id":"indicator-values","name":"Indicator values","description":"This finding identifies a calculated value and the rules and evidence supporting it.","questions":[{"text":"What indicator, value, work center scope and reporting period does this indicator record declare?","id":"indicator-result"},{"text":"Which formula version, input records, time boundaries, exclusions, ideal rates and counting conventions support this indicator value?","id":"calculation-evidence"}]},{"id":"comparability","name":"Comparability","description":"This finding records whether explicitly identified performance records support a meaningful comparison.","questions":[{"text":"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?","id":"comparison-assessment"},{"text":"Which production counts and scrap counts feed this shift report?","id":"shift-counts"},{"text":"Which maintenance work orders are linked to this downtime event?","id":"maintenance-links"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["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."]},"ethics":{"considerations":["Performance data can be used for intrusive monitoring of individual workers.","Targets on indicators can push people to misreport stops."],"affectedParties":["Operators and shift leaders","Maintenance staff","Plant management"]},"owners":{"steward":"The head of production who answers for production performance reporting.","roles":[],"masterSystems":["Manufacturing execution system","Process data historian","Enterprise asset management system"]},"relations":[{"target":"EM-MFG-03","type":"neighbor"},{"target":"EM-MFG-01","type":"neighbor"},{"target":"EM-OPS-03","type":"neighbor"},{"target":"EM-DAT-05","type":"neighbor"},{"target":"EM-PEO-07","type":"neighbor"},{"target":"WM-SFT-017","type":"references","note":"conceptual-candidate"},{"target":"WM-DAT-010","type":"references","note":"conceptual-candidate"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"required","items":["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":{"applicability":"required","items":["The contour supports loss analysis, shift reporting and comparison of lines by stated formulas."]},"hazards":{"applicability":"required","items":["Misleading indicators can drive wrong investment or staffing decisions.","Pressure on figures can hide stops that matter for safety."]},"interfaces":{"applicability":"optional","items":["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":{"applicability":"required","items":["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":[{"title":"ISO 22400: key performance indicators for manufacturing operations management"},{"title":"ISA-95 / IEC 62264: production performance"},{"title":"Lean manufacturing practice: loss categories and overall equipment effectiveness"},{"title":"ISA-95 Standard: Enterprise-Control System Integration","url":"https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard","note":"Checked live (HTTP 200) on 2026-10-21."},{"title":"IEC 62264-1:2013 Enterprise-control system integration - Part 1: Models and terminology","url":"https://webstore.iec.ch/en/publication/6675","note":"Checked live (HTTP 200) on 2026-10-21."}],"openQuestions":["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."],"resources":{"source":"https://ver.cy/enterprise/models/em-mfg-07/"},"provenance":{"origin":"enterprise research programme","builtFrom":["enterprise/models/em-mfg-07/brief.json","ver-cy/world-models/card-supplements/em-mfg-07.json"],"providers":[],"researchStatus":"published-partial","generatedAt":"","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Enterprise record contour: physical properties belong to referenced world models.","_supplement":"Sections authored in card supplement 1.1.0 by Claude (Opus 5.5) (2026-10-21, unreviewed). Written from the industry contour brief and established practice in the field; source pages were checked live on 2026-10-21. Unreviewed. Revised against an independent Codex review on 2026-10-21.","_gate":"Published through the contour publication gate 1.0 on 2026-10-21T19:02:23+00:00: completeness 1.00; subject: research brief; 2 live sources; review by codex: pass"},"score":1.0}}