Integration of Demand Resources within ISORTO Operations

1
Integration of Demand Resources within ISO/RTO
Operations

• September 25, 2008
• Peter Friedland
• Manager EMS Market Systems

2
Agenda

• Project Status
• Development of new business requirements (Nov
  1st)
• Develop a plan for Implementation of Real-Time DR
  Dispatch functions
• Develop a plan for Implementation of Settlements
  functions
• Continue August 28, 2008 Discussion
• Architecture
• Real-time Dispatch Semantics

3
Project Status

• ISO Project Team is busy drafting updated
  Business Requirements for Nov 1st
• Project Approval is expected in November
• Functional Requirements will start in October
  concurrent with Business Requirements
• Real-Time Dispatch Development activities will
  start in November
• Settlements Development activities TBD

4
Real-Time Dispatch Timeline
5
Integration of DR Assets within SCADA
6
Architecture Questions/Answers

• Business Continuity
• Some DDEs may have large data center
  infrastructure, including a backup data centers
  outside of New England.  They may need a system
  that not only uses redundant lines, but can also
  handle redundant RTUs.  Redundant RTUs may not
  be a requirement for all DDEs.  Will DDEs have
  the capability to use RTUs that meet redundancy
  requirements?
• ISO-NE will work closely with DDEs to ensure
  that remote data center and RTU redundancy
  requirements can be achieved. The simplest
  approach will be to have the ISO CFE configured
  to connect to a prioritized connection list of
  DDE RTUs to attempt connection. Only one RTU
  will be connected at any given time. In this
  scenario, the DDE would manage the failover of
  the RTU from their primary location to the backup
  and the ISO CFE would follow.
• CFE Communication Front End

7
Architecture Questions/Answers

• Testing and Verification
• Testing in this type of environment can be very
  challenging and we need to make sure that there
  are clear and well defined testing and acceptance
  procedures in place when working with this
  system.
• Absolutely agree. The efficient design of the
  messaging , particularly for the RTU, will be
  crucial for efficient and accurate Real-Time
  dispatch. Another major challenge will be
  monthly model synchronization and checkout.
  Testing and Acceptance Procedures will play a
  vital role in assuring our systems function
  properly and for efficient use of staff.

8
Architecture Questions/Answers

• Communication Lines
• 3. Some DDEs may need to communicate asset
  updates through the RTU for thousands of assets.
  Will the 56k line be enough bandwidth?
• We will run tests to determine bandwidth
  adequacy. For larger DDEs with more assets it
  may become necessary to secure a larger pipe.
  Again, efficiency of messaging and report by
  exception (RBE) will reduce the need for a
  larger pipe in most instances. Also, asset
  metadata updates will not be sent through the
  RTU.
• 4. If dedicated lines are point-to-point and not
  part of a larger carrier network, then providers
  will incur significant costs to enable data
  centers that are geographically disparate.
• From discussions with our IT Management, the
  majority of the cost is associated with the lines
  between the telco central office and your
  facility. We will secure some quotes to confirm
  this.
• 5. In other parts of the country some DDEs have
  encountered program rules that required the RTU
  to be physically located in the ISOs service
  territory.  Is this the case with ISO-NE?
• No we will not discriminate based on the location
  of the data center

9
Architecture Questions/Answers

• RTU Implementation
• 6. Some DDEs may prefer to implement an RTU at
  the software level so that we can run it as a
  service on our platform.  Will this cause issues?
• In general, no. You should consider implementing
  a software solution on a clustered server to
  ensure the highest availability. On the other
  hand, RTUs are typically hardware devices with
  no moving parts. This type of device typically
  does not require redundancy but having a spare
  RTU configured and on the shelf is highly
  advisable. Some RTU solutions even come with
  redundant power supplies for even higher
  availability and fault tolerance.

10
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

11
Real-Time Dispatch Semantics

• Real-Time Dispatch Instructions (tentative
  design)
• Next day DR Hourly Dispatch Instructions for each
  Resource will be available at 2200hr the day
  before
• These hourly dispatch instructions will be
  distributed via file and/or web service (TBD)
• During the dispatch day, Dispatch Instructions
  will be issued once per minute via SCADA for all
  resources
• In general, these SCADA Dispatch Instructions
  will match the 2200hr hourly plan unless
  overridden by the System Operator
• Each set of DDE Dispatch Instructions will
  consist of an implementation time followed by a
  list of Resource/MW pairs organized by Load Zones
  (2010)

12
Real-Time Dispatch Semantics

• Real-Time Dispatch Instructions (contd)
• Starting in 2011, each set of DDE Dispatch
  Instructions will also include Resource/MW pairs
  organized by Dispatch Zones
• The System Operator may choose to lower Resource
  MW interruption values during the day
• The System Operator may chose to raise Resource
  MW interruption values during the day. This will
  require that ISO-NE be in O.P. 4 Actions Six or
  above
• There will be an O.P. 4 indicator sent to the DDE
  RTU once per minute

13
Real-Time Dispatch Semantics

• Real-Time Telemetering of Asset Data
• Asset data will be organized in the RTU as
  Asset/MW pairs
• Asset data will be updated in the RTU by the DDE
  at least every five minutes
• ISO will poll the RTU for changed data once per
  minute. Appropriate deadbands will be
  configured. This is typically referred to as
  Class Polling
• ISO will poll the RTU for all data once per hour.
  This is typically referred to as Integrity
  Polling