ISA-95 for plant leaders: where ERP ends, where MES begins, and why the boundary matters

What ISA-95 is

ANSI/ISA-95, Enterprise-Control System Integration, is a multi-part standard from the International Society of Automation, published internationally as IEC 62264. It defines the interface between enterprise business systems and manufacturing control systems: which activities sit on each side, and what information passes between them. Part 1, covering models and terminology, was revised in a 2025 edition. Part 3 describes the activity models of manufacturing operations management.

ISA-95 describes functions and information, not products. That is its main value to a buyer: offers from different vendors can be compared against the same model rather than against each vendor’s own terminology.

The functional levels

The time frames are the most practical part of the model. Level 4 plans in days and weeks; the floor reacts in minutes and seconds. Decisions that need minute-level response, such as re-sequencing after a breakdown or holding a lot after a failed test, do not belong in a system designed for daily or weekly planning cycles. Equally, planning logic duplicated at Level 3 creates a second version of the master data.

The four areas of manufacturing operations management

Part 3 of the standard divides Level 3 into four areas of operations management. Each is a set of activities, not a software module: one application may serve several areas, or several applications may share one.

• Production operations: dispatching, detailed scheduling, execution, production tracking and performance analysis.
• Maintenance operations: maintenance requests and work orders, scheduling, execution and analysis of equipment performance.
• Quality operations: test definitions, test execution, quality tracking and analysis, and the release or hold of material.
• Inventory operations: managing and tracking the movement, location and status of material within the plant.

Within each area the standard applies the same generic activities: definition management, resource management, detailed scheduling, dispatching, execution management, data collection, tracking and performance analysis. The repetition is deliberate. It allows a plant to check, area by area, whether every activity has an owner.

What crosses the Level 3–4 boundary

The standard’s value lies less in the levels than in the information exchanged between them. In broad terms, Level 4 sends down what to make and with what: production schedules, product definitions, and material and resource availability. Level 3 returns what happened: production performance, material consumed and produced, quality results and equipment capability.

Part 2 of the standard defines the object models for these exchanges. B2MML, maintained by MESA International, implements those models as XML schemas, with a JSON version also available, so that integrations can use a published structure instead of a bespoke mapping on every project.

Using the model to scope a system

A practical exercise is to list the information objects that matter to the plant and agree one system of record for each, before any product is selected.

Where two systems both claim to be the record for the same object, the result is double entry and reconciliation work. The exercise is short when operations, quality, maintenance and IT leads are in the room together, and it prevents most of the scope disputes that otherwise surface during implementation.

Three common misreadings

1. “The levels are a network diagram.” They are a functional hierarchy. Modern architectures may move data between levels through message brokers or shared data layers; the functional boundaries still apply.
2. “MES must be one product.” Part 3 describes activities. A plant may meet them with one suite, several applications, or a mix of packaged and custom software, provided each activity has an owner and the information flows are defined.
3. “ISA-95 is only for large enterprises.” The model scales down. A single plant benefits from the same clarity on who owns schedules, lots and quality results, and a small team has less capacity to absorb double entry.

The same equipment hierarchy (site, area, line and cell) is also the natural structure for machine data. Our guide to connecting legacy machines explains why context matters as much as the connection itself.

How OrbitX approaches this

We use ISA-95 as the neutral reference when scoping, because it describes functions rather than products, our own solution included. The scoping table above is completed with your operations, quality, maintenance and IT leads before any product is discussed, and every proposal, ours among them, is compared against it. See how this fits into the Orbit Method.