The five-level pyramid has become a slogan. The standard is more precise, and far more useful, than the diagram people remember.
Everyone knows the ISA-95 pyramid: five tiers, from the shop floor to the ERP. The picture is accurate, but it represents only a fraction of what the standard offers. Three quarters of its content is about something else: object models and exchange flows.
What the standard actually describes
ISA-95 defines a shared vocabulary for talking about production: what counts as a resource, personnel, equipment, material, capability, product definition. It then describes the messages that travel between level 4 and level 3: production schedule, production performance, product definition, available capability.
That is the part with project value. When an interface specification uses the standard's objects, the two teams — business and production — stop talking past each other.
Three common misreadings
- "The pyramid imposes a rigid stack." It does not: it describes responsibilities, not network topology. A data historian can perfectly well read level 2 directly.
- "ISA-95 forbids connecting the ERP to controllers." The standard forbids nothing. It simply explains why that shortcut is expensive to maintain.
- "Level 3 is the MES." Level 3 is a set of functions; MES is only one possible carrier, alongside LIMS, CMMS or WMS.
How we use it
We treat ISA-95 as a specification grammar. Every interface is described with the standard's objects, then translated into the chosen technical format. The document stays readable by a production manager, which means it can be approved by the right people rather than by IT alone.
The benefit becomes measurable when you change vendor: an interface specified in ISA-95 terms is rebuilt in a few weeks, where an interface described in proprietary terms has to be rediscovered from scratch.
Back to the blog