Parallel Flow Visualization
— Data Requirements —
Jim Busbin
Chairman, IDC Working Group
NERC ORS Meeting
Toronto, Ontario
September 23-24, 2009
Parallel Flow Visualization
Presentation Topics —
Purpose
Background
Data Requirements
Data Archive
IDC Change Order 283, Revision 2
Parallel Flow Visualization
Purpose
Parallel Flow Visualization
Purpose
The Purpose Statement from the Parallel Flow
Visualization SAR states:
The requested enhancements to the TLR procedure in the Eastern
Interconnection will improve the wide-area view of Reliability
Coordinators (RCs) such that they better understand the current
operating state of the bulk electric system and will result in the
assignment of relief obligations during periods of congestion that are
more representative of those actually contributing to the congestion.
Parallel Flow Visualization
Background
Parallel Flow Visualization
Background
May 6 NERC ORS Meeting in Indianapolis, IN.
IDCWG was directed to:
Identify the minimum data set required to achieve the required calculations by the
September 2009 ORS meeting
Identify the required changes to the IDC to identify the GTL impacts
Recommend a vendor to perform the GTL calculations for all EI RCs
Determine, in cooperation with the vendor, the GTL calculation methodology
Identify to the ORS any additional items that are required to incorporate GTL
impacts
The IDCWG should target having proposed recommendations to the ORS for the
November 2009 meeting
Parallel Flow Visualization
Background
IDCWG has discussed and identified requirements to support Parallel
Flow Visualization – we continue to evaluate these requirements
June 3-4 IDCWG Meeting:
Discussed charge given by ORS
Initiated identification of requirements
July 8-9 IDCWG Meeting:
Meeting held to discuss Parallel Flow Visualization
Identification of requirements continued
August 18-19 IDCWG Meeting
OATI asked to revise Change Order 283 to include requirements identified in July
meeting – this modification will become Revision 2
Parallel Flow Visualization
Data Requirements
Parallel Flow Visualization
Data Requirements — Introductory Notes
Reference: “Generation-to-Load Reporting Requirements”
whitepaper, January 2, 2009
Generation-to-load flows will be calculated by one vendor. Raw
data used in the calculation will be submitted to the vendor
Frequency of all data submission will be every fifteen minutes
unless otherwise noted (♣).
Data will be submitted to reflect current-hour conditions and a
projection of peak next hour conditions. To be clear, each data
submission will contain data for the present hour and also for
the next hour
Parallel Flow Visualization
Data Requirements — Categories
Load and Losses
• Real Time Load Magnitude and Distribution
Generation Output
• Real-Time Output vs. Static Values
Flowgate Flows
• Provides Error Checking Capability
Topology Updates
• Provides More Frequent Update of Topology and
Additional Data
Parallel Flow Visualization
Data Requirements
Load and Losses —
Total Real-Time BA Load
• Geographic Zones
• Conforming / Non-Conforming Zones
• Individual Bus Loads
• and Total for BA
Real-Time Losses for Total BA
Projection of Next Hour Total Peak BA Load
• Geographic Zones
• Conforming / Non-Conforming Zones
• Individual Bus Loads
• and Total for BA
Projection of Next Hour Losses for Total BA
Parallel Flow Visualization
Data Requirements
Generation Output —
Real-Time Generation Output
• Output for Each Generating Unit Shown in Model
• Net of Auxiliary Equipment / As Modeled
Total Real-Time Generation Output for BA
Projected Next Hour Generation Output
• Output for Each Generating Unit Shown in Model
• Projected Maximum Output of Unit in Next Hour
• Net of Auxiliary Equipment / As Modeled
Total Projected Next-Hour Generation Output for BA
Generating Unit Real-Time Upper and Lower Normal Limits
Joint Ownership Identification ♣
Parallel Flow Visualization
Data Requirements
Flowgate Flows —
Actual real-time flow on each active flowgate monitored element
shown in the Book of Flowgates
Projection of next hour maximum flow on each active flowgate
monitored element shown in the Book of Flowgates Projection
of Next Hour Losses for Total BA
Actual real-time flow on each active flowgate contingency
element shown in the Book of Flowgates
Projection of next hour maximum flow on each active flowgate
contingency element shown in the Book of Flowgates
Un-accounted for usage will be identified and calculated as the
difference between real time flows and the summation of
calculated tag impacts, market flows and generation-to-load
flows
Parallel Flow Visualization
Data Requirements
Topology Updates —
Increase frequency of IDC update from SDX and matrix
calculation to every fifteen minutes
Outage updates submitted to SDX every fifteen minutes
Parallel Flow Visualization
Data Requirements
Additional Data —
Control Device Data – Scheduled and Actual Flows, Real-Time
and Projected Next Hour:
Phase shifting transformers
DC lines
Variable frequency transformers
Dynamic Schedules – Actual and projected next-hour flows
Identification of pumped storage hydro units ♣
Parallel Flow Visualization
Data Requirements
Additional Data —
(NAESB / United States) – Designated Network Resource
(DNR) generating units/plants
(NAESB / United States) – DNR capacity
(NAESB) Assignment of priorities for generation-to-load (7-F
versus 6-NN)
Net scheduled interchange
Net actual interchange
Parallel Flow Visualization
Data Archive
Parallel Flow Visualization
Data Archive
Impact archive will be added that saves
• Tag impacts
• Market flows
• Generation to load flows
• Un-accounted for usage
• Real-time flows by flowgate
Archive to run around the clock – not just when a flowgate is in
TLR
Suggest current calendar year’s and previous year’s data be
available on line
Suggest previous three year’s data be available off-line
Parallel Flow Visualization
… so far?
Parallel Flow Visualization
IDC Change Order 283,
Revision 2