Physical Model

What is the physical model?

The physical model is the hierarchical equipment model of the batch control standard ISA-88 (IEC 61512-1) that divides a production plant into seven levels: enterprise, site, area, process cell, unit, equipment module and control module. Every piece of equipment gets a fixed place and a fixed role, from the corporate group down to a single valve. As a result, control code, recipes, MES and ERP can refer to the same equipment by the same names. The model is a shared language in which OT and IT meet.

The physical model describes what you produce with, separately from what you produce. That separation makes equipment control reusable for every recipe.

🧠 Which levels make up the physical model?

ISA-88 was approved by ISA in 1995, adopted by the IEC in 1997 as IEC 61512-1 and revised in 2010 as ANSI/ISA-88.00.01-2010. The seven levels fall into two groups. A company sets up the top three according to organisational and business criteria; the standard does not elaborate on them. The bottom four are defined by engineering and form the core of batch control.

Levels may be omitted, but a process cell always contains at least one unit. A collection of units and associated equipment used to make all or part of a batch is called a train in ISA-88.

🔧 What exactly do equipment modules and control modules do?

The distinction between the two lowest levels determines how reusable your control code becomes:

• Control module - one or more field devices with their basic control, such as a control valve with position feedback, a pump with motor protection, or a PID control loop with sensor and actuator. A control module executes commands (open, close, setpoint), monitors itself and reports status and alarms. In code this is often one function block per device, named after its tag, for example TIC-101.
• Equipment module - a functional group of control modules that independently carries out a minor processing activity, such as dosing, heating or agitating. An equipment module can contain an equipment phase that is called from the recipe.
• Unit - the collection of equipment modules and control modules around one main vessel, such as a reactor or mixing tank.

A common mistake is to treat the PLC or the controller itself as a control module. The PLC is the platform the modules run on; the control module is the logical unit of device plus control. The 2010 edition explicitly allows a process cell to contain equipment modules or control modules directly, for example for shared storage tanks, and a unit to contain control modules directly without an intermediate equipment module.

🔄 How does the physical model relate to the other ISA-88 models?

The physical model does not stand alone. ISA-88 links it to a procedural control model and a recipe model:

The master recipe refers to equipment classes, for example “a 5,000-litre mixing tank”. Only when a batch starts does the batch system allocate a specific unit. The same recipe therefore runs on any unit of the same class, and a new product does not need new PLC code.

🏭 How does it differ from the ISA-95 equipment hierarchy?

The physical model is often attributed to ISA-95, but the seven levels including equipment module and control module come from ISA-88. ISA-95 has its own, role-based equipment hierarchy that builds on ISA-88:

ISA-95 stops at the work unit because MES and ERP do not schedule any lower; equipment modules and control modules belong to the world of control. ISA-95 also covers discrete manufacturing (production line, work cell) and continuous processes (production unit). The technical report ISA-TR88.95.01-2008 describes how to use both standards together.

📦 What does the physical model look like in practice?

A brewery is a classic ISA-88 example:

• Enterprise: brewing group
• Site: brewery in North Brabant
• Area: brewhouse
  • Process cell: brewing line 1
    • Unit: mash tun
      • Equipment module: water dosing (flow meter, dosing valve, temperature control)
        • Control module: dosing valve with limit switches
        • Control module: hot water temperature control loop
      • Equipment module: agitator with variable frequency drive
    • Unit: lauter tun, wort kettle, whirlpool

You can set up the model step by step:

1. Start from the P&ID - mark the main vessels (units) and draw boundaries around equipment that always works together.
2. Fix the naming - use one naming convention, for example site/area/cell/unit/em/cm, that recurs in the PLC, SCADA, the historian and MES.
3. Decide on shared equipment - piping, CIP installations and storage tanks that serve several units need an explicit choice and allocation.
4. Build a module library - one tested type per control module (valve, pump, control loop) and per equipment module, product-neutral.
5. Link to asset management - register the same hierarchy in your asset inventory and CMMS, so failures, maintenance and assets sit in the same place in the tree.

🔐 What does the physical model mean for IT/OT integration and security?

• Data structure - in a Unified Namespace the topic structure often follows the same tree; OPC UA address spaces and MQTT Sparkplug B can represent the hierarchy directly.
• Operation - ISA-101 recommends a display hierarchy for HMI screens that runs from overview to detail; it maps neatly onto the tree from area via unit to control module.
• Zones - a process cell with its units often forms one zone in the zones and conduits model of IEC 62443. Segmentation along those boundaries limits the impact of an incident to one production line.
• Risk assessment - because every device has a fixed place, you can assess vulnerabilities and changes per cell or unit, which strengthens OT security.

❓ Frequently asked questions

Is the physical model part of ISA-88 or ISA-95?

The physical model with seven levels down to the control module is part of ISA-88 Part 1 (IEC 61512-1). ISA-95 uses a derived equipment hierarchy that stops at the work unit. The terms process cell and unit appear in both standards.

What is the difference between a unit and an equipment module?

A unit in the physical model carries out one or more major processing activities and usually processes one batch at a time, like a reactor. An equipment module carries out a smaller, well-defined activity, such as dosing or heating, and usually belongs to a unit. Recipes are allocated to units; equipment modules execute the phases.

Is a PLC a control module?

A PLC is not a control module in the ISA-88 physical model. A control module is the logical combination of a field device, such as a valve or pump, with its basic control. That control runs as a software block on a PLC or DCS, which often hosts hundreds of control modules at once.

Do you have to use every level of the physical model?

No, levels of the physical model may be omitted when they add no value in your situation. A small plant, for example, has only one site and one area. Only the unit is indispensable, because recipes and batches are allocated to it.

Can the physical model be used outside batch production?

The physical model was written for batch processes, but the idea of reusable equipment modules and control modules is also applied in continuous and discrete environments. For discrete lines and machines, the ISA-95 hierarchy and PackML are a more natural fit. See also Discrete, Batch and Continuous Processes.

How does the physical model help with a Unified Namespace?

The physical model provides a stable, unambiguous tree structure for topic names in a Unified Namespace. Data from a temperature control loop then gets a path such as site/area/cell/unit/module that every consumer understands. That prevents each system from using its own naming.

📌 In summary

The ISA-88 physical model gives every piece of equipment a fixed place in seven levels, from enterprise to control module, so that control, recipes and business systems speak the same language.

The top three levels are organisational, the bottom four technical. Process cell and unit form the bridge to the ISA-95 hierarchy of MES and ERP, while equipment modules and control modules make control modular and reusable. Applying the model consistently in the PLC, SCADA, historian and asset management lays a solid foundation for OT convergence and for zoning according to IEC 62443.