Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN/CSA-ISO/IEC 10036-01:2026 – Data Encoding for Industrial Automation – Part 1: Framework and General Requirements
A Comprehensive Guide to the Canadian Adoption of the International Standard for Interoperable Data Exchange in Automated Manufacturing Environments
Scope and Purpose
CAN/CSA-ISO/IEC 10036-01:2026 represents the Canadian adoption of the international standard ISO/IEC 10036-1:2026, Information technology — Data encoding for industrial automation — Part 1: Framework and general requirements. This standard establishes a common framework for representing, encoding, and exchanging structured data across heterogeneous industrial automation systems, including programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA) systems, robots, and manufacturing execution systems (MES).
The primary purpose of CAN/CSA-ISO/IEC 10036-01 is to enable seamless interoperability between equipment from different vendors by defining a standardized data encoding model. It specifies the fundamental data constructs, encoding rules, and conformance requirements that serve as the foundation for subsequent parts of the series (10036-02 through 10036-10). The standard applies to all sectors that rely on automated manufacturing, such as automotive, aerospace, electronics, pharmaceuticals, and food processing, where consistent data interpretation is critical for quality control, traceability, and efficiency.
Technical Requirements
Data Encoding Model
The core of the standard is a layered data model that separates raw data representation from semantic interpretation. The model comprises three layers:
- Physical Layer – Defines the byte-level representation and alignment of data elements in a message stream.
- Logical Layer – Specifies the structure of data units, including headers, payloads, and trailers, along with field types and lengths.
- Semantic Layer – Provides the meaning of data values through mappings to external dictionaries (e.g., ISO 15926, IEC 61360).
Encoding Types and Rules
CAN/CSA-ISO/IEC 10036-01 defines several mandatory and optional encoding schemes to accommodate different performance and memory constraints. The standard requires that all implementations support at least one of the mandatory encodings. The table below summarises the primary encoding types specified in the standard.
| Encoding Type | Mandatory/Optional | Description | Typical Use Case |
|---|---|---|---|
| Compact Binary Encoded (CBE) | Mandatory | Fixed‑width field encoding with minimal overhead; uses big‑endian byte order for all integers. | Real-time control messages |
| Tagged Length Value (TLV) | Mandatory | Self‑describing encoding with a 16‑bit tag, 16‑bit length, and variable payload. | Configuration and diagnostic data |
| XML Canonical Encoding (XCE) | Optional | XML 1.0 representation consisting of elements and attributes in a canonical form defined in Annex A. | Human‑readable logs and cross‑system exchanges |
| JSON Binary Mapping (JBM) | Optional | Compact binary representation of JSON key‑value pairs using a predefined schema registry. | Cloud interfaces and web services |
Conformance Requirements
Implementations claiming conformance to CAN/CSA-ISO/IEC 10036-01 must satisfy the following technical requirements:
- Support for at least one mandatory encoding type (CBE or TLV).
- Correct implementation of the byte ordering and alignment rules as specified in Clause 7.
- Ability to encode and decode all mandatory data types (boolean, unsigned integer, signed integer, floating-point, string, and nested structure).
- Provision of an interface for registering custom tags with the registry authority defined in the standard.
- Implementation must pass the conformance test suite provided in Annex B of the standard.
Implementation Highlights
Integration with Existing Systems
Adopting CAN/CSA-ISO/IEC 10036-01 does not require a complete rewrite of existing automation software. The standard’s layered architecture allows it to operate as a middleware layer that translates proprietary data formats into a canonical encoding. Organizations can gradually migrate by introducing translation gateways or adapting controller firmware to output the standard encoding.
Testing and Validation
Before deployment, implementers should run the official conformance test suite, which includes more than 200 test cases covering edge conditions such as buffer overflows, invalid tags, and unsupported data types. The standard also recommends field validation using a reference encoder/decoder tool provided by the maintaining body.
Tip: Use the reference implementation (available in C++ and Python) to generate test vectors for your integration platform. This helps avoid interoperability surprises during commissioning.
Security Considerations
While CAN/CSA-ISO/IEC 10036-01 focuses on data encoding, it includes an informative annex on securing encoded data streams. Implementers should apply transport-layer security (TLS 1.3 or higher) when exchanging encoded messages over public or untrusted networks, and they should validate that decoders handle malformed inputs gracefully to avoid parsing vulnerabilities.
Compliance Notes
Certification Process
Certification for CAN/CSA-ISO/IEC 10036-01 is administered by the Standards Council of Canada (SCC) in partnership with the IEC Conformity Assessment Board. Manufacturers can apply for a certificate of conformance after submitting documentation and passing an independent laboratory test. The certification mark may be affixed to products that successfully meet all mandatory requirements.
Documentation Requirements
Applicants must provide a conformance statement that declares which encoding types are implemented, a description of the test environment, and a report showing results of the conformance test suite. The documentation must also include a mapping of any product‑specific data types to the standard’s built-in types.
Important: Certification to CAN/CSA-ISO/IEC 10036-01 does not imply compliance with other parts of the 10036 series (e.g., Part 2 for process data or Part 3 for geometry data). Separate certifications are required for each part that a product claims to support.
Maintenance and Updates
The standard is subject to periodic revision. The current edition (2026) supersedes the 2020 edition, which was a preliminary release. Users should verify that their implementations reference the latest version to ensure alignment with current encoding rules and registry updates.
Benefit: Early adopters of the 2026 edition gain access to the new JSON Binary Mapping (JBM) encoding, which reduces bandwidth use by up to 40% compared to plain JSON when deployed in cloud-connected automation systems.
Frequently Asked Questions
Q: Is CAN/CSA-ISO/IEC 10036-01 identical to the international ISO/IEC 10036-1:2026?
A: Yes, the Canadian adoption is technically identical to the international standard. The CAN/CSA prefix indicates its adoption by the Canadian Standards Association as a National Standard of Canada. Any national deviations or additional requirements are clearly marked in an appendix if they exist. For this standard, there are no Canadian deviations.
A: Yes, the Canadian adoption is technically identical to the international standard. The CAN/CSA prefix indicates its adoption by the Canadian Standards Association as a National Standard of Canada. Any national deviations or additional requirements are clearly marked in an appendix if they exist. For this standard, there are no Canadian deviations.
Q: Do I need to support all four encoding types to claim conformance?
A: No, conformance requires support for at least one of the two mandatory encoding types (Compact Binary Encoded or Tagged Length Value). The optional encodings (XML Canonical Encoding and JSON Binary Mapping) may be omitted. However, if a product claims to support an optional encoding, it must implement it exactly as specified in the standard.
A: No, conformance requires support for at least one of the two mandatory encoding types (Compact Binary Encoded or Tagged Length Value). The optional encodings (XML Canonical Encoding and JSON Binary Mapping) may be omitted. However, if a product claims to support an optional encoding, it must implement it exactly as specified in the standard.
Q: How does the standard handle custom or proprietary data types?
A: The standard provides a mechanism for registering custom data types through an online registry maintained by the ISO/IEC JTC 1/SC 31 committee. Registered types are assigned a unique tag (for TLV encoding) or a schema identifier (for JBM). This ensures that custom types can be recognised across different systems without conflict.
A: The standard provides a mechanism for registering custom data types through an online registry maintained by the ISO/IEC JTC 1/SC 31 committee. Registered types are assigned a unique tag (for TLV encoding) or a schema identifier (for JBM). This ensures that custom types can be recognised across different systems without conflict.
© 2026 – CAN/CSA-ISO/IEC 10036-01:2026 Article. This content is for informational purposes and does not replace the official standard text.