Many manufacturers buy MES software as a standalone block, set down next to the existing systems. The ISA-95 standard tells another story: it assigns the software a precise position in the architecture and two non-negotiable interfacing obligations. Understanding this position changes how you scope a project. The CIM pyramid (Computer-Integrated Manufacturing) imposes very concrete constraints on an industrial architecture, well beyond the theoretical diagram everyone has already come across.
Key takeaways
- The ISA-95 standard, equivalent to IEC 62264, structures the plant into hierarchical levels, from the field to business management.
- MES software sits at level 3, between industrial SCADA and enterprise management.
- This position imposes two standardized interfaces: down to SCADA, up to the ERP.
- Complying with ISA-95 determines interoperability and prevents the build-up of data silos.
MES software: its exact place in the CIM pyramid
The ISA-95 standard, published internationally as IEC 62264, defines the models and interfaces between enterprise management systems and industrial control systems. It organizes the plant into hierarchical levels, each with a distinct role. This breakdown is what the CIM pyramid represents.
This pyramid has five tiers. Levels 0 and 1 cover the physical process, the sensors and the PLCs. Level 2 is the industrial SCADA layer, handled by the SCADA system and the HMI. Level 4 brings together the ERP and the enterprise’s business planning. Level 3 is the territory of MES software. It drives production execution: manufacturing orders, traceability, quality control, real-time tracking of operations. Confusing this level with SCADA is a common mistake, with heavy consequences for a project’s scope. SCADA drives equipment in real time, while MES software orchestrates and records execution.
This boundary is not just a matter of vocabulary. It determines who does what, and therefore which functions you expect from each software block. Badly drawn, it leads to costly functional duplication, or worse, to gaps in the data chain.
What the ISA-95 standard imposes on the architecture
An ISA-95 interface is a standardized exchange point between two levels of the pyramid, defining which data flows and in what format. The position of level 3, therefore, imposes two interfaces on MES software, not one. This is the architectural consequence most often underestimated at the scoping stage.
The downward interface connects level 3 to level 2. Here the MES collects the real-time data fed up by industrial SCADA. Without a reliable historian layer to turn this raw data into usable information, execution stays blind. The quality of the MES depends first on the quality of the data it receives.
The upward interface connects level 3 to level 4. MES software exchanges orders, bills of materials and production reports with the ERP. The B2MML standard, derived from ISA-95, structures these exchanges in XML and avoids custom gateways, which are costly to maintain and hard to evolve.
The direct consequence: IT/OT convergence is not an option, but a requirement imposed by the position of level 3. An indicator like OEE is only reliable if the chain between SCADA and execution is wired to the standard. Data poorly qualified at the bottom of the pyramid distorts every decision made at the top.
Choosing MES software compatible with an ISA-95 architecture
Open MES software is a platform able to communicate with its existing environment without heavy custom development, upstream and downstream. This openness is not a convenience; it is the condition for complying with ISA-95 without recreating silos. Three criteria make it concrete in the field:
- An open and modular platform, able to communicate in multiple protocols with the level 2 already in place without forcing the replacement of the existing SCADA.
- A native or tightly integrated historian layer, to avoid depending on fragile exports between heterogeneous systems.
- Standardized connectors to the ERP, rather than gateways developed case by case.
In practice, an MES that ignores ISA-95 ends up recreating the silos it claimed to abolish. It then increases the operational maintenance burden across the installation’s entire lifecycle.
The value of MES software does not lie in its feature list but in its ability to occupy level 3 of the CIM pyramid cleanly. ISA-95 is not an administrative constraint: it is the grammar that guarantees your data flows from the field up to business management. Scoping an MES project means checking its two interfaces first, before looking at its screens.
