North American Electric Reliability Council

Document Sample
North American Electric Reliability Council Powered By Docstoc
					                                   North American Electric Reliability Council
                               Princeton Forrestal Village, 116-390 Village Boulevard, Princeton, New Jersey 08540-5731

                                JOINT ENGINEERING COMMITTEE/OPERATING COMMITTEE

                                                           Le Château Frontenac Hotel
                                                          Québec City, Québec, Canada

                                                         July 8, 1997 — 8:15 to 10 a.m.


                                                       MINUTES OF THE MEETING


                     Engineering Committee Chairman Garey C. Rozier presided over the Joint Engineering Committee/
             Operating Committee (EC/OC) meeting held Tuesday, July 8, 1997 from 8:15 to 10 a.m. at Le Château
             Frontenac Hotel, Québec City, Québec, Canada. The meeting agenda is attached as Exhibit A.

                       Mr. Rozier asked the EC and OC members to respond and submit to the NERC staff in a timely fashion
             the requested meeting forms indicating their planned attendance at EC, OC, and Joint EC/OC meetings. These
             forms are critical to planning meeting facilities and luncheons without incurring unnecessary cost penalties in the
             contractual arrangements for the meetings.

              L. Terhune, Chairman of the Security Process Support System Task Force (SPSSTF), provided an
       Harry Security Process Support System Task Force
verview of the Task Force’s activities since it was approved by the OC in March 1997. The scope of the Task
orce focuses on the development of a transaction information system (TIS), an interchange distribution
alculator (IDC), and the proof of concept of a transmission reservation and scheduling (TRS) prototype.

        Mr. Terhune pointed out that these main scope objectives have been temporarily on hold while the Task
orce directed its efforts to several quick-start initiatives primarily in support of transmission loading relief
rocedures needed for 1997 summer. Self-directed SPSSTF work teams were instrumental in developing an
 terim IDC, a next-day information system (NDI), and an interim TIS. These teams will use the experience of
 ese quick-start initiatives as the basis for completing their assigned activities. A NERC symposium is being
 anned for September, which should help build consensus on an integrated system design for a transaction
 anagement system.

       Mr. Terhune also reported that the TRS work team was meeting later in July to begin the definition of a
 RS straw man and the specifications for a proof-of-concept prototype for the transmission reservation and
cheduling function based on actual flows as defined in the December 1996 report of the Transmission
 eservation and Scheduling Task Force. The proof-of-concept TRS prototype is expected to be operational at the
nd of 1998. Several Committee members suggested that the Task Force consider speeding up this proof-of-
oncept activity as implementation, if viable, will take additional time. Mr. Terhune’s presentations overheads are
 cluded as Exhibit B.




                                     Phone 609-452-8060 • Fax 609-452-9550 • URL www.nerc.com
Joint EC/OC Meeting Minutes
July 8, 1997


NERCnet

        Louis G. Leffler, NERC Project Manager, reported on the concept of a communications network that
would tie together all participants in the electric power industry to enable the commercial electricity business to be
conducted reliably and securely. For the time being, this concept is termed “NERCnet.” Mr. Leffler also briefly
described the components of NERCnet and the services that such a system could be capable of performing or
accommodating.

Interregional Security Network

         Bobby J. Mills, Chairman of the Telecommunications Working Group, reported that an interregional
security network (ISN) was being designed and was expected to be available by the end of 1997. Conceptually,
this ISN application may some day become a part of a larger NERCnet communications network mentioned
above. ISN will be capable of transferring near real-time system data from control area energy management
systems to data-receiving security coordinators. This data will be used to assess the status of the interconnected
electric systems. The initial data quantities for ISN have been defined and the first connections are expected to be
made in August.

        Mr. Mills reported that Intermedia Communications, Inc. (ICI) was selected as the vendor to implement
ISN. The contract is currently under review by TWG and NERC. ICI indicates that 60 days are required for the
ISN installation and that four nodes should be available by August 30. The remaining nodes should be up and
running by October 15, 1997.

Transaction Information System (“Tagging”)

        John W. Pope, Chairman of the Transaction Information System (TIS) Task Force, provided an update
on the TIS project. He reported that Operating Policy 3, developed by the Interconnected Operations Subcom-
mittee and approved by the Regions in May, describes the new “tagging” requirement for transactions, which is
the centerpiece of the TIS system.

         As the number of transactions across the transmission systems increases with open access to trans-
mission, the complexity and distances of transactions require that certain information be made available to system
operators and security coordinators so that they can reliably manage the facility loadings and security of the
networks. A method to kept track of all of this information has been proposed as a “tag” for each transaction.
Because of the urgent need for transaction information for the 1997 summer peak period, NERC has developed an
interim TIS system using a spreadsheet-based “tag” entry template and Internet e-mail to transport the tags
between the appropriate parties involved in a transaction. The highlights of this spreadsheet tagging template were
briefly reviewed by Mr. Leffler.

         Mr. Pope also reported that July 1 was the start-up date for implementation of the tagging system and
that seven days into the registration, only about 60% of the expected registrants have registered. As of July 24, all
users must use the NERC template, and security coordinators are to ensure that all transactions information is
provided to the interim IDC. As developed, the receivers of electric power have the responsibility to make sure the
tag data is complete and up to date. Tagging pertains currently to control area to control area transactions only.
The inclusion of interfaces or zones within a control area will eventually develop as the technology is enhanced.


                                                                                                                   2.
Joint EC/OC Meeting Minutes
July 8, 1997


        To date, NERC has sponsored five workshops to educate transmission users on the tagging process. Two
addition workshops are planned for July — one in Cincinnati, Ohio and the other in Denver, Colorado.

Due Process

        Donald M. Benjamin, NERC Director-Operations, presented the details of a proposed new process for
developing and approving NERC Policies and Standards for the Committee’s review and comment. This draft
process was developed by the NERC staff and the OC’s Interconnected Operations Subcommittee and is included
under Item 4 of the July 8, 1997 Joint EC/OC meeting agenda. This draft is intended to capture the key aspects of
the concept of a “due process” procedure approved by the NERC Board in May 1997.

         While both the OC and EC have had long-standing procedures for soliciting comments, reviewing, and
approving their Policies and Standards, some entities in the electric industry that are not afforded membership in
certain Regional Councils have objected to the way that these NERC Policies and Standards are developed and
approved.

         In May 1997, the NERC Board of Trustees approved the concept of a new “due process” procedure for
developing and approving NERC reliability Standards that will provide the opportunity for broad input from all
electric market participants and affected parties, and final approval of new or revised Standards by a two-thirds
majority vote of the NERC Board. The detailed of the “due process” procedure are slated for approval at the
September 1997 Board meeting.

        The EC and OC comments on the proposed “due process” procedure are included as Exhibit C. In
addition to these comments, follow-on comments from the separate July EC and OC meetings will be addressed
and developed into a revised draft “due process” procedure that will be presented to the Board for approval at its
September 1997 meeting.

Regional Highlights

          Several Regional Council reports were distributed at the meeting. Copies are available from the NERC
staff or the Regional Councils.

Adjournment

        There being no further business before the Committees, the Joint meeting was adjourned at 10 a.m.

Respectfully submitted,

Virginia C. Sulzberger
Virginia C. Sulzberger
Director-Engineering




                                                                                                                 3.
                                                                                                            Exhibit A




                   North American Electric Reliability Council
                 Princeton Forrestal Village, 116-390 Village Boulevard, Princeton, New Jersey 08540-5731




          JOINT ENGINEERING COMMITTEE/OPERATING COMMITTEE MEETING

                                            Le Château Frontenac Hotel
                                               Quebéc City, Québec

                                             July 8, 1997 — 8–10 a.m.
                                                      AGENDA


Introductions — Garey A. Rozier

 1.    Security Process Support System Task Force — Harry L. Terhune

*2.    NERCnet — Louis G. Leffler
       a. Interregional Security Network — Bobby J. Mills

*3.    Transaction Information System (“Tagging”) — John W. Pope and Colin L. Wright

*4.    Due Process — Donald M. Benjamin
                                          Exhibit B
NERC
         Security Process Support
            System Task Force

               Status Report
           NERC Joint Engineering/Operating
                 Committee Meeting



                     July 8, 1997




NERC
            Transmission Market &
            Security Initiatives
v   May 1996 -- Board approved ATC
    Reference Document and
    recommendations
v   Transmission Reservation and
    Scheduling Task Force (TRSTF) formed
    –   Conceptualized a TRS Process




                                                      1
NERC
            Transmission Market &
            Security Initiatives
v   January 1997 -- Board approved
    development of “proof of concept”
    prototype of the TRS Process proposed
    by TRSTF report
v   March 1997 -- Security Process Support
    System Task Force (SPSSTF) scope
    approved by Operating Committee




NERC        SPSSTF Scope

v Transaction    Information System
    (TIS)
v Interchange    Distribution Calculator
    (IDC)
v TRS    “proof of concept” prototype




                                             2
NERC
         SPSSTF Progress March
         - May 1997

v Main scope objectives temporarily
  on hold
v “Quick  Start” Initiatives -- In
  support of Transmission Loading
  Relief Procedures for 1997 summer




NERC     Quick Start Initiatives

v Interim Interchange Distribution
  Calculator (iIDC)
v Next-Day   Information system
  (NDI)
v InterimTransaction Information
  System (iTIS)




                                      3
NERC
        SPSSTF Self-Directed
        Work Teams
v TIS SDWT -- Transaction
  Information System
v IDC SDWT -- Interchange
  Distribution Calculator
v TRS SDWT -- Transmission
  Reservation and Scheduling
  Prototype




NERC
        Distribution Factor
        Task Force
v Created 1st. iIDC Distribution
  Factor Matrix (2.7 million elements)
v Monthly matrix updates for iIDC
v Defining procedure and
  requirements for weekly matrix
  updates
v Defining integration with IDC




                                         4
NERC      TIS SDWT

v Building    on experience from iTIS
v Defining    interfaces for integration
  with IDC
v TIS   Integration into NERCnet
   –   Defining communications
       requirements




NERC      IDC SDWT

v Defining functionality of multiple
  customer interfaces
v Building on experience from iIDC
v Defining interfaces for integration
  with TIS and IS
v IDC Integration into NERCnet
   –   Defining communications
       requirements




                                           5
NERC           IDC Modular Design

v IDC Security Process Module
   – Support Transmission Loading Relief
     (TLR)
       u Tabulate MW curtailment of specific
         transactions
       u Assess impacts of curtailment list/Modify

   –   Support Near Term Coordination of
       Operation
       u Flag transmission overloads from impending
         schedules
       u Day ahead/longer term security assessment
         and coordination




NERC
               IDC Security Process
               Module
                                Security
                                Assessment
                                Module              Alternative
           TLR Listing                              Study
            Module                                  Module




                     Operation               Impending
                     Coordination            Transaction
                     Module                  Module




                                                                  6
NERC          IDC Modular Design

v FLOBAT             Module
   –   Support Transmission Reservation and
       Scheduling using FLOBAT Concepts
        u   Identify “significantly affected” Flowgates
        u   Display MW reservation requirements for
            Flowgate ATCs
        u   Support transmission reservations and
            scheduling process (TRS to perform)




NERC          IDC FLOBAT Module
                Flowgate             Flowgate ATC
                Impact               Reservation
                Module               Module




                 Transaction   TRS       Approval
                 Study         Modules   Process
                 Module                  Module




                                                          7
NERC       TRS SDWT

v Defining  requirements of “proof-
  of-concept” prototype from TRSTF
  report -- Process, functions, etc.
v Defining interfaces for integration
  with TIS and IDC
v TRS Integration into NERCnet
    –   Defining communications
        requirements




NERC       TRS Strawman

v   SDWT meets July 15-16 in Chicago to begin
    definition of strawman and specification
v   iIDC and iTIS Learning Experiences of value
v   Compatibility with Existing Tariffs required
v   Must satisfy criteria at reliability “gates”
v   Flow above cutoff requires reservation or has
    lower priority than any reserved use




                                                    8
NERC      SPSSTF Activity

         NERC Transaction
v Preparing
  Management System Strawman




NERC
          NERC Transaction
          Management System
v Integration    of:
   –   Transaction Information System
   –   Security Information System (ISN)
   –   Interchange Distribution Calculator
   –   Transmission Reservation &
       Scheduling
   –   OASIS (Phase I and Phase II)
v NERCnet      Platform




                                             9
NERC      TMS Symposium

          -- NERC Transaction
v September
  Management Symposium
   –   In progress before announcement of
       FERC Technical Conference
   –   Involve ALL NERC groups (IOS, SCS,
       DEWG, TWG, ATCWG, etc.)
   –   Involve How Group & CPWG
   –   Build consensus on potential
       integrated system design




                                            10
                                                                                        Exhibit C

            EC/OC Comments on Proposed “Due Process” Procedure
                for Developing and Approving NERC Standards

                               (July 8, 1997 — EC/OC Meeting)


         (Views expressed by EC and OC members, not necessarily EC/OC agreements.)

P   NERC should canvass its mailing list as well as electric industry organizations to identify
    interested parties in Standards development.

P   NERC needs to clarify that Standards will be approved at meetings of the NERC Board of
    Trustees, as opposed to over the Internet.

P   Further clarification is needed to emphasize that the appeals process pertains only to appeals
    as to whether “due process” is being followed or not. The appeals process does not pertain to
    appeals or reconsiderations of technical merits or comments on the Standards.

P   Any “no” votes on proposed Standards should be accompanied by a text with specific
    language that would make the Standard(s) acceptable.

P   The proposed due process procedure as presented combines the management of the due
    process and the management of the Standards development. It may be more appropriate to
    have one committee manage the due process procedure and a second committee actually
    perform the Standards development.

P   The process needs to clarify whether voting on changes to a document will involve a vote on
    only the changes per se or on the whole document.

P   Comments on the Standards development can be on technical and equity issues.

P   The due process procedure is fundamentally flawed by the current makeup of the NERC
    Board of Trustees and the Standards Committee (Engineering Committee (EC) or Operating
    Committee (OC), as appropriate).

P   It should be clarified that a new Standard or a change in an existing Standard can be requested
    by any party (individual or organization).

P   Comments on the due process procedure from this Joint EC/OC meeting as well as any
    additional comments from the separate EC and OC meetings should be addressed with a new
    draft sent out to the EC and OC for further review and comment.

				
DOCUMENT INFO