Review

Tailoring Mechanisms

There are two ways to tailor the VEC schema according to your own needs in a compatible way to create your own process, tool or company specific VEC schema (which is still a valid VEC): New literals can be added to open enumerations (see Open and Closed Enumerations) With “Schema Filtering” the schema can be made more restrictive (Less allowed classes, attributes etc.). In order to remain compatible with the VEC, both approaches require that the changes are in a way, so that a file that is validated against the custom Schema must also be valid against the regular XML Schema of the Standard.

Custom Properties

This implementation guideline gives more details and examples on the usage and the correct interpretation of the VEC concept: Extensibility with Custom Properties. CustomProperty is available in all subclasses of ExtendableElement. In the following examples the class Person is used, which intentionally is not a subclass of ExtendableElement, but for a clear and easy to understand example of custom properties it is well suited. The left side shows the Person class as defined in the VEC.

Wires

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 on the PROSTEP JIRA. This page or section resolves KBLFRM-953 This Implementation Guideline covers the various aspects of a correct wire representation in the VEC for different scenarios and variants of wires.

General Structure of VEC Files & Documents

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. Whereas the PartVersion “just” represents a PDM anchor / reference for a part or component plus some Meta-Information, the DocumentVersion has different characters in the VEC (for more details see section Usages of the DocumentVersion): It can serve as a plain PDM anchor / reference to a document, with no further content / information in the VEC, like the PartVersion for parts (VEC equivalent to the KBL External_reference).

Sealed Ring Terminals

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 on the PROSTEP JIRA. This page or section resolves KBLFRM-631 Sealed ring terminal with overlapping protection Ring terminals are often installed with a wire protection (e.