130 likes | 254 Views
Integration of Demand Resources within ISO/RTO Operations. November 20, 2008 Peter Friedland Operations Solutions Manager. Agenda. Project Status Development of DR Integration Business Requirements (Dec 31 st )
E N D
Integration of Demand Resources within ISO/RTO Operations November 20, 2008 Peter Friedland Operations Solutions Manager
Agenda • Project Status • Development of DR Integration Business Requirements (Dec 31st) • Develop Software Functional Requirements/Specifications for RT Dispatch Functions • Develop Software Functional Requirements/Specifications for Asset Registration and Settlements functions • Continue October 23, 2008 Discussion • Communication Circuits • DR Model Synchronization
Project Status • ISO Project Team is busy drafting updated Business Requirements for Dec 31st • Project On-track for November 2008 Approval • SOW with external software vendor is in progress with work expected to begin in January 2009 • ISO-NE Real-Time Dispatch Software Development activities will start in November 2008 • Software Functional Requirements will start in November 2008 – concurrent with Business Requirements • Settlements and Asset Registration Software Development activities TBD
High-Level Software Development Activities • ISO-NE responsibilities include: • All DNP3 communication-related software including DDE model synchronization • EMS User Interfaces and Dispatch Interfaces to Settlements • Customer Asset Management (CAMS) Enhancements • Settlements System • Outside Vendor responsibilities include: • DR Model Management including monthly model update capabilities within the EMS • Various Real-Time Dispatch functions including security-constrained study tools • Various real-time prediction tools • Training/Testing simulator enhancements • Software interfaces to ISO Systems
Q4 2008-Q2 2009 ISO/DDE Activities • Review of Asset Registration through DDE Model Synchronization Business Requirements – 1/31/2009 • Communication Software Functional Requirements - 2/28/2009 • DR RTU Specification, similar to existing RIG Replacement RTU Specification – 3/31/2009 • Software RTU Reference Implementation – 4/30/2009 • Coordinated Testing and refinement of RTU Reference Implementation – Q2 through Q3 2009
Integration of DR within SCADA – Logical View RTU connections are initiated from ISO; no inbound connections allowed to CFE Once a connection is established to RTU, ISO efficiently polls the RTU for changes; no unsolicited data is allowed from the RTU ISO pushes dispatch instructions to the RTU in the form of Analog and Binary Outputs
Frame Relay Circuit Cost and Availability • Within continental US, 56K circuit costs about $200/month or $400/month for two circuits – Update: Request for Quotes for about ½ of the DDE’s have been received. It is expected that DDE’s will have the required Router and Frame Relay circuits no later than 11/1/2009 for testing. • Atlanta, Bethlehem (PA), Boston, Buffalo, Dallas, Middletown (CT) • $431/month • Installation time approximately 1 month
Frame Relay Circuit Cost and Availability • ISO-NE telecommunication vendor is currently establishing availability and quotes for Frame Relay outside of continental US – Update: Quotes have been received and will need to be discussed with affected DDE’s outside of this meeting • Monthly charges are higher • Single frame relay • Single Canada private line
DR Model Synchronization and Testing • DR Resource/Assets can change on a monthly basis • ISO-NE and DDE’s will establish an efficient means for exchanging DR ‘meta-data’ for the purpose of regular RTU configuration and testing prior to the start of each month • ‘Meta-Data’ will consist of information needed to establish identity and other attributes of Resource and Assets • ‘Meta-Data’ will consist of information needed to establish mapping between the Resource/Assets and DNP objects within the RTU Master and Slave • ‘Meta-Data’ will be automatically be generated by ISO-NE DR Model Management System based upon information derived from CAMS • DR ‘Meta-Data’ will also include test data to automatically test the integrity of the new model within the RTU Master and Slave