Upload
rolf-ramsey
View
213
Download
1
Embed Size (px)
Citation preview
EDS 2Early Delivery Systems
Review and Request for ApprovalMay 2007
John Webb
2EDS 2 – Approach and ScheduleMarch 2007
Page 2EDS 2 – Early Delivery Systems
Agenda– EDS 2
• Context Setting• Review
– Scope– Approach– System Requirements– Schedule
• Request for Approval
3EDS 2 – Approach and ScheduleMarch 2007
Page 3EDS 2 – Early Delivery Systems
EDS 2 – Context Setting– 3/22/2007 TPTF Meeting
• Presented EDS 2 Approach and submitted document for comment• No comments received
– 4/25/2007 TPTF Meeting• TPTF requested that EDS 2 Approach contain more detail• Additional detailed provided and the updated document was submitted for
comment
– 5/22/2007 TPTF Meeting• No comments received• Can provide overview of EDS 2 as a presentation• Request for approval
4EDS 2 – Approach and ScheduleMarch 2007
Page 4EDS 2 – Early Delivery Systems
EDS 2 – Scope of Transition Plan Tasks
Tasks Transition Plan Task Descriptions
5.4.1 (2a) Verify all data and telemetry submittals meet Protocol 3.10 (NOMCR)
5.4.1 (2b) Verify accuracy of all transmission element constraints
5.4.1 (2c) Verify TSP calculations for transmission constraints likely to be binding in SCED
5.4.2 (1) Verify SE performance meets Protocol 3.10.9
5.4.2 (2) Verify trial of SE test based on live SCADA, resolving errors to meet performance criteria, and to verify bus load forecast functionality
5.4.2 (4) Begin continuous operation of SCADA and post information to TSPs and QSEs meeting Protocol 6.3.2
5.4.3 (1) Begin NSA verification, testing major transmission elements
5.4.3 (2) Compare NSA to Zonal and add contingencies and screening
5.4.3 (3) Continuously monitor Mon-Fri meeting Protocol 6.5.7.1.11
5EDS 2 – Approach and ScheduleMarch 2007
Page 5EDS 2 – Early Delivery Systems
EDS 2 – Approach– Release 3
• Verify Telemetry and SE performance
• Provide performance reports to TSPs and QSEs
• Verify Network Security Analysis (NSA)
• Develop Maintenance Procedures
– Release 4• Verify Network Model Management System (NMMS)
• Verify Network Operations Model Change Request (NOMCR)
• Develop Network Model Maintenance Procedures
6EDS 2 – Approach and ScheduleMarch 2007
Page 6EDS 2 – Early Delivery Systems
EDS 2 Release 3 - Approach– 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
7EDS 2 – Approach and ScheduleMarch 2007
Page 7EDS 2 – Early Delivery Systems
EDS 2 Release 3 - Approach– Topology Consistency Analyzer
• Identify and report on status errors
– Forced Outage Detection• Identify and report on unplanned outages• EDS 3 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
8EDS 2 – Approach and ScheduleMarch 2007
Page 8EDS 2 – Early Delivery Systems
EDS 2 Release 3 - Approach
SCADA Telemetry
DynamicRatings
EDW MIS
NetworkSecurityAnalysis
StateEstimator
TopologyConsistency
Analyzer
TransmissionConstraint
Management
ForcedOutageDetector
9EDS 2 – Approach and ScheduleMarch 2007
Page 9EDS 2 – Early Delivery Systems
EDS 2 Release 3 - Systems– Release 3 configuration
• Early releases of software packages
– EMS 2.3 (COTS+ - Commercial off the Shelf with customizations)
» Telemetry Performance Tool
» SE Functionality
» SE Performance Tool
» NSA Functionality
– Enterprise Data Warehouse
» Reporting on SE and Telemetry performance by QSE and TSP
– MIS Portal
» Providing QSE and TSP access to performance reports
» Providing QSE and TSP access to hourly status reports
<< See the next slide for the desired configuration >>
10EDS 2 – Approach and ScheduleMarch 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
NodalTelemetry
EMS 2.2 to2.3
converter
Reportexceptions
NSA
SESCADA
Telemetry
Performance
SE
Customs
Zonal Nodal
Nodal – EMS (COTS+)
Reporting
EDWRTC
Archive
MIS
EMS 2.3
DNP
RTUMap
ZonalTelemetry
Zonal - EMS
TSP
QSE
TSP
QSE Nodal
QSE
Zonal
ICCP 2.3
ICCPMap TSP
11EDS 2 – Approach and ScheduleMarch 2007
Page 11EDS 2 – Early Delivery Systems
EDS 2 Release 4 - Approach– Network Model Management System (NMMS):
• Network model, ICCP database and with ownership / operatorship information
• Nodal Network Model is under change control
– Network Operations Model Change Request (NOMCR)• TSPs and QSEs electronically submit model changes and receive
acknowledgement
• Network model has been correctly updated
• TSP and QSE updates are confirmed
• TSPs may export network model for review
– Single Entry Model– Network Model Export
12EDS 2 – Approach and ScheduleMarch 2007
Page 12EDS 2 – Early Delivery Systems
EDS 2 Release 4 - Systems– Release 4 configuration
• Early releases of software packages
– Network Model Management System (NMMS)
» Database for network model, ICCP mapping, Ownership/Operatorship
– EMS 2.3 (COTS+)
» Integration with NMMS
<< See the next slide for the desired configuration >>
13EDS 2 – Approach and ScheduleMarch 2007
Page 13EDS 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
NodalTelemetry
Refresh /Convert
Reportexceptions
NSA
SESCADA
Telemetry
Performance
SE
Customs
Zonal Nodal
Nodal – EMS (COTS+)
Reporting
EDWRTC
Archive
MIS
EMS 2.3
Network Model Interface
DNP
RTUMap
ZonalTelemetry
QSE
Zonal - EMS
TSP
QSE
MIS
TSP
Nodal
TSP
QSE
ICCP 2.3
ICCPMap TSP
Zonal
14EDS 2 – Approach and ScheduleMarch 2007
Page 14EDS 1 and 2 – Early Delivery Systems
EDS 2 Schedule
2007
Initiation/Planning
Load Modeling
Feb Mar Apr May Jun Jul Aug Sep OctJan Nov
Release 3 – SE/Telemetry/NSA
Dec Jan Feb
Release 4 – NMMS/EMS Integration
Monitoring and Control
2008
15EDS 2 – Approach and ScheduleMarch 2007
Page 15EDS 2 – Early Delivery Systems
EDS 2 Approach Questions?
16EDS 2 – Approach and ScheduleMarch 2007
Page 16EDS 2 – Early Delivery Systems
Request for Approval