Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62656-1: Standardized Product Ontology Register and Transfer by Spreadsheets
✅ Standard at a Glance
IEC 62656-1:2014 is an International Standard that specifies the logical structure for a set of spreadsheets used as “data parcels” to define, transfer, and register product ontologies. Developed by IEC Technical Committee 3D (Product data definition and management), it introduces the Parcellized Ontology Model (POM) — a framework that enables machine-readable exchange of product reference dictionaries using familiar spreadsheet formats. This standard bridges the gap between complex ontology modelling languages and the practical tools used by engineers worldwide.
IEC 62656-1:2014 is an International Standard that specifies the logical structure for a set of spreadsheets used as “data parcels” to define, transfer, and register product ontologies. Developed by IEC Technical Committee 3D (Product data definition and management), it introduces the Parcellized Ontology Model (POM) — a framework that enables machine-readable exchange of product reference dictionaries using familiar spreadsheet formats. This standard bridges the gap between complex ontology modelling languages and the practical tools used by engineers worldwide.
🔌 1. The Need for Standardized Product Data Exchange
1.1 The Product Data Challenge
In the modern electrotechnical industry, product data is created, exchanged, and consumed by thousands of organizations worldwide. Manufacturers define product specifications, testing laboratories record compliance data, distributors catalog inventory, and end-users search for compatible components. Each of these stakeholders uses different software tools, data formats, and organizational vocabularies. Without a standardized framework for product ontology — the formal description of product categories, properties, data types, and relationships — data exchange becomes a manual, error-prone process that creates inefficiency across the entire supply chain.
IEC 62656-1 addresses this challenge by defining a Parcellized Ontology Model (POM) that structures product ontology information into discrete, manageable parcels that can be implemented and exchanged as spreadsheet files. The standard recognizes that while sophisticated ontology languages (such as OWL or EXPRESS) exist, the vast majority of engineering professionals work with spreadsheet tools daily. By defining the semantic rules for organizing ontology data within spreadsheets, IEC 62656-1 makes ontology-based data exchange accessible to a much wider community.
💡 Engineering Insight
The key innovation of IEC 62656-1 is its recognition that ontology models must evolve over time. Unlike static data schemas, the POM structure allows an ontology model to be modified and extended as instances of the meta-meta dictionary. This means that when new product categories or properties are needed, the ontology can be updated through the same spreadsheet-based workflow used for data entry — no specialized ontology engineering tools required. This self-describing capability is what makes IEC 62656-1 practical for real-world industrial deployment.
The key innovation of IEC 62656-1 is its recognition that ontology models must evolve over time. Unlike static data schemas, the POM structure allows an ontology model to be modified and extended as instances of the meta-meta dictionary. This means that when new product categories or properties are needed, the ontology can be updated through the same spreadsheet-based workflow used for data entry — no specialized ontology engineering tools required. This self-describing capability is what makes IEC 62656-1 practical for real-world industrial deployment.
1.2 Relationship with IEC 61360 and ISO 13584
IEC 62656-1 is closely related to two foundational standards for product data management. IEC 61360 (Standard data element types with associated classification scheme for electric items) defines the Common Data Dictionary (CDD) — a shared repository of standardized property definitions used across all electrotechnical domains. ISO 13584 (Parts Library, also known as PLIB) defines a framework for computer-interpretable representation and exchange of parts library data. IEC 62656-1 was developed as a superset or generalization of ISO 13584-35, extending it with the capability to evolve ontology models through meta-dictionary updates.
| Standard | Full Title | Role in Product Data Ecosystem | Key Contribution |
|---|---|---|---|
| IEC 61360-1 | Standard data element types — Definitions, principles and methods | Defines the semantic rules for property definitions in the CDD | Property naming conventions, data types, value domains |
| IEC 61360-2 | Standard data element types — EXPRESS dictionary schema | Defines the EXPRESS-based data model for dictionary exchange | Machine-readable dictionary schema, ISO 10303 mapping |
| IEC 62656-1 | Standardized product ontology register and transfer by spreadsheets | Defines spreadsheet-based ontology exchange using POM | Parcel structure, meta-ontology layers, CSV/XML mapping |
| ISO 13584-35 | Parts library — Methodology for schematic parts families | Defines ontology modelling methodology for parts libraries | Foundation for POM, extended by IEC 62656-1 |
🔬 2. The Parcellized Ontology Model (POM) Architecture
2.1 Core Concepts: Parcels, Dictionaries, and Libraries
The POM organizes product ontology data into three fundamental structures. A data parcel is an information structure comprising a set of properties and a set of tuples of values for those properties, aimed at describing a domain data dictionary, library, or ontological modelling concept. A dictionary parcel defines the schema — the classes, properties, and relationships that form the vocabulary of a product domain. A library parcel provides the instances — actual product data that conforms to the dictionary schema. This separation of schema and instance data is a fundamental design principle that enables flexible, extensible data exchange.
Each parcel is implemented as a set of spreadsheet sheets organized in a level-pair structure. The schema header section defines the columns and their data types, while the data section contains the actual values. This design allows any standard spreadsheet application (Microsoft Excel, LibreOffice Calc, Google Sheets) to read and write parcel data without specialized software.
2.2 The Multi-Layer Ontology Architecture
One of the most powerful features of IEC 62656-1 is its multi-layer ontology architecture, which provides four levels of abstraction:
| Layer | Name | Purpose | Example |
|---|---|---|---|
| Layer 0 | Axiomatic Ontology (AO) | Defines the fundamental building blocks: class, property, relation, term | “A class is a set of objects sharing common characteristics” |
| Layer 1 | Meta-Ontology (MO) | Defines meta-classes and meta-properties used to build domain ontologies | “dictionary class”, “supplier class”, “unit of measure class” |
| Layer 2 | Domain Ontology (DO) | Defines the classes and properties for a specific product domain | “circuit breaker”, “rated current”, “breaking capacity” |
| Layer 3 | Instance Data (ID) | Contains actual product data conforming to the domain ontology | “Manufacturer X, Type Y, Rated current = 630 A” |
💡 Engineering Insight
The multi-layer architecture is what makes IEC 62656-1 uniquely powerful compared to simple spreadsheet templates. Because the meta-ontology (Layer 1) is itself defined as instances of the axiomatic ontology (Layer 0), the entire ontology framework can evolve without breaking existing data. When a new product domain requires new property types or class structures, these can be added at Layer 1 through the standard’s meta-dictionary mechanism. All existing Layer 2 and Layer 3 data remain valid because they conform to the meta-dictionary, which is versioned and backward-compatible by design.
The multi-layer architecture is what makes IEC 62656-1 uniquely powerful compared to simple spreadsheet templates. Because the meta-ontology (Layer 1) is itself defined as instances of the axiomatic ontology (Layer 0), the entire ontology framework can evolve without breaking existing data. When a new product domain requires new property types or class structures, these can be added at Layer 1 through the standard’s meta-dictionary mechanism. All existing Layer 2 and Layer 3 data remain valid because they conform to the meta-dictionary, which is versioned and backward-compatible by design.
2.3 Mapping to EXPRESS and Other Standards
IEC 62656-1 includes a standard mapping between the meta-data of dictionary parcels in spreadsheet format and the meta-data represented in IEC 61360-2 compliant EXPRESS models. This mapping enables bidirectional conversion between the user-friendly spreadsheet representation and the machine-optimized EXPRESS representation used by the IEC Common Data Dictionary (CDD) and ISO 10303 (STEP) systems. The standard also supports CSV (Comma Separated Values) format for basic interchange and XML schema-compatible formats for more advanced applications.
⚠️ Implementation Note
While IEC 62656-1 defines the logical structure of parcels, it does not mandate a specific physical file format. Implementers must ensure that their tools correctly handle the semantic rules defined in the standard, particularly regarding data type encoding, multi-language support, and unit of measure representation. The IEC provides sample parcels and validation tools through the IEC Common Data Dictionary (CDD) portal to assist with implementation verification.
While IEC 62656-1 defines the logical structure of parcels, it does not mandate a specific physical file format. Implementers must ensure that their tools correctly handle the semantic rules defined in the standard, particularly regarding data type encoding, multi-language support, and unit of measure representation. The IEC provides sample parcels and validation tools through the IEC Common Data Dictionary (CDD) portal to assist with implementation verification.
💡 3. Practical Applications and Industry Impact
3.1 Use Cases in Electrotechnical Industry
The POM framework defined in IEC 62656-1 enables several critical use cases in the electrotechnical industry:
Reference Dictionary Management: National committees and industry consortia can define and maintain standardized product vocabularies (reference dictionaries) using spreadsheet tools, then register them in the IEC CDD. This eliminates the need for specialized ontology engineering skills in the dictionary maintenance workflow.
Manufacturer Data Exchange: Manufacturers can export their product specifications as parcels conforming to IEC 62656-1, enabling automated import by distributor catalog systems, engineering design tools, and procurement platforms. The standardized structure eliminates the need for custom data conversion for each business partner.
Regulatory Compliance Documentation: Testing laboratories and certification bodies can use parcels to define compliance criteria and record test results in a machine-readable format that can be automatically compared against product specifications.
✅ Interoperability Benefits
Organizations implementing IEC 62656-1 report significant reductions in data exchange errors (typically 60-80% fewer data mapping issues) compared to ad-hoc spreadsheet exchanges. The standardized parcel structure provides a common “contract” between data producers and consumers, reducing the need for manual data validation and correction. For engineering design tools, automated import of standardized product data can reduce component selection time by 30-50%.
Organizations implementing IEC 62656-1 report significant reductions in data exchange errors (typically 60-80% fewer data mapping issues) compared to ad-hoc spreadsheet exchanges. The standardized parcel structure provides a common “contract” between data producers and consumers, reducing the need for manual data validation and correction. For engineering design tools, automated import of standardized product data can reduce component selection time by 30-50%.
3.2 Relationship with IEC Common Data Dictionary (CDD)
The IEC Common Data Dictionary (CDD), maintained as an online database conforming to IEC 61360-4, serves as the central repository for standardized product ontology data. IEC 62656-1 provides the mechanism for importing and exporting CDD data using spreadsheet parcels. This enables organizations with limited internet connectivity or strict data sovereignty requirements to work with CDD data offline, then synchronize their changes when connectivity is available. The CDD currently contains over 60,000 standardized property definitions used across all electrotechnical domains.
💡 Engineering Insight
For engineering organizations, the practical workflow is: (1) Download the relevant domain dictionary parcels from the IEC CDD; (2) Extend them with organization-specific properties and product families using standard spreadsheet tools; (3) Populate instance data from internal product databases; (4) Validate the parcels using IEC 62656-1 compliant tools; (5) Publish the validated parcels for use by design, procurement, and maintenance systems. This workflow eliminates the traditional bottleneck of custom data mapping between different software platforms.
For engineering organizations, the practical workflow is: (1) Download the relevant domain dictionary parcels from the IEC CDD; (2) Extend them with organization-specific properties and product families using standard spreadsheet tools; (3) Populate instance data from internal product databases; (4) Validate the parcels using IEC 62656-1 compliant tools; (5) Publish the validated parcels for use by design, procurement, and maintenance systems. This workflow eliminates the traditional bottleneck of custom data mapping between different software platforms.
3.3 Future Evolution and Integration
IEC 62656-1 is designed to evolve alongside emerging data technologies. The multi-layer ontology architecture naturally supports integration with semantic web technologies (RDF, OWL, SPARQL), industrial IoT data models (such as OPC UA information models), and digital twin frameworks. The standard’s Part 31 specifically addresses interface mapping with the Common Information Model (CIM) used in power utility automation. As Industry 4.0 and digital transformation initiatives accelerate, IEC 62656-1 provides the foundational vocabulary framework that ensures product data remains interoperable across the expanding ecosystem of smart manufacturing systems.
🚨 Common Pitfall: Ignoring Version Control
A frequent implementation error is treating IEC 62656-1 parcels as static files without proper version control. Because the POM framework allows ontology evolution, different versions of a dictionary parcel may define the same property with different data types or value domains. Organizations must implement robust version management to ensure that instance data is always validated against the correct dictionary version. The IEC CDD provides built-in versioning, but local implementations must replicate this discipline.
A frequent implementation error is treating IEC 62656-1 parcels as static files without proper version control. Because the POM framework allows ontology evolution, different versions of a dictionary parcel may define the same property with different data types or value domains. Organizations must implement robust version management to ensure that instance data is always validated against the correct dictionary version. The IEC CDD provides built-in versioning, but local implementations must replicate this discipline.
❓ Frequently Asked Questions
Q1: Do I need specialized software to create IEC 62656-1 compliant parcels?
A: No — one of the key design goals of IEC 62656-1 is to enable ontology exchange using standard spreadsheet applications such as Microsoft Excel or LibreOffice Calc. The standard defines the logical structure (column headers, data types, sheet naming conventions) that must be followed. However, for validation and conversion to EXPRESS format, specialized tools are recommended. The IEC provides reference implementations and validation tools through the CDD portal. For organizations with large-scale data exchange needs, commercial PLM (Product Lifecycle Management) systems increasingly support IEC 62656-1 import/export natively.
Q2: How does IEC 62656-1 differ from simple CSV data exchange?
A: While CSV can transport tabular data, it carries no semantic information about what the data means. IEC 62656-1 parcels include not only the data values but also the complete ontology context: property definitions, data types, units of measure, value ranges, language-specific names and definitions, and class hierarchies. This means that a receiving system can automatically interpret and validate the data without human intervention or out-of-band agreements. The standard also defines how to handle multi-language content, versioning, and supplier identification — none of which are addressed by simple CSV exchange.
Q3: Is IEC 62656-1 limited to electrotechnical products?
A: While IEC 62656-1 was developed by IEC and its primary use case is electrotechnical product data, the POM framework is domain-agnostic. The axiomatic ontology (Layer 0) and meta-ontology (Layer 1) can support any product domain. The standard’s relationship with ISO 13584 (Parts Library) and ISO 10303 (STEP) means it can be applied to mechanical, hydraulic, pneumatic, and other engineering domains. Some organizations have adapted the POM framework for non-engineering applications such as medical device classification and building information modelling (BIM).
Q4: How does IEC 62656-1 handle multilingual product data?
A: The POM structure natively supports multilingual content. Each text property (such as property name, definition, and note) can be provided in multiple languages using ISO 639-1 language codes. The standard defines how language-specific text is organized within the parcel sheets, allowing a single parcel to contain definitions in English, French, German, Chinese, Japanese, and any other language. This is particularly important for IEC standards, which are published in English and French as official languages, while many products require documentation in additional local languages for regulatory compliance.
