ISO 22400 can be phased in by site. The standard defines how manufacturing KPIs are structured and calculated, but it does not require a single, simultaneous global go-live.
Phased adoption is normal
In multi-site, regulated environments, most organizations roll out ISO 22400 gradually, for example:
- Pilot on one plant or value stream to harden definitions and data mappings.
- Extend to other lines or sites once the KPI model, interfaces, and reports are stable.
- Backfit legacy reports and dashboards over time, retiring old KPIs under change control.
This approach reduces disruption, limits downtime on critical assets, and respects the validation/qualification burden on MES, historians, and reporting tools.
Key constraints and risks in a site-by-site rollout
A phased approach is feasible, but there are non-trivial constraints you need to manage explicitly:
- Single source of truth for KPI definitions: Maintain a governed catalog of ISO 22400-aligned KPIs (e.g., OEE, availability, performance, quality) so that each site implements the same definition and calculation method.
- Version control and traceability: Treat KPI definition changes like any other controlled document or configuration. You should be able to show which version of a KPI definition was active for which site and time period.
- Mixed-state reporting: During the transition, some sites will use ISO 22400-compliant KPIs and others will not. Enterprise dashboards must clearly label which metrics are ISO 22400-based and avoid blended rollups that silently mix incompatible definitions.
- System coexistence: Brownfield plants will often keep legacy MES/SCADA/ERP reports. Plan for coexistence rather than assuming you can replace them all at once, and map legacy data sources into the ISO 22400 model incrementally.
- Validation and qualification: Any MES, historian, or analytics changes that support ISO 22400 KPIs will typically require validation, especially in aerospace, defense, or medical-adjacent work. Phasing by site can limit scope, but you still need documented test evidence for each environment.
- Operator and supervisor training: Ensure each site understands not just the formulas, but how events (downtime, speed loss, scrap) must be logged to keep ISO 22400 KPIs meaningful. Training content and work instructions should be controlled and consistent.
Why not do a single global cutover?
In long-lifecycle, regulated manufacturing, attempting a “big bang” ISO 22400 rollout across all sites often fails or stalls due to:
- Integration complexity: Sites use different versions of MES, historians, PLC code, and ERP. Aligning all data interfaces and event models at once is high risk.
- Downtime and production risk: Coordinated, multi-site downtime windows are rare. Plants typically cannot accept simultaneous disruption to data collection on critical lines.
- Validation burden: Validating new KPI logic and data flows across all sites at once creates a large, multi-team validation project with high coordination overhead.
- Change saturation: Operators, planners, and quality leads already manage multiple initiatives. Phasing reduces the load and allows lessons learned from early sites to improve later rollouts.
For these reasons, a controlled, incremental rollout is usually more realistic than full replacement of existing KPI and OEE reporting in one step.
How to phase ISO 22400 responsibly
To make a site-by-site approach robust and auditable:
- Define a corporate KPI governance model: Clarify who owns ISO 22400 interpretations, approves changes, and manages the central KPI catalog.
- Choose a reference site: Implement ISO 22400 rigorously at one site first and treat it as the reference implementation for others.
- Standardize data mapping patterns: Document how common events (planned downtime, minor stops, rework, scrap) map to ISO 22400 inputs so other sites can follow the same pattern even with different equipment vendors.
- Maintain clear labeling during transition: Mark reports and dashboards with “ISO 22400-aligned” where applicable, and keep legacy KPIs visibly separate until migrated.
- Use formal change control: Manage each site’s transition as a controlled change, with impact analysis, test plans, and rollback procedures.
In summary, you do not need to implement ISO 22400 everywhere at once. A phased rollout by site is often the only practical option in brownfield, regulated operations, provided you enforce cross-site consistency of definitions, robust change control, and clear traceability for how metrics are calculated and used.
