The ActualActivity template describes how to represent a record of an activity that has at
least started and may have finished - an actual activity.
It can be used to record any information about an actual activity, such as who has
performed
and/or reported the activity, what method (a specification of how to perform an activity)
was followed, and when the activity was
performed. It is mandatory to assign an identifier or name to the activity, and a
start time,
and to relate it to a method (activity method).
This template should not be used for recording activities that are performed by a
product. e.g. a sortie flown by an aircraft, nor activities managed by a WorkOrder and DirectedActivity.
The ActualActivity is one of a set of templates
used to represent work and activities. These are summarized in Figure 1
which shows that the model contains templates for:
- representing request and authority for work,
- managed planned authorized activities and a corresponding record of the work done,
- unmanaged planned activities and a corresponding record of the activity done,
- record of activities performed by a product.
The actual templates are:
-
Managed work
- The WorkRequest template represents a
request for work to be undertaken;
- The WorkOrder template represents the
authorization of work to be undertaken, often in response to a WorkRequest;
- The DirectedActivity template represents
an activity that is planned to be undertaken under the authority of a given
WorkOrder.
- The WorkDone template represents a record
of the work done in response to an authorized DirectedActivity.
-
UnManaged activities
- The PlannedActivity template represents an
activity that is planned to be undertaken that is neither governed by a WorkOrder nor an activity to be performed by a
product.
- The ActualActivity template represents a
record of an activity that is performed in response to a PlannedActivity.
-
Product activities
- The ActualProductUsage template represents
a record of an activity that has been performed by a product, the
usage of a product.
The SysML Block Definition diagram in Figure 2 shows how a
activity is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
plannedActivity [0..1] (Block: Ap239Ap233Psm:
Activity)
the planned activity that resulted in this activity being
undertaken.
location [0..*] (Block: Ap239Ap233Psm:
Location)
The location where the activity was performed.
contract [0..*] (Template: OASIS:
Contract)
The contract under which the activity was performed.
project [0..*] (Template: OASIS:
Project)
The project under which the activity was performed.
Parts:
ids [1..*] (Template: OASIS:
Identification)
The collection of identifiers of the activity.
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The id must be classified as an Activity_identification_code or a
subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
classifications [0..*] (Template: OASIS:
Classifier)
The classification of the activity.
The reference data used in Template: OASIS:
Classifier is restricted as follows:
RDL constraint 1:The reference data for:
OASIS:Classifier.class -> ExternalOwlClass.class
is restricted to the following class or a subclass:
status [0..1] (Template: OASIS:
StateAssertion)
the status of the activity
The reference data used in Template: OASIS:
StateAssertion is restricted as follows:
RDL constraint 1:The status is represented by individuals of the State_of_activity_actual class.
The reference data for:
OASIS:StateAssertion.sameAs -> ExternalOwlObject.individual
is restricted to individuals that are members of the
following
class:
Example reference data is:
names [0..*] (Template: OASIS:
Name)
The names of the activity
Values:
dateStarted [1] (Block: Ap239Ap233Psm:
DateTimeString)
The date and time when the activity started.
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')
dateCompleted [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date and time when the activity ended.
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')