The PartAssembly template describes how to represent the parent/child relationship
betwen design parts (a design assembly).
The SysML Block Definition diagram in Figure 1
shows how a Part is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
child [1] (Template: OASIS:
Part)
The child Part
assemblyType [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
The reference to the class used to classify the assembly.
The following constraint, normally a uniqueness constraint, is
applicable when instantiating the ExternalOwlClass:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: ur1Specification: (OCL2.0)
ExternalOwlClass::allInstances()->isUnique(class)
The reference data used in Block: Ap239Ap233Psm:
ExternalOwlClass is restricted as follows:
RDL constraint 1:There must be one identifier that is the breakdown identifier.
The reference data for:
ExternalOwlClass.class
is restricted to the following class or a subclass:
Parts:
locationIndicators [0..*] (Template: OASIS:
Identification)
The collection of Identifiers that identifies the usage of the child in the assembly
in a diagram, list, chart, or on a physical piece of equipment.
Values:
startEffectivityDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date when the assembly relationship starts to be 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')
endEffectivityDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date when the assembly relationship ends to be 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')