Parallel Flow Visualization Data Requirements Parallel Flow Visualization Data Requirements NERC ORS Meeting Toronto, Ontario September 23-24, 2009 Jim

Parallel Flow Parallel Flow VisualizationVisualization

— Data Requirements —— Data Requirements —

NERC ORS MeetingNERC ORS MeetingToronto, OntarioToronto, Ontario

September 23-24, 2009September 23-24, 2009

Jim Busbin

Chairman, IDC Working Group


Presentation Topics —Presentation Topics —

PurposePurpose

BackgroundBackground

Data RequirementsData Requirements

Data ArchiveData Archive

IDC Change Order 283, Revision 2IDC Change Order 283, Revision 2


PurposePurpose

Parallel Flow VisualizationParallel Flow VisualizationPurposePurpose

The Purpose Statement from the Parallel Flow The Purpose Statement from the Parallel Flow Visualization SAR states:Visualization SAR states:

The requested enhancements to the TLR The requested enhancements to the TLR procedure in the Eastern Interconnection will procedure in the Eastern Interconnection will improve the wide-area view of Reliability improve the wide-area view of Reliability Coordinators (RCs) such that they better Coordinators (RCs) such that they better understand the current operating state of the understand the current operating state of the bulk electric system and will result in the bulk electric system and will result in the assignment of relief obligations during periods assignment of relief obligations during periods of congestion that are more representative of of congestion that are more representative of those actually contributing to the congestion. those actually contributing to the congestion.


BackgroundBackground

Parallel Flow VisualizationParallel Flow VisualizationBackgroundBackground

May 6 NERC ORS Meeting in Indianapolis, IN. May 6 NERC ORS Meeting in Indianapolis, IN.

IDCWG was directed to:IDCWG was directed to:

Identify the minimum data set required to achieve the required Identify the minimum data set required to achieve the required calculations by the calculations by the September 2009 ORS meetingSeptember 2009 ORS meeting

Identify the required changes to the IDC to identify the GTL Identify the required changes to the IDC to identify the GTL impactsimpacts

Recommend a vendor to perform the GTL calculations for all EI Recommend a vendor to perform the GTL calculations for all EI RCsRCs

Determine, in cooperation with the vendor, the GTL calculation Determine, in cooperation with the vendor, the GTL calculation methodologymethodology

Identify to the ORS any additional items that are required to Identify to the ORS any additional items that are required to incorporate GTL incorporate GTL impactsimpacts

The IDCWG should target having proposed recommendations to the The IDCWG should target having proposed recommendations to the ORS for the ORS for the November 2009 meeting November 2009 meeting

Parallel Flow VisualizationParallel Flow VisualizationBackgroundBackground

IDCWG has discussed and identified requirements to IDCWG has discussed and identified requirements to support Parallel Flow Visualization – we continue to support Parallel Flow Visualization – we continue to evaluate these requirementsevaluate these requirements

June 3-4 IDCWG Meeting:June 3-4 IDCWG Meeting:Discussed charge given by ORSDiscussed charge given by ORS

Initiated identification of requirementsInitiated identification of requirements

July 8-9 IDCWG Meeting:July 8-9 IDCWG Meeting:Meeting held to discuss Parallel Flow VisualizationMeeting held to discuss Parallel Flow Visualization

Identification of requirements continuedIdentification of requirements continued

August 18-19 IDCWG MeetingAugust 18-19 IDCWG MeetingOATI asked to revise Change Order 283 to include OATI asked to revise Change Order 283 to include

requirements identified in July requirements identified in July meeting – this modification will meeting – this modification will become Revision 2become Revision 2


Data Data RequirementsRequirements


Data Requirements — Introductory NotesData Requirements — Introductory NotesReference: “Generation-to-Load Reporting Reference: “Generation-to-Load Reporting Requirements” whitepaper, January 2, 2009Requirements” whitepaper, January 2, 2009

Generation-to-load flows will be calculated by one Generation-to-load flows will be calculated by one vendor. Raw data used in the calculation will be vendor. Raw data used in the calculation will be submitted to the vendor submitted to the vendor

Frequency of all data submission will be every fifteen Frequency of all data submission will be every fifteen minutes unless otherwise noted by (♣). minutes unless otherwise noted by (♣).

Data will be submitted to reflect current-hour Data will be submitted to reflect current-hour conditions and a projection of peak next hour conditions and a projection of peak next hour conditions. To be clear, each data submission will conditions. To be clear, each data submission will contain data for the present hour and also for the next contain data for the present hour and also for the next hour hour


Data Requirements — CategoriesData Requirements — Categories

Load and LossesLoad and Losses• Real Time Load Magnitude and DistributionReal Time Load Magnitude and Distribution

Generation OutputGeneration Output• Real-Time Output vs. Static ValuesReal-Time Output vs. Static Values

Flowgate FlowsFlowgate Flows• Provides Error Checking CapabilityProvides Error Checking Capability

Topology UpdatesTopology Updates• Provides More Frequent Update of Topology Provides More Frequent Update of Topology

and and

Additional DataAdditional Data


Data RequirementsData RequirementsLoad and Losses —Load and Losses —

Total Real-Time BA LoadTotal Real-Time BA Load• Geographic ZonesGeographic Zones• Conforming / Non-Conforming ZonesConforming / Non-Conforming Zones• Individual Bus Loads Individual Bus Loads • andand Total for BA Total for BA

Real-Time Losses for Total BAReal-Time Losses for Total BA

Projection of Next Hour Total Peak BA LoadProjection of Next Hour Total Peak BA Load• Geographic ZonesGeographic Zones• Conforming / Non-Conforming ZonesConforming / Non-Conforming Zones• Individual Bus LoadsIndividual Bus Loads• andand Total for BA Total for BA

Projection of Next Hour Losses for Total BAProjection of Next Hour Losses for Total BA


Data RequirementsData RequirementsGeneration Output —Generation Output —

Real-Time Generation OutputReal-Time Generation Output• Output for Each Generating Unit Shown in ModelOutput for Each Generating Unit Shown in Model• Net of Auxiliary Equipment / As ModeledNet of Auxiliary Equipment / As Modeled

Total Real-Time Generation Output for BATotal Real-Time Generation Output for BA

Projected Next Hour Generation OutputProjected Next Hour Generation Output• Output for Each Generating Unit Shown in ModelOutput for Each Generating Unit Shown in Model• Projected Maximum Output of Unit in Next HourProjected Maximum Output of Unit in Next Hour• Net of Auxiliary Equipment / As ModeledNet of Auxiliary Equipment / As Modeled

Total Projected Next-Hour Generation Output for Total Projected Next-Hour Generation Output for BABA

Generating Unit Real-Time Upper and Lower Generating Unit Real-Time Upper and Lower Normal LimitsNormal Limits

Joint Ownership Identification ♣Joint Ownership Identification ♣


Data RequirementsData RequirementsFlowgate Flows —Flowgate Flows —

Actual real-time flow on each active flowgate Actual real-time flow on each active flowgate monitored element shown in the Book of Flowgatesmonitored element shown in the Book of Flowgates

Projection of next hour maximum flow on each active Projection of next hour maximum flow on each active flowgate monitored element shown in the Book of flowgate monitored element shown in the Book of Flowgates Projection of Next Hour Losses for Total Flowgates Projection of Next Hour Losses for Total BABA

Actual real-time flow on each active flowgate Actual real-time flow on each active flowgate contingency element shown in the Book of Flowgatescontingency element shown in the Book of Flowgates

Projection of next hour maximum flow on each active Projection of next hour maximum flow on each active flowgate contingency element shown in the Book of flowgate contingency element shown in the Book of FlowgatesFlowgates

Un-accounted for usage will be identified and Un-accounted for usage will be identified and calculated as the difference between real time flows calculated as the difference between real time flows and the summation of calculated tag impacts, market and the summation of calculated tag impacts, market flows and generation-to-load flowsflows and generation-to-load flows


Data RequirementsData RequirementsTopology Updates —Topology Updates —

Increase frequency of IDC update from SDX and Increase frequency of IDC update from SDX and matrix calculation to every fifteen minutes matrix calculation to every fifteen minutes

Outage updates submitted to SDX every fifteen Outage updates submitted to SDX every fifteen minutes minutes


Data RequirementsData RequirementsAdditional Data —Additional Data —

Control Device Data – Scheduled and Actual Control Device Data – Scheduled and Actual Flows, Real-Time and Projected Next Hour:Flows, Real-Time and Projected Next Hour: Phase shifting transformersPhase shifting transformers DC linesDC lines Variable frequency transformersVariable frequency transformers

Dynamic Schedules – Actual and projected next-Dynamic Schedules – Actual and projected next-hour flows hour flows

Identification of pumped storage hydro units ♣Identification of pumped storage hydro units ♣


Data RequirementsData RequirementsAdditional Data —Additional Data —

(NAESB / United States) – Designated Network (NAESB / United States) – Designated Network Resource (DNR) generating units/plantsResource (DNR) generating units/plants

(NAESB / United States) – DNR capacity(NAESB / United States) – DNR capacity

(NAESB) Assignment of priorities for generation-(NAESB) Assignment of priorities for generation-to-load (7-F versus 6-NN)to-load (7-F versus 6-NN)

Net scheduled interchangeNet scheduled interchange

Net actual interchangeNet actual interchange

Individual actual tie-line flowsIndividual actual tie-line flows





Impact archive will be added that savesImpact archive will be added that saves• Tag impactsTag impacts• Market flowsMarket flows• Generation to load flowsGeneration to load flows• Un-accounted for usageUn-accounted for usage• Real-time flows by flowgateReal-time flows by flowgate

Archive to run around the clock – not just when a Archive to run around the clock – not just when a flowgate is in TLRflowgate is in TLR

Suggest current calendar year’s and previous Suggest current calendar year’s and previous year’s data be available on lineyear’s data be available on line

Suggest previous three year’s data be available Suggest previous three year’s data be available off-lineoff-line


IDC Change Order 283,IDC Change Order 283,

Revision 2Revision 2


Documents

Parallel Flow Visualization Data Requirements Parallel Flow Visualization Data Requirements NERC ORS Meeting Toronto, Ontario September 23-24, 2009 Jim