Template:- OASIS:ActualMissionItem

The ActualMissionItem template describes how to represent an item that has a role in an ActualMission. It enables the tracking of when an item was part of the mission and when it was not.

The SysML Block Definition diagram in Figure 1 shows how an activity is represented in the PLCS PSM.

Template Properties

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

References:
mission [1] (Template: OASIS:ActualMission)
The mission
item [1] (Template: OASIS:RealizedPart)
The item which is in the mission
approvals [0..*] (Block: Ap239Ap233Psm:Approval)
The collection of approvals for the item in the mission
Values:
startEffectivityDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date when the item starts to be in the mission

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')
endEffectivityDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date when the time starts to be in the mission

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')