Alarm Data Table

You can store alarms from a ROC in a Geo SCADA Expert Data Table. The Data Table will have a specific schema entry. Unlike the other ROC Plus database objects, Data Tables are generic database objects (see Configuring Data Tables in the Geo SCADA Expert Guide to Core Configuration).

 

To create a Data Table:

1. Right-click on the required group in the Database Bar.
   A context-sensitive menu is displayed.
2. Select the Create New option, followed by the Tables and Grids option.
3. Select the Data Table option.
   A new Data Table is added to the database.
4. Specify a suitable name for the Data Table (taking into account the Geo SCADA Expert naming restrictions).
5. Right-click on the Data Table entry in the Database Bar and select the Edit Properties option. Specify a suitable Table Name and Title for the table and then save the configuration.
6. Do not make any other changes to the table.

 

The Geo SCADA Expert ROC Plus Driver can create the correct columns in the Data Table automatically. To do this, you need to associate the Data Table with the relevant Geo SCADA Expert ROC Plus Scanner object. To do this:

1. Display the properties window (‘configuration Form’) for the ROC Plus Scanner object.
2. On the Options tab, locate the Alarms and Events section.
3. Use the browse button next to the Alarm Data Table field to display a Reference browse window. Locate and select the Data Table that you have just added to the database.
4. Save the configuration changes.
   The ROC Plus driver will create the correct columns in the Data Table, providing that the Data Table contains 0 records and the Get Alarms option is enabled on the Scanner. (If the referenced data table is not empty, the driver will not create columns, because data loss could possibly occur.)

 

A correctly configured Alarm Data Table is included in the ROC PlusDemo.sde file.

A single Data Table can store alarms from multiple flow computers. For the Geo SCADA Expert ROC Plus Driver to populate an Alarm Data Table, the table has to contain the columns that are shown in the figure below, with the correct data type at a minimum. Additional columns are allowed, but the driver will only populate those columns that are shown below. The columns that the driver adds to the Alarm Data Table are described below.

The underlying alarms are described in the Opcode 118 section in the ROC Protocol Specifications Manual.

• AlarmAction. A numeric code indicating what the alarm action was. This is the raw value that the driver gets from the ROC.
• AlarmActionDescription. The driver’s decoding of the AlarmAction field.
• AlarmCode. A numeric code indicating the reason why the alarm was logged. This is the raw value that the driver gets from the ROC.
• AlarmCodeDescription. The driver’s decoding of the AlarmCode field.
• Alarm Description. This is a text description of the alarm that comes directly from the ROC.
• AlarmType. A numeric code indicating the type of alarm. This is the raw value that the driver gets from the ROC.
• AlarmTypeDescription. The driver’s decoding of the AlarmType field.
• Logical. This is the location or logical location for Parameter alarms only.
• MeterName. This column is populated with the contents of the Meter Name field on the Scanner tab of the ROC Plus Scanner object that retrieved the alarms. This information is provided as a convenient way to filter alarms records from multiple ROCs.
• Parameter. This is the parameter that was changed. The ParameterDescription column shows the driver’s decoding of this parameter number, but for the sake of auditability, the raw parameter number is also populated in the data table.
• Parameter Description. This is the driver’s decoding of the parameter. This is provided for convenience, so that anyone reading the Alarm Table does not have to manually decode the information (for example, to ascertain that PointNumber = 113 and Parameter = 15 refers to an orifice plate diameter).
• Point Number. This is the point that was changed. The PointNumberDescription column shows the driver’s decoding of the point number, but for the sake of auditability, the raw point number is also populated in the data table.
• Point Number Description. This is the driver’s decoding of the point number. This is provided for convenience.
• ScannerId. This is the Geo SCADA Expert database ID of the ROC Plus Scanner object that populated this record in the Alarm Data Table. This information might prove useful in an SQL query as part of a filter or a join.
• SRBX. This indicates whether the alarm was a spontaneous report by exception (SRBX) alarm.
• Timestamp. This is the time of the alarm with the offset in the ROC Time Zone field on the Scanner tab of the ROC Plus Scanner object applied. This value is stored in the data table as a UTC time, so it can be used to sort or filter in an SQL query. As this value is stored as a time, ViewX or Virtual ViewX fixes the value when the Data Table is displayed.
• TimestampString. This is the time of the alarm from the ROC with no offsets applied. Because this value is stored as a string, ViewX or Virtual ViewX do not fix the value when it is displayed. This column is provided for auditability.
• Value. This is the value of the parameter at the time of the alarm.