The ISA-95 equipment hierarchy is the shared vocabulary that lets operations, engineering and IT agree on where a machine lives: enterprise, site, area, work center and work unit. In this explainer you will learn what each level means, how the hierarchy differs between discrete and process plants, the mistakes teams make when applying it, and how to map live, data-producing devices onto it for a unified namespace.
What ISA-95 Is
ISA-95, published internationally as IEC 62264, is a standard for integrating enterprise systems such as ERP with manufacturing operations systems such as MES and SCADA. It defines models for production, maintenance, quality and inventory activities, and the information exchanged between business and plant floor.
Two parts of ISA-95 are easy to confuse:
- The functional hierarchy describes levels of activity, from Level 0 (the physical process) through Level 1 (sensing and manipulating), Level 2 (monitoring and control), Level 3 (manufacturing operations management) to Level 4 (business planning and logistics). It answers "what kind of work happens here?"
- The role-based equipment hierarchy describes physical and logical assets: enterprise, site, area, work centers and work units. It answers "where is this asset in the organisation?"
This article is about the second. When people say "an ISA-95 topic structure" for MQTT, they almost always mean the equipment hierarchy. The functional levels relate more closely to the Purdue model, which our Purdue model vs ISA-95 comparison untangles.
The Levels of the ISA-95 Equipment Hierarchy
| Level | Definition | Discrete example | Process example |
|---|---|---|---|
| Enterprise | The company, the top of the hierarchy | Acme Manufacturing | Acme Beverages |
| Site | A physical, geographical location | Dallas plant | Izmir brewery |
| Area | A grouping within a site, often by function or product | Machining, Assembly | Brewing, Packaging, Utilities |
| Work center | An equipment grouping that performs a production step | Production line, work cell | Process cell, production unit |
| Work unit | The lowest level ISA-95 models for scheduling | Station, machine | Unit, such as a vessel or reactor |
ISA-95 distinguishes several types of work center, depending on the style of manufacturing:
- Production line for discrete, repetitive manufacturing such as bottling or car assembly.
- Work cell for discrete manufacturing where a group of machines works flexibly, such as a machining cell.
- Process cell for batch manufacturing, following ISA-88 terminology.
- Production unit for continuous processes such as a distillation column or paper machine.
- Storage zone for areas that hold material, such as a tank farm or warehouse.
Each work center type has a matching work unit: stations or machines within a line or cell, units within a process cell, and storage units within a storage zone.
Below the Work Unit
ISA-95 stops at the work unit because that is as far as business and operations systems need to schedule. In practice you often need to go deeper. ISA-88, the batch control standard, continues with equipment modules and control modules, for example a heater module within a vessel and a temperature transmitter within the heater. Many plants extend the hierarchy this way when they need sensor-level addressing.
Worked Example: A Bottling Plant
To make the levels concrete, here is a single plant described through the hierarchy:
Enterprise acme
Site dallas
Area packaging
Work center line-02 (production line)
Work units depalletizer, rinser, filler, capper, labeler, case-packer
Area utilities
Work center compressed-air (production unit)
Work units comp-01, comp-02, dryer-01
Area warehouse
Work center finished-goods (storage zone)
Work units rack-a, rack-b
A filler on Line 2 now has an unambiguous address: acme/dallas/packaging/line-02/filler. Any system, from the historian to the maintenance app, can use that address as its key.
Common Mistakes When Applying the Hierarchy
- Mixing organisational and physical structure. Departments and cost centres change more often than buildings and lines. Base the hierarchy on physical equipment and keep organisational data as attributes.
- Inconsistent depth. If some machines sit under a line and others directly under an area, wildcard queries break. Introduce a placeholder work center such as
standalonerather than skipping a level. - Encoding attributes in names.
filler-krones-2019mixes identity with vendor and year. Keep names short and put attributes in metadata. - Ignoring utilities and storage. Compressors, boilers and tanks matter for energy and quality analysis. Give them areas and work centers too.
- Designing the whole enterprise at once. Model one site and one area deeply, prove it with real data, then extend the pattern.
- No owner. Someone must approve new nodes, or the hierarchy drifts as each project adds its own branches.
From Hierarchy to Live Data
The equipment hierarchy becomes really useful when it is the structure of your real-time data, not just a diagram in an MES. That is the core idea of a unified namespace: devices publish into MQTT topics that follow the hierarchy, so the topic path is the asset address. Our ISA-95 MQTT topics guide shows exactly how to encode the levels into topics, and UNS topic structure gives complete trees for discrete and process plants.
You can try this in a minute against the free public MQTT broker. The public area is readable by everyone and allows 8 topic levels, so use a unique prefix and simulated values only:
mosquitto_pub -h broker.connectmq.com -p 1883 -i isa95-demo-pub-m3 -r \
-t "connectmq/demo/m3x8/dallas/packaging/line-02/filler/state" -m "running"
mosquitto_sub -h broker.connectmq.com -p 1883 -i isa95-demo-sub-m3 \
-t "connectmq/demo/m3x8/dallas/packaging/#" -v
Here the enterprise level is replaced by the demo prefix to stay within the public broker's level limit; on a private broker you would start the topic with the enterprise name.
Seeing the Hierarchy in ConnectMQ
ConnectMQ detects ISA-95 and unified namespace topics, and its portal includes a devices view organised by ISA-95 levels. As devices publish, they appear under their enterprise, site, area, line and equipment, which makes it easy to spot a gateway that published under the wrong area or a machine whose name does not match the standard. For Sparkplug B edge nodes, ConnectMQ decodes the payloads and republishes them into ISA-95 topics, for example from spBv1.0/factory1/DDATA/line1/cnc1 to connectmq/factory1/production/line1/cnc1/telemetry, so Sparkplug devices land in the same hierarchy as everything else.
Using the Hierarchy Beyond Topics
The same addresses pay off across systems:
- Historians and data lakes can store site, area, line and equipment as columns or tags, enabling queries like "energy per line per shift" without lookup tables.
- Alerting can be scoped by branch, so the utilities team only receives utilities alerts.
- Digital twins can mirror the hierarchy one to one; see ISA-95 and digital twins.
- Access design can follow branches, with credentials issued per gateway or application covering the area it serves.
For where this fits in a full plant architecture, our industrial IoT MQTT guide covers gateways, protocols and brokers end to end.
Map Your ISA-95 Hierarchy With ConnectMQ
The fastest way to validate a hierarchy is to publish real data into it and look. ConnectMQ is a cloud MQTT broker with an ISA-95 devices view, ISA-95 topic detection and Sparkplug B republishing built into the portal. Create a broker on the free Serverless plan at app.connectmq.com, no credit card required, and watch your devices fall into place level by level. If you are new to brokers, start with what an MQTT broker does.
Frequently Asked Questions
What are the levels of the ISA-95 equipment hierarchy?
Enterprise, site, area, work center and work unit. Work centers include production lines, work cells, process cells, production units and storage zones, each with matching work units.
Is a line the same as a cell in ISA-95?
Both are work centers. A production line suits repetitive discrete production, while a work cell suits flexible groupings of machines. Use whichever matches how the equipment actually runs.
How deep should the hierarchy go?
ISA-95 stops at the work unit. Extend below it with ISA-88 style equipment and control modules only when you need sensor-level addressing.
Is ISA-95 the same as the Purdue model?
No. ISA-95 models enterprise-to-control integration and equipment roles, while the Purdue model is a network reference architecture. They share level numbering, which causes the confusion.
