This template describes how to represent the fact that something has been observed
to be
in a given state and that this assertion has been confirmed by evidence such as a
measurement.
NOTE
An asserted state should be used for representing business process states such as
Approval and work order states.
For details on how represent a hypothesized state, see StateAssessment.
The asserted state is assigned by a AppliedStateAssignment.
This is not instantiated by this template, but is needed to assign the observed state
to something.
When assigning the state, the role of the AppliedStateAssignment
should be specified by being classified. For example, if the sate observed is a fault
state
then the AppliedStateAssignment should be classified by as a
http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Fault_state_assignment.
The SysML Block Definition diagram in Figure 1
shows how State is represented in the PLCS PSM.
The following SysML Part, Reference, and Value properties are defined for this template:
References:
definition [1] (Block: Ap239Ap233Psm:
ProxyItemSelect)
The reference data that identifies the state definition that the observed
state is asserted to be in.
The reference data used in Block: Ap239Ap233Psm:
ProxyItemSelect is restricted as follows:
RDL constraint 1:The reference data for:
ExternalOwlObject.individual
is restricted to individuals that are members of the
following
class:
Parts:
id [0..1] (Template: OASIS:
Identification)
An optional identification of the observed state.
The reference data used in Template: OASIS:
Identification is restricted as follows:
RDL constraint 1:The id must be classified as a state definition identification code.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
name [0..1] (Template: OASIS:
Name)
An optional name of the observed state.
Values:
assertionDateTime [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date or dateTime when the observed state was asserted to be a defined state.
NOTE
The assertionDateTime and the observationDateTime may be the same
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')
observationDateTime [0..1] (Block: Ap239Ap233Psm:
DateTimeString)
The date or dateTime when the state was observed.
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')