Release Update Support

Process of editing mappings between ECLASS Releases

There are generally three forms of mapping in ECLASS. There are mappings between...

  • two ECLASS versions
  • Basic and Advanced
  • ECLASS and other standards

The following guide explains the process of editing mappings between ECLASS Releases. The reason to write such a guide is the following: It is not uncommon for CCs to be split into two successor CCs during the release process. However, the user may subsequently request that a CC has to be split into more than two classes, which was not part of the original change request. It is therefore necessary to identify a method for making subsequent adjustments to the mappings.

Example case: Split CC

As illustrated in the attached screenshot, the CC “27-14-11-20 Feed-through terminal block” was initially split into two successor CCs, which are “27-25-01-01 Feed-through terminal” and “27-25- 01-02 multi-level terminal block”. The two CCs “27-25-01-18 Potential distribution block” and “27- ECLASS Guide 30: Mapping Plan between Releases Version: 1.0 Date: 28.11.2024 4 25-01-19 Potential distribution terminal” have been newly created. However, the two classes also originate from source 27-14-11-20. The missing mapping information should now be able to be added to the mapping afterwards. Going forward, the ability to correct or adjust mappings between releases will be a key functionality.

Other examples:

  • User removes a Property from a Class and adds a new Property to the Class instead of requesting a CR of type “Replace Property”
  • The replace information is missing and needs to be added to the mapping afterwards)

Other reasons for editing mappings:

  • External standards
  • Corrections between Basic and Advanced

DOWNLOAD

X

Wir benötigen Ihre Zustimmung

Diese Website verwendet notwendige Cookies zur Sicherstellung des Betriebs der Website. Eine Analyse des Nutzerverhaltens durch Dritte findet nicht statt. Detaillierte Informationen über den Einsatz von Cookies finden Sie in unserer Datenschutzerklärung.