Author: Jorge Miguel Ordacgi Filho, ONS, Brazil
Before going back in time - briefly
When SCADA systems started to be implemented in Control Centers, most of the substations were protected and controlled by electromechanical devices and some substations had static (electronic) devices. This meant that all substation secondary systems were based on one kind of analogue technology. Except for remote measurements, that required one transducer for each specific quantity (f, V, I, P and Q), these devices were only able to communicate data by plain binary means: electrical contacts. The word then was data! What else could substation protection and control devices send up but data? Raw data only!
By that time, it was common that substation and control center operators had different readings for the same electrical quantity, because of the use of distinct transducers, sometimes with different accuracy classes. What to say about energy and power demand measurements for billing purposes? In Brazil, and probably all around the world, they still remain without any direct relation with f, V, I, P and Q measurements used by the operators.
Another typical condition of those days was that SCADA systems had to pick up their data (measurements and status of breakers and switches) within existing substations, which should be minimally "disturbed" by the introduction of extra transducers and auxiliary relays to cope with the SCADA needs. These transducers and auxiliary relays had to be wired to existing devices and to the remote terminal unit (RTU), so minimal "disturbance" meant minimum wiring. Even with all possible care, many accidental trips occurred, as usual when dealing with substations in service.
Could logic checks, at least, be done at the substation level? Of course, yes. But such logic checks demanded more wiring, which imposed more accidental tripping risks, so they were not even considered. On the other hand, logic checks could be implemented in new substations without risks of accidental tripping, but why should they be implemented? Control centers had processing capacity, control centers demanded all data, and control centers could do more through SCADA systems! In fact, SCADA systems quickly evolved with new and fascinating facilities: one of them was the state estimator, required by the unavailability of RTUs in all substations. The absence of local logic tests led the state estimators to be complemented by topological estimators. Even though, a plain inconsistency of a switch secondary contacts was enough to impose some complicated problems for the state estimation. It must be bared in mind that busbar static protections could do such kind of check since the sixties. But the devices could not "talk" among themselves and share information, despite some of them already being able to transform raw data into information with great added value.
Sequence of events (SOE) became a must, despite having no time synchronism among substations, the task of analyzing a disturbance was so demanding that any tip was most welcome. Disturbance analysis engineers were (and still are) so skilled that they could time synchronize manually the majority of the available data and transform the whole thing into information that supported a detailed report about the events in the power system.
Still back in time - more briefly, but under specialists' view point
The prevalent conditions in substation and control centers were quite clear during the dawn of SCADA systems: no processing capability was available at the substation level and control centers were inherently built with processing capacity and human-machine-interface. Clearly, the two teams of specialists -control center people and substation visionaries - had different problems to cope with. The difference in the immediate needs put the two teams apart. No competition between them, but no common goal, except for the time synchronization among RTUs: a demand of control center specialists to be solved by substation and communication specialists.
This situation is beginning to change because:
To sum up, synchrophasor measurement systems and wide area control and protection systems are important and challenging for both substation and control center people. But why should the two communities stick to them, now when substation PAC systems can already be much more useful for control centers?
The question above shall be rephrased this way: why not start to do deeper use of substation processing capabilities and send no more data to the control centers, but information with great added value? This would leave the control center processing capability to be used for even more "noble" tasks.
It can be done right away
Digital technology evolved so fast that PAC systems are effectively available at the bay and substation levels. Since the implementation of the first coordinated systems, one may say that the word system is properly applied to the substation secondary environment. Nevertheless, there were still limitations concerning intra-substation communication, mainly when products from different vendors had to be integrated in the same PAC system. Any substation planned to be built in more than one stage - the majority - could easily have fair PAC digital systems provided by distinct manufacturers. From the control center viewpoint, there could be many PAC systems provided by as many vendors, once there were substation data concentrators that could handle all the distinct communication protocols out of the RTUs and send to the upper level all the data. Only raw data, because there was no new stimulation for local processing, except for special means. It doesn't mean that the first PAC digital systems were not able to solve a significant share of existing problems, such as time synchronization. They solved it and did more, for instance:
Nowadays, there are no more limitations stemming from substation communication, thanks to IEC61850 standard. It allows all vendors to use the same communication protocol while preserving their proprietary algorithms. More than that, IEC61850 imposes a new way of conceiving and thinking about PAC substation systems with positive consequences over a number of issues. Perhaps the less discussed one would be local data processing to check all substation data (measurements and status), transforming them into information and sending messages with added value to control centers. This necessarily includes SOE and other similar issues.
Comparison of measurements and status data improves the identification of incorrect measurements, providing correct quantities to the control center. In a near future it will be all part of a self-healing process of the PAC system.
Any inconsistency and measurement problem will immediately generate local or remote alarm. The word remotely means not only that the remote operator will be warned, surely, but that the state estimator will acknowledge any problem that could not be solved at the substation level.
The procedures will bring the following benefits:
There are practically no technical challenges in achieving the benefits above. A lot more can be done, but a wider integration between substation and control center specialists. A new way of thinking shall be imposed to both groups for the sake of operators and real-time engineers.
