Project

Usage Node A UsageNode represents a position in an abstract vehicle. For example the "Head Light Left". UsageNodes belong to the master data and they are defined on some companywide level.

Usage Constraints A UsageConstraintSpecification is intended to describe the allowed usage of the constrainedParts. A UsageConstraintSpecification is a container for various UsageConstraints each representing a single constraint. The sequencing of the UsageConstraints specifies the priority: a general denial may be relativized by a following UsageConstraint and vice-versa.

Usage Constraints A UsageConstraintSpecification is intended to describe the allowed usage of the constrainedParts. A UsageConstraintSpecification is a container for various UsageConstraints each representing a single constraint. The sequencing of the UsageConstraints specifies the priority: a general denial may be relativized by a following UsageConstraint and vice-versa.

Usage Constraints A UsageConstraintSpecification is intended to describe the allowed usage of the constrainedParts. A UsageConstraintSpecification is a container for various UsageConstraints each representing a single constraint. The sequencing of the UsageConstraints specifies the priority: a general denial may be relativized by a following UsageConstraint and vice-versa.

Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or responsible person. An ItemVersion normally has approval information and can be specified within the VEC by the relationship ItemVersion.

Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or responsible person. An ItemVersion normally has approval information and can be specified within the VEC by the relationship ItemVersion.

Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or responsible person. An ItemVersion normally has approval information and can be specified within the VEC by the relationship ItemVersion.

Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or responsible person. An ItemVersion normally has approval information and can be specified within the VEC by the relationship ItemVersion.

Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or responsible person. An ItemVersion normally has approval information and can be specified within the VEC by the relationship ItemVersion.

Lifecycle Information An ItemVersion can carry information about the creation of the item. This means the creating timestamp and an optionally information regarding the creator or responsible person. An ItemVersion normally has approval information and can be specified within the VEC by the relationship ItemVersion.