IndustryHub
LEARN / STANDARDS / ISA

ISA-95

ISA-95

Enterprise-Control System Integration

ISA-95 (also IEC 62264) defines the standard interface between enterprise (ERP, business systems) and manufacturing operations (MES, DCS, batch). It is the backbone of every digital manufacturing initiative, smart factory roadmap, and Industry 4.0 architecture.

Document structure

ISA-95.01 / IEC 62264-1

Models and terminology

The hierarchical Levels 0-4 of manufacturing operations, role-based equipment hierarchy, four categories of information exchanged (Product Definition, Production Capability, Production Schedule, Production Performance).

ISA-95.02 / IEC 62264-2

Object model attributes

Detailed object model for personnel, equipment, material, process segments. Data dictionary for exchange.

ISA-95.03 / IEC 62264-3

Activity models of manufacturing operations management

The 4 production activities : Production, Maintenance, Quality, Inventory. Each modeled as a workflow of MOM (Manufacturing Operations Management) activities.

ISA-95.04 / IEC 62264-4

Object models for MOM

Inside MOM Level 3 : activity-level object models for each of the 4 activity categories.

ISA-95.05 / IEC 62264-5

Business-to-manufacturing transactions

Transactional pattern (Get, Show, Process, Cancel, Change, Sync). B2MML XML schemas implementing these.

ISA-95.06 / IEC 62264-6

Messaging service model

Service-oriented architecture for B2M messaging.

Key concepts

The 5 Levels
Level 0 (physical process), Level 1 (sensing/actuation — instrumentation), Level 2 (monitoring/control — DCS/PLC), Level 3 (manufacturing operations — MES/MOM), Level 4 (business planning — ERP). The ISA-95 cake.
Manufacturing Operations Management(MOM)
Level 3 of the hierarchy. Activities : production scheduling, dispatch, execution, data collection, performance analysis, quality, maintenance, inventory. Implemented by MES systems.
Production Schedule
Information flow from ERP (Level 4) to MOM (Level 3) specifying what to produce, when, and with what material allocation. ISA-95 defines its structure.
Production Performance
Information flow from MOM (Level 3) back to ERP (Level 4) — actual production results, yield, downtime, OEE inputs.
Equipment hierarchy
Enterprise > Site > Area > Production Line / Cell > Work Cell / Unit > Equipment Module. Compatible with ISA-88 physical model. Different roles per industry (assembly Line for discrete vs Process Cell for batch).
B2MML
Business to Manufacturing Markup Language. XML implementation of ISA-95 (and ISA-88) data exchange. Maintained by OAGi. Used as the default by most MES↔ERP integrations.

Notes & guidance

The “iceberg” of manufacturing

Walk into a factory. The visible part is the equipment — robots, conveyors, reactors, packaging lines. That’s roughly Level 0-1-2 of the ISA-95 hierarchy: physical process, instrumentation, basic control. Most factory tours stop there.

The much bigger, invisible part is everything that decides what the factory does, when, with what materials, in what quantity, and how it reports back to the business. That’s Levels 3 and 4 : MES (Manufacturing Execution System) and ERP (Enterprise Resource Planning). The orchestration layer.

ISA-95 is the standard that lets these layers talk to each other despite being made by different vendors over decades.

The 5 levels in plain words

┌────────────────────────────────────────────────────────────────┐
│ Level 4 :  Business Planning & Logistics                       │
│           (ERP : SAP, Oracle, Microsoft Dynamics)              │
│           — "Make 10,000 vaccine doses by Friday"              │
└──────────────────────────────┬─────────────────────────────────┘
                               │  ◀── ISA-95 boundary ──▶
                               │  (Production Schedule, Performance, ...)
┌──────────────────────────────┴─────────────────────────────────┐
│ Level 3 :  Manufacturing Operations Management (MOM)           │
│           (MES : Aveva, Siemens Opcenter, GE Proficy, Rockwell)│
│           — "On Monday at 06:00, start Batch B1234 on Reactor R3"│
└──────────────────────────────┬─────────────────────────────────┘
                               │  ◀── ISA-95 / OPC UA ──▶
┌──────────────────────────────┴─────────────────────────────────┐
│ Level 2 :  Supervisory Control (HMI, SCADA)                    │
│           — Real-time operator view + setpoints                │
└──────────────────────────────┬─────────────────────────────────┘
┌──────────────────────────────┴─────────────────────────────────┐
│ Level 1 :  Basic Control (PLC, DCS, Safety PLC)                │
│           — Control loops, interlocks, sequences                │
└──────────────────────────────┬─────────────────────────────────┘
┌──────────────────────────────┴─────────────────────────────────┐
│ Level 0 :  Physical Process                                    │
│           Sensors, actuators, reactors, conveyors              │
└────────────────────────────────────────────────────────────────┘

The vertical integration at the Level 3 ↔ Level 4 boundary is where ISA-95 lives. It’s the contract that ERPs and MES systems honor when exchanging :

  1. Product Definition : recipes, BOMs, formulas (links to ISA-88)
  2. Production Capability : what each piece of equipment can do, current availability
  3. Production Schedule : the order list ERP sends down to MOM
  4. Production Performance : the actuals MOM sends back to ERP

Why MES exists at all (Level 3)

ERP runs on transactional time : daily, hourly. Production lives on operational time : seconds, minutes. The gap is huge.

ERP knows : “We need to ship 1000 units of SKU-42 by Friday.” ERP doesn’t know : “Right now machine M3 just stopped due to a sensor fault, M1 has 240 units staged but the batch on M1 needs to finish before M3 can be reassigned.”

That coordination is Level 3 work — done by humans + MES + Schedulers + Quality systems. ISA-95 formalizes who-talks-to-whom-with-what-data so that the upper levels (ERP) don’t pretend to manage real-time logistics and the lower levels (DCS) don’t pretend to manage business outcomes.

ISA-95 vs Asset Administration Shell (AAS)

The German Plattform Industrie 4.0 has developed the Asset Administration Shell (AAS) as the digital twin standard for Industry 4.0. AAS sits at a similar interface but with a more modern, semantic data model (RDF, ontologies). It’s complementary, not a replacement.

In 2024-2026, ISA-95 v3 work explicitly aligns the B2MML / ISA-95 data structures with AAS so that the two can coexist without translation pain. Practical effect : modern MES implementations support BOTH ISA-95 / B2MML for legacy integration AND AAS submodels for forward-looking digital twin features.

The “Industry 4.0 vendor checklist” with ISA-95 in mind

When evaluating a smart manufacturing initiative or vendor pitch, ISA-95 is a reasonable benchmark :

  • Does the proposed solution respect the level hierarchy or does it try to bypass MES and connect ERP directly to PLCs? (Red flag : tight coupling at wrong levels.)
  • Does it speak B2MML or a proprietary equivalent ? (Lock-in risk.)
  • Does it model the 4 activity categories (Production, Maintenance, Quality, Inventory) explicitly ? (If only Production, it’s incomplete.)
  • Does it handle historical data at Level 3 properly (genealogy, batch record reconstruction) ?

These questions reveal whether a vendor truly understands manufacturing operations or just rebadges a generic data lake.

Applicable industries

  • Pharmaceutical (GxP / Track & Trace)
  • Food & Beverage (Allergen, Lot tracking)
  • Automotive (Just-in-time, Tier-1 supplier integration)
  • Electronics manufacturing (high-mix low-volume)
  • Aerospace (As-built configuration management)
  • Process industries (continuous + batch)

References & further reading