nerc related files dl/idcwg_aug 24...%pdf-1.6 %âãÏÓ 8969 0 obj >stream hÞÄykoÛf...

116-390 Village Blvd. Princeton, NJ 08540

609.452.8060 | www.nerc.com

Agenda Interchange Distribution Calculator Working Group

August 24, 2011 | 8 a.m.–5 p.m. August 25, 2011 | 8 a.m.–5 p.m. IESO Clarkson Facility 2635 Lakeshore Road W Mississauga, Ontario Conference – 1‐866‐740‐1260, Pass code 5247004

1. Administrative Matters

a. Arrangements – Larry Kezele

b. Notice of Public Meeting – Larry Kezele

“Participants are reminded that this meeting is public. Notice of the meeting was posted on the NERC website and widely distributed. Participants should keep in mind that the audience may include members of the press and representatives of various governmental authorities, in addition to the expected participation by industry stakeholders.”

c. Welcome and Introductions – Chair Bahbaz

d. Announcement of Quorum – Larry Kezele

e. NERC Antitrust Compliance Guidelines* – Larry Kezele

f. Parliamentary Procedures* – Larry Kezele

g. Approve Agenda – Chair Bahbaz

Closed sessions will be conducted as required. The August 24–25, 2011 IDCWG meeting agenda in Word format is included in the IDC Change Order zip file.

h. Future Meetings and Conference Calls – Chair Bahbaz

i. October 11–12, 2011 (8 a.m. – 5 p.m. both days), in Minneapolis, MN (hosted by OATI)

Interchange Distribution Calculator Working Group Meeting Agenda August 24–25, 2011

2

i. Approval of the IDCWG Meeting Minutes* – Chair Bahbaz

Attachment 1.i.1 – May 11–12, 2011 IDCWG Meeting Minutes

Attachment 1.i.2 – June 2, 2011 IDCWG Conference Call Meeting Minutes

Attachment 1.i.3 – June 23, 2011 IDCWG Conference Call Meeting Minutes

Attachment 1.i.4 – July 18, 2011 IDCWG Conference Call Meeting Minutes

j. NERC feedback from Reliability Coordinator Working Group (RCWG) and Operating Reliability Subcommittee (ORS) – Larry Kezele

i. The RCWG has not met since the last IDCWG meeting. The Operating Committee approved merging the RCWG into the ORS at its June 2011 meeting.

ii. The ORS has not met since the last IDCWG meeting.

k. North American Electric Reliability Corporation/North American Energy Standards Board (NERC/NAESB) coordination update

i. Business Practices Subcommittee – Ed Skiba or Narinder Saini

l. Review IDCWG roster and List Servers* – Larry Kezele

Attachment 1.l.1 – IDCWG Roster

Attachment 1.l.2 – IDC List Server

Attachment 1.l.3 – IDC_Plus List Server

Attachment 1.l.4 – DFTFFG List Server

m. Review of membership of the IDC self‐directed work teams – Chair Bahbaz Project Management Yasser Bahbaz (Team Lead), Allan Watson, Larry Kezele,

Brian Nolan

Market Flow Yasser Bahbaz (Team Lead), LaChelle Brooks, Raja Thappetaobula, Allan Watson, David Mahlmann, Larry Kezele

Documentation Ben Taylor (Team Lead), Cheryl Mendrala, LaChelle Brooks, Allan Watson, Larry Kezele

2. Review of Active Interchange Distribution Calculator (IDC) Change Orders (CO)

(Secretary’s Note: The IDC Change Orders for discussion at this meeting are posted in a zip file on the IDCWG Web site.)

a. CO‐283: Generator‐to‐Load Reporting Requirement (Status — Accepted as implemented on November 1, 2010)

Action:

i. Review outstanding variances and other areas of development


3

ii. Field trial would not start until the permanent solution is determined and implemented in IDC production

iii. Status of data transmittals

iv. Reliability Coordinator Permissions to address GTL Data Confidentiality

v. Coordination with NAESB BPS (Open Action Items)

Explanation of Implementation of IDC CO‐283 – What does CO‐283 accomplish today, once full sets of data are provided under the Parallel Flow Visualization Interim Solution, and what it may or may not accomplish under a permanent solution.

How will the data be integrated to show how curtailments would be assigned in the production/test systems?

b. CO‐315: Circuit B3M (ONT‐ITC) Phase Shifter Modeling Changes (Status — NYISO, MISO, PJM, and IESO are reviewing CO‐315)

Action: On hold.

c. CO‐316: Send a Target Market Flow not Equal to 9999 to External Market Entities of Flowgates (Status — Congestion Management Working Group to review need to proceed with the development and deployment of CO‐316.) Action: On hold.

d. CO‐317: Michigan – Ontario PAR Status Change Switch (Status — Approved for development, contingent upon resolution of a contractual agreement regarding funding between NERC and MISO) Action: NERC and MISO have not yet finalized a contractual agreement regarding funding.

e. CO‐320: Set PGEN for Base Loaded Units to Effective Pmax for NNL (Status — Approved for development) Action: Review development status and accept as implemented.

f. CO‐321: Data Interface for TLR CMR Report Data for SPP (Status —SPP and NERC have approved for development) Action: Review development status.

g. CO‐322: Generation Priority Submission (Status —Evaluatied) Action: Review evaluation and approve for development.

h. CO‐323: MISO Request to Access IDC Data for webImpact (Status — Approved for development) Action: NERC has signed CO‐323. Review status of development.

i. CO‐325: Changes to TLR Event History Display (Status — Approved for development) Action: Review status of testing and accept as implemented.


4

j. CO‐326: Parallel Flow Visualization Metrics (Status — Review draft) Action: Approve for evaluation.

k. CO‐328: Intra‐Hour Tag Curtailments (Status — Approved for development) Action: Prioritize development.

l. CO‐329: Load Adjustment During TLR 5 Issuance (Status — Approved for development) Action: Prioritize development.

m. CO‐330: Authorization of OATI Use of IDC Data for DOE Studies (Status — Evaluated) Action: Approve for development.

n. CO‐331: IDC Interface to NAESB webRegistry (Status — Evaluated) Action: Approve for development.

3. Review of Active webSDX (SDX) Change Orders (CO) (Secretary’s Note: The webSDX Change Orders for discussion at this meeting are posted in a zip file on the IDCWG Web site.)

a. CO‐08: Remaining GUI Changes (Status —Evaluated, at its January 2011 meeting MISO, PJM and VACAR‐S asked to review and comment on evaluation) Action: Review evaluation and approve for development.

b. CO‐09: Addition of Derate Validation to webSDX (Status —Approved for evaluation) Action: Review evaluation and approve for development.

4. Review of Active webFactor (Factor Viewer) Change Orders (CO) (Secretary’s Note: The Factor Viewer Change Orders for discussion at this meeting are posted in a zip file on the IDCWG Web site.) There are no webFactor change orders to review at this meeting.

5. Review of Active NERC IT Services Change Orders (CO) (Secretary’s Note: The NERC IT Services Change Orders for discussion at this meeting are posted in a zip file on the IDCWG Web site.)

There are no NERC IT Services change orders to review at this meeting.

6. Review of Active Book of Flowgates Change Orders (CO) (Secretary’s Note: The Book of Flowgates Change Orders for discussion at this meeting are posted in a zip file on the IDCWG Web site.)

a. CO‐10: Validate Temporary Flowgates in Book of Flowgates (Status — Approved for development) Action: NERC has signed BoF CO‐10. Review development status.


5

b. CO‐11: Base Case Deadline Communication (Status — Evaluated, at its January 2011 meeting, the DFWG deferred further action until its next meeting)

Action: On hold.

c. CO‐15: MISO Source‐Sink Mapping (Status — Approved for development) Action: NERC has signed CO‐15. Review development status.

7. IDCWG Calendar of Change Order Implementation and Other IDC-Related Events

a. May 18, 2011

i. IDC CO‐319 (Posting of Current TLR Data to the NERC Data Exchange Site) implemented

ii. IDC CO‐305 (NNL Worksheet in Study Mode) implemented

iii. NERC IT Services CO‐01 (Posting of Current TLR Data to the NERC Data Exchange Site) implemented

b. June 1, 2011 – IDC Summer Model Update

c. June 29, 2011

i. IDC CO‐313 (Use of SDX Common Names in IDC) implemented

ii. IDC CO‐324 (Change in Default TLR Start Time for TLR 3B and 5B in IDC TLR Issuance Window) implemented

iii. IDC CO‐327 (Creation of TVAT Pseudo Balancing Authority for the Alcoa Elements in the TVA Balancing Authority) implemented

iv. WebSDX CO‐07 (SDX File Daily Load Time Conversion) implemented

d. June 30, 2011 – IDC Summer Model Update

e. August 3, 2011 – IDC Summer Model Update

f. September 1, 2011 – IDC Summer Model Update

g. October 4, 2011 – IDC Summer Model Update

8. IDCWG Maintenance

a. IDC operation:

i. IDC and SDX user comments

b. Event/incident reports – OATI

i. Review Help Desk calls

9. New Projects, Issues, Other

a. WebSDX Documentation The working group will review Version 1.0 of the Balancing Authority webSDX User Guide for Providing Generator Outputs and


6

Priority and Version 2.3 of the webSDX User Administrator Registration Guide to determine if these documents require revision to support implementation of IDC CO‐322.

b. Change Order Prioritization The working group will continue its discussion of prioritizing change order development for 2011.

c. Default Time for TLR 1 The working group will discuss the need to change the default start time when issuing a TLR 1.

d. DFTFFG List Server Following the merger of the DFWG into the IDCWG, several NERC list servers were consolidated and some eliminated. However, OATI noted that some messages which emanate from the Book of Flowgates application are sent to [email protected]. The working work will consider the impact of eliminating this list server.

e. GSF and GLDF Calculations Chair Bahbaz will inform the working group of recent efforts to identify the cause of sporadic inaccuracies in the IDC’s calculation of GSF and GLDF matrices.

f. TLR Level 5B Chair Bahbaz will review a draft Request for Initiation of a NAESB Business Practice Standard, Model Business Practice or Electronic Transaction to provide for reallocation during TLR 5B.

g. Reference Document Review

i. Parallel Flow Calculation Procedure Reference Document – At its May 2010 meeting, Chair Busbin requested additional time to research the history of Parallel Flow Calculation Procedure Reference Document before making a final recommendation to the Operating Reliability Subcommittee.

ii. Reliability Coordinator Reference Document – At its March 2010 meeting, the working group, by consensus, approved rewriting the SDX section of the Reliability Coordinator Reference Document to become a reliability guideline. The working group also supported the elimination of the TLR Level 6 section of the reference document. The Operating Reliability Subcommittee has not yet been informed of the working group’s decision.

* Background material included


609.452.8060 | www.nerc.com

1

Antitrust Compliance Guidelines

I. General

It is NERC’s policy and practice to obey the antitrust laws and to avoid all conduct that unreasonably restrains competition. This policy requires the avoidance of any conduct that violates, or that might appear to violate, the antitrust laws. Among other things, the antitrust laws forbid any agreement between or among competitors regarding prices, availability of service, product design, terms of sale, division of markets, allocation of customers or any other activity that unreasonably restrains competition. It is the responsibility of every NERC participant and employee who may in any way affect NERC’s compliance with the antitrust laws to carry out this commitment. Antitrust laws are complex and subject to court interpretation that can vary over time and from one court to another. The purpose of these guidelines is to alert NERC participants and employees to potential antitrust problems and to set forth policies to be followed with respect to activities that may involve antitrust considerations. In some instances, the NERC policy contained in these guidelines is stricter than the applicable antitrust laws. Any NERC participant or employee who is uncertain about the legal ramifications of a particular course of conduct or who has doubts or concerns about whether NERC’s antitrust compliance policy is implicated in any situation should consult NERC’s General Counsel immediately.

II. Prohibited Activities

Participants in NERC activities (including those of its committees and subgroups) should refrain from the following when acting in their capacity as participants in NERC activities (e.g., at NERC meetings, conference calls and in informal discussions):

• Discussions involving pricing information, especially margin (profit) and internal cost information and participants’ expectations as to their future prices or internal costs.

• Discussions of a participant’s marketing strategies.

• Discussions regarding how customers and geographical areas are to be divided among competitors.

Attachment 1.e.

Antitrust Compliance Guidelines 2

• Discussions concerning the exclusion of competitors from markets.

• Discussions concerning boycotting or group refusals to deal with competitors, vendors or suppliers.

• Any other matters that do not clearly fall within these guidelines should be reviewed with NERC’s General Counsel before being discussed.

III. Activities That Are Permitted

From time to time decisions or actions of NERC (including those of its committees and subgroups) may have a negative impact on particular entities and thus in that sense adversely impact competition. Decisions and actions by NERC (including its committees and subgroups) should only be undertaken for the purpose of promoting and maintaining the reliability and adequacy of the bulk power system. If you do not have a legitimate purpose consistent with this objective for discussing a matter, please refrain from discussing the matter during NERC meetings and in other NERC-related communications. You should also ensure that NERC procedures, including those set forth in NERC’s Certificate of Incorporation, Bylaws, and Rules of Procedure are followed in conducting NERC business. In addition, all discussions in NERC meetings and other NERC-related communications should be within the scope of the mandate for or assignment to the particular NERC committee or subgroup, as well as within the scope of the published agenda for the meeting. No decisions should be made nor any actions taken in NERC activities for the purpose of giving an industry participant or group of participants a competitive advantage over other participants. In particular, decisions with respect to setting, revising, or assessing compliance with NERC reliability standards should not be influenced by anti-competitive motivations. Subject to the foregoing restrictions, participants in NERC activities may discuss:

• Reliability matters relating to the bulk power system, including operation and planning matters such as establishing or revising reliability standards, special operating procedures, operating transfer capabilities, and plans for new facilities.

• Matters relating to the impact of reliability standards for the bulk power system on electricity markets, and the impact of electricity market operations on the reliability of the bulk power system.

• Proposed filings or other communications with state or federal regulatory authorities or other governmental entities.

• Matters relating to the internal governance, management and operation of NERC, such as nominations for vacant committee positions, budgeting and assessments, and employment matters; and procedural matters such as planning and scheduling meetings.

Parliamentary Procedures Based on Robert’s Rules of Order, Newly Revised, 10th Edition, plus “Organization and Procedures Manual for the NERC Standing Committees”

Motions Unless noted otherwise, all procedures require a “second” to enable discussion.

When you want to… Procedure Debatable Comments

Raise an issue for discussion

Move Yes The main action that begins a debate.

Revise a Motion currently under discussion

Amend Yes Takes precedence over discussion of main motion. Motions to amend an amendment are allowed, but not any further. The amendment must be germane to the main motion, and can not reverse the intent of the main motion.

Reconsider a Motion already approved

Reconsider Yes Allowed only by member who voted on the prevailing side of the original motion.

End debate Call for the Question or End Debate

Yes If the Chair senses that the committee is ready to vote, he may say “if there are no objections, we will now vote on the Motion.” Otherwise, this motion is debatable and subject to 2/3 majority approval.

Record each member’s vote on a Motion

Request a Roll Call Vote

No Takes precedence over main motion. No debate allowed, but the members must approve by 2/3 majority.

Postpone discussion until later in the meeting

Lay on the Table Yes Takes precedence over main motion. Used only to postpone discussion until later in the meeting.

Postpone discussion until a future date

Postpone until Yes Takes precedence over main motion. Debatable only regarding the date (and time) at which to bring the Motion back for further discussion.

Remove the motion for any further consideration

Postpone indefinitely

Yes Takes precedence over main motion. Debate can extend to the discussion of the main motion. If approved, it effectively “kills” the motion. Useful for disposing of a badly chosen motion that can not be adopted or rejected without undesirable consequences.

Request a review of procedure

Point of order No Second not required. The Chair or secretary shall review the parliamentary procedure used during the discussion of the Motion.

Notes on Motions

Seconds. A Motion must have a second to ensure that at least two members wish to discuss the issue. The “seconder” is not recorded in the minutes. Neither are motions that do not receive a second.

Announcement by the Chair. The Chair should announce the Motion before debate begins. This ensures that the wording is understood by the membership. Once the Motion is announced and seconded, the Committee “owns” the motion, and must deal with it according to parliamentary procedure.

Attachment 1.f.

Voting Voting Method When Used How Recorded in Minutes

Unanimous Consent When the Chair senses that the Committee is substantially in agreement, and the Motion needed little or no debate. No actual vote is taken.

The minutes show “by unanimous consent.”

Vote by Voice The standard practice. The minutes show Approved or Not Approved (or Failed).

Vote by Show of Hands (tally) To record the number of votes on each side when an issue has engendered substantial debate or appears to be divisive. Also used when a Voice Vote is inconclusive. (The Chair should ask for a Vote by Show of Hands when requested by a member).

The minutes show both vote totals, and then Approved or Not Approved (or Failed).

Vote by Roll Call To record each member’s vote. Each member is called upon by the Secretary,, and the member indicates either “Yes,” “No,” or “Present” if abstaining.

The minutes will include the list of members, how each voted or abstained, and the vote totals. Those members for which a “Yes,” “No,” or “Present” is not shown are considered absent for the vote.

Notes on Voting (Recommendations from DMB, not necessarily Mr. Robert)

Abstentions. When a member abstains, he is not voting on the Motion, and his abstention is not counted in determining the results of the vote. The Chair should not ask for a tally of those who abstained.

Determining the results. The results of the vote (other than Unanimous Consent) are determined by dividing the votes in favor by the total votes cast. Abstentions are not counted in the vote and shall not be assumed to be on either side.

“Unanimous Approval.” Can only be determined by a Roll Call vote because the other methods do not determine whether every member attending the meeting was actually present when the vote was taken, or whether there were abstentions.

Majorities. Robert’s Rules use a simple majority (one more than half) as the default for most motions. NERC uses 2/3 majority for all motions.


609.452.8060 | www.nerc.com

Minutes Interchange Distribution Calculator Working Group

May 11–12, 2011 OATI Minneapolis Office 2300 Berkshire Lane North Minneapolis, Minnesota

The Interchange Distribution Calculator Working Group (IDCWG) met on May 11–12, 2011 in Minneapolis, Minnesota. The meeting agenda is affixed as Exhibit A. Chair Yasser Bahbaz presided and Larry Kezele announced that a quorum was present. Mr. Kezele read the applicable Notice of Public Meeting. Attendees Yasser Bahbaz, Chair SPP Keith Mitchell MISO Allan Watson, Vice Chair IESO Kevin Pera Xcel Energy Cheryl Mendrala (speakerphone) ISO-NE Nelson Muller OATI Ben Taylor (speakerphone) TVA Larry Kezele NERC Carlos Gonzalez-Perez OATI David Mahlmann NYISO Ed Skiba (speakerphone) MISO LaChelle Brooks PJM Jim Latimer OATI Mohamad Yassin OATI Brian Strickland (speakerphone) ICTE Hugh Francis Southern Narinder Saini (speakerphone) Entergy Raja Thappetaobula MISO Sudhakar Chavali (speakerphone) MISO Troy Sorrells OATI Neil Shah (speakerphone) MISO Jose Medina OATI

Antitrust Compliance Statement Mr. Kezele summarized the NERC Antitrust Compliance Guidelines.

Interchange Distribution Calculator Working Group Meeting Minutes The IDCWG approved the minutes of the January 19, 2011 Distribution Factor Working Group meeting (Motion 1), the minutes of the March 23–24, 2011 IDCWG meeting (Motion 2), the minutes of the April 7, 2011 DFWG conference call meeting (Motion 3), and the minutes of the April 11, 2011 IDCWG conference call meeting (Motion 4).

Attachment 1.i.1

Interchange Distribution Calculator Working Group Meeting Minutes May 11–12, 2011

2

Future Meetings Meeting/Conf. Call Purpose Date

IDCWG Conference Call Discuss change orders CO-320, CO-321, CO-324, CO-325, CO-322, CO-07, and CO-10

June 2, 2011 (2p.m.– 4p.m. EDT)

IDCWG Meeting Regular Meeting August 24, 2011 (8a.m.– 5p.m. EDT) and August 25, 2011 (8a.m.– 5 p.m. EDT) Toronto, ON hosted by IESO

IDCWG Meeting Regular Meeting October 11, 2011 (8a.m.– 5p.m. CDT) and October 12, 2011 (8a.m.– 5 p.m. EDT) Minneapolis, MN hosted by OATI

Review of Agenda Chair Bahbaz reviewed the agenda and prioritized agenda items. The working group will conduct closed sessions as required.

IDCWG Roster The working group reviewed and revised the roster. Larry Kezele informed the working group that he will begin merging the two working groups into a single roster and two email list servers ([email protected] and [email protected]). The [email protected] list server may remain intact; however, the [email protected] and [email protected] list servers will eventually be discontinued.

IDCWG Self-directed Work Teams The working group reviewed membership of each of the self-directed work teams. Project Management Yasser Bahbaz (Team Lead), Allan Watson, Larry Kezele, Brian

Nolan Market Flow Yasser Bahbaz (Team Lead), Raja Thappetaobula, LaChelle

Brooks, Allan Watson, David Mahlmann, Larry Kezele Documentation Ben Taylor (Team Lead), Allan Watson, Cheryl Mendrala,

LaChelle Brooks, Larry Kezele

NERC Update Larry Kezele reported that the Reliability Coordinator Working Group (RCWG) met on May 3, 2011 and the Operating Reliability Subcommittee (ORS) met on May 4, 2010. Mr. Kezele reviewed the RCWG and ORS discussion topics, as identified in the agenda, and responded to working group questions. The ORS moved to cancel IDC CO-310, approved merging the RCWG into the ORS, approved merging the DFWG into the IDCWG, approved

mailto:[email protected]�






3

the formation of the Alcoa Tapoco pseudo balancing authority, and supported implementation of IDC CO-324 before the summer of 2011.

NERC/NAESB Coordination Ed Skiba, co-chair of the NAESB Business Practices Subcommittee (BPS), provided an overview of efforts to develop a permanent solution to replace the Interim solution for use in the parallel flow visualization project. The two options being considered are 1) the Hybrid option and 2) the Flowgate Allocation option. The BPS expects to arrive at a final solution at its May 17–19, 2011 meeting. Following BPS approval, the final solution will be posted for a 30-day comment period. At that point the BPS will begin development of related business practices. Executive Committee approval is also required. Other coordination issues: • Submission of Generator Priority Data – The IDCWG discussed this topic at its last

meeting and concluded that an IDC change order is not required since either the balancing authority or the reliability coordinator can supply this data. However, whether the balancing authority or the reliability coordinator submits the data, the entity must submit both the generator priority and the associated MWs. The working group discussed alternatives available for the submission of generator priority data and generator outputs. If the balancing authority submits the generator priority data, then it must also provide the MW output that is firm or the percent of MW output that is firm. This data will override data provided by its reliability coordinator. Chair Bahbaz and Brian Strickland will draft a webSDX change order to implement this proposal.

• Parallel Operation of GTL and TLR – The BPS and the IDCWG are developing commercial and reliability metrics to determine the differences in congestion relief under GTL versus TLR.

• Status of Data Submittals – Keith Mitchell will provide the BPS an update at its May 17–19, 2011 meeting.

Motions Motion-1: Moved: Raja Thappetaobula; Action: Passed. Approve the minutes of the January 19, 2011 DFWG meeting. Motion-2: Moved: Raja Thappetaobula; Action: Passed. Approve the minutes of the March 23–24, 2011 IDCWG meeting. Motion-3: Moved: Raja Thappetaobula; Action: Passed. Approve the minutes of the April 7, 2011 DFWG conference call meeting.


4

Motion-4: Moved: Raja Thappetaobula; Action: Passed. Approve the minutes of the April 11, 2011 IDCWG conference call meeting. Motion-5: Moved: Vice Chair Watson; Action: Passed. Approve CO-324 (Change in Default TLR Start Time for TLR 3B and 5B in IDC TLR Issuance Window) for evaluation. Motion-6: Moved: Ben Taylor; Action: Passed. Cancel CO-296 (Chouteau Generation Pseudo Balancing Authority). Motion-7: Moved: Hugh Francis; Action: Passed. In accordance with the Operating Reliability Subcommittee’s directive, cancel CO-310 (IDC Treatment of Tagged, Intra-Balancing Authority Transactions). Motion-8: Moved: David Mahlmann; Action: Passed. Accept CO-319 (Posting of Current TLR Data to the NERC Data Exchange Site) as implemented. Motion-9: Moved: David Mahlmann; Action: Passed. Accept NERC IT Services CO-01 (Posting of Current TLR Data to the NERC Data Exchange Site) as implemented. Motion-10: Moved: LaChelle Brooks; Action: Passed. Accept CO-305 (NNL Worksheet in Study Mode) as implemented. Motion-11: Moved: David Mahlmann; Action: Passed. Approve CO-321 (Data Interface for TLR CMR Report Data for SPP) for development, contingent upon resolution of an agreement between NERC and SPP regarding funding. Motion-12: Moved: Ben Taylor; Action: Passed. Approve CO-09 (Addition of Derate Validation to webSDX) for evaluation.

Motion-13: Moved: Ben Taylor; Action: Passed. Approve CO-327 (Creation of TAP Pseudo Balancing Authority for the Alcoa Elements in the TVA Balancing Authority) for evaluation.

IDC Change Orders (CO) 1. CO-283 Generator-to-Load Reporting Requirements

• Model Updates – When the model is updated in the GTL environment, errors are flagged and messages sent to the submitter. Mohamad Yassin suggested that reliability coordinator support staff be informed of model updates prior to the model be uploaded.


5

• TSIN Mapping of Sources to Generators – This information is needed to identify the sources of e-Tags, which would improve IDC granularity.

• GLT Metrics – See discussion of CO-326 below. • Status of GTL Data Transmittals – This agenda item was not discussed. • Reliability Coordinator Permissions to Address GTL Data Confidentiality – The

working group reviewed the current list of reliability coordinator permissions received.

2. CO-296 Chouteau Generation Pseudo Balancing Authority

Chair Bahbaz reported that there are operating guides in place to monitor the dispatch and system impact of Chouteau generation. Ben Taylor moved to cancel CO-296 (Motion 6). The working group approved the motion.

3. CO-305 NNL Worksheet in Study Mode The NNL worksheet is now available to operators only when the reliability coordinator has NNL relief obligations as part of a TLR Level 5. Revision 2 of CO-305 is a request to make the NNL Worksheet available as a study tool for use by operators at anytime. By implementing the NNL worksheet in study mode, operators would be able to select a flowgate, inspect the current amount of NNL flowing on the flowgate, specify a desired amount of NNL relief, and step through the NNL worksheet process to determine which units to move to achieve the desired amount of NNL relief. The working group approved Revision 2 of CO-305 for development at its May 2010 meeting. Larry Kezele reported that NERC has approved CO-305 for development. Mohamad Yassin reported that CO-305 is ready for testing. Vice Chair Watson, Brian Strickland and Chair Bahbaz tested the development of CO-305. LaChelle Brooks moved to accept CO-305 as implemented (Motion 10). The working group approved the motion.

4. CO-310 IDC Treatment of Tagged, Intra-Balancing Authority Transactions

The present determination of Balancing Area to Balancing Area (BA to BA) transactional impacts on any given flowgate by the IDC is through the calculation and use of transfer distribution factors (TDFs). Presently, impacts of tagged, intra-BA transactions on any given flowgate are not subject to curtailment as the calculated intra-BA TDF will always be zero, which is, of course, below the curtailment threshold criterion of 5%. To capture the impact of intra-BA transactions on flowgates, the IDC would be modified to identify those tagged transactions which source and sink in the same BA. Where the specific generation source is not known for a tagged, intra-BA transaction, a calculation utilizing the BA’s TDF and LSF would be utilized to assess its impact on any given flowgate – such that flowgate impact due to intra-BA “X” transaction is equal to TDF (BA X) – LSF (BA X). Where the specific generation source is known for tagged, intra-BA transactions, a calculation utilizing the BA’s GSF and LSF


6

should be utilized to assess its impact on any given flowgate – such that flowgate impact due to intra-BA “X” transaction is equal to GSF (Gen in BA X) – LSF (BA X). In accordance with the Operating Reliability Subcommittee’s directive, Hugh Francis moved to cancel CO-310 (Motion 7). The working group approved the motion.

5. CO-313 Use of SDX Common Names in IDC CO-313 seeks to introduce the use of the common name identifier within the IDC and

to specifically utilize common names within displays which present Generation Shift Factors (GSF) and/or bus names associated with Network and Native Load (NNL) calculations. Thus, CO-313 requests that functionality be added to the IDC such that webSDX common names, when present, replace bus names given in the model and that this change be incorporated into displays which present Generation Shift Factors (GSF) and/or bus names associated with NNL calculations.

The working approved CO-313 for development at its October 2010 meeting. Larry

Kezele reported that NERC approved CO-313 for development. Mohamad Yassin reported that OATI has not yet started on the development of CO-313.

6. CO-315 Circuit B3M (ONT-ITC) Phase Shifter Modeling Changes

Raja Thappetaobula and David Mahlmann reported that NYISO, MISO, PJM, and IESO are reviewing CO-315. CO-315 may be redrafted following this review.

7. CO-316 Send a Target Market Flow not Equal to 9999 to External Market Entities of Flowgates CO-316 addresses the sending of a target market flow not equal to 9999 to external market entities of flowgates. Chair Bahbaz reported that the working group previously addressed target market flow through the implementation of multiple change orders. At the working group’s August 2010 meeting, former Chair Busbin suggested that the Congestion Management Working Group consider the impacts of implementation of CO-316 before the working group takes action. Chair Bahbaz reported that the Market Flow Task Force of the CMWG is reviewing development and deployment of CO-316 and requested that further action by the working group related to CO-316 remain on hold.

8. CO-317 Michigan–Ontario PAR Status Change Switch

The working group approved CO-317 for development, contingent upon resolution of a contractual agreement regarding funding between NERC and MISO, at its October 18, 2010 conference call meeting. CO-317 requests a single status flag that resets all four PARs in the MI-ONT interface with a single status change.


7

9. CO-319 Posting of Current TLR Data to the NERC Data Exchange Site CO-319 proposes that the current TLR Data generated in the IDC be posted in XML format to the NERC Data Exchange site that is hosted by OATI on behalf of NERC. The NERC Data Exchange site also includes historical Factors files in CSV format. Thus, implementation of CO-319 provides an alternative source of current TLR data in the event that the NERC CRC site is unavailable.

The working group approved CO-319 for development at its January 2011 meeting. Larry Kezele reported that NERC approved CO-319 for development. David Mahlmann moved to accept CO-319 as implemented (Motion 8). The working group approved the motion.

10. CO-320 Set PGEN for Base Loaded Units to Effective PMAX for NNL Chair Bahbaz explained that the NNL relief requirement is currently determined by the amount of online generation available to serve a particular load value submitted to SDX. All online generation is adjusted to meet this load value. The scaled value does not always represent the correct real time output for these units. Knowing that base loaded units are typically always at or close to PMAX, and that these units are flagged, thru setting MBASE to zero, to exempt them from participating in TDF calculations, a logic can be put in place to set the PGEN for these units for NNL purposes to the effective PMAX when appropriate. Implementation of CO-320 changes the IDC logic for NNL allocation to set the SCALED PGEN for units with MBASE of 1.1 or less (=<1.1) to their effective PMAX. Effective PMAX should reflect any de-rates or outages submitted for the units. The units may be scaled lower than the effective PMAX only if the total PMAX of units is greater than the load value submitted to SDX.

The working group approved CO-320 for development at its March 2011 meeting. Larry Kezele reported that NERC approved CO-320 for development. Mohamad Yassin reported that OATI has begun development of CO-320.

11. CO-321 Data Interface for TLR CMR Report Data for SPP The working group reviewed the evaluation of CO-321. Chair Bahbaz explained that currently the NERC IDC Tool generates a Congestion Management Report (CMR) for every TLR issuance. This report is available through Graphical User Interface (GUI) and is available for manual user download in a Comma Separated Value (CSV) format. Implementation of CO-321 would transfer all TLR data that is currently available through downloadable CSV format CMR automatically into the OATI webData for every confirmed TLR Level 3 or greater. The data would be sent for the entire TLR event once, after the TLR event is terminated and all curtailments and reloads associated with any of the TLR actions in the event are completed.


8

David Mahlmann moved to approve CO-321 for development, contingent upon resolution of an agreement between NERC and SPP regarding funding (Motion 11). The working group approved the motion.

12. CO-322 ATSI Integration into PJM Carlos Gonzalez-Perez reported that OATI reviewed the draft CO-322 for the ATSI (FirstEnergy Corp) Integration into PJM on June 1, 2011. There are no code changes needed to accomplish the purpose of CO-322, since all requirements can be met through data changes in the model, the Book of Flowgates, and the NERC Registry. Therefore, OATI recommends that PJM and the IDCWG withdraw the draft of CO-322 and that the change order number be used for an upcoming draft. In addition, during its discussion of CO-322, the IDCWG acknowledged that the June 1, 2011 IDC base case model cutover time and model build would begin at 12:30 EDT and is expected to be complete at 1:15 EDT.

13. CO-323 MISO Request to Access IDC Data for webImpact Implementation of CO-323 provides the aggregated impact of Midwest ISO scheduled firm transmission service reservations on coordinated flowgates. This impact will be used by the Midwest ISO to determine the firm limit of its market flows on its reciprocally coordinated flowgates. Development of CO-323 would require OATI to build an interface between the NERC IDC and OATI’s webImpact, which is an OATI hosted engine to calculate the requested impacts, to support the following tasks:

i) Access the Transfer Distribution Factors (TDFs)

ii) Identify interchange schedules that source/sink or wheel through the Midwest ISO system

iii) Retrieve the list of Midwest ISO coordinated flowgates

The working group approved CO-323 for development at its March 2011 meeting. Larry Kezele reported that NERC approved CO-323 for development. Jim Latimer reported that CO-323 is under development.

14. CO-324 Change in Default TLR Start Time for TLR 3B and 5B in IDC TLR Issuance Window The working group reviewed a draft of CO-324. Raja Thappetaobula explained that currently, in the NERC IDC Tool TLR Issuance Window whenever a reliability coordinator selects a TLR 3B or TLR 5B the IDC defaults the TLR start time to 10 minutes from the time the reliability coordinator selected the TLR level option. The reliability coordinator still has the option to change the start time to any time that they prefer to be the start time of TLR, but generally the issuing reliability coordinator issues the TLR with a start time of 10 minutes from the issue time without changing


9

the start time. This causes issues to impacted sink reliability coordinators in that they have less time to acknowledge the TLR and, in some instances, a sink balancing authority’s schedulers end up denying tag curtailments to avoid NERC BAL standard violations. In order to avoid the above situations, implementation of CO-324 changes the default TLR start time to 20 minutes from the time TLR level 3B or 5B is selected. The reliability coordinator will still have the option to change the start time to any time that they prefer to be the start time of TLR. The issuance of TLR 3B and 5B should also be considered in reliability coordinator training programs. The working group discussed specific examples related to the timing of the issuance of a TLR 3B and a TLR 5B. Following the working group’s discussion, Vice Chair Watson moved to approve CO-324 for evaluation (Motion 5). The working group approved the motion.

15. CO-325 Changes to TLR Event History Display

Chair Bahbaz explained that currently, the IDC’s TLR Event History display, which is used for post analysis, displays a summary of each TLR issuance on the specific flowgate. There are columns for data such as relief requested, remaining relief, relief provided, the number of tags curtailed, and the MW value of curtailments. He stated that this display includes “not required tags” and tags that have an outside restriction placed on them by balancing authorities that were not actually curtailed by the TLR. This can mislead IDC users. Implementation of CO-325 modifies the TLR Event History display by deleting the requested relief column and changing the relief provided, tags cut, and MWs cut columns to the values in the row labeled “Required Tags”. Mohamad Yassin reported that OATI has not yet evaluated CO-325.

16. CO-326 Parallel Flow Visualization Metrics The working group reviewed a draft of CO-326. Chair Bahbaz explained the purpose of CO-326 which is:

As the parallel flow visualization (PFV) project prepares to enter the pilot period, more benchmarking tools are needed to compare the results in both current production IDC logic and the generator-to-load (GTL) calculation logic. The difference between the two logics in the two environments should be justifiable and defensible through the enhancements in visualization of parallel flows in the IDC. The following metrics assume that the methodology for PFV relief assignment has been determined and incorporated into the IDC.


10

To accomplish this testing and comparison, the working group requests that OATI creates metrics in the IDC to analyze the GTL calculation, compare it to the current IDC logic and evaluate the differences in results. The core of CO-326 is to help accomplish the following objectives:

• Measure the accuracy of the data inputted by reliability coordinators, balancing authorities, transmission service providers, and transmission operators

• Measure the availability and the frequency of updated data submission by entities

• Validate that the correct PFV calculation methodology logic is implemented

• Measure the accuracy of the results of the PFV logic

• Quantify the differences between the PFV calculations and the results with respect to the current IDC logic in terms of curtailments and relief assignments

The working group discussed the metrics identified in draft CO-326. Chair Bahbaz will redraft CO-326 based upon the working group’s discussion. Chair Bahbaz formed a GTL/PFV task team (Vice Chair Watson, Ben Taylor, Chair Bahbaz, Hugh Francis, Mohamad Yassin, and LaChelle Brooks) to begin development of GUI displays to present the reliability metrics data. Chair Bahbaz also formed a GTL calculations team (David Mahlmann, Ben Taylor, Chair Bahbaz, LaChelle Brooks, and Mohamad Yassin). The task teams will report out at the working group’s August 2011 meeting.

17. CO-327 Creation of TVAT Pseudo Balancing Authority for the Alcoa Elements in the TVA Balancing Authority Ben Taylor reviewed a draft of CO-327, which creates a new pseudo balancing authority within the TVA balancing authority. The Operating Reliability Subcommittee approved the formation of this pseudo balancing authority at its May 4, 2011 meeting. Ben Taylor moved to approve CO-327 for evaluation (Motion 13). The working group approved the motion.

SDX Change Orders (CO) 1. CO-07 SDX File Daily Load Time Conversion

Currently, in the SDX files for daily load data, no time conversion occurs between the submitted file and the posted file, when in two different time zones. For example, PJM submits data in Eastern Time. The peak times for daily loads do not convert to Central Standard Time before posting. Implementation of webSDX CO-07 would correctly apply the time conversion for daily load data in the webSDX files. The working group approved webSDX CO-07 for development at its March 2010 meeting. Larry Kezele reported that NERC approved CO-07 for development. Mohamad Yassin


11

reported that OATI has completed development of CO-07. LaChelle Brooks will test the development of CO-07. CO-08 Remaining GUI Changes Chair Bahbaz reminded the working group that during its April 26, 2010 conference call, it was agreed that webSDX CO-02 (Miscellaneous GUI Changes) would be partially implemented with the understanding that sections 4 and 5 of the change order would be addressed in a new change order. The purpose of webSDX CO-08 is to address those outstanding items; however, the change order also requested additional functionality not originally requested in webSDX CO-02. The working group deferred action on CO-08 until its next meeting.

2. CO-09 Addition of Derate Validation to webSDX Ben Taylor stated that currently there is no validation performed by the webSDX tool to ensure a unit is not being de-rated to above its Pmax in the base case. This, however unlikely, has been a problem in the past and has resulted in inaccurate information being posted to the webSDX tool and, consequently, potentially being used in the planning of operations. Ben Taylor moved to approve CO-09 for evaluation (Motion 12). The working group approved the motion.

WebFactor Change Orders (CO) There were no webFactor change orders to consider. NERC IT Services Change Orders (CO) 1. CO-01 Posting of Current TLR Data to the NERC Data Exchange Site

The working group reviewed the evaluation of NERC IT Services CO-01. CO-01 proposes that the current TLR Data generated in the IDC be posted in XML format to the NERC Data Exchange site that is hosted by OATI on behalf of NERC. The NERC Data Exchange site also includes historical Factors files in CSV format. Thus, implementation of CO-01 provides an alternative source of current TLR data in the event that the NERC CRC site is unavailable. The working group approved CO-01 for development at its January 2011 meeting. Larry Kezele reported that NERC approved CO-01 for development. David Mahlmann moved to accept NERC IT Services CO-01 as implemented (Motion 9). The working group approved the motion.

Book of Flowgates Change Orders (CO) 1. CO-10 Validate Temporary Flowgates in Book of Flowgates


12

Larry Kezele reported that the DFWG approved BoF CO-10 for development at its March 30, 2010 meeting and that the costs for developing the change order are included in NERC’s 2011 budget. Larry Kezele reported that NERC approved CO-10 for development. Mohamad Yassin reported that OATI has not yet started development of CO-10.

2. CO-11 Base Case Deadline Communication Larry Kezele reported that the DFWG approved BoF CO-11 for evaluation at its March 30, 2010 meeting. At its January 2011 meeting, the DFWG decided to keep BoF CO-11 on hold until its next meeting. Ben Taylor will revise the script and base case development timeline to include information through 2013.

3. CO-14 ATSI Integration into PJM Carlos Gonzalez-Perez reported that OATI reviewed the draft CO-14 for the ATSI (FirstEnergy Corp) Integration into PJM on June 1, 2011. There are no code changes needed to accomplish the purpose of CO-14, since all requirements can be met through data changes in the model, the Book of Flowgates, and the NERC Registry. Therefore, OATI recommends that PJM and the IDCWG withdraw the draft of CO-14 and that the change order number be used for an upcoming draft.

4. CO-15 MISO Source-Sink Mapping Implementation of CO-15 would provide the Midwest ISO with the aggregated impact of its scheduled firm transmission service reservations on coordinated flowgates. MISO will use this impact to determine the firm limit of its market flows on its reciprocally coordinated flowgates. Development of CO-15 requires OATI to build an interface between the NERC IDC and OATI’s webImpact, which is an OATI hosted engine to calculate the requested impacts, to support the following tasks:

i) Access the Transfer Distribution Factors (TDFs)

ii) Identify interchange schedules that source/sink or wheel through the Midwest ISO system

iii) Retrieve the list of Midwest ISO coordinated flowgates

Furthermore, implementation of CO-15 requires that the distribution factors for the Midwest ISO OASIS sources and sinks be a data source into webImpact. However, currently there is no specific mapping of OASIS sources and sinks to generators available in the Flowgate Management System (BOF) or IDC. CO-15 requests the creation of a mapping in the BOF to resolve this issue. This mapping would be updated through the IDC model update process via the Book of Flowgates.


13

Finally, the process for model update would to be modified to enable MISO personnel to resolve any mapping errors via the BOF user interface. This shall take place following the base case upload done by the BOF administrator. The working group approved CO-15 for development at its March 2011 meeting. Larry Kezele reported that NERC approved CO-15 for development. Jim Latimer reported that CO-15 is under development.


14

Calendar of Change Order Implementation and Other Related Events

1. May 6, 2011 – IDC Summer Model Upload

2. May 10, 2011 – Emergency IDC Summer Model Update

3. May 18, 2011

a. NERC IT Services CO-01 (Posting of Current TLR Data to the NERC Data Exchange Site) implemented

b. IDC CO-319 (Posting of Current TLR Data to the NERC Data Exchange Site) implemented

c. IDC CO-305 (NNL Worksheet in Study Mode) implemented

4. June 1, 2011 – IDC Summer Model Update

5. July 6, 2011 – IDC Summer Model Update

6. August 3, 2011 – IDC Summer Model Update

7. September 1, 2011 – IDC Summer Model Update

8. October 4, 2011 – IDC Summer Model Update

IDC Operations and Maintenance 1. IDC and SDX User Comments

a. TLR Trends – OATI analyzed TLR events for trends and presented its findings. The trends indicated that conducting the model uploads at 2230 CPT is less impactful to system operations since that is when the number of TLRs are in effect begins to significantly decrease. The working group decided to continue conducting model uploads at 2230 CPT.

2. IDC Event/Incident Reports — Mohamad Yassin reviewed IDC and webSDX help desk calls since the working group’s March 23–24, 2011 meeting.

3. Transition of IDC, SDX, and BoF to a New Production Platform — Troy Sorrells briefed the working group regarding the transition of the IDC, webSDX and the BoF from its existing production platform to the new production platform. The transition required all system users to modify the IP addresses and URLs used to access these reliability tools. OATI refers to the new hardware platform as its “private cloud environment.” All software applications will be accessible at either of the two OATI data centers.

New Projects, Issues, and Other IDC/webSDX Matters 1. WebSDX Documentation The working group reviewed Version 1.0 of the Balancing

Authority webSDX User Guide for Providing Generator Outputs and Priority and Version 2.3 of the webSDX User Administrator Registration Guide. These documents may require revision to reflect development and implementation of IDC CO-322.


15

2. Change Order Prioritization The working group discussed its 2011 budget for IDC,

webSDX, webFactor, and BoF change orders and prioritized those that should begin development as soon as practicable.

3. Impact of E-Tags That Do Not Start at the Top of the Hour Yasser Bahbaz explained

that when an e-Tag starts sometime during the upcoming hour, it is not curtailed during a TLR 3A. The working group previously drafted and implemented CO-128 (User Interface for Intra-hour e-Tags) to address this issue and a GUI display was developed to capture data related to intra-hour e-Tags.

Nelson Muller reviewed two options for further analysis to capture these e-Tags that would otherwise not be curtailed. Implementation of either option would result in running TLRs every 15 minutes. The working group decided that intra-hour e-Tags would be reliability capped at the lowest scheduled MW amount and the TLR curtailment calculation would use the reliability cap to determine the tag’s curtailment adjustment. Chair Bahbaz will draft an IDC change order for the working group’s further discussion.

4. SDX Data Submittals Ben Taylor explained that the working group should revisit the SDX data submittal verification or quality check routines. In some instances, generators are being de-rated to a level in excess of its base case Pmax. OATI reviewed the existing data verification and quality check routines. Mr. Taylor suggested modifying the data quality check routine such that a data submission that includes a generator unit de-rate to a level in excess of its Pmax would not be accepted. Mohamad Yassin stated that this data validation check could be easily added. Mr. Taylor drafted a webSDX change order to add this validation check (see discussion of webSDX CO-09 above).

5. Net Target Market Flow The working group deferred discussion of this topic to its next meeting.

6. TLR Level 5B — Chair Bahbaz stated that the initial issuance of a TLR 5B does not

result in reallocation of transactions in the next hour as is done when a TLR 3B is issued. This is especially problematic when back-to-back 5Bs are issued, since the TLR curtailments keep increasing. Nelson Muller queried the IDC on the number of back-to-back TLR 5Bs and determined that this occurs about once a month. He will draft a Request for Initiation of a NAESB Business Practice Standard for the working group’s review at its June 2, 2011 conference call.


16

7. Reference Document Review i. Parallel Flow Calculation Procedure Reference Document – Larry Kezele

recommended that the working group not expend additional resources to revise the Parallel Flow Calculation Procedure Reference Document, given that the NAESB BPS will be rewriting the TLR business practices to implement the approved permanent solution.

ii. Reliability Coordinator Reference Document – Chair Bahbaz requested the Documentation SDWT to review the status of the Reliability Coordinator Reference Document.

Adjournment The meeting was adjourned at 2:21 p.m. CDT on May 12, 2011.

Larry Kezele Larry Kezele Secretary


609.452.8060 | www.nerc.com

Minutes – Conference Call Interchange Distribution Calculator Working Group June 2, 2011 | 2–4 p.m. (EDT)

The Interchange Distribution Calculator Working Group (IDCWG) met by conference call on June 2, 2011 at 2:00 p.m. EDT. Chair Yasser Bahbaz presided and Larry Kezele announced that a quorum was present. Attendees Yasser Bahbaz, Chair SPP Allan Watson, Vice Chair IESO Ben Taylor TVA Hugh Francis Southern David Mahlmann NYISO Raja Thappetaobula MISO LaChelle Brooks PJM Brian Strickland ICTE Carlos Gonzalez-Perez OATI Jim Latimer OATI Wendy Ladd VACAR-S Mohamad Yassin OATI Larry Kezele NERC Notice of Public Meeting LLaarrrryy KKeezzeellee rreeaadd tthhee aapppplliiccaabbllee NNoottiiccee ooff PPuubblliicc MMeeeettiinngg..

Antitrust Compliance Statement Larry Kezele summarized the NERC Antitrust Compliance Guidelines.

Conference Call Summary The Interchange Distribution Calculator Working Group discussed the following:

Attachment 1.i.2

Interchange Distribution Calculator Working Group Conference Call Minutes June 2, 2011

2

IDC Change Orders

1. CO‐313 Use of SDX Common Names in IDC CO‐313 seeks to introduce the use of the common name identifier within the IDC and to specifically utilize common names within displays which present Generation Shift Factors (GSF) and/or bus names associated with Network and Native Load (NNL) calculations. Thus, CO‐313 requests that functionality be added to the IDC such that webSDX common names, when present, replace bus names given in the model and that this change be incorporated into displays which present Generation Shift Factors (GSF) and/or bus names associated with NNL calculations.

The working approved CO‐313 for development at its October 2010 meeting. OATI reported CO‐313 is ready for testing, and Vice Chair Watson and Brian Strickland were tasked to test its development.

2. CO‐320 Set PGEN for Base Loaded Units to Effective PMAX for NNL Chair Bahbaz explained that the NNL relief requirement is currently determined by the amount of online generation available to serve a particular load value submitted to SDX. All online generation is adjusted to meet this load value. The scaled value does not always represent the correct real time output for these units. Knowing that base loaded units are typically always at or close to PMAX, and that these units are flagged, thru setting MBASE to zero, to exempt them from participating in TDF calculations, a logic can be put in place to set the PGEN for these units for NNL purposes to the effective PMAX when appropriate. Implementation of CO‐320 changes the IDC logic for NNL allocation to set the SCALED PGEN for units with MBASE of 1.1 or less (=<1.1) to their effective PMAX. Effective PMAX should reflect any de‐rates or outages submitted for the units. The units may be scaled lower than the effective PMAX only if the total PMAX of units is greater than the load value submitted to SDX.

The working group approved CO‐320 for development at its March 2011 meeting. Mohamad Yassin reported that CO‐320 is still under development.

3. CO‐321 Data Interface for TLR CMR Report Data for SPP Chair Bahbaz explained that currently the NERC IDC Tool generates a Congestion Management Report (CMR) for every TLR issuance. This report is available through Graphical User Interface (GUI) and is available for manual user download in a Comma Separated Value (CSV) format. Implementation of CO‐321 would transfer all TLR data that is currently available through downloadable CSV format CMR automatically into the OATI webData for


3

every confirmed TLR Level 3 or greater. The data would be sent for the entire TLR event once, after the TLR event is terminated and all curtailments and reloads associated with any of the TLR actions in the event are completed.

The working group approved CO‐321 for development, contingent upon resolution of an agreement between NERC and SPP regarding funding at its May 2011 meeting. The working group took no further action regarding CO‐321.

4. CO‐322 Generation Priority Submission Chair Bahbaz reviewed a draft of CO‐322. He explained that part of the Parallel Flow Visualization project is that entities are required to submit the MW output for each generator accompanied with the priority assigned to each MW. Currently, the priority is submitted in the same WebMethod as the generator MW output. There is a need for the flexibility to allow different entities to submit real MW output and the associated priority of the MW.

The working group will further consider CO‐322 at its next meeting.

5. CO‐324 Change in Default TLR Start Time for TLR 3B and 5B in IDC TLR Issuance

Window The working group reviewed the evaluation of CO‐324. Chair Yasser explained that currently, in the NERC IDC Tool TLR Issuance Window whenever a reliability coordinator selects a TLR 3B or TLR 5B the IDC defaults the TLR start time to 10 minutes from the time the reliability coordinator selected the TLR level option. The reliability coordinator still has the option to change the start time to any time that they prefer to be the start time of TLR, but generally the issuing reliability coordinator issues the TLR with a start time of 10 minutes from the issue time without changing the start time. This causes issues to impacted sink reliability coordinators in that they have less time to acknowledge the TLR and, in some instances, a sink balancing authority’s schedulers end up denying tag curtailments to avoid NERC BAL standard violations. In order to avoid the above situations, implementation of CO‐324 changes the default TLR start time to 20 minutes from the time TLR level 3B or 5B is selected. The reliability coordinator will still have the option to change the start time to any time that they prefer to be the start time of TLR. The issuance of TLR 3B and 5B should also be considered in reliability coordinator training programs. Chair Bahbaz further explained that he briefed the Operating Reliability Subcommittee regarding CO‐324. Following the working group’s discussion, Vice Chair Watson moved to approve CO‐324 for development. The working group approved the motion.


4

6. CO‐325 Changes to TLR Event History Display Chair Bahbaz explained that currently, the IDC’s TLR Event History display, which is used for post analysis, displays a summary of each TLR issuance on the specific flowgate. There are columns for data such as relief requested, remaining relief, relief provided, the number of tags curtailed, and the MW value of curtailments. He stated that this display includes “not required tags” and tags that have an outside restriction placed on them by balancing authorities that were not actually curtailed by the TLR. This can mislead IDC users. Implementation of CO‐325 modifies the TLR Event History display by deleting the requested relief column and changing the relief provided, tags cut, and MWs cut columns to the values in the row labeled “Required Tags”. The working group reviewed the evaluation of CO‐325. Following its review, Raja Thappetaobula moved to approve CO‐325 for development. The working group approved the motion.

7. CO‐326 Parallel Flow Visualization Metrics Chair Bahbaz reported that he will send out a revised draft of CO‐326 for working group comments.

8. CO‐327 Creation of TVAT Pseudo Balancing Authority for the Alcoa Elements in the TVA Balancing Authority Ben Taylor reviewed the evaluation of Version 1 of CO‐327, which creates a new pseudo balancing authority within the TVA balancing authority. The Operating Reliability Subcommittee approved the formation of this pseudo balancing authority at its May 4, 2011 meeting. Mr. Taylor noted that minor revisions were needed in the change order; therefore, he moved to approve Version 2 of CO‐327 for evaluation. The working group approved the motion. Following the working group’s review of the evaluation of Version 2 of CO‐327, Ben Taylor moved to approve Version 2 of CO‐327 for development. The working group approved the motion.

9. CO‐328 Intra‐Hour Tag Curtailments Chair Bahbaz reviewed a draft of CO‐328. Currently the IDC only takes into consideration the profile value at the time of the effective TLR Time. If a tag has a profile of 0 MW at xx: 00 for TLR xA level but 100 MW xx: 15 thru xx+1:00, the TLR will consider the 0 MW for impact purpose and, therefore, it will not curtail the tag regardless of the priority. The method for which the impacts are captured should be changed to account for the profile changes of tags within the hour and assign a target MW for each tag.


5

Hugh Francis moved to approve CO‐328 for evaluation. The working group approved the motion.

10. CO‐329 Load Adjustment During TLR 5 Issuance Chair Bahbaz reviewed a draft of CO‐329. During TLR level 5, NNL is allocated to each entity depending on their impact on the flowgates based on their generator impact. Balancing authority load is used for scaling the generators, which is used for calculating NNL on the flowgate. These balancing authority load values are uploaded to SDX. If no data is being uploaded to SDX, then the load value defaults to base case load, which are the seasonal loads. Using these base case loads can inflate the NNL relief allocated to the balancing authorities, especially during shoulder months.

The working group requested revisions to the draft change order, and Hugh Francis moved to approve CO‐329 for evaluation. The working group approved the motion.

WebSDX Change Orders

1. CO‐07 SDX File Daily Load Time Conversion Currently, in the SDX files for daily load data, no time conversion occurs between the submitted file and the posted file, when in two different time zones. For example, PJM submits data in Eastern Time. The peak times for daily loads do not convert to Central Standard Time before posting. Implementation of webSDX CO‐07 would correctly apply the time conversion for daily load data in the webSDX files. The working group approved webSDX CO‐07 for development at its March 2010 meeting. Larry Kezele reported that NERC approved CO‐07 for development. Mohamad Yassin reported that OATI has completed development of CO‐07. LaChelle Brooks was tasked to test the development of CO‐07.

Book of Flowgates Change Orders

1. CO‐10 Validate Temporary Flowgates in Book of Flowgates Larry Kezele reported that the DFWG approved BoF CO‐10 for development at its March 30, 2010 meeting and that the costs for developing the change order are included in NERC’s 2011 budget. Larry Kezele reported that NERC approved CO‐10 for development. Mohamad Yassin reported that CO‐10 is still in development.

Other

1. Draft SMEE to Southern Change Order Hugh Francis explained that the South Mississippi Electric Power Association (SMEPA) is a registered balancing authority and load‐serving entity. SMEPA has load inside the boundaries of the balancing area and also in the Entergy


6

balancing area (SMEE) and the Southern balancing area. The SMEPA load outside of the SMEPA balancing area is served through the use of e‐Tags. The SMEPA load in the Entergy balancing area (SMEE) was designated as a LSE only pseudo balancing authority in the IDC sometime in the past. This pseudo balancing authority is only used internal to the IDC. Special sink rules have already been established for SME‐EES transactions to be designated as serving SMEE load.

The working group noted that this is only a Book of Flowgates change. The working group will further discuss this topic at its August 2011 meeting.

2. Real‐time IDC Curtailments Vice Chair Watson explained that IDC TLR curtailments are periodically not being sent to the electronic tagging system; therefore, expected TLR curtailments are not being implemented. OATI reported that very sporadic instances have occurred recently, and that they are implementing internal process and monitoring to help identify the source of the problem. OATI will provide addition information as it becomes available.

3. Next Meeting The working group scheduled a one‐hour conference call meeting on June 23, 2011 at 2 p.m. EDT.

AAddjjoouurrnnmmeenntt

The conference call meeting was adjourned at 3:45 p.m. EDT on June 2, 2011.

Larry Kezele Larry J. Kezele Secretary


609.452.8060 | www.nerc.com

Minutes – Conference Call Interchange Distribution Calculator Working Group June 23, 2011 | 2 p.m.–3 p.m. (EDT)

The Interchange Distribution Calculator Working Group (IDCWG) met by conference call on June 23, 2011 at 2:00 p.m. EDT. Chair Yasser Bahbaz presided and Committee Secretary Larry Kezele announced that a quorum was present. Attendees Yasser Bahbaz, Chair SPP Allan Watson, Vice Chair IESO Ben Taylor TVA Hugh Francis Southern David Mahlmann NYISO Raja Thappetaobula MISO LaChelle Brooks PJM Brian Strickland ICTE Carlos Gonzalez-Perez OATI Jim Latimer OATI Cheryl Mendrala ISO-NE Mohamad Yassin OATI Nelson Muller OATI Lee Willingham Entergy Paul Graves FRCC Larry Kezele NERC Notice of Public Meeting LLaarrrryy KKeezzeellee rreeaadd tthhee aapppplliiccaabbllee NNoottiiccee ooff PPuubblliicc MMeeeettiinngg.. Antitrust Compliance Statement Larry Kezele summarized the NERC Antitrust Compliance Guidelines.

Attachment 1.i.3


2

Conference Call Summary

The Interchange Distribution Calculator Working Group (IDCWG) discussed the following:

IDC Change Orders

1. CO-313 Use of SDX Common Names in IDC

CO-313 seeks to introduce the use of the common name identifier within the IDC and to specifically utilize common names within displays which present Generation Shift Factors (GSF) and bus names associated with Network and Native Load (NNL) calculations. Thus, CO-313 requests that functionality be added to the IDC such that webSDX common names, when present, replace bus names given in the model and that this change be incorporated into displays which present GSF and bus names associated with NNL calculations.

The working approved CO-313 for development at its October 2010 meeting. OATI reported CO-313 is ready for testing, and Brian Strickland tested its development. Raja Thappetaobula moved to accept CO-313 as implemented. The working group approved the motion.

2. CO-320 Set PGEN for Base Loaded Units to Effective PMAX for NNL

Chair Bahbaz explained that the NNL relief requirement is currently determined by the amount of online generation available to serve a particular load value submitted to SDX. All online generation is adjusted to meet this load value. The scaled value does not always represent the correct real time output for these units. Knowing that base loaded units are typically always at or close to PMAX, and that these units are flagged, thru setting MBASE to zero, to exempt them from participating in TDF calculations, a logic can be put in place to set the PGEN for these units for NNL purposes to the effective PMAX when appropriate.

Implementation of CO-320 changes the IDC logic for NNL allocation to set the SCALED PGEN for units with MBASE of 1.1 or less (=<1.1) to their effective PMAX. Effective PMAX should reflect any de-rates or outages submitted for the units. The units may be scaled lower than the effective PMAX only if the total PMAX of units is greater than the load value submitted to SDX.

The working group approved CO-320 for development at its March 2011 meeting. OATI completed development of CO-320; however, internal testing is not complete. Chair Bahbaz, Wendy Ladd and Raja Thappetaobula will test CO-320.

3. CO-321 Data Interface for TLR CMR Report Data for SPP

Chair Bahbaz explained that currently the NERC IDC Tool generates a Congestion Management Report (CMR) for every TLR issuance. This report is available through Graphical User Interface (GUI) and is available for manual user download in a Comma Separated Value (CSV) format.


3

Implementation of CO-321 would transfer all TLR data that is currently available through downloadable CSV format CMR automatically into the OATI webData for every confirmed TLR Level 3 or greater. The data would be sent for the entire TLR event once, after the TLR event is terminated and all curtailments and reloads associated with any of the TLR actions in the event are completed.

The working group approved CO-321 for development, contingent upon resolution of an agreement between NERC and SPP regarding funding at its May 2011 meeting. The working group took no further action regarding CO-321.

4. CO-322 Generation Priority Submission

Chair Bahbaz reviewed a draft of CO-322. He explained that part of the Parallel Flow Visualization project is that entities are required to submit the MW output for each generator accompanied with the priority assigned to each MW. Currently, the priority is submitted in the same WebMethod as the generator MW output. There is a need for the flexibility to allow different entities to submit real MW output and the associated priority of the MW.

Hugh Francis moved to approve CO-322 for evaluation. The working group approved the motion.

5. CO-324 Change in Default TLR Start Time for TLR 3B and 5B in IDC TLR Issuance Window

Chair Yasser explained that currently, in the NERC IDC Tool TLR Issuance Window whenever a reliability coordinator selects a TLR 3B or TLR 5B the IDC defaults the TLR start time to 10 minutes from the time the reliability coordinator selected the TLR level option. The reliability coordinator still has the option to change the start time to any time that they prefer to be the start time of TLR, but generally the issuing reliability coordinator issues the TLR with a start time of 10 minutes from the issue time without changing the start time. This causes issues to impacted sink reliability coordinators in that they have less time to acknowledge the TLR and, in some instances, a sink balancing authority’s schedulers end up denying tag curtailments to avoid NERC BAL standard violations.

In order to avoid the above situations, implementation of CO-324 changes the default TLR start time to 20 minutes from the time TLR level 3B or 5B is selected. The reliability coordinator will still have the option to change the start time to any time that they prefer to be the start time of TLR. The issuance of TLR 3B and 5B should also be considered in reliability coordinator training programs.

OATI reported that it has completed the development and internal testing of CO-324. Raja Thappetaobula and Vice Chair Watson tested its development. Vice Chair Watson moved to accept CO-324 as implemented. The working group approved the motion.


4

Vice Chair Watson reported that the same TLR timing issues addressed by implementation of CO-324 occur when a TLR is issued at TLR Level 1 and transactions are reloaded. The default time is 10-minutes. The working group agreed to further consider this issue at its August 2011 meeting.

6. CO-325 Changes to TLR Event History Display

Chair Bahbaz explained that currently, the IDC’s TLR Event History display, which is used for post analysis, displays a summary of each TLR issuance on the specific flowgate. There are columns for data such as relief requested, remaining relief, relief provided, the number of tags curtailed, and the MW value of curtailments. He stated that this display includes “not required tags” and tags that have an outside restriction placed on them by balancing authorities that were not actually curtailed by the TLR. This can mislead IDC users.

Implementation of CO-325 modifies the TLR Event History display by deleting the requested relief column and changing the relief provided, tags cut, and MWs cut columns to the values in the row labeled “Required Tags”.

OATI report that, while it has completed development of CO-325, the change order continues to be internally tested.

7. CO-326 Parallel Flow Visualization Metrics

Chair Bahbaz reported that he will send out a revised draft of CO-326 for working group comments.

8. CO-327 Creation of TVAT Pseudo Balancing Authority for the Alcoa Elements in the TVA Balancing Authority

Ben Taylor stated that CO-327 creates a new pseudo balancing authority within the TVA balancing authority. The Operating Reliability Subcommittee approved the formation of this pseudo balancing authority at its May 4, 2011 meeting. OATI reported that, while it has completed development of CO-327, the change order cannot be tested until the IDC model has been changed to reflect the addition of the new pseudo balancing authority. Mr. Taylor asked if the July 6, 2011 summer model update could be moved to June 29, 2011. OATI expressed some concerns in moving the model update date, since the new model will contain changes related to the Generator-to-Load project. Nevertheless OATI and the working group will attempt to meet the June 29, 2011 model update date. Following this discussion, Raja Thappetaobula moved to accept Version 2 of CO-327 as implemented, contingent upon successful testing by TVA and OATI. The working group approved the motion.

9. CO-328 Intra-Hour Tag Curtailments

Chair Bahbaz reviewed the evaluation of CO-328. Currently the IDC only takes into consideration the profile value at the time of the effective TLR Time. If a tag has a profile of 0 MW at xx: 00 for TLR xA level but 100 MW xx: 15 thru xx+1:00, the TLR


5

will consider the 0 MW for impact purpose and, therefore, it will not curtail the tag regardless of the priority. The method for which the impacts are captured should be changed to account for the profile changes of tags within the hour and assign a target MW for each tag.

Hugh Francis moved to approve CO-328 for development. The working group approved the motion. Nelson Muller reported that development of CO-328 may require unforeseen changes to the IDC graphical user interface.

10. CO-329 Load Adjustment During TLR 5 Issuance

Chair Bahbaz reviewed the evaluation of CO-329. During TLR level 5, NNL is allocated to each entity depending on their impact on the flowgates based on their generator impact. Balancing authority load is used for scaling the generators, which is used for calculating NNL on the flowgate. These balancing authority load values are uploaded to SDX. If no data is being uploaded to SDX, then the load value defaults to base case load, which are the seasonal loads. Using these base case loads can inflate the NNL relief allocated to the balancing authorities, especially during shoulder months.

Hugh Francis moved to approve CO-329 for development. The working group approved the motion.

WebSDX Change Orders

1. CO-07 SDX File Daily Load Time Conversion Currently, in the SDX files for daily load data, no time conversion occurs between the submitted file and the posted file, when in two different time zones. For example, PJM submits data in Eastern Time. The peak times for daily loads do not convert to Central Standard Time before posting. Implementation of webSDX CO-07 would correctly apply the time conversion for daily load data in the webSDX files. The working group approved webSDX CO-07 for development at its March 2010 meeting. Larry Kezele reported that NERC approved CO-07 for development. Mohamad Yassin reported that OATI has completed development of CO-07. LaChelle Brooks tested the development of CO-07. Raja Thappetaobula moved to accept webSDX CO-07 as implemented. The working group approved the motion.


1. CO-10 Validate Temporary Flowgates in Book of Flowgates Larry Kezele reported that the DFWG approved BoF CO-10 for development at its March 30, 2010 meeting and that the costs for developing the change order are included in NERC’s 2011 budget. Larry Kezele reported that NERC approved CO-10 for development. Mohamad Yassin reported that CO-10 is still in development.


6

Other

1. Draft SMEE to Southern Change Order Hugh Francis explained that the South Mississippi Electric Power Association (SMEPA) is a registered balancing authority and load-serving entity. SMEPA has load inside the boundaries of the balancing area and also in the Entergy balancing area (SMEE) and the Southern balancing area. The SMEPA load outside of the SMEPA balancing area is served through the use of e-Tags.

The SMEPA load in the Entergy balancing area (SMEE) was designated as a LSE only pseudo balancing authority in the IDC sometime in the past. This pseudo balancing authority is only used internal to the IDC. Special sink rules have already been established for SME-EES transactions to be designated as serving SMEE load.

Chair Bahbaz and Hugh Francis will further discuss how to implement the required IDC model changes to model the SMEE pseudo balancing authority.

2. Real-time IDC Curtailments

OATI explained that on three occasions IDC TLR curtailments were not sent to the electronic tagging system; therefore, expected TLR curtailments were not implemented. In response, OATI re-installed an older version of middle-ware on June 3, 2011 and since then the issue has not reoccurred.

3. Status of the Generation-to-Load Project (CO-283)

OATI reported that CO-283 is now running in the IDC production environment; however, it will not begin receiving any new GTL data until completion of the July 2011 model upload. OATI reported the working group also needs to begin the GLT registration process.

4. IDC, webSDX, and Book of Flowgates

OATI reported that the test environments for the IDC, the webSDX and the Book of Flowgates have new URLs.

5. GSF and GLDF Calculations

Chair Yasser reported that sporadically the IDC’s calculation of generator shift factors and generator-to-load distribution factors are incorrect. These factors are used in NNL calculations. OATI is archiving the GSF and GLDF matrices for further analysis and investigation.

6. Change Order Implementation

The working group decided to implement IDC CO-313, IDC CO-324, and webSDX CO-07 into the IDC and webSDX production environments on Wednesday, June 29, 2011 at 10 a.m. CDT. Version 2 of IDC CO-327 will be implemented in the production environment in conjunction with the July 2011 model update.


7

7. Next Meeting

The working group scheduled a one-hour conference call meeting on July 18, 2011 at 2 p.m. EDT.

AAddjjoouurrnnmmeenntt The conference call meeting was adjourned at 3:32 p.m. EDT on June 23, 2011.



609.452.8060 | www.nerc.com

Minutes – Conference Call Interchange Distribution Calculator Working Group July 18, 2011 | 2:00 p.m.–3:00 p.m. (EDT)

The Interchange Distribution Calculator Working Group (IDCWG) met by conference call on July 18, 2011 at 2:00 p.m. EDT. Chair Yasser Bahbaz presided and Larry Kezele announced that a quorum was present. Attendees

Yasser Bahbaz, Chair SPP Allan Watson, Vice Chair IESO Mike Lowman VACAR‐S Hugh Francis Southern Raja Thappetaobula MISO LaChelle Brooks PJM Brian Strickland ICTE Carlos Gonzalez‐Perez OATI Jim Latimer OATI Nelson Muller OATI Mohamad Yassin OATI Kevin Pera Xcel Energy Lee Willingham Entergy Paul Graves FRCC Larry Kezele NERC Notice of Public Meeting

LLaarrrryy KKeezzeellee rreeaadd tthhee aapppplliiccaabbllee NNoottiiccee ooff PPuubblliicc MMeeeettiinngg..

Antitrust Compliance Statement

Larry Kezele summarized the NERC Antitrust Compliance Guidelines.

Attachment 1.i.4

July 29, 2011

75

Interchange Distribution Calculator Working Group

RC-SPP Chairman

Yasser Bahbaz Ops. Engineer II

Southwest Power Pool 415 North McKinley Suite 140 Plaza West Little Rock, Arkansas 72205-3020

(501) 688-1607 ybahbaz.re@ spp.org

RC-NPCC-IESO Vice Chairman

Allan Watson Senior Operations Officer

Independent Electricity System Operator Station A Box 4474 Toronto, Ontario M4W 4E5

(905) 855-6414 allan.watson@ ieso.ca

IESO Jose Alcaraz

Independent Electricity System Operator

jose.alcaraz@ ieso.ca

FRCC Richard Becker

Project Planning Engineer Florida Reliability Coordinating Council 1408 North Westshore Boulevard Suite 1002 Tampa, Florida 33607

(813) 207-7967 [email protected]

PJM Alternate LaChelle D Brooks

Engineer PJM Interconnection, L.L.C. 955 Jefferson Ave Norristown, Pennsylvania 19403

610-666-4302 [email protected]

ICTE Jason Davis

Supervisor, Operations Engineering

Southwest Power Pool 415 North McKinley Suite 140 Little Rock , Arkansas 72205-3020

(501) 614-3374 (501) 851-1784 Fx jdavis.re@ spp.org

Southern Hugh A. Francis

Principal Engineer Southern Company Services, Inc. 600 N. 18th Street MB PCC Birmingham, Alabama 35291

(205) 257-6027 hafranci@ southernco.com

RC-FRCC Jeff Gooding

Manager Training and Certification

Florida Power & Light Co. 4200 W. Flagler Street Miami, Florida 33134

(305) 442-2508 (305) 442-5221 Fx jeff_gooding@ fpl.com

FRCC Paul G. Graves

Lead Engineer Progress Energy 6565 38th Avenue North St. Petersburg, Florida 33710

(727) 384-7519 (728) 384-7865 Fx paul.graves@ pgnmail.com

IESO Hardeep Kandola

Section Head - Models & Data Independent Electricity System Operator Station A, Box 4474 Toronto, Ontario M5W 4E5

(905) 855-6205 (905) 855-6319 Fx hardeep.kandola@ ieso.ca

VACAR-S Alternate Michael G. Lowman

System Operator Duke Energy (EC02B) P.O. Box 1006 Charlotte, North Carolina 28201-1006

(704) 373-5195 michael.lowman@ duke-energy.com

RC-NPCC-NYISO David C. Mahlmann

Manager, Operations Engineering New York Independent System Operator 3890 Carman Road Schenectady, New York 12303

(518) 356-6101 (518) 356-9858 Fx dmahlmann@ nyiso.com

Attachment 1.l.1

July 29, 2011

76

TVA Roy Mathai Electrical Engineer, Power

Tennessee Valley Authority 1101 Market Street PCC 1-A Chattanooga, Tennessee 37402


RC-NPCC-ISONE Cheryl Mendrala

Principal Engineer ISO New England, Inc. One Sullivan Road Holyoke, Massachusetts 01040

(413) 535-4184 (413) 535-4399 Fx cmendrala@ iso-ne.com

HQT Maxime Nadeau

Engineer - Operations Hydro-Quebec TransEnergie 2 Complexe Desjardins Tour est - Centre Hydro - B1 Montreal, Quebec H5B 1H7

(514) 289-2211 ext. 4044 (514) 289-4556 Fx nadeau.maxime@ hydro.qc.ca

Southern Linda J. Smith

Operations Planning Engineer Sr. Southern Company Services, Inc. 600 N. 18th Street MB PCC Birmingham, Alabama 35291

(205) 257-4019 ljsmith@ southernco.com

NYISO Alternate Jeremiah Stevens

Engineer New York Independent System Operator 3980 Carmen Rd Schenectady, New York 12303

(518) 356-8709 (518) 356-9858 Fx jstevens@ nyiso.com

ICTE Brian Strickland

Senior System Operator Southwest Power Pool 415 North McKinley, Suite 140 Little Rock, Arkansas 72205

(501) 614-3507 bstrickland.re@ spp.org

RC-SERC-TVA Benjimin Taylor

Electrical Engineer Reliability Engineering

Tennessee Valley Authority 1101 Market Street Pcc 2-A Chattanooga, Tennessee 37402

4236974077 (423) 697-4025 Fx [email protected]

RC-MISO Raja Thappetaobula

Technical Manager (Real Time Operations)

Midwest ISO, Inc. 1797 hilo avenue n Oakdale, Minnesota 55128

6516328460 (651) 632-8417 Fx rthappetaobula@ midwestiso.org

RC-SPC Yong Zheng, P. Eng.

Network Management Engineer II SaskPower Grid Control Centre Highway #33 East Regina, Saskatchewan S4P 0S1

(306) 566-3119 (306) 566-3479 Fx yzheng@ saskpower.com

RC-IESO Alternate

Tim R. Babcock Senior Operations Officer

Independent Electricity System Operator Station A Box 4474 Toronto, Ontario M5W 4E5

(905) 855-6410 (905) 855-4188 Fx tim.babcock@ ieso.ca

PJM Alternate Michael Colby

Lead Engineer PJM Interconnection, L.L.C. 955 Jefferson Avenue Norristown, Pennsylvania 19403

(610) 666-4703 (610) 666-4286 Fx [email protected]

RC-PJM Alternate

David Hislop Reliability Engineer

PJM Interconnection, L.L.C. 955 Jefferson Ave Norristown, Pennsylvania 19403


July 29, 2011

77

RC-MISO Alternate

Tom Jones Manager, Central Regional Operations Engineering

Midwest ISO, Inc. 701 City Center Drive P.O. Box 4202 Carmel, Indiana 46082-4202

(317) 249-5802 tjones@ midwestiso.org

RC-VACAR-S Alternate

Wendy Ladd System Coordinator

Duke Energy Carolina 526 S. Church Street Mail Code EC02B Charlotte, North Carolina 28201-1006

(704) 382-6940 (704) 373-3500 Fx wendy.ladd@ duke-energy.com

MISO Alternate Cheng Luo

Transmission Utilization Engineer

Midwest ISO, Inc. P.O. Box Carmel, Indiana 46082-4202

(317) 249-5063 cluo@ midwestiso.org

Alternate Walter Omoth, P.Eng.

Supervisor, System Security & Performance

SaskPower Grid Control Centre Highway #33 East Regina, Saskatchewan S4P 0S1

(306) 566-3264 (306) 566-3479 Fx womoth@ saskpower.com

MISO Alternate Neil Shah

Lead - Transmission Utilization Midwest ISO, Inc.

(317) 249-5633 nshah@ midwestiso.org

SPP Alternate Jason Smith, PE

Supervisor, Operations Engineering Analysis/Support

Southwest Power Pool 415 North McKinley Suite 140 Plaza West Little Rock, Arkansas 72205-3020

(501) 614-3293 (501) 280-9446 Fx jsmith.re@ spp.org

NERC Staff Jordan Erwin

Administrative Assistant North American Electric Reliability Corporation 3353 Peachtree Road, N.E. Suite 600, North Tower Atlanta, Georgia 30326

(404) 446-2560 jordan.erwin@ nerc.net

Staff Coordinator Larry J Kezele

Manager of Operations North American Electric Reliability Corporation 116-390 Village Boulevard Princeton, New Jersey 08540-5721

(609) 524-7004 (609) 452-9550 Fx larry.kezele@ nerc.net

Interchange Distribution Calculator Working Group Conference Call Minutes July 18, 2011

2

Conference Call Summary

The Interchange Distribution Calculator Working Group discussed the following:

IDC Change Orders

1. CO‐320 Set PGEN for Base Loaded Units to Effective PMAX for NNL Chair Bahbaz explained that the NNL relief requirement is currently determined by the amount of online generation available to serve a particular load value submitted to SDX. All online generation is adjusted to meet this load value. The scaled value does not always represent the correct real time output for these units. Knowing that base loaded units are typically always at or close to PMAX, and that these units are flagged, thru setting MBASE to zero, to exempt them from participating in TDF calculations, a logic can be put in place to set the PGEN for these units for NNL purposes to the effective PMAX when appropriate. Implementation of CO‐320 changes the IDC logic for NNL allocation to set the SCALED PGEN for units with MBASE of 1.1 or less (=<1.1) to their effective PMAX. Effective PMAX should reflect any de‐rates or outages submitted for the units. The units may be scaled lower than the effective PMAX only if the total PMAX of units is greater than the load value submitted to SDX.

The working group approved CO‐320 for development at its March 2011 meeting. OATI completed development of CO‐320. Chair Bahbaz reported that SPP and ICTE tested the development of CO‐320; however, he requested that other working group members also test its development.

2. CO‐321 Data Interface for TLR CMR Report Data for SPP Chair Bahbaz explained that currently the NERC IDC Tool generates a Congestion Management Report (CMR) for every TLR issuance. This report is available through Graphical User Interface (GUI) and is available for manual user download in a Comma Separated Value (CSV) format. Implementation of CO‐321 would transfer all TLR data that is currently available through downloadable CSV format CMR automatically into the OATI webData for every confirmed TLR Level 3 or greater. The data would be sent for the entire TLR event once, after the TLR event is terminated and all curtailments and reloads associated with any of the TLR actions in the event are completed.

The working group approved CO‐321 for development, contingent upon resolution of an agreement between NERC and SPP regarding funding at its May 2011 meeting. The working group took no further action regarding CO‐321.


3

3. CO‐322 Generation Priority Submission Chair Bahbaz reviewed a draft of CO‐322. He explained that part of the Parallel Flow Visualization project is that entities are required to submit the MW output for each generator accompanied with the priority assigned to each MW. Currently, the priority is submitted in the same WebMethod as the generator MW output. There is a need for the flexibility to allow different entities to submit real MW output and the associated priority of the MW.

The working group approved CO‐322 for evaluation at its June 23, 2011 conference call. OATI has not yet evaluated CO‐322.

4. CO‐325 Changes to TLR Event History Display

Chair Bahbaz explained that currently the IDC’s TLR Event History display, which is used for post analysis, displays a summary of each TLR issuance on the specific flowgate. There are columns for data such as relief requested, remaining relief, relief provided, the number of tags curtailed, and the MW value of curtailments. He stated that this display includes “not required tags” and tags that have an outside restriction placed on them by balancing authorities that were not actually curtailed by the TLR. This can mislead IDC users. Implementation of CO‐325 modifies the TLR Event History display by deleting the requested relief column and changing the relief provided, tags cut, and MWs cut columns to the values in the row labeled “Required Tags”. OATI completed development of CO‐325. Vice Chair Watson will test the development of CO‐325 and report his findings at the working group’s next meeting.

5. CO‐326 Parallel Flow Visualization Metrics Chair Bahbaz reported that he will send out a revised draft of CO‐326 for working group comments.

6. CO‐328 Intra‐Hour Tag Curtailments Chair Bahbaz stated that currently the IDC only takes into consideration the profile value at the time of the effective TLR Time. If a tag has a profile of 0 MW at xx: 00 for TLR xA level but 100 MW xx: 15 thru xx+1:00, the TLR will consider the 0 MW for impact purpose and, therefore, it will not curtail the tag regardless of the priority. CO‐328 changes the method for which the impacts are captured to account for the profile changes of tags within the hour and assign a target MW for each tag.


4

In other words, CO‐328 modifies the IDC to look through the full profile of a tag. The IDC will consider highest value of the tag profile and consider that value for impact purposes. However, the IDC will consider the lowest value on the profile of the tag for “Relief Provided” purposes. Once the IDC calculates the maximum value at which the tag can flow, based on the maximum value of the tag profile, a target will be sent out for that tag. The working group approved CO‐328 for development at its June 23, 2011 meeting. Larry Kezele reported that before NERC approves development of CO‐328 the working group needs to prioritize its development.

7. CO‐329 Load Adjustment During TLR 5 Issuance Chair Bahbaz stated that during TLR level 5 NNL is allocated to each entity depending on their impact on the flowgates based on their generator impact. Balancing authority load is used for scaling the generators, which is used for calculating NNL on the flowgate. These balancing authority load values are uploaded to SDX. If no data is being uploaded to SDX, then the load value defaults to base case load, which are the seasonal loads. Using these base case loads can inflate the NNL relief allocated to the balancing authorities, especially during shoulder months.

CO‐329 allows for a balancing authority load adjustment for balancing authorities with potential NNL obligation (i.e., GLDF >5%) at the time of TLR 5 issuance. This provides the reliability coordinator the opportunity to correct and confirm the load within the IDC; much like the process of toggling generators on/off as needed as the time of TLR 5 issuance. This option shall also be implemented in the “STUDY TLR” application.

The working group approved CO‐329 for development at its June 23, 2011 meeting. Larry Kezele reported that before NERC approves development of CO‐329 the working group needs to prioritize its development.


1. CO‐10 Validate Temporary Flowgates in Book of Flowgates Larry Kezele reported that the DFWG approved BoF CO‐10 for development at its March 30, 2010 meeting and that the costs for developing the change order are included in NERC’s 2011 budget. Larry Kezele reported that NERC approved CO‐10 for development. Mohamad Yassin reported that CO‐10 is still in development. Chair Bahbaz, Brian Strickland, and Raja Thappetaobula will test the development of BoF CO‐10.


5

Other

1. Draft SMEE to Southern Change Order Hugh Francis explained that the South Mississippi Electric Power Association (SMEPA) is a registered balancing authority and load‐serving entity. SMEPA has load inside the boundaries of the balancing area and also in the Entergy balancing area (SMEE) and the Southern balancing area. The SMEPA load outside of the SMEPA balancing area is served through the use of e‐Tags. The SMEPA load in the Entergy balancing area (SMEE) was designated as a LSE only pseudo balancing authority in the IDC sometime in the past. This pseudo balancing authority is only used internal to the IDC. Special sink rules have already been established for SME‐EES transactions to be designated as serving SMEE load.

Chair Bahbaz and Hugh Francis discussed how to implement the required IDC model changes to model the SMEE pseudo balancing authority. The working group concluded that a change order is not required to implement the model changes.

2. Status of the Generation‐to‐Load Project (CO‐283) The working group discussed sending GTL data to the IDC production environment and open action items from the NAESB Business Practices Subcommittee. These items will be further discussed at the working August 2011 meeting.

3. GSF and GLDF Calculations

Chair Yasser reported that sporadically the IDC’s calculation of generator shift factors and generator‐to‐load distribution factors are incorrect. These factors are used in NNL calculations. OATI is archiving the GSF and GLDF matrices for further analysis and investigation.

4. Change Order Implementation OATI implemented IDC CO‐313, IDC CO‐324, IDC CO‐327, and webSDX CO‐07 into the IDC and webSDX production environments, respectively, on Wednesday, June 29, 2011 at 10 a.m. CDT.

AAddjjoouurrnnmmeenntt

The conference call meeting was adjourned at 3:04 p.m. EDT on July 18, 2011.


Attachment 1.l.2

IDC Working Group

[email protected] lyris list, dated August 12, 2011

Member Alcaraz Jose [email protected]

Member Babcock Timothy R. [email protected]

Member Bahbaz Yasser [email protected]

Member Brooks LaChelle D [email protected]

Member Colby Michael [email protected]

Member Davis Jason [email protected]

Member Erwin Jordan [email protected]

Member Francis Hugh A. [email protected]

Member Gooding Jeff [email protected]

Member Graves Paul G. [email protected]

Member Hislop David [email protected]

Member Jones Tom [email protected]

Member Kandola Hardeep [email protected]

Member Kezele Larry J [email protected]

Member Ladd Wendy T. [email protected]

Member Lowman Michael G. [email protected]

Member Luo Cheng [email protected]

Member Mahlmann David C. [email protected]

Member Mathai Roy [email protected]

Member Mendrala Cheryl [email protected]


Attachment 1.l.2

Member Nadeau Maxime [email protected]

Member Omoth Walter [email protected]

Member Shah Neil [email protected]

Member Smith Jason [email protected]

Member Smith Linda J. [email protected]

Member Stevens Jeremiah [email protected]

Member Strickland Brian [email protected]

Member Taylor Benjimin [email protected]

Member Thappetaobula Raja [email protected]

Member Watson Allan [email protected]

Member Zheng Yong [email protected]

Attachment 1.l.2

IDC Working Group













Member Jones Tom [email protected]










Attachment 1.l.2












Attachment 1.l.3

IDC Working Group



Member Allen Eric H. [email protected]



Member Becker Richard [email protected]

Member Beuning Stephen J. [email protected]

Member Bresler Frederick [email protected]


Member Busbin James Y. [email protected]

Member Cobb Richard Phillip [email protected]


Member Cummings Robert W. [email protected]




Member Garcia Armando [email protected]

Member Gonzalez-Perez Carlos [email protected]





Attachment 1.l.3

Member Howell Victor A. [email protected]

Member Jaleeli Nasser - [email protected]




Member Latimer Jim [email protected]

Member Lee Stephen T. [email protected]

Member Lemmons David F. [email protected]





Member McMahan Scott [email protected]


Member Mokhtari Sasan [email protected]

Member Morasco Rob [email protected]

Member Muller Nelson [email protected]


Member Nickell Lanny D. [email protected]

Member Nolan Brian M. [email protected]


Member Pettitt Bill [email protected]

Attachment 1.l.3

Member Reichenbach Donald E. [email protected]

Member Riley Jonathan [email protected]

Member Saini Narinder K. [email protected]

Member Scott Gordon L. [email protected]


Member Shanahan Patrick J. [email protected]

Member Skiba Ed [email protected]



Member Spila George [email protected]





Member Thomas Mark [email protected]

Member Uhrin James A [email protected]

Member Van Osdol Wayne [email protected]

Member Vermillion James [email protected]



Member Zwergel David T. [email protected]

[email protected]

Attachment 1.l.3

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

Attachment 1.l.3

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

Attachment 1.l.4

IDC Working Group



Member Becker Richard [email protected]

Member Busbin James Y. [email protected]



Member Jones Gary S. [email protected]


Member Morasco Rob [email protected]

Member Muller Nelson [email protected]

Member Nolan Brian M. [email protected]


Member Reichenbach Donald E. [email protected]

Member Rhodes Robert C. [email protected]

Member Riley Jonathan [email protected]

Member Shafeei Phillip F. [email protected]




[email protected]

[email protected]


nerc related files dl/idcwg_aug 24...%pdf-1.6 %âãÏÓ 8969 0 obj >stream hÞÄykoÛf...

Documents