EDS 2 Early Delivery Systems Release 3 – WebEx Conference July 10, 2007.
-
Upload
roger-norman -
Category
Documents
-
view
217 -
download
1
Transcript of EDS 2 Early Delivery Systems Release 3 – WebEx Conference July 10, 2007.
EDS 2Early Delivery Systems
Release 3 – WebEx ConferenceJuly 10, 2007
2EDS 2 – Release 3July 2007
Page 2EDS 2 – Early Delivery Systems
Agenda– Overview
• Timeline• Context Setting
– EDS 1 – Release 1 (ERCOT Alarm Processing)– EDS 1 – Release 2 (Point to Point Verification)– EDS 2 – Release 3 (Data Quality)– EDS 2 – Release 4 (Network Model)
– EDS 2 Release 3• Organization Chart• Protocol References and Standards• Key Activities• Procedures• Metrics
– Next Steps and Questions
3EDS 2 – Release 3July 2007
Page 3Texas Nodal Program TimelineE
DS
4
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Alarms Processing
FAT
EMS 2A
ED
S 1
ED
S 2
ED
S 3
FAT – Rel 3
EMS 2B EDW 1
FAT – Release 4
NMMS 1 NMMS 2 EIP 1
FAT – Release 5
REG 1 MMS 1
EMS 2C
EIP 2 S&B 1MIS 1EIP 3
EDW 2
FAT – Release 6
EMS 3EDW 3
EIP 4
FAT – Release 7
EDW 4CRR 1CMM 1 EIP 5
FAT – Release 8
MMS 2S&B 2
EDW 5 EIP 6
FAT – Release 9
MMS 2S&B 2
OS
NMMS 3 EMS 4EDW 6
EIP 7EMS 5 DIS
P2P Checkout
SE Verification
ITEST
RTM Go-Live
DAM Go-Live
EDS 2 Release 3: SE VerEMS- State Estimator & Tel Perf Stds,NSA, SPS/RAP, SCADA and DynRatings for Single Model
EDW– SE Statistics
EDS 2 Release 4: NM VerNMMS- Network Model, NOMCR
EMS- EMS /NMMS Interface
EIP
EDS 3 Release 5: LMPsMMS– SCED
EMS- NSA, RLC
COMS- S&B (FIP, FOP,Ver Costs)- Registration
EIPMISEDW
EDS 3 Release 6: LFC TestingEMS- LFC
EIPEDW
EDS 3 Release 7: CRRCRRCOMS- CMM
EIPEDW
EDS 4 Release 8: RT SettlementsMMS- RT Settlements InterfaceS&BEIP, EDWEDS 4 Release 9: DAM, RUCMMS- All Markets- OSEMS – Load Forecast, Out EvalNMMSS&BEIP, EDW
ITEST
ITEST
LegendIntegration TestingProject FAT Activities
Settlements Statements
Upload Bids
Test Settlements
Outages DAM, RUC, SASMFull Nodal Functionality
24*7 Operation 168 Hr Test
NOMCR Chk out Network Model Verification
Rel 1
Rel 2
EDS 1 Release 1:EMS COTS
EDS 1 Release 2:ICCP Upgrade
Rel 3
FAT
EDS
FAT
ITEST
EDS
FAT
ITEST
EDS
SCED TestingRegUpload Offers
Rel 4
Rel 5
Rel 7
Rel 6
6 month LMP Posting
CRR Data Validation Trial Ops of CRR
LFC Comms Testing
ITEST
EDS
FAT
FAT
EDS
ITEST
ED
S 4 Go-Live
Activities
EDS 1 EDS 2 EDS 3 EDS 4
MP Interface Spec
Start of EDS activities
FAT milestones
EDS Preparatory Milestones
Rel 8
Rel 9
LFC Testing
ReadinessDeclaration
Readiness Declarations
EDS 2 – Release 3
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
4EDS 2 – Release 3July 2007
Page 4EDS 2 - Release 3 TimelineE
DS
4
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Alarms Processing
FAT
EMS 2A
ED
S 1
ED
S 2
ED
S 3
FAT – Rel 3
EMS 2B EDW 1
FAT – Release 4
NMMS 1 NMMS 2 EIP 1
FAT – Release 5
REG 1 MMS 1
EMS 2C
EIP 2 S&B 1MIS 1EIP 3
EDW 2
FAT – Release 6
EMS 3EDW 3
EIP 4
FAT – Release 7
EDW 4CRR 1CMM 1 EIP 5
FAT – Release 8
MMS 2S&B 2
EDW 5 EIP 6
FAT – Release 9
MMS 2S&B 2
OS
NMMS 3 EMS 4EDW 6
EIP 7EMS 5 DIS
P2P Checkout
SE Verification
ITEST
RTM Go-Live
DAM Go-Live
EDS 2 Release 3: SE VerEMS- State Estimator & Tel Perf Stds,NSA, SPS/RAP, SCADA and DynRatings for Single Model
EDW– SE Statistics
EDS 2 Release 4: NM VerNMMS- Network Model, NOMCR
EMS- EMS /NMMS Interface
EIP
EDS 3 Release 5: LMPsMMS– SCED
EMS- NSA, RLC
COMS- S&B (FIP, FOP,Ver Costs)- Registration
EIPMISEDW
EDS 3 Release 6: LFC TestingEMS- LFC
EIPEDW
EDS 3 Release 7: CRRCRRCOMS- CMM
EIPEDW
EDS 4 Release 8: RT SettlementsMMS- RT Settlements InterfaceS&BEIP, EDWEDS 4 Release 9: DAM, RUCMMS- All Markets- OSEMS – Load Forecast, Out EvalNMMSS&BEIP, EDW
ITEST
ITEST
LegendIntegration TestingProject FAT Activities
Settlements Statements
Upload Bids
Test Settlements
Outages DAM, RUC, SASMFull Nodal Functionality
24*7 Operation 168 Hr Test
NOMCR Chk out Network Model Verification
Rel 1
Rel 2
EDS 1 Release 1:EMS COTS
EDS 1 Release 2:ICCP Upgrade
Rel 3
FAT
EDS
FAT
ITEST
EDS
FAT
ITEST
EDS
SCED TestingRegUpload Offers
Rel 4
Rel 5
Rel 7
Rel 6
6 month LMP Posting
CRR Data Validation Trial Ops of CRR
LFC Comms Testing
ITEST
EDS
FAT
FAT
EDS
ITEST
ED
S 4
Go-LiveActivities
EDS 1 EDS 2 EDS 3 EDS 4
MP Interface Spec
Start of EDS activities
FAT milestones
EDS Preparatory Milestones
Rel 8
Rel 9
LFC Testing
ReadinessDeclaration
Readiness Declarations
Protocols
Standards
Zonal Procedures
Trans Plan
Use Cases
Inputs
Nodal Procedures
MP Extracts
Completed Metrics
Verified Protocols
Activities Timeline Deliverables
Nodal
TPTF
Tele
& SE
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
2007 2008
Load Modeling
Procedure Creation
Jun Jul Aug Sep Oct Nov Dec JanMay
EDS2.R3: EMS 2B+2C (no Telemerty stats)
EDS2.R3 Metrics
Procedure Verification
EDW Reportsare available
MIS Accessis available
EDS 2 Starts
5EDS 2 – Release 3July 2007
Page 5EDS 2 – Early Delivery Systems
EDS 2 – Context Setting– EDS 1 Release 1 Activities (started April 1, 2007)
• ERCOT Alarm Processing – verify that SCADA alarm status and limits are configured correctly
– Largely an internal ERCOT activity with limited involvement by MPs
– EDS 1 Release 2 Activities (started June 1, 2007)• Nodal Point-to-Point Verification of ICCP mapping and refresh rates
– Each market participant has been scheduled to provide ERCOT with Nodal ICCP point data, and after their data is loaded into the Nodal ICCP/EMS system, they will provide operators to verify each station (point by point) with ERCOT operators.
– This activity has a 4 month duration (June 1 thru Sept 30)– Approximately 100,000 points need to be loaded and verified– Progress-to-date
» 7,000 CenterPoint Energy points have been verified» 17,000 of 23,000 Oncor (TXU) points have been verified» 1,200 NRG points have been verified
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
6EDS 2 – Release 3July 2007
Page 6EDS 2 – Early Delivery Systems
EDS 2 – Release 3– EDS 2 Release 3 Activities (scheduled to start September 2007)
• Measure Telemetry performance– accumulates data over a quarter
• Verify, tune and measure State Estimator performance– accumulates data over a month
• Verify the Network Security Analysis functions• Generate and post Telemetry and SE performance reporting
– New EMS tool and with reporting via Enterprise Data Warehouse– October / November 2007 timeframe
• Provide access to Telemetry and SE performance reporting (MIS / TML)– November / December 2007 timeframe
• Implement Telemetry and SE performance data issue resolution process– Working jointing with each market participant– November 2007 timeframe
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
7EDS 2 – Release 3July 2007
Page 7EDS 2 – Early Delivery Systems
EDS 2 – Release 4– EDS 2 Release 4 Activities (scheduled to start November 2007)
• Verify Network Model Management System (NMMS)• Verify NOMCR (Network Operations Modeling Change Request) process
– Detailed plan to follow that schedules the verification of each TSP– Submit and process NOMCR– Receive confirmation and verification
• Verify model export process• Begin “Single Entry Process”
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
8EDS 2 – Release 3July 2007
Page 8EDS 1 – Release 1 Configuration
EDS 1 - Release 1
Objectives EDS 1 - Release 1 System Diagram
Configure ERCOT Alarm Processing: * Identify the desired alarm process configurations * Design approach to categorize, organize and prioritize alarms * Gain approval of the design with ERCOT OperationsConfigure the approved design * Verify the new configuration with selected TSPs and QSEs * Implement Alarm Configuration on Nodal EMS (COTS)
TPTF Activities Mapping5.4.1.2.f5.4.1.2.g
* Verify Alarm Processing for changes in status* Verify Alarm Processing for limit violations
Genesys 3.1.1
Network Model
EMS 2.2
NSA
SESCADA
EMS 2.2 to 2.3
converter
SCADA
Nodal – EMS (COTS)
EMS 2.3
DNP
RTU Map
Zonal Telemetry
Zonal - EMS
TSP
QSE
ICCP 2.3
ICCP Map
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
9EDS 2 – Release 3July 2007
Page 9EDS 1 – Release 2 Configuration
EDS 1 - Release 2
Objectives EDS 1 - Release 2 System Diagram
ICCP Communications * Verify ICCP failover and performance: - for each TSP and QSE - for ERCOT
Point-to-Point Verification * Verify each station for all TSPs and QSEs * Identify issues, request TSP/QSE to submit changes * SCADA database under full change control process
TPTF Activities Mapping5.4.1.1
5.4.1.2.d5.4.1.2.e5.4.1.2.k
* Install systems* Build and verify graphic displays for all substations* Verify actual telemetry from TSPs and QSEs
* Verify redundant communication (ERCOT, MP)* Verify telemetry meets performance requirements* Verify telemetry meets Protocol 3.10.7.4 (failover, scan rates)
Genesys 3.1.1
Network Model
OAG 2.4
Map
OAG 2.4
Map
EMS 2.2
NSA
SESCADA
Nodal Telemetry
EMS 2.2 to 2.3
converter
SCADA
Nodal – EMS (COTS)
EMS 2.3
DNP
RTU Map
Zonal Telemetry
Zonal - EMS
Nodalpts
QSE
Zonalpts
ICCP 2.3
ICCP Map TSP
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
10EDS 2 – Release 3July 2007
Page 10EDS 2 – Release 3 Configuration
EDS 2 - Release 3
Objectives EDS 2 - Release 3 System Diagram
SE Verification * Verify SE performance * Provide report to TSPs and QSEs
Telemetry Verification * Verify Telemetry performance * Provide report to TSPs and QSEs Network Security Analysis * Compare NSA to Zonal * Continuously monitor Monday - Friday
TPTF Activities Mapping5.4.1.2.b5.4.1.2.c
5.4.2.15.4.2.25.4.2.4
5.4.3.15.4.3.25.4.3.3
* Verify Transmission Element constraints* Verify TSP calculations likely binding in SCED
* Verify SE Performance (3.10.9)* Begin trial of SE test based on live SCADA* Begin continuous SCADA (6.3.2)
* Begin NSA* Compare NSA to Zonal * Continuously monitor Mon - Fri (6.5.7.1.11)
Genesys 3.1.1
Network Model
OAG 2.4
Map
OAG 2.4
Map
EMS 2.2
NSA
SESCADA
Nodal Telemetry
EMS 2.2 to 2.3
converter
Report exceptions
NSA
SESCADA
Telemetry
Performance
SE
Customs
Zonal Nodal
Nodal – EMS (COTS+)
Reporting
EDWRTC
Archive
MIS
EMS 2.3
DNP
RTU Map
Zonal Telemetry
Zonal - EMS
TSP
QSE
TSP
QSE Nodal
QSE
Zonal
ICCP 2.3
ICCP Map TSP
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
11EDS 2 – Release 3July 2007
Page 11EDS 2 – Release 4 Configuration
EDS 2 - Release 4
Objectives EDS 2 - Release 4 System Diagram
NMMS Network Model Verification * Verify NMMS Database is successfully loaded with: * Network Model Database * ICCP Database * Ownership / Operatorship * Placed under change control * Verify NMMS and EMS Integration * Verify EMS Applications * Verify NMMS Functionality * Verify NOMCR Process
TPTF Activities Mapping5.4.1.2.a * Model data & telemetry meet Protocol 3.10
(NOMCR)Genesys 3.1.1
Network Model
OAG 2.4
Map
OAG 2.4
Map
EMS 2.2
NSA
SESCADA
Nodal - NMMS
CIM
Network Model
SCADA Model
Nodal Telemetry
NSA
SESCADA
Telemetry
Performance
SE
Customs
Zonal Nodal
Nodal – EMS (COTS+)
Reporting
EDWRTC
Archive
MIS
EMS 2.3
Network Model Interface
DNP
RTU Map
Zonal Telemetry
QSE
Zonal - EMS
TSP
QSE
MIS
TSP
Nodalpts
TSP
QSE
ICCP 2.3
ICCP Map TSP
Zonalpts
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
12EDS 2 – Release 3July 2007
Page 12EDS 2 – Early Delivery Systems
EDS 2 Release 3 - Organization
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
EDS 2 – Early Delivery System – Release 3 Organization Chart
Market Participants
TransmissionServiceProvider
(TSP)
EDS 2
DevelopProcedures
EDS 2 – Release 3 Team Organization
QualifiedScheduling
Entity(QSE)
Metrics
Verify SE
Verify NSA
Telemetry and SEPerformance
MIS / TMLAccess
OperationsSupport
AdvancedNetwork
Applications
OperationsPlanning
OutageCoordination
OperationsSupport
Engineering
Grid Operations Client Services EMMS Production
13EDS 2 – Release 3July 2007
Page 13EDS 2 – Release 3 Scope
Ref # Name
3.10.7.4 Telemetry Criteria
6.5.7.1.1 SCADA Telemetry
6.5.7.1.2 Network Topology Builder
6.5.7.1.3 Bus Load Forecast
6.5.7.1.4 State Estimator
6.5.7.1.5 Topology Consistency Analyzer
6.5.7.1.6 Breakers/Switch Status Alarm Processor and FOD
6.5.7.1.7 Real-Time Weather and Dynamic Rating Processor
6.5.7.1.8 Overload Alarm Processor
6.5.7.1.9 Contingency List and Contingency Screening
6.5.7.1.10 Network Security Analysis Processor and Security Violation Alarm
6.5.7.1.13 (4) Data Inputs and Outputs for Real-Time Sequence Hourly Reports
Nodal Protocols References
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
14EDS 2 – Release 3July 2007
Page 14EDS 2 – Release 3 Scope
Telemetry Standard – TAC Approved for Nodal– General Telemetry Performance Criteria
• The sum of flows into any telemetered bus must be less than the greater of 5 MW or 5% of the largest line rating at each bus
• 98% of all telemetry must be available at least 80% each quarter
– Critically Important Telemetry Performance Criteria• ERCOT shall identify 10% of MW / MVar pairs that are critically important
• ERCOT shall identify 20 voltage points that are critically important
– Telemetry Restoration• Lost data / signals must be restored
– Calibration, Quality Checking & Testing– ICCP Links
• Data Quality (quality codes = Valid, Manual, Suspect, Invalid, Comm-Failure)
• Links must be available 98% each month (excluding planned outages)
• Server failover must be restored within 5 minutes
• Communications failover must be restored within 30 seconds
– ERCOT Requests for New Telemetry
– ERCOT Requests for Redundant Telemetry
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
15EDS 2 – Release 3July 2007
Page 15EDS 2 – Release 3 Scope
State Estimator Standard – TAC Approved for Nodal– State Estimator Performance Requirements
• State Estimator converges 97% of runs during a monthly test period.• Each month for transmission elements, causing 80% of congestion cost (latest year)
– the residual difference between State Estimator and Power Flow for critically monitored transmission element MW flows shall be less than 3% of the associated emergency rating on at least 95% of samples measured
– the MW telemetry value and the MW SE value shall be less than 3% of the associated element emergency rating on at least 95% of samples measured
• Each month for the 20 most voltage critical buses– telemetered bus voltage minus state estimator voltage shall be within the greater of 2%
or the accuracy of the telemetered voltage measurement involved for at least 95% of samples measured
• On all transmission elements greater than 100kV; the difference between state estimator MW solution and the SCADA measurement will be less than 10 MW or 10% of the associated emergency rating (whichever is greater) on 99.5% of all elements during a 30 day period.
– To meet these objectives ERCOT will:• Work with TSP to resolve problem in accordance with Telemetry Standard• Direct additional telemetry be installed on elements contributing most to 80% of congestion
costs for the latest year for which data is available• Alarm any sum of flow around a bus the greater of 5% of the largest line rating connected to
the bus or 5MW, and requesting that the applicable TSP or QSE correct the failure• Utilize quality codes sent by data provider in assigning confidence factors for data used in
SE• Post monthly results
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
16EDS 2 – Release 3July 2007
Page 16EDS 2 – Early Delivery Systems
Activity ERCOT MP
Develop and Test Procedures Restructure Load Model Verify and Tune State Estimator Verify Network Security Analysis Generate and Test Hourly Reports Generate and Post Telemetry and SE Performance Reports Review and Analyze Performance Reports Access Performance Reports via the MIS Portal Submit & Process Service Requests for Performance Issues
EDS 2 Release 3 – Key Activities
Timeline Context ActivitiesProtocols MetricsProceduresOrganization
17EDS 2 – Release 3July 2007
Page 17EDS 2 – Early Delivery Systems
EDS 2 Release 3 – Key Activities– Telemetry Verification
• Accumulate and calculate monthly and quarterly availability data• Generate reporting per Telemetry Standards
– Highlight and verify availability issues– Provide on MIS for market participants
• Develop ERCOT Operations Procedures to address and resolve issues
– State Estimator Verification • Topology build• Forecast bus load• Nodal SE solution and compares to Zonal• Accumulate and calculate monthly performance data• Generate reporting per SE Standards
– Highlight and verify data issues– Provide on MIS for market participants
• Develop ERCOT Operations Procedures to address and resolve issues
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
18EDS 2 – Release 3July 2007
Page 18EDS 2 – Early Delivery Systems
EDS 2 Release 3 – Key Activities– Topology Consistency Analyzer
• Identify and report on status errors
– Forced Outage Detection• Identify and report on unplanned outages• EDS 4 integrates with the outage scheduler
– Network Security Analysis• Verify dynamic ratings are correctly calculated• Verify overload notification• Verify constraints and contingency list• Verify Special Protection Schemes (SPS) / Remedial Action Plans (RAP):
– Triggering conditions are defined and can be executed– Post-SPS and post-RAP results are correct and can be reported
• Verify load rollover modeling• Verify transmission constraint management (calculate shift factors)• Develop Nodal NSA operating procedures• Benchmark results against Zonal real time operations
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
19EDS 2 – Release 3July 2007
Page 19EDS 2 – Early Delivery Systems
EDS 2 Release 3 – Key Activities
SCADA Telemetry
DynamicRatings
EDW MIS
NetworkSecurityAnalysis
StateEstimator
TopologyConsistency
Analyzer
TransmissionConstraint
Management
ForcedOutageDetector
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
20EDS 2 – Release 3July 2007
Page 20EDS 2 – Release 3 Scope
Enterprise Data Warehouse Reports– Telemetry Performance Reports
• Electrical Buses Not Meeting Telemetry Accuracy Requirements
– SE Performance Reports• MW Residuals SE Vs Telemetry for Congested Transmission Element
• SE Convergence Rate
• Voltage Residuals SE Vs Telemetry for Critical Buses
• MW Residuals SE Vs Telemetry for Major Transmission Elements
• MW Residuals SE Vs RTCA Base case for Congested Transmission Element
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
21EDS 2 – Release 3July 2007
Page 21EDS 2 – Release 3 Scope
Nodal Procedures
Organization Area Existing New Total
Operations Support SCADA 3 1 4
SE 3 4 7
NSA 1 1 2
EMMS Production SCADA 1 2 3
Operations SCADA 1 14 15
SE 3 3 6
NSA 6 10 16
TOTAL 18 35 53
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
22EDS 2 – Release 3July 2007
Page 22EDS 2 – Release 3 Scope
Nodal Procedures– Operations Support
• SCADA– SCADA Tagging Procedures– SCADA Manual Replacement Maintenance – SCADA Calculation and Maintenance – Telemetry and State Estimator Performance Monitoring and Reporting
• State Estimator– Real Time corrections to meet SE/Telemetry and LMP standards (through SE and Topology
Consistency Analyzer results)– New Metering Proposal– Handling of SCADA/SE non-compliance issues– State Estimator Load Modeling Maintenance– SE Procedure - Data Model Issues– State Estimator measurement weights maintenance and Tuning – Unit Reactive Curve Update and Maintenance Procedure
• Network Security Analysis– Contingency Definition and Maintenance Procedure– Manual Constraint Definition and Maintenance
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
23EDS 2 – Release 3July 2007
Page 23EDS 2 – Release 3 Scope
Nodal Procedures– Production Support
• SCADA– New ICCP points verification procedure– Site Failover – Alarm Processor Maintenance Procedure
– Operations• SCADA
– Respond to Overloaded Equipment Alarm– Respond to SPS Proximity Alarm– Respond to Under or Over Voltage condition Alarm– Approval to Energize– Respond to Incorrect Telemetry Alarm– Respond to Communication Link Failures– Send Base Points to QSE– Store an Operator Entered Value in the Real-Time Database– Display Summary Displays– Establish Communication on Communication Link Failover– Establish Communication on Failed Link Recovery– Establish ICCP Communications– Establish Communications on ERCOT Site Failover– Add a Real-Time Database Point On-Line– Process stored value
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
24EDS 2 – Release 3July 2007
Page 24EDS 2 – Release 3 Scope
Nodal Procedures– Operations
• State Estimator– Process Topology– Identify Bad Measurements– Resolve unavailable SE Solution– Build Real-Time Power Flow Cases– Build Off-Line Power Flow Cases– Respond to Poor SE Results, including cases of Large Residuals
• Network Security Analysis– Resolve Real-Time Overload Violations– Analyze Look Ahead Security and Stability– Resolve Actual Voltage Limit Violation– Resolve Contingency Voltage Limit Violation– Respond to Unresolved Contingency– Respond to Cascading Contingency– Manage VSS Savecases– Establish RTCA Base Case– Process Security Violations– Establish VSS Base Case– Respond to VSS Failure– Respond to RTCA Failure– Study VSA– Study TSA– Study CA– Establish Plans to Alleviate Voltage Violations
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
25EDS 2 – Release 3July 2007
Page 25EDS 2 – Data Issue Resolution Process
Data Issue Resolution Process
Mar
ket
Par
tici
pan
tsO
per
atio
ns
Mo
del
ing
EM
MS
Pro
d
ICC
PA
dv
Net
Ap
ps Telemetry
and SE Performance
ICCP Data Research
Network Model Data Research
Determine Priority and
Assign
Internal review to determine items to send
to MP
SE Spreadsheet
Pending
SE Spreadsheet
To Implement
Create Service Request
Implement
Implement
SE Spreadsheet
Closed
Determine Resolution
Conference Call
Verify Implemented
Items
SE Spreadsheet
Assigned
Create Service Request
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
26EDS 2 – Release 3July 2007
Page 26EDS 2 – Release 3 Metrics Reporting
ID Metric Target Completion
MP6 QSE and TSP Telemetry / ICCP availability EDS 2 Release 3 + 14 days
MP14 MP EDS 2 Trials Participation Start of EDS 2 Release 4 + 14 days
E1 ERCOT Staff Completed Training Go Live Activities less 14 days
E3Validate Telemetry / SE EDW is accessible via MIS
EDS 2 Release 3 complete
E9 Develop Texas Nodal Procedures Go-Live less 60 days
EM01 Network Security Analysis EDS 2 Release 3 complete + 60 days
EM09 Validate Zonal and Nodal Common Constraints SCED Testing EDS Trial
N3 Validate SE Performance and Accuracy EDS 2 Release 3 complete
C3 Contingency Plan for ICCP Data Failure Go Live Activities less 60 days
C6 Develop Plan for SE Failure Go Live Activities less 60 days
Metrics
Timeline Context MetricsProceduresOrganization ActivitiesProtocols
27EDS 2 – Release 3July 2007
Page 27EDS 2 – Release 3
Next Steps– Schedule WebEx to review EDW reports in detail– Schedule additional WebEx conferences as needed– Complete Nodal Procedures for EDS 2 Release 3– Begin planning for EDS 2 Release 4
Questions…