《. The Functional Model and Market Structures - NERC》由会员分享，可在线阅读，更多相关《. The Functional Model and Market Structures - NERC（117页珍藏版）》请在三一文库上搜索。
1、NERC Reliability Functional Model Technical Document Version 5NERC Reliability Functional Model Technical DocumentVersion 45This document is a companion to Version 54 of the Functional Model. It provides context, explanations, opinions, and discussions on various aspects of the Functional Model. App
2、roved by Standing Committees: September 10-11,This is Version 5 REDLINE 2009 06 09 as further revised by MY 2009 06 13(2) version of May 25, 2009 builds on Functional ModelTechnical Dec 4, 2007 - post-call) Changes made on call to p 4, 5, 6, 9, 30Approved by Standards Committee: NOTES agreed to do a
3、 planning roll-up - do in planning discussion section?September 22,Prepared by the Functional Model Working GroupJuneSeptember 20098- 117 -Table of ContentsNERC Reliability Functional Model Technical Document1Table of Contents2Introduction64Section I Entity Tasks and Interrelationships751.Reliabilit
4、y Coordinator962.Balancing Authority1183.Planning Coordinator13104.Transmission Planner14115.Resource Planner18146.Transmission Operator20167.Interchange Coordinator23198.Transmission Service Provider31239.Transmission Owner322410.Distribution Provider332511.Generator Operator342612.Generator Owner3
5、52713.Purchasing-Selling Entity362814.Load-Serving Entity372915.Compliance Enforcement Authority383016.Standards Developer393117.Market Operator (Resource Integrator)403218.Reliability Assurer4133Section II Technical Discussions42341.General Clarifications of the Functional Model43352.Reliability St
6、andards48393.Market Operations (Resource Integration)50404.The Functional Model and Market Structures54445.Providing and Deploying Ancillary and Reliability-Related Services56466.Managing Bilateral Interchange Transactions Basic Concepts59487.Managing Bilateral Interchange Scheduling Agents62518.Non
7、-coincident Resource Integrator and Balancing Authority Areas63529.Implementing the Interchange Coordinator665410.Distribution Provider as Load-Serving Entity705711.Planning Functions755912.Terminology Changes in Version 5796213.Reliability Areas and Boundaries977113.Generating versus Transmission A
8、ssets1027514.Roles in Load Curtailment1037615.History of Revisions10679NERC Reliability Functional Model Technical Document1Table of Contents2IntroductionSection 1 Entity Tasks and Interrelationships4Section I Entity Responsibilities and Interrelationships1.Reliability Coordinator51.Reliability Coor
9、dinator2.Balancing Authority723.Planning Coordinator93.Balancing Authority4.Transmission Planner1045.Resource Planner1156.Transmission Operator1367.Interchange AuthorityCoordinator1478.Transmission Planner1689.Transmission Service Provider18910.Transmission Owner191011.Distribution Provider201112.Ge
10、nerator Operator211213.Generator Owner221314.Purchasing-Selling Entity231415.Load-Serving Entity241516.Compliance Enforcement AuthorityMonitor251617.Standards Developer261718.Market Operator (Resource Integrator)271819.Reliability Assurer28Section II2 Technical Discussions291.General Clarifications
11、of the Functional Model302.Reliability Standards323.Market Operations (Resource Integrator)334.The Functional Model and Market Structures355.Providing and Deploying Ancillary and Reliability-RelatedInterconnected Operations Services376.Managing Bilateral Interchange Transactions Basic Concepts397.Ma
12、naging Bilateral Interchange Transactions Scheduling Agents418.Non-coincident Resource Integrator and Balancing Authority Areas429.Implementing the Interchange AuthorityCoordinator Functional Entity4310.Task Assignment Options10.Distribution Provider as Load-Serving Entity4411.Planning Functions11.D
13、emand Response Providers4612.Reliability Areas and Boundaries12.Planning Functions4813.Generating versus Transmission Assets13.Terminology Changes in Version 55114.Roles in Load Curtailment14.Reliability Areas and Boundaries60611513.History of Revisions6465NERC Reliability Functional Model Technical
14、 Document1Table of Contents2Section 1 Entity Responsibilities and Interrelationships341.Reliability Coordinator352.Balancing Authority373.Resource Planner394.Transmission Operator3115.Interchange AuthorityInterchange Coordinator3136.Transmission Planner3157.Transmission Service Provider3178.Transmis
15、sion Owner3189.Distribution Provider31910.Generator Operator32011.Generator Owner32112.Purchasing-Selling Entity32213.Load-Serving Entity32314.Compliance Monitor32415.Standards Developer32516.Market Operator (Resource Integrator)32617.Reliability Assurer327Section 2 Technical Discussions3281.General
16、 Clarifications of the Functional Model3292.Reliability Standards3323.Market Operations (Resource Integrator)3334.The Functional Model and Market Structures3355.Providing and Deploying Ancillary and Reliability-Related Services3376.Managing Bilateral Interchange Transactions Basic Concepts3397.Manag
17、ing Bilateral Interchange Transactions Scheduling Agents3418.Non-coincident Resource Integrator and Balancing Authority Areas3429.Implementing the Interchange AuthorityInterchange Coordinator Function34310.Task Assignment Options34411.Planning Functions34612.Reliability Areas and Boundaries34913.His
18、tory of Revisions353IntroductionThis document is intended as a companion to Version 45 of the Functional Model tothat will help the reader better understand the Models Functions, fFunctionalResponsible eEntities and their relationships. It is also intended to explain the changes made to Version 34 o
19、f the Model. A new version of the Technical Document was not issued with Version 4 of the Functional Model. As a result, the present document also addresses changes made in Version 4 of the Model that have been retained in Version 5. This document therefore provides context, explanation and opinions
20、. It is a companion to, rather than a formal part of, Version 5 of the Model. A new version of the Technical Document was not issued with Version 4 of the Functional Model. As a result, the present document also addresses changes made in Version 4 of the Model that have been retained in Version 5. S
21、ection I1 provides details about each of the Responsible Entities. Some entities, such as the Transmission Owner or Purchasing-Selling Entity, are adequately described in the Functional Model document, and there is little detail to add here. Others, such as the Interchange AuthorityAuthorityIntercha
22、nge Coordinator and Balancing Authority, are more complex both unto themselves and in their relationship with other entities, and this document provides additional explanations. Section II2 includes technical discussions on related topics and tasks such as managing Arrangedbilateral and Confirmed In
23、terchange Transactions, and functional entity Confirmed Interchange Schedules, task assignment and delegation, the planning functions, and boundary conditions. . Many of these topics are mentioned in the Functional Model, but the details may not be obvious. The discussion of Market OperationsStructu
24、res addresses illustrates the various types of markets and pools, and concludes that the Model applies to is not dependent on any particular different market structures. or pool “depth.” There is also discussion of a number of the concepts related to the Functional Model. of a scheduling agent, as w
25、ell as discussion of the relationship of the Market Operator and Balancing Authority, under both bid-based and cost-based dispatch of resources. In addition, certain concepts and conclusions from the 2005 report of the Functional Model Reliability Standards Coordination Task Force (FMRSCTF) are also
26、 discussed. This includes the implementation of the Reliability Coordinator and Interchange Coordinator entities in standards; Regional Reliability Plans, and Responsible Entity Areas and boundaries. Final report is dated March 11, 2005. See ftp:/ note: A Technical Document with V4 of the FM was iss
27、ued. Both footnotes should be deleted.Section I1 Entity TasksResponsibilities and InterrelationshipsThis section describes theVersion 4 of the Model, issued in 2008, clarified the concept of responsibility in the Model, as reflected in the use of the term Responsible Entity. In particular, it was cl
28、arified that while there were responsibilities of the entities in the Functional Model within the context of the Model itself. It is important to recognize that , the responsibilities that will actually apply to an organization will be determined within NERCs registration, certification and complian
29、ce processes and NERCs Reliability SStandardsSstandards, not by the Model. The Model describes a somewhat conceptualized state in which responsibility However, it subsequently became apparent to the Functional Model Working Group that having two different contexts for closely related Tasks are infer
30、red to be assigned to a single organization, avoidingresponsibility did not completely eliminate the potential complexity and ambiguity that could result from responsibility for these Tasks being split between two or more organizations. The situation described in the conceptualized state of the Mode
31、l will not always be achieved in actuality, because of factors related to particular organizational structures and relationshipsfor confusion. On this basis, Version 5 goes one step further and eliminates reference to responsibility within the Model, regulatory and legal requirements. Addressing how
32、 such factors will impactreplacing the term responsible entity with the term functional entity. In Version 5 of the Model, an entity is defined by the functions Tasks it is responsible for performings, not by the responsibilities isit has. In Version 5 of the Model, the Functional Model Working grou
33、p recommends usesing the term functional entity to apply to the entity given in the Functional Model (Balancing Authority, etc.). It is proposed that other NERC documents follow this usage, and also that they useing the terms registered entity, certified entity and responsible entity, in reference t
34、o specific organizations. For example, PJM is a registered entity and certified entity for the Balancing Authority functional entity.As a result of refocusing the jobModel on Tasks rather than responsibility, Version 5 of the Technical Document has removed discussions associated with responsibility
35、of individual organizations. These matters are now addressed within the context of NERCs registration, certification and compliance programs, typically within NERCs Rules of Procedure. These include situations where: an organizations may bundle a number of different functions and registerreliability
36、 as the corresponding functional entities, for example Reliability Coordinator and Transmission Operatortwo or more organizations may register jointly with NERC as functional entities and thereby divide or share responsibility for meeting standards. requirements (Joint Registry Organizations) an org
37、anization may register and assume responsibility for Tasks performed by others, such as a rural cooperative on behalf of its members.The Model provides a framework and guidelines, it does not specify responsibilities or requirements.conceptualized in which. are inferred to be assignedmentthe that co
38、uld result from responsibility for these Tasks being split between The situation described in the conceptualizedof in actuality1. Reliability CoordinatorThe Reliability Coordinators purview must be broad enough to enable it to calculate Interconnection Reliability Operating Limits, which will involv
39、e system and facility operating parameters beyond its own Area as well as within it. This is in contrast to the Transmission Operator, which also maintains reliability, but is directly concerned with system parameters within its own Area.The Reliability Coordinator is the highest operating authority
40、; the underlying premise is that reliability of a wide-area takes precedence over reliability of any single local area. Only the Reliability Coordinator hashasis required to have the perspective/vision necessary to act in the interest of wide-area reliability. The Reliability Coordinator also assist
41、s the Transmission Operator in relieving equipment or facility overloads through transmission loading relief measures if market-based dispatch procedures are not effective.Role in Interchange Transactions. The Reliability Coordinator does not receive tags, but on may curtaildeny Interchange Transact
42、ions until they are arranged and ready for implementation as Interchange Schedules. As such, it does not approve or deny tags. However, once the Reliability Coordinator receives the Interchange Schedule information, it will have the necessary informationTTransactions with respect to aid its assessme
43、nt of the impacts of flowing and impending Transaction Schedules on its areas reliability. As necessary, the Reliability Coordinator may issue transmission loading relief requests (or similar requests for congestion management) which may result in reducing, removing or halting flowing or impending I
44、nterchange Transactions. This is viewed by some as “denying” the Interchange Transactions although in this context, the “denialreliability and provides its denial” is not provided during the collection of approval stage. Bens response to Mikes comment: it is OK to mention interchange schedules here.
45、 We dont really need to stick with Arranged Interchange and Confirmed Interchange only. to the Interchange AuthorityInterchange Coordinator.Day-ahead analysis. The Reliability Coordinator will receive the dispatch plans from the Balancing Authority on a day-ahead basis. The Reliability Coordinator w
46、ill then analyze the dispatch from a transmission reliability perspective. If the Reliability Coordinator determines that the Balancing Authoritys dispatch plans will jeopardize transmission reliability, the Reliability Coordinator will work with the Balancing Authority to determine where the dispat
47、ch plans need to be adjusted. The Reliability Coordinator obtains generation and transmission maintenance schedules from Generator Operators and Transmission Operators. The Reliability Coordinator can deny a transmission outage request if a transmission system reliability constraint would be violated.The Transmission Operator is responsible for the reliability of its “local” transmission system in accordance with maintaining System O