| Life cycle data for process plant: Reference data for observations and measurements | ISO/WD 15926-x:200x(E) |
A monitoring_activity receives information about a time_variation_of_property from an observing_activity and issues messages according to pre-set criteria.
EXAMPLE 1 Consider the activity which monitors the temperature of mill M_101 during 2007-12-13, shown in Figure 1.
There are two activities linked by a flow of information:
measuring_activity which measures the temperature of mill M_101; andmonitoring_activity which issues a message whenever the temperature crosses one of two set levels, going up.The measuring_activity is recorded as follows:
:Measure_oil_temperature_for_mill_M-101_during_2007-12-31
a iso15926-x:measuring_activity ;
iso15926-x:observes_variation_of_property ;
[ a iso15926-x:time_variation_of_property ;
rdfs:subPropertyOf myOnt:oilTemperature ;
iso15926-x:domain_of_variation
:M-101_during_2007-12-31
] ;
iso15926-x:gives_result_record
:Oil_temperature_for_mill_M-101_during_2007-12-31_signal .
The definition of the domain of variation is:
:M-101_during_2007-12-31
iso15926-2:temporal_part_of :M-101 ;
iso15926-x:during
[ topology:end_1_of_edge [ iso15926-x:utc_iso8601 "2007-12-30T24:00" ] ;
topology:end_2_of_edge [ iso15926-x:utc_iso8601 "2007-12-31T24:00" ] ] .
The monitoring_activity is recorded as follows:
:Monitor_oil_temperature_for_mill_M-101_during_2007-12-31
a iso15926-x:monitoring_activity ;
iso15926-x:reads_record
:Oil_temperature_for_mill_M-101_during_2007-12-31_signal ;
iso15926-x:has_monitoring_criteria_set
[ owl:oneOf ( :Mill_type_ABC_OilTemperatureHigh
:Mill_type_ABC_OilTemperatureHighHigh ) ] .
The complete set of criteria for a monitoring_activity is specified by a has_monitoring_criteria_set.
A temporal part of
time_variation_of_property can be a member of a monitoring criterion.
EXAMPLE 2 The monitoring criteria for the monitoring_activity in example 1 are:
These criteria can be defined as follows:
:Mill_type_ABC_OilTemperatureHigh
[ owl:intersectionOf (
[ a iso15926-x:level_crossing_criterion ;
iso15926-x:set_level [ iso15926-4:celsius [ basics:decimal "100" ] ] ;
iso15926-x:set_tolerance [ iso15926-4:celsius [ basics:decimal "5" ] ] ]
iso15926-x:going_up ) ] .
:Mill_type_ABC_OilTemperatureHighHigh
[ owl:intersectionOf (
[ a iso15926-x:level_crossing_criterion ;
iso15926-x:set_level [ iso15926-4:celsius [ basics:decimal "150" ] ] ;
iso15926-x:set_tolerance [ iso15926-4:celsius [ basics:decimal "5" ] ] ]
iso15926-x:going_up ) ] .
The set_tolerance prevents multiple level crossing messages being generated when the temperature hovers around the specified level.
The class going_up is included as part of the criterion, to prevent level crossing messages being generated when the temperature falls.
A monitoring_activity issues a message whenever it finds a temporal part of a
time_variation_of_property which is a member of one of its criteria.
EXAMPLE 2 The variation of the oil temperature for mill M_101 during 2007-12-31 has two level crossings, as shown in Figure 2.
The monitoring_activity issues two messages which contain formulae as follows:
Oil_temperature_for_mill_M-101_during_2007-12-31_message-1
[ a iso15926-x:time_variation_of_property ;
rdfs:subPropertyOf myOnt:oilTemperature ;
iso15926-x:domain_of_variation [ iso15926-2:temporal_part_of :M_101 ] ;
iso15926-x:variation_during
[ iso15926-x:nominal_value [ iso15926-x:utc_iso8601 "2007-12-31T11:15" ] ] ]
]
a :Mill_type_ABC_OilTemperatureHigh .
Oil_temperature_for_mill_M-101_during_2007-12-31_message-2
[ a iso15926-x:time_variation_of_property ;
rdfs:subPropertyOf myOnt:oilTemperature ;
iso15926-x:domain_of_variation
[ iso15926-2:temporal_part_of :M_101 ] ;
iso15926-x:variation_during
[ iso15926-x:nominal_value [ iso15926-x:utc_iso8601 "2007-12-31T22:50" ] ] ]
]
a :Mill_type_ABC_OilTemperatureHighHigh .
These messages record:
M_101;myOnt:oilTemperature;Mill_type_ABC_OilTemperatureHigh or
Mill_type_ABC_OilTemperatureHighHigh.The messages could be sent by e-mail, published on the Web within journal file, or processed by a dedicated system. On a journal file, the provenance of a message could be recorded as follows:
:Monitor_oil_temperature_for_mill_M-101_during_2007-12-31
iso15926-x:creates_formula
:Oil_temperature_for_mill_M-101_during_2007-12-31_message-1
{
[ a iso15926-x:time_variation_of_property ;
rdfs:subPropertyOf myOnt:oilTemperature ;
iso15926-x:domain_of_variation
[ iso15926-2:temporal_part_of :M_101 ] ;
iso15926-x:variation_during
[ iso15926-x:nominal_value [ iso15926-x:utc_iso8601 "2007-12-31T11:15" ] ] ]
]
a :Mill_type_ABC_OilTemperatureHigh
} .
An object is a monitoring_activity if and only if:
iso15926-2:activity;time_variation_of_property is detected which is a member of one of a set of specified monitoring criteria classes.NOTE 1 The monitored time_variation_of_property for a monitoring_activity is specified by a monitors property.
NOTE 2 An input signal for a monitoring_activity is specified by a reads_record property.
NOTE 3 The set of monitoring criteria classes for a monitoring_Activity is specified by a has_monitoring_criteria_set property.
NOTE 4 A monitoring_activity can receive an input signal from a different measuring_activity. Alternatively a monitoring_activity can also measure, in which case it is also classified as a measuring_activity.
NOTE 5 An output message formula, content or record for a monitoring_activity can be recorded by a gives_monitoring_formula, gives_monitoring_content, or gives_monitoring_record property.
NOTE 6 OWL specification:
--> <owl:Class rdf:about="&iso15926-x;monitoring_activity"> <rdfs:subClassOf rdf:resource="&iso15926-2;activity"/> <rdfs:isDefinedBy rdf:resource="&iso15926-x-doc;/monitoring_activity.htm#monitoring_activity"/> </owl:Class> <!--
An object is a
monitors
relationship if and only if:
basics:mapping between monitoring_activity and time_variation_of_property;monitoring_activity looks for parts of a time_variation_of_property that are members of specified monitoring criteria classes.NOTE OWL specification:
--> <owl:ObjectProperty rdf:about="&iso15926-x;monitors"> <rdfs:domain rdf:resource="&iso15926-x;monitoring_activity"/> <rdfs:range rdf:resource="&iso15926-x;time_variation_of_property"/> <rdfs:isDefinedBy rdf:resource="&iso15926-x-doc;/monitoring_activity.htm#monitors"/> </owl:ObjectProperty> <!--
An object is a
has_monitoring_criteria_set relationship if and only if:
basics:mapping between monitoring_activity and a set of subclasses of time_variation_of_property;monitoring_activity looks for parts of a
time_variation_of_property which are members one of the set.NOTE 1 The domain of has_monitoring_criteria_set is the powerset of the powerset of
time_variation_of_property. This is inconvenient, but inescapable.
NOTE 2 OWL specification:
--> <owl:ObjectProperty rdf:about="&iso15926-x;has_monitoring_criteria_set"> <rdfs:domain rdf:resource="&iso15926-x;monitoring_activity"/> <rdfs:range rdf:resource="&iso15926-x;class_of_class_of_time_variation_of_property"/> <rdfs:isDefinedBy rdf:resource="&iso15926-x-doc;/monitoring_activity.htm#has_monitoring_criteria_set"/> </owl:ObjectProperty> <!--
An object is a gives_monitoring_formula relationship if and only if:
basics:mapping between monitoring_activity and formula;formula is about parts of the monitored time_variation_of_property that meet the monitoring criteria and that have been detected by the monitoring_activity.The relationship gives_monitoring_formula is a specialisation of creates_formula.
NOTE OWL specification:
--> <owl:ObjectProperty rdf:about="&iso15926-x;gives_monitoring_formula"> <rdfs:domain rdf:resource="&iso15926-x;monitoring_activity"/> <rdfs:range rdf:resource="&iso15926-x;formula"/> <rdfs:subPropertyOf rdf:resource="&iso15926-x;creates_formula"/> <rdfs:isDefinedBy rdf:resource="&iso15926-x-doc;/monitoring_activity.htm#gives_monitoring_formula"/> </owl:ObjectProperty> <!--
An object is a gives_monitoring_content relationship if and only if:
basics:mapping between monitoring_activity and information_content;information_content is about parts of the monitored time_variation_of_property that meet the monitoring criteria and that have been detected by the monitoring_activity.The relationship gives_monitoring_content is a specialisation of creates_content.
NOTE OWL specification:
--> <owl:ObjectProperty rdf:about="&iso15926-x;gives_monitoring_content"> <rdfs:domain rdf:resource="&iso15926-x;monitoring_activity"/> <rdfs:range rdf:resource="&iso15926-x;information_content"/> <rdfs:subPropertyOf rdf:resource="&iso15926-x;creates_content"/> <rdfs:isDefinedBy rdf:resource="&iso15926-x-doc;/monitoring_activity.htm#gives_monitoring_content"/> </owl:ObjectProperty> <!--
An object is a gives_monitoring_record relationship if and only if:
basics:mapping between monitoring_activity and information_carrier;information_carrier has contents about parts of the monitored time_variation_of_property that meet the monitoring criteria and that have been detected by the monitoring_activity.The relationship gives_monitoring_record is a specialisation of creates_record.
NOTE OWL specification:
--> <owl:ObjectProperty rdf:about="&iso15926-x;gives_monitoring_record"> <rdfs:domain rdf:resource="&iso15926-x;monitoring_activity"/> <rdfs:range rdf:resource="&iso15926-x;information_carrier"/> <rdfs:subPropertyOf rdf:resource="&iso15926-x;creates_record"/> <rdfs:isDefinedBy rdf:resource="&iso15926-x-doc;/monitoring_activity.htm#gives_monitoring_record"/> </owl:ObjectProperty> <!--
© ISO 200x — All rights reserved