RDBMS Configuration
The Network Management System Generic SCADA Adapter (RTAdapter) utilizes several RDBMS tables for both configuration and run-time operation.
Configuration tables include:
The tables below are configuration tables that generally need to be populated via project specific sql scripts. Example configuration for these tables is provided for the Oracle (OPAL) model in $NMS_HOME/sql/OPAL_scada.sql.
• SCADA_MEASUREMENTS_ST: SCADA point configuration staging table used to populate the ANALOG_MEASUREMENTS and DIGITAL_MEASURMENTS run-time SCADA measurement tables - required.
• The SCADA_MEASUREMENTS_ST staging table can be populated via the scadapop process or by a project specific mechanism.
• The SCADA_MEASUREMENTS_ST table can be truncated and repopulated at will while DDService is active (running). Once SCADA_MEASUREMENTS_ST is populated as desired the UpdateDDS -recacheMeasures command will send a message to DDService to merge updates from the SCADA_MEASUREMENTS_ST staging table into the ANALOG_MEASUREMENTS and/or DIGITAL_MEASURMENTS runtime SCADA tables - preserving any existing run-time quality codes and/or stored SCADA data values. Note the same process (UpdateDDS -recacheMeasures) also merges information from the SCADA_CONTROLS_ST staging table (if populated) into the SCADA_CONTROLS runtime table.
• SCADA_IDS: SCADA Adapter configuration table - required for both RTAdapter and optional scadapop processes.
• Maps name of each SCADA adapter to a unique integer used to specify SCADA specific configuration in related SCADA configuration tables.
• SCADA_STATES: SCADA Adapter configuration table – maps strings to integers - optional.
• SCADA_SYNONYMS: SCADA Adapter configuration table – maps SCADA input to NMS attributes and/or conditions - required.
• SCADA_LINKS: SCADA Adapter configuration table used to initially identify an active external Live Energy Connect server. Used when Live Energy Connect is using RDBMS (rather than more proprietary LEC Real-Time-Protocol) for updates into NMS. Also used for (related) routine heartbeat processing.
• SCADA_POINTS: staging table used by the scadapop process to help populate SCADA_MEASUREMENTS_ST and SCADA_CONTROLS_ST –optional.
Note: The RTAdapter process does not require population of the SCADA_POINTS table. The use of SCADA_POINTS as a staging table is merely one optional solution for the ultimate goal of configuring the required SCADA measurements staging table (SCADA_MEASUREMENTS_ST) and optionally the SCADA_CONTROLS_ST table. If the SCADA_POINTS table is used it can be populated via the standard Network Management System Model Build process or via a project specific mechanism.
Runtime Tables Used by RTAdapter Regardless of Polling Mode
• ANALOG_MEASUREMENTS: Standard NMS table defining analog measurements from an external SCADA.
• DIGITAL_MEASUREMENTS: Standard NMS table defining digital measurements from an external SCADA.
• SCADA_VIEW: NMS maintained view on network_components, analog_measurements, digital_measurements, attributes, classes and units tables. Used by RTAdapter and/or external SCADA systems for access to current NMS SCADA information.
• SCADA_CONTROLS: SCADA run-time control table - defines which NMS outbound control actions are valid for each NMS device and attribute – required to support NMS outbound SCADA controls.
• The SCADA_CONTROLS_ST table can be populated via the scadapop process or by a project specific mechanism.
• The SCADA_CONTROLS table is loaded by the DDService process on startup and can be reloaded by a running DDService by issuing the UpdateDDS -recachMeasures request.
Runtime Queuing Tables Used by RTAdapter in RDBMS Polling (Preferred) Mode
• SCADA_ANALOG_IN: RTAdapter polling table used to queue incoming analog SCADA updates.
• SCADA_DIGITAL_IN: RTAdapter polling table used to queue incoming digital SCADA updates.
• SCADA_CONDITION_IN: RTAdapter polling table used to queue incoming condition (note, tag, etc) SCADA updates. Must be activated via corresponding RT_CONDITIONS_IN SRS_RULE.
• SCADA_RESPONSE_IN: Optional RTAdapter polling table used to register responses to NMS outbound control or tag requests. Must be activated via corresponding RT_RESPONSE_IN SRS_RULE.