physical model

A physical model in manufacturing and industrial operations is a structured representation of real-world equipment, assets, and material flows. It is used to describe how physical resources are arranged and interact so that control systems, MES, batch systems, and planning tools can work with them in a consistent way.

Core meaning in manufacturing and OT/IT

In this context, a physical model typically includes:

• Equipment and units, such as reactors, mixers, packaging lines, conveyors, tanks, and storage locations.
• Equipment hierarchy, such as site, area, process cell, unit, equipment module, and control module, as commonly referenced in standards.
• Physical connections, such as piping, transfer lines, and material handling systems that define how materials can move.
• Capabilities and constraints, such as maximum batch size, cleanability, or permitted product families on a line.

The physical model does not describe how to make a specific product step by step. Instead, it describes what physical equipment exists, how it is organized, and what it is capable of doing. Control recipes, MES routing, and scheduling rules are then mapped onto this model.

Relation to S88 and other standards

In S88-style batch manufacturing, the physical model usually refers to the equipment model, which structures the physical plant into levels such as process cells, units, equipment modules, and control modules. This model is distinct from the procedural model and recipe structures, but they interact closely:

• The physical model defines where operations can run.
• The procedural model defines how operations are executed.
• Recipes reference the physical model when assigning specific units or equipment for a batch.

Similar physical modeling concepts appear in other frameworks and tools, such as ISA-95 equipment hierarchies, plant models in DCS systems, and resource models in MES/ERP.

Operational use

Physical models are used by:

• Control systems (DCS/PLC) to organize I/O, control modules, and interlocks according to physical equipment.
• MES and batch systems to allocate units, enforce equipment constraints, and manage campaigns.
• Scheduling and planning tools to understand which orders can run on which lines or units.
• Quality and compliance workflows to associate process data, alarms, and events with specific physical assets for traceability.

A well-defined physical model helps ensure that data from OT systems, MES, historians, and quality systems can be consistently tied back to specific equipment and locations.

What it is not

• It is not the same as a procedural model or recipe logic, which describes the sequence of operations.
• It is not necessarily a 3D CAD model, although CAD systems also use the term “physical model” for geometric representations.
• It is not a simulation model by default, although a simulation can be built on top of a physical model.

Common confusion

Physical model vs procedural model: In S88 and similar frameworks, the physical model addresses equipment and structure, while the procedural model addresses tasks, operations, and sequences. Both are needed for a complete manufacturing model.

Physical model vs data model: A physical model describes assets and flows in the physical plant. A data model describes how related information is stored and related in databases or integration layers. The two should align but are conceptually different.

Connection to the source context

In the context of the S88 standard, the physical model typically refers to the S88 equipment model. It is used alongside procedural models and recipes to organize batch manufacturing so that equipment, control, and MES/ERP integration can be managed in a consistent and maintainable way.