Coordination Process for Reciprocal Coordinated Flowgates Sample Clauses

Coordination Process for Reciprocal Coordinated Flowgates. The Parties will establish and finalize the process and timing for exchanging their respective ATC/AFC calculations and Firm Flow calculations/allocations with respect to all RCFs. Further, the process will allocate Flowgate capacity on a future-looking basis, including the allocation of Firm and Non-Firm Capability for use in both internal dispatch and selling of transmission service. The Congestion Management Process sets forth the procedure for reciprocal coordination. For any Flowgate comprised of one or more controllable devices, the historically determined Firm Flow on the Flowgate and any allocated rights to that Flowgate under this process are subject to the operating practices of the controllable device. To the extent the controllable device is able to maintain scheduled flows, there are no parallel flows on the Flowgate and a historical allocation based on parallel flows will not occur. In this instance, the use of the Flowgate will be limited to entities that have arranged transmission service across the interface formed by the controllable device. To the extent the controllable device cannot maintain scheduled flows, there will be a historical allocation on the Flowgate based on parallel flows.
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Coordination Process for Reciprocal Coordinated Flowgates. The Parties will establish and finalize the process and timing for exchanging their respective ATC/AFC calculations and Firm Flow calculations/allocations with respect to all RCFs. Further, the process will allocate Flowgate capacity on a future-looking basis, including the allocation of Firm and Non-Firm Capability (Priority 7, 6, and 2) for use in both internal dispatch and selling of transmission service. The Congestion Management Process sets forth the procedure for reciprocal coordination. For any controllable Flowgate, the historically determined Firm Flow on the Flowgate and any allocated rights to that Flowgate under this process are subject to the operating practices of the controllable device. The operating practices of the controllable device will be made available to the MIDWEST ISO and PJM before a change is made. To the extent the controllable device is able to maintain the schedule across the controllable Flowgate, there are no parallel flows and a historical allocation based on parallel flows will not occur. In this instance, the use of the controllable Flowgate will be limited to entities that have arranged transmission service across the interface formed by the controllable device. To the extent the controllable device cannot maintain the schedule across the controllable Flowgate, there will be a historical allocation based on parallel flows.
Sample 1Sample 2
Coordination Process for Reciprocal Coordinated Flowgates. In order to coordinate congestion management proactively, each Party agrees to respect the other Party’s determinations of AFC/ATC and calculations of firmness for real- time operations. The Parties will establish and finalize the process and timing for exchanging enhancing their respective ATC/AFC calculations pursuant to the Congestion Management Process to be developedand Firm Flow calculations/allocations with respect to all RCFs. Further, the process will allocate Flowgate capacity on a future-looking basis, including the allocation of Firm and Non-Firm Capability for use in both internal dispatch and selling of transmission service. The Congestion Management Process will sets forth the procedure for reciprocal coordination. For any Flowgate comprised of one or more controllable devices, the historically determined Firm Flow on the Flowgate and any allocated rights to that Flowgate under this process are subject to the operating practices of the controllable device. To the extent the controllable device is able to maintain scheduled flows, there are no parallel flows on the Flowgate and a historical allocation based on parallel flows will not occur. In this instance, the use of the Flowgate will be limited to entities that have arranged transmission service across the interface formed by the controllable device. To the extent the controllable device cannot maintain scheduled flows, there will be a historical allocation on the Flowgate based on parallel flows.
Sample 1
Coordination Process for Reciprocal Coordinated Flowgates. The Parties will establish and finalize the process and timing for exchanging their respective ATC/AFC calculations and Firm Flow calculations/allocations with respect to all RCFs. Further, the process will allocate Flowgate capacity on a future-looking basis, including the allocation of Firm and Non-Firm Capability (Priority 7, 6, and
Sample 1

Related to Coordination Process for Reciprocal Coordinated Flowgates

  • Donor Coordination Throughout the multi-year development of the Compact, MCC and the Government have engaged in an inclusive process that included consultations with the United States Government, Nepali communities and key private sector actors, non-government actors, and other donors as well as multilateral organizations. In particular, MCC worked closely with the World Bank and the Asian Development Bank in reviewing and agreeing on various power sector reforms required in Nepal for future programming by the two banks. MCC also consulted frequently with the United Kingdom’s Department for International Development (“DFID”) during its preparation of a political economy analysis of power sector reform.

  • General Coordination 5.1.1 Contractor’s Pre-Construction Phase Services team shall attend Project Team meetings with Owner, Owner representatives, and A/E at regularly scheduled intervals throughout the Pre-Construction Phase. Frequent Project Team meetings are anticipated prior to Owner acceptance of the GMP and during completion of the Construction Documents.

  • 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 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.

  • Cooperation and Coordination The Parties acknowledge and agree that it is their mutual objective and intent to minimize, to the extent feasible and legal, taxes payable with respect to their collaborative efforts under this Agreement and that they shall use all commercially reasonable efforts to cooperate and coordinate with each other to achieve such objective.

  • 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.8). All coordinators are required to maintain current At-Sea Monitor Certification. Ensure that all key personnel attend any refresher trainings for At-Sea Monitors. For a specific job description see Section J, Attachment 2, Labor Category Classifications and Job Descriptions.

  • Technical Cooperation 1. The Parties shall strengthen their cooperation in the field of standards, technical regulations, metrology, market surveillance, accreditation and conformity assessment systems with a view to increasing the mutual understanding of their respective systems and facilitating access to their respective markets. To that end, they may establish regulatory dialogues at both horizontal and sectoral levels.

  • Scheduling Coordinator Buyer shall act as the Scheduling Coordinator for the Project. In that regard, Buyer and Seller shall agree to the following:

  • Program Coordinator An individual designated by the program director to assist the program director in managing Match activities.

  • Utility Coordination Identify all potential utility conflicts and provide preliminary office check plans showing the problem locations, posted to the City’s FTP site. Plans will clearly identify specific utility company facilities by color and by name (i.e. not just “gas” or “fiber optic”). ENGINEER shall include a conflict list for each utility, also posted to the FTP site. ENGINEER shall meet with utility company representatives to review plans and utility verification forms (Attachment No. 3 to Exhibit “A”) at each milestone date and as directed by the CITY and as determined necessary by the ENGINEER. This in- formation will be compiled into a summary report (Attachment No. 4 to Exhibit “A” also available on the City’s FTP site) maintained and updated by ENGINEER as necessary to present a cohesive and reflective status of utilities, and provided to the City as necessary. ENGINEER shall maintain involvement with utility companies until all conflicts have been resolved (not just identified). When appropriate, the City Engineer will approve the identification on plans of conflicts to be resolved during construction. ENGINEER shall meet with involved utility company/ies and project contractor to resolve any conflicts with utilities that occur during construction.

Time is Money Join Law Insider Premium to draft better contracts faster.