ISA-88 describes not only how recipes are structured but also how equipment is organised, through a physical model that groups equipment into levels. The equipment module is a key level in that model: it bundles together the individual control modules that make up a coordinated bit of processing kit, such as a dosing header or a temperature-control skid. Getting this level right is what makes batch phase logic reusable and keeps configuration clean. This guide explains what an equipment module is, how it groups control modules, where it sits relative to the unit and the control module, and how it can be shared or dedicated.
ISA-88 equipment module in one line: An ISA-88 equipment module is a level of the physical equipment model that groups one or more control modules together to carry out a finite, coordinated processing activity, such as dosing a reagent, transferring material, or controlling a temperature. It sits below the unit and above the control module in the hierarchy, packaging lower-level control elements into a functional block of equipment that phase logic can command, and it can be dedicated to one unit or shared among several.
The equipment module exists to package a set of related control modules into a single functional unit of equipment. A control module is the lowest grouping in the ISA-88 physical model, typically a single device or a small closely-coupled set, such as a valve or a regulatory control loop, that the system commands directly. On their own, individual control modules are just parts. An equipment module gathers the ones that work together to accomplish something and presents them as a coordinated whole that can carry out a defined activity. It is the level at which loose components become a purposeful piece of processing equipment.
The activity an equipment module performs is finite and specific. A dosing header made of several valves and a flow measurement, grouped as an equipment module, exists to add a measured quantity of a reagent. A transfer manifold groups the valves and pump controls needed to move material from one place to another. A temperature-control skid groups the heating, cooling, and sensing elements needed to hold a temperature. In each case the equipment module bundles the underlying control modules into something that does one identifiable job, and it coordinates them so that job is done as a single activity rather than as a set of separate device commands.
This grouping is what lets higher-level logic treat a cluster of equipment as one thing. Instead of a recipe or an operator having to command each valve and pump individually, the equipment module offers the activity as a whole, orchestrating its control modules internally. That abstraction is the point of the level: it hides the detail of how the individual components are driven and exposes only the coordinated function, so the rest of the system deals with a dosing capability or a transfer capability rather than a pile of valves.
The equipment module's place in the physical hierarchy is precise: it sits below the unit and above the control module. A unit is a larger piece of equipment, such as a reactor or a mixing vessel, that carries out major processing activities and around which a batch is often organised. A unit is typically made up of several equipment modules, each providing one of the coordinated functions the unit needs, and each equipment module is in turn made up of control modules. The hierarchy descends from process cell to unit to equipment module to control module, and the equipment module is the level that packages control modules into functions the unit can use.
This positioning explains why the equipment module matters for keeping configuration clean. The unit is too coarse to represent a single coordinated activity like dosing, and the control module is too fine, being just one device. The equipment module is the right-sized level in between: coordinated enough to be a real function, contained enough to be reused. Recognising this middle level, rather than collapsing everything into either the unit or bare control modules, is what gives a batch system its modularity, and confusing the equipment module with the control module beneath it is one of the most common configuration mistakes.
The distinction from the control module is worth stressing because the two are easily conflated. A control module commands a single device or tightly-coupled pair directly; an equipment module coordinates several control modules to perform an activity. A single valve is a control module; the dosing header that uses that valve along with others and a flow measurement is an equipment module. The control module is the atom of direct device control, and the equipment module is the molecule that combines atoms into a function. Keeping that line clear prevents the muddle where every grouping is called an equipment module or every device is treated as one.
An important property of an equipment module is whether it is dedicated to one unit or shared among several. An exclusive-use, or dedicated, equipment module belongs to a single unit and is always available to it. A shared equipment module serves more than one unit, such as a common transfer manifold or a shared reagent header that several reactors draw on, and because more than one unit may want it, its use has to be arbitrated so that two units do not try to command it at once. ISA-88's model accounts for this sharing, and a well-designed batch system manages the acquisition and release of shared equipment as batches run.
Grouping equipment this way is precisely what makes phase logic reusable, which is the practical payoff of the level. Because an equipment module presents a coordinated function through a clean interface, the phase logic that drives that function, the code that actually performs a dose or a transfer, can be written once against the equipment module and reused wherever that kind of module appears. Every dosing header of the same design can share the same dosing phase logic. Without the equipment module abstraction, that logic would be tangled up with specific devices and much harder to reuse, so the modular grouping directly reduces engineering effort and inconsistency.
For monitoring and supervision, the equipment module is a natural unit of visibility as well as of control. Because it represents a coordinated function with a defined state, a supervisory layer can show whether that function is idle, active, held, or, in the shared case, currently acquired by a particular unit. For distributed batch operations, a cloud SCADA platform such as Merobix can surface the state of equipment modules and their underlying process data centrally, so a team can see which shared header is in use, whether a temperature-control skid is holding its target, and how each functional block is behaving across sites. The same modular structure that makes phase logic reusable also makes the plant's state describable in clear functional pieces, which is exactly what makes remote monitoring of a batch operation comprehensible.
A control module is the lowest grouping in the ISA-88 physical model, commanding a single device or a tightly-coupled pair directly, such as a valve or a regulatory loop. An equipment module sits one level up and groups several control modules together to perform a coordinated, finite activity like dosing or transferring. The control module is the atom of direct device control; the equipment module combines those atoms into a function.
Yes. An equipment module can be exclusive-use, dedicated to a single unit, or shared among several units, such as a common transfer manifold or reagent header that several reactors use. Because a shared module can be wanted by more than one unit, its use must be arbitrated so two units do not command it at once, and a batch system manages acquiring and releasing shared equipment as batches run.
An equipment module presents a coordinated function through a clean interface, hiding how its individual control modules are driven. That means the phase logic that performs the function, such as running a dose, can be written once against the equipment module and reused wherever a module of that design appears. Without the abstraction, the logic would be tangled with specific devices and hard to reuse, so the grouping directly cuts engineering effort.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.