The RealizedPartAssembly template describes how to represent the parent/child relationship
betwen parts in the real world (a realized 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] (Block: Ap239Ap233Psm:
ProductViewDefinition)
The child part really used in the parent
The following constraint, normally a uniqueness constraint, is
applicable when instantiating the ProductViewDefinition:
rule.Ap239Ap233Psm.ExternalOwlClass.ur1
Constraint: ur1Specification: (OCL2.0)
ProductViewDefinition::allInstances()->isUnique(Sequence{viewDefinitionOf, initialContext})
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')