Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 13870-04:2023 – Data Semantic Models for Industrial Internet of Things: Technical Requirements and Compliance Guide
Understanding the CAN/CSA adoption of ISO/IEC 13870-04 for interoperable IIoT data representation
The international standard IEC 13870-04:2023, adopted in Canada as CAN/CSA-ISO/IEC 13870-04:2023, defines a comprehensive framework for data semantic models in Industrial Internet of Things (IIoT) environments. This fourth part of the IEC 13870 series provides a structured approach to representing device capabilities, data attributes, and communication semantics to ensure seamless interoperability across heterogeneous IIoT systems. This article examines the scope, technical requirements, implementation practices, and compliance procedures established by the standard.
Scope and Purpose
IEC 13870-04 specifies the syntax, semantics, and metadata required to describe IIoT device data points in a platform-independent manner. It applies to any IIoT system involving sensors, actuators, controllers, and gateways that need to exchange structured information. The standard primarily targets equipment manufacturers, system integrators, and software developers who must ensure consistent data interpretation across multiple domains such as manufacturing, energy, and logistics.
The document is part of a series that addresses interoperability at different layers: IEC 13870-01 covers the overall architecture, IEC 13870-02 deals with network protocols, IEC 13870-03 specifies security profiles, and this part (04) focuses on the semantic data model. It is aligned with the broader ISO/IEC 13870 series, which originated from joint work between IEC TC 65 (Industrial-process measurement, control and automation) and ISO/IEC JTC 1/SC 41 (Internet of Things and related technologies).
Technical Requirements
Data Semantic Model Structure
The core of IEC 13870-04 is a formal ontology expressed in both RDF/OWL and JSON-LD. Every device must expose at least one DataPoint object, which contains:
- DeviceID – Globally unique identifier (e.g., urn:uuid:…)
- DataPointType – Enumeration: Measurement, Status, Command, Event
- Value – The current value (with atomic data type)
- Timestamp – UTC timestamp of the last value change
- Metadata – Optional extensions including unit, quality flags, and contextual annotations
The standard mandates that the DataPoint object be serialized using JSON-LD in both request and response payloads for RESTful interfaces and in the application layer of MQTT messages. Additional serializations (XML, Protobuf) are permitted if they preserve the semantic meaning defined by the ontology.
Mandatory and Optional Attributes
IEC 13870-04 defines three categories of attributes: Mandatory, Conditional, and Optional. The following table summarizes key attributes and their requirements:
| Attribute | Requirement | Description |
|---|---|---|
| DeviceID | Mandatory | Globally unique IRI; must be resolvable to the device’s semantic model |
| DataPointType | Mandatory | One of: Measurement, Status, Command, Event |
| UnitOfMeasure | Conditional | Required when DataPointType = Measurement; uses UCUM notation |
| Timestamp | Mandatory | UTC ISO 8601 with microsecond precision |
| QualityFlag | Optional | Indicates data quality (good, uncertain, bad) per OPC UA Part 8 |
| ContextURI | Conditional | Required when the DataPoint belongs to a process context (e.g., batch, line) |
Each mandatory attribute must be present in every DataPoint instance. Conditional attributes are required based on the value of the DataPointType or other attributes. The standard also defines minimum cardinality for attributes in REST API responses and MQTT topic messages.
When implementing the semantic model, reuse standard ontologies such as those from IEC 61360 (CDD) or the NIST Ontology for Manufacturing (OEM) to maximize interoperability. The @context field in JSON-LD must reference a public URI maintained by the certification body.
Implementation Highlights
Implementers of IEC 13870-04 must support at least one transport protocol that is defined in IEC 13870-02, such as MQTT 5.0 or AMQP 1.0. The semantic model is carried as JSON-LD in the payload. The standard provides detailed mapping rules for common Industrial protocols with their own type systems:
- OPC UA: Mapping IEC 13870-04 DataPoints to OPC UA Variable nodes using the OPC UA Companion Specification for IIoT Semantics.
- Modbus: The model must be proxied through a gateway that publishes JSON-LD to a broker.
- HART-IP: Extension via HART field device specification (FDS) that wraps the DataPoint struct.
The standard requires that each device provide a semantic registry document (JSON file) accessible via the DeviceID endpoint. This document lists all DataPoints with their respective attributes and serves as the base for run-time syntactic validation.
Ensure that device certificates meet the cryptographic requirements specified in IEC 13870-03 (Annex A). Failure to validate the identity of the publishing device can lead to spurious data being accepted by subscribers. All semantic registries must be signed using the device’s private key.
Furthermore, the standard defines a conformance test suite that includes:
- A static test that verifies the structure of the semantic registry (JSON Schema validation).
- A dynamic test that checks the consistency of published data points against their expected types and ranges (reasoning engine).
- An interoperability test with a reference subscriber to confirm data round-tripping.
Compliance Notes
IEC 13870-04 compliance is achieved through self-declaration or third-party certification by an accredited testing laboratory. The process includes:
- Submission of the device’s semantic registry and sample data stream.
- Execution of the conformance test suite (static and dynamic tests) by the testing body.
- Documentation review of the device’s security implementation per IEC 13870-03.
- Issue of an IECQ (IEC Quality Assessment System) certificate for the product model.
All compliant devices must display the IEC 13870-04 compliance marking on their physical label and include the claim in their MQTT connection CONNACK packet. The certification body maintains a public registry of compliant hardware and software implementations.
Implementations that pass the conformance test suite receive the IECQ Mark, which significantly reduces integration risk for end users. The certification is valid for three years, with annual surveillance audits required for active product lines.
It is important to note that national adoptions such as CAN/CSA-ISO/IEC 13870-04 may include additional requirements or deviations specific to Canadian regulations. For instance, the Canadian version requires that the DeviceID incorporate the registered RTM (Radio Type Marker) for wireless devices. Always consult the local adoption document for any such annexes.
Frequently Asked Questions
Q: Is IEC 13870-04 mandatory for all IIoT devices sold in Canada?
A: The Canadian version (CAN/CSA-ISO/IEC 13870-04) is a nationally adopted standard that is referenced in several procurement guidelines, but it is not yet a mandatory technical regulation. However, many large integrators require compliance for projects involving federal or provincial infrastructure. We recommend early adoption to ensure market readiness.
A: The Canadian version (CAN/CSA-ISO/IEC 13870-04) is a nationally adopted standard that is referenced in several procurement guidelines, but it is not yet a mandatory technical regulation. However, many large integrators require compliance for projects involving federal or provincial infrastructure. We recommend early adoption to ensure market readiness.
Q: Can I use an existing data model like OPC UA’s DA model to satisfy IEC 13870-04?
A: Yes, as long as the model can be expressed as JSON-LD following the mandatory attributes and the @context mapping defined in the standard. The IEC 13870-04 Companion Specification for OPC UA provides guidelines for translating OPC UA variable structures into DataPoint objects. Direct use of OPC UA binary encoding is not considered compliant unless the gateway also publishes a JSON-LD proxy version.
A: Yes, as long as the model can be expressed as JSON-LD following the mandatory attributes and the @context mapping defined in the standard. The IEC 13870-04 Companion Specification for OPC UA provides guidelines for translating OPC UA variable structures into DataPoint objects. Direct use of OPC UA binary encoding is not considered compliant unless the gateway also publishes a JSON-LD proxy version.
Q: How often must I update the semantic registry document?
A: The semantic registry must be updated whenever the data point set changes (e.g., firmware update that adds new sensors). The registry must be made available at the DeviceID endpoint within 30 seconds of the device coming online. The standard strongly recommends that devices include a version identifier in the registry (via the
A: The semantic registry must be updated whenever the data point set changes (e.g., firmware update that adds new sensors). The registry must be made available at the DeviceID endpoint within 30 seconds of the device coming online. The standard strongly recommends that devices include a version identifier in the registry (via the
modelVersion attribute) to allow subscribers to detect changes. Article written for informational purposes. The referenced standard IEC 13870-04:2023 and its Canadian adoption CAN/CSA-ISO/IEC 13870-04 are maintained by the International Electrotechnical Commission and the Standards Council of Canada, respectively. Users should consult the official published documents for full normative requirements.
© 2026 IEC/ISO Technical Article Series