Skip to main content

Equipment Model

:::info Quick Reference: 7 Hierarchy Levels Enterprise > Site > Area > Process Cell > Unit > Equipment Module > Control Module

Levels 1-3 follow ISA-95. Levels 4-7 follow ISA-88. You can use as many or as few levels as your plant needs. :::

What is an equipment model?​

Start with a simple question: how do you describe your factory to a computer?

Imagine you are giving a tour to a new employee:

  • "This is our Munich factory" (a site)
  • "We are in the Packaging Hall" (an area)
  • "This is Bottling Line 1" (a production line / process cell)
  • "And this machine here is the Filling Station" (a unit)
  • "See this component? That is Filler Head #3" (an equipment module)
  • "And this little probe measures the temperature" (a sensor / control module)

That natural description of your factory is the equipment model. ISA-95 and ISA-88 simply give it a formal structure so that software like OpSee can organize, filter, and calculate metrics at every level.

The standards behind it​

Two international standards define how manufacturing equipment should be organized:

StandardScopeLevelsFocus
ISA-95 (IEC 62264)Enterprise to Area1-3Business and logistics: where things are
ISA-88 (IEC 61512)Process Cell to Control Module4-7Process control: how things work

Together, they form a complete 7-level hierarchy from the boardroom to the sensor.

The equipment hierarchy​

OpSee supports 7 hierarchy levels that cover the full range from enterprise down to individual sensors:

LevelTermStandardExamplePurpose
1EnterpriseISA-95Acme CorpThe company or organization
2SiteISA-95Munich FactoryA physical location (factory, plant)
3AreaISA-95Packaging HallA logical section within a site
4Process CellISA-88Bottling Line 1A coordinated set of units (a production line)
5UnitISA-88Filling StationWhere a specific operation happens
6Equipment ModuleISA-88Filler Head #3A functional group within a unit
7Control ModuleISA-88Temperature SensorIndividual sensor or actuator

:::info Flexible hierarchy You are not forced to use all 7 levels. Create as many or as few as your plant requires. A small factory might only use Site > Area > Unit. A complex pharmaceutical plant might use all 7. OpSee adapts to your structure. :::

Where does OpSee fit? The automation pyramid​

In manufacturing IT, systems are organized in layers called the automation pyramid (based on ISA-95). OpSee operates at Level 3, the MES layer:

ISA-95 Automation Pyramid The ISA-95 automation pyramid. OpSee operates at Level 3 (MES), connecting the factory floor and business systems.

ISA-95 Automation Pyramid — the five levels from field devices to enterprise

  • Level 0-1: the physical world. Sensors measure temperature, pressure, speed; PLCs control motors and valves
  • Level 2: SCADA systems supervise machines and display HMI screens for operators
  • Level 3: MES (OpSee) connects the factory floor and business systems. It tracks OEE, manages production orders, handles recipes, and monitors quality
  • Level 4: ERP systems handle business planning, finance, and supply chain

:::tip Why does this matter? The pyramid clarifies OpSee's role: it connects the shop floor to the front office. Data flows up from sensors (Level 0) through PLCs and SCADA (Levels 1-2), into OpSee (Level 3), and can be shared with ERP (Level 4). :::

How OpSee implements this​

Equipment properties​

Each equipment item in OpSee has:

  • Name: display name (translated in all configured languages)
  • Type: defines the role in the hierarchy (e.g., "Process Cell", "Unit", "Equipment Module")
  • Parent: the equipment one level up in the hierarchy
  • Icon & Color: visual identification in dashboards and menus
  • Description: free-text description
  • Batch management: whether this equipment supports batch operations (ISA-88)

Equipment types​

Equipment types map to the ISA-88 hierarchy levels. When you create a type, you assign it one of the 7 levels above. This enables:

  1. Classification: group equipment by their role in the hierarchy
  2. OEE behavior: determine which reason trees apply to which equipment types
  3. Recipe matching: recipes reference equipment types, not individual equipment

Equipment classes & capabilities​

  • Classes define categories of similar equipment (e.g., "CNC Machines", "Conveyors", "Reactors")
  • Capabilities define what an equipment can do (e.g., "Welding", "Cutting", "Filling") with optional capacity and unit of measure

These are used by the Recipes module to match equipment requirements to available equipment.

Equipment and other modules​

The equipment hierarchy is the backbone of OpSee. Almost every other module references it:

ModuleRelationship
OEEAvailability records are tracked per equipment. OEE is calculated per equipment or aggregated up the hierarchy
ProductionProduction orders run on specific equipment
PersonnelSchedules assign shifts and operators to equipment
MaterialMaterials are assigned to equipment they run on
RecipesRecipes define which equipment types they require
Data TagsSensors (MQTT/OPC-UA tags) are linked to equipment
CockpitDashboard widgets can be filtered by equipment

Best practices​

:::tip Model your hierarchy before creating equipment Sketch your plant hierarchy on paper first. Start from the top (site/area) and work down. A well-structured hierarchy makes OEE roll-ups, filtering, and reporting much easier. :::

:::tip Use equipment types consistently Create types like "Site", "Area", "Process Cell", "Unit", "Equipment Module" and apply them consistently. This enables filtered views and reason tree assignments that work across your entire plant. :::

:::tip Start simple, expand later You do not need all 7 levels from day one. Start with 3-4 levels that match your current needs. You can always add more detail later as your OEE tracking matures. :::

Next steps​

Prerequisites​