General Technical Part
General Technical Part The class GeneralTechnicalPartSpecification is intended to aggregate common technical attributes that are relevant for most kinds of parts (e.g. …
General Technical Part The class GeneralTechnicalPartSpecification is intended to aggregate common technical attributes that are relevant for most kinds of parts (e.g. …
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 …
Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or …
Usage Constraints A UsageConstraintSpecification is intended to describe the allowed usage of the constrainedParts. A UsageConstraintSpecification is a container for various …
Parts and Documents DocumentVersion and PartVersion are representing one of the most fundamental key concepts of the VEC. They are the only classes in the VEC model that are …
Before reading these implementation guidelines, it is highly recommended to read the “Description of Parts” section in the VEC Online Model Description. This section explains the …
The definition of the product itself (the wiring harness) is one of the major use cases of the VEC. The figure below illustrates the basic building blocks in the data model and …
For reasons of traceability (e.g. requirements) or because certain information is better represented in other standards than in the VEC format (e.g. 3D models for components), it …
A wide range of different systems, supporting different use cases, are used in the process of wiring harness development. All of them might have a VEC-Interface for input & output, …
The PartVersion is one of the two anchors for PDM information in the VEC. All technical information about a PartVersion is contained in one or more documents. These describing …