Template:- OASIS:Contract

The Contract template describes how to represent a contract and the relationship between a contract and the parties and documents involved, and the products created and/or actions undertaken as a result of the contract.

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

Template Properties

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

References:
documents [0..*] (Template: OASIS:Document)
The collection of documents representing the contract.
contractor [0..1] (Template: OASIS:Organization)
The organization establishing the contract
contractee [0..1] (Template: OASIS:Organization)
The organization contracted by the contractor
contractorContact [0..1] (Template: OASIS:PersonInOrganization)
The person representing the contractor in the contract
contracteeContact [0..1] (Template: OASIS:PersonInOrganization)
The person representing the contractee in the contract
assignedTo [0..1] (Block: Ap239Ap233Psm:ContractAssignmentSelect)
The object on which the contract is assigned to.
applicableLocations [0..*] (Block: Ap239Ap233Psm:Location)
The geographical location where the contract is valid.
Parts:
ids [1..*] (Template: OASIS:Identification)
The collection of identifiers of the contract
The reference data used in Template: OASIS:Identification is restricted as follows:
RDL constraint 1:
The id must be classified as an Contract_identification_code or a subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
names [0..*] (Template: OASIS:Name)
The collection of names of the contract
descriptions [0..*] (Template: OASIS:Descriptor)
The collection of descriptions of the contract
classifications [0..*] (Template: OASIS:Classifier)
The classification of the contract.
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:
startDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date when the contract starts

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')
endDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date when the contract ends.

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')
signOffDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date when the contract is signed off

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')
assignedToStartEffectivityDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The start effectivity date of the assignedTo object

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')
assignedToEndEffecitivityDate [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The end effectivity date of the assignedTo object

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