SCADA Metadata Generation With Change History
In addition to collecting, persisting, and marshaling real-time (and older data) from the EMS
SCADA Hosts to the Pegasus Data Servers, Pegasus’ PDC also retrieves the EMS Database key
values (names) for every SCADA Object (all Analogs, Limits, Accumulators, and Status Points)
from the SCADA Database. The PDC generates a Pegasus Invariant Key (IKey) for every SCADA
Object scanned & stored. This Invariant Key is used throughout Pegasus for data storage,
management, retrieval, and presentation.
Pegasus detects and manages all changes in EMS SCADA Database Objects, while retaining the
Object’s Pegasus Invariant Key, to insure all SCADA Database Objects retain their full data
history in the Pegasus RDS™. Pegasus automatically generates new Invariant Keys for new
SCADA Objects and communicates those keys along with all Metadata describing the Invariant
Key to the Pegasus Data Servers. A Pegasus Rapport-FG user interface (EMS Host resident UI)
assists the EMS Analyst in managing the rare SCADA database changes that cannot be
automatically resolved by the Pegasus PDC.
Pegasus Servers store both current SCADA Metadata and all historical changes to SCADA
Metadata over time (e.g. a full Audit Trail by SCADA Object and by time). All SCADA metadata is
stored in standard SQLServer database tables, easily accessible through the Smart Client or by
Custom Applications that access these tables directly.