Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62016: Core Model of the Electronics Domain
Understanding the EXPRESS-Based Information Model for Electronic CAD Interoperability
IEC 62016, first published in 2003, establishes the Core Model of the electronics domain — a formal information model that defines common semantics for electronic design data handled by computer-aided design (CAD) systems. The standard uses the EXPRESS language (ISO 10303-11) to describe concepts, attributes, relationships, and constraints that any compliant CAD system should recognize.
The Core Model is not an implementation specification or a physical data format. Rather, it is a conceptual representation that ensures CAD systems share a common understanding of fundamental electronics design concepts, enabling smoother inter-communication, data sharing, and exchange.
Architecture of the Core Model
The Core Model is organized into 10 EXPRESS schemas, each addressing a distinct category of electronic design information. These schemas collectively describe hierarchy, connectivity, design configuration, properties, and naming within electronic circuits.
| Schema | Category | Description |
|---|---|---|
| hierarchy_model | Hierarchy | Describes how cells are divided into sub-cells, forming a hierarchical structure |
| design_hierarchy_model | Design Configuration | Annotates occurrence hierarchy with view selection and design-specific data |
| connectivity_view_model | Connectivity | Defines how circuits connect for information or energy flow |
| logical_connectivity_model | Logical Connectivity | Describes bit-level abstract electrical connectivity within hierarchy levels |
| instance_model | Instantiation | Handles cell instances and their configuration within a design |
| global_port_model | Port Abstraction | Defines global ports and port bundles for cross-boundary connections |
| property_model | Properties | Handles named property-value pairs attached to design objects |
| property_override_model | Property Override | Manages property value overrides across hierarchy levels |
| name_model | Naming | Provides naming conventions and name resolution for design objects |
| library_model | Library | Defines library structures for organizing reusable design cells |
By standardizing these 10 information categories, IEC 62016 provides a solid foundation for EDA tool interoperability. Any two compliant tools can understand the same hierarchical connectivity, property annotations, and design configuration without ambiguity.
Hierarchy and Connectivity Modeling
The hierarchy_model schema captures how a circuit may be decomposed into cells, which can be further subdivided. This creates a tree-like structure where each cell may have multiple representations (e.g., behavioral, structural, physical). The design_hierarchy_model extends this by selecting specific views to form a configured design hierarchy — analogous to VHDL configuration mechanisms.
Connectivity is modeled at multiple abstraction levels. The logical_connectivity_model describes connectivity at the bit level, specifying how signals travel between ports within the same hierarchical level. The connectivity_view_model provides a higher-level view, bundling related signals into buses and handling fan-out, commoning, and slicing operations.
A critical design consideration: the Core Model separates logical connectivity from physical connectivity. This separation allows designers to verify logical correctness before committing to physical implementation — a key principle in modern digital design workflows.
Practical Applications and Engineering Insights
From an engineering perspective, IEC 62016’s Core Model has several important implications for EDA tool developers and system integrators:
1. Tool Interoperability. When two EDA tools claim compliance with the Core Model, they share a common semantic foundation. This eliminates the need for point-to-point translators and reduces integration costs. A netlist generated by a synthesis tool can be directly consumed by a placement-and-routing tool without semantic loss.
2. Design Reuse. The library_model and instance_model schemas provide formal mechanisms for packaging and instantiating reusable IP blocks. Libraries store cell definitions, while instances capture their usage context including parameter overrides via the property_override_model.
3. Design Configuration Management. The design_hierarchy_model enables tracking of which views and configurations were used in a particular design. This is essential for regression testing, ECO (Engineering Change Order) management, and version tracking across design iterations.
| Design Concept | Core Model Representation | EXPRESS Entity |
|---|---|---|
| Cell | A functional block in the hierarchy | cell |
| Port | Connection point of a cell | port |
| Net | Electrical connection between ports | net |
| Bus | Grouped collection of nets | bus |
| Instance | Usage of a cell within a parent cell | instance |
| Property | Named attribute attached to any object | property |
| Library | Container for reusable cell definitions | library |
One limitation engineers should be aware of: the 2003 edition of IEC 62016 has a stability date of 2012-07, after which it was due for reconfirmation, withdrawal, or revision. Always check the current status before building long-term compliance strategies around this standard.
Frequently Asked Questions
This standard provides essential guidance for EDA interoperability.
The Core Model remains an important reference for understanding the foundational concepts of EDA data interoperability. Its influence can be seen in subsequent standards and in the architecture of modern electronic design automation platforms.
The Core Model’s approach to design information modeling has influenced subsequent standards in the ECA ecosystem. Its EXPRESS-based schema definitions provide a formal foundation that can be extended for domain-specific applications. For example, the separation of logical and physical connectivity foreshadowed the rise of electronic system-level (ESL) design methodologies, where abstract functional models are refined into implementation-specific representations through successive transformations. Engineers working with modern high-level synthesis flows will recognize these concepts in the分层 refinement steps of today’s ESL tools.
Q: What is the relationship between IEC 62016 and EDIF?
A: IEC 62016’s Core Model was created partly by enhancing the EDIF CFI DR Alignment Model Version 1.0. While EDIF focuses on netlist exchange format, the Core Model provides a broader conceptual framework for design information.
A: IEC 62016’s Core Model was created partly by enhancing the EDIF CFI DR Alignment Model Version 1.0. While EDIF focuses on netlist exchange format, the Core Model provides a broader conceptual framework for design information.
Q: Is IEC 62016 still relevant for modern EDA tools?
A: The Core Model concepts remain foundational, but modern tools have evolved significantly since 2003. The standard’s value lies in its conceptual framework rather than as a direct implementation specification. Many of its concepts have been absorbed into newer standards and proprietary tool interfaces.
A: The Core Model concepts remain foundational, but modern tools have evolved significantly since 2003. The standard’s value lies in its conceptual framework rather than as a direct implementation specification. Many of its concepts have been absorbed into newer standards and proprietary tool interfaces.
Q: Which programming language is used to express the Core Model?
A: The Core Model is expressed in EXPRESS (ISO 10303-11), which is a formal information modeling language designed for defining data specifications. It is not an implementation language but rather a conceptual modeling language.
A: The Core Model is expressed in EXPRESS (ISO 10303-11), which is a formal information modeling language designed for defining data specifications. It is not an implementation language but rather a conceptual modeling language.
Q: Can IEC 62016 be used for PCB design data?
A: The 2003 edition primarily focuses on connectivity, hierarchy, and design information for the electronics domain. The standard mentions that future parts may extend to PCB domain and schematic representation, but these extensions were not included in Edition 1.0.
A: The 2003 edition primarily focuses on connectivity, hierarchy, and design information for the electronics domain. The standard mentions that future parts may extend to PCB domain and schematic representation, but these extensions were not included in Edition 1.0.
