M2M Coordination Processes Sample Clauses

M2M Coordination Processes. The fundamental philosophy of the M2M coordination processes that are set forth in the attached Market-to-Market Coordination Schedule is to allow any transmission constraints that are significantly impacted by generation dispatch changes in both the NYISO and PJM markets or by the operation of the NY-NJ PARs to be jointly managed in the real-time security- constrained economic dispatch models of both Parties. This joint real-time management of transmission constraints near the market borders will provide a more efficient and lower cost transmission congestion management solution and coordinated pricing at the market boundaries. Under normal system operating conditions, the Parties utilize the M2M coordination processes on defined Flowgates that experience congestion. The goal of redispatch coordination at M2M Redispatch Flowgates and Other Coordinated Flowgates is to utilize the more cost effective generation between the two markets to manage the congestion in accordance with Section 7.1 of the attached Market-to-Market Coordination Schedule. The goal of NY-NJ PAR coordination is to operate the NY-NJ PARs to efficiently manage the congestion in accordance with Section 7.2 of the attached Market-to-Market Coordination Schedule. NY-NJ PAR coordination can occur at any Flowgate and need not be formally invoked by either Party. It is ordinarily in effect. The M2M coordination process include settlement rules that apply when M2M coordination is occurring.
Sample 1Sample 2Sample 3See All (34)
AutoNDA by SimpleDocs
M2M Coordination Processes. The fundamental philosophy of the M2M transmission congestion coordination processes that is are set forth in the attached Market-to-Market Coordination Schedule is to allow any transmission constraints that are significantly impacted by generation dispatch changes in both the NYISO and PJM markets or by the operation of the NY-NJ PARs to be jointly managed in the real-time security-constrained economic dispatch models of both Parties. This joint real-time management of transmission constraints near the market borders will provide a more efficient and lower cost transmission congestion management solution and coordinated pricing at the market boundaries. Under normal system operating conditions, the Parties utilize the M2M coordination processes on defined M2M Flowgates that experience congestion. The Party that is responsible for monitoring a M2M Flowgate will initiate and terminate the redispatch component of the M2M coordination process. The Party that is responsible for monitoring a M2M Flowgate is expected to bind that Flowgate when it becomes congested, and to initiate market-to-market redispatch The goal of redispatch coordination at M2M Redispatch Flowgates and Other Coordinated Flowgates is to utilize the more cost effective generation between the two markets to manage the congestion in accordance with Section 7.1.2 of the attached Market-to-Market Coordination Schedule. The goal of NY-NJ PAR coordination is to operate the NY-NJ PARs to efficiently manage the congestion in accordance with Section 7.2 of the attached Market-to- Market Coordination Schedule. NY-NJ PAR coordination can occur at any Flowgate and need not be formally invoked by either Party. It is ordinarily in effect. The M2M coordination processes includes a settlement process rules that applies apply when M2M coordination is occurring.
Sample 1Sample 2

Related to M2M Coordination Processes

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

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

  • Care Coordination The Parties’ subcontract shall require that the Enrollee’s CP Care Coordinator provide ongoing care coordination support to the Enrollee in coordination with the Enrollee’s PCP and other providers as set forth in Section 2.6.

  • Program Coordinator Each program may designate a program coordinator to assist with the matching processes. The program coordinator:

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

  • Operation and Coordination The ISO shall direct the operation of, coordinate the maintenance scheduling of, and coordinate the planning of certain facilities of the NYS Power System, including coordination with the control center(s) maintained by or on behalf of the NTO, in accordance with the Reliability Rules and all other applicable reliability rules, standards and criteria, as follows:

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

  • Evaluation Process A. The immediate supervisor will meet with an employee at the start of the employee’s probationary, trial services, transition, and annual review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory.

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