Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TS 29002-20: Industrial Automation Systems — Data Exchange Specification
Technical specification for standardized data exchange of industrial component information across heterogeneous systems
ISO/TS 29002-20 is a Technical Specification that defines the data exchange mechanisms for industrial automation systems component information. While Part 10 of the series establishes the abstract data model, Part 20 specifies how instances of that model are serialized, transmitted, and validated across system boundaries. This standard is critical for achieving practical interoperability between engineering tools, procurement systems, and manufacturing platforms. Organizations implementing ISO/TS 29002-20 can realize significant reductions in integration cost and data translation errors compared to custom point-to-point data mapping approaches.
The data exchange specification in ISO/TS 29002-20 is designed to support multiple exchange paradigms, including file-based exchange (using STEP physical files), web services (SOAP and REST), and message-based integration (using XML messaging patterns).
1. Exchange Formats and Serialization
ISO/TS 29002-20 defines two primary exchange formats: the STEP physical file format (ISO 10303-21) and the XML Schema-based format (ISO/TS 29002-20 XML). The STEP physical file format is compact and efficient for batch processing of large parts libraries, while the XML format provides better integration with modern web-based systems and supports validation through XML Schema (XSD) and Schematron rules.
Each exchange format supports the full range of data model constructs defined in Part 10, including item classes, properties, property values, constraints, and classification hierarchies. The standard also defines a minimum content profile that ensures basic interoperability: any conformant system must be able to process at least the minimum content profile, which includes item class identification, a basic set of properties with values, and classification information.
When designing data exchange workflows, be aware that the STEP physical file format uses a fixed-width text encoding that does not natively support Unicode. For multilingual applications, the XML format is strongly recommended to ensure proper handling of non-Latin character sets (CJK, Cyrillic, Arabic, etc.).
2. Protocol Bindings and Communication Patterns
The standard specifies protocol bindings for several communication patterns commonly encountered in industrial automation environments. The following table summarizes the key bindings and their recommended use cases:
| Binding Type | Transport Protocol | Recommended Use Case |
|---|---|---|
| File Exchange | File system, FTP, SFTP | Batch import/export of parts libraries, offline data synchronization |
| SOAP Web Service | HTTP/S, SOAP 1.2 | Enterprise application integration with transactional guarantees |
| RESTful API | HTTP/S, JSON/XML | Lightweight integration for web and mobile applications |
| Message Queue | AMQP, MQTT, JMS | Event-driven data synchronization across distributed systems |
| OData Protocol | HTTP/S, OData v4 | Data query and discovery for analytics and reporting tools |
For transactional integrity, the SOAP binding supports WS-ReliableMessaging and WS-AtomicTransaction, ensuring that complex multi-step data exchanges (such as updating a component catalog with hundreds of items) are treated as atomic operations. The RESTful binding, while lighter weight, relies on standard HTTP status codes and ETag-based concurrency control for conflict detection.
The RESTful API binding described in ISO/TS 29002-20 follows the OpenAPI Specification (OAS) structure, making it straightforward to generate client SDKs and API documentation using standard OpenAPI tooling such as Swagger Editor and AutoRest.
3. Validation and Conformance Testing
ISO/TS 29002-20 places strong emphasis on data validation and conformance testing. The standard defines a conformance class structure that categorizes implementation capabilities into levels: Class 1 (basic data read/write), Class 2 (full data model with constraints), Class 3 (advanced features including complex property dependencies and cross-references). Each conformance class specifies mandatory and optional capabilities, along with test cases that implementers must pass to claim conformance.
Validation is performed at multiple levels: syntactic validation checks that the exchange file or message conforms to the specified schema (STEP physical file structure or XSD); semantic validation verifies that the data content adheres to the dictionary definitions and constraints specified in the data model; and business rule validation ensures that the data satisfies domain-specific rules defined by the exchanging parties.
One of the most common integration failures occurs when systems exchange valid syntactic data that violates implicit semantic rules. For example, a pressure rating value of “10000” may be syntactically valid, but if the unit of measure is inconsistently interpreted as psi versus kPa between systems, the result can be catastrophic. Always include explicit unit references in every exchange.
Performance considerations are also addressed in the standard. For large-scale data exchanges involving thousands of components, the STEP physical file format offers superior performance due to its compact token-based encoding, while the XML format provides better readability and self-description at the cost of larger payload sizes. Implementers should select the exchange format based on the specific requirements of each use case, considering factors such as data volume, network bandwidth, processing capacity, and the need for human readability during debugging. A common pattern is to use STEP files for bulk data synchronization during off-peak hours and XML or REST APIs for real-time queries and small updates during normal operations.
4. FAQs
Q: What is the relationship between ISO/TS 29002-20 and the STEP Application Protocols (APs)?
A: ISO/TS 29002-20 provides a lightweight data exchange mechanism that complements the full STEP Application Protocols (such as AP 242 for managed model-based 3D engineering). While STEP APs handle complete product model data including geometry, ISO/TS 29002-20 focuses specifically on component library data and classification.
Q: Can ISO/TS 29002-20 be used for real-time data exchange in manufacturing?
A: The standard is primarily designed for business-to-business exchange of component master data, which is typically not time-critical. For real-time manufacturing data exchange, other standards such as OPC UA or MQTT are more appropriate. However, the ISO/TS 29002-20 message queue binding can support near-real-time synchronization scenarios.
Q: How is data security addressed in ISO/TS 29002-20 exchanges?
A: The standard does not define built-in security mechanisms but recommends using transport-layer security (TLS 1.2 or higher) for all network-based exchanges. For file-based exchanges, the standard recommends file-level encryption (AES-256) and digital signatures for integrity verification.
Q: Does ISO/TS 29002-20 support delta or incremental updates?
A: Yes. The standard defines an update mechanism that allows systems to exchange only the differences (delta) since the last synchronization. This is achieved through timestamps, version numbering, and a change-tracking construct in the data model that records modification history.
