Do we need to change our MES or ERP to support ISO 22400?

You usually do not need to replace your MES or ERP to support ISO 22400. ISO 22400 defines a standardized model for manufacturing KPIs (such as OEE) and supporting data, not a specific software product. In most regulated, brownfield environments, the work is to map and extend what you already have, not to rip and replace core systems.

What ISO 22400 actually requires

At a practical level, supporting ISO 22400 means you can:

• Calculate KPIs according to ISO 22400 definitions (e.g., equipment states, time categories, performance factors).
• Trace the source data used for each KPI (events, quantities, time stamps) in a way that is auditable.
• Use consistent terminology and structures so different plants or systems interpret KPIs the same way.

The standard does not mandate a particular MES or ERP vendor, database, or architecture.

When you can keep your existing MES/ERP

In most plants, you can support ISO 22400 by working with your current stack and doing one or more of the following:

• Data mapping: Map existing status codes, order types, equipment hierarchies, and time buckets in MES/ERP to the ISO 22400 structures and categories.
• Configuration changes: Add or adjust reason codes, equipment states, shift calendars, or production event types in MES to align with ISO 22400 definitions.
• Reporting/analytics layer: Implement ISO 22400 logic in a data warehouse, historian, or analytics layer that consumes MES/ERP data, rather than modifying MES/ERP transaction logic.
• Lightweight extensions: Add edge data collection (e.g., machine connectivity) to fill gaps where MES/ERP lacks sufficient granularity for ISO 22400 KPIs.

This approach fits regulated environments where full replacement of MES or ERP triggers extensive qualification, validation, and change-control burdens.

When changes to MES/ERP are actually needed

You may need to modify (but still not replace) MES or ERP if:

• Key ISO 22400 base data is not captured at all (for example, no reliable machine state events or production quantity confirmations).
• Existing status or reason codes are too coarse or overloaded to map cleanly to ISO 22400 categories.
• Time or quantity stamping is inconsistent across lines, plants, or systems, making standardized KPIs untrustworthy.
• There is no reliable way to link equipment, orders, and time (e.g., weak traceability between ERP orders and MES execution).

In these cases, you typically:

• Introduce new event types, fields, or reason codes in MES.
• Standardize master data structures (equipment hierarchy, product families, calendars) in MES/ERP.
• Improve integration so ERP order data and MES execution data can be joined consistently.

All of this needs to go through formal change control, validation, and regression testing in regulated contexts.

Why full replacement is rarely the right path

Replacing MES or ERP solely to “support ISO 22400” is rarely justified in aerospace-grade or similar environments because:

• Qualification and validation cost: New core systems require extensive validation, documentation, and often regulatory notifications or re-approvals.
• Downtime and cutover risk: MES/ERP cutovers can disrupt production if anything goes wrong, which conflicts with tight delivery and compliance demands.
• Integration complexity: Existing MES/ERP are usually integrated with PLCs, historians, QMS, PLM, and LIMS. Rebuilding those integrations only to compute standardized KPIs adds risk with limited benefit.
• Equipment lifecycle: Many assets and controls are qualified for decades; changing the transactional backbone around them can re-open long-closed compliance questions.

In practice, most organizations get ISO 22400 alignment by adding a standardized KPI data model and calculation layer on top of existing systems.

Key dependencies and failure modes

Whether you can stay on your current MES/ERP depends on:

• Data quality: If timestamps, quantities, and states are unreliable, ISO 22400 calculations will be unreliable regardless of the software brand.
• Plant-to-plant consistency: Different code sets and practices across sites can make ISO 22400 rollout difficult without harmonization.
• Integration maturity: Poor integration between MES, ERP, and equipment will limit how far you can go without infrastructure work.
• Change governance: Even small MES/ERP changes can be slow in regulated environments; planning and phasing are critical.

Typical failure modes include treating ISO 22400 as a “tool purchase” instead of a data and governance project, or attempting a big-bang MES replacement that stalls under validation and integration load.

Practical approach for brownfield environments

A pragmatic path in most brownfield, regulated facilities is:

1. Perform a gap analysis: compare current KPI calculations, data sources, and code sets to ISO 22400.
2. Standardize master data and codes where possible without system replacement.
3. Add or adjust MES/ERP configuration and integrations to capture missing events and links.
4. Implement ISO 22400 KPI logic in a reporting/analytics layer, with traceability back to source records.
5. Validate calculations, data flows, and reports under your existing CSV/validation framework.

This preserves your existing MES and ERP investments while still moving toward a standardized KPI framework aligned to ISO 22400.