Solutions · ETIM
Derive ETIM features from product data
Technical details are scattered across descriptions, tables and individual data fields. In an ETIM pilot for your product data, we assess a selected set to identify which details can be transferred to the appropriate ETIM features and values. The result is reviewed by specialists and delivered in the agreed format.
Before making an offer, we assess the source data, ETIM version, desired scope and output format.
- Description
- Feature
- Product information
- Value / unit
- Open issues
- Review and approval
Supported product information Approval Output
Technical details are scattered across descriptions, tables and individual data fields. In an ETIM pilot for your product data, we assess a selected set to identify which details can be transferred to the appropriate ETIM features and values. The result is reviewed by specialists and delivered in the agreed format.
Typical starting point
Source data
- technical values are scattered across many source fields
- names and units are inconsistent
- relevant details appear only in short or long descriptions
Mapping and rules
- existing attributes need mapping to ETIM features
- values need normalisation and expert review
Target and handover
- the target class is known, but feature coverage is unclear
What is assessed in the pilot
Supported product information
- source field suitability and mapping
- available evidence for feature values
Processing
- normalisation of units and notation
- generation of selected feature proposals
Review and approval
- identification of uncertainty and missing evidence
- expert review and explicit approval
Output
- export of approved results in the agreed format
Why classes and features are considered separately
Class assignment determines which ETIM class a product belongs to. Feature derivation converts technical information into the features and values defined for that class. The two steps may be connected, but they have different data requirements and error patterns.
Clarify the available data before enrichment
If data coverage, field structure or product range boundaries have not yet been clarified, the ETIM readiness analysis should come first.
Limits
Agreed limits
- no guaranteed completeness or match rate
- no invention of missing product information
- no approval without sufficient evidence
- price and delivery time are agreed individually
- translation, editorial maintenance and system integration only by separate agreement
FAQ
Are missing feature values added automatically?
We derive feature suggestions from reliable information in your existing product data. If the evidence is missing, the value remains open; missing facts are not invented.
Can units be normalised?
This can be part of an agreed pilot. Permitted units and conversions are defined in the scope and checked.
Does the ETIM class need to be known already?
Not always. If class assignment and feature derivation are to be assessed together, this must be explicitly included in the pilot scope.
Solutions · ETIM
Define your task
Before making an offer, we assess the source data, ETIM version, desired scope and output format.