EAI within control centre- Integration of legacy SCADA/AGC system with network applications

Transcription

1 EAI within control centre- Integration of legacy SCADA/AGC system with network applications N.Čukalevski, G.Jakupović, M.Stojić, J.Trhulj Mihailo Pupin Institute, Belgrade, SCG D.Vlaisavljević, B.Filipović EPS, Belgrade, SCG EPCC-8, Les Diablerets, Switzerland 08. June 2005.

2 Motivation within ESI The ESI today is becoming liberalized and market oriented. More actors, parties, transactions, exchange volumes, Lower reserves Different generation and flow patterns Increased complexity of company's daily operation.

3 Motivation within ESI As a consequence, need for more data (information) at faster pace. Requirement and need to exchange data with other ESI actors. Need to integrate existing isolated systems

4 EPS: quantitative portrait (2004) Installed capacity of generation: MW Total power generation at EPS: GWh HV (400,220,110 kv) lines: 9497 km Substations capacity: MVA Controlled by 1 NDC and 6 RCC NDC controls power plants and 400, 220 kv network

5 Motivations within EPS control system Relatively low level of TM coverage: about 20 from 40 system objects. Limited control system functionality: just SCADA/AGC Existing control system isolated: operation data not used outside the control room

6 CS IT related open problems Existing SCADA/AGC vendor specific s/w with no open API available. No appropriate data model for data definition and maintenance. No relational DB for data engineering. No explicit technological address for basic entities.

7 Integration Project goals To increase the functionality of the control system by adding several network app s (NT, SE, BLF). To allow for integration with other app s within and outside the CC.

8 Integration Project phased approach adopted: Intra-control centre application integration (AI). Control centre integration with other systems (EAI).

9 Intra-control centre application integration

10 Control centre integration with other systems (EAI)

11 Main architectural features Data level application integration employing Application Data Base (ADB) Openness: SCADA API, DB-MW (ISO SQL92), Flexibility: relative ease of expansion employing: standard DB-MW, XML based data exchange, web-interface

12 SCADA API functionality Real-time data read/write, from/to SCADA run-time memory segments. Access/exchange of the following data: Analogous measurements Status indications Alarms Commands

13 SCADA API s/w architecture

14 SCADA Connector performs Mapping of measurements/indications associated to topological devices with their points within SCADA. Periodic scanning and updates of measurements/indications from SCADA. Additional data sanity checking. Triggering of NT-SE-BLF applications.

15 Application data base content: All data necessary to represent static network topology Network parameters Software parameters Network application I/O data

16

17 Implementation Standard H/W OS: Linux, Windows C++ RDBMS: MySQL, ver.4.1.xx ODBC XML

18 Network applications Network Topology determination (NT) Static State Estimation (SE): orthogonal, with Givens rotations, observabillity, bad data detection, Bus Load Forecast (BLF)

19 System testing: In two phases: FAT, SAT Content: Different system sizes (FAT) Different levels of TM coverage Functionality test Performance test

20 FAT configuration

21 SAT configuration

22 System testing data Number of nodes: 100 Number of analog measurements: 320 Zero injections: 60 Pseudo measurements: initially 14 needed Observability reached with 2 additional RTU s commissioned in the meantime. Low Redundancy: 1.8

23 Measured vs estimated data

24 Conclusions Successful and efficient intra CC data-level integration with affordable tools. Platform for standard-based inter CC integration (basic EAI). Estimated values at operators disposal. Availability of estimated values even for the (still) untelemmetered objects.

25 Thank you! For further information contact: