Create records to classify Remote Terminal Unit (RTU) events and alarms

Follow this procedure to classify individual event messages uploaded from the Remote Terminal Unit (RTU) using proto_event records.

Proto_event records are stored in the proto_event table, and are created and edited using the proto_event Row Edit dialog box within the Advanced Database Editor (ADE). For general information on ADE and how to create records, refer to the Advanced Database Editor (ADE) Administrator documentation.

To create records to classify RTU events and alarms

1. In ADE, select View > Gas Operations.

2. Navigate to the proto_event Row Edit dialog box.

   

3. Refer to the table below for information on configuring the items on the proto_event Row Edit dialog box.

4. If applicable, select the desired runs/streams from the Bitmask configuration dialog box.

   

   Item	Description
   Name	Enter the name of the proto_event record.
   Event Group	Enter or select the name of the proto_event_grp record with which the proto_event will be grouped.
   Identifier Register	Do one of the following: Enter 0 if using one of the following protocol drivers: Bristol Standard Asynchronous Protocol (BSAP) Driver with Configurable Gas Load (CGL) for OASyS Fisher Remote Operations Controller (ROC)/Fisher Remote Operations Controller (ROC) Plus Driver with Configurable Gas Load (CGL) for OASyS Enter the point type number (the register number from the RTU as contained in the polled event).
   Identifier Vector	Do one of the following: If you are using the Fisher Remote Operations Controller (ROC)/Fisher Remote Operations Controller (ROC) Plus Driver with Configurable Gas Load (CGL) for OASyS, or to match any event type, enter *. If you are using the Bristol Standard Asynchronous Protocol (BSAP) Driver with CGL for OASyS, enter the signal name that triggers the event. Any events for this signal name will be processed the same. Typing "*" will match any signal name. Enter the event type value in the polled event (converted to a text string). Notes: Typing the Vector string "*" may not always be the best option. Since the first matching proto_event record is used to process an event, configuring the Vector string as "*" may cause some events to go to the wrong Run/Stream. The "*" string should only be used when all the events for a specific Register number are to be processed the same way. When using the BSAP driver, since the only valid Register value is 0, all possible events would be processed the same way. Using "*" as a wildcard character within a string is not a valid configuration. For example, a value of "A*" will not match any event type string that begins with "A".
   Message	The event message to use for this particular event.
   Device Problematic	Select to have the system send an event message to AVEVA Measurement Advisor indicating that the event is problematic.
   Remote Event	Select to have the system send the event to the Operational Activities Summary window.
   XOS Alarm	Select to have the system send the Message to the Alarm Summary window with the indicated Alarm Severity.
   Alarm Severity	Select the severity of the alarm. Options: low minor medium major high critical
   Enable Config Updates	Select to have the system update the configuration in AVEVA Measurement Advisor when there is a configuration change in the device.
   Config Item Name	Select the name of the parameter that will be changed.
   Event EFM Dest	Indicate whether you want to apply the event to all runs or all streams, or to a particular run or stream. Options: None – The event is not processed into gas history. Run Number – The event goes to the gasmeter that is configured with a specific run number for the remote. Multiple Runs – The event goes to the gasmeters that are configured for the specified runs for the remote. All Runs – The event goes to all runs configured for the remote. Stream Number – The event goes to the Gas Quality stream that is configured with a specific stream number for the remote. Multiple Streams – The event goes to the Gas Quality streams that are configured for the specified streams for the remote. All Streams – The event goes to all streams configured for the remote. Note: The Totalflow protocol driver ignores these settings. Instead, it uses the run information stored within the event message.
   Run/Stream	Enter the run/stream number for the meter. Notes: Only configure this field if you selected either Run Number or Stream Number in the Event EFM Dest field. This field is not used by the Totalflow Protocol Driver.
   Configure Runs/Streams	Select to open the Bitmask configuration dialog box. Notes: This button is only available if you selected either Multiple Runs or Multiple Streams in the Event EFM Dest field. This functionality is not used by the Totalflow Protocol Driver.