A shared set of rules that describes the objects that matter in a factory, such as products, orders, operations, resources and states, with stable identities and the relationships between them across systems like ERP, MES and maintenance.
An industrial data model is a shared set of rules that describes the objects that matter in a factory, such as products, orders, operations, resources and states. It gives these objects stable identities and defines the relationships between them, so that the same object can be recognized across systems such as ERP, MES and maintenance. The concept addresses a common situation: a factory can collect large amounts of data and still struggle to answer a basic operational question about what a given event actually affects.
The starting point is that each system in a plant describes the same factory from its own viewpoint. According to the M365.FM episode "What Is an Industrial Data Model", ERP knows customer orders, materials, planned dates and inventory. MES knows what is executing on the shop floor. PLCs and SCADA know machine states, alarms and process values. Maintenance knows asset condition and service history. Quality knows inspection and release status, and engineering knows the product definition. The episode frames the core problem as one of description rather than collection: the issue is usually not a lack of data, but that these systems describe the same factory through different structures and identifiers. An industrial data model supplies the common layer that ties those descriptions together.
In practice, such a model is used to connect events and records that would otherwise stay isolated. A machine alarm, for example, only becomes meaningful for planning or quality when it can be traced to the resource, the operation, the order and the product involved. Stable identities for objects and explicit relationships between them make that tracing possible. Typical decisions around a model include which objects to represent, how to identify them consistently across source systems, which states to track, and how the relationships between orders, operations, resources and products should be expressed.
Standards offer one established example of this kind of thinking. ISA-95, also standardized as ANSI/ISA-95 and IEC 62264, is an international standard from the International Society of Automation for building an automated interface between enterprise systems and control systems. It applies to batch, continuous and repetitive processes in any industry. Its objectives are consistent terminology, consistent information models and consistent operations models, so that suppliers and manufacturers share a common foundation. The sources note that the ISA-95 page does not use the phrase industrial data model, so it should be read as a standards-based example rather than a definition of the term.
The structure of ISA-95 illustrates how a shared model can be organized. Part 1 sets terminology and object models that determine which information should be exchanged and helps define the boundary between enterprise and control systems. It includes a Purdue-style scheduling and control hierarchy, an equipment hierarchy, a functional data flow model, and object models with relationships and attributes. Part 2 defines attributes for every object in Part 1, which can underpin information exchange and relational databases. Part 3 models manufacturing operations management at level 3, the production or MES layer, and later parts address object models for operations management, business-to-manufacturing transactions, messaging and information exchange profiles.
Taken together, an industrial data model is less a single product than an agreement about how a factory's objects, identities and relationships are described. It sits between the enterprise level, where ERP holds orders and materials, and the control level, where PLCs and SCADA hold machine states and process values, and it helps the systems in between, such as MES, maintenance and quality, refer to the same things in the same way.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
Type
Concept
Key points about Industrial data model
Key points about Industrial data model from the episodes, each with its source episode:
An industrial data model creates shared meaning by defining factory objects and giving them stable identity. · What Is an Industrial Data Model
Episodes about Industrial data model
Episodes in which Industrial data model is discussed:
A factory can collect mountains of data and still struggle to answer what a single machine stop really affects. This episode is for manufacturing, IT/OT and data architects who need ERP, MES, maintenance and quality data to share one meaning. Learn how an…
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is an industrial data model? (AI)
It is a shared set of rules that describes the objects that matter in a factory, such as products, orders, operations, resources and states, with stable identities and relationships between them across systems like ERP, MES and maintenance.
Why do factories need one if they already collect a lot of data? (AI)
The M365.FM episode "What Is an Industrial Data Model" says the problem is usually not missing data but that ERP, MES, SCADA, maintenance, quality and engineering describe the same factory through different structures, which makes it hard to tell what an event affects.
How does ISA-95 relate to an industrial data model? (AI)
ISA-95 (also IEC 62264) defines terminology, object models and attributes for exchanging information between enterprise and control systems. The source does not use the phrase industrial data model, so it serves as a standards-based example rather than a definition.
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.