Template:- OASIS:Applicability

The Applicability template describes how to indicate that an item is applicable to another item.

The SysML Block Definition diagram in Figure 1 shows how a Product Configuration is represented in the PLCS PSM

Template Properties

The following SysML Part, Reference, and Value properties are defined for this template:

References:
applicableTo [1] (Block: Ap239Ap233Psm:EffectivityAssignmentSelect)
The entity which is the target for the applicability
appliedParameters [1..*] (Block: Ap239Ap233Psm:ConditionParameterSelect)
The entities that define the domain for the applicability
conditionExpressionProxy [1] (Block: Ap239Ap233Psm:ProxyItemSelect)
The logical expression operators for the applicability (i.e. AND, OR, XOR, NOT)
Parts:
applicabilityRole [0..1] (Template: OASIS:Classifier)
The role for the applicability (i.e. variantApplicability, Range applicability, etc ...)
effectivityRole [0..1] (Template: OASIS:Classifier)
The role for the valid dates
Values:
endEffectivityDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date to which the applicability is valid

The following constraint, normally a uniqueness constraint, is applicable when instantiating the DateTimeString:

rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: XSDDATETIME
Specification: (OCL2.0)
self.matches('[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z')
startEffectivityDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date from which the applicability is valid

The following constraint, normally a uniqueness constraint, is applicable when instantiating the DateTimeString:

rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: XSDDATETIME
Specification: (OCL2.0)
self.matches('[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z')