ISA-95 / IEC 62264

Overview

ISA-95, published internationally as IEC 62264, defines models and terminology for integrating enterprise systems (level 4) with manufacturing operations and control systems (levels 0–3). Its centrepiece is the role-based equipment hierarchy, a consistent way to describe a site from the enterprise down to individual equipment, alongside object models for equipment, material, and personnel. Evaluators on industrial tenders use ISA-95 as a common vocabulary for plant data, so a platform that follows the same model integrates with far less custom mapping.

Key requirements

Role-based equipment hierarchy

Model physical assets as a hierarchy of Enterprise, Site, Area, Work Center, and Work Unit so every system shares one structural view of the plant.

Consistent object model

Represent equipment, material, and personnel with consistent, typed objects and properties rather than ad-hoc tags, so data has the same meaning everywhere.

Equipment classes and instances

Define reusable equipment classes (templates) and instantiate them, so common properties and behaviour are defined once and shared across like assets.

Level 3 to level 4 integration

Provide a clean boundary and data flow between operations/control (level 3) and business systems (level 4) so production information moves between them reliably.

How ControlBird aligns

Hierarchical entity tree mirrors the equipment hierarchy

ControlBird's data model is a hierarchical tree of entities with explicit parent and child relationships. You can model Enterprise → Site → Area → Work Center → Work Unit directly, with no translation layer between the standard's model and the product's.

Schema inheritance models equipment classes

Entity types are schema-driven and support inheritance, so you define an equipment class once with its shared fields and derive specific equipment from it. This matches the ISA-95 notion of equipment classes and instances.

Typed entity and field model gives a consistent object model

Every entity has a type and strongly typed fields. Equipment, the assets it represents, and related records are described with the same consistent object model the standard calls for, instead of loosely named tags.

Reactive data flow supports level 3 to level 4 integration

Field indirection and change notifications let business-facing services read and react to operations data through the same store, providing a clean, observable path for production information to move between control and enterprise layers.