Electro-Technical Information Model (ETIM) is a classification structure, and a description standard, used to standardize the electronic exchange of product data for electrical and electronic products, and to enable the electronic trading of these products. The standard is designed to meet the requirements of the electrical industry and allows for a uniform technical description of electrical goods and their assignment to a class of products. To support customers who need to work with data using the ETIM standard, the inbound data exchange functionality includes ETIM formats that allow for easy processing and setup of ETIM classifications and their related data elements. For more information on ETIM, search the web.
ETIM Static vs. Dynamic Versions in STEP
STEP supports both ETIM static and dynamic versions, allowing you to choose the approach that best fits your needs. The key difference lies in how classification data is published, updated, and maintained over time.
ETIM Static Version
-
Fixed dataset: A static version represents a snapshot of the ETIM classification model at a specific point in time (for example, ETIM 8.0, ETIM 9.0).
-
Versioned release: Changes (like new classes or attributes) are released only in the next official version.
-
Predictable updates: Users know exactly when new data or changes will be released (for example, every 2–3 years).
-
Stable environment: Suitable for environments where stability and controlled updates are required.
For example: If a class or attribute is modified, it will only appear in the next version, such as ETIM 10.0.
ETIM Dynamic Version
-
Continuously updated dataset: A dynamic version is updated incrementally as soon as changes are approved by ETIM.
-
Live sync: Users always work with the latest approved classification data without waiting for a major release.
-
Faster innovation adoption: Suitable for businesses that want to adopt classification updates as soon as they are available.
-
Frequent changes: Requires systems and processes that can handle ongoing updates.
For example: If a new attribute is approved today, it will appear in the dynamic version immediately, without waiting for a formal release.
The ETIM Industry Standards Package commercial license must be enabled on your system to use this functionality. Contact Stibo Systems to begin the process of enabling a license or licenses for your system.
ETIM Import Methods
ETIM files can be imported into the system in two ways:
-
Automated API-based approach: This method uses the ETIM Taxonomy API Importer, which allows users to integrate ETIM taxonomies across multiple languages and select specific versions and Article Groups during the import process. Users can schedule automatic imports, ensuring a consistent update process. More information about this import method is explained in the ETIM Taxonomy API Importer topic.
-
Manual file-based approach: This method involves manually downloading an ETIM file from the ETIM server and then executing the import into the system using Import Managers or IIEP, like other import processes. More information about this import method and the configurations required to use this method is available in the ETIM File-based Import topic.
Key differences
The table below depicts the differences between the API-based and file-based imports.
| API-based import | File-based import | |
|---|---|---|
|
Supported versions |
ETIM versions 4, 5, 6, 7, 8, 9, 10, and Dynamic. |
ETIM versions 6, 7, 8, 9, 10, and Dynamic. |
|
Language support |
Mapping_LOV_IndustryStandard |
Languages are provided by the regional offices as independent files. |
|
Can be automated? |
Yes, using standard STEP process scheduling |
No |
|
Are attributes specific? |
No |
Configurable |
|
Supports dynamic |
Yes – separately prefixed as a standalone solution. |
Yes |
|
Support FVALUE Details |
Yes |
Yes
|
Note: For users implementing API-based approach: ETIM Dynamic version is completely separated from the ETIM Static versions. Classifications and attributes created for specific ETIM versions cannot be used in dynamic ETIM versions, and vice versa. However, LOVs and units are shared in both dynamic and specific versions. ETIM Dynamic objects are prefixed with ETIMD.