The ResourceOrder template describes how to represent an order(the request) of supplies
from a customer to a supplier.
The SysML Block Definition diagram in Figure 2 shows how a
work request is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
documents [0..*] (Template: OASIS:
Document)
The collection of documents for the order
contract [0..1] (Template: OASIS:
Contract)
The contract under which the order is sent
Parts:
ids [1..*] (Template: OASIS:
Identification)
The collection of identifications for the resource order
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The id 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:
name [0..1] (Template: OASIS:
Name)
The name for the resource order
classifications [1..*] (Template: OASIS:
Classifier)
The collection of classifications for the order.
The reference data used in Template: OASIS:
Classifier is restricted as follows:
RDL constraint 1:There must be at least one class that is, or is a subclass of, Resource_order to indicate
the type of the resource order. For example a SparePartOrder
The reference data for:
ExternalOwlClass.class
is restricted to the following class or a subclass:
Values:
orderDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date when the order is placed
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')