![\"A](\"https://wiki.aspotomasyon.com/assets/diagrams/opc-solutions-context.svg\")
OPC UA Companion Specifications define standardized information models for specific industries and application domains. They enable semantic interoperability between devices and software from different vendors, ensuring that a \"pump\" or \"temperature sensor\" from one manufacturer is understood identically by systems from another.
The base OPC UA specification provides a generic object-oriented address space with nodes, references, and services. It defines fundamental types (BaseObjectType, BaseVariableType) and built-in services (Read, Write, Browse, Subscribe). However, a generic \"pump\" node carries no semantic meaning about pump-specific parameters, states, or methods. Companion specifications build on this foundation by:
\nThis layered approach ensures that any OPC UA client can discover and interact with devices from any vendor at a semantically meaningful level without prior knowledge of proprietary protocols.
\n\nEUROMAP 83 defines the OPC UA information model for injection moulding machines, while EUROMAP 84 covers the interface between injection moulding machines and handling robots (auxiliary equipment). Together they standardise:
\nFor a plastics manufacturer with 20 machines from five vendors, EUROMAP 83/84 eliminates the need for five different data-mapping drivers. A single OPC UA client can read cycle counts, alarm histories, and quality data from every machine identically.
\n\nThe ISA-95 companion specification maps the standard equipment hierarchy to OPC UA object types:
\nEach object carries ISA-95 attributes such as equipment status, personnel assignments, and material consumption. This allows an MES to navigate the OPC UA address space from Enterprise down to individual sensors, exactly mirroring the ISA-95 hierarchy used in ERP and MES databases.
\n\nPackML standardises the state model and tag naming convention for packaging machinery. Its OPC UA companion specification represents the PackML state machine as an OPC UA FiniteStateMachineType with the following standard states:
\nIdle → Starting → Execute → Idle (normal cycle) with additional states: Held, Suspended, Aborted, Stopped, Resetting, Completing, Complete. Transitions are clearly defined: e.g., from Execute, a \"hold\" command transitions to Held; from Held, a \"resume\" command returns to Execute.
The tag naming convention (e.g., .Machine.StateCurrent, .Machine.ProductionRate, .Machine.AlarmActive) is encoded as standardised OPC UA Variables. Any OPC UA-enabled SCADA or MES can consume PackML data from any compliant packaging machine without custom engineering.
\n\nMDIS addresses the maritime industry's need for interoperable shipboard systems. It defines an OPC UA object model for:
\nBy standardising these data models, MDIS enables a single integrated bridge system to monitor and control equipment from multiple vendors. Classification societies (DNV, Lloyds, Bureau Veritas) increasingly require MDIS compliance for new-build vessels.
\n\nThe Field Device Integration (FDI) standard (IEC 62769) packages device configuration, diagnostics, and calibration data into a consistent OPC UA information model. An FDI package contains the device's full electronic device description (EDD) and user interface components. When integrated via OPC UA:
\nCompanion specifications are the key enabler of plug-and-produce interoperability in Industry 4.0. When a new device is connected to the network, an OPC UA discovery client can:
\nThis reduces engineering effort from days to minutes for device integration and lays the foundation for truly interoperable, multi-vendor automation architectures.
\n\n\nASP OTOMASYON A.Ş. and its subsidiaries OPCTurkey and ASP Dijital provide end-to-end industrial engineering solutions for process automation, data operations and AI.
Follow an ASP project guide to connect the fundamentals with implementation and acceptance.
![\"Engineering](\"https://wiki.aspotomasyon.com/assets/diagrams/opc-solutions-review.svg\")
Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.
","markdown":"# OPC UA Companion Specifications — Industry-Specific Information Models\n\n> OPC UA Companion Specifications define standardized information models for specific industries and application domains.\n\n- Canonical URL: https://wiki.aspotomasyon.com/article/opc-ua-companion-specifications\n- Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki)\n- Category: OPC Solutions\n- Published: 2026-05-13 · Updated: 2026-09-13\n- Reading time: 5 min · Language: English\n\n**OPC UA Companion Specifications** define standardized information models for specific industries and application domains. They enable semantic interoperability between devices and software from different vendors, ensuring that a \"pump\" or \"temperature sensor\" from one manufacturer is understood identically by systems from another.\n\n\n\n*A conceptual OPC UA client/server path. Application certificates establish application trust; user authorization controls what a connected user may do.*\n\n---\n\n## How Companion Specifications Extend the OPC UA Base Model\n\nThe base OPC UA specification provides a generic object-oriented address space with nodes, references, and services. It defines fundamental types (BaseObjectType, BaseVariableType) and built-in services (Read, Write, Browse, Subscribe). However, a generic \"pump\" node carries no semantic meaning about pump-specific parameters, states, or methods. Companion specifications build on this foundation by:\n\n- Defining **domain-specific ObjectTypes** (e.g., InjectionMouldingMachineType, PackagingMachineType)\n- Standardising **Variable names and data types** (e.g., MoldTemperature has EURange of 0–400 °C)\n- Specifying **state machines** with standardised states and transitions\n- Defining **Methods** for domain operations (e.g., StartCycle, EjectPart, ChangeMold)\n\nThis layered approach ensures that any OPC UA client can discover and interact with devices from any vendor at a semantically meaningful level without prior knowledge of proprietary protocols.\n\n## EUROMAP 83/84 — Injection Moulding Machines\n\nEUROMAP 83 defines the OPC UA information model for injection moulding machines, while EUROMAP 84 covers the interface between injection moulding machines and handling robots (auxiliary equipment). Together they standardise:\n\n- **Process parameters:** Injection pressure, screw speed, barrel zone temperatures, back pressure, clamping force, and cycle time. Each parameter is published as a typed Variable with engineering units and range metadata.\n- **Machine states:** A standardised state machine (Idle, Setup, Production, Alarm, Stopped, etc.) with defined transitions. An MES can query any EUROMAP 83-compliant machine and know exactly what state it is in.\n- **Alarms and events:** Standardised alarm categories and severity levels. Alarms include a machine-readable Cause and RemedialAction, enabling automated response workflows.\n\nFor a plastics manufacturer with 20 machines from five vendors, EUROMAP 83/84 eliminates the need for five different data-mapping drivers. A single OPC UA client can read cycle counts, alarm histories, and quality data from every machine identically.\n\n## ISA-95 Companion Specification — MES Integration\n\nThe ISA-95 companion specification maps the standard equipment hierarchy to OPC UA object types:\n\n- **Enterprise** → EnterpriseType (top-level organisational unit)\n- **Site** → SiteType (a geographic location, e.g., a factory)\n- **Area** → AreaType (a production area, e.g., Batch Processing Area)\n- **Production Line / Cell** → WorkCenterType (a physical grouping of equipment)\n- **Unit / Machine** → EquipmentModuleType (individual process units or machines)\n\nEach object carries ISA-95 attributes such as equipment status, personnel assignments, and material consumption. This allows an MES to navigate the OPC UA address space from Enterprise down to individual sensors, exactly mirroring the ISA-95 hierarchy used in ERP and MES databases.\n\n## PackML (OMAC) — Packaging Machine Language\n\nPackML standardises the state model and tag naming convention for packaging machinery. Its OPC UA companion specification represents the PackML state machine as an OPC UA FiniteStateMachineType with the following standard states:\n\n`Idle → Starting → Execute → Idle` (normal cycle) with additional states: Held, Suspended, Aborted, Stopped, Resetting, Completing, Complete. Transitions are clearly defined: e.g., from Execute, a \"hold\" command transitions to Held; from Held, a \"resume\" command returns to Execute.\n\nThe tag naming convention (e.g., .Machine.StateCurrent, .Machine.ProductionRate, .Machine.AlarmActive) is encoded as standardised OPC UA Variables. Any OPC UA-enabled SCADA or MES can consume PackML data from any compliant packaging machine without custom engineering.\n\n## MDIS — Maritime Device Integration Standard\n\nMDIS addresses the maritime industry's need for interoperable shipboard systems. It defines an OPC UA object model for:\n\n- **Main engines and auxiliary engines:** Speed, load, exhaust temperature, fuel consumption, vibration\n- **Navigation equipment:** GPS, gyrocompass, radar, AIS, echo sounder\n- **Auxiliary systems:** Ballast water treatment, fire detection, HVAC, power generation\n\nBy standardising these data models, MDIS enables a single integrated bridge system to monitor and control equipment from multiple vendors. Classification societies (DNV, Lloyds, Bureau Veritas) increasingly require MDIS compliance for new-build vessels.\n\n## FDI — Field Device Integration\n\nThe Field Device Integration (FDI) standard (IEC 62769) packages device configuration, diagnostics, and calibration data into a consistent OPC UA information model. An FDI package contains the device's full electronic device description (EDD) and user interface components. When integrated via OPC UA:\n\n- HART, FOUNDATION Fieldbus, and PROFIBUS devices appear as OPC UA objects with standardised parameters\n- Configuration software from any vendor can commission and calibrate any FDI-compliant device\n- Diagnostic data (e.g., electronics temperature, sensor drift, communication errors) is exposed uniformly\n\n## Enabling Plug-and-Produce Interoperability\n\nCompanion specifications are the key enabler of **plug-and-produce** interoperability in Industry 4.0. When a new device is connected to the network, an OPC UA discovery client can:\n\n1. Browse the device's address space to determine its supported companion specifications\n2. Instantiate the standardised ObjectTypes and state machines\n3. Map device signals directly to the MES, SCADA, or digital twin without manual configuration\n\nThis reduces engineering effort from days to minutes for device integration and lays the foundation for truly interoperable, multi-vendor automation architectures.\n\n> ASP OTOMASYON A.Ş. and its subsidiaries OPCTurkey and ASP Dijital provide end-to-end industrial engineering solutions for process automation, data operations and AI.\n\n---\n\n## References & Further Reading\n\n1. [OPC Foundation — Companion Specifications Directory](https://reference.opcfoundation.org/) — Official listing of all OPC UA companion specifications, including EUROMAP 83/84, ISA-95, PackML, MDIS, and FDI information models.\n2. [EUROMAP — European Plastics and Rubber Machinery Association](https://www.euromap.org) — Official EUROMAP 83/84 specifications for OPC UA information models in plastics injection moulding machine integration.\n3. [ISA-95 / IEC 62264 — Enterprise-Control System Integration](https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard) — International standard for which the OPC UA companion specification defines standardised information models mapping the ISA-95 equipment hierarchy.\n4. [OMAC — PackML Packaging Machine Language](https://www.automate.org/omac/packml.aspx) — Official OMAC guidelines for PackML, the industry standard state model and tag naming convention for packaging machinery with OPC UA companion specification.\n5. [FieldComm Group — FDI (Field Device Integration) Standard](https://en.wikipedia.org/wiki/IEC_62769) — Official FDI specification (IEC 62769) for universal device integration and configuration across HART, FOUNDATION Fieldbus, and PROFIBUS protocols.\n6. [MDIS — Maritime Device Integration Standard](https://reference.opcfoundation.org/MDIS/v130/docs/1) — Official MDIS specification for OPC UA-based interoperability of maritime and offshore systems, covering engines, navigation, and auxiliary equipment.\n\n## Apply this to your project\n\n- Record the endpoint, supported security policies, application identity, certificate expiry, and user permissions.\n- Verify the value, engineering unit, StatusCode, and source timestamp together at the receiving application.\n- Test disconnection and recovery with representative subscriptions; preserve evidence of any data gaps or repeated values.\n\n[Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance.\n\n\n\n*Engineering review sequence: Discover → Authenticate → Subscribe → Recover. Keep the recorded evidence with the accepted configuration.*\n\n## Primary references and further reading\n\nUse the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.\n\n- [OPC Foundation — OPC UA Part 4: Services](https://reference.opcfoundation.org/specs/OPC-10000-4/)\n- [OPC Foundation — OPC UA Part 2: Security Model](https://reference.opcfoundation.org/specs/OPC-10000-2/)\n\n---\n\nCite the canonical article: https://wiki.aspotomasyon.com/article/opc-ua-companion-specifications (OPC UA Companion Specifications — Industry-Specific Information Models, ASP OTOMASYON, updated 2026-09-13).\n","headings":[{"id":"how-companion-specifications-extend-the-opc-ua-base-model","title":"How Companion Specifications Extend the OPC UA Base Model"},{"id":"euromap-8384-injection-moulding-machines","title":"EUROMAP 83/84 — Injection Moulding Machines"},{"id":"isa-95-companion-specification-mes-integration","title":"ISA-95 Companion Specification — MES Integration"},{"id":"packml-omac-packaging-machine-language","title":"PackML (OMAC) — Packaging Machine Language"},{"id":"mdis-maritime-device-integration-standard","title":"MDIS — Maritime Device Integration Standard"},{"id":"fdi-field-device-integration","title":"FDI — Field Device Integration"},{"id":"enabling-plug-and-produce-interoperability","title":"Enabling Plug-and-Produce Interoperability"},{"id":"references-further-reading","title":"References & Further Reading"},{"id":"apply-this-to-your-project","title":"Apply this to your project"},{"id":"primary-references-and-further-reading","title":"Primary references and further reading"}],"faq":[],"references":[{"name":"OPC Foundation — Companion Specifications Directory","url":"https://reference.opcfoundation.org/"},{"name":"EUROMAP — European Plastics and Rubber Machinery Association","url":"https://www.euromap.org"},{"name":"ISA-95 / IEC 62264 — Enterprise-Control System Integration","url":"https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard"},{"name":"OMAC — PackML Packaging Machine Language","url":"https://www.automate.org/omac/packml.aspx"},{"name":"FieldComm Group — FDI (Field Device Integration) Standard","url":"https://en.wikipedia.org/wiki/IEC_62769"},{"name":"MDIS — Maritime Device Integration Standard","url":"https://reference.opcfoundation.org/MDIS/v130/docs/1"},{"name":"OPC Foundation — OPC UA Part 4: Services","url":"https://reference.opcfoundation.org/specs/OPC-10000-4/"},{"name":"OPC Foundation — OPC UA Part 2: Security Model","url":"https://reference.opcfoundation.org/specs/OPC-10000-2/"}],"related":[{"slug":"industrial-communication-protocol-selection-guide","title":"Choosing an Industrial Communication Protocol: A Decision Guide","summary":"Pick an industrial protocol by the job it must do (cyclic control, device access, plant data, or telemetry), then match timing, data model, and security to…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/industrial-communication-protocol-selection-guide","markdown_url":"https://wiki.aspotomasyon.com/article/industrial-communication-protocol-selection-guide.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/industrial-communication-protocol-selection-guide","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1767,"image":"https://wiki.aspotomasyon.com/assets/social/industrial-communication-protocol-selection-guide-bbf4fa97587d.png"},{"slug":"asset-administration-shell-digital-twin-interoperability","title":"Asset Administration Shell: A Standard Digital Twin Container","summary":"The Asset Administration Shell gives each physical asset a standard digital container of submodels, so engineering, operations, and enterprise systems can…","category":{"slug":"digital-transformation","name":"Digital Transformation"},"url":"https://wiki.aspotomasyon.com/article/asset-administration-shell-digital-twin-interoperability","markdown_url":"https://wiki.aspotomasyon.com/article/asset-administration-shell-digital-twin-interoperability.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/asset-administration-shell-digital-twin-interoperability","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1876,"image":"https://wiki.aspotomasyon.com/assets/social/asset-administration-shell-digital-twin-interoperability-aa58402e4e17.png"},{"slug":"opc-ua-information-model-design","title":"Designing OPC UA Information Models","summary":"The OPC UA information model is what makes OPC UA far more than a data transport.","category":{"slug":"opc-solutions","name":"OPC Solutions"},"url":"https://wiki.aspotomasyon.com/article/opc-ua-information-model-design","markdown_url":"https://wiki.aspotomasyon.com/article/opc-ua-information-model-design.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/opc-ua-information-model-design","published":"2026-08-06T12:26:37+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":5,"word_count":965,"image":"https://wiki.aspotomasyon.com/assets/social/opc-ua-information-model-design-ce767593b5d6.png"},{"slug":"opc-ua-protocol-overview","title":"OPC UA Protocol Overview","summary":"OPC Unified Architecture (OPC UA) , defined by IEC 62541, is the platform-independent, service-oriented architecture for secure, reliable data exchange in…","category":{"slug":"opc-solutions","name":"OPC Solutions"},"url":"https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview","markdown_url":"https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/opc-ua-protocol-overview","published":"2026-05-12T12:47:31+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":873,"image":"https://wiki.aspotomasyon.com/assets/social/opc-ua-protocol-overview-eae98061a685.png"}],"citation":"ASP OTOMASYON. OPC UA Companion Specifications — Industry-Specific Information Models. Updated 2026-09-13. https://wiki.aspotomasyon.com/article/opc-ua-companion-specifications"}}