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
The following SysML Part, Reference, and Value properties are defined for this template:
References:
Parts:
applicabilityRole [0..1] (Template: OASIS:
Classifier)
The role for the applicability (i.e. variantApplicability, Range applicability, etc
...)
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: XSDDATETIMESpecification: (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: XSDDATETIMESpecification: (OCL2.0)
self.matches('[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z')