Understand the Reflex Monitor

The Reflex Monitor application is designed to monitor a field on a configured point. If that field changes to the reflex record's pre-defined Required Trigger State, it is an indication that it is time to execute a series of actions, which have been defined in the Action Sequence record. The Action Sequences can be responsible for automating activities such as pipeline shutdowns, pump starts, or other essential activities.

By using the Reflex Monitor application, you are introducing an extra layer of automated safety to your Action Sequence execution. For example, pipeline shutdowns can be automatically issued if a valve closes. Additionally, valves along your flow's pathway can be opened if a pump starts. As long as you have something to act as a trigger, a reflex record can eliminate the burden of manually monitoring data to find out when to act.

The Reflex Monitor application performs the following checks to ensure that the pipeline's automation activities are executed safely:

• A timeout period check. When the Required Trigger State is entered, the reflex can count down from a configured value. When the end of the timeout period has been reached, the Action Sequences will be executed. If the point leaves the Required Trigger State during the period, the Action Sequences will not be started.

• A data quality threshold check. The data quality is continuously monitored and collected. Your Administrator will have defined a quality threshold that the data must meet or exceed to execute the Action Sequences. If you are in your Trigger State but have not met or exceeded your data quality threshold, nothing will happen until your data quality improves (and even then, the evaluation is subject to the timeout period information).

• A configuration error check. If the Trigger Point or at least one Action Sequence associated with the reflex record is detected to be missing, the Data Quality of the reflex record will transition from Fresh to Error. A reflex that has a Data Quality of Error will not execute the associated Action Sequences until the configuration issue is resolved.