Template:- OASIS:ResourceOrderDelivery

The ResourceOrderDelivery template describes how to represent an actual delivery and the associated delivery slip

The SysML Block Definition diagram in Figure 2 shows how a work request is represented in the PLCS PSM.

Template Properties

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

References:
plannedDelivery [1] (Block: Ap239Ap233Psm:DirectedActivity)
The reference to the planned delivery
actualDeliveryItems [0..*] (Block: Ap239Ap233Psm:ManagedResource)
The collection of items the supplier is delivering (the delivery slip)
status [0..1] (Template: OASIS:StateAssertion)
The status of the actual delivery
deliveryMethod [0..1] (Block: Ap239Ap233Psm:ActivityMethod)
The method used for the delivery
deliveryLocation [0..1] (Block: Ap239Ap233Psm:Location)
The location where the delivery is sent
deliveredBy [0..1] (Block: Ap239Ap233Psm:OrganizationOrPersonInOrganizationSelect)
The actor performing the delivery
Parts:
id [1] (Template: OASIS:Identification)
The id of the actual delivery
The reference data used in Template: OASIS:Identification is restricted as follows:
RDL constraint 1:
The id must be classified as a Activity_actual_identification_code or a subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
Values:
actualDeliveryDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The actual date when the delivery is sent

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