This section specifies the template WorkRequest.
The specification comprises a SysML Block that represents the template and an
associated Parametric Diagram that defines the templates and
PLCS PSMTemplate objects
instantiated by the WorkRequest template.
The specification comprises the following sections:
NOTE
An explanation of a template and its specification is provided in
the
Template
overview
The WorkRequest template describes how to represent a request for some work to be
undertaken.
The WorkRequest 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.
Figure 1 - Templates representing activities
The SysML Block Definition diagram in Figure 2 shows how Work
order is represented in the PLCS PSM.
Figure 2 - Work request model
No templates have been explicitly defined as being related to the WorkRequest template.
NOTE
The WorkRequest template may make reference
to other templates as part of the Parametric Diagram. These are not listed
here.
Figure 3 shows the SysML Block that represents the template. The Block is an abstraction
representing a pattern of templates and PLCS PSMTemplate objects.
The properties, i.e. the SysML Block Part, Reference and Value properties, of the
template's SysML Block are described in the Template
Properties section.
The output ports shown on the template's SysML Block are described in the template output ports section.
The SysML Parametric diagrams for the template Block are shown in template parametric diagram section.
Figure 3 - Template block definition diagram for WorkRequest
The following SysML Part, Reference, and Value properties are defined for this template:
References:
status [0..1] (Block: Ap239Ap233Psm:
ProxyItemSelect)
The reference data used in Block: Ap239Ap233Psm:
ProxyItemSelect is restricted as follows:
RDL constraint 1:The status is represented subclasses of State_of_work_request.
The reference data for:
OASIS:StateAssertion.sameAs -> ExternalOwlObject.individual
is restricted to the following class or a subclass:
Parts:
ids [1..*] (Template: OASIS:
Identification)
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The ids must be classified as an Work_request_identification_code or a
subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
version [0..1] (Template: OASIS:
Identification)
the version identifier being assigned to the
WorkRequest.
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The identifier must be a version identifier.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
classifications [0..*] (Template: OASIS:
Classifier)
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 classes that are subclasses of the following class:
Values:
dateRequested [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
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')
The following output ports are defined for this template:
workRequest (Block: Ap239Ap233Psm:
WorkRequest)
Enables the
Block: Ap239Ap233Psm:
WorkRequest instantiated by this template to be referenced
when the template is used.
There are no constraints defined for this template.
This section describes the template's Parametric Diagrams. Each diagram details
the pattern of templates and PLCS PSMTemplate objects that are required to
represent the template WorkRequest.
The public properties, i.e. those visible in the template's SysML block (See Figure 3) are shown on the left of a
Parametric Diagram.
NOTE
Restrictions on the reference data to be set on the public properties is
defined in the
Template Properties section.
The output ports are shown on the right of a Parametric Diagram.
PLCS PSM
objects are shaded khaki and
Templates
are shaded light green in a Parametric Diagram.
Figure 2 - WorkRequest
Figure 3 - WorkRequest Requestor
Figure 4 - WorkRequest Triggered By
Figure 5 - WorkRequest Applies To
The following blocks are instantiated by this template and bound to private parts
of the
template as shown in the Parametric Diagram
section:
Private Part Property:
workRequest [1] (Block: Ap239Ap233Psm:
WorkRequest)
Private Part Property:
statusAssg [0..1] (Block: Ap239Ap233Psm:
StateAssignment)
Private Part Property:
requestorAsgClassifier [0..1] (Template: OASIS:
Classifier)
Private Reference Property:
classReqAsg [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
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)
Private Part Property:
dateAsgClassifier [0..1] (Template: OASIS:
Classifier)
Private Reference Property:
classDateRequested [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
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)
Private Part Property:
assigneeAsgClassifier [0..*] (Template: OASIS:
Classifier)
Private Reference Property:
classAssignee [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
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)
Private Part Property:
clsTriggeredByAsg [0..1] (Template: OASIS:
Classifier)
Private Reference Property:
clTriggeredBy [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
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)
Private Part Property:
clsAppliesToAsg [0..*] (Template: OASIS:
Classifier)
Private Reference Property:
classSubject [0..1] (Block: Ap239Ap233Psm:
ExternalOwlClass)
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)
Private Part Property:
triggeredByJustification [0..1] (Template: OASIS:
Justification)
Figure 6 shows the instances that have been instantiated in the template. These are
used to set the default value of blocks.
Figure 6 - Model instance diagram for WorkRequest
The following instances have been created:
There are no constraint blocks defined in this template.
No example data sets have been provided for this Template.