Forward Coordination Processes Sample Clauses

Forward Coordination Processes. For each Reciprocal Coordinated Flowgate, a manager and an owner will be defined. The manager will be responsible for all calculations regarding that Flowgate; the owner will define the set of point-to-point reservations to be utilized when determining point-to-point impacts on that Flowgate.
Sample 1
AutoNDA by SimpleDocs
Forward Coordination Processes. 1. For each Reciprocal Coordinated Flowgate, a managing entity and an owning entity will be defined. The manager will be responsible for all calculations regarding that Flowgate; the owner will define the set of Firm Transmission Service reservations to be utilized when determining Firm Transmission Service impacts on that Flowgate. 2. Managing entities will calculate both Historic Firm Gen-to-Load Flow impacts and historic Firm Transmission Service impacts for all entities. These impacts will be used to define the Historic Ratio and the Allocation of transmission capability. 3. The managing entity will utilize the current NERC IDC Base Case (or other mutually agreeable base case) to determine impacts. The case should be updated with the most current set of outage data for the time period being calculated. 4. Managing entities will calculate Allocations on the following schedule: Allocation Run Type Allocation Process Start Range Allocated Allocation Process Complete April Seasonal Firm Every April 1 at 8:00 EST Twelve monthly values from October 1 of the current year through September 30 of the next year April 1 at 12:00 EST October Seasonal Firm Every October 1 at 8:00 EST Twelve monthly values from April 1 of next year through March 31 of the following year October 1 at 12:00 EST Monthly Firm Every month on the second day of the month at 8:00 EST Six monthly values for the next six successive months 2nd of the month at 12:00 EST Weekly Firm Every Monday at 8:00 EST Seven daily values for the next Monday through Sunday Monday at 12:00 EST Two-Day Ahead Firm Every Day at 17:00 EST One daily value for the day after tomorrow Current Day at 18:00 EST Day Ahead Non-Firm Every Day at 8:00 EST Twenty-four hourly values for the next 24- hour period (Next Day HE1-HE24 EST) Current Day at 9:00 EST 5. Historic Ratios are defined during the seasonal runs the first time an impact is calculated. For example, the 2004 April seasonal firm run would define the Historic Ratio for April 2005 – September 2005 (October through March would have been calculated during the 2003 October seasonal firm run). The Historic Ratio is based on the total impacts of the Reciprocal Entity on the Flowgate (Historic Firm Gen-to-Load Flows and historic Firm Transmission Service flows, down to 0%) relative to the total impacts of all other Reciprocal Entities’ impacts on the Flowgate. For example, if Reciprocal Entity A had a 30 MW impact on the Flowgate and Reciprocal Entity B had a 70 MW im...
Sample 1
Forward Coordination Processes. 1. For each Reciprocal Coordinated Flowgate, a manager and an owner will be defined. The manager will be responsible for all calculations regarding that Flowgate; the owner will define the set of point-to-point reservations to be utilized when determining point-to-point impacts on that Flowgate. 2. Managing entities will calculate both historic Gen-to-Load Firm Impacts and historic Point-to-Point Firm Impacts for all entities. These impacts will be used to define the Historic Ratio and the Allocation of transmission capability. 3. The managing entity will utilize the current NERC IDC Base Case (or other mutually agreeable Base Case) to determine impacts. The case should be transformed with the most current set of outage data for the time period being calculated. 4. Managing entities will calculate Allocations on the following schedule: Allocation Run Type Allocation Process Start Range Allocated Allocation Process Complete
Sample 1

Related to Forward Coordination Processes

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

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

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

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

  • Order Coordination and Order Coordination-Time Specific 2.1.9.1 “Order Coordination” (OC) allows BellSouth and Lightyear to coordinate the installation of the SL2 Loops, Unbundled Digital Loops (UDL) and other Loops where OC may be purchased as an option, to Lightyear’s facilities to limit end user service outage. OC is available when the Loop is provisioned over an existing circuit that is currently providing service to the end user. OC for physical conversions will be scheduled at BellSouth’s discretion during normal working hours on the committed due date. OC shall be provided in accordance with the chart set forth below. 2.1.9.2 “Order Coordination – Time Specific” (OC-TS) allows Lightyear to order a specific time for OC to take place. BellSouth will make every effort to accommodate Lightyear’s specific conversion time request. However, BellSouth reserves the right to negotiate with Lightyear a conversion time based on load and appointment control when necessary. This OC-TS is a chargeable option for all Loops except Unbundled Copper Loops (UCL) and Universal Digital Channel (UDC), and is billed in addition to the OC charge. Lightyear may specify a time between 9:00 a.m. and 4:00 p.m. (location time) Monday through Friday (excluding holidays). If Lightyear specifies a time outside this window, or selects a time or quantity of Loops that requires BellSouth technicians to work outside normal work hours, overtime charges will apply in addition to the OC and OC-TS charges. Overtime charges will be applied based on the amount of overtime worked and in accordance with the rates established in the Access Services Tariff, Section E13.2, for each state. The OC-TS charges for an order due on the same day at the same location will be applied on a per Local Service Request (LSR) basis.

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their 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. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

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

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