Dr. Yi Hu, Dr. Damir Novosel Quanta Technology LLC

Transcription

1 Brazil CIGRE B5 PDC Workshop Considerations and Requirements of PDCs for WAMPAC Systems Dr. Yi Hu, Dr. Damir Novosel Quanta Technology LLC Rio de Janeiro, Brazil April 6, 2010

2 Presentation Outline Global WAMPAC Deployment Overview PDCs in Synchrophasor Technology Based WAMPAC PDC requirements Substations PDC requirements Control Centers PDC requirements Discussions Page 2

3 Synchrophasor Technology and WAMPAC Paradigm-shift synchronized measurement technology, has enabled the development and deployment of a new generation of wide-area monitoring, protection and control systems (WAMPAC) with the ability to Take a snap-shot of a large power system at precisely the same moment Track various power system dynamics disturbances, oscillations, etc. Worldwide, there are many deployment projects of large scale WAMPAC are ongoing in USA, Brazil, China, Page 3

4 Large Scale Synchrophasor Deployment in US WECC and EIPP (now NASPI) projects did not start as large scale deployment projects, but as R&D projects resulting in challenges: Scalability and flexibility System performance and interoperability Use of applications by operations Recent Major Projects: Southern California Edison Wide-area Situation Awareness System (WASAS) First deployment project with an approved general rate case Install PMUs in about 70 substations Applications in control room as well as planning and engineering BPA Wide-Area Monitoring and Control Move from the existing research network to a secure, reliable productiongrade synchro-phasor network that will provides the foundation for realtime applications, such as situational awareness and controls /04/00 Event at 12:55 Pacific Time (08/04/00 at 19:55 GMT ) Angle Reference is Grand Coulee Grand Coulee John Day Malin N Colstrip Big Eddy 500 Keeler 500 kv Vincent Devers 500 kv Vincent 500kV Mohave 500kV Devers 500kV Grand Coulee 500kV Page 4

5 US DOE Awarded SGIG Synchrophasor Projects Source: NERC WECC WISP (250 PMUs): PG&E, BPA, SCE, SRP, PacfiCorp, Idaho Power, NV Energy, CAISO NYISO (35 new PMUs) Midwest ISO (150 PMUs) PJM (90 PMUs) ISO New England (30 PMUs) Duke Energy Carolina (45 PMUs) Entergy (18 new PMUs) American Transmission Company LLC two projects (3-5 PMUs) Midwest Energy Inc. (1 substation) Page 5

6 Global Large Scale Synchrophasor Deployment Projects Brazil National Interconnected Power System (NIPS) Synchronized Phasor Measurement System (SPMS) by ONS and 35 Transmission Owners Initially for around 70 substations, based on extensive studies including 350 transmission lines and 40 transformers End-goal to provide full observability of the entire NIPS China State Grid & Southern Power Grid PMUs installed in over 400 substations (765, 500, 330 and 220 kv) By 2012 All 765 and 500 kv substations and generation plants over 600 MW Some 330 and 220 kv substations and generation plants over 300 MW Wide area monitoring applications Page 6

7 Large Scale Deployment of PMU Systems Stringent and varied requirements Must be a production system (full vendor support), high reliability and availability Accommodate all participants while ensuring interconnection performance Address both short and long term needs System expandability Initially limited number of measurements will grow over time including both synchrophasor and non-phasor data System flexibility and adaptability Start with small number of applications and add new in the future Address technology advancements and product development Address relevant standards development that will continue to evolve: NERC CIP ; synchro- phasor (IEEE C37.118); cyber security; IEC 61850, etc. Consider system integration with other enterprise systems, such as EMS/SCADA, DMS, GIS Page 7

8 Major Differences in WAMPAC Deployment Resources sharing is the norm, not an option for the large scale deployment Enable a wide range of widearea monitoring, protection and control applications Many resources can also be used by local intra-substation and inter-substation applications Sharing allows for reducing overall cost and/or increasing system redundancy A network supported system The foundation to allow for resources sharing Entity X Entity Y Control Centers Departments Device A Device B Inter-Entity Sharing Intra-Entity Sharing Intra-Location (e.g. intra-substation) Sharing Entity Z Entity N Substations Applications Device C Device M Page 8

9 Main Considerations in WAMPAC Deployment Synchrophasor data as a continuous data stream from measurement sources to applications Request-response mechanism may not work and will be too slow for many applications Support of one-to-many real-time streaming data distribution Deployment must consider in the initial phase how to enable multiple applications with a diverse requirements to share common resources Continued system expansion and evolvement is a necessity Technologies will continue to advance at a fast pace Standards continue to evolve to keep pace with the technology advancement Constant hardware and software upgrade with improved performance Many WAMPAC applications are still in the development stage and will emerge in the future Most deployment will be limited in scope at the beginning, but are expected to expand over time to support more and more applications Page 9

10 Presentation Outline Global WAMPAC Deployment Overview PDCs in Synchrophasor Technology Based WAMPAC PDC requirements Substations PDC requirements Control Centers PDC requirements Discussions Page 10

11 Roles of Phasor Data Concentrators in WAMPAC A key component to provide important system functions and optimally manage data Increase system flexibility Simplify system interactions and management applications deal with one PDC vs. all PMUs Accommodate various system requirements PMUs generate data at different rates Different data rates required by different applications Balance system requirements (reliability and availability) and cost Page 11

12 Role of Phasor Data Concentrators in WAMPAC Increase system efficiency Minimize/Reduce communication requirements, e.g. bandwidth requirement Compact data for real-time transmission Use local storage to Avoid transmitting high resolution data and/or all data in real-time Allow lower availability communication channels to be used while still achieving high level of completeness of data Shared common processing for multiple applications Time alignment Pre-processing, e.g. down-sampling Data validation and data storage and retrieval management Page 12

13 Main Functions of PDCs in WAMPAC Real-time streaming data handling Data input and checking Receive data from various synchrophasor data sources (PMUs, PDCs, Phasor Gateways, etc.) Determine the integrity and quality of received data Data processing as necessary for data re-distribution Data re-distribution Distributing data to various data users/applications as required Page 13

14 Other Possible PDC Functions Should be part of the overall WAMPAC system May be included in a PDC, depending on type of deployment project and consequent architecture and design Data storage and access management E.g. event detection and archiving Data source management Device configuration info Device status and performance monitoring and reporting Etc. Part of data quality validation and marking In any case, PDCs may need to have a role Page 14

15 Type of PDCs Used for R&D projects, pilot projects less stringent requirements Production systems must meet more stringent requirements Vendor Design and Platform Dedicated, only-pdc systems Specialized hardware/software system platform, or Off-the-shelf hardware and operating system based system Integrated functions of devices and applications Example: PMUs adding simple PDC functions such as data alignment Location Substations Control centers: Top level, regional, sub-regional, local, etc. Any other places where they may be needed Office locations PDC requirements vary depending on the type! Page 15

16 Presentation Outline Global WAMPAC Deployment Overview PDCs in Synchrophasor Technology Based WAMPAC PDC requirements Substations PDC requirements Control Centers PDC requirements Discussions Page 16

17 PDC Requirements for Deployment Projects These are dedicated production systems Discussion focus on two most common types of PDCs seen in these deployment projects Substation PDCs (Sub-PDC) Control center PDCs (CC-PDC) Page 17

18 About Waiting Time and Processing Time in PDCs Data with same time tags typically do not arrive at PDCs at the same time Differences in data sources own latency and delays Uneven communication delays among data sources Typically need to wait for data arrival before starting the processing How long it could wait depend on many factors, such as application data latency requirements and system limitations Could be different for each output data streams (if PDC output multiple re-distributed data streams) and for data storages Processing time must be less than the period between two consecutive data packets for an output stream Depend on the data rate of the re-distributed data streams Page 18

19 Presentation Outline Global WAMPAC Deployment Overview PDCs in Synchrophasor Technology Based WAMPAC PDC requirements Substations PDC requirements Control Centers PDC requirements Discussions Page 19

20 Functional Requirements for Sub-PDCs PMU management functions PMU configuration information management configuration request PMU performance monitoring, alarming and reporting PMU data stream status monitoring PMU data streams performance monitoring (e.g. latency) Sub-PDC performance monitoring Data integrity check (e.g. C packet CRC check) Late and/or missing data handling Abnormal condition alarming and reporting Data reasonableness check? PMU operation control start/stop data streaming, etc. Page 20

21 Functional Requirements for Sub-PDCs (cont.) Input and output interfaces Communication protocols IPv4 and IPv6 Multiple TCP/IP and UDP/IP operating mode support (messagingstreaming data): TCP-TCP, TCP-UDP, UDP-UDP Multicast support in UDP/IP streaming data ability to receive multicast data from PMUs, and send data to user configurable multicast IP address Existing and future protocols: IEEE C communication protocol, future IEC and others (IEEE Std. 1344, etc.) Network interfaces Multiple physical Ethernet ports support e.g. for multiple substation LANs Galvanic and optical connector options Isolated input and output port option e.g. for substation LAN and WAN isolation Page 21

22 Functional Requirements for Sub-PDCs (cont.) Real-time streaming data handling Ingestion support IPv4 and IPv6, multiple synchrophasor protocols (IEEE C37.118, future IEC 61850, etc.), TCP/IP and UDP/IP (unicast and multicast) Processing time alignment, filtering, down-sampling, etc. Re-distribution support IPv4 and IPv6, multiple synchrophasor protocols (IEEE C37.118, future IEC 61850, etc.), TCP/IP and UDP/IP (unicast or multicast), multiple output data streams (local applications, other PDCs such as CC-PDCs, etc.) Data storage management Raw data received could store more data than the re-distributed (e.g. store the highest resolution data while re-distribute lower ones; store single phase phasors and re-distribute only positive sequence ones) Processed data time-aligned, filtered/down-sampled data Output data re-distributed data Page 22

23 Functional Requirements for Sub-PDCs (cont.) HMI/GUI for configuration, diagnostic, and data viewing Configuration Allow maximum configurability for users do not assume anything Ingestion IPv4 or IPv6; synchrophasor protocols (IEEE C37.118, future IEC 61850, etc.); separate TCP/IP and UDP/IP (unicast and multicast) for messaging and data exchange Processing waiting time for time alignment; filter type and parameters; down-sampling parameters; etc. Re-distribution IPv4 or IPv6; synchrophasor protocols (IEEE C37.118, future IEC 61850, etc.); separate TCP/IP and UDP/IP (unicast and multicast) for messaging and data exchange Security compliant with entity s physical and cyber security requirements Page 23

24 Sub-PDC Sizing Requirement System frequency and reporting rate support For 50 or 60 Hz system? Support how many reporting rates? Input sizing No. of PMUs, phasors, and other data contained in each PMU data packet Output sizing No. of output data streams Maximum size of each stream Storage sizing Period of data retention Input raw data Processed data Output data Page 24

25 Performance Requirements for Sub-PDCs System time Sync accuracy to UTC < 1 μs Timing resolution < 1 μs Time and date format conform to ISO 8601 standard Data handling performance requirements Total PDC time = Data ingestion time + Data processing time (alignment, filtering, down sampling, etc.) + Data repacking time for redistribution should be < ½ of the time period between two successive data packets of a data stream for the data rate supported E.g. at maximum 100 (120) fps for 50 (60) Hz system: < 5 (4.16) ms Must meet the above requirement when Sub-PDC is at the maximum configuration Maximum input and output configuration With all data processing functions enabled Availability requirement Compliant to entity s substation critical equipment availability requirements Page 25

26 Other Key Requirements for Sub-PDCs Hardware requirements Must be suitable for operating in substation environment must meet the requirements of relevant international, national, industry and entity specific standards for substation equipment E.g. IEC , IEEE C37.90, IEC , etc. Non-volatile storage is preferred for local data storage Provide options and upgradability for communication interfaces Compliant to entity s other hardware requirements (e.g. higher class seismic requirement for earthquake prone areas) Software requirements Upgradability Self-monitoring and alarming Local and remote configuration Software security requirements at delivery Compliant to entity s other software requirements (e.g. operating systems, common services, etc.) Page 26

27 Presentation Outline Global WAMPAC Deployment Overview PDCs in Synchrophasor Technology Based WAMPAC PDC requirements Substations PDC requirements Control Centers PDC requirements Discussions Page 27

28 Main Difference of Control Center PDCs Generally is part of a WAMPAC in control centers Top level and many second/third level (e.g. regional/subregional) control centers typically have two locations (main and backup or alternative) Overall WAMPAC typically have Operational Production (OP), Production Testing (PT), Development (DEV) and Training Simulator (TS) subsystems Not only receiving data and re-distributing data to WAMPAC applications in control centers, but may also need to exchange data with other systems or provide data to other users Exchange data with other systems within entity intra-entity data exchange (e.g. EMS/SCADA system) Exchange data with other WAMPAC of other entities inter-entity data exchange Provide data to other users within entity e.g. to planning, engineering, protection, automation, users Page 28

29 Main Difference of Control Center PDCs (cont.) Generally is part of a WAMPAC in control centers (cont.) System and data management function support PMU/PDC data stream status monitoring, alarming and reporting Support for Quality of Service e.g. input data stream performance monitoring, CC-PDC performance monitoring, etc. Data alignment, pre-processing and validation Event detection and archiving Will need to consider entity s control center hardware and software procurement requirements Preferred hardware (servers, network equipment, etc.) Preferred software environment (operating systems) Preferred database, software tools, etc. Enterprise common services Page 29

30 ISO/SO Control Center WAMPAC Overview Page 30

31 Deployment View of A Production WAMPAC Page 31

32 Functional Requirements for CC-PDCs Input and output interfaces Communication protocols Similar requirements as Sub-PDCs but in general will need to support additional protocols, such as ICCP, OPC, and other protocols for exchanging data with other systems, such as EMS/SCADA Network interfaces Similar requirements as Sub-PDCs but may need to have more Ethernet ports than Sub-PDCs to support more network connections (with other entities, to phasor gateways, etc.) Real-time streaming data handling Similar requirements as Sub-PDCs for data ingestion, processing and re-distributing but must be able to handle much higher volume of data input/output than Sub-PDCs Data validation may be required Page 32

33 Functional Requirements for CC-PDCs (cont.) Data storage management Two types of data storage online and historian data storage Online data storage: all raw data, processed data (time-aligned data, filtered/down-sampled data), validated data and re-distributed data will be kept for a specified period of time before discarded Historian data storage: may store low resolution historical data, event data, or all data Data storage systems may not be part of CC-PDC may require additional database interfaces to common databases Manage missing data retrieval with other PMUs/PDCs HMI/GUI for configuration, diagnostic, and data viewing Shall provide similar functions as Sub-PDC Security compliant with entity s control center physical and cyber security requirements Page 33

34 CC-PDC Sizing Requirement System frequency and reporting rate support Similar requirements as Sub-PDCs but typically need to be able to support all reporting rates Input and output sizing Typically only have initial sizing based on Input: initial No. of PMUs/Sub-PDCs/Other PDCs and No. of phasors and other data contained in each data packet Output: Initial sizing based on No. of output data streams and maximum size of each stream Must be expandable for future system expansion May provide a maximum sizing if the size of the future system is known Page 34

35 CC-PDC Sizing Requirement (cont.) Storage sizing may be included if CC-PDC has its own data storage systems or as a sizing guideline for external data storage systems On-line database sizing Depend on: Period of data retention; Input raw data points; Processed data Historian database sizing Depend on types of databases and/or storage/retrieval system used Whether event detection and event archive is used or not Page 35

36 Performance Requirements for CC-PDCs System time The same as Sub-PDC Data handling performance requirements The same total processing time requirement as for Sub-PDC but must be able to handle much higher data volume both initially and after expansion Availability requirement Compliant to entity s control center critical equipment availability requirements Page 36

37 Other Key Requirements for CC-PDCs Hardware and software requirements The same as other critical control center systems, such as EMS/SCADA system, such as Redundant system configuration (both local for each location and remote by having installation at least at two locations) High availability Uninterrupted operation Open system design Page 37

38 Anything else? Additional PMU-PDC/PDC-PDC messaging scheme to support system functionalities System architecture support Hierarchical and peer-to-peer (including multicasting) Messaging protocol suite TCP/IP and/or UDP/IP Device (PMU, PDC) configuration and status info Request/response Notification for configuration change, status change for orderly shutdown/startup, alarms, reports Data quality flagging Late or missing data handling Detection, Notification, Request/Response, Data transfer mechanism Needs industry to work out solutions for these functionalities Page 38

39 Presentation Outline Global WAMPAC Deployment Overview PDCs in Synchrophasor Technology Based WAMPAC PDC requirements Substations PDC requirements Control Centers PDC requirements Discussions Page 39

40 Discussions Page 40

41 Contact information Dr. Yi Hu, Director WAMPAC Quanta Technology LLC 4020 Westchase Blvd., Suite 300 Raleigh, NC 27607, U.S.A. Phone: Cell: Page 41

42

43 Increase System Flexibilities System interactions PMU-Application interactions E.g. if PDCs are used, applications will need to deal with less devices directly, such as configure an application to access data For some tasks, such as data preprocessing and data validation, it may not be efficient for every application to do it It may not be possible for every application to talk to every PMUs when PMUs are supplying data to multiple applications Accommodate different system requirements It may not be possible for every PMU to meet diverse requirements of all applications that use their data nightmare for managing the configuration of the PMUs and applications Page 43