The schema for this table is defined in ces_schema_scada.sql file.

The script, OPAL_scada_ids.sql, populates generic SCADA sources for the OPAL model. A source is any SCADA system that can provide information to the adapter. There could be one SCADA source defined for each of multiple SCADA vendors, or a utility may choose to divide their territory into multiple regions, with each region acting as a separate SCADA source. Each SCADA source must have a unique name as well as a unique integer ID.

 

The SCADA_POINTS table contains a row for each device in the Oracle Utilities Network Management System operations database that has SCADA information associated with it. Each record has a "scada_name" column which, in order to populate one of the measurements tables, must match a valid "scadapop -scada <scada>" parameter - where <scada> is a valid and active scada_ids.scada_name value. Where there is a match, a row is populated in the scada_measurements_st table for each defined attribute.

The SCADA_POINTS table is normally populated via device driven attribute population during the model build process. It is a staging table for the scadapop-driven measurement point population process. It is not accessed during adapter execution.

The schema for this table can be found in the file ces_retain_scada.sql

 

The scada_measurements_st table is a staging table used to help populate the analog_measurements and digital_measurements (production) tables. The schema for this table can be found in the file ces_retain_services.sql.