The EventReport template describes how to represent the report of an event. As it
could report on many things, this concept is represented as a Collection and can
potentially contain:
- documents
- observed environments
- observations
- performed activities
- proposed solutions for the problem
- affected items
The SysML Block Definition diagram in Figure 1 shows how a
activity 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)
A collection of documents assigned to the EventReport
approvals [0..*] (Block: Ap239Ap233Psm:
Approval)
The collection of approvals for the report
contract [0..1] (Template: OASIS:
Contract)
The contract reference the event report is linked with
Parts:
ids [1..*] (Template: OASIS:
Identification)
The collection of identification of the EventReport (
Collection)
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:There must be one identifier that identifies the
Collection.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
classifications [0..*] (Template: OASIS:
Classifier)
The collection of classifications for the EventReport (
Collection)
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:
versionId [1] (Template: OASIS:
Identification)
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:
Values:
creationDate [1] (Block: Ap239Ap233Psm:
DateTimeString)
The date when the report is created
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')
closureDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date when the report is closed
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')