ISA-95
ISA-95 (also published as IEC 62264) is an international model for integrating enterprise systems with manufacturing operations and control. It describes equipment hierarchy, activity models, and the kinds of information that should cross the boundary between business systems and the floor without pretending one application owns every layer.
For Industry 4.0 programs, ISA-95 is still useful even when networks become more peer-to-peer. It keeps ownership honest: ERP and MES remain systems of record for many transactions, while live twins and analytics consume shared state. Modern stacks may carry that state over OPC UA, APIs, or message buses. The boundary question stays the same.
Plants that skip the model often discover the failure late: a twin project quietly tries to become the new ledger for orders and inventory, or a dashboard project cannot resolve which system owns a downtime code.
Key Components
Equipment hierarchy - Enterprise, site, area, line, cell, and unit levels that give assets a shared place in the plant model.
Activity models - Production, quality, maintenance, and inventory activities and how they relate across levels.
Information categories - What crosses the enterprise-to-control boundary (schedules, performance, capability, and definitions).
Integration boundaries - Clear ownership so interconnection does not mean rip-and-replace of every system of record.
Applications in Manufacturing and Logistics
Manufacturing teams use ISA-95 language when mapping MES to lines and cells, and when deciding which KPIs originate where. Logistics and warehouse teams use related hierarchy thinking when staging areas, docks, and movers must appear next to production state in one view. Digital twin projects use the hierarchy to attach live location and sensor feeds to the same named places the business already trusts.
Benefits and Challenges
Benefit: shared vocabulary for integration workshops and less accidental replacement of systems of record. Challenge: treating the classic pyramid as the only allowed topology, or stopping at hierarchy slides while identifiers and tag meaning stay messy on the floor.
Related Terms
MES, ERP, and WMS sit inside the enterprise and operations layers the model discusses. SCADA and PLC systems sit closer to control. Interoperability and system integration are the practical work of making those layers exchange state.
Frequently Asked Questions
Does Industry 4.0 make ISA-95 obsolete? No. Flat or event-driven transports still need ownership and hierarchy clarity. ISA-95 is often the language for those boundaries.
Is ISA-95 a protocol? No. It is an integration model. Protocols and APIs carry the messages. The model says what should be owned where.
Why does a twin project care? Because a live map that redefines orders and inventory without agreeing systems of record will fight MES and WMS forever.