Coordinated Flowgates Sample Clauses

Coordinated Flowgates. An Operating Entity will conduct sensitivity studies to determine which Flowgates are significantly impacted by the flows of the Operating Entity’s Control Zones (historic Control Areas that existed in the IDC). An Operating Entity identifies these Flowgates by performing the following four studies to determine which Flowgates the Operating Entity will monitor and help control. A Flowgate passing any one of these studies will be considered a Coordinated Flowgate. Only AFC Flowgates will be eligible for consideration as Coordinated Flowgates. A Flowgate must have AFCs computed and these AFCs must be used to sell Transmission Service in order to be a Coordinated Flowgate. An Operating Entity may also specify additional Flowgates that have not passed any of the four studies to be Coordinated Flowgates. For Flowgates on which the Operating Entity expects to utilize the TLR process to protect system reliability, such specification is required. For a list of Coordinated Flowgates between Reciprocal Entities, please see each Reciprocal Entity’s Open Access Same-Time Information System (OASIS) website. Coordinated Flowgates are identified to determine which Flowgates an entity impacts significantly. This set of Flowgates may then be used in the congestion management processes and/or Reciprocal Operations defined in this document. When performing the four Flowgate studies, a 5% threshold will be applied on an absolute basis without regard to the positive or negative sign of the impact. Use of a 5% threshold in the studies may not capture all Flowgates that experience a significant impact due to market operations. The Operating Entities have agreed to adopt a lower threshold at the time NERC and/or NAESB implements the use of a lower threshold in the TLR process.
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Coordinated Flowgates. ‌ An Operating Entity will conduct sensitivity studies to determine which Flowgates are significantly impacted by the Market Flows of the Operating Entity’s Control Zones (currently the Control Areas that exist today in the IDC). An Operating Entity identifies these Flowgates by performing the following four studies to determine which Flowgates the Operating Entity will monitor and help control. A Flowgate passing any one of these studies will be considered a Coordinated Flowgate (CF). An Operating Entity may also specify additional Flowgates that have not passed any of the four studies to be Coordinated Flowgates. For Flowgates on which the Operating Entity expects to utilize the TLR process to protect system reliability, such specification is required. For a list of Coordinated Flowgates between SPP and MISO, please see Appendix C. Coordinated Flowgates are defined to determine which Flowgates an entity impacts significantly. This set of Flowgates may then be used in the Congestion Management processes and/or Reciprocal Operations defined in this document.
Sample 1
Coordinated Flowgates. 3.2.1 Flowgate Studies 3.2.2 Disputed Flowgates
Sample 1

Related to Coordinated Flowgates

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Coordination The Parties shall confer regularly to coordinate the planning, scheduling and performance of preventive and corrective maintenance on the Large Generating Facility and the Interconnection Facilities.

  • Project Management and Coordination The Engineer shall coordinate all subconsultant activity to include quality of and consistency of work and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Coordinators The contractor shall assign coordinators as needed to coordinate At-Sea Monitor deployment and provide At-Sea Monitor support services. The coordinator shall be designated as key personnel under this contract (per section H.

  • Classroom Management The certificated classroom teacher demonstrates in his/her performance a competent level of knowledge and skill in organizing the physical and human elements in the educational setting.

  • Project Coordination The Engineer shall coordinate all subconsultant activity to include quality and consistency of deliverables and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Block Trades; Other Coordinated Offerings 2.3.1 Notwithstanding any other provision of this Article 2, but subject to Sections 2.4 and 3.4, at any time and from time to time when an effective Registration Statement is on file with the Commission, if a Demanding Holder wishes to engage in (a) an underwritten registered offering not involving a “roadshow,” an offer commonly known as a “block trade” (a “Block Trade”) or (b) an “at the market” or similar registered offering through a broker, sales agent or distribution agent, whether as agent or principal, (an “Other Coordinated Offering”), in each case, with a total offering price reasonably expected to exceed, in the aggregate, $25 million, then if such Demanding Holder requires any assistance from the Company pursuant to this Section 2.3, such Holder shall notify the Company promptly of the Block Trade or Other Coordinated Offering at least five (5) business days prior to the day such offering is to commence and the Company shall use its commercially reasonable efforts to facilitate such Block Trade or Other Coordinated Offering; provided that the Demanding Holders representing a majority of the Registrable Securities wishing to engage in the Block Trade or Other Coordinated Offering shall use commercially reasonable efforts to work with the Company and any Underwriters or brokers, sales agents or placement agents (each, a “Financial Counterparty”) prior to making such request in order to facilitate preparation of the registration statement, prospectus and other offering documentation related to the Block Trade or Other Coordinated Offering. 2.3.2 Prior to the filing of the applicable “red xxxxxxx” prospectus or prospectus supplement used in connection with a Block Trade or Other Coordinated Offering, a majority-in interest of the Demanding Holders initiating such Block Trade or Other Coordinated Offering shall have the right to withdraw from such Block Trade or Other Coordinated Offering for any or no reason whatsoever upon written notification to the Company, the Underwriter or Underwriters (if any) and Financial Counterparty (if any) of their intention to withdraw from such Block Trade or Other Coordinated Offering. Notwithstanding anything to the contrary in this Agreement, the Company shall be responsible for the Registration Expenses incurred in connection with a Block Trade or Other Coordinated Offering prior to its withdrawal under this subsection 2.3.2. 2.3.3 Notwithstanding anything to the contrary in this Agreement, Section 2.2 shall not apply to a Block Trade or Other Coordinated Offering initiated by a Demanding Holder pursuant to Section 2.3 of this Agreement. 2.3.4 The Demanding Holder in a Block Trade or Other Coordinated Offering shall have the right to select the Underwriters and Financial Counterparty (if any) for such Block Trade or Other Coordinated Offering (in each case, which shall consist of one or more reputable nationally recognized investment banks). 2.3.5 A Demanding Holder in the aggregate may demand no more than four (4) Block Trades or Other Coordinated Offerings pursuant to this Section 2.3 in any twelve (12) month period. For the avoidance of doubt, any Block Trade or Other Coordinated Offering effected pursuant to this Section 2.3 shall not be counted as a demand for an Underwritten Offering pursuant to subsection 2.1.3 hereof.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!