Working magic with data and strengthening competitiveness - tips for providing data to retail partners, customers and portals

In our networked world, it is essential to be able to provide product data digitally. To retail partners, customers and portals (in addition to our own online output channels such as websites and stores). In this context, certain classifications and formats play an important role. Without structured data, there is no e-commerce. Or to put it in a nutshell: no good e-commerce without "clean" data.

Clean data in the company's own language

Fitting, valve or tap? Which term is used is not really that important. It is more important that terms are used consciously and consistently. Although standards can help in finding the right terminology, in my opinion, the company itself is the guideline for terminology.

From my practical experience, I can make the following recommendations on the subject of data quality ("clean" data):

• Maintain numbers as numerical values rather than text, for example to enable calculations and conversions to imperial values.
• Maintain compound numerical values granularly, for example units. Maintain from-to and min-max values separately, for example to enable any concatenations.
• Wherever possible, use value lists for selection to improve consistency.
• Mark language-neutral texts as such to avoid translation work.
• Classify attributes, e.g. ERP data, mechanical data, electrical data, approvals, etc., to improve the overview.
• Define data sovereignty and synchronize other data sources (ERP, PDM or similar) to avoid redundancies and thus inconsistencies.

Standardization of product data

As already mentioned, each company should decide for itself how it names products and product properties - the main thing is to be consistent! However, standardized classifications are required for the provision of data to partners and customers. This makes it easier for customers and partners to find and compare products.

Very different standard classifications and versions are required. Two classifications play a major role here: ECLASS and ETIM. ECLASS is now available in version 15 and ETIM in version 10. Which of the classification systems is used, or even whether both are used, depends on the (industry-specific) requirements. In principle, however, you should start with one classification version, after which any further classification will be much easier.

In my opinion, it is essential to familiarize yourself with ECLASS and ETIM. The freestyle are the latest developments: ECLASS Advanced and ETIM MC. ECLASS Advanced and ETIM MC are more sophisticated and also meet engineering, construction and BIM (Building Information Modeling) requirements.

Classification mapping

ECLASS and ETIM use a standardized, standardized language, which naturally differs from the corporate language. Mapping is therefore necessary. On the one hand, the products must be mapped into the correct groups of the classification and on the other hand, the characteristics must be mapped, for example

• a specific fitting product to the ECLASS group "Shut-off valve" with the number 37.01.02.01
• the length feature to the ECLASS feature "Installation length of the valve" with the number BAI514005

Feature mapping in particular is very complex and requires the above-mentioned "clean" data. There are also good service providers who can help to make quick progress here.

If the mapping has been created satisfactorily, then you can really work your magic and fulfill the wishes of partners and customers at the touch of a button - and thus rise in the supplier ranking.

Export formats for data provision

Let's move on to the exports themselves, we are talking about e-catalogs, which are ultimately made available to customers and partners. There are also very different formats and versions for e-catalogs. In my opinion, Excel, BMEcat (in versions 1.2 and 2005) and Json are mandatory.
Incidentally, if a direct connection is possible, this should be used. However, this is rarely possible in exchanges with customers and partners.

In step 2, the use of other formats can be checked, for example ARGE Neue Medien (BDMG), OXOMI, AUSSCHREIBEN.DE (GAEB), BIM (e.g. IFC), FAB-DIS, nexmart, Datanorm/Eldanorm.

It should also be possible to play out the standard classification, for example ECLASS or ETIM, in the selected format. The mapping mentioned above must be taken into account. In addition, images, documents, videos and texts are exported in the selected language. Customers and partners can then use this data to create their own stores or catalogs or feed their purchasing system.

The latest developments are the icing on the cake: AAS (Asset Administration Shell) and, in future, DPP (Digital Product Pass). If you have completed the mandatory program described so far, you will find it easy to do so here.

Conclusion

Even if everything changes and evolves - the product data itself, classifications and formats - the principles and methodology remain the same: manage product data cleanly in a PIM system, define data sovereignty, standardize terms across the company, perform mapping to standard classifications such as ECLASS and ETIM, provide standard formats such as Excel, BMEcat and Json. Once you have mastered the methodology, you are ready for new requirements such as the digital product passport.