ApplicationConstraint
Note: There is a newer version of this specification see VEC 2.1.0
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
| Attribute | Value |
|---|---|
| Owner | variants |
| Applied Stereotype | |
| Base Classifier | ExtendableElement |
| Is Abstract | false |
| Derived Classifiers |
Attributes
| Name | Type | Mult. | Description | Owning Classifier |
|---|---|---|---|---|
| type | ApplicationConstraintType | 1 | 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 |
| fromDate | Date | 0..1 | Specifies the lower bound of the time period to which the application constraint applies. |
ApplicationConstraint |
| toDate | Date | 0..1 | Specifies the upper bound of the time period to which the application constraint applies. |
ApplicationConstraint |
| fromSerialNumber | String | 0..1 | Specifies the lower bound of a serial number range to which the application constraint applies. |
ApplicationConstraint |
| toSerialNumber | String | 0..1 | Specifies the upper bound of a serial number range to which the application constraint applies. |
ApplicationConstraint |
| projectPhase | String | 0..* | Specifies the project phases to which the application constraint applies. |
ApplicationConstraint |
| fromEffectivityControlKey | String | 0..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 |
| toEffectivityControlKey | String | 0..1 | See FromEffectivityControlKey. |
ApplicationConstraint |
Outgoing Relations
| Type | Role | Mult. | Mult. | Description |
|---|---|---|---|---|
| Project | project | 0..* | Defines the projects for which the application constraint applies. |
|
| ApplicationConstraint | baseInclusion | 0..1 | 0..* | An ApplicationConstraint can only be satisfied if its baseInclusion is satisfied as well. |
Incoming Relations
| Type | Mult. | Role | Mult. | Description |
|---|---|---|---|---|
| ConfigurableElement | applicationConstraint | 0..* | Deprecated since VEC V2.0.0. Use ConfigurationConstraints instead. References the application constraints that apply to the ConfigurableElement. |
|
| ApplicationConstraintSpecification | 1 | applicationConstraint | 1..* | Specifies the UsageConstraints that apply to the PartVersion or PartUsages described by the UsageConstraintSpecification. |
| ConfigurationConstraint | applicationConstraint | 0..* | References the application constraint that applies to the ConfigurationConstraint. |
|
| ApplicationConstraint | 0..* | baseInclusion | 0..1 | An ApplicationConstraint can only be satisfied if its baseInclusion is satisfied as well. |