CIM Issues #7124
Rename SCADA package as Communications package
IEC 61970-301
Description
From the early days of the CIM, the Meas package includes a definition of measurable values, and the SCADA package includes the classes RemoteUnit, RemotePoint, RemoteControl that record some of the information used by SCADA systems for communication with remote devices. However the SCADA package does not have a full model of a SCADA system.
The classes RemoteUnit and CommsLink are quite generic.
RemoteUnit has an enumerated type : RTU, SubstationControlSystem, ControlCenter, IED
When discussing extensions for new protocols like IEC 61850, or IEEE 2030.5, some people are confused by the package prefix SCADA, as this is assumed to mean that communication is only performed by a dedicated SCADA systems.
It would be clearer to rename the SCADA package as "Communications".
Proposed Solution
Rename SCADA package as Communications package
Updated by Svein Olsen 9 days ago
I do agree that the name SCADA can be confusing and misleading if one is associated with the traditional SCADA application. However, SCADA stands for Supervisory Control and Data Acquisition. Without linking this to application it could be argued that both Meas and Senor part of AuxiliarEuipment should be part of a packaged that deals with Supervisory Control and Data Acquisition. I am open for changing the name, but I do not think "Communication". This could lead to the association that this packaged deals with communication protocols. Maybe ICCPConfiguration could be a candidate for "Communication" as this is a mapping between CIM and Inter-Control Center Communications Protocol (ICCP). The current ICCPConfiguration is not a good name on this packaged.
That Meas include Control does not make sense. In general I would prefer that we agree what should be inside the packaged first and then we can agree on names. However, if I needed to pick one word I would choose Supervisory – The overarching function that involves observing, analyzing, and making decisions based on acquired data.
What we quickly can agree on is changing the current description:
"
Contains entities to model information used by Supervisory Control and Data Acquisition (SCADA) applications. Supervisory control supports operator control of equipment, such as opening or closing a breaker. Data acquisition gathers telemetered data from various sources. The subtypes of the Telemetry entity deliberately match the UCA and IEC 61850 definitions.
This package also supports alarm presentation but it is not expected to be used by other applications.
"
changes to:
"
Contains entities to model information used for operational supervision, control, and data acquisition in power system applications function. Supervision involves real-time monitoring and decision support, enabling operator and automated control of equipment such as opening or closing a breaker. Data acquisition gathers real-time measurements from various sources, independent of the underlying communication technology.
"
Updated by Todd Viegut 3 days ago
19-Feb-2025: Weekly TF13 call
Discussed the additional comments posted by Svein. The consensus is that "Supervisory" is a better name that is not so generic as "Communications" but not so restrictive as "SCADA" and seems to better support the intent of the issue Tom has raised.