ISA-95, known internationally as IEC 62264, is the standard for integrating enterprise business systems with plant-floor control systems. It defines a five-level hierarchy, a shared vocabulary for equipment and operations, and the data models that let an ERP and an MES exchange information without a hand-built translation for every plant.
That is the textbook version. In practice, ISA-95 is the reason a released order in your business system can become a work order on a specific line, and the reason the counts, genealogy, and quality results from that line can flow back up without anyone retyping them into a spreadsheet. This guide walks the levels, the equipment hierarchy, the four operations domains, and B2MML, the XML that makes the standard usable, then shows where a modern AI layer fits into the picture.
What is ISA-95, and what problem does it solve?
ISA-95 solves the enterprise-to-control integration problem: the software that runs the business and the software that runs the machines were built by different people, speak different languages, and run on different clocks. Your business system thinks in orders, part numbers, and weeks. Your controls think in tags, setpoints, and milliseconds. Without a shared model, connecting them means a bespoke, brittle interface at every plant, the kind that breaks the first time someone renames a line.
The standard is published by the International Society of Automation as ANSI/ISA-95 and adopted worldwide by the International Electrotechnical Commission as IEC 62264; the technical content is the same document under two names. It grew out of the Purdue Reference Model for Computer Integrated Manufacturing in the 1990s, which is why the levels are sometimes called the Purdue model. ISA-95 does not tell you which products to buy. It gives you a common language, levels, objects, and messages, so the products you already own can be connected in a way the next engineer can understand.
What are the five ISA-95 levels?
ISA-95 organizes plant systems into five functional levels, numbered 0 through 4, each with its own job and its own natural time horizon. Level 0 is the physical process itself. Levels 1 and 2 sense and control it. Level 3 manages the work of making product. Level 4 plans the business. The higher you go, the longer the time horizon and the more abstract the data.
Here is what lives at each level:
- Level 0, the physical process. The actual making of product: the mixer turning, the press stamping, the oven heating. Everything above exists to run and record this.
- Level 1, sensing and manipulation. The sensors that read the process and the actuators, drives, and PLCs that act on it, cycling in milliseconds.
- Level 2, supervisory control. The SCADA HMI, and DCS layer where operators watch and adjust the process, with alarms and setpoints on a horizon of seconds.
- Level 3, manufacturing operations management. The MES or MOM layer that dispatches work orders, tracks production, builds genealogy, and computes OEE across shifts and days.
- Level 4, business planning and logistics. The ERP layer that manages orders, inventory, purchasing, and cost on a horizon of weeks to months.
Most of what ISA-95 standardizes is the conversation between Level 4 and Level 3, what the business tells the plant to make, and what the plant reports back. Levels 0 through 2 are the province of control engineers and are largely governed by other standards; ISA-95 mainly cares that their data can be summarized upward.
What is the ISA-95 equipment hierarchy?
The equipment hierarchy is ISA-95's model for naming physical assets consistently, from the whole company down to a single machine. It runs Enterprise → Site → Area → work-center level → work-unit level. The top three are the same everywhere; the bottom two use role-based names that depend on whether you run discrete, batch, or continuous production.
Why does this matter? Because an asset name is the join key for every other system. When your MES says line 3 made 4,200 units and your ERP wants to know which cost center that was, and your CMMS logged a bearing change on the same machine, they can only agree if they share a hierarchy. A consistent equipment model is unglamorous plumbing, and it is exactly the plumbing that data silos form around when it is missing.
What does ISA-95 actually standardize? The four operations domains
At Level 3, ISA-95 describes manufacturing operations management as four parallel domains, each with the same shape: definitions, resources, schedules, performance, and capability. The four domains are production, maintenance, quality, and inventory operations. Modeling them the same way is deliberate, it means a maintenance schedule and a production schedule can be reasoned about with the same objects.
| Domain | Owns | Answers | Talks to |
|---|---|---|---|
| Production operations | Work orders, routing, genealogy, counts | What are we making, and how is it going? | ERP (orders down, results up), controls (setpoints, actuals) |
| Maintenance operations | Work requests, PMs, asset condition | What needs fixing, and when? | CMMS/EAM, condition monitoring |
| Quality operations | Tests, holds, nonconformances, dispositions | Is it good, and can we prove it? | LIMS/QMS, in-line inspection |
| Inventory operations | Material movements, lots, locations | What do we have, and where? | WMS, ERP inventory |
The standard itself comes in parts. Part 1 sets the models and terminology. Part 2 details the object attributes. Part 3 describes the activity models of manufacturing operations management. Parts 4 and 5 cover the object models and the business-to-manufacturing transactions that move between Level 4 and Level 3. You do not need to memorize the part numbers; you need to know the standard separates the vocabulary (Parts 1–2) from the activities (Part 3) from the messages (Parts 4–5).
How does ISA-95 connect MES and ERP? B2MML and the order round-trip
ISA-95 defines the message content; B2MML defines the message format. B2MML, the Business To Manufacturing Markup Language, is a set of XML schemas that implement the ISA-95 data models, maintained by MESA International and freely available. When people say two systems are "ISA-95 integrated," they usually mean the two systems exchange B2MML documents, often over OPC UA or a message bus. Here is the round-trip that plumbing enables:
- ERP releases a production request. Level 4 issues an order to make a quantity of a product by a date, as an ISA-95 production request.
- MES turns it into executable work. Level 3 expands the request into a work order with routing, materials, and the specific work centers that will run it.
- Controls execute and report actuals. Levels 1 and 2 run the process; the MES collects counts, states, and process values against the order in real time.
- MES records what happened. Genealogy, quality results, downtime reasons, and consumed materials are attached to the order as it runs.
- MES sends a production response upward. Level 3 returns an ISA-95 production performance message: what was actually made, from which lots, at what yield.
- ERP reconciles. Level 4 closes the order, relieves inventory, books cost, and updates the plan, using data it never had to retype.
The value is not the XML. The value is that the round-trip happens without a human as the integration layer. Every retyped number is a place for error and delay to enter; ISA-95 exists to remove those places.
Where does an AI operational layer fit in the ISA-95 stack?
The classic model is clean, and real plants are messy. Half your operations data lives on paper the standard never anticipated: a downtime reason scrawled on a clipboard, a changeover trick in a lead operator's head, a quality note in a binder. ISA-95 assumes each level has a system that produces structured data. The mid-market reality is that Level 3 is often a stack of spreadsheets and Level 0 paperwork.
An AI operational layer sits alongside this hierarchy rather than replacing a rung of it. It reads what the levels already produce, machine tags from Levels 1–2, order and quality records from an MES or ERP where they exist, and the paper and tribal knowledge the model leaves out, and turns them into something every role can search, cite, and act on. That is the wedge Harmony takes as a manufacturing operating system: honor the ISA-95 structure where it exists, digitize the parts of the plant it never covered, and connect the systems you already run with no rip-and-replace. Plants like CLS got real-time production visibility this way without a multi-year Level 3 project. It is also how a plant gets value from adjacent tech, predictive maintenance AI quality control and smart-factory tooling, without first perfecting every level of the pyramid.
ISA-95 by the numbers
The primary sources for the standard and its data models:
- ISA-95 defines five functional levels (0–4) and four operations domains, published as ANSI/ISA-95 by the International Society of Automation (ISA-95 committee, isa.org).
- The same content is adopted worldwide as IEC 62264 the enterprise-control system integration standard (IEC, iec.ch).
- B2MML is the freely available XML implementation of the ISA-95 models, maintained by volunteers of MESA International (MESA International, B2MML).
Read those honestly: ISA-95 is a reference model, not a product you install. It is most valuable as a shared language for a project you scope yourself, which levels you are connecting, which domain, and what data crosses the boundary.