Template:- OASIS:Observation

This template describes how to represent an observation made on something such as a product or an activity. A typical observation is the symptom of a fault

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

Template Properties

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

References:
observedByEquipment [0..*] (Template: OASIS:RealizedPart)

the person or equipment that did the observing. By default this is a piece of physical equipment, represented by ProductAsRealized.

NOTE    One use of Observation is to provide a link between health monitoring equipment and the file it produces (recorded as a Document).
observedDuring [0..1] (Block: Ap239Ap233Psm:ActivityActual)

the ActivityActual that was being performed when the observation was made. The value of this attribute need not be specified.

EXAMPLE 3   An unexpected problem may be found during a maintenance activity, in which case the ActivityActual is the maintenance activity itself.
EXAMPLE 4   Aircraft health monitoring data is collected during a flight. The flight profile may be recorded using the ActivityActual.
NOTE 3   Some business rules may require that an observation is always made against an ActivityActual, while others may not require that the activity be recorded.
observedByPersOrg [0..*] (Block: Ap239Ap233Psm:PersonOrOrganizationOrPersonInOrganizationSelect)

the person or organization that did the observing.

inContext [0..*] (Block: Ap239Ap233Psm:ObservedContextSelect)

the context in which the observation is made.

EXAMPLE    A problem is found during a maintenance operation. The set of contexts can include the equipment being maintained, the end product the equipment is fitted to, the activity being undertaken, the manual that describes the activity and the resources being used.
Parts:
descriptions [0..*] (Template: OASIS:Descriptor)
The description of the Observation that has been observed.
classifications [0..*] (Template: OASIS:Classifier)

The classifications of the Observation made.

NOTE    If the observation is a symptom, then is shoudl be calssifed as such using http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Symptom
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:
http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/plcs/plcs-psm/refdata/plcs-psm#Observation
ids [1..*] (Template: OASIS:Identification)
The collection of identifiers of the observation.
The reference data used in Template: OASIS:Identification is restricted as follows:
RDL constraint 1:
The id must be classified as a Observation_identification_code or a subclass thereof.
The reference data for:
OASIS:Identification.role -> ExternalOwlClass.class
is restricted to the following class or a subclass:
http://docs.oasis-open.org/plcs/ns/plcslib/v1.0/data/contexts/OASIS/refdata/plcs-rdl#Observation_identification_code
names [0..*] (Template: OASIS:Name)
The collection of names of the observation.
Values:
dateObserved [0..1] (Block: Ap239Ap233Psm:DateTimeString)
The date/time when the Observation was made.

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