DocumentVersion

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 “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.

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 is necessary to be able to reference external documents from VEC elements.

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?

The VEC has two major key concepts: PartVersion and DocumentVersion. Both are ItemVersions and both are used to reference / identify a piece of relevant information in a PDM context unambigiously.

Parts, Documents and Resources DocumentVersion, PartVersion and ResourceVersion are representing one of the most fundamental key concepts of the VEC. They are the only classes in the VEC model that are defining version information.

Parts, Documents and Resources DocumentVersion, PartVersion and ResourceVersion are representing one of the most fundamental key concepts of the VEC. They are the only classes in the VEC model that are defining version information.

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 defining version information.

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 defining version information.