ISA-95: The Standard That Defines How Plant Systems Talk to Business Systems

ISA-95 is the international standard (published as IEC 62264) that defines how enterprise business systems and plant-floor systems should exchange information, giving manufacturers a shared vocabulary and set of models for connecting ERP, MES, SCADA, and control equipment. Instead of every integration being invented from scratch, ISA-95 describes what each layer of a plant does, what data it owns, and how messages between layers should be structured.

The five levels of the ISA-95 model

The standard organizes a manufacturing business into levels, usually drawn as a pyramid:

• Level 0: the physical process itself, the machines transforming material.
• Level 1: sensors and actuators reading and manipulating the process.
• Level 2: control systems, PLCs, and SCADA or HMI software supervising the process in real time.
• Level 3: manufacturing operations management, the domain of the MES: scheduling, dispatching, quality workflows, maintenance operations, and performance analysis.
• Level 4: business planning and logistics, the ERP layer: orders, inventory accounting, and long-range planning.

Each level runs on a different clock. Level 1 thinks in milliseconds, Level 2 in seconds, Level 3 in minutes and shifts, Level 4 in days and months. Many integration failures come from ignoring that mismatch and pushing raw millisecond data at systems built for daily aggregates.

What ISA-95 actually standardizes

Beyond the pyramid picture, the useful substance of ISA-95 is its object models: standard definitions for personnel, equipment, material, and process segments, plus message models for production schedules, production performance, and capability. These models are what make it possible for an ERP from one vendor and an MES from another to agree on what a "production order confirmation" contains. The B2MML XML schemas implement these models in a machine-readable form that integration teams can adopt directly.

A worked example: one production order through the levels

A beverage plant receives an order for 10,000 cases. Level 4 (ERP) creates the production order and sends a schedule message down. Level 3 breaks it into two shifts on filler line 2, reserving materials and dispatching work. Level 2 executes: the line PLC runs recipes, and supervisory software records 96,400 good bottles and 3,600 rejects across 14 hours of run time. Level 3 aggregates that into a production performance message: 9,640 good cases, 360 cases of loss, with downtime coded to two changeovers and one label-jam pattern. Level 4 receives exactly the summary it needs for inventory and costing, not a flood of sensor points. Every layer got data at the granularity it can act on, which is the entire point of the standard.

The pyramid under pressure: ISA-95 and the unified namespace

Modern architectures increasingly replace strict layer-to-layer messaging with a unified namespace, a central hub where every system publishes and subscribes to live data. That changes how data moves, but it does not make ISA-95 obsolete: the object models and level responsibilities remain the common language for what the data means. Transports like OPC UA and MQTT carry the data; ISA-95 still describes the business semantics behind it.

ISA-95 and ISA-88

ISA-95 is often mentioned alongside ISA-88, the batch control standard. The short version: ISA-88 standardizes how recipes and batch procedures are structured inside Level 2 and Level 3, while ISA-95 standardizes how operations as a whole talk to the business layer. Batch-heavy industries such as food, beverage, and pharma typically use both.

Where Fabrico fits

Fabrico operates squarely in the Level 2 to Level 3 space: it captures real-time production data (including via computer vision on machines with no PLC access), turns it into OEE and loss analysis, and runs the maintenance operations side of Level 3 with a full CMMS: work orders, assets, spare parts, and preventive scheduling. It is not an ERP and does not replace Level 4; it produces the clean, structured operational data that Level 4 systems and integration projects depend on. Being EU-built with EU data residency, it also keeps that operational data under European governance. You can see the production side in the OEE and computer vision overview.

Frequently Asked Questions

Is ISA-95 mandatory or certified?

No. ISA-95 is a reference model, not a regulation. Nobody certifies a plant as "ISA-95 compliant." Its value is shared vocabulary: integration projects go faster when both sides describe systems and messages the same way.

How is ISA-95 different from OPC UA?

They answer different questions. OPC UA is a communication technology for moving data between systems securely. ISA-95 defines what the systems are, which data belongs to which layer, and what business messages mean. Many projects use OPC UA as the transport for ISA-95-shaped information.

Does a mid-size factory need to care about ISA-95?

You do not need to read the standard cover to cover. But when you buy or integrate MES, OEE, or CMMS software, the level model helps you scope what each system should own, and it protects you from projects that try to push ERP responsibilities onto the shop floor or vice versa.

Want a clean Level 3 data foundation without a multi-year integration project? Book a Fabrico demo to see real-time OEE, computer vision, and a field-ready CMMS working from one data layer.