Classification Class

The template for CR concerning classification classes. Examples are marked yellow in the template.

NEW CC

NEW CC = A new CC shall be created.

Mandatory fields:

CR type NEW CC
id_cc_internal If creating a new CC, insert a unique ID, e.g. YOURNAME_NEW_CC_01
class coded name 8-digit ECLASS identifier
preferred name EN Name of the new Class (See naming rules)
definition EN Definition of the new class (See naming rules)
CR Proposer Your name
Reason for request Your reason for the change

EDIT CC

EDIT CC = changing an existing CC

Mandatory fields: CR type EDIT CC id_cc_existing the 6-digit identifier of the existing CC previous coded name the current class coded name (current release) class coded name 8-digit ECLASS identifier preferred name EN the old attribute you want to change and the corresponding attribute “…new” with your proposed change, e.g. preferred name EN and preferred name EN new CR Proposer Your name Reason for request Your reason for the change

MOVE CC

(only valid for major release!)

 

MOVE CC = A CC shall be moved, i.e. will get a new class coded name

Mandatory fields: CR type MOVE CC id_cc_existing the 6-digit identifier of the existing CC class coded name your proposed new class coded name (future release) preferred name EN the name of the moved class CR Proposer Your name Reason for request Your reason for the change


NOTE: This structural change is only allowed on the 4th level, i.e. only a class on the 4th level can be moved to a different spot in the hierarchy on the 4th level. Thereby a predecessor-successor-relation is documented for product classes (4th level). In case of a CC on the 2nd or 3rd level, the old CC has to be deleted (see DELETE CC) and a new CC has to be created (see NEW CC). The DELETE CC of a CC on 3rd or 2nd level is only possible, if all its subordinate (child-) CCs on the 4th level have been moved/joined/split and a successor-CC is thereby documented. NOTE: This requests changes only the CC’s coded name. The id_cc_existing, the preferred name, definition and all its relations to keywords and properties stay the same. In case a CC is moved into another segment, the aspect (segment-specific basic properties) of the source segment will be replaced by the aspect of the target segment.

SPLIT CC

(only valid for major release!)

 

SPLIT CC = A CC shall be split into at least two classes (existing or new classes)

Mandatory fields: CR type SPLIT CC id_cc_existing the 6-digit identifier of the existing CC (to be split, source) previous coded name the current class coded name (current release) previous preferred name EN the name of the split class

class coded name the target class coded name (in future release) preferred name EN the name of the target class CR Proposer Your name Reason for request Your reason for the change

NOTE: SPLIT CC does always have to include more than one line, i.e. there have to be at least two lines with the same previous coded name and two different (new) class coded names. The original class will be automatically deleted, as the content is represented in at least two other classes. No separate CR DELETE CC has to be created by the requestor. NOTE: This structural change is only allowed for source classes and target classes on the 4th level, i.e. only a class on the 4th level can be split only into classes on the 4th level. Thereby a predecessor-successor-relation is documented for product classes (4th level). NOTE: If a SPLIT CC is combined with NEW CC-changes, additional lines have to be filled out to create the new classes in which the old class will be split into.

Example (see screenshot below): 19010202 shall be split into new classes 19010203 and 19010204. Four lines have to be filled out: NEW CC 19010203 (line 2), NEW CC 19010204 (line 3), SPLIT CC 19010202 into 19010203 (line 7), SPLIT CC 19010202 into 19010204 (line 8). The CR for DELETE CC for 19010202 will be done automatically in the name of the same requestor.

JOIN CC

(only valid for major release!)

 

JOIN CC = More than one existing CC shall be joined/merged in one new or existing CC

Mandatory fields: CR type JOIN CC id_cc_existing the 6-digit identifier of the existing CC (to be joined in the target) previous coded name The source; the current class coded name (current release) previous preferred name EN the name of the source class that is to be joined class coded name the target class coded name (will be part of future release) preferred name EN the name of the remaining target class (new or existing) CR Proposer Your name Reason for request Your reason for the change

NOTE: JOIN CC can be done into an existing CC or a new CC (as target class), in which at least one other CC is joined (source class). The source class(es) will be automatically deleted. NOTE: This structural change is only allowed for source classes and target classes on the 4th level, i.e. only classes on the 4th level can be joined only on the 4th level. Thereby a predecessor-successor-relation is documented for product classes (4th level). NOTE: A JOIN CC can be combined with a NEW CC-change as target class. I.e. in case of creating a new class an additional line has to be filled out to create the new class in which the existing source classes will be joined into.

Example 1 (see screenshot): 19010201 shall be joined in new class 19010204. Two lines have to be filled out: NEW CC 19010204 (line 3) and JOIN CC 19010201 in 19010204 (line 6). The CR for DELETE CC 19010201 will be done automatically in the name of the same requestor.


Example 2: 19010101 and 19010102 shall be joined in existing class 19010101. Only one line has to be filled out: JOIN CC 19010102 in 19010101. The CR for DELETE CC 19010102 will be done automatically in the name of the same requestor.

DELETE CC

(only valid for major release!)

 

DELETE CC = An existing CC shall be removed from the ECLASS standard

Mandatory fields: CR type DELETE CC id_cc_existing the 6-digit identifier of the existing CC (to be deleted) class coded name the 8-digit class coded name (current release) CR Proposer Your name Reason for request Your reason for the change

NOTE: o DELETE CC is only possible for CCs on 2nd and 3rd levels: if all subordinate (child-) CCs on 4th level have a successor by move/split/join and the parent classes to be deleted are empty o For CCs on 4th level: in case of SPLIT CC or JOIN CC, the source CCs are automatically deleted. Thereby a predecessor-successor-relation is documented for product classes (4th level), the DELETE CC line does not have to be filled out, it would be a duplicate.

NONE

NONE = A CC-Relation is changed in another table, the reference has to be added here Mandatory fields: CR type NONE id_cc_existing the 6-digit identifier of the existing CC preferred name EN The name of the class to be referred on (See ECLASS Wiki for naming rules) class coded name your proposed new class coded name (future release))


NOTE: NONE is a mandatory line, if the referred element is not yet included in another CR in this table. If a property or a keyword shall be added to the CC, the CC has to be named here.