Steady-State Loading & Resource Utilization

Since all data for SCADA Analog, Limit, Accumulator, and Status Point devices is always captured and persisted to the 4-Way Data Buffers (described above), there is no increase in EMS Host CPU Loading, Memory Requirements, Disk Resources, or I/O Loading during EMS System Disturbances or Failover. Similarly, Pegasus Data Servers are steady state regardless of EMS Host activity. Pegasus Data Servers automatically detect EMS Host Failover, but incur no significant processing load as a function of EMS Failover, Electrical System Grid activity, or SCADA Database Schema changes.

The Pegasus SCADA data stream is not stored “by exception”. Several proprietary techniques, in addition to standard data stream compression, are used to reduce disk storage requirements. Note that since data is not stored “by exception”; there are no “Points to Select” or “Dead Bands to Set”, greatly reducing installation and operational maintenance.

For approximately 60,000 SCADA Objects at 1 Site (over 320,000 SCADA Objects are scanned across all 5 Sites), scanned every 5 seconds and permanently stored every 1 minute at 1 Site, the Pegasus Data Collector (PDC) requires less than 2% nominal loading on a dual 400 MHz Compaq Alpha EMS Server. A Pegasus Data Server managing all real-time refresh and permanently managing & storing real-time history for those same 60,000 SCADA Objects requires less than 5% nominal loading on a dual 3 GHz Dell P4-based Server (and considerably less on current Multi-Core Servers).

In both cases, peak loading is less than 10% and does not occur as a function of EMS Server activity, but rather as a function of routine activities performed by Pegasus (e.g. Pegasus loading is steady-state with respect to EMS Server loading). The only load that varies on Pegasus Data Servers is the number of concurrent Clients (thru the Pegasus APIs) retrieving data.