The ISA-95 model organizes manufacturing operations into a five-level functional hierarchy, from the physical production process (Level 0) through sensing and actuation (Level 1), supervisory control (Level 2), manufacturing operations management (Level 3), and enterprise business planning and logistics (Level 4). This layered architecture creates clear boundaries of responsibility and data flow, enabling interoperability between ERP systems, MES platforms, and SCADA or PLC controllers without requiring custom point-to-point integrations.
Glossary
ISA-95 Model

What is ISA-95 Model?
The ISA-95 model is an international standard (IEC 62264) that defines a hierarchical framework for integrating enterprise business systems with manufacturing control systems, establishing a common terminology and information model for the interface between the enterprise and plant floor.
By standardizing the data models for equipment, personnel, materials, and process segments, ISA-95 provides the semantic foundation for modern Industrial DataOps pipelines and Unified Namespace architectures. The model's object-oriented asset hierarchy directly informs how sensor telemetry is contextualized and structured within time-series databases and stream processing frameworks, ensuring that raw machine data carries the operational context—such as work order, batch ID, and equipment state—required for meaningful analytics and autonomous decision-making.
Core Components of the ISA-95 Standard
The ISA-95 model defines a standardized framework for integrating enterprise business systems with manufacturing control systems through a hierarchical decomposition of activities and data flows.
Level 4: Business Planning & Logistics
The highest level of the hierarchy, encompassing enterprise-wide business activities. This level establishes the basic plant production schedule, material use, shipping, and inventory levels.
- Core Functions: Order processing, demand forecasting, procurement, long-term production planning
- Time Horizon: Months to years
- Key Systems: ERP (Enterprise Resource Planning), PLM (Product Lifecycle Management)
- Data Exchange: Communicates production plans and receives plant performance summaries from Level 3
Level 3: Manufacturing Operations Management
The domain of workflow and recipe control that coordinates the execution of production on the plant floor. This level manages the detailed scheduling, quality assurance, and resource allocation to meet Level 4 objectives.
- Core Functions: Detailed production scheduling, dispatching, quality management, maintenance management
- Time Horizon: Days to weeks
- Key Systems: MES (Manufacturing Execution System), LIMS (Laboratory Information Management System), WMS (Warehouse Management System)
- Data Exchange: Translates business plans into operational commands; aggregates process data from Level 2 for reporting
Level 2: Supervisory Control
The layer responsible for monitoring, supervising, and controlling the physical process through automated systems. This level executes the recipes and setpoints defined by Level 3.
- Core Functions: Supervisory control, data acquisition, alarm management, operator interfaces
- Time Horizon: Seconds to hours
- Key Systems: SCADA (Supervisory Control and Data Acquisition), HMI (Human-Machine Interface)
- Data Exchange: Sends setpoints to Level 1 controllers; collects real-time process data for visualization and historical logging
Level 1: Basic Process Control
The direct sensing and manipulation of the physical process. This level executes closed-loop control algorithms to maintain process variables at desired setpoints.
- Core Functions: PID loop control, discrete logic execution, safety interlocks, analog and digital I/O processing
- Time Horizon: Milliseconds to seconds
- Key Systems: PLCs (Programmable Logic Controllers), DCS (Distributed Control Systems), RTUs (Remote Terminal Units)
- Data Exchange: Reads sensor inputs; writes actuator outputs; reports process values to Level 2
Level 0: Physical Production Process
The actual physical equipment and material transformation occurring on the factory floor. This level represents the tangible reality that all higher levels seek to monitor and control.
- Core Functions: Material transformation, motion, chemical reaction, assembly
- Time Horizon: Real-time, continuous
- Key Components: Motors, valves, conveyors, reactors, robots, sensors, actuators
- Data Exchange: Generates raw sensor signals consumed by Level 1; receives actuation commands from Level 1 controllers
Activity Models & Data Structures
Beyond the physical hierarchy, ISA-95 defines standardized activity models and data structures for information exchange between levels. These models decompose manufacturing operations into generic, reusable functions.
- Part 1: Defines standard terminology and object models for resources, personnel, equipment, and material
- Part 2: Specifies B2MML (Business To Manufacturing Markup Language) , an XML schema implementing the object models for electronic data exchange
- Part 3: Details activity models for production, maintenance, quality, and inventory operations management
- Part 5: Establishes KPIs and metrics for measuring manufacturing performance across the hierarchy
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the ISA-95 standard, its hierarchical structure, and its role in modern industrial data architectures.
The ISA-95 model (ANSI/ISA-95) is an international standard developed by the International Society of Automation that defines a hierarchical framework for integrating enterprise business systems with manufacturing control systems. It works by establishing a clear, five-level functional hierarchy that segments industrial operations from the physical production process at Level 0 up to enterprise business planning at Level 4. The model specifies standardized terminology, information models, and data exchange interfaces between these levels, with a particular focus on the critical boundary between Level 3 (Manufacturing Operations Management) and Level 4 (Enterprise Resource Planning). By defining objects such as personnel, equipment, physical assets, and process segments, ISA-95 creates a common language that enables disparate systems—from PLCs and SCADA to ERP and MES—to exchange contextualized production data reliably. This structured decomposition prevents the chaotic point-to-point integration that plagues many factories, instead promoting a modular, maintainable architecture where each level can evolve independently while adhering to agreed-upon data contracts.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
The ISA-95 model does not operate in isolation. These interconnected standards and architectural patterns form the technical foundation for implementing the hierarchical model in modern, software-defined industrial environments.
Unified Namespace (UNS)
A single source of truth for all industrial data, structured around the ISA-95 asset hierarchy. It enables decoupled, real-time data exchange between OT and IT systems by organizing information based on the Enterprise > Site > Area > Line > Cell model.
- Maps directly to ISA-95 physical asset hierarchy
- Enables contextualized data discovery without point-to-point integration
- Uses MQTT Sparkplug for stateful, topic-based communication
Purdue Model
A reference architecture for industrial control system security that segments the network into hierarchical levels, from physical processes to the enterprise DMZ. It is the security-focused counterpart to ISA-95's functional hierarchy.
- Level 0/1: Physical process and basic control
- Level 2: Area supervisory control
- Level 3: Site manufacturing operations (MOM)
- Level 4: Business planning and logistics (ERP)
OPC UA PubSub
An extension of OPC Unified Architecture that decouples data producers from consumers using a publish-subscribe pattern, often over MQTT or AMQP. It enables scalable cloud and edge integration while preserving the rich information modeling that maps to ISA-95 equipment hierarchies.
- Supports JSON and binary encoding for efficiency
- Integrates with MQTT brokers for cloud-native architectures
- Maintains ISA-95 compliant asset modeling
Data Historian
A specialized time-series database designed for industrial environments to archive high-fidelity process data over long periods. Historians are the primary data repository at ISA-95 Levels 2 and 3, capturing sensor telemetry for compliance, analysis, and reporting.
- Optimized for lossless compression of analog signals
- Supports time-weighted averages and interpolation
- Foundation for predictive maintenance algorithms
Asset Administration Shell (AAS)
A standardized digital representation of an industrial asset defined by Industry 4.0 (IEC 63278) . It provides a discoverable, interoperable interface for an asset's properties, capabilities, and lifecycle data, serving as the digital twin counterpart to ISA-95's physical asset model.
- Contains submodels for different lifecycle aspects
- Enables cross-vendor interoperability
- Complements ISA-95 hierarchy with semantic richness
Digital Thread
A communication framework that connects traditionally siloed data throughout the product lifecycle, from design and manufacturing to service. It creates a closed feedback loop that traverses all ISA-95 levels, linking ERP, MES, SCADA, and physical processes.
- Links PLM data to operational performance
- Enables traceability from raw material to finished product
- Closes the loop between design intent and manufacturing reality

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us