ISA-95: The Standard for MES Architectures and ERP Integration

Modern manufacturing has to bridge two worlds that speak different languages: business planning (orders, dates, costs) and shop-floor operations (machines, sensors, real-time control). Without a shared structure, the result is data silos, brittle point-to-point interfaces, and integration projects that never quite scale.

The international standard ISA-95 (IEC 62264) solves this. It gives manufacturers a common, vendor-independent language for connecting everything from a sensor to the ERP — clearly defined, future-proof, and proven across thousands of plants worldwide. This guide explains the level model, the functional domains, the object and data models, the B2MML/OPC UA stack, the parts of the standard, and how a cloud MES implements it in practice.

Contents

• What is ISA-95? (in plain English)
• The ISA-95 levels: the automation pyramid (Level 0–4)
• How ISA-95 maps PLC, SCADA, MES and ERP
• The four functional domains of ISA-95
• The ISA-95 object & equipment hierarchy models
• The four information categories exchanged between ERP and MES
• B2MML and OPC UA: the technical stack
• The parts of the standard (IEC 62264 Part 1–6)
• ISA-95 in practice: real-world examples
• ISA-95 vs VDI 5600
• ISA-95 vs ISA-88
• Best practices for ISA-95 implementation
• How a cloud MES implements ISA-95
• What ISA-95 means for your MES decision
• Related articles
• Frequently asked questions

What is ISA-95? (in plain English)

ISA-95 is the international standard for the exchange of information between ERP systems and Manufacturing Execution Systems (MES). It defines a five-level model of manufacturing IT (Level 0–4), a set of standardised data objects, and four operational domains. ISA-95 is vendor-independent and forms the architectural backbone of nearly every modern MES implementation worldwide.

Put simply: ISA-95 is the map that tells every system in a factory where it sits, what it is responsible for, and how it should talk to the layer above and below it. The business layer decides what to produce; the control layer decides how the machines run; ISA-95 defines the clean handshake in between so neither side has to know the other's internal details.

The standard was developed by the International Society of Automation (ISA) as ANSI/ISA-95, and is published internationally — technically identical — as IEC 62264. So when you see "ISA-95", "ANSI/ISA-95" or "IEC 62264", they refer to the same family of standards. Its level structure derives from the well-known Purdue Enterprise Reference Architecture (PERA).

ISA-95 specifies three things:

• Which functions exist in manufacturing IT and where they belong.
• Which data objects those functions exchange (schedules, performance, material, equipment, personnel).
• How that exchange is structured and named, so different vendors interpret it the same way.

The payoff is interoperability: a scalable, vendor-neutral foundation for smart manufacturing and Industry 4.0.

The ISA-95 levels: the automation pyramid (Level 0–4)

The ISA-95 level model — often drawn as the "automation pyramid" — organises manufacturing IT into five layers. Level 0 is the physical process, Levels 1–2 cover sensing and control, Level 3 is the MES/operations layer, and Level 4 is the enterprise/ERP layer. Level 3 is the critical bridge between operational technology (OT) and information technology (IT).

Each level also operates on a different time horizon. Level 4 plans in months, weeks and days; Level 3 works in days, shifts, hours and minutes; Levels 0–2 react in seconds and milliseconds. That separation of time scales is exactly why the layers must not be merged — and why ISA-95 keeps them distinct.

Level 3 is the bridge between OT and IT. It consolidates production data, dispatches and tracks orders, and feeds results back up — while keeping shop-floor systems stable and autonomous. This layered approach prevents overlap between planning logic (ERP) and operational control (MES), and ensures consistent data flow across the enterprise. The boundary between Level 3 and Level 4 is the interface ISA-95 describes in the most detail — including the data objects, message formats and transaction types that flow between MES and ERP.

How ISA-95 maps PLC, SCADA, MES and ERP

Read the pyramid bottom-up and it becomes a simple chain of responsibility:

• Sensors & PLCs (Level 1–2) run the machine in real time — they read signals and execute control logic in milliseconds.
• SCADA (Level 2) supervises and visualises those PLCs across a line or area, and raises alarms.
• MES (Level 3) turns machine reality into operations: it schedules and dispatches orders, captures production and quality data, calculates OEE, and manages material and maintenance.
• ERP (Level 4) runs the business: it owns orders, materials planning, costing and delivery.

ISA-95 defines the two key handshakes in that chain. OPC UA typically carries the Level-2 → Level-3 conversation (machine data up, set-ups down). B2MML typically carries the Level-3 → Level-4 conversation (orders down, performance up). Get those two interfaces right and the whole stack interoperates — regardless of who built each component.

The four functional domains of ISA-95

ISA-95 divides Level-3 operations into four domains, each modelled with the same generic activity pattern (scheduling, dispatching, execution, data collection, tracking, analysis, definition and resource management). The same four domains reappear in MOM (Manufacturing Operations Management) and underpin the VDI 5600 MES functions:

1. Production Operations Management — order dispatching, sequencing, execution and progress tracking.
2. Quality Operations Management — inspection planning, results collection, SPC, traceability and deviation handling.
3. Maintenance Operations Management — work orders, preventive plans, downtime analysis and availability.
4. Inventory Operations Management — material flow, work-in-progress, locations and stock levels.

Because every Level-3 function maps to one of these domains, the four domains describe the core scope of any MES — and give you a clean checklist when comparing platforms.

The ISA-95 object & equipment hierarchy models

ISA-95 doesn't just describe layers — it defines objects. Part 2 of the standard specifies four common resource models that every compliant system shares: Personnel, Role-Based Equipment, Physical Asset and Material. These are the nouns of manufacturing; standardising them is what lets two systems agree on what "an order", "a machine" or "a batch of material" actually means.

Equipment is organised into a role-based equipment hierarchy — a nested tree that lets you address anything from a whole company down to a single machine:

This hierarchy is what makes ISA-95 scalable: the same model addresses one machine on a pilot line or 15,000 machines across a global enterprise — only the depth of the tree changes.

The four information categories exchanged between ERP and MES

At the Level 3 ↔ Level 4 interface, ISA-95 groups everything into four categories of information. Two flow downward (what to make) and two flow upward (what's possible and what happened). Each maps directly to a B2MML schema:

This closed loop — schedule down, performance up — is the heart of ERP-MES integration. It's also why "did we make what we were asked to make?" becomes a question of standardised data rather than a custom report per plant.

B2MML and OPC UA: the technical stack

ISA-95 is conceptual; B2MML and OPC UA make it real. B2MML implements the ISA-95 data model for ERP↔MES, while OPC UA carries real-time machine data between the shop floor and the operations layer. Together they form the full communication stack of an ISA-95 architecture.

B2MML (Business-to-Manufacturing Markup Language)

B2MML is the XML implementation of ISA-95, maintained by MESA International (it originated with the World Batch Forum). It is a set of XML Schemas (XSD) that turn the ISA-95 objects — product definition, schedule, performance, material, equipment, personnel — into concrete, machine-readable messages. Any ERP or MES that supports B2MML understands the same structures, which is what removes custom point-to-point mapping.

ProductionSchedule vs ProductionPerformance vs ProductionRequest: a ProductionSchedule is the set of orders ERP sends down ("make 500 of part X by Friday"); a ProductionRequest is a single request inside that schedule; a ProductionPerformance is what the MES sends back up ("480 good, 12 scrap, 3.2t steel consumed"). Schedule and request are intent; performance is reality.

OPC UA (Open Platform Communications Unified Architecture)

OPC UA (standardised as IEC 62541) is the de-facto standard for secure OT/IT communication. It transmits real-time machine data, metadata and events through a unified, semantic information model — so a value isn't just "42", it's a typed "temperature" or "alarm". Combined with ISA-95, OPC UA delivers true semantic interoperability from sensor to enterprise dashboard, usually via an IoT/edge gateway.

The two now connect directly: the OPC Foundation and MESA jointly published the OPC UA ISA-95 Common Object Model companion specification, which represents ISA-95's equipment, personnel, material and physical-asset objects natively in OPC UA. In other words, the same ISA-95 nouns can now travel over OPC UA in real time — closing the gap between the B2MML (batch/transactional) and OPC UA (real-time) worlds.

The parts of the standard (IEC 62264 Part 1–6)

ISA-95 / IEC 62264 is published in several parts, each addressing a different layer of the integration problem. You rarely need all of them, but knowing the map helps when a vendor cites "Part 2 compliance" or "Part 5 transactions":

ISA-95 in practice: real-world examples

Manufacturers use ISA-95 as the blueprint for scalable, maintainable IT/OT architectures. Typical applications include:

• MES rollouts across heterogeneous plants — uniform function mapping prevents duplicate structures.
• ERP-MES integration — orders, bills of materials and feedback travel through standardised objects.
• Global reporting — harmonised KPIs across business units and suppliers.
• Legacy modernisation — existing SCADA systems connect via OPC-UA gateways to an ISA-95-compliant layer.

Example — Meleghy Automotive (6 plants, 4 countries): the automotive supplier connects SAP R/3 to SYMESTIC through a bidirectional ABAP-IDoc interface. Production orders are dispatched automatically to lines, machine cycles are mapped to manufacturing orders, and results flow back into ERP in a standardised format — across 6 plants in Germany, Spain, the Czech Republic and Hungary, with mixed controller generations in press lines, welding cells and assembly areas. Within six months the rollout delivered roughly −10% downtime, +7% output and +5% availability — a textbook ISA-95 setup that would not scale without standardised data objects and clean level separation.

Customer Story Automotive

How Meleghy Automotive connects its plants with a single MES platform

• Standardized MES platform across all sites
• Real-time transparency in body production
• OEE & loss reasons captured automatically
• Scales from pilot to series production

Read case study Approx. 4 min read · free

Rollout Multi-site MES

Case Study

Example — Carcoustics: within six months, Carcoustics scaled to 500+ machines across 7 plants on 3 continents. OT integration runs through IXON IoT devices and MQTT into Microsoft Azure, complemented by a bidirectional SAP R/3 connection. The Level-3 functions (order control, performance analysis, set-up support) run entirely in the cloud, while Level-2 data (PLC signals, machine alarms) is delivered via standardised gateways — ISA-95 level separation in its purest form.

See more in SYMESTIC case studies.

ISA-95 vs VDI 5600

ISA-95 and VDI 5600 are complementary, not competing. ISA-95 describes the architecture — levels, data flows and interface objects. VDI 5600 defines the concrete MES functions and processes inside that architecture. ISA-95 answers "where does the data flow?"; VDI 5600 answers "what does the MES do with the data?"

Together they form the foundation of modern Manufacturing Operations Management (MOM). Industry 4.0 extends this with semantic standards such as the Asset Administration Shell (AAS) and Digital Twin concepts — the next evolution of the ISA-95 idea.

ISA-95 vs ISA-88

ISA-95 and ISA-88 sit on different layers and solve different problems. ISA-95 standardises the vertical integration between ERP (Level 4) and MES (Level 3). ISA-88 (Batch Control) standardises the procedural control of batch processes on Levels 1–2 — how a recipe is structured and executed. In short, ISA-95 picks up where ISA-88 leaves off, and the two are designed to coexist: ISA-88 organises the batch on the floor, ISA-95 reports it to the business.

Best practices for ISA-95 implementation

1. Start with information modelling. Define the data objects and levels before selecting systems — top-down, not tool-first.
2. Use standardised formats. Combine B2MML and OPC UA to avoid one-off custom integrations.
3. Maintain semantic consistency. Use identical naming and IDs for the same object across ERP, MES and SCADA.
4. Establish governance. Keep ISA-95 models under revision control and aligned with business goals — they are living documents.
5. Scale iteratively. Begin with a pilot line, then extend domain by domain and site by site — don't try to implement all four domains at once.

How a cloud MES implements ISA-95

Cloud-native MES platforms keep the ISA-95 level separation intact — only the infrastructure moves. Level-2 data (machine cycles, alarms, process parameters) is captured via standardised OPC-UA and IoT gateways. Level-3 functions (order control, detailed scheduling, OEE analysis, quality capture) run in the cloud platform. Level-4 integration (SAP, Infor, Microsoft Dynamics) happens over REST API and standard connectors. The ISA-95 logic is identical — the servers simply move from a local rack into certified cloud data centres.

Solutions such as SYMESTIC implement all four ISA-95 functional domains — production, quality, maintenance and inventory — on a single platform, with standardised gateways for fast machine connectivity (including legacy equipment) and a REST API for bidirectional ERP integration. The result: faster deployments, standard interfaces, and an architecture that scales from one line to a global rollout.

What ISA-95 means for your MES decision

ISA-95 is far more than a technical standard — it is the organising framework of digital manufacturing, the map on which ERP, MES and automation agree. Companies that build their architecture consistently on ISA-95 gain real interoperability, shorter integration times and long-term investment protection.

The practical takeaway when you evaluate an MES: check whether the vendor covers all four ISA-95 functional domains, whether the level separation is implemented cleanly, and whether ERP integration uses standard objects rather than bespoke mapping. The MES software comparison and MES vs ERP guides help you assess this systematically.

Related articles

MES cluster

• MES: Definition, Functions & Benefits 2026 — pillar article
• MES vs MOM: the ISA-95 framework & 4 domains
• MES functions per VDI 5600 — all 8 explained
• MES vs ERP: differences & integration
• MES software: vendors, features & costs compared
• MES architecture: on-prem vs cloud vs hybrid

Technology & standards

• OPC UA: architecture, security & MES connectivity
• IoT gateway: machine connectivity in practice
• ERP system: definition & scope
• OT vs IT: convergence patterns that work

Frequently asked questions about ISA-95

What is ISA-95?

ISA-95 (internationally IEC 62264) is the standard for exchanging information between ERP and Manufacturing Execution Systems (MES). It defines a five-level model (Level 0–4), standardised data objects, and four operational domains. It is vendor-independent and forms the architectural foundation of nearly every modern MES.

What are the ISA-95 levels (the automation pyramid)?

The ISA-95 level model structures manufacturing IT into five levels: Level 0 (physical process), Level 1 (sensors/actuators), Level 2 (PLC, SCADA — process control), Level 3 (MES/operations for scheduling, quality and maintenance) and Level 4 (ERP/enterprise for orders, planning and logistics). Level 3 is the central bridge between OT and IT.

How does ISA-95 map PLC, SCADA, MES and ERP?

PLCs and sensors (Level 1–2) run machines in real time; SCADA (Level 2) supervises and visualises them; the MES (Level 3) schedules orders and captures production/quality data; ERP (Level 4) runs the business. ISA-95 defines the two key handshakes: OPC UA for Level 2→3 and B2MML for Level 3→4.

What is the role of B2MML and OPC UA in ISA-95?

B2MML is the XML implementation of the ISA-95 data model for standardised ERP↔MES exchange. OPC UA (IEC 62541) is the de-facto standard for OT/IT connectivity, transmitting machine data in real time from PLC to operations layer. Together they form the complete ISA-95 communication stack, now also bridged by the OPC UA ISA-95 Common Object Model companion specification.

How do ISA-95 and VDI 5600 complement each other?

ISA-95 describes the architecture — levels, data flows and interface objects. VDI 5600 defines the concrete MES functions and processes (8 task areas). ISA-95 answers "where does the data flow?", VDI 5600 answers "what does the MES do with it?" Together they form the methodical foundation of Manufacturing Operations Management.

What is the difference between ISA-95 and ISA-88?

ISA-95 standardises the vertical integration between ERP (Level 4) and MES (Level 3). ISA-88 (Batch Control) standardises the procedural control of batch processes on Levels 1–2. ISA-95 picks up where ISA-88 leaves off, and the two are designed to coexist.

Is ISA-95 only relevant for large enterprises?

No. ISA-95 is an architectural model, not an implementation mandate. Even a mid-sized manufacturer with 30 machines benefits: clean level separation prevents MES functions being rebuilt inside the ERP (or vice versa), standardised objects ease ERP integration, and the model scales from a pilot line to a multi-site rollout.

How do ISA-95 and cloud MES fit together?

Cloud-native MES platforms implement the ISA-95 level separation by transporting Level-2 data (machine signals) through standardised IoT gateways into the cloud, providing Level-3 functions as a SaaS service, and integrating ERP (Level 4) over REST API. The ISA-95 logic stays identical — only the infrastructure changes.

What is the difference between a ProductionSchedule and a ProductionPerformance message?

A ProductionSchedule is what ERP sends down to the MES — the orders to make ("500 of part X by Friday"). A ProductionPerformance is what the MES sends back up — what was actually produced ("480 good, 12 scrap, material consumed"). Schedule is intent; performance is reality. Both are standardised B2MML schemas.