The BreakdownStructure template describes how to represent to represent a relationship
between a
BreakdownElementDefinition
and another
BreakdownElementDefinition
that is a constituent.
The SysML Block Definition diagram in Figure 1
shows how a System Breakdown is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
Parts:
ids [0..*] (Template: OASIS:
Identification)
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The id must be classified as a Breakdown_element_usage_identification_code or a
subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
Values:
startEffectivityDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
the date that defines the lower bound of the interval of applicability.
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')
endEffectivityDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
the date that defines the upper bound of the interval of applicability. The
value of the attribute need not be specified. If the value for this attribute is not
specified, the interval of applicability has no upper limit.
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')