References the corresponding languageCode of the value.
The value of the LocalizedString in language defined by the languageCode.
AnAbstractSlotis a geometrical place in a connector housing, which can contain / group cavities. This can be either direct, if it isSlotand indirect if it is aModularSlot.
If it is aSlot, then it is an inseparable part of the connector housing, which means it is created during the manufacturing process of the connector housing.
If it is aModularSlotit is a place where one or more other connector housing can be place during the assembly.
Specifies the number of the slot. This must be unique within a ConnectorHousingSpecification.
AnAbstractSlotReferencerepresents the usage of an AbstractSlot in the context of PartUsage or PartOccurrence.
Specifies a unique identification of the SlotReference. The identification is guaranteed to be unique within the ConnectorHousingRole. The cavity & slot number is defined by the associated cavity and slot.
Class for the definition of alias identifications. Alias identifications are additional identifications for VEC-elements, which are valid in a certain scope (e.g. PPS-ID's).
Specifies the identification value.
Defines the type (or the role) of the AliasIdentification. Defined literals are contained in an OpenEnumeration.
The scope in which the AliasIdentification is valid / or the issuer of the alias id. This could be for example a certain process, a company or an IT-System.
On optional human readable description of the AliasIdentification.
Specification of the electrological aspects of an antenna.
Specifies the minimum operating frequency of the antenna.
Specifies the maximum operating frequency of the antenna.
Specifies the impedance of the antenna.
AnApplicationConstraintdefines a condition with which it is possible to express the inclusion or exclusion of ConfigurableElements in different variants of a product. TheApplicationConstraintis focused to express validity rules based on time periods or elements of the product hierarchy in a concise way (attributes and relationships). It is complementary to theVariantConfigurationwhich expresses validity rules based on control strings.
AnApplicationConstraintcan reference anotherApplicationConstraintasbaseInclusion. In this case, anApplicationConstraintcan only be satisfied if itsbaseInclusionis also satisfied.
Defines if the application constraint is positive (allowance) or negative (denial). If theApplicationConstrainthas abaseInclusionthatbaseInclusionshall define the same type.
Specifies the lower bound of the time period to which the application constraint applies.
Specifies the upper bound of the time period to which the application constraint applies.
Specifies the lower bound of a serial number range to which the application constraint applies.
Specifies the upper bound of a serial number range to which the application constraint applies.
Specifies the project phases to which the application constraint applies.
In the production logistics of complex products (like vehicles), the control of operation and cancellation dates of changes, features, components or the like is usually not carried out via concrete dates but via "date keys". These keys are then mapped in planning systems with concrete time specifications for certain plants or production steps. In the VEC these keys are calledEffectivityControlKey.
With theFromEffectivityControlKeyandTo EffectivityControlKeya validity interval can be defined. If one of the two values is defined and the other is omitted, the meaning shall be "unbounded".
SeeFromEffectivityControlKey.
AnApplicationConstraintcan only be satisfied if itsbaseInclusionis satisfied as well.
Defines the projects for which the application constraint applies.
Specification for the definition of application constraints. The associated ApplicationConstraints are restricting the possible usages of the associatedConfigurableElements.
Defines the approval of an ItemVersion. This consists of the StatusOfApproval and the Permissions issued for the approval.
Specifies a unique identification of the approval. The identification is guaranteed to be unique over all VEC-documents. Normally this would reference to a company specific approval number or something similar. KBLFRM-349
Room for additional information about the item.
Room to specify for which companies the Approval is valid. It might be e.g. that an approved Item may only be delivered by some specific company.
The approval level concerning approval status. Predefined are the values: NotYetApproved, Approved and Withdrawn. The status refers to the status of theApproval, not the status of theItemVersion.So, e.g. withdrawn means the approval (with its corresponding level) has been withdrawn, not theItemVersionitself.
Relates to activities that are allowed with the ItemVersion after release for example building pilot tools or production tools. The levelOfApproval applies to theItemVersionitself without further detailing or additional context. So, for example "Free" means, that from a component's perspective the correspondingPartVersionhas satisfied all qualification procedures and can be used within its specified limits without restriction.
The levelsPlanned,Free,Invalidrefer to a single approval level. The levelsDevelopandRestrictedrefer to a category of approval levels in the lifecycle of anItemVersionthat all belong to the same phase but are highly company specific. For example,Developapprovals might be a "a start of construction approval" or a "building of prototypes or tools allowed approval". "Restricted" approvals might be "only for special purpose vehicles", "spare part only" or "residual parts may be used up".
In these cases, theadditionalLevelInformationcan be used to provide further information (e.g. a company specific approval level).
Additional potentially company specific information about the level of approval (e.g. further detailing of a "Restricted" approval.
Specifies the permission issued with the approval.
AnAssignmentGroupis a concept that allows the clustering of arbitrary elements in ways that are orthogonal to hierarchical and semantic structure of the VEC.
Specifies a unique identification of the AssignmentGroup. The identification is guaranteed to be unique within the specification.
Specifies additional, human readable information about theAssignmentGroup.
Specification that containsAssignmentGroups.
Contains the AssignmentGroups that are defined by this AssignmentGroupSpecification.
ABaselineSpecificationdefines a set ofItemVersions (Document-andPartVersions) that relate to each other in a certain way e.g. all parts and documents in their specific versions that contributed to a specific manufactured result.
Baselines are a standard mechanism to support change, release and configuration management.
Defines the state of the baseline itself (e.g. if it is finalized or work in progress).
Defines the state of the content of the baseline in regard of its defined scope.
References theItemVersionsthat are the content of the baseline.
Specification of the electrological aspects of a battery.
Specifies the nominal voltage of the battery.
Specifies the current the battery provides.
Specifies the battery's current in cool state.
Specifies the power capacity of the battery.
Specification for fixings that are mounted onto a bolt. This means the fixing itself has got a hole, which is mounted onto a bolt of the surrounding.
Specifies the type of the bolt on which the fixing can be mounted.
Specifies the shape of the bolt on which the fixing can be mounted.
Specifies the diameter of the bolt on which the fixing can be mounted.
Specifies the height of the bolt on which the fixing can be mounted.
ABoltTerminalRoledefines the instance specific properties and relationships of a ring terminal.
Specification for the definition of bolt terminals. These are the counterparts to ring terminals.
Specifies the diameter of the bolt in a nominal way.
Specifies the height of the bolt (the height of the part to which ring terminals can be attached).
Defines the size (diameter) of the bolt in a nominal way (e.g. "M8").
Specifies the type of the bolt.
Specifies if the bolt provides torsion protected or not.
Defines the maximum number of (ring) terminals that can be attached to this bolt at the same time.
A custom property with a boolean value.
Defines the value of the CustomProperty.
The bounding box is used to define a cuboid (box) that can contain a described part completely. Therefore, it is a simplified representation of the bounding volume and represents a definition of the maximum volume occupied by the part.
It is valid to use theBoundingBoxto describe the dimensions of a component, even if not all dimensions are known (e.g. only length and width). However, it must be possible to transform such a partial bounding box into a complete bounding box by adding the missing dimensions.
Defines the extent of the bounding box in the direction of x(length).
Defines the extent of the bounding box in the direction of y(width).
Defines the extent of the bounding box in the direction ofz(height).
ABridgeTerminalRoledefines the instance specific properties and relationships of a bridge terminal (see BridgeTerminalSpecification).
A bridge terminal is a part that behaves like terminal but has noWireReceptions.It is used to create short circuit between different pins in a connector. In its use, it can realize a schematic connection on its own and independently of other components.
References theConnectionthat is realized by thisBridgeTerminalRole.
A bridge terminal is a part that behaves like terminal but has noWireReceptions.It is used to create short circuit between different pins in a connector. In its use, it can realize a schematic connection on its own and independently of other components.
Defines the position of a BuildingBlock2D on a HarnessDrawing.
Specifies a unique (optional) identification of the BuildingBlockPositioning2D. The identification is guaranteed to be unique within the HarnessDrawingSpecification2D.
Defines the position of a BuildingBlock3D in the HarnessGeometry.
Specifies a unique (optional) identification of the BuildingBlockPositioning3D. The identification is guaranteed to be unique within the HarnessGeometrySpecification3D.
References the building block that is positioned.
Specifies the positioning of the building block in the harness geometry.
Specification for the description of a two-dimensional building block. A building block is a reusable section of a geometry.
Specifies the CartesianPoint2Ds that are used in the BuildingBlockSpecification2D.
Specification for the description of a three-dimensional building block. A building block is a reusable section of a geometry.
References the Zone that is building block represents. This shall be a TopologyZone with the type "DmuZone".
Specifies the GeometrySegment3Ds defined by the BuildingBlockSpecification3D.
Specifies one outlet of the cable duct.
Specifies the identification of the Outlet. This must be unique within a CableDuctSpecification.
Specifies thePlacementPointthat represents thisCableDuctOutletin a PlaceableElementSpecification.
ACableDuctRoledefines the instance specific properties and relationships of a cable duct.
References theCableDuctSpecificationthat is instanced by thisCableDuctRole.
Specification for cable ducts. A cable duct can have one or more outlets.
ACableLeadThroughspecifies a hole in the grommet through which wires can pass through the grommet. There can be different technical realizations of a lead through, e.g. it can be realized with a shrinking material or an additional seal. The properties of aCableLeadThroughare defined in the referencedCableLeadThroughSpecification.
For a precise placement in topology, aCableLeadThroughspecifies outlets.
Specifies the identification of the CableLeadThrough. This must be unique within a GrommetSpecification.
References theCableLeadThroughSpecificationthat defines the technical properties of thisCableLeadThrough.
Specifies the identification of theCableLeadThroughOutlet. This must be unique within aCableLeadThrough.
Specifies thePlacementPointthat represents thisCableLeadThroughOutletin a PlaceableElementSpecification.
ACableLeadThroughReferenceis the instance of a CableLeadThrough. It can define a set of plugs or seals that are used together with it. Plugs are used if no wire is present, seals are used together with a wire.
Specifies a unique identification of the CableLeadThroughReference. The identification is guaranteed to be unique within the GrommetRole.
References the plugs that are used with this CableLeadThroughReference. This association might be a 150% selection.
ACableLeadThroughspecifies a hole in the grommet through which wires can pass through the grommet. TheCableLeadThroughSpecificationdefines the technical properties of aCableLeadThrough(or a set of similar ones).
Defines the type of a cable lead through. Standardized values are defined in anOpenEnumeration.
Defines the geometry of a cable lead through in the sealing area. Standardized values are defined in anOpenEnumeration.
Specifies the dimension of the cable lead through in the sealing area.
Specifies the minimum diameter a segment can have to fit through the cable lead through. This definition is necessary, since segments that are too small might cause movements and unacceptable torsion forces or they are not sealable.
Specifies the maximum diameter a segment can have to fit into the cable lead through.
Specifies if the cable lead through is sealable.
ACableTieRoledefines the instance specific properties and relationships of a cable tie.
Specification for the definition of cable ties.
Specification of the electrological aspects of a capacitor.
The breakdown voltage of the capacitor.
Specifies the height of the object. The unit of this value is the baseUnit of containing BuildingBlockSpecification2D.
Specifies the width of the object. The unit of this value is the baseUnit of containing BuildingBlockSpecification2D.
A CartesianPoint2D is a point that is defined by its coordinates in a rectangular two-dimensional Cartesian coordinate system.
Specifies the value of x-coordinate of the Cartesian point. The unit of this value is the baseUnit of containing BuildingBlockSpecification2D.
Specifies the value of y-coordinate of the Cartesian point. The unit of this value is the baseUnit of containing BuildingBlockSpecification2D.
A CartesianPoint3D is a point that is defined by its coordinates in a rectangular three-dimensional Cartesian coordinate system.
Specifies the value of x-coordinate of the Cartesian point. The unit of this value is the baseUnit of containing BuildingBlockSpecification3D.
Specifies the value of y-coordinate of the Cartesian point. The unit of this value is the baseUnit of containing BuildingBlockSpecification3D.
Specifies the value of z-coordinate of the Cartesian point. The unit of this value is the baseUnit of containing BuildingBlockSpecification3D.
Abstract super class for vectors, either 2D or 3D.
A Cartesian vector in the two-dimensional space.
Specifies the x-coordinate in 2D space.
Specifies the y-coordinate in 2D space.
A Cartesian vector in three-dimensional space.
Specifies the x-coordinate in 3D space.
Specifies the y-coordinate in 3D space.
Specifies the z-coordinate in 3D space.
A cavity is a defined space in a connector housing for location of an electrical terminal or cavity plug or seal. A cavity may also be empty.
Defines whether the cavity is available for contacting. If the cavity is not available, it means that it is completely closed.
Provides an identifier for the cavity. The cavity number needs to be unique within aSlot.
Defines whether the cavity has an integrated terminal (for example an IDC cavity) or if an additional terminal is required.
If this attribute is "true", the cavity can reference aTerminalSpecificationasintegratedTerminalSpecificationin order to specify the integrated terminal.
Specifies the terminal, if the cavity has an integrated terminal (e.g. an IDC).
ACavityAccessoryRoledefines the instance specific properties and relationships of a cavity accessory.
ACavityAccessoryis a non-electrical part used in a cavity with no sealing properties (e.g. a wire fixation).
Specifies a range of valid wire diameters to which the cavity accessory fits.
Specifies the wireReceptionType to which the cavity accessory fits.
Specifies the wire addon needed to reach aCavityfrom a specificSegmentConnectionPoint. More specifically, it is the addon required to calculate the cutting length of a wire. It is not a measured distance between the segment connection point and the insertion point of the cavity. For eachSegmentConnectionPointthere shall be no more than one add-on value per cavity and type.
Specifies the wire length add on needed for the cavity.
Defines the type of the add-on (seeCavityAddOn).
ACavityCouplingdefines the mapping between two cavities of theConnectorHousingRolesassociated with theCouplingPoint.
Defines the mapping of two cavities contained Slot A & B of the containing SlotMapping-object.
The identification of the Cavity on side A
The identification of the Cavity on side B
A CavityMounting defines the cavities (CavityReference) where the contacted elements (Terminal) will be mounted.
Specifies the CavityMoutingDetails, if a detailed description of the relationships between Cavities and TerminalReceptions is needed.
With a CavityMountingDetail it is possible to describe a detailed cavity mounting.
This is needed if the information which terminal reception is mounted into which cavity is important. There are cases where this information can be relevant (e.g. bridge contacts with an asymmetric wire mounting).
TheCavityPartSpecificationis an abstract class for common properties of non-electrical parts that are used inCavities.
Specifies a valid cavity dimensions to which the cavity part fits. The dimension defines the size of the sealing area of the cavity (crimp end), not in the contacting area (box end).
Note: CavityDimension is of type Size which is defined as x & y with type NumericalValue. NumericalValue can define tolerances. So, a cavity dimension is not necessarily a single fixed value.
Specifies the hardness of the cavity seal.
Defines the geometry of the cavity sealing.
This attribute is defined as an OpenEnumeration.
Defines a list of terminal types that are compatible to this CavitySealSpecification. This defines as well the compatible cavities, since a plug is normally used when no terminals are present.
Defines a list ofCavityGeometriesthat are compatible with this cavity part.
A CavityPlugRole defines the instance specific properties and relationships of a cavity plug.
References theCavityPlugSpecificationthat is instanced by thisCavityPlugRole.
Specification for the definition of cavity seals. A cavity plug is a watertight non-electrical object to fill an empty cavity.
The rotation of the cavity is defined as the angle between the primary locking of the cavity and the Y-axis of the connector housing coordinate system.
TheUnitin which all coordinates (e.g. cartesian points) of thisCavityPositionDetail are defined. Shall be a unit of length (e.g. millimetre).
The position of the center of the cavity in the entrance surface of the connector during the insertion process.
A CavityReference represents the usage of a Cavity in the context of PartUsage or PartOccurrence.
Specifies a unique identification of the CavityReference. The identification is guaranteed to be unique within the ConnectorHousingRole. The cavity & slot number is defined by the associated cavity and slot.
References theComponentPortthat is implemented by thisCavityReference.
Contains the terminal role if the cavity has an integrated terminal (e.g. an IDC).
A CavitySealRole defines the instance specific properties and relationships of a cavity seal.
References theCavitySealSpecificationthat is instanced by thisCavitySealRole.
Specification for the definition of cavity seals. ACavitySealis a watertight non-electrical object to fill a populated Cavity.
Specifies a range of valid wire diameters to which the cavity seal fits.
Specifies the wireReceptionType to which the cavity seal fits.
Defines the inside diameter in the relaxed state for a cavity seal.
Specification for the definition of cavities.
Specifies the angle against two planes of the connector housing a terminal used in this cavity can be buckled.
Deprecated (since Version 1.1.4): This attribute has been marked as deprecated, as it has been replaced by the more meaningful mechanism withTerminalTypes.
Defines the geometry of a cavity in the sealing area (crimp end).
Specifies the dimension of the cavity in the sealing area of the cavity (crimp end), not in the contacting area (box end).
TheHeightof a cavity is defined as the dimension of cavity in the direction of the primary locking. TheWidthis the dimension orthogonal to theHeight.
For cavities withGeometry = CirculartheSize.Widthshall be equal toSize.Height.
Specifies the minimum diameter a wire is allowed to have to fit into the cavity. This definition is necessary, since wires that are too small might cause movements and in acceptable torsion forces on terminals.
Specifies the maximum diameter a wire is allowed to have to fit into the cavity.
Specifies if the cavity has a primary locking and of what type it is.
Specifies if the cavity is sealable.
Defines a list of terminal types that are compatible to this CavitySpecification.
A ChangeDescription describes the implemented issues that are reason for the aggregating ItemVersion to be either an initial or successor version. A ChangeDescription can optionally define the person who has approved the change.
Specifies an identifier for the ChangeDescription. This can be the ID of a change order or an ID which indicates model upgrading. (see KBLFRM-249)
Specifies the label of the change on a drawing for example. If more than one change is issued with one ItemVersion (e.g. change 0001, 0002), in some cases the different changes are labelled on the drawing (e.g. A, B, C).
Specifies additional, human readable, information about the ChangeDescription.
Specifies the person who has approved the change.
Specifies the date when the change was performed.
Specifies the design engineer who is/was responsible to perform the change.
Specifies the identification of a corresponding change request. (see KBLFRM-249)
Specifies the coding of a slot or a connector housing.
Specifies the name of the coding.
Specifies a color value. A color is always defined by a key value. What color is meant by this key value is defined by a standard reference system (e.g. RAL).
For example, if a RAL color should be expressed in the terms of the VEC thereferenceSystemwould be "RAL", thekeywould be the RAL number defined by the standard (e.g. "1003" for signal yellow).
Attributes of the type Color normally have the multiplicity [0..*]. This means that such an attribute can have a value for different referenceSystems (e.g. RAL, RGB,...). It must not have multiple values for the same ReferenceSystem.
The key of the color in the corresponding color reference system.
The identification of the color reference system, which is defining possible values and the semantic of color keys. (see KBLFRM-315). For common color reference systems the literals defined in the open enumerationColorReferenceSystemshall be used.
On optional human readable description of the color (e.g. the name).
A custom property that represents a tuple of values.
The customProperties that represent the individual values of the complex property.
AComponentConnectoris a grouping ofComponentPortsand represents a logical abstraction of a connector of anEEComponent. When theComponentNodeis realized by anEEComponentRoletheComponentConnectorwill result in aHousingComponent.
It is permitted that aComponentConnectoris a 150% definition of connector.
A ComponentNode is a node where an electrological component is located. It is a representative for an element in the electric system, e.g. an actuator, a sensor, an ECU. In this way it is quite similar to a NetworkNode and may even reference the corresponding NetworkNode in this case. However, a ComponentNode is more likely to be used as a representative of an inliner or a splice. Moreover, a ComponentNode can define childNodes in order to describe its internal structure.
Specifies a unique identification of the ComponentNode. The identification is guaranteed to be unique within the ConnectionSpecification.
Room for a short name of the ComponentNode.
Specifies the type of the ComponentNode.
Room for additional, human readable information about the ComponentNode.
Specifies the sub type of a ComponentNode. The sub type allows a differentiation within a specific type. E.g. an actuator can be differentiated into lamps, speakers, motors.
References theUsageNodethat is realized by thisComponentNode.
Defines a port of ComponentNode. A ComponentPort is usually the realization of a NetworkPort. Electrological connections are defined between two or more ComponentPorts.
Specifies a unique identification of the ComponentPort. The identification is guaranteed to be unique within the ComponentConnector.
Specifies the direction of the signal on this ComponentPort.
Room for additional, human readable information about the ComponentPort.
References theSignalthat is associated with theComponentPort.
Defines a unit as a composition of other units. The composition is done by multiplying the different other units. By this way combined units like kg/m can be formed.
References theUnitsthat are used as factors to create theCompositeUnit.
The CompositionSpecificiation is used to define a set of occurrences required to describe unambiguously the design of a composite part. This does not have to be necessarily the same occurrences which are building the bill of material. Example: A company might want to regard an antenna cable as one part out of a bill of material perspective. However, at the same time it may be useful for the company to be able to describe the contacting of the antenna cable within the VEC. (see also PartStructureSpecification)
Specifies the PartOccurrences defined in the CompositionSpecification.
TheConductorCurrentInformationspecifies the maximum current for which a conductor is approved. As the maximum current is dependent from the voltage and the environment temperature it is modelled as a class and not only as an attribute.
The maximum current value.
The environment temperature for which this maximum current value is applicable.
The voltage for which this maximum current value is applicable.
ConductorMaterialis a helper class to specifyvalidConductorMaterials.This is necessary, since all attributes of the typeMaterialhave a multiplicity of * with the semantics that it always definesone Materialwith the possibility to define it in different reference systems.
Since a wire reception can have more than onevalidConductorMaterialthis container class is necessary to keep the semantics clear.
Specifies the material.
Specification for the definition of conducting properties of a WireElement.
Specifies the cross-section area of the conductor (e.g. 0,5 mm²). The cross-section area is a nominal value, which refers to the conducting properties of the conductor normalized to the properties of a full material core.
Specifies the mass information of the conductor. In most cases this mass information is known as copper weight and is normally specified as mass per length (e.g. gram per meter).
Specifies the material of the conductor.
Specifies the electrical resistance of the conductor. In most cases this is specified as resistance per length (e.g. Ohm per meter).
Specifies the structure of the conductor according to ISO 6722-1 for ConductorSpecifications with Type = Stranded.
Should only be used for ConductorSpecifications with type=Stranded.
Specifies the type of the conductor, e.g. if it is rigid or stranded.
Specifies the number of strands in one conductor. If the conductor is solid than the number of strands would be one.
Specifies the plating material of the conductor.
Specifies the diameter of a single strand in the conductor.
Specifies the voltageRange for which the conductor is approved.
Specifies the current information of the conductor. These are the maximum currents for which the conductor is approved.
Abstract base class for all elements which can be configured with a VariantConfiguration.
Deprecated since VEC V2.0.0. Use ConfigurationConstraints instead.
References the application constraints that apply to the ConfigurableElement.
Deprecated since VEC V2.0.0. Use ConfigurationConstraints instead.
References the configuration information that applies to the ConfigurableElement.
Contains or moreConfigurationContraintsthat apply to thisConfigurableElement.This is explained in more details in the recommendation chapter / model diagram "Variants".
Represents aConfigurationContraint("When does this element exist?") for a specific application (ApplicationConstraint)and a "configuration universe" (VariantConfiguration.configurationType)
Specifies a unique identification of theConfigurationConstraint. The identification is guaranteed to be unique within theConfigurableElementand does not change over the time.
References the application constraint that applies to the ConfigurationConstraint.
References the configuration information that applies to the ConfigurationConstraint.
A Connection is an electrological connection between two or more ComponentPorts.
Specifies a unique identification of the Connection. The identification is guaranteed to be unique within the ConnectionSpecification.
Specifies additional, human readable information about the Connection.
Specifies installation instruction for the connection.
A connection end is the end of a Connection at a ComponentPort.
Specifies a unique identification of the ConnectionEnd. The identification is guaranteed to be unique within the ConnectionSpecification.
Specifies if the ConnectionEnd is connected to the internal or the external side of the ComponentPort.
Specifies if the ConnectionEnd is male or female. This may be e.g. important in case of an inliner.
Specifies installation instruction for theConnectionEnd.
A ConnectionGroup references two or more Connections expressing that the physical realization of the referenced Connection shall be somehow grouped e.g. twisted. For complex structures a ConnectionGroup can specify subgroups.
Specifies a unique identification of the ConnectionGroup. The identification is guaranteed to be unique within the ConnectionSpecification.
Specifies the type of the connectionGroup, valid literals are defined in the open enumerationConnectionGroupType.
Specifies additional InstallationInstructions for the ConnectionGroup.
Room for additional, human readable information about the ConnectionGroup.
Specifies a unique identification of theComponentNodeViewItem. The identification is guaranteed to be unique within theConnectionViewSpecification.
Specifies the grid square in which theComponentNodeViewIt emis placed (e.g. E/40).
Specifies allComponentPortViewItemsthat are displayed on thisComponentNodeViewItem .The order of this association defines the clockwise arrangement of the ports on the node. As eachComponentPortViewItemcan also define the side on which it is placed, side definitions take precedence over order.
Caution:This association isordered!
A ConnectionSpecification is used to define electrological connectivity.
TheConnectionViewSpecificationsupports the exchange of a basic layout for aConnectionSpecification.
A ConnectorHousingCapRoledefines the instance-specific properties of a cap for a connector (backshells).
References theConnectorHousingCapSpecificationthat is instanced by thisConnectorHousingCapRole.
Specification for the definition of caps (backshells) of connectors. Different caps can add additional wire length addons to a connector housing.
A 'cap' which already defines the number of cavities, coding etc. is in the VEC defined byConnectorHousingSpecificationwithModularSlotsand not by aConnectorHousingCapSpecification.
Specifies the wire length add on needed for the cap.
Defines theOutletDirectionfor wires.
This attribute is defined as anOpenEnumeration.
A ConnectorHousingRole defines the instance specific properties and relationships of a connector housing.
Specifies if this instance of a connector housing should be sealed (waterproof).
References the ComponentConnector that is realized by the referenced ConnectorHousing (OccurrenceOrUsage with ConnectorHousingRole). This can especially be relevant for inliners. KBLFRM-341.
References theConnectorHousingSpecificationthat is instanced by thisConnectorHousingRole.
Specification for the definition of connector housings. A connector housing consists of a one or more slots. In the means of the VEC, a connector housing can be a conventional connector housing, a contact module or a connector shell.
Specifies the average wire length add on for this connector.
Specifies the allowed voltage range for the connector housing.
Defines whether the connector is coupleable or not. Connectors that are coupleable can be used in an inline position. Connectors that are not coupleable can be connected only to an ECU or something similar.
IftruetheConnectorHousinghas a connector position assurance (CPA).
A CPA is some sort of feature of a connector, that secures the connector in its correctly assembled position with its mating part.
Defines theOutletDirectionfor wires.
This attribute is defined as anOpenEnumeration.
Specifies theSegmentConnectionPointsthe connector housing.
A contact point defines the relationship between Terminals, Seals, Plugs, Cavities and Wires. It specifies a single contacting variant. This means that the contacting is manufactured, as specified by theContactPoint. Either all participants (Cavities, Terminals, Seals, Wires) set into a relationship by theContactPointexist in a specific harness or none. There is no requirement, to filter the participants of a contacting situation with information derived from VariantConfigurations or assembly / module associations in order to create a manufacturing variant.
TheContactPointrepresents a single potential. Consequently, all cavities and wires referencing / being referenced by aContactPointare short-circuited and have the same potential (even if the signals on the wires are named differently. If a contacting of a terminal has more than one potential (e.g. a coax-contact) one contact point for each potential is needed.
Specifies a unique identification of the ContactPoint. The identification is guaranteed to be unique within the ContactingSpecification.
A Contract-instance describes the relationship between an ItemVersion-instance and a Company-instance additionally defining the role the company takes in reference to the ItemVersion.
Specifies the company which acts in the specified Role in the Contract Relationship.
The role the company takes in reference to the associated ItemVersion. Predefined are the values: OEM, Supplier and Manufacturer.
A CopyrightInformation-instance specifies copyright information for one or more Items.
An informal text which specifies copyright information.
Defines the properties of a circular conductor (core) which are specific for them.
Specifies the outside diameter of the core.
Specification for the definition of corrugated pipes.
Specifies the height of a corrugation of the pipe.
Specifies the width of a corrugation of the pipe.
Specifies the gradient of a corrugation of the pipe.
ACouplingPointdefines a single coupling. If a coupling takes place, all sub elements are connected. If the coupling is disconnected, all subelements are disconnected.
If a coupling occurs between two connectors, and not just between two terminals, theCouplingPointreferences the respectiveConnectorHousingRoles.
Specifies theMatingPointsdefined within theCouplingPoint.
Specification for the description of a Coupling. A coupling allows the mapping between independent harness sections or EEComponents of the electrical system. This is done by the mapping of either-or both, ConnectorHousingRoles & TerminalRoles of one side to the other.
A Creation-instance provides additional information to the owning ItemVersion stating personal information on the creator and the creation date.
Specifies the date when the associated ItemVersion was created. (see KBLFRM-241)
Specifies the person who has created the Item.
Specifies the person, which is the responsible designer for the ItemVersion at the point of creation.
TheCurve3Dis an abstract representation of a curve, that defines the three-dimensional appearance of the centreline of a segment. The concrete type of the curve (e.g. NURBSCurve) defines the mathematical function that applies to curve and stores the required parameter set for this function in the VEC.
Abstract base class for custom properties. Basically, a custom property is key / value pair. The key (propertyType) defines the meaning of the value. A custom property can either be a simple value (string), a numerical value or a value range.
A CustomUnit can be used to define "FreeText"-Units. Custom units must not be used for units that can be expressed by any of the other subclasses of Unit. Custom units are only allowed if a unit is needed that cannot be handled by any of the other classes.
A unique identification of the custom unit.
A custom property with a date value.
Defines the value of the CustomProperty.
ADefaultDimensiondefines a tolerance value that shall be applied to a part, if no explicit tolerance value has been defined.
dimensionValueRange defines the magnitude of measurements for which the tolerance applies (e.g. length from 500mm - 1500mm).
ThedimensionTypedefines to which measurements thisDefaultDimensionapplies.
ADefaultDimensionSpecificationdefines tolerances that shall be applied to a part, if no explicit tolerance value has been defined.
A Dimension defines a measurement for the distance between two Locations. An acceptable tolerance can be specified additionally. If the Locations are not located on adjacent topology-elements it is possible to specify a Path for the dimension along which the measurement must be taken.
The value for the Dimension is not specified as NumericalValue (which can define a Tolerance as well). This is because the "valueComponent" of the NumericalValue is mandatory. For Dimensions it shall be optional since there are scenarios where the dimension only specifies a Tolerance for a distance defined by the topology (segment length + placement information).
Specifies a unique identification of the Dimension. The identification is guaranteed to be unique within the containing PlacementSpecification.
Defines the value of the dimension. This value can be null, if it shall be calculated and only a tolerance shall be defined.
Defines if the value of theDimensionwas calculated (e.g. the sum of segment lengths in the topology) or if it was defined manually.
References the location that is used as dimension point for the dimensioning (e.g. the entry point of a bundle into a connector housing).
See KBLFRM-329 and KBLFRM-391.
References the location that is used as reference point for the dimensioning (e.g. the location of a fixing as this relates to a fixpoint of the body in white).
See KBLFRM-329 and KBLFRM-391.
ADimensionAnchorrepresents an abstract anchor onto which aDimensioncan be specified.
Specification of the electrological aspects of a diode.
Voltage at which the diode starts conducting in forward direction.
Voltage at which the diode starts conducting in reverse direction.
Specifies the maximum electric current tolerated by the diode.
A DocumentBasedInstruction is an Instruction to a SheetOrChapter in a DocumentVersion or to a complete DocumentVersion.
A DocumentRelatedAssignmentGroup allows the creation of traceability links to elements in aDocumentVersionfor a set of VEC objects. The semantic of the traceability link is defined by theDocumentRelationType.
If this group relates to a specific element in therelatedDocumentVersionthe identifier of the element is defined in this attribute (e.g. a requirements number).
References theDocumentVersionto which this group relates.
Allows a more specific relationship to aSheetOrChapterwithin therelatedDocumentVersion.
The DocumentVersion 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. The documents are containing the actual content of the VEC since all Specifications are an element of a document.
The documentNumber is the major identifier of a DocumentVersion. The format is user defined and respectively company specific.
The type of the document, that is defined in anOpenEnumerationand gives a hint about the content of the document. Values for typical types of documents in the process are predefined (e.g. a part master document for the specification of aPartVersion).
At later point, further constraint might be attached todocumentTypedefining a minimum content for certain types of documents.
The documentVersion specifies the version index of a document (see also documentNumber).
An arbitrary change index that indicates if the digital representation (the content in VEC) of thisDocumentVersionhas been changed / regenerated. This can be for example an index, a timestamp or a checksum. This allows the detection of changes in the content, even when the DocumentNumber & DocumentVersion is the same.
For a more detailed explanation in the context see "Parts & Documents". KBLFRM-837.
The creatingSystem specifies the computer application or the machine which is used to create the document.
The dataFormat specifies the convention that was used to structure the information in the document. This is useful if the DocumentVersion is a pointer to an external document, which is not contained in the VEC or if the content of this DocumentVersion was automatically generated by the extraction of the information out of the original document.
The name of the file as it appears in the VEC-Package, including the folder structure (fully qualified name) that contains thisDocumentVersion. If this DocumentVersion is a link to an external document (e.g. a ComponentSymbol), then the fileName attribute points to the file containing the original document. The usage of this attribute is only valid, if the original document is distributed along with the VEC-file in a VEC-Package. It must not point to any file location which is not part of the VEC-Package (e.g. a File on a central server file share).
The location is a possibility to provide a reference to the source location of theDocumentVersion(e.g. a document management system or an archive system) where the original document can be found.The location shall be provided either as an URN or URL.
The number of sheets contained in the document.
A custom property with a double value.
Defines the value of the CustomProperty.
An EEComponentRole defines the instance specific properties and relationships of an EE-component.
References theEEComponentSpecificationthat is instanced by thisEEComponentRole.
Base-class for the specification of electrological components, which are connected to the harness. Usually electrological components are not part of the harness e.g. a fuse, a switch or a control device. All EEComponents can have one or more HousingComponents which are possible interfaces for the connection to a harness.
Specifies thePowerConsumptionsof thisEEComponentSpecification.This refers to the internal power consumption of this E/E-component, not the power-consumption that might occur indirectly over other E/E-components that are supplied through this component.
Specifies the availableSwitchingStatesof the EEComponent.
Specification for fixings that are mounted onto an edge.
Defines a range of valid thicknesses, onto which the fixing can be mounted.
Abstract base class for extendable elements. Extendable elements have the possibility to define non-standard custom properties.
This association allows allExtendableElementsin the VEC to referenceDocumentVersionsas "external reference".
This association shall be used for the extension of elements in the VEC with information that cannot be represented in the VEC in an appropriate way but can be expressed in some external format (e.g. a specific symbol for aComponentNode).
DocumentVersionsreferenced by this association shall not contain anySpecifications.
This association is no replacement for associations with a more precise semantic like theDocumentBasedInstructionor the associations betweenPartVersionandDocumentVersion.
AnExtensionSlotdefines a slot within an EE-Component where other EE-Components can be plugged into (modular extension). This is necessary for example for modular power distributions.
Identification of the ExtensionSlot, which must be distinct for all ExtensionSlots of an EEComponent.
References thePartRelationsthat are valid inserts for thisExtensionSlot.
This reference points toPartRelationsin order to allow referencing indirectly aPartVersionif the description of individualPartVersionsis done with one physical VEC file perPartVersionand to allow the expression of optional inserts, choices etc. However, inserts for anExtensionSlotare alwaysEEComponentsby itself. Therefore, the referencedPartVersionshall have aPrimaryPartType = EEComponent.
An ExtensionSlotReference represents the usage of an ExtensionSlot in the context of a PartUsage or PartOccurrence.
AnExternalMappingis used to relate anExtendableElementin the VEC with an element located in an external data source. The element in the VEC is referenced by themappedElement, the external element is identified by the attributeexternalReference.
Defines the unique key of the external element. How this key shall be interpreted is dependent from the format of the external data source.
AnExternalMappingSpecificationis used to define a mapping between an external data source (represented by the referencedmappedDocument) and the content of a VEC file.
Reference to theDocumentVersionthat represents the external data source that connected to the VEC content by theExternalMappingSpecification.
Specifies the mappings of individual element.
AFerriteRoledefines the instance specific properties and relationships of a ferrite.
Defines the of windings that the wires are wound around the ferrite.
Specification for the definition of ferrites.
A FileBasedInstruction is an Instruction that references a file packaged (VEC-Package) together with a VEC-file. Such a file can be for example an image.
The name of the file as it appears in the package, including the folder structure (fully qualified name).
The last modified timestamp of the file.
The dataFormat specifies the format of the FileReference. The dataFormat has to be a valid "Internet Media Type" (seehttps://www.iana.org/assignments/media-types/media-types.xhtml).
Specification for the definition of filler elements in the wire.
Specifies the material of the filler.
Specifies the diameter of the filler.
Specifies one outlet of the fitting.
Specifies the identification of the Outlet. This must be unique within a FittingSpecification.
Specifies the inner diameter of the outlet.
Specifies the outer diameter of the outlet.
Defines the nominal size of a tube. The nominal size is a name for the size of the tube that is somehow related to the inner diameter of the tube. However, it is not the inner diameter (e.g. "10.5").
Specifies thePlacementPointthat represents thisFittingOutletin a PlaceableElementSpecification.
Specification for the definition of fittings. A fitting is a part that is used to connect pipes or tube. A fitting has a specific form (e.g. Y,T)
Specifies the form of the fitting (e.g. Y, T).
A FixingRole defines the instance specific properties and relationships of a fixing.
References theFixingSpecificationthat is instanced by thisFixingRole.
Specification for the definition of fixings. A fixing is used to fix the harness in a certain position (e.g. at the car body, a seat, an ECU etc.). The FixingSpecification describes how the fixing is attached to the "non-harness" element. The attachment to harness is described by a PlaceableElementSpecification.
Defines the properties of a flat (rectangular) conductor which are specific for them.
Defines the size (width & height) of the flat core.
TheFunctionalAssignmentGroupclusters elements that contribute to a specific function or a functional aspect. With such a group, certain functional requirements can be associated.
Functional requirements that apply to the members of this group.
Allows the definition of functional requirements in an enumerable way (e.g. conformance to a certain ASIL level). Attributes of this type have the multiplicity of [0..*]. The following restrictions apply:
The type defines to which category a requirement belongs (e.g. Functional Safety).
The reference system identifies the system in which the values are defined (e.g. ISO26262)
The value that represents the functional requirement (e.g. ASIL D).
FunctionalStructureNodescan be used to define a hierarchical structure onFunctionalAssignmentGroups. EveryFunctionalStructureNodecan referenceFunctionalAssignmentGroupsandFunctionalStructureNodesas children.
Specifies a unique identification of theFunctionalStructureNode.
Room to specify additional identifiers for theFunctionalStructureNode.
On optional human readable description of theFunctionalStructureNode.
Room for a human readable short name, title etc. of theFunctionalStructureNode.
Specification to define any hierarchical structure on functional assignment groups (e.g. by the means of a functional organization). The hierarchy starts with a single root node.
Identification of the FuseComponent, which must be distinct for all FuseComponents of an MultiFuseSpecification.
Specification of the electrological aspects of a fuse.
The geometric type of a fuse.
Specifies the maximum electric current tolerated by the fuse.
Specification for the definition of common properties for technical parts.
Specifies the color of the part.
Specifies the mass of the part.
Specifies the material of a part.
Specifies the robustness of a part.
Specifies valid temperatures for a part.
The Failures In Time (FIT) rate of a device is the number of failures that can be expected in one billion (109) device-hours of operation.[14] (E.g. 1000 devices for 1 million hours, or 1 million devices for 1000 hours each, or some other combination.) (seehttps://en.wikipedia.org/wiki/Failure_rate#Units)
Defines whether accessories which are not explicitly defined by aPartRelationmay be used with instances of this part. If this attribute is not specified the default value istrue.
Defines the bounding box of the part.
A GeometryNode is the geometric representation of a TopologyNode. A TopologyNode may be represented by more than one GeometryNodes, but only within differentBuildingBlockSpecification2D/3D.That means, in a single BuildingBlockSpecification aTopologyNodeshall only be represent once (or not).
A GeometryNode is either a GeometryNode2D or a GeometryNode3D.
Specifies a unique identification of the GeometryNode. The identification is guaranteed to be unique within the corresponding BuildingBlockSpecification. For all VEC-documents a GeometryNode-instance can be trusted to be the same if the BuildingBlockSpecification-instance is the same (see BuildingBlockSpecification) and the identification of the GeometryNode is the same.
Specifies additional identifiers for the GeometryNode.
A GeometryNode2D is the geometric representation of a TopologyNode in 2D-space.
A GeometryNode3D is the geometric representation of a TopologyNode in 3D-space.
A GeometrySegment is the geometric representation of a TopologySegment. A TopologySegment may be represented by more than one GeometrySegments, but only within differentBuildingBlockSpecification2D/3D.That means, in a single BuildingBlockSpecification aTopologySegmentshall only be represent once (or not).
Furthermore, the definition of theGeometrySegmentshall be consistent to the definition in theTopologySpecification.That means, that aGeometrySegmentshall have thoseGeometryNodesas start- & endNode that represent theTopologyNodesreferenced from the correspondingTopologySegment.
A GeometrySegment is either a GeometrySegment2D or a GeometrySegment3D.
Specifies a unique identification of the GeometrySegment. The identification is guaranteed to be unique within the corresponding BuildingBlockSpecification. For all VEC-documents a GeometrySegment-instance can be trusted to be the same if the BuildingBlockSpecification-instance is the same (see BuildingBlockSpecification) and the identification of the GeometrySegment is the same.
Specifies additional identifiers for the GeometrySegment.
A GeometrySegment2D is the geometric representation of a TopologySegment in 2D-space.
Specifies the start vector of the geometry segment. The start vector is a tangent to the segment at the start position.
Specifies the end vector of the geometry segment. The end vector is a tangent to the segment at the end position.
A GeometrySegment3D is the geometric representation of a TopologySegment in 3D-space.
Specifies the start vector of the geometry segment. The start vector is a tangent to the segment at the start position.
Specifies the end vector of the geometry segment. The end vector is a tangent to the segment at the end position.
Specifies an ordered list of curves which describe the centerline of the segment. If a segment is described by more than one curve, the centrelines of the individual curves are aligned in the order of this association.
A GrommetRole defines the instance specific properties and relationships of a grommet.
References theGrommetSpecificationthat is instanced by thisGrommetRole.
Specification for the definition of grommets.
Specifies the hardness of the grommet.
Specifies the valid diameter of a hole into which the grommet fits.
Specifies valid the plate thickness at the hole into which the grommet fits.
Specifies the type of the grommet.
The HarnessDrawingSpecification2D specifies a two-dimensional drawing of a harness. A harness drawing is composed of one or more BuildingBlockSpecifaction2D which are placed on the drawing.
The HarnessGeometrieSpecification3D specifies a three-dimensional model of a harness. A harness model is composed of one or more BuildingBlockSpecifaction3D which are placed in the model.
Specifies the type of the harness geometry.
Specifies the BuildingBlockPositioning3Ds that are forming the HarnessGeometrySpecification3D.
Specification for fixings that are mounted into a hole. This means the fixing has got a bolt which is mounted into a hole of the surrounding.
Specifies the diameter of the hole in which the fixing is mounted.
Specifies the thickness of the plate in which the hole is positioned.
Specifies the type of how the fixing is fixated in the hole. In other words, it defines what features the hole has to provide to allow a fixation of the fixing.
A HousingComponent describes the interface of an EEComponent with which it can be connected to another EEComponent or a harness. The characteristics of the interface can be described with a referenced ConnectorHousingSpecification. (see KBLFRM-300)
Identification of the HousingComponent, which must be distinct for all HousingComponents of an EEComponent.
Specifies additional, human readable information about theHousingComponent.
The values of this attribute define theHousingComponentTypesthat are valid to be associated with thisHousingComponent.In other word, if thisHousingComponentcanbe associated with a relay, a fuse, a connector housing of a harness. The values are matching thePrimaryPartTypeof thePartVersionof the component that should be associated (plugged) into this housing component.
Specifies theSegmentConnectionPointstheHousingComponent.
A HousingComponentReference represents the usage of a HousingComponent in the context of a PartUsage or PartOccurrence. (KBLFRM-401)
Specifies a unique identification of the HousingComponentReference. The identification is guaranteed to be unique within the EEComponentRole.
The IECUnit class can define quantities in the terms of the IEC-Unit-System by specifying the corresponding IEC prefix (optional) and an IEC unit name.
Specifies the name of the IEC unit.
Specifies the prefix of the IEC unit.
The ImperialUnit class can define quantities in the terms of the Imperial-Unit-System by specifying the corresponding Imperial unit name.
Specifies the name of the imperial unit.
Abstract super class to specify different types of instructions. Possible instructions are text, file or document based.
Specification for the definition of insulation properties of a WireElement.
Specifies the base color of the insulation.
Specifies the first identification color of the insulation.
Specifies the second identification color of the insulation.
Specifies the color of a label printed on the insulation of the wire.
Specifies the type of a label printed, stamped or integrated on or in the insulation of the wire (e.g. alpha numerical, bar code).
Specifies the value of a label printed on the insulation of the wire. This value applies to all wire elements that satisfy this specification, so all instances share the same label value (e.g. a wire type or a core number in a multi core wire).
If instances of a wire require individual labeling it has to be defined on theWireElementReference.
Specifies the material of the insulation.
Specifies the thickness of the insulation.
A custom property with an integer value.
Defines the value of the CustomProperty.
AnInternalComponentConnectiondefines a conductive connection betweenPinComponentswithin anEEComponent. Such a connection can be statically permanent or dynamically switch (e.g. by a relais). This behaviour can be defined with aSwitchingState.
The electrical behaviour of anInternalComponentConnectioncan be further specified by a referencedConductorSpecification.
Identification of theInternalComponentConnection, which must be distinct for allInternalComponentConnectionof anEEComponent.
An InternalTerminalConnection represents an electrical connection within a terminal. For standard terminals all receptions (wire- and terminal-receptions) have an electrical connection. For non-standard terminals (e.g. coax) only some receptions have an electrical connection. The InternalTerminalConnection is modelled as a separate class and not as relationship between wire- and terminal-reception, since it is possible that a terminal has only one kind of reception (e.g. a parallel connector, a cavity bridge). (see KBLFRM-302)
Specifies a unique identification of the InternalTerminalConnection. The identification is guaranteed to be unique within the TerminalSpecification (this might be for example an internal connection number).
Defines two or more ItemVersions to be equivalent out of the view of a certain company. The ItemEquivalence class will most likely be used by a company to express which PartNumber a certain PartVersion has in the context of other companies (same applies toDocumentVersions). However, for every other company separate ItemEquivalences are needed as the statement of equivalence can be very subjective.
Specifies the company which states the ItemEquivalence.
References all ItemVersion that are considered to be equivalent by the ItemEquivalence. A singleItemEquivalenceshall only referenceItemVersionsof the same class (eitherDocumentVersionsorPartVersions).
An ItemHistroyEntry defines the direct relationship between ItemVersions in the terms of predecessor and successor. There are two possible types of relationships between ItemVersions, derivation and sequence. Derivation means for example for parts, that the successor version is a new part developed on the base of the predecessor version. Sequence means the successor version is an improvement of the predecessor version. By the combination of more than one ItemHistoryEntry a linear sequence of ItemVersions can be represented.
Specifies the type of relationship between the ItemVersions.
Abstract super-class for physical objects (e.g. a Terminal), virtual objects (e.g. a 150% Harness) as well as documents (e.g. a wiring diagram). In difference to AP 212 the VEC makes it only possible to describe/exchange information about Versions since Master-Objects cannot exist without one or more Versions.
Room for a short name of the Item. In case of a document the attribute is wanted to contain its title.
Room for additional, human readable information about the ItemVersion. e.g. Buchsengehäuse 26-polig
Defines the publishing company of the ItemVersion. The companyName is part of the main identifier of an ItemVersion together with the corresponding number (partNumber or documentNumber) and version (partVersion or documentVersion).
Processing instructions for the application of the part or the document.
References theCopyrightInformationthat is in effect for thisItemVersion.If noCopyrightInformationis referenced by theItemVersion, theCopyrightInformationthat is referenced by theVecContent(if defined) shall be considered as in effect for thisItemVersion.
Specifies the type of a label printed, stamped or integrated on or in component (e.g. alpha numerical, bar code).
Specifies the value of a label printed on the component.
Specifies the type of a label printed, stamped or integrated on or in component (e.g. alpha numerical, bar code).
Specifies the value of a label printed on the component. This value applies to all components that satisfy this specification, so all instances share the same label value (e.g. a part number).
If instances of a component require individual labeling it has to be defined on the LabelingRole.
ALocalGeometrySpecificationis responsible to create a relationship between the 3D model of a component (e.g. a connector, a cable duct or a fixing) and entities of the VEC. The 'Local' in the name refers to the fact that all definitions within this specification are 'local' to the 3D model of a specific component (a component in a library, not in a specific usage).
Specifically, it defines a transformation to transform theBoundingBoxof a component into to coordinate system of the component and it defines the positions ofPlacement-andMeasurementPointsin this coordinate system.
TheUnitin which all coordinates (e.g. cartesian points) are defined. Shall be a unit of length (e.g. millimetre).
The transformation that defines the positioning of the bounding box in coordinate system of the component.
AllCartesianPoint3Dsthat are used in thisLocalGeometrySpecification.AllCartesianPoint3Dsare defined in relation to the coordinate system of the component.
All position defined by thisLocalGeometrySpecification.
ALocalPositiondefines the position of a relevant point of component within the coordinate system of the component.
Allows the internationalization of text contents. Attributes of the type LocalizedString normally have the multiplicity [0..*]. This means that such an attribute can have multiple values for different locales. It must not have multiple values for the same locale.
Defines the value of theCustomProperty.
Defines thetypeof theLocalizedTypedString. This allows the definition of a more detailed semantic than the semantic of the attribute itself with the typeLocalizedTypedString.Agreed type values are defined in an OpenEnumeration.
A Location specifies a distinct position on a topology. Locations can be used for the placement of components or for the definition of Dimensions.
Specifies a unique identification of the Location. The identification is guaranteed to be unique within the PlacementSpecification.
Specifies an identification for matching the location with a reference point of component (e.g. a cable channel).
References thePlacementPointReferencethat is placed by this location.
The Mapping defines the concrete mapping two parts aliased as A & B. For performance reasons the roles PartSideA and PartSideB are abbreviated to A & B.
Specification for the description of a PinMapping. A PinMapping allows the mapping between the Cavities of two independent ConnectorHousingSpecifications. This is for example needed to determine the Mating for an Inliner or for the Mating between an EE-Component and a ConnectorHousing. The PinMapping is a part master data.
Allows the definition of mass information. Attributes of the type MassInformation normally have the multiplicity [0..*]. This means that such an attribute can have mass values for different determinationTypes and valueSources. It must not have multiple values for the same determinationType and valueSource.
Specifies the determination type of the mass information.
Specifies the mass as numerical value.
ThevalueSourcedefines in an OpenEnumeration the source from which theMassInformationhas been retrieved. This information, in combination with theValueDeterminationgives a hint about the reliability of theMassInformation
Allows the definition of material information. Attributes of the type Material normally have the multiplicity [0..*]. This means that such an attribute can have material values for differentreferenceSystems. It must not have multiple values for the samereferenceSystems.
The key of the material in the corresponding material reference system.
The identification of the material reference system, which is defining possible values and the semantic of material keys.
On optional human readable description of the material (e.g. the name).
If the mating of the two terminals is not unambiguously, a MatingDetail can specify the TerminalReceptions that are mated.
References theConnectionthat is realized by thisMatingPointDetail .For example, when a connection is realized by directly plugging or screwing two E/E components together.
The definition at level of theMatingDetailmight be required if theTerminalRoleof the MatingPoint carries multiple different potentials (e.g. Coax).
A MatingPoint defines the Mating of two terminals. This normally occurs when two inliners are connected. Then terminals of one side (female) are mated with terminals of the other side (male).
Specifies a unique identification of theMatingPoint. The identification is guaranteed to be unique within aCouplingPoint.
References theConnectionthat is realized by thisMatingPoint .For example, when a connection is realized by directly plugging or screwing two E/E components together.
Defines the position of a MeasurementPoint within the coordinate system of the component. MeasurementPoint onto which dimension can be defined.
Defines a reference point on a component that can be used to apply a Dimension. This is normally a significant point of the component e.g. an edge, a hole, a bolt or something similar.
Specifies a unique identification of the MeasurementPoint. The identification is guaranteed to be unique within a component.
AMeasurementPointReferenceis the instance of aMeasurementPointin the context of anOccurrenceOrUsage.
Specifies a unique identification of the MeasurementPointReference. The identification is guaranteed to be unique within the containing PlaceableElementRole.
References theMeasurementPointthat is instanced by thisMeasurementPointReference.
A ModularSlot is a place in a connector housing where different other connector housings can be placed during the assembly (e.g. by clicking them into the connector housing).
Specifies whether the allocation of the ModularSlot is optional or not (can a usage of the connector housing leave this ModularSlot empty.
References thePartRelationsthat are valid inserts for thisModularSlot.
This reference points toPartRelationsin order to allow referencing indirectly aPartVersionif the description of individualPartVersionsis done with one physical VEC file perPartVersionand to allow the expression of optional inserts, choices etc. However, inserts for aModularSlotare always ConnectorHousings by itself. Therefore, the referencedPartVersionshall have aPrimaryPartType = ConnectorHousing
Specifies the wire addon needed to reach aModularSlotfrom a specificSegmentConnectionPoint. The addon needed to reach the cavities of the insert(s) from this point is defined by theConnectorHousingSpecificationof the insert.
Specifies the wire length add on needed for the modular slot.
AModularSlotReferencerepresents the usage of aModularSlotin the context of PartUsage or PartOccurrence.
References the inserts that are used in thisModularSlotReference.More than one insert is valid in the case variant dependent equipment of the slot.
A ModuleFamily is a mechanism to group mutually exclusive modules. This could be for example something like "audio equipment", "diesel engine".
In other words, a module family groups different variants of the same basic feature. In a real car configuration only one member of the family can participate. For the example module family "audio equipment" the members may be named: "Basic Audio Equipment", "Standard Audio Equipment", "Premium / High End Audio Equipment".
Specifies a unique identification of the ModuleFamily. The identification is guaranteed to be unique within the ModuleFamilySpecification. For all VEC-documents a ModuleFamily-instance can be trusted to be the same if the ModuleFamilySpecification-instance is the same and the identification of the ModuleFamily is the same.
Room for additional, human readable information about the ModuleFamily.
Specification for the description of module families (see ModuleFamily).
A ModuleList is a mechanism to control additional / completion PartOccurrences. This means for a car configuration, if at least one of the modules in the list participates in the configuration, the "completionComponent" participates, too.
Specifies a unique identification of the ModuleList. The identification is guaranteed to be unique within the ModuleListSpecification. For all VEC-documents a ModuleList-instance can be trusted to be the same if the ModuleListSpecification-instance is the same and the identification of the ModuleList is the same.
Room for additional, human readable information about the ModuleList.
Specification for the description of module lists (see ModuleList).
Specification for the definition of cavity plugs that apply to more than one cavity. A cavity plug is a watertight non-electrical object to fill an empty cavity. MultiCavityPlugs are formed to fit into one connector / slot and to seal more than one cavity at once. Normally there are different variants of these MultiCavityPlugs that can seal a connector in different pinning scenarios. The cavities that are plugged by a MultiCavityPlug are defined with a SealedCavitiesAssignment.
References theSealedCavitiesAssignmentsthat are valid for thisMultiCavityPlug. One individualSealedCavitiesAssignmentis used for each connector housing that matches witch thisMultiCavityPlug.
Specification for cavity seals that apply to more than one cavity. A CavitySeal is a watertight non-electrical object to fill a populated Cavity. MultiCavitySeals are formed to fit into one connector / slot and to seal more than one cavity at once.
There are existing two types of MultiCavitySeals:
The cavities that are left open by a MultiCavitySeal are defined with a SealedCavitiesAssignment.
References theOpenCavitiesAssignmentsthat are valid for thisMultiCavitySeal. One individualOpenCavitiesAssignmentis used for each connector housing that matches witch thisMultiCavitySeal.
Defines the manufacturing types of a Multi-fuse.
Specifies the maximum electric current tolerated by the multifuse in total.
Represents a control point of aNURBSCurve.It consists of a referencedCartesianPoint3Dfor the position and aweight.
The weight of the NURBSControlPoint.
TheCartesionPoint3Dthat defines the position of thisNURBSControlPoint.
The NURBSCurve represents the parameter set of a NURBS (Non-Uniform rational B-Spline) in the VEC. For a complete definition of NURBS see for example (https://en.wikipedia.org/wiki/Non-uniform_rational_B-spline).
Basically, a NURBS curve is defined by:
Commonly used default assignments for the parameters are:
The VEC NURBSCurvecorresponds to removedBSplineCurve(VEC Version <= 1.1.3 and KBL). However, theBSplineCurvedid not define weight and knot vector, so default assignments where assumed. Existing implementations are using "uniform non-rational b splines", unfortunately some implementations use "uniform clamped" and some "unclamped".
Since a NURBS cannot be rendered correctly without the knowledge of all parameters and to avoid further misconceptions the VEC allows the definition of all parameters of a NURBS. Furthermore, it requires the specification of all parameters, even if some known default assignment (e.g. non-rational) is used.
Defines the degree of the NURBS (for details see the class description ofNURBSCurve).
Defines the knot-vector of the NURBS(for details see the class description ofNURBSCurve).
Defines the control points of the NURBS curve (for details see the class description ofNURBSCurve)
A Net is an undirected link betweenNetworkPorts. It defines that theNetworkPortsare related to each other with theNet.
ANetis normally an instance of aNetType. E.g. if "CAN-BUS" is defined as aNetTypetypicalNetswould be "BODY-CAN", "AUDIO-CAN".
Specifies a unique identification of the Net. The identification is guaranteed to be unique within the NetSpecification.
Room for additional, human readable information about the Net.
Defines a logical grouping of specificNets. For example, it can be used to identify allNetsof specific CAN domain, a function, a requirement level (e.g. Safety & Security).
Specifies a unique identification of the NetGroup. The identification is guaranteed to be unique within the NetSpecification.
Specifies the type of the group.
Room for additional, human readable information about the NetGroup.
Specification for the description of electrological nets.
Specifies the NetworkNodes defined in the NetSpecification.
ANetTypedefines the different types of Nets used in theNetSpecification. The level of detail of theNetTypesfor the can be process dependent.
A NetType could be just used to differentiate between conventional (analogue) communication and bus communication (digital), it can also already define the different types of digital communication (e.g. CAN, MOST, Ethernet).
Specifies a unique identification of the NetType. The identification is guaranteed to be unique within the NetSpecification.
Room for additional, human readable information about theNetType.
Specifies the type of the transmission medium for signals of this type.
TheNetViewSpecificationsupports the exchange of a basic layout for aNetSpecification.
A NetworkNode is a representative for an actor in the electric system, e.g. an actuator, a sensor, an ECU
Specifies a unique identification of the NetworkNode. The identification is guaranteed to be unique within the NetSpecification.
Room for a short name of the NetworkNode.
Specifies the type of a NetworkNode. Common values are agreed as anOpenEnumeration.
Room for additional, human readable information about the NetworkNode.
Specifies the sub type of a NetworkNode. The sub type allows a differentiation within a specific type. E.g. an actuator can be differentiated into lamps, speakers, motors.
References theUsageNodethat is realized by thisNetworkNode.
Specifies a unique identification of theNetworkNodeViewItem. The identification is guaranteed to be unique within theNetViewSpecification.
Specifies the grid square in which theNodeViewItemis placed (e.g. E/40).
Specifies allNetworkPortViewItemsthat are displayed on thisNetworkNodeViewItem.The order of this association defines the clockwise arrangement of the ports on the node. As eachNetworkPortViewItemcan also define the side on which it is placed, side definitions take precedence over order.
Caution:This association isordered!
NetworkPort is the source or the receiver of a of a Net.
Specifies a unique identification of the NetworkPort. The identification is guaranteed to be unique within the NetSpecification.
Specifies the direction of the signal on this NetworkPort.
Room for additional, human readable information about the NetworkPort.
Specifies a TopologyNode as a Location.
References the TopologyNode on which the Location is located.
Defines the relationship of an inner node to its outer topology. The relationship to the outer topology is expressed with aLocation.
A quantity expressed with a numerical value and a unit.
Specifies the value of the numerical value.
A custom property with a numerical value. (see KBLFRM-319)
Defines the value of theCustomProperty.
An OccurrenceOrUsage is an abstract appearance of a part in the harness. This can either be a concrete part (with a part number or something similar) or the description (specification / requirements) of a part that should be used at that position. In the first case it would be a PartOccurrence in the second case a PartUsage.
Specifies a unique identification of the OccurrenceOrUsage. The identification is guaranteed to be unique within the context. For all VEC-documents an OccurrenceOrUsage-instance can be trusted to be the same if the context-instance is the same and the identification of the OccurrenceOrUsage is the same.
Room to specify additional identifiers for the OccurrenceOrUsage.
Specifies an abbreviation of theOccurrenceOrUsage. Normally this a human readable short name.
Specifies additional, human readable information about the OccurrenceOrUsage.
References theUsageNodethat is realized by thisOccurrenceOrUsage.
References theOccurrenceOrUsagefor which thisOccurrenceOrUsageis an accessory / supplementary component. If anOccurrenceOrUsagedefines more than onereferenceElement, the semantic is that it is related to the combination all "reference elements" and not to each individually. In other words, in a variable product definition theOccurrenceOrUsageonly exists if allreferenceElementsexist.
Specifies the different roles of the OccurrenceOrUsage.
An OccurrenceOrUsageViewItem2D specifies the representation of an OccurrenceOrUsage in a 2DDrawing.
Specifies a unique identification of the OccurrenceOrUsageViewItem2D. The identification is guaranteed to be unique within the BuildingBlockSpecification2D.
Specifies additional identifiers for the OccurrenceOrUsageViewItem2D.
Specifies the grid square in which the OccurrenceOrUsageViewItem2D is placed (e.g. E/40).
Specifies theOccurrenceOrUsageswhich are represented by the view item.
Important:To use oneOccurenceOrUsageViewItemfor multipleOccurrenceOrUsagesis only valid, if the referenced items are true alternatives to each other. That means, they must have an identical placement, the geometrical models used for each item must be substitutable and the item must be mutually exclusive to each other.
AnOccurrenceOrUsageViewItem3Dspecifies the existence and representation of anOccurrenceOrUsagein a 3D-model.
The definition of the existence is necessary because a 150% model of a harness might contain different geometric variants and not all of them must be represented in the sameBuildingBlockSpecification3D.
There are two different cases for the representation ofOccurrenceOrUsages in a 3D model. There are components that can be represented explicitly by a 3D model of the component (e.g. connectors, cable ducts, fixings) and there are components that are represented implicitly by a generic visualization and their placement on the topology (e.g. tapes, tubes). If an OccurrenceOrUsage has a 3D model and it shall be placed explicitly in 3D space, theOccurrenceOrUsageViewItem3Ddefines aTransformation3Din theorientationrole. If noorientationis defined theOccurrenceOrUsageis represented implicitly.
Specifies a unique identification of the OccurrenceOrUsageViewItem. The identification is guaranteed to be unique within the BuildingBlockSpecification3D.
Specifies additional identifiers for the OccurrenceOrUsageViewItem3D.
Specifies theOccurrenceOrUsageswhich are represented by the view item.
Important:To use oneOccurenceOrUsageViewItemfor multipleOccurrenceOrUsagesis only valid, if the referenced items are true alternatives to each other. That means, they must have an identical placement, the geometrical models used for each item must be substitutable and the item must be mutually exclusive to each other.
An OnPointPlacement is a placement of an OccurrenceOrUsage that places it onto discrete points, in most cases one point. In some cases, it is necessary to place a component (with more than one reference point) onto multiple points (e.g. a cable duct).
An OnWayPlacement places an OccurrenceOrUsage onto an area of the Topology (e.g. a tape or a tube). The area is defined by a startLocation and an endLocation. If startLocation and endLocation are not located on the same TopologySegment it is possible to specify a Path of TopologySegments over which the OnWayPlacement goes.
The names start- and endLocation are used to distinguish between the two ends. It does not indicate a direction as property of the product (e.g. for tapes).
An OpenCavitiesAssignment groups the cavities of ONE connector that are open in a MultiCavitySeal. If a MultiCavitySeal fits into more than one connector, than there are as many OpenCavitiesAssignments.
Specifies the cavities that are open.
An OpenWireEndTerminalRole defines the instance specific properties and relationships of an open wire end.
Specification for the definition of open wire ends. An open wire end is an end of wire located at a specific location in the harness. Open wire ends are not connected to some other component, in contrast to regular connectors or ring terminals. Only one wire is ending at a single open wire end, otherwise it would be a splice.
The OtherUnit class can be used to define a unit, which is necessary in the context of data exchange but not contained in the standard systems (e.g. Piece).
Specifies the name of the unit.
A PartOccurrence is an instance of a component with a specified part number (PartVersion).
If a PartUsage is realized by more than one PartOccurrence it is possible to specify which one is the preferred. (see KBLFRM-264)
References the PartOccurrences that are an alternative for this PartOccurrence.
References the PartOccurrence which is instantiated by the PartOccurrence. This reference is for example needed in the case of usage of assemblies.
References the PartVersion that is instantiated by this PartOccurrence.
Base class for all specifications which are describing aPartVersionor aPartUsage. APartOrUsageRelatedSpecificationspecifies a certain aspect of the described part or usage (e.g. general technical part information, connector housing aspects or wire aspects).
The specialPartType allows the specification of subclassifications for a PartOrUsageRelatedSpecification (e.g. different types of connector housings).
APartRelationdefines additional parts (e.g. accessories) for a specific part. These parts are in some way or usage scenario required for the part itself to be used. However, they are not included with the part number and have to ordered separately. This can be used for example for caps, cable ties etc.
The associatedPartRelationsof aGeneralTechnicalPartSpecificationrepresent a configurable bill of material that can/must be ordered together with the part, when it is used. EachPartRelationrepresents an item / line in this bill of material. The semantic by which aPartRelationis resolved toPartVersionsis defined by thePartRelationType.If multiplePartRelationsresolve to the samePartVersionsthe resulting bill of material is the sum of them.
If aPartRelationreferences more than oneaccessoryPartthePartRelationTypedefines the semantic to resolve this reference for a resulting bill of material. If the type isMandatoryall referencedPartVersionsshall be in the resulting bill of material. If the type isOptional, the referencedPartVersionscan be selected by choice into the resulting bill of material. However, the choice applies toall PartVersions of onePartRelation.ForMandatoryit is semantically equivalent to haveone PartRelationreferencingN PartVersionsor to haveN PartRelations, each referencingone PartVersion.ThePartRelationType OneOfAlldefines, that exactlyoneof the referencedPartVersionsshall be chosen for the resulting bill of material.
If the samePartVersionis referenced multiple times, each reference counts as its own position.
Example: To express that aPartVersionshall be used at least three times and with a maximum of 6 times, three mandatory and three optionalPartRelationsto thisPartVersionwould be created.
With these concepts, simple yes/no decisions can be represented. However, there cases where there are constraints between accessory parts (e.g. if part A, then choice of 2 x B or 1 x C). To express such logic in a static object model is not very feasible and inflexible. For such cases, therelationType 'Custom'was introduced. In this case, the relationships and constraints between all referencedaccessoryPartcanbe expressed with some custom expression language in thecustomRelationExpressionattribute. Even if it is custom, the expression shall only refer to elements that are contained in theaccessoryPartrelation and shall not influence otherPartRelationsof the sameGeneralTechnicalPartSpecification.
Specifies the type of the relation.
Defines the relationship between the accessory parts in a proprietary expression language. This attribute shall only be used, if therelationType = 'Custom'.
Specification for the description of a part structure. This specification defines the PartOccurrences that are in the bill of material of the described PartOrUsage. This is necessary, because it is possible, that for a definite description a Part more PartOccurrences are needed than the ones that are in the bill of material (see CompositionSpecification).
Specifies the type of content of the bill of material (e.g. module, harness complete set)
References the PartOccurrences that are building the bill of material of a composite part.
APartSubstitutionSpecificationdefines a set ofPartVersionsthat can be used alternatively, due to an incomplete specification for the 150% product description. For a concrete wiring harness only on validPartVersionremains. The selection logic for validPartVersionsis not included in the VEC.
APartSubstitutionSpecificationcan be used for example tubes or ring terminals, where a part of the specification is known at design time, but not yet the complete specification. For tubes for example the tube diameter is not known at design time, since it depends on the bundle diameter of a specific configuration.
PartUsages shall be used for the specification of the elements on an electrical system wiring plan and for the specification of the elements on a pure geometry description. PartUsages shall more than ever be used in cases where it is necessary to describe a certain instance of a part or part group, possibly together with certain technical properties, but where it is at the same time yet not possible to define a concrete part number.
The primary type of the PartUsage defines the type of the described part (e.g. ConnectorHousing, Fixing, etc.) Since the VEC supports dual use parts (e.g. Fixing & WireProtection) there is no direct connection between the primaryPartUsageType and the allowed specifications for the description of a PartUsage.
Specification for the definition of PartUsages.
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 elements are normally referencing to the PartVersion.
The partNumber is the major identifier of a PartVersion. The format is user defined and respectively company specific. For all VEC-documents a PartVersion-instance can be trusted to be identical if the combination of partNumber, partVersion and companyName is identical.
The partVersion specifies the version index of a part (see also partNumber).
The primary type of the part defines the type of the part (e.g. ConnectorHousing, Fixing, etc.) Since the VEC supports dual use parts (e.g. Fixing & WireProtection) the primary part type is necessary to define which specification associated to part is the primary character of the part. Therefore, all primary part types correspond to a PartOrUsageRelatedSpecification (e.g. ConnectorHousing --> ConnectorHousingSpecification).
Flags a part as "preferred" by the means of being a preferred part out of a group of parts with identical technical properties. The preferred part should be used, if the other properties of a couple of parts do not allow a distinct decision.
Even though the name suggests a boolean value, this attribute has the type "string". The way in which preference is expressed varies greatly between the process and usually it is a multi-value flag and not just a yes/no answer.
Contains a part description from the point of view of the preferred use case. Defines the function for which the part was initially designed. (e.g. "Grommet for Hatch", "...passenger compartment"). This can be an important information for searching and selecting parts.
Room to specify additional identifiers for the PartVersion. This field must not be used for alternative PartNumbers. It is intended for identifiers others than PartNumbers, such as human readable identifiers printed on the part e.g. a number of fuse or a relay. Therefore, it does not have to be strictly unique.
Thenaturespecifies how thePartVersioncan be used in the different processes or the significance of thePartVersionin the process.
Thenatureof aPartVersionis normally inherent and does not change. If thenaturethe underlying part changes a new (other)partNumberis assigned to the part and respectively a newPartVersionis created.
It used to differentiate for example normal (productive) part numbers from preliminary (prototypic) part numbers.
A PartWithSubComponentsRole defines the instance specific properties and relationships of a part with subcomponents. A PartWithSubComponents is a composite part like an Assembly, a Module, Harness.
References thePartStructureSpecificationthat is instantiated by thisPartWithSubComponentsRole.
References the subcomponents that belong to this instance of a PartWithSubComponents.
Describes a path in the topology. APathis a continuous way through a topology without interruptions, defined by an ordered list ofTopologySegments.
A PathSegment is a part of the 2D presentation of a GeometrySegment2D. The complete presentation of a GeometrySegment2D is built from an ordered list of PathSegments. Each PathSegment has an ordered list of control points through which the path goes. If no curveRadius is specified the control points are connected by a direct straight line. If a curveRadius is specified, the PathSegment can be drawn by a segment of a circle which touches all control points and has the radius specified.
The radius of the curve which describes the appearance of the path segment.
Describes an act of acceptance together with information about the responsible person, department and company who directly provoked the approval level and status as described in the referenced Approval-instance. (see KBLFRM-229)
Specifies the type of permission. Predefined values are: Seen, Checked, Released.
Specifies the date when the permission was stated.
Specifies the person who was involved in the approval process giving a certain Permission.
Specifies all relevant data of a person.
Specifies the name of the company the person belongs to.
Specifies the department the person belongs to.
Specifies the person's first name.
Specifies the person's last name.
Specifies the person's phone number.
Specifies the person's email address.
Specifies identifiers for thePersonin different contexts.
A PinComponent describes a pin of an EEComponent. A PinComponent is part of a HousingComponent and is defined by tree aspects.
Identification of the PinComponent, which must be distinct for all PinComponent of a HousingComponents.
Specifies additional, human readable information about thePinComponent.
Specifies the type of aPinComponent.
Specifies the configuration dependent electrical behavior of thePinComponent.
APinComponentBehaviorspecifies the electrical behavior of aPinComponent.Since the behavior of a pin is configuration dependent (e.g. the software deployed on an ECU) thePinComponentBehaviorinherits fromConfigurableElement.Therefore, aPinComponentcan specify multiplePinComponentBehavior.
Identification of the PinComponentBehavior which identifies it from a user perspective, and which must be distinct for all PinComponentBehaviors of a PinComponent.
The direction of the signal on this pin.
Specifies thePinTypeof thePinComponent.
Classifies the appliance of a Pin in terms of the duration of the appliance (see PinApplianceType).
Specifies additional, human readable information about thePinComponentBehaviour.
Specifies theSignalassociated with the pin in this behavior.
Specifies the current information of thePinComponentin thisPinComponentBehavior. Since the current values of a pin can be defined for different types and times it is possible to define multiplePinCurrentInformationsfor aPinComponentBehavior.
Specifies the optical information of the pin, if it has the type optical.
Specifies the voltage information of thePinComponentin thisPinComponentBehavior. Since the voltage values of a pin can be defined for different types and times it is possible to define multiplePinVoltageInformationsfor aPinComponentBehavior.
A PinComponentReference represents the usage of a PinComponent in the context of a PartUsage or PartOccurrence. (KBLFRM-401)
Specifies a unique identification of the PinComponentReference. The identification is guaranteed to be unique within the HousingComponentReference.
Allows the definition of currents for a pin of an EEComponent. A current can be further specified by a duration. Attributes of the type PinCurrentInformation normally have the multiplicity [0..*]. This means that such an attribute can have PinCurrentInformation entries for different types and durations. It must not have multiple entries for the same type and duration.
Defines the type of the current.
The current of the pin.
Specifies the timing of thePinCurrentInformation.
Allows the specification of optical information in a PinComponentBehavior.
The frequency of the optical signal.
The attenuation of the optical pin at the defined frequency.
Specifies the timing for aPinCurrentInformationor aPinVoltageInformation.
Specifies the type of the timing.
Specifies the time value of the timing.
Allows the definition of voltages for a pin of anEEComponent. A current can be further specified by a duration. Attributes of the typePinVoltageInformationnormally have the multiplicity [0..*]. This means that such an attribute can havePinVoltageInformationentries for different types and durations. It must not have multiple entries for the same type and duration.
Defines the type of the voltage.
The voltage of the pin.
Specifies the timing of thePinVoltageInformation.
ThePinWireMappingPointcreates a single variance free mapping between aContactPointand aPinComponentReferencewithin aPinWireMappingSpecification(more details there).
APinWireMappingSpecificationcan be used createvariance freemappings between a wire (represented by the contact point) and the pin of an E/E component. This is a possibility to create a shortcut in the model between a wire and its connected E/E-component (e.g. a fuse) that might be only indirectly connected to a wire (e.g. via a fuse and relay carrier). This is a relevant information for e.g. the validation of fusing. See the Pin Wire Mapping Diagram for more details.
A PlaceableElementRole defines the instance specific properties and relationships of a PlaceableElement.
References thePlaceableElementSpecificationthat is instanced by thisPlaceableElementRole.
Specification for the general aspects of a component that are enabling the component to be placed in a topology. All components that should have the ability to be placed on a certain position in the topology must have a PlaceableElementSpecification
Defines thePlacementTypesthat are valid for this element.
Specifies theMeasurementPointsof aPlaceableElement.
Specifies thePlacementPointsof aPlaceableElementSpecification.
A placement defines the placement of a PlaceableElementRole onto a Topology. For the definition of the place on the Topology, Locations are used. A Placement can either be a placement on discrete points (OnPointPlacement) or on an area of the topology (OnWayPlacement).
Specifies a unique identification of the Location. The identification is guaranteed to be unique within the PlacementSpecification.
Room to specify additional type information of the placement.
Defines a point on the component which can be placed explicitly in the topology (e.g. opening in a grommet, the entry point of a connector housing). If a PlacementPoint requires further specification for a certain component type (e.g. the entry point of a connector housing), this is done by an element specific for the component type, which related to the placement point.
Specifies a unique identification of the PlacementPoint. The identification is guaranteed to be unique within a component.
Specifies the valid segment diameter range for which thisPlacementPointis suitable.
References thePartRelationsthat specify supplementary parts for thisPlacementPoint, e.g. cable ties for attaching the component on the harness.
Defines the position of a PlacementPoint within the coordinate system of the component. PlacementPoints are points where a component is attached to aTopologySegment.Therefor aPlacementPointPositioncan define a tangent vector (in the coordinate system of the component) for a segment that is connected to thePlacementPoint.
A vector in the direction of the tangent on theTopologySegmentthat is attached to thePlacementPointrepresented by this instance. The vector is defined in the coordinate system of the 3D model of the component.
APlacementPointReferenceis the instance of aPlacementPointin the context of anOccurrenceOrUsage.
Specifies a unique identification of the PlacementPointReference. The identification is guaranteed to be unique within the containing PlaceableElementRole.
References thePlacementPointthat is instanced by thisPlacementPointReference.
Specification for the description of placements.Placementsare used to connectOccurrenceOrUsageswith a topology.
A PluggableTerminalRole defines the instance specific properties and relationships of a pluggable terminal.
Specification for the definition of pluggable terminals.
Defines the type of the terminal. The type defines constraints about the numbers of wire and terminal receptions and their relations.
Specifies the properties of a potential distributor (e.g. a joint connector).
Defines if thePotentialDistributorcan be screwed by itself to be fixed. This fixation is a non-electrical connection. If thePotentialDistributorcan be fixated electrical (like a ring terminal) it shall have onePinComponentwith aRingTerminalSpecification.
Specifies the diameter of the bolt for which the potential distributor is designed for.
Defines the size (diameter) of the bolt for which the potential distributor is designed for in a nominal way (e.g. "M8").
Specifies the type of the bolt to which the potential distributor is compatible.
Defines the power consumption of anEEComponent. AnEEComponentcan have multiple differentPowerConsumptionse.g. standby, maximum. AnEEComponentcan have multiplePowerConsumptionsbut must not have more than onePowerConsumptionsof the sametype.
The type of aPowerConsumption. This should be an enumeration of values defined in a conformance class.
Specifies the power consumption for this type ofPowerConsumption.
Specifies a certain vehicle project. Instances of this class are assumed to be constant. Thus, this is located directly under VEC-root element.
A vehicle project can be some abstract or concrete node in the product structure, addressed by the car classification levels.
Provides a classification according to "CC8 Recommended Practices Specification and Configuration, Product Structures". Car classification is the identification of a set of similar cars to be offered to the market. Level 2 stands for "Technical information / platform" and reflects the level of a product class in a BoM system which represents a main technical product base (e.g. project, platform, engineering series etc.). In some cases, this level carries a complete BoM ("Maximum BoM") for a project, platform, engineering series etc. This level is in some cases called technical documentation.
Provides a classification according to "CC8 Recommended Practices Specification and Configuration, Product Structures". Car classification is the identification of a set of similar cars to be offered to the market. Level 3 stands for "Configuration information / product family" where all variant control mechanisms are attached.
Provides a classification according to "CC8 Recommended Practices Specification and Configuration, Product Structures". Car classification is the identification of a set of similar cars to be offered to the market. Level 4 stands for "Furthest pre-configured abstract product class" and represents the furthest configured class of a product, which is not yet a real product. E.g. this could be a complete vehicle, engine, gearbox etc. which has not been evaluated against customer special choices or an abstract vehicle, engine, gear-box etc. which could become a real one after the associated BoM is evaluated. The purpose of this level of a product class instance is in any case to reflect that level of product class of a BoM system which leads to the individual BoM for a single product.
Specifies the development order number (car or engine project)
Room for additional information about the item.
Defines the material length of aWireProtectionRole. AWireProtectionRolecan have multiple lengths of different types but must not have more than one length of the same type.
Specification of the electrological aspects of a relay.
Specifies the maximum current allowed for the relais.
The type of the relay (switching behaviour). This is an OpenEnumeration, for values seeRelaisType.
Defines if the relais switch with low noise / silently or not.
Specifies the appliance type of a relais.
ARequirementsConformanceSpecificationcan be used to express the conformance of aPartVersion(or a group ofPartVersions). ThePartVersionsto which thisRequirementsConformanceSpecificationapplies are expressed through thedescribedPartreference.
ARequirementsConformanceStatementstates that thePartVersionsreferenced by the parentRequirementsConformanceSpecificationsatisfy or do not satisfy the requirements defined in the associatedDocumentVersion(via therequirementsSpecificationassociation).
Defines if thedescribedPartssatisfy (satisfy = true) or explicitly fail (satisfy = false) to conform with therequirementsSpecification.
A free text description / additional information / comment for theRequirementsConformanceStatement.
References theDocumentVersionthat contains the requirements to which a conformance statement shall be expressed.
A RingTerminalRole defines the instance specific properties and relationships of a ring terminal.
Specification for the definition of ring terminals. These are the counterparts to bolt terminals.
Specifies the diameter of the bolt for which the ring terminal is designed for in a numerical way.
Defines the size (diameter) of the bolt for which the ring terminal is designed for in a nominal way (e.g. "M8").
Specifies the thickness of the contact surface of the ring terminal.
Specifies the type of the bolt to which the ring terminal is compatible.
Specifies the diameter of the circle around the center of the bolt which passes through the farthest outside point of the contact surface of the ring terminal. (see KBLFRM-311)
Specifies if the ring terminal is torsion protected or not. (see KBLFRM-311)
Allows the definition of robustness properties. Robustness of a component is specified as a level of robustness against a specific influence (e.g. oil, water, UV-light). The influence is specified by theclassand the level is specified by theclassKey. Valid robustness classes and keys are specified by the reference system. Attributes of the type RobustnessProperties normally have the multiplicity [0..*]. This means that such an attribute can have RobustnessProperties entries for differentclassReferenceSystemsandclasses.
Constraints for the multiplicity of entries for the sameclassandclassReferenceSystemare defined by the reference system. It most cases an element can have only one single value for aclassandclassReferenceSystem.This applies for example to cumulative ratings where a "higher" rating includes all "lower" ratings. However, there are reference systems where this is not true, for example in the "ISO 20653 - Liquid Ingress Protection" a component rated as IPX7 is not automatically rated IPX5 and vice versa. In these case, multiple values (classKey) for a singlec lassandclassReferenceSystemare allowed.
Note: Most reference systems just define one class or at least some of the possible classes, but not all (e.g. the ISO 20653 defines "Solid Particle Protection" and "Liquid Ingress Protection", whereas the ISO 6722 defines "Ambient Temperature" among others).
Specifies the identifier of a robustness class defined by the robustness class reference system. Robustness classes are for example: oil, petrol, UV, water. Specific known and used classes are defined in an open enumeration.
Specifies a key for the robustness level defined in the specified robustness class (e.g. A, B, C). The classKey is the key as specified in the reference system and no additional syntax or prefixes, e.g. for ISO 20653 (Ingress Protection) it is"9K"and not"IPX9K".
The identification of the robustness class reference system, which is defining possible values and the semantic of robustness classes and robustness class keys. Specific known and used reference systems are defined in an open enumeration.
Specifies if the described element has a robustness in the specified robustness class. (see KBLFRM-260)
On optional human readable description of the robustness (e.g. the name).
A Role is the corresponding mechanism for OccurrenceOrUsages to the PartOrUsageRelatedSpecifcations for PartVersions or PartUsages. The PartOrUsageRelatedSpecifcations are describing a certain aspect of the master data of a part. A Role describes the corresponding properties and relationships for instances of a part (e.g. the usage specific properties of a wire occurrence like the length or the contacting).
Specifies a unique identification of the Role. The identification is guaranteed to be unique within the OccurrenceOrUsage.
A RoutableElement is an element that can be routed, which mean it is possible to assign it to a Path in the Topology.
A Routing is the assignment of a RoutableElement (Connection or WireElementReference) to a path in the topology.
Specifies a unique identification of the Routing. The identification is guaranteed to be unique within the RoutingSpecification.
Allows the specification of an explanation why this routing has been routed in a special way.
Specifies that routing has been created in a special way. This means it has not been calculated in the standard way, because for some reason the result of the standard calculation has been inconvenient.
Specification for the description of Routings.
The SIUnit class can define quantities in the terms of the SI-Unit-System by specifying the corresponding SI prefix (optional) and a SI unit name. The usage of SI units must be the preferred way of expressing units, since these units can be easily translated into other SI units.
Specifies the name of SI unit (e.g. metre, second,...)
Specifies the prefix of the SI unit (e.g. milli, centi, mirco,...)
ASealedCavitiesAssignmentgroups the cavities of ONE connector that are sealed by a MultiCavityPlug. If a MultiCavityPlug fits into more than one connector, than there are as manySealedCavitiesAssignments.
Specifies the Cavities that are sealed.
Specifies a point where the connector can be attached to the topology (sometimes called bundle position point or insertion point).
Specifies a unique identification of the SegmentConnectionPoint. The identification is guaranteed to be unique within the ConnectorHousingSpecification.
Specifies thePlacementPointthat represents thisSegmentConnectionPointin aPlaceableElementSpecification.
Specifies theCavitiesthat are reachable with wires through thisSegmentConnectionPoint.
Specifies a point where theHousingComponentcan be attached to the topology [if required] (sometimes called bundle position point or insertion point).
Note: The suffix HC is justified by the fact that class names must be unique within the model and the name SegmentConnectionPoint is already used within the ConnectorHousingSpecification. However, the represented semantics of the two connection points are so similar that the use of actually different names for both would rather have led to confusion. So SegmentConnectionPointHC actually is short hand for "SegmentConnectionPoint within HousingComponent".
Specifies thePlacementPointthat represents thisSegmentConnectionPointin aPlaceableElementSpecification.
Specifies the cross-section area of a segment. For the data exchange the cross-section area is used and not the diameter, because the diameter is only a valid measure for circular segments. For circular segments, the diameter and the cross-section area can be translated into each other without the loss of information. Attributes of the type SegmentCrossSectionArea normally have the multiplicity [0..*]. This means that such an attribute can have SegmentCrossSectionArea entries for different crossSectionAreaTypes and valueDeterminations. It must not have multiple entries with the same crossSectionAreaType and valueDetermination.
Specifies the value of the cross-section area of the segment.
Specifies the method for determination of the value.
Specifies the type of the cross-section area of the segment. Different types are for example needed to differentiate between the designed space of a segment and the required space (e.g. calculated from the wires going through the segment).
Attribute is defined as anOpenEnumeration.
Specifies the length of aTopologySegment. The length of aTopologySegmentis defined as the length of the centerline of the segment.
Attributes of the type SegmentLength normally have the multiplicity [0..*]. This means that such an attribute can have SegmentLength-entries for different classifications. It must not have multiple entries with the same classification.
Specifies the length of the TopologySegment.
Specifies the classification of the segment length.
Specifies a point on a TopologySegment as a Location.
Specifies the offset / distance of the Location to the anchor of the location.
Specifies if the location on theTopologySegmentis defined as on offset relative to the startNode of the TopologySegment or the endNode.
References theTopologySegmenton which the Location is located.
Defines the relationship of an inner segment to its outer topology. The relationship to the outer topology is expressed with aPath.
Documents can be structured into sheets or chapters. Since it is possible, that one document describes a couple of parts it is necessary to be able to specify which sheet or chapter contains the description of which part. (see KBLFRM-308)
The identification of the sheet or chapter within the document. This value must be distinct within the context of a document.
The sheetNumber is the major identifier of a SheetOrChapter. The format is user defined and respectively company specific. This field has to be used if a SheetOrChapter has its own "DocumentNumber".
The sheetVersion specifies the version index of a sheet (see also sheetNumber)
Room for additional, human readable information about the SheetOrChapter.
Defines the format of the SheetOrChapter. This is an alias for a specific sheet / paper size (e.g. DINA4). If both attributes are defined theSheetSizetakes precedence.
Specifies the properties of a shield.
Defines the optical tissue density of the strands of a shield. This is defined as a value in percentage.
Should only be used for ShieldSpecifications with type=Braided.
Defines the type of winding of the shield.
Should only be used for ShieldSpecifications with type=Foil.
Specification of tubes that are shrinkable.
Defines the factor of shrinking for the tube.
Defines the shrinkage in longitudinal direction.
Defines the material of the resin usable for this shrinkable tube.
Defines the water absorption of the shrinkable tube specification.
Specifies a signal.
Specifies a unique identification of the Signal. The identification is guaranteed to be unique within the SignalSpecification.
Name of the Signal, which is not guaranteed to be unique and is normally function oriented.
Specifies the name of the clamp e.g. KL15, KL30, KL31.
Specifies additional identifiers for theSignal.
A human readable description of the signal.
Specifies the information type of the signal.
Specifies the type of the transmission medium for the signal.
Specifies the form of the signal.
Specifies the curve of the signal.
Defines the data rate of the signal. This applies only to signals withsignalType = 'information' andsignalInformationType = 'digital'. For the numerical value, an appropriate IECUnit combination shall be used (e.g. GBit / Second).
Defines a recommended Specification for the cores that implement this signal.
Defines a recommended Specification for the insulation (e.g. the color) that implements this signal.
Defines a requirement for wire tuples.
Specification for the definition of a list of valid signals.
Specifies the signals.
A custom property with a simple value (string).
Defines the value of theCustomProperty.
Defines the size of an element by width & height. Per definition is width > height.
The width of the element.
The height of the element.
A slot is a group of cavities in a connector housing with own properties. The design of a slot is described in a SlotSpecification.
Specifies the color of the slot.
Specifies the type of the sealing of the slot, if sealed. The values are defined in anOpenEnumeration.
If this attribute is defined, it is only permitted to use terminals of one of the listed terminal suppliers.
The used company name shall be same as the one used asPartVersion.companyNamefor part numbers of this supplier.
References thePartRelationsthat specify supplementary parts for this slot.
Specifies the Cavities forming the Slot.
ASlotCouplingdefines the mapping between two slots of theConnectorHousingRolesassociated with theCouplingPoint.
For regularly laid out slots the slot layout describes the positions of the cavities
The horizontal distance between the center points of two cavities.
The vertical distance between the center points of two cavities.
The number of cavity rows of the slot.
Defines the mapping of two slots contained PartVersion A & B of the containing Mapping-object.
The identification of the Slot on side A
The identification of the Slot on side B
ASlotReferencerepresents the usage of aSlotin the context of PartUsage or PartOccurrence.
This is the relationship of the supplementary parts actually used in thisSlotReference.This is the actual selection of the potential supplementary parts defined in the correspondingSlot.supplementaryPartsassociation.
Specification for the definition of slots.
Specifies whether the slot needs EMV protection.
Specifies the gender of the slot. Valid values are defined in an open enumeration.
Specifies the layout of the slot from a mechanical / geometrical point of view.
Specifies whether the slot supports secondary locking.
The possible number of cavities in the layout defined by the SlotSpecification. This includes all cavities in the layout. The actual Slot can define specific cavities in the layout as "not available".
References the layout associated with this slot.
Allows the definition of a sound damping class. The sound damping class of a component is specified as a level of sound damping. The level is specified by theclassKey. Valid keys are specified by thereferenceSystem. Attributes of the typeSoundDampingClassnormally have the multiplicity [0..*]. This means that such an attribute can haveSoundDampingClassentries for differentreferenceSystems. It must not have multiple entries for the samereferenceSystem.
Specifies a key for the level defined in the sound damping class (e.g. A, B, C).
The identification of the sound damping class reference system, which is defining possible values and the semantic of sound damping keys.
A SpecificRole is the possibility to define instance specific properties with custom properties (see ExtendableElement). This is necessary, if the part is described by custom properties of a PartOrUsageRelatedSpecification.
Specifies the type for role.
References thePartOrUsageRelatedSpecificationthat is instantiated by thisSpecificRole.
Abstract super-class for all specifications. Every technical information exchanged with the VEC is contained in the different specializations of a specification.
Specifies a unique identification of the specification. The identification is guaranteed to be unique within the document containing the specification. For all VEC-documents a Specification-instance can be trusted to be identical if the DocumentVersion-instance is the same (see DocumentVersion) and the identification of the Specification is the same.
Specifies additional, human readable information about the specification.
A SpliceTerminalRole defines the instance specific properties and relationships of a splice terminal.
Specifies the type of splice (inline, end).
Specifies the insulation state of the splice, in other words is electrically insulated or not.
Specification for the definition of splice terminals.
Specifies a stripe which has fixed length and width. A stripe is a textile, foam or similar piece with fixed length & width that is wrapped around the harness.
Specifies the length of the stripe.
Specifies the valid segment diameter range for which the stripe can be used.
Specifies the width of the stripe.
Specifies the thickness of the stripe (adhesive + backing).
ASwitchingStatedefines a certain static state of anEEComponent. Under which conditions or when such a state applies, should be described in an external description model.
ASwitchingStatereferences a collection ofInternalComponentConnections, with the semantic that these connections exist (and only these connections) when the switching state is active.
Identification of the SwitchingState, which must be distinct for all SwitchingStates of an EEComponent.
Specifies theInternalComponentConnectionsthat are switched by thisSwitchingState.
SpecificWireProtectionRolefor instances ofTapeSpecification.
Specifies the amount of overlap two rounds of taping around a segment have, as an absolute value. A negative value means, that there is a gap between two rounds.
Specifies the amount of overlap two rounds of taping around a segment have, as a relative value. A negative value means, that there is a gap between two rounds. Values are defined as a factor, not as a percentage. Values can be between 1.0 and negative "infinity".
Examples:An overlap of 1.0 defines that the second round is placed exactly on top of the first one. An overlap of 0.5 specifies that one half of the second round is on top of the first round (50% overlapping), a value of 0 specifies, that there is no overlap, but also no gap. A value of -2.0 specifies that there is a gap twice the width of the tape between two rounds.
Specifies the direction of the taping.
Specifies the gradient of the taping.
Defines the type of the tape's winding (seeWindingType).
Defines the firmness of the tape's winding (see WindingFirmness).
Specification for the description of tapes.
Specifies the material of carrier of the tape, on which the adhesive material is applied.
Specifies the adhesive material of the tape.
Specifies the width of the tape.
Specifies the thickness of the tape (adhesive + backing).
Specifies the inner diameter of the coil on which the tape is delivered.
Defines valid temperature ranges for a general technical part. A part can have different valid temperature ranges in different scenarios e.g. operating temperature, storage temperature, processing temperature, environment temperature. A class can own multiple TemperatureInformations but must not have more than one TemperatureInformations of the same temperatureType.
Specifies the allowed temperature range for this type of temperature.
The type of a TemperatureInformation.
Allows the definition of valid current ranges for a terminal. A current range is always defined for a coreCrossSectionArea and a nominal voltage. Attributes of the type CurrentRangeInformation normally have the multiplicity [0..*]. This means that such an attribute can have CurrentRangeInformation entries for different coreCrossSectionAreas and nominalVoltages. It must not have multiple entries for the same coreCrossSectionAreas and nominalVoltages.
Specifies the valid current range for the terminal. It is defined as a value range, because there are terminals where minimum current is needed to avoid corrosion.
Specifies the nominalVoltage for which the CurrentRangeInformation is valid.
Specifies the coreCrossSectionArea for which the CurrentRangeInformation is valid. The coreCrossSectionArea is a relevant information, because the thermal absorption of the core depends on the cross-section area and thus is an influence factor for the valid current range.
ATerminalPairingis a standard reference setup of exactly two terminals and a defined length of a core contacted to both terminals. TheTerminalPairingdefines physical properties that apply to this combination.
Specifies the joining force of the two terminals.
Specifies the force required to unmate the two terminals.
References the first terminal of the TerminalPairing.
References the CoreSpecification that is used on both sides of the ContactSystem.
References the second terminal of the TerminalPairing (first and second does not imply any specific order).
Specification for the definition of TerminalPairings.
Specifies the TerminalPairings described by this TerminalPairingSpecification.
A TerminalReception is the area of a terminal where the contacting with another terminal (e.g. between a connector housing and a control unit) takes place. Normally the terminal reception is placed in a cavity of a connector housing.
This class represents such an area on the terminal.
Specifies a unique identification of the TerminalReception. The identification is guaranteed to be unique within the TerminalSpecification (this might be for example a reception number).
Specifies the gender of the TerminalReception. The gender is included in the TerminalReception class in order to be able to refer the same TerminalReceptionSpecification gender independent.
ATerminalReceptionReferenceis an instance of aTerminalReception.
Specifies a uniqueidentificationof theTerminalReceptionReference. Theidentificationis guaranteed to be unique within theTerminalRole(this might be for example a reception number).
References theTerminalReceptionthat is instanced by thisTerminalReceptionReference.
Specification for the definition of terminal receptions. A TerminalReception is the area of a terminal where the contacting with another terminal (e.g. between a connector housing and a control unit) takes place. Normally the terminal reception is placed in a cavity of a connector housing.
Deprecated (since Version 1.1.4): This attribute has been marked as deprecated, as it has been replaced by the more meaningful mechanism withTerminalTypes.
Specifies the plating material of the terminal reception.
Specifies if the terminal reception has a primary locking and of what type it is.
The force until the terminal is pulled out of the housing (normally a not intended case). KBLFRM-366
Specifies the length of the contact area (see diagram "Terminal Dimensions").
Specifies the terminal type that is associated with the terminal reception.
A TerminalRole defines the instance specific properties and relationships of a terminal.
Specifies if this instance of a terminal should be sealed (waterproof). This applies for example to SpliceTerminals.
References theTerminalSpecificationthat is instanced by thisTerminalRole.
Specifies theTerminalReceptionReferencesof thisTerminalRole.
Specifies theWireReceptionReferencesof thisTerminalRole.
Specification for the definition of terminals. A terminal can own multiple WireReceptions & TerminalReceptions.
Specifies the allowed voltage range for the connector housing.
Defines theSealingTypeof the Terminal. This type always refers to the sealing of the terminal itself. However, even a terminal which is not sealable can be used in sealed locations with additional measures (e.g. on the slot).
Specifies the length of the terminal between the contact area (terminal reception) and the crimp are (wire reception, see diagram "Terminal Dimensions").
Specifies the overall length the terminal (see diagram "Terminal Dimensions").
Specifies theTerminalCurrentInformationthat is applicable for the terminal.
Defines the type (system) of a terminal. The type is specified by a combination of a name for the system and an optional nominalSize.
In some processes the terminal type is referred as cavity system, because the system of cavities, terminals, seals, plugs and other cavity accessories must match / be compatible.
However, since a terminal has only one since type and a cavity can be compatible to more than one it is namedTerminalTypein the VEC.
Specifies the type of the cavity (e.g. MQS, DFK, ...).
Specifies the nominal size of terminals that fit into the cavity. (e.g. 2x4).
A TextBasedInstruction is used to specify human readable instructions in text.
Specifies the instruction in a human readable form. Different languages are possible.
Enables the specification of value ranges which can be tolerated.
Specifies the lower boundary for the tolerance.
Specifies the upper boundary for the tolerance.
As the name implies, aTopologyBendingRestrictiondefines restrictions on the bendability a path in theTopology.There are multiple reasons, why such restrictions exist, for example:
Since these restrictions can be determined using a variety of methods the VEC provides a concept to store this information for later use. This makes the information available in the downstream processes, without detailed knowledge of the determination procedure (e.g. during form board design, packaging or installation).
The restriction applies to a path of segments as this can cover different case:
Specifies the minimum bend radius for the restricted path, if it is used in a dynamic environment, where it is bended repeatedly (e.g. in the grommet of the back door).
Specifies the minimum bend radius for the restricted path, if it is used in a static environment, where it is bended once during installation. After that it remains unchanged in its bended position during usage.
The path that defines the restricted way in the topology.
ATopologyBendingRestrictionSpecificationcan be used to defineTopologyBendingRestrictions.
A TopologyGroupSpecification defines a new Topology based on the grouped Topologies. (see KBLFRM-240)
A TopologyMappingSpecificationallows the definition of hierarchical topologies. It relates an outer topology with an enclosed inner topology.
A TopologyNode is a point in the Topology where TopologySegments are starting and ending.
Specifies additional identifiers for the TopologyNode.
Example: TopologyNode Ids may vary from one CAD system export to another. Therefore, the CAD system Id is improper for identification attribute. The identification shall have a value which is unique within the Topology. AliasId may be used for the CAD system Id.
Specifies a unique identification of the TopologyNode. The identification is guaranteed to be unique within the TopologySpecification. For all VEC-documents a TopologyNode-instance can be trusted to be the same if the TopologySpecification-instance is the same (see TopologySpecification) and the identification of the TopologyNode is the same.
Specifies an identifier that can be used for matchingTopologyNodesthat belong to differentTopologySpecificationsand are actually representing the same node. Example: There are twoTopologySpecifications, each specifying the topology of a certain zone of the car. If the zones are adjacent, it is possible that there areTopologyNodesin both zones where the two topologies are connected / have contact. These "connection-nodes" would then define the samematchingPointId.
Specifies processing instructions for the TopologyNode.
Specifies the type of the TopologyNode. A Node can either be an EndNode, a Junction or an Inliner.
If thisTopologyNodeis an instance of anotherTo pologyNodethat is defined elsewhere (e.g. the topology of an assembly), then the instantiated may be referenced here.
References theUsageNodethat is realized by thisTopologyNode.
ATopologySegmentis a distance in the Topology where no intermediate electrical contacts appear. If a Topology contains routed wires, then the wire at the beginning of a TopologySegment must be the same as in the ending.
TopologySegmentsare a logical construct to describe the physical representation of a wiring harness topology. Therefore, aTopologySegmentis only valid if it has a physical manifestation.TopologySegmentswith a length of 0 or less do not have a physical manifestation and are thereforenotvalid.
Additionally, the usage ofTopologySegmentswith a length of 0 create problems in the overall process. For example, the synchronization of 3D / 2D systems becomes harder or even impossible and the handling of wire protections on thoseTopologySegmentis also unclear.
Specifies a unique identification of the TopologySegment. The identification is guaranteed to be unique within the TopologySpecification. For all VEC-documents a TopologySegment-instance can be trusted to be the same if the TopologySpecification-instance is the same (see TopologySpecification) and the identification of the TopologySegment is the same.
Specifies the form of the TopologySegment. A TopologySegment can either be circular or noncircular.
Specifies additional identifiers for the TopologySegment.
Example: TopologySegment Ids may vary from one CAD system export to another. Therefore, the CAD system Id is improper for identification attribute. The identification shall have a value which is unique within the Topology. AliasId may be used for the CAD system Id.
Specifies processing instructions for the TopologySegment.
If thisTopologySegmentis an instance of anotherTo pologySegmentthat is defined elsewhere (e.g. the topology of an assembly), then the instantiated may be referenced here.
Specification for the definition of a topology. A topology consists of TopologyNodes, TopologySegments.
ATopologyZonedivides a topology in different sections / design spaces. ATopologyZonemay be subdivided in furtherTopologyZone. There can be multiple reasons for creating an orthogonal sectioning on aTopology. Therefore,TopologyZonescan be overlapping.
Specifies a unique identification of the Zone (normally the name). The identification is guaranteed to be unique within the TopologySpecification. For all VEC-documents a Zone-instance can be trusted to be the same if the TopologySpecification-instance is the same (see TopologySpecification) and the identification of the Zone is the same.
The type of the TopologyZone. Valid values are defined in an OpenEnumeration.
Specifies additional, human readable information about the zone.
Defines the ambient temperature that can occur in this zone. This can result in specific requirements for the used components.
Defines the robustness properties that are required in this zone. This can result in specific requirements for the used components (e.g. the ability for sealing).
The assignments of specific topology elements to this zone.
Specifies the subTopologyZonesthat are part theTopologyZone. AllZoneAssignmentsdefined for subZones are automatically inherited by the parent zone.
Specification for the definition of TopologyZones.
Specifies theTopologyZonesthat are part of theTopologyZoneSpecification.
A Transformation is a geometric transformation and specifies a transformation matrix.
A Transformation is a geometric transformation and specifies a transformation matrix.
Specifies tubes.
Specifies the bend radius of the tube.
Defines the inner diameter of a tube. In the case of a shrinkable tube, it is the diameter of the tube in the unshrinked state.
Specifies the thickness of the wall of the tube.
Specifies whether the tube is slit or not. The style of the slitting can be defined with theslitStyle.If aslitStyleis defined, it implies thatisSlit=true.
Specifies the style of the slitting of the tube. If aslitStyleis defined, it implies thatisSlit=true.
This attribute is defined as anOpenEnumeration.
Defines the nominal size of a tube. The nominal size is a name for the size of the tube that is somehow related to the inner diameter of the tube. However, it is not the inner diameter (e.g. "10.5").
Defines the secondary nominal size of a tube. The nominal size is a name for the size of the tube that is somehow related to the inner diameter of the tube. However, it is not the inner diameter (e.g. "10.5").
The secondary nominal size shall only be used for two-parted tubes (see TubeSlitStyle = TwoParts). The secondary nominal size defines the size of the outer (larger) tube of a two-parted tube.
Specifies the shape of the cross section of the tube.
This attribute is defined as anOpenEnumeration
Specifies the outer diameter of the tube. The outer diameter of a tube shall only be used for circular tubes (shape = Circular). For other shapes, height and width shall be used.
Specifies the height of the tube. If the height is defined, a width shall be defined, too. The height and width of a tube shall only be used for tubes that are not circular (shape != Circular). For circular shapes, the outside diameter shall be used.
Specifies the width of the tube. If the width is defined, a height shall be defined, too. The height and width of a tube shall only be used for tubes that are not circular (shape != Circular). For circular shapes, the outside diameter shall be used.
Specifies the length of the tube if it is a predefined value.
The USUnit class can define quantities in the terms of the US-Unit-System by specifying the corresponding US unit name. The US Unit System is quite similar to the imperial unit system; however, some units are defined slightly different.
Specifies the name of theUSUnit.
A precisely specified quantity in terms of which the magnitudes of other quantities of the same kind can be stated. The different systems to define units are represented by the subclasses of this class (e.g. SIUnit, ImperialUnit).
Defines the exponent with which this unit instance should be used. In order to define square meters for example, the SIUnit "metre" with an exponent of 2 will be used. If no exponent is defined it is equivalent to the value 1.
Specifies a constraint of the possible usages for PartVersion or PartUsages. UsageConstraints are of part master data information. UsageConstraints specify general restrictions for the application of a PartVersion or PartUsage (e.g. a certain period of time in which the part is allowed to be used). (see KBLFRM-229)
Defines if the usage constraint is positive (allowance) or negative (denial).
Specifies the lower bound of the time period to which the usage constraint applies.
Specifies the upper bound of the time period to which the usage constraint applies.
Specifies the lower bound of a serial number range to which the usage constraint applies.
Specifies the upper bound of a serial number range to which the usage constraint applies.
Specifies the project phases to which the usage constraint applies.
In the production logistics of complex products (like vehicles), the control of operation and cancellation dates of changes, features, components or the like is usually not carried out via concrete dates but via "date keys". These keys are then mapped in planning systems with concrete time specifications for certain plants or production steps. In the VEC these keys are calledEffectivityControlKey.
With theFromEffectivityControlKeyandTo EffectivityControlKeya validity interval can be defined. If one of the two values is defined and the other is omitted, the meaning shall be "unbounded".
SeeFromEffectivityControlKey.
References theProjectsto which theUsageConstraintapplies. This means the described PartVersion is allowed / denied in the referenced UsageConstraint.
References theUsageNodeto which theUsageConstraintapplies. This means the describedPartVersionis allowed / denied in the referenced UsageNode.
Specification for the definition of usage constraints. The associated UsageConstraints are restricting the possible usages of the associated PartVersions and PartUsages.
References thePartVersionsto which thisUsageConstraintSpecificationapplies.
Specifies the UsageConstraints that apply to the PartVersion or PartUsages described by the UsageConstraintSpecification. The ordering of this association is relevant. The elements shall arranged in the order of ascending priority. That means, elements further back in the collection have a higher priority.
AUsageNoderepresents a position in an abstract vehicle. For example, the "Head Light Left".UsageNodesbelong to the master data and they are defined on some companywide level. They can be used to enforce consistent naming over different projects and different development streams (e.g. between Geometry and Electrologic).
AUsageNodecan be realized by different elements in the VEC (e.g.NetworkNode, OccurrenceOrUsage, TopologyNode, ComponentNode).
Specifies an abbreviation of theUsageNode. Normally this a human readable short name.
Specifies a uniqueidentificationof theUsageNode. Theidentificationis guaranteed to be unique within the context. For all VEC-documents aUsageNode-instancecan be trusted to be the same if the context-instance is the same and theidentificationof theUsageNodeis the same.
Specifies additional, human readable information about theUsageNode.
Defines the type of the UsageNode. The type determines how the UsageNode is handled in the latter processes.
Specifies theProjectsin which theUsageNodecan be used.
AUsageNodeSpecificationis a container for the specification ofUsageNodes.
Specifies theUsageNodesdefined by thisUsageNodeSpecification.
A pair of numerical values representing a value range.
Lower bound of the value range.
Upper bound of the value range.
A custom property with a value range. (see KBLFRM-319)
Defines the value of the CustomProperty.
Abstract class either for a single numerical measure or a range of numerical measures with upper, lower, or upper and lower bounds.
VariantCodes are defining the literals on which VariantConfiguration are stated. Possible VariantCodes might be different for steering types, optional equipment, engine-power class.
Specifies a unique identification of the variant code. This is also the literal value for the VariantCode, which shall be used in the logisticControlExpressions of VariantConfigurations.
Room to specify additional identifiers for the VariantCode.
Room for a human readable short name, title etc. of the VariantConfiguration.
Allows the classification of a VariantCodes.
On optional human readable description of the variant code.
Specification for the definition of variant codes.
A variant configuration defines a condition with which it is possible to express the inclusion or exclusion of ConfigurableElements in different variants of a product.
AVariantConfigurationcan reference anotherVariantConfigurationasbaseInclusion. In this case, aVariantConfigurationcan only be satisfied if itsbaseInclusionis also satisfied.
Specifies a unique identification of the variant configuration. The identification is guaranteed to be unique within the specification and does not change over the time.
On optional human readable description of the variant configuration.
Specifies a logisticControlString which can be used if the variant management is not done by boolean logic.
Specifies a logisticControlExpression expressed as boolean term.
Allows the classification of a VariantConfiguration.
(see KBLFRM-250, KBLFRM-314, KBLFRM-290)
AVariantConfigurationcan only be satisfied if itsbaseInclusionis satisfied as well.
Specification for the definition of variant configurations.
With a VariantGroup it is possible to group VariantCodes. The semantic of this grouping should be defined with the groupType (e.g. composition, choice, etc.).
Specifies a unique identification of the variant code.
Room to specify additional identifiers for the VariantGroup.
Room for a human readable short name, title etc. of the VariantGroup.
On optional human readable description of the variant group.
Allows the classification of a VariantGroups into different types. For example: - composition (e.g. winter package) - choice (e.g. right hand / left hand driving). Agreed literals for this attribute are defined in the OpenEnumerationVariantGroupType.
Specification for the definition of variant groups.
VariantStructureNodescan be used to define a hierarchical structure onVariantGroups. EveryVariantStructureNodescan referenceVariantGroupsandVariantStructureNodesas children.
Specifies a unique identification of theVariantStructureNode.
Room to specify additional identifiers for theVariantStructureNode.
Room for a human readable short name, title etc. of theVariantStructureNode.
On optional human readable description of theVariantStructureNode.
Specification to define any hierarchical structure on variant groups (e.g. by the means of a functional organization). The hierarchy starts with a single root node.
The VecContent is the XML-Root node for any VEC-Document.
Specifies the version of the VEC used for the file.
Specifies the name of the system that has generated the VEC-file.
Specifies the date of creation of the VEC-file.
Specifies the version of the system that has generated the VEC-file.
References theCopyrightInformationthat is in effect for the complete content of thisVecContent. It is applied to allItemVersionsthat do not references their own individualCopyrightInformation.
AWireElementspecifies aWireElementSpecificationin the context of aWireSpecification. This is necessary to define a uniqueidentificationof aWireElementSpecificationin the context of aWireSpecification.Additionally, theWireElementserves as anchor for the instancing of a wire (WireElementReference) as theWireElementSpecificationsare not uniquely related to aWireSpecificationfor reasons of reusability.
The identification of the WireElement. The identification is guaranteed to be unique within a wire and immutable. The identification is guaranteed to be the same for the same WireElement over different VEC documents.
Reference theWireElementSpecificationthat is represented by theWireElement.
Defines thesubWireElementsof thisWireElement. ThesubWireElementsshall be consistent with thesubWireElementSpecificationsof theWireElementSpecificationreferenced by thisWireElementand shall resemble that hierarchy.
A WireElementReference represents the usage of a WireElement in the context of a PartUsage or PartOccurrence. For contacting purposes, a WireElementReference has WireEnds. KBLFRM-384
Specifies a unique identification of the WireElementReference. The identification is guaranteed to be unique within the WireRole.
If this attribute istrue, theWireElementReferenceis not connected (unused) on purpose. This can be the case for example if a multi core is used, but not all cores are necessary in a specific situation.
However, for allWireElementsdefined in theWireSpecificationa correspondingWireElementReferenceshall exist. This attribute can be used to mark these unused cores explicitly.
References theConnectionGroupthat is realized by thisWireElementReference.This applies normally toWireElementReferencethat havesubWireElements.
References the WireElement that is represented by the WireElementReference.
A WireElementSpecification is the basic element to describe a wire in the VEC. A WireElementSpecification can be atomic or composed recursively out of other WireElementSpecifications. A WireElementSpecification can reference an InsulationSpecification, if it has an insulation, a CoreSpecification, if it has a core or a WireGroupSpecification if it is a grouping of other WireElementSpecifications in the Wire (e.g. a multi-core wire with twisted pairs).
Defines the type of the wire. A wire must not have more than one type. This attribute allows more than one value for the reason, that the same type can be expressed in multiple reference systems.
Specifies the minimum bend radius for wire element, if it is used in a dynamic environment, where it is bended repeatedly (e.g. in grommet of the back door). (see KLBFRM-311)
Specifies the minimum bend radius for wire element, if it is used in a static environment, where it is bended once during installation. After that it remains unchanged in its bended position during usage. (see KLBFRM-311)
Specifies the outside diameter of the WireElement.
Specifies if it is allowed to use the WireElement in a dynamic environment. (see KBLFRM-311)
Defines the impedance of this wireElement. Typically used for WireElements that have subWireElements e.g. twisted pair or coax wires.
Defines the size of a WireElement if it has not the shape of circle. If it has the shape of a circle the size is normally defined by its outside diameter.
Defines theWireReceptionTypesthat are allowed for joining with the specifiedWireElement.
Defines the grid spacing. The grid spacing is the distance between the centres of two adjacent sub wire elements.
This attribute is only valid forWireElementSpecificationsthat haveSubWireElementSpecifications.
Defines the shape of aWireElement.Circular wire elements are defined by their outsideDiameter, all others are defined by their size.
If theWireElementhas a core then the specification of the core is referenced here.
If theWireElementis a filler then the specification of the filler is referenced here.
If theWireElementhas an insulation then the specification of the insulation is referenced here.
Specifies the contained subWireElements if the WireElement has sub elements. If aWireElementSpecificationcontains the sameWireElementSpecificationmultiple times, then it shall be referenced as often as it occurs in the reality. Otherwise theWireElementSpecificationwouldn't specify a wire element unambiguously, because the representation in the model would be the same, regardless of the number of sub elements. Therefore, this association must not be realized with a "set" semantic.
If theWireElementSpecificationis representing a wire group, then the specification of the wire group is referenced here. That means as well, that theWireElementSpecificationshall havesubWireElementSpecifications.
A WireEnd is the end of a wire. This class mainly needed for the definition of a contacting. As a wire can be contacted on more than two ends (e.g. IDC) the WireEnd has a position on the wire.
Specifies a unique identification of the WireEnd. The identification is guaranteed to be unique within the WireElementReference.
Specifies the position of the WireEnd on the wire. This must be a value between 0 and 1.
AWireEndAccessoryRoledefines the instance specific properties and relationships of aWireEndAccessory.
References theWireEndAccessorySpecificationthat is instanced by thisWireEndAccessoryRole.
WireEndAccessorySpecificationsare describing parts that are used for a treatment of a wire end before the actual terminal is attached to theWireEnd(e.g. a ferrule).
The actual specification is done by the referencedWireReceptionSpecificationsince aWireEndAccessoryis basically just a singleWireReception.
References the singleWireReceptionSpecificationthat is specifying the properties of theWireEndAccessorythat are related to wire.
Specification for the definition of WireGroups. Wire groups are for example used for the representation of twisted pairs.
Specifies the type of the group (e.g. twisted pair, ...).
Specifies the length of twist if the wire group is representing a twisted pair.
AWireGroupingis the definition of a multi core wire in its usage. The elements of aWireGroupingare well defined wires (e.g. with a part number). The grouping itself is only created in its concrete usage. The most common use case is the individual definition of unshielded twisted pair wires without creating the full combinatorics of every possible core / insulation / twist combination in a part master data system (and by this creating part numbers for all of them). However, there are other use cases as well.
AWireGroupinggroups therelatedWireElementReferenceson an equal level containedWireGroupings are on a lower level. So, in order to create something like a shielded twisted pair, oneWireGrouping"A" that references twoWireElementReferencesis required to represent the twisted pair and anotherWireGrouping "B" that containsWireGrouping"A" and references the "shield wire element".
The referencedWireGroupSpecificationdefines the handling of theWireGroupingduring its assembly (e.g. twist).
Specifies a unique identification of the WireGrouping. The identification is guaranteed to be unique within the WireGroupingSpecification.
References theConnectionGroupthat is realized by thisWireGrouping.
References the concrete wire elements (WireElementReference) that are grouped by the WireGrouping.
References theWireGroupSpecificationthat applies to theWireGrouping.
References theWireGroupingsthat are contained in thisWireGrouping.
Specification for the description of WireGroupings.
Defines the length of a WireElementReference. A WireElementReference can have multiple lengths of different types but must not have more than one length of the same type.
The type of the length. Possible values are defined in an open enumeration (see WireLengthType).
The length value for the type.
AWireMountingdefines the mounting of a wire end to terminal. If the contacting is required to be waterproof a cavity seal can be mounted additionally.
References the cavity seal that is used for the wire mounting.
References the wire ends that are used for the wire mounting. The minimum cardinality is one, because a wire mounting without wire end makes no sense.
The maximum cardinality is * in order to support multi crimps.
Specifies the WireMoutingDetails, if a detailed description of the relationships between WireEnds and WireReceptions is needed.
With a WireMountingDetail it is possible to describe a detailed wire mounting.
This is needed if the information which wire end is mounted onto which wire reception is important (e.g. coax contacts).
A WireProtectionRole defines the instance specific properties and relationships of a wire protection. This is a general-purpose role for instances of all types ofWireProtectionSpecificationsthat do not have specific instance attributes. ForTapeSpecificationsthe more specificTapeRoleshall be used.
TheProtectionLengthspecifies the length of the area covered by the protection. As a consequence, theProtectionLengthmay differ from the real length of the material (e.g. for tapes).
References theWireProtectionSpecificationthat is instanced by thisWireProtectionRole.
Specification for the description of wire protections.
Specifies the class of sound damping. According to the VDA this is a value between A & E. KBLFRM-311
A WireReception is the area of a terminal where the contacting with a wire element (e.g. by crimping) takes place. This class represents such an area on the terminal. Its description is done with a WireReceptionSpecification, which is independent from the TerminalSpecification. This allows the reuse of the specification of similar WireReception on different terminals.
Specifies a unique identification of the WireReception. The identification is guaranteed to be unique within the TerminalSpecification (this might be for example a reception number).
Specifies the angles against two planes of the connector housing a wire reception can be buckled. The planes are defined in a way, that angles of [0.0, 0.0] specify an unbuckled (regular) terminal. The two planes are perpendicular to each other and parallel to the plugging direction of the terminal (the direction of the pin).
The plane for the first angle is the plane in which the uncrimped wire reception would be, if the terminal has not been buckled. Since most terminals are cut or punched in some way out of a sheet of metal, this plane would be the same as metal sheet before further deformation.
For ring terminals the first plane is perpendicular to the bolt direction.
With a viewing direction from the wire reception to the terminal reception and the intended wire position above the terminal, buckling directions up and right are expressed by positive angles, down and left by negative angles.
Specifies thePlacementPointthat represents thisWireReceptionin a PlaceableElementSpecification.
Specifies the wire addon required for this wire reception.
Specifies the wire length add on needed for the wire reception.
Defines the type of the add-on.
AWireReceptionReferenceis an instance of aWireReception.
Specifies a uniqueidentificationof theWireReceptionReference. Theidentificationis guaranteed to be unique within theTerminalRole(this might be for example a reception number).
References theWireReceptionthat is instanced by thisWireReceptionReference.
Specification for the definition of wire receptions. A WireReception is the area of a terminal where the contacting with a wire element (e.g. by crimping) takes place.
Specifies a value range for cross-section areas of cores that are compatible with the wire reception.
For wire receptions where a single core is attached to, this value defines theValueRangeof thecrossSectionAreaof the core. For wire receptions where more than one core is attached to (e.g. ring terminals, splices), this attribute defines the valid value range for the sum of the cross-section areas of all attached cores.
Specifies the length of the insulation which must be stripped off to fit to this wire reception.
Specifies if it is possible to contact more than one core at the wire reception. If this attribute is set to true, the wire reception is allowed for more than one wire, but one wire is possible as well. If set to false, only one wire is allowed.
Specifies the type of the wire reception. The wireReceptionType defines how the wire is joined with the wire reception.
This attribute is defined in an OpenEnumeration.
Specifies a value range for valid diameters a WireElement must have to fit to the wire reception.
Specifies the plating material of the wire reception.
Specifies if the wire reception can be sealed. (see KBLFRM-311)
Specifies the length of the front (facing the terminal reception) bell mouth of the conductor crimp (wire reception, see diagram "Terminal Dimensions").
Specifies the length of the conductor crimp (wire reception, see diagram "Terminal Dimensions").
Specifies the length of the rear bell mouth of the conductor crimp (wire reception, see diagram "Terminal Dimensions").
Specifies the length of the crimp area, conductor + insulation crimp (wire reception, see diagram "Terminal Dimensions").
Specifies the length of the insulation crimp (wire reception, see diagram "Terminal Dimensions").
Specifies the length of the cut off tab (wire reception, see diagram "Terminal Dimensions").
Specifies the length of the connection between the conductor and the insulation crimp (wire reception, see diagram "Terminal Dimensions").
Specifies the materials of a conductor, that are valid to use with thisWireReceptionSpecification. This material shall be matched against theConductorSpecification.material.
A WireRole defines the instance specific properties and relationships of a wire.
References theWireSpecificationthat is instanced by thisWireRole.
Specification for the definition of a wire. This can either be a complex multicore wire or a normal single core. In the VEC a wire is defined by one WireElement, which may be composed from other WireElements.
References theWireElementSpecificationthat defines the properties of the top-mostWireElement.
Specifies theWireElementthat represents the root of theWireSpecification.
ASpecificationto define requirements for the handling of wire / wire element tuples (pairs, triple,...) with the focus on twisting. More precisely, the allowed untwisting at the wire ends and required measures against it.
This definition is made independent from theWireGroup, as the might be defined for the part master data (the wire on the roller). The specifications for untwisting are based on the concrete usage.
AWireTupleTerminationis to define the handling of wire ends in a tuple (group). This is mostly relevant for twisted pairs / triple / tuple to define the handling of untwisting.
AWireTupleTerminationSpecificationis the container specification forWireTupleTerminations.
Specifies a wire type. A wire type is always defined by a key value. What wire type is meant by this key value is defined by a standard reference system.
Specifies the type of the wire (e.g. FLRY, NYFAZw). Valid values are defined by the wireTypeReferenceSystem.
Specifies the reference system for the wire type.
AZoneAssignmentdefines that a specific TopologySegment is affected by theTopologyZone.If a coverage is defined, only the parts of the Segment that have a coverage are affected. If no coverage is defined, the whole segment is affected.
TheTopologySegmentthat is assigned toTopologyZonewith thisZoneAssignment.
Contains a set ofZoneCoveragesthat define the areas of aTopologySegmentthat is affected by the TopologyZone. If no coverage is defined, the complete segment is affected. Multiple coverages can be necessary if theTopologySegmentzigzags in and out of theTopologyZone.
AZoneCoveragedefines an area on aTopologySegmentthat lies within aTopologyZone.The area is defined with twoLocations.Locationsare the same mechanism that is used to define placements for components. The area that is in theTopologyZoneis the area between the two locations. There is no semantic in the direction of the definition, so the assignment of first & second Location is completely arbitrary.
However, there are some restrictions for the definition of the locations. All locations have to be in relation to the TopologySegmentthat is referenced by the containingZoneAssignment. This means theLocationshave to be either aSegmentLocation on therespective TopologySegmentor aNodeLocationon the start or end node of this particularT opologySegment.AZoneCoveragefrom start to end node of aTopologySegmentis equivalent to the complete omission ofZoneCoveragesfor a particularZoneAssignment.
Enumeration for the definition of AnchorType of the SegmentLocation.
The offset of the location is measured from the startNode of the TopologySegment.
The offset of the location is measured from the endNode of the TopologySegment.
Enumeration for the definition of the type of an ApplicationConstraints. Valid values are allow and deny.
Enumeration to define the state of the content of the baseline in regard of its defined scope.
Enumeration the define the valid states of a baseline.
OpenEnumeration for the shapes of the bolts on which the fixing can be mounted.
OpenEnumeration for the types of the bolts on which the fixing can be mounted.
Defines valid values for the geometry of aCableLeadThroughin the sealing area.
Defines valid types for CableLeadThroughs.
Defines valid values of the geometry of cavities in the sealing area (crimp end).
Defines the literals that shall be used for specific color reference systems.
Defines agreed values forComponentNodeSubTypes. Not all combinations ofComponentNodeSubTypesandComponentNodeTypesare semantically correct (e.g. Lamp, Microphone, Speaker, Motor are all Actuators).
Defines the common agreed values for the types of a ComponentNode.
Specifies the structure of the conductor according to ISO 6722-1 for ConductorSpecifications with Type = Stranded.
Specifies the type of the conductor, e.g. if it is rigid or stranded.
Defines the gender of a connetion end.
Defines the type of physical realization that is expressed by aConnectionGroup.
Defines theOutletDirectionof a connector for wires.
Enumeration for the definition of roles a contractor has in a contract.
ThedimensionTypedefines to which measurements thisDefaultDimensionapplies.
Defines the predefinedDocumentTypesof aPartVersion.A certainDocumentTypehas normally a typical set of information that is defined within its scope. E.g. a part master document containsSpecificationsthat are used for the description of a definedPartVersion.
The content and the degree of information a DocumentTypemay vary in the different processes.
OpenEnumeration to define different fitting forms.
Defines the type of winding for foil shields. It can be folded around and along the inner wire elements like a cigarette paper or it can be wound around them in a spiral. Both types result in different manufacturing and EMC properties.
Defines the values for the type a fuse. This is the geometrical type.
Enumeration for the definition of the GeometryType.
Enumeration for the definition of the type of relationship represented by an ItemHistoryEntry. (see KBLFRM-271)
Defines the valid HousingComponentTypes. The values in this Enumeration are matching the relevantPrimaryPartTypes.For a description of the values seePrimaryPartType.
Enumeration for the definition of IEC unit prefixes.
Enumeration for the definition of IEC unit names.
Enumeration for the definition of imperial unit names.
Enumeration for the definition of the insulation state of the splice.
Enumeration for the definition of ISO language codes. (see KBLFRM-317)
Afar
Abkhazian
Chinese
Zulu
Enumeration for the definition of a LengthClassification.
The LevelOfApproval standardizes the approval levels most engineering processes have in common. SeeApproval.levelOfApprovalfor more details.
Defines possible sources forMassInformations.
OpenEnumeration for the manufacturing types of the multi-fuses.
Defines agreed values forNetworkNodeSubTypes. Not all combinations ofNetworkNodeSubTypesandNetworkNodeTypesare semantically correct (e.g. Lamp, Microphone, Speaker, Motor are all Actuators).
Defines the common agreed values for the Types of a NetworkNode.
Enumeration for the definition of the type of a TopologyNode.
Enumeration for the definition of other unit names.
OpenEnumerationthat defines the nature of aPartVersion. The nature specifies how thePartVersioncan be used in the different processes or the significance of thePartVersionin the process.
Defines how the set ofacessoryPartsreferenced by aPartRelationshould be interpreted.
Mandatorymeans that in a usage of a componentallreferencedacessoryPartsmust be used.
Optionalmeans that in a usage of a componentsomereferencedacessoryPartscan be used by choice.
OneOfAllmeans that in a usage of a component exactlyoneof the referencedacessoryPartsmust be selected.
Custom means, that there is some kind of custom constraints / logic between referencedPartVersionsthat has to be evaluated to determine the selected accessories.
OpenEnumeration that defines standard content types for thePartStructureSpecification.
Classifies the appliance of a Pin in terms of the duration of the appliance.
E.g. the power supply pin of a power window has "shortTerm" PinApplianceType, in contrast to the head light which is a "long term".
Specifies the type of aPinComponent.
Defines the different available current types of a pin.
Defines the different available timing types of a pin.
Defines the type of a pin.
Defines the different available voltage types of a pin.
Defines the type for which aPlaceableElementcan be used.
OnWayrefers to anOnWayPlacement.
OnPointrefers to anOnPointPlacement.
Defines valid values for the type of PluggableTerminals. The type defines constraints about the numbers of wire and terminal receptions and their relations.
Defines the valid primary locking types for terminals.
The primary type of the part defines the type of the part (e.g. ConnectorHousing, Fixing, etc.) Since the VEC supports dual use parts (e.g. Fixing & WireProtection) the primary part type is necessary to define which specification associated to part is the primary character of the part. Therefore, all primary part types correspond to a PartOrUsageRelatedSpecification (e.g. ConnectorHousing --> ConnectorHousingSpecification).
The primary part type 'Other' is used if the PartVersion is not further specified by the VEC, which means it has no PartOrUsageRelatedSpecification, only a GeneralTechnicalPartSpecification or a direct instance of PartOrUsageRelatedSpecification.
Specifies the appliance type of a relais.
Defines the type of a relais (switching behaviour).
Defines the literals that shall be used for specific robustness classes.
Defines the literals that shall be used for specific robustness class reference systems.
Enumeration for the definition of the sealing state of the splice.
Defines valid values of the geometry of a cavity sealing. It defines the cross-section geometry.
Defines valid values the type of the cross-section area of aTopologySegment, since aTopologySegmentcan have different cross section areas with different meanings in the process.
Enumeration for the definition of the SegmentForm.
Enumeration for the definition of SI unit prefixes.
Enumeration for the definition of SI unit names. In difference to the SI-System gram is used as literal for the measurement of mass, instead of kilogram. Since a unit is formed with prefix and unit name gram would have to be defined as milli kilogram otherwise.
Enumeration for the definition of SignalDirections.
Defines the gender of a slot.
OpenEnumeration that defines standard slot layouts. A slot layout represents the mechanical / geometrical properties / layout of the slot, not the electrical properties.
Defines the possible sealing types for a slot, if the slot shall be sealed in its usage.
Enumeration for the definition of type of splice.
Enumeration for the definition of the state of an approval.
Defines the direction in relation to the start & end-Location of the corresponding placement. If no TapingDirection is defined it is arbitrary.
Defines the nominal sizes for threaded bolts as "ISO metric screw thread" or as "Unified Thread Standard" (Imperial).
See alsoTerminalBoltType.MetricThread / ImperialThread.
For the definition of the values seehttps://en.wikipedia.org/wiki/ISO_metric_screw_threadandhttps://de.wikipedia.org/wiki/Unified_Thread_Standard.
Defines the possible sealing types for a terminal, if the terminal shall be sealed in its usage.
There can be various reasons to define TopologyZones. These can be differentiated with these type literals.
Defines valid shapes of the cross section of a tube.
Defines valid types / styles of a slitted tube.
Enumeration for the definition of the type of a permission.
Enumeration for the definition of US unit names.
American wire gauge (AWG), also known as the Brown & Sharpe wire gauge, is a standardized wire gauge system used in the United States and Canada.
Enumeration for the definition of the type of a UsageConstraint. Valid values are allow and deny.
Enumeration for the different types ofUsageNodes.
Enumeration for the definition of a value determination. (see KBLFRM-316)
The value is determined by a calculation algorithm.
The value is determined by an exact measurement.
The value is estimated by a person.
OpenEnumeration for the available types of the variant codes.
Defines valid values for the type of VariantGroups.
Defines the firmness with which a tape is applied to a segment.
Defines the type of taping.
Specifies possible values for the typeof wire add-ons (e.g.CavityAddOn).
Defines the shape of a wire element.
OpenEnumeration for the types of wire groups.
Specifies possible values for thelengthTypeofWireLength.
TheWireReceptionTypedefines in anOpenEnumerationhow a wire is joined with a wire reception.