ISA-95 (also known as ANSI/ISA-95 and IEC 62264) is an international standard that describes how information should flow between enterprise systems and manufacturing systems. It defines a common set of models, terminology, and integration patterns for connecting business planning and logistics with plant operations. In practice, it is used as a reference framework rather than a detailed implementation blueprint, and its value depends heavily on how consistently it is interpreted and applied across systems and sites.
The primary purpose of ISA-95 is to reduce ambiguity and integration risk when connecting different classes of systems. This includes enterprise systems at Level 4 such as ERP, SCM, finance, and order management, manufacturing operations systems at Level 3 such as MES/MOM, LIMS, WMS, and quality systems, and control and field systems at Levels 0–2 such as DCS, PLCs, SCADA, historians, and instrumentation. By describing the information that should move between these levels, ISA-95 helps organizations reduce ad hoc interfaces and clarify what data should originate where.
A well-known part of ISA-95 is the functional hierarchy, which defines Levels 0–4 and clarifies responsibilities from physical process control up through business planning and logistics. The standard also defines information models for production orders, schedules, materials, equipment, personnel, and process segments, which can be used to structure master data and integration payloads. In addition, it provides activity models for production, quality, maintenance, and inventory operations, and describes the types and directions of information exchanges between enterprise and manufacturing systems.
In regulated manufacturing, ISA-95 is often used to establish a shared language between IT, OT, engineering, quality, and vendors when discussing system responsibilities and data flows. It can help reduce custom, point-to-point integrations that become fragile under change control and validation pressure, especially when multiple vendors are involved. Plants use ISA-95 concepts to clarify boundaries between ERP and MES/MOM, avoid functional overlap or gaps, and support more consistent data structures needed for traceability and regulated reporting.
ISA-95 is not a complete implementation guide and does not prescribe specific architectures, technologies, or products, so design decisions still require local engineering judgment. Vendors and integrators frequently claim ISA-95 alignment but interpret models differently, leading to mismatches unless data definitions, responsibilities, and message structures are specified in detail. The standard focuses on integration and information models, not on detailed control strategies, functional safety, or cybersecurity, which must be addressed using additional standards, internal procedures, and validation approaches.
Aligning existing ERP, MES, SCADA, and custom applications to ISA-95 in a brownfield plant can require significant changes to data structures, interfaces, and even organizational responsibilities. Because most regulated facilities already operate with validated systems and established integrations, adopting ISA-95 is usually an incremental refactoring of models and interfaces, not a wholesale replacement of current platforms. Any ISA-95-driven changes must pass through formal change control, regression testing, and, where applicable, revalidation, which can limit how far and how fast organizations can standardize.
Organizations commonly use ISA-95 to define system roles and boundaries (for example, what resides in ERP versus MES versus LIMS), especially when planning upgrades or integrating new equipment or plants. It is also used to specify integration requirements in RFPs and project documents, giving a structured way to describe production orders, material flows, and equipment capabilities. Many teams adopt ISA-95 information and activity models as a reference when designing master data, production models, and standard-based interfaces for MOM/MES implementations, while still tailoring details to local regulatory, product, and integration constraints.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
