PartStructureSpecification

As described in detail in the Implementation Guideline “General Structure / Usages of the DocumentVersion” one use case of the DocumentVersion is to serve as a payload data container within the VEC, either for the digital representation of an external document or for native digital data.

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 concepts for the representation of part master data and component specifications in the VEC.

Before reading these implementation guidelines, it is highly recommended to read the “Instantiation of Components” section in the VEC Online Model Description. This Implementation Guideline complements the Specification Chapter Instantiation of Components with concrete examples and detailed definitions for specific use cases.

Before reading these implementation guidelines, it is highly recommended to read the “Composite Part Descriptions” section and its subsections in the VEC Online Model Description first. Whereas the model description defines the general concepts of multilevel composite parts and 100% and 150% variance for those parts, this implementation guideline follows a use case oriented approach and explains the correct usage of the different aspects of a VEC implementation (e.

Disclaimer: This page or section is currently under review by the community. The content of this page or section can be subject to change at any time. If you find any issues or if you have any review comments please drop us an issue in our Issue Management on GitHub.

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, so sooner or later the question arises “What are the expectations for the behavior of those interfaces?

Assemblies, Modules and Harness (Configurations) The KBL introduced different concepts for composite parts: harnesses, modules, harness configurations and assemblies. The KBL defines a harness as a set of occurrences, just like an assembly.

Assemblies, Modules and Harness (Configurations) The KBL introduced different concepts for composite parts: harnesses, modules, harness configurations and assemblies. The KBL defines a harness as a set of occurrences, just like an assembly.

Assemblies, Modules and Harness (Configurations) The KBL introduced different concepts for composite parts: harnesses, modules, harness configurations and assemblies. The KBL defines a harness as a set of occurrences, just like an assembly.

Harness and Variants In addition to the CompositionSpecification and the PartStructureSpecification, the VEC defines two other concepts to control occurrences, especially composite parts (e.g. modules): ModuleFamily and ModuleList. PartWithSubComponentsRoles referenced by a ModuleFamily respectively the OccurrenceOrUsage these PartWithSubComponentRoles belong to are mutually exclusive.