4 Surprising Truths About ISA-95: The Unseen Framework Running Modern Manufacturing

Part 1 of 5 in our Edge to Enterprise series. Before any system can share plant data, it needs a common language. This post is about that language; the rest of the series builds on it, from the edge (CATIM Edge IPC) to the enterprise (i3X).

In a modern factory, the corporate office and the plant floor are worlds apart. Enterprise Resource Planning (ERP) systems speak the language of supply chains and logistics, while shop-floor control systems—the PLCs, sensors, and robots—speak in a staccato of sub-second signals and automated commands. This communication gap creates a digital Tower of Babel, leading to inefficiency, errors, and missed opportunities.

Enter ISA-95. It is not just another technical standard; it is the essential “universal translator” that brings order to this chaos. Think of it as the Rosetta Stone for manufacturing, creating a common language that allows business and production systems to communicate seamlessly. While ISA-95 is a foundational concept for Industry 4.0, it is widely misunderstood. This article will reveal four of the most surprising and impactful truths about the unseen framework running modern manufacturing.

1. It’s a blueprint for communication, not a piece of software

The most common misconception about ISA-95 is that it is a system you can buy or install. It’s not. It is a conceptual framework—a set of models and terminology designed to create a common language for integration.

ISA-95 provides a standardised vocabulary and set of models so that different systems can understand each other. This makes it immune to most technological upgrades, as its purpose is to define what should be communicated, not how that communication is technically implemented. This stability makes adopting ISA-95 a long-term strategic investment that de-risks future technology choices. Its entire purpose is to define the ‘nouns’ of manufacturing (like equipment, materials, and personnel) and the ‘verbs’ (the information exchanged about them) so that every system is speaking the same language.

The International Society of Automation (ISA) summarises this core purpose:

The objectives of ISA-95 are to provide consistent terminology that is a foundation for supplier and manufacturer communications, provide consistent information models, and to provide consistent operations models…

Because ISA-95 is a flexible blueprint and not a rigid program, it can be applied to all types of manufacturing, including batch processes, continuous processes, and repetitive (discrete) manufacturing.

2. It creates a GPS for your factory’s data

In many plants, operational data is stored in complex relational databases, leaving OT engineers, who think in terms of production lines and work cells, lost in a maze of tables and columns they can’t navigate. ISA-95 solves this by providing a logical, human-understandable structure for organising all data within a manufacturing enterprise.

Think of it as a logical address for every single data point in your plant.

Instead of relying on database tables, ISA-95 Part 2 provides a “semantic hierarchy” that mirrors the physical layout of the factory. This structure organises information in a way that anyone familiar with the plant can intuitively understand. The hierarchy typically follows this pattern:

This hierarchy is adaptable; the level below ‘Area’ might be a ‘Production Line’ in discrete manufacturing, a ‘Process Cell’ for batch processes, or a ‘Production Unit’ in a continuous process, making the model universally applicable. This structure, often implemented as a Unified Namespace (UNS), allows an OT engineer to easily find a specific sensor tag by navigating from the enterprise level down to the exact machine, without needing to understand complex database schemas. This simple but powerful concept bridges a critical gap between the IT and OT worlds.

3. It covers the entire operation, not just the production line

Another common myth is that ISA-95 is only concerned with production or manufacturing execution. In reality, the standard defines the entire scope of Manufacturing Operations Management (MOM), a collection of critical functions that extend far beyond simply making products.

These MOM systems, which operate at Level 3 of the ISA-95 model, encompass a wide variety of activities necessary to run a modern plant. While production is a key component, ISA-95 also provides a framework for managing essential support functions, including:

• Quality control
• Maintenance management
• Personnel management
• Document management
• Product traceability and genealogy
• Resource management
• Flow of products and batches
• Performance analysis

This comprehensive scope is why ISA-95 provides a common framework for integrating a diverse set of systems, such as Manufacturing Execution Systems (MES), Laboratory Information Management Systems (LIMS), Warehouse Management Systems (WMS), and Computerized Maintenance Management Systems (CMMS). It ensures that all aspects of the manufacturing operation can share information coherently.

4. It organises time as much as it organises technology

Perhaps the most profound insight ISA-95 offers is its understanding of time. The standard’s five-level activity model acts like a layered sandwich, separating different business and control functions not just by their role, but by the timescale on which they operate.

The key levels are defined by their primary function and operating timeframe:

• Level 4: Business Planning & Logistics (ERP Systems) – Decides what to produce and when, establishing the basic plant schedule, determining inventory levels, and managing material use.
• Level 3: Manufacturing Operations Management (MES/MOM Systems) – Manages the workflow to produce it, dispatching work, maintaining records, and optimising the production process.
• Level 2: Monitoring & Control (PLCs/DCS) – Carries out the real-time control, performing supervisory and automated control of the physical process.
• Levels 1 & 0: Sensing & Physical Process – The actual sensors, valves, and machines on the floor.

You may know this layering as the Purdue model, the reference architecture that ISA-95’s levels grew from. Purdue added a strict rule: each level talks only to the level next to it. That kept plants stable, but it also turned every new data request into a chain of hand-offs from the machine up to the ERP. ISA-95 keeps the vocabulary and the levels; as we show in The End of API Chaos, modern architectures keep that meaning without forcing data to climb the levels one hand-off at a time.

The most counter-intuitive truth is that each level defines “real-time” differently. This temporal separation is critical for operational stability:

• Level 2 operates in sub-seconds.
• Level 3 operates in a timeframe of seconds, minutes, hours, and shifts.
• Level 4 operates in a timeframe of days, weeks, and months.

This separation is crucial: you cannot manage a global supply chain with millisecond-level data, and you cannot control a physical process with a monthly business plan. ISA-95 provides the structure to ensure the right information is used at the right level and at the right time, preventing operational chaos.

ISA-95 and the Unified Namespace

A Unified Namespace (UNS) is a single, event-driven hub, typically an MQTT broker, where every system publishes its current state and every application subscribes to what it needs. It replaces the web of point-to-point connections with one place to look. But a UNS is only as useful as its structure, and that structure is where ISA-95 comes in.

The ISA-95 equipment hierarchy maps directly onto the UNS topic tree. Each level becomes one segment of the topic path, so every data point has a predictable address:

Put together, the filler's running state lives at acme/brisbane/packaging/line1/filler/state. Anyone who knows the plant can find it, and any application can subscribe to it without a custom integration.

The two are complementary. ISA-95 decides what things are called and how they relate; the UNS moves the live values under those names. Without ISA-95, a UNS tends to sprawl into inconsistent, vendor-specific topic names that every new application has to decode. Without a UNS, ISA-95 stays a diagram on the wall instead of a structure that systems actually share.

A UNS carries current state, though, not history or meaning on its own: an application still needs to know what a value represents and where its history lives. That gap is what the rest of this series addresses.

Conclusion: the enduring blueprint for the future

ISA-95 is not a technology; it is a foundational philosophy for communication, data organisation, and operational management. It provides the clear, consistent, and logical rules needed to build the smart factories of today and tomorrow.

Its relevance is only growing, as demonstrated by the 2025 update to the standard, which directly addresses modern trends like “digital transformation,” “data-centric architectures,” and “modular architectures” designed to operate in cloud and hybrid environments. This release equips the global industrial community with the shared ontologies and semantic models needed to design connected, intelligent, and agile manufacturing systems.

As our factories become smarter and more connected, how will a universal language like ISA-95 become even more critical for orchestrating not just machines, but entire intelligent enterprises? The next post in this series starts at the edge, where that language meets the machine.

The Edge to Enterprise series

1. 4 Surprising Truths About ISA-95 - the vocabulary every system shares (you are here)
2. CATIM Edge IPC: the ultimate OT intelligence - why intelligence belongs at the edge
3. The End of API Chaos - one API for every application
4. i3X vs MQTT: One Moves Bytes, the Other Moves Meaning - moving bytes versus moving meaning
5. Sense, Decide, Act: The Controller Is the Platform - the platform we built on these ideas

Next: CATIM Edge IPC: the ultimate OT intelligence

About CATIM. CATIM - Creating Automation Technology In Motion - empowers people to engineer automation solutions that solve hard technical problems. Working on a data or AI project? Get in touch.