DocumentVersion

Description of Parts In other formats like the KBL- or the KOMP-model the diverse types of parts (e.g. connector housing, terminal, wire) are differentiated by inheritance with a subclass for each type inheriting from the type corresponding to PartVersion.

Description of Parts In other formats like the KBL- or the KOMP-model the diverse types of parts (e.g. connector housing, terminal, wire) are differentiated by inheritance with a subclass for each type inheriting from the type corresponding to PartVersion.

Description of Parts In other formats like the KBL- or the KOMP-model the diverse types of parts (e.g. connector housing, terminal, wire) are differentiated by inheritance with a subclass for each type inheriting from the type corresponding to PartVersion.

Item Equivalence ItemVersions (DocumentVersions and PartVersions) are company specific keys / identifiers for a part (component) or a piece of information. However, this also means that the same part, or piece of information, can have different identifiers depending on the context.

Item Equivalence ItemVersions (DocumentVersions and PartVersions) are company specific keys / identifiers for a part (component) or a piece of information. However, this also means that the same part, or piece of information, can have different identifiers depending on the context.

Item Equivalence ItemVersions (DocumentVersions and PartVersions) are company specific keys / identifiers for a part (component) or a piece of information. However, this also means that the same part, or piece of information, can have different identifiers depending on the context.

Item Equivalence ItemVersions (DocumentVersions and PartVersions) are company specific keys / identifiers for a part (component) or a piece of information. However, this also means that the same part, or piece of information, can have different identifiers depending on the context.

Item Equivalence The class ItemEquivalence enables the description of equivalence relationships between two or more ItemVersions. The standard use case is to relate ItemVersions defined in the context of one company (numbering system) to ItemVersions defined in the context of another company.

Item Equivalence The class ItemEquivalence enables the description of equivalence relationships between two or more ItemVersions. The standard use case is to relate ItemVersions defined in the context of one company (numbering system) to ItemVersions defined in the context of another company.

Description of Parts In traditional data formats the diverse types of parts (e.g. connector housing, terminal, wire) are differentiated with individual subclasses for each type inheriting from the type corresponding to PartVersion.