The EventReportItem template describes how to represent an EventReport item.
Items in an event report could be many type of things:
- observed environments
- observations
- performed activities
- proposed solutions for the problem
- affected items
The SysML Block Definition diagram in Figure 1 shows how a
collection is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
Parts:
itemRoles [0..*] (Template: OASIS:
Classifier)
The collection of roles for the item in the EventReport (
EventReport)
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:
descriptions [0..*] (Template: OASIS:
Descriptor)
The collection of descriptions (optional) for the event report/item relationship
Values:
startEffectivityDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date (optional) when the item in the EventReport starts to be valid
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')
endEffectivityDate [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date (optional) when the item in the EventReport ends to be valid
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')