180 likes | 516 Views
7/15/2012. NERC-DME and DOE-EIPP PMU. 2. Major Blackouts - Increased Oversight NERC*
E N D
1. NERC-DME and DOE-EIPP PMU/DC A Review of Their Different Requirements and theBenefits of Their Convergence Harish I. Mehta
Mehta Tech, Inc.
Fault and Disturbance Analysis Conference
May 2, 2006
2. 7/17/2012 NERC-DME and DOE-EIPP PMU 2 Major Blackouts - Increased OversightNERC* – ERO** – Mandatory RegulationsDME*** and PMU/DC**** As we endeavor to satisfy the data requirements specified in NERC-DME and EIPP-PMU requirements we face challenges not addressed before. We need to choose between different data acquisition solutions for each or a common solution with various options. This paper presents an analysis to identify these challenges without advocating a specific solution.
* NERC – North American Reliability Council
** ERO – Electric Reliability Organization
*** DME – Disturbance Monitoring Equipment
**** PMU/DC – Phasor Measurement Unit/Data Concentrator
3. 7/17/2012 NERC-DME and DOE-EIPP PMU 3 Major Blackouts - Increased OversightNERC – ERO – Mandatory Regulations November 9, 1965 Blackout
Formation of NERC and Regional Reliability Councils
August 14, 2003 Blackout
DOE-EIPP* – Demonstration Project - 2003
Energy Policy Act of 2005 including a directive to form ERO – 2005
* DOE – Department of Energy
EIPP – Eastern Interconnect Phasor Project
4. 7/17/2012 NERC-DME and DOE-EIPP PMU 4 Major Blackouts - Increased OversightNERC – ERO – Mandatory Regulations Changes in Oversight Authority
Electric Reliability Organization - ERO
ERO - NERC with Enforcement Responsibilities - 2006
Reliability Monitoring/Reporting Standards – 2006/2008
Development of Standards PRC-002, 003, 004 and 018
Disturbance Monitoring and Reporting Equipment (DME) Standards
SAR (Standard Authorization Request) for PMU/DC
5. 7/17/2012 NERC-DME and DOE-EIPP PMU 5 NERC-DME Standards DME Recordings*
Sequence of Events Recording
Digital Fault Recording
Dynamic Disturbance Recording
Data from dedicated or multifunction devices that follow industry practices
Trigger-initiated fault and sequence of events recording
Long (10-days) buffer for disturbance recording
Data in each type of recordings have different attributes
* While NERC is a standards writing entity, it does not write equipment standards. DME standards define NERC’s application requirements for disturbance monitoring. These standards permit the use of multifunction devices without restricting their use for non-disturbance monitoring applications.
6. 7/17/2012 NERC-DME and DOE-EIPP PMU 6 NERC-DME Information Disturbance Analysis using DME Recordings
Event Analysis/Reconstruction – Disturbance, Fault, Sequence of Events
Analysis of Protection System Operations
Model Verification
Long-term Reliability Analysis, Benchmarking, Compliance verification
7. 7/17/2012 NERC-DME and DOE-EIPP PMU 7 EIPP – Eastern Interconnect Phasor Project Visionary Demonstration Project*
With the efforts of broad spectrum of stakeholders, advance one component of information landscape, namely information systems, covering regional issues
Make better use of measurements and information to improve system performance
* Summary of information on EIPP Website
8. 7/17/2012 NERC-DME and DOE-EIPP PMU 8 DOE-EIPP PMU/DC and RTDMS Real-time Uses of PMU/DC Data Real-time Wide Area Visualization
Real-time Visualization based on information with system’s “Functional Status” for “Situational Awareness”*
Host Super DC at TVA to create Wide Area Views for participants
Automatic Detection of System Anomalies
Oscillation Detection, Phase Angle comparison, etc.
Wide Area Protection and Control (Future)
* DOE/FERC February 2006 Report to the Congress pursuant to the Section 1839 of Energy Policy Act of 2005
9. 7/17/2012 NERC-DME and DOE-EIPP PMU 9 DOE-EIPP PMU/DC and RTDMS Off-line Analysis Using PMU/DC Data
Off-line Analysis*
State Estimation with improved accuracy
System Model verification
Disturbance analysis
* Information with Functional Status and Situational Awareness to assist the Reliability Coordinators may require integration of some of the off-line analysis in the on-line applications.
10. 7/17/2012 NERC-DME and DOE-EIPP PMU 10 NERC DME and EIPP PMU/DCKey Overlap and Differences Time Sync
DME < 4 milliseconds of UTC (Universal Time Code)
PMU/DC < 50 microseconds of UTC
Measurement Accuracies
DME Follow Customary Industry Practices
Accuracy defined for the signal at DME input terminals
PMU/DC < 1% TVE – Total Vector Error Traceable to NIST Standards (to be issued in 2006)
Accuracy defined for the primary currents, voltages and events
11. 7/17/2012 NERC-DME and DOE-EIPP PMU 11 NERC DME and EIPP PMU/DCKey Overlap and Differences Local Processing to detect Anomalies for Recordings
DME
DFR (Waveform recording) Trigger-initiated
SER (Event recording) Change of state
DDR (RMS recording) 10-day buffer
PMU/DC
PDS - Phasor Data Stream 20-30 phasor/sec data stream
Positive sequence values only
Local Analysis including triggers (local detection of anomalies) is not required
12. 7/17/2012 NERC-DME and DOE-EIPP PMU 12 NERC DME and EIPP PMU/DCKey Overlap and Differences DME – Multiple Data Types
DFR Point on the Waveform equally spaced measurements
SER High speed event monitoring
DDR 6 equally spaced RMS values per second
PMU/DC - Single Data Type
PDS – Phasor Data Stream Data Stream of equally spaced phasor values at a rate of 20 to 60 times per second
13. 7/17/2012 NERC-DME and DOE-EIPP PMU 13 NERC DME and EIPP PMU/DCKey Overlap and Differences DME Data Capture Capacities
DFR and SER Assure “event” capture
(sufficient storage for several credible events under severe operating conditions)
DDR 10-day (preferably local)
(capacity defined to assure data availability for delayed request)
PMU/DC Data Capture Capacities
Accurately time-tagged Phasor and Event Data
Availability of data from certain, as opposed to all sites is acceptable
14. 7/17/2012 NERC-DME and DOE-EIPP PMU 14 NERC DME and EIPP PMU/DCKey Overlap and Differences
DME Data Communication
No NERC specified requirement
Utilities use Manufacturer’s Data Communication Protocols for Record Retrieval
High-speed Data Communication Backbones*
Data communication protocol (as defined in C37.118) is preferred, other schemes are accepted
* EIPP presently recognizes the inherent delays in the range of seconds for data communications in a geographically distributed system.
15. 7/17/2012 NERC-DME and DOE-EIPP PMU 15 NERC DME and EIPP PMU/DCKey Overlap and Differences
Future Wide Area Monitoring Needs
Power System “Functional Status” and “Situational Awareness” will require capture of additional information similar to DME data
Network communication is required for data and information transfer – IEEE C37.118 and/or IEC 61850?
Calculation of results in PMU/DC for quicker response and/or reduced communication burden
16. 7/17/2012 NERC-DME and DOE-EIPP PMU 16 DME and PMU/DC Key Differences Communication Requirements for Wide Area Monitoring
EIPP PMU/DC requires real-time data communication
NERC-DME has no such requirement
Measurement and Time Sync Practices
EIPP requires accurate measurements including allowance for wiring and measurement device influences
Equally spaced and time-tagged phasor values
Defined test and calibration procedures
Generalized Provisions for Different Data Types
DME includes a wider set of data types than just the positive sequence data type in PMU
17. 7/17/2012 NERC-DME and DOE-EIPP PMU 17 DME and PMU/DC Data Acquisition The differences in data acquisition for DME and PMU applications deserve careful attention for various reasons
Use of dedicated or multifunction devices
Consistent data for various purposes – differences in accuracies for signals to device terminals or for primary measurements on a sustained basis can be a major challenge
Common software tools for DME and PMU/DC data formats, analysis, protocols, etc.
Wider foundation for long-term installed system support without addition of specialized devices or software
18. 7/17/2012 NERC-DME and DOE-EIPP PMU 18 DME and PMU/DC Common Data Acquisition Commit to Common Data Acquisition Capabilities
Provide support for collection of all data types required for DME and PMU applications – treat phasors as one more DME data type
Avoid requirements that conflict with common data acquisition
Permit use of devices that meet any combination of data types
Allow different level of application compliance
Define appropriate “accuracy, test, verification, periodic testing and certification requirements” for each data type
Define provisions for error handling in measurement and data handling for common data acquisition capabilities
Develop standards or collection of consistent standards (e.g. data format, etc.) that support all data types