Two plants land on the same row of a report, and the meeting asks why one performs worse. Before that question there is another one. Do the two figures come from the same definition? If the content, the context, the reference time, the system boundary, or the company threshold does not match, the row is comparing labels.
This page is the method for checking that. The figure stays at its plant until those five boxes are written the same way. It does not rank sites. It does not reconcile the systems inside one hall. The comparison is between plants that do not measure with the same cut. If one box differs, stop and fix the definition before the meeting argues about performance.
The same indicator name is not the same measure
A matching name does not prove a matching measure.
ISO 22400-1 says a KPI is standardized to the extent that a correct, complete and unambiguous standard exists, and that this standard can be plant-wide, corporate-wide or industry-wide. It says validity is the syntactic and semantic compliance between the operational definition and the standard definition, and that if no standard exists, validity is zero. ISO 22400-1
Validity, in that sentence, is not a statistical test. It is compliance of the operational definition with the standard definition. A standard that exists only for one plant can be met there and still be useless for the next row. The criterion does not say what share of plants already agree. If there is no standard, the comparison stops.
The stated benefit is narrower than a ranking. ISO 22400-1 says an international standard for KPIs is beneficial for comparing enterprise operations over extended periods of time and for comparing similar operations of enterprises within an industry. ISO 22400-1 preview The sentence covers similar operations, and it covers comparison over time. It does not say that two indicators defined in different ways are already comparable, and it does not provide a method for ordering plants.
ISO 22400-1 defines a key performance indicator as a quantifiable level of achieving a critical objective. Its note says KPIs are derived directly from, or through an aggregation function of, physical measurements, data and/or other KPIs. definition in ISO 22400-1 Aggregation is part of the definition. The clause does not say that aggregating local figures removes a difference of scope, of time base, or of population.
ISO 22400-1 says performance monitoring is specific to identified objectives of the enterprise, and that KPIs are most useful when their values identify trends relative to operational objectives. It also says operational areas such as sales, manufacturing, engineering, marketing and business support have different sets of performance indicators that are used together. criteria in ISO 22400-1 That is why one enterprise uses more than one family of indicators.
It is not a method for comparing plants, and it does not rank those areas.
The ISO catalog says ISO 22400-1:2014 was last reviewed and confirmed in 2025, so that edition remains current. Its abstract describes an industry-neutral framework for defining, composing, exchanging and using MOM KPIs, as defined in IEC 62264-1, for batch, continuous and discrete industries, including criteria for constructing KPIs. ISO 22400-1 catalog Confirmation means the 2014 edition remains current.
It does not mean every plant already uses it, and the abstract does not contain the comparability criterion or the content and context lists. If there is no standard, or the definition does not comply with it, the comparison stops.
Hierarchy level and the time base change the figure
The same wording can fail to fit in the same column once the clock or the level changes. The standards do not assign an interval to each level.
ISO 22400-2 defines reference time as the base timeline for time models, corresponding to the planned maximum interval available for production and maintenance tasks, with examples of a calendar day of 24 hours and a week. Planned time is the planned duration of a specific period. Actual time is the realized duration and may be less than, equal to, or greater than the corresponding planned time. A time model is a partition of the reference time. ISO 22400-2
If one plant partitions the calendar day and the other partitions the week, the time model is not the same.
The public text names planned busy time and actual unit busy time, but it does not include the formulas that combine them. Do not complete those formulas from memory. A draft remark about continuous operations is not in the 2014 text.
ISO 22400-2 says the functional-hierarchy levels provide different functions and work in different timeframes: Level 4 is business planning and logistics, Level 3 is manufacturing operations and control, and Levels 1 and 2 are batch, continuous or discrete control.
Enterprise, site and area are generic terms, while work-centre and work-unit terms are specific to batch, continuous, discrete or repetitive production and to storage and movement. hierarchy in ISO 22400-2 That sentence does not assign minutes to Level 2 or a month to Level 4. Sharing “site” or “area” does not mean the same process or the same size.
ISO 22400-2 says the KPIs in that part reside at Level 3, are generated or calculated within Level 3, and that some are forwarded to Level 4. Parameters from Levels 2 and 1 might be needed. The part uses generic terms such as work centres and work units rather than industry-specific terms, and its equipment KPIs relate to work units as specified in IEC 62264. Level 3 in ISO 22400-2
“Might be needed” is not a finding that every plant stores Level 1 and Level 2 history at the same granularity. Forwarding a Level 3 indicator to Level 4 does not make the local definitions identical.
ISO/TR 22400-10 says a work unit log is a data recording of work unit events together with their time stamps. It says the report describes practical use of the formulae in ISO 22400-2 for production control and monitoring and is to be applied together with that part. Its dated normative reference is ISO 22400-2:2014. ISO/TR 22400-10 The contents list worked examples and energy-calculation logs, but those numbers are not in the free text.
Do not cite them as plant results, and those titles are not a method for comparing energy.
ISO/TR 22400-10 defines planned shut down time as time in which the work unit is planned to be out of operation, and planned down time as time, included in the planned operation time, in which the work unit is planned for no operations. It notes that ISO 22400-2:2014 Figure 3 gives an overview of the time lines for work units. time partitions in ISO/TR 22400-10 Those are two partitions, not a complete plant calendar.
The figure is not in the free text, so its boxes are not described here. A local label such as downtime can still fail to match either term.
IEC 62264-1:2013 describes Level 3 manufacturing operations management and the interface content and transactions within Level 3 and between Level 3 and Level 4. Its stated goals are to increase uniformity and consistency of interface terminology and to reduce the risk, cost and errors associated with implementing these interfaces. The second edition extended both the functional hierarchy and the equipment hierarchy using IEC 62264-3 and added a physical asset equipment model. IEC 62264-1:2013
The uniform terminology here is the terminology of the interface between enterprise and control. The abstract does not define site, area, work center, or work unit, and it does not say that matching interface names make the formulas comparable.
ISA’s ISA-95 overview says the standard, also known as ANSI/ISA-95 or IEC 62264, organizes technology and business processes into layers defined by activities and outlines an interface among those layers. It says the equipment hierarchy model can be applied across discrete, continuous and logistics industries, and that the levels allow practitioners to describe boundaries between systems. Part 1 includes a discussion of how physical assets of a manufacturing enterprise are organized.
The page says the standard primarily deals with the interface between level 3 and level 4. ISA-95 This is an overview page, not the clause text. It locates the asset and the boundary. It does not explain why the systems inside one plant stop talking to each other. That is SCADA, historian, MES and ERP. The product examples by level on that page are not indicator definitions.
A shared dictionary does not flatten the plants
Using the same standard name does not put the two plants in the same slot.
ISO 22400-1 says a KPI is comparable to the extent that means are defined to reference supporting measurements over a period of time, and that a normalizing factor expresses the indicator in absolute terms with appropriate units of measure. ISO 22400-1 The text does not say which factor to use, and it does not say that a ratio makes two sites equivalent.
The ISO 22400-2 catalog says the KPIs are presented by their formula and corresponding elements, their time behaviour, their unit or dimension and other characteristics, and that the part indicates the user group and the production methodology to which they correspond. With reference to equipment, those KPIs relate to work units as specified in IEC 62264. ISO 22400-2 catalog It does not print the formulas, and it does not give a count.
It speaks of a selected number in current practice. Citing the part does not erase the user group or the production methodology.
ISO 22400-2 describes manufacturing operations management as production, maintenance, quality and inventory operations. Each category’s activity model includes detailed scheduling, dispatching, execution management, resource management, definition management, tracking, data collection and analysis. Analysis is the performance of calculating KPIs using information from other activities. activities in ISO 22400-2 That is a model of where an indicator is calculated, not an account of why the systems inside one plant disagree.
ISO 22400-2 says KPIs alone are not sufficient for the necessary management and execution operations. For many indicators a company-specific threshold is defined, and crossing it initiates action, for example to improve efficiency or quality. It says warning and action limits are often necessary so that trends are detected before the company-specific threshold is violated. thresholds in ISO 22400-2 The threshold belongs to the company.
The text does not authorize copying a corporate limit without restating the context.
The public contents of ISO 22400-2 include an annex titled Alternative OEE calculation based on loss time model. The 2014 introduction also defines KPIs, in that introductory wording, as quantifiable and strategic measurements that reflect an enterprise’s critical success factors. ISO 22400-2 contents Only the annex title is public, not the calculation. That introduction does not replace the Part 1 definition, and this page does not produce a closed count of indicators.
NISTIR 8107 places ISO 22400 as defining key performance indicators used in manufacturing operations management, and places IEC 62264, based upon ISA-95, as defining activity models, function models and object models in the MOM domain. It describes ISA-95 as a commonly used reference model for automated interfaces between enterprise and control systems, developed for global manufacturers and designed for all industries and for batch, discrete and continuous processes. NISTIR 8107
It does not measure how often plants define the same indicator differently. “Global manufacturers” and “all industries” describe the intended scope, not a result that sites already match. Context for a record inside one plant is a different job, covered in industrial data context.
Match the definition before a figure moves
The figure can wait.
ISO 22400-1 says a KPI is characterized by content and context. Content is a quantifiable element with a specific unit of measure and, when defined, should include name, identifier, description, scope, formula, unit of measure, range and trend. Context is a verifiable list of conditions that are met; the retrieved text says the specification should include timing, constraints, usage, audience, production methodology and an effect-model diagram. content and context in ISO 22400-1
Do not add context fields from beyond the public preview. In the retrieved examples, scope may be a work unit, a work center, a work order, a product, or personnel. A work unit against an area stops the figure.
Someone who writes only “daily,” without saying whether that is the 24-hour day, the planned time, or the actual time, leaves the time box half done. reference time in ISO 22400-2
Company-specific reading shows up in planning standards too. ISO 18828-4 ISO 18828-4 says that, beyond a uniform core set, companies often use a self-defined range of measurable values and a target-oriented, company-specific interpretation. It says the indicators by themselves cannot measure process performance. Continuous comparison with process improvement requires thresholds that are defined and applied, and those thresholds depend on the particular company.
It also says system boundaries of the analysis need attention, and that a general trend or theoretical optimum still needs company-specific examination and an application-based interpretation before use. Adaptation is a condition, not an automatic transfer from planning indicators to operations indicators.
NIST’s operations-driven performance-measurement project says that making full use of manufacturing-operations data is impeded by a lack of well-defined methods and standards, and that system characterization defines the frame of reference needed to evaluate and improve the performance of a system against a norm. It says the work explores formalized performance metrics, standardized modeling methods and standard guidelines for applying performance measures. NIST measurement project
The page was updated on 26 March 2025, and plans from earlier fiscal years are still in the body. It is not a benchmark across sites, and it is not a count of plants.
The same NIST project page says deriving effective performance metrics is difficult because manufacturing systems are complex, and that a key technical barrier is to develop models that use the data produced by operations together with the desired performance metrics.
It also says every unit manufacturing process may have a unique set of KPIs, and that guidelines for selecting those KPIs strengthen both the characterization of an individual process and system improvement. metrics in the NIST project “Unique set” refers to unit manufacturing processes in that plan, including sustainability. It is not a census of OEE, and it is not a failure rate.
Yan Lu, KC Morris, and Simon Frechette write that when a sustainability assessment has to resolve trade-offs and apportion impacts between production and the product, standards are needed to supply unambiguous and comparable data for that decision. NISTIR 8107 The sentence stays inside sustainability assessment. It does not turn a table of operating indicators into a valid ranking.
WizeeMind is a plant assistant that keeps source, time, asset and approval limits with the evidence. It does not make two plants comparable by itself.
Sorting two figures on a sheet does not fill the card. That is the shortcut in the Excel trap in production. Without the examination that belongs to each company, the figure does not move.
What this method does not decide
The ISO 22400-2 catalog lists Amendment 1, edition 2017, under the title Key performance indicators for energy management, and says amendments are additional content not included in the text of the existing standard. The same record places the 2014 edition at stage 90.92, to be revised, with ISO/DIS 22400-2 under development. ISO 22400-2 catalog The page does not define those indicators.
Do not cite the draft, and the title is not a method for comparing energy between plants.
ISO 18828-4 specifies KPIs in production planning that allow comparison and monitoring of the production-planning process in a standardized framework. It organizes them in a multi-level system. The scope is limited to production planning for products in series production and only to tasks carried out inside that planning process. The indicators are recommendations. ISO 18828-4 That is comparison of planning processes, not of operating performance.
Do not reuse its ratios, such as an information waiting time or an area utilization, as if they were ISO 22400 operations indicators.
ISA’s overview of ISA-95 Part 7 says that part defines technology-independent services and messages for associating and mapping aliases, meaning equivalent identifiers, and associated context exchanged between manufacturing-operations applications and applications in other domains. It says identification of the organization and owner of each system, and lifecycle management of the equivalent object namespaces, are outside the scope of that part. ISA-95 Part 7 The map equates identifiers and carries context.
It does not reconcile formulas, time models, or denominators, and the owner of each namespace stays outside.
NISTIR 8107 says integration from machine to plant to enterprise systems is vital and critically depends upon standards. NISTIR 8107 The same report concludes that existing manufacturing standards are not enough to fully enable smart manufacturing, especially for cybersecurity, cloud-based manufacturing services, supply-chain integration, and data analytics. That does not say ISO 22400 fails as a dictionary of indicators.
Comparing shifts inside one historian is a different job, covered in five analyses hidden in the plant historian. Once the difference has been matched, spending is decided in plant investment decisions. If the boxes do not match, argue about the box, not the value.
Frequently asked questions
Can two plants that use the same indicator name be compared?
No, not while each plant keeps a different definition. In ISO 22400-1, comparability is a property of the definition, not an effect of the shared name. Means have to be defined to reference the supporting measurements over a period of time, and a normalizing factor has to express the indicator in absolute terms with appropriate units. ISO 22400-1 The text does not choose the factor, and a ratio does not make two sites equivalent.
Why do the level and the clock change the figure?
The Part 2 indicator is calculated at Level 3, and reference time may be a 24-hour day or a week. Actual time may be less than, equal to, or greater than planned time. Forwarding the number to Level 4 does not prove that the two plants stored the same detail from the lower levels. ISO 22400-2 The work unit log, with its time stamps, is applied together with that part. ISO/TR 22400-10
ISA-95 places the boundary between systems and does not validate the formula. ISA-95
Is adopting ISO 22400 enough to make the plants match?
No. The 2014 edition of Part 1 remains current after the 2025 confirmation, and the threshold that starts an action remains specific to the company. ISO 22400-1 catalog Current does not mean applied in each plant, and the abstract does not bring the content and context lists. Copying the group threshold without rewriting the context is not authorized. thresholds in ISO 22400-2
What has to be written down before a figure moves between plants?
Content, context, reference time, the system boundary, and the company-specific threshold have to be written down. If one box is blank, the figure does not move. Reference time is the base timeline, and a time model is its partition. A general trend still needs the company’s own examination before it is used. ISO 18828-4 Write the five boxes for one indicator and two plants. Leave the figure where it is until those boxes match.
Does this method cover energy or planning indicators?
No. The energy amendment sits outside the text of ISO 22400-2:2014, and the indicators in ISO 18828-4 compare series-production planning, not the operating performance of plants. Neither the amendment nor the revision draft enters this card. ISO 22400-2 catalog ISO 18828-4
When the indicator is not in those two groups, the next step is to fill the five boxes for one indicator and two plants, and leave each figure where it is until the five match.