ISA-95 levels, explained without the diagram worship

ISA-95 (IEC 62264) is the standard vocabulary for enterprise–control system integration, and its level model is the most photocopied diagram in manufacturing IT. The levels matter less as network tiers than as a way to name who owns which decisions and data.

The levels in one paragraph each

• Level 0–1: the physical process and its controllers. Sensors, actuators, PLCs, DCS controllers, robots. Time is measured in milliseconds; data is tags and I/O. Owned by operations and controls engineering.
• Level 2: supervision. SCADA, HMIs, batch servers, historians. Time is seconds to shifts; data is trends, alarms, and operator actions. Still operations-owned, increasingly IT-adjacent.
• Level 3: operations management. MES/MOM: scheduling, dispatch, genealogy, quality, OEE. Time is shifts to weeks; data is work orders, lots, and serial numbers. Jointly owned — this is where IT/OT arguments live.
• Level 4: business planning. ERP: orders, inventory, procurement, finance. Time is weeks to quarters. IT-owned, with master data (materials, routings, customers) that Level 3 must not contradict.

Level 3.5 (the DMZ, historians, integration brokers) is industry slang, not the standard — useful slang, but do not cite it in a specification.

What the standard actually standardizes

ISA-95's durable contribution is not the pyramid; it is the object models: equipment, personnel, material, and production definitions with consistent attributes and relationships, plus B2MML — XML schemas for exchanging production schedules, performance, quality, and maintenance information between Level 4 and Level 3. When your MES vendor says "ISA-95 compliant," ask which parts and which exchanges: the claim ranges from "we read the glossary" to tested B2MML interop.

In practice, greenfield MES integrations increasingly use REST/JSON or MQTT payloads shaped by ISA-95 concepts rather than literal B2MML. The standard's vocabulary (what counts as a lot, a work center, an operation) still prevents the classic failure where ERP and MES use the same words for different things.

Using it in conversation

The levels are a translation layer. "That decision belongs at Level 3" ends debates about whether the ERP or the MES owns dispatching. "Level 2 to Level 3" names the SCADA→MES handoff that needs tag-to-lot context mapping. Learn the nouns, hold the boundaries lightly, and spend your rigor on the interface definitions instead of the diagram.

References

• ISA standards: ISA-95, ISA-88, ISA/IEC 62443
• Automation World — MES and operations coverage
• OPC UA, MQTT, and Sparkplug B: how they fit together — Shopfloor