ApplicationConstraint

An ApplicationConstraint defines a condition with which it is possible to express the inclusion or exclusion of ConfigurableElements in different variants of a product. The ApplicationConstraint is 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 the VariantConfiguration which expresses validity rules based on control strings.

An ApplicationConstraint can reference another ApplicationConstraint as baseInclusion. In this case, an ApplicationConstraint can only be satisfied if its baseInclusion is also satisfied.

General Information

AttributeValue
Ownervariants
Applied Stereotype
Base ClassifierExtendableElement
Is Abstractfalse
Derived Classifiers

Attributes

NameTypeMult.DescriptionOwning Classifier
typeApplicationConstraintType1

Defines if the application constraint is positive (allowance) or negative (denial). If the ApplicationConstraint has a baseInclusion that baseInclusion shall define the same type.

ApplicationConstraint
fromDateDate0..1

Specifies the lower bound of the time period to which the application constraint applies.

ApplicationConstraint
toDateDate0..1

Specifies the upper bound of the time period to which the application constraint applies.

ApplicationConstraint
fromSerialNumberString0..1

Specifies the lower bound of a serial number range to which the application constraint applies.

ApplicationConstraint
toSerialNumberString0..1

Specifies the upper bound of a serial number range to which the application constraint applies.

ApplicationConstraint
projectPhaseString0..*

Specifies the project phases to which the application constraint applies.

ApplicationConstraint
fromEffectivityControlKeyString0..1

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 called EffectivityControlKey.

With the FromEffectivityControlKey and ToEffectivityControlKey a validity interval can be defined. If one of the two values is defined and the other is omitted, the meaning shall be "unbounded".

ApplicationConstraint
toEffectivityControlKeyString0..1

See FromEffectivityControlKey.

ApplicationConstraint

Outgoing Relations

Other EndThis EndGeneral
RoleTypeMult.Agg.UniqueOrderedMult.Description
baseInclusionApplicationConstraint0..1NYN0..*

An ApplicationConstraint can only be satisfied if its baseInclusion is satisfied as well. 

projectProject0..*NYN

 Defines the projects for which the application constraint applies.

Incoming Relations

This EndOther EndGeneral
RoleMult.Agg.UniqueOrderedTypeMult.Description
applicationConstraint1..*YYNApplicationConstraintSpecification1Specifies the ApplicationConstraints.
applicationConstraint0..*NYNConfigurationConstraint

References the application constraint that applies to the ConfigurationConstraint.

applicationConstraint0..*NYNConfigurableElement

References the application constraints that apply to the ConfigurableElement.

baseInclusion0..1NYNApplicationConstraint0..*

An ApplicationConstraint can only be satisfied if its baseInclusion is satisfied as well. 

Previous