ISA-95 is a vocabulary, not an architecture mandate.
ISA-95 (IEC 62264) is the standard for integrating enterprise and control systems: a functional hierarchy of manufacturing operations, an equipment model, and information models for exchanging production data between business systems and operations. In daily practice, its equipment hierarchy is the shared language plants use to name things consistently.
What practitioners actually use.
The Where
ISA-95 contributes a stable, business-recognizable location vocabulary. Most UNS topic paths borrow it: enterprise/site/area/line/cell.
Not The What
The meaning of each message — encoding, units, quality, state — comes from payload conventions like Sparkplug B and deliberate contextualization.
Not The Flow
Event-driven publish/subscribe replaces the strictly layered, request-driven data flow the level diagram is often — wrongly — read as mandating.
The standard is misused more often than misunderstood.
- Reading it as an architecture blueprint. It standardizes vocabulary and information models; data does not have to climb level by level through a chain of systems.
- Modeling the org chart or the network layout instead of the physical process.
- Over-modeling before the first use case: months perfecting object models nobody consumes yet.
- Declaring it obsolete because MQTT exists. Event transport replaces polling chains, not the need for shared names.
Where ISA-95 sits in the stack.
ISA-95 provides the naming backbone of a Unified Namespace; Sparkplug B covers the payload and session layer the hierarchy says nothing about; contextualization attaches the hierarchy path (and much more) to each value; a consistent hierarchy is one of the first things AI readiness work checks; and it is one of the support models inside the Digital Platform. When you are ready to turn the hierarchy into a governed namespace design, the Namespace Architect generates one from your site's actual organization.