Contract Renewal State may renew this Contract under its then-existing terms and conditions (subject to potential cost adjustments described below in section 2) in one (1)-year intervals, or any interval that is advantageous to State. This Contract, including any renewals, may not exceed a total of seven (7) years.
Renegotiation The contract may be renegotiated at any time by the parties, based upon appropriate and reasonable changes in circumstances upon which the original terms of the contract were based.
Modification or Renegotiation This agreement may be modified only by written agreement signed by the parties hereto. The parties agree to renegotiate the agreement if federal and/or state revisions of any applicable laws or regulations make changes in this agreement necessary.
CONTRACT RENEWAL PERIOD FURNITURE ADDITIONS/DELETIONS: Contractors wishing to make furniture additions/changes to their contract during the contract period should be aware of the following additions/changes will be allowed only once during a contract period. No changes to discount percentages are allowed during this contract period. Additions/changes must be submitted during the contract renewal period. When requesting additions and/or changes; contractor shall submit a request either by letter or via email which shall include a list of all items being proposed for addition and/or change. Contractor shall submit all required documents supporting any new items. Product literature for all new items shall also be submitted with the request. Contractor is responsible for submitting a complete name, address, email address, phone and fax numbers when a new dealer is added.
Contract Review Agent shall have reviewed all material contracts of Borrowers including, without limitation, leases, union contracts, labor contracts, vendor supply contracts, license agreements and distributorship agreements and such contracts and agreements shall be satisfactory in all respects to Agent;
Contract Revisions Notwithstanding Contract Exhibit C, Special Contract Conditions section 6.9, the following types of revisions can be made to the Contract without a formal Contract amendment, upon written notice: Revisions by the Contractor: 1) Contractor’s Information and Contacts 2) Contractor’s Contract Manager Revisions by the Department: 1) Department’s Contract Manager 2) Department’s Quarterly Sales Report (Contract Exhibit J) 3) Contractor Performance Survey (Contract Exhibit I) Contract Exhibit C, Special Contract Conditions section 6.9, applies to all other modifications to the Contract.
Contract Extension The City may, in its sole discretion, unilaterally exercise an option to extend the Contract as described in the Contract Documents. In addition, the City may, in its sole discretion, unilaterally extend the Contract on a month-to-month basis following contract expiration if authorized under Charter section 99 and the Contract Documents. Contractor shall not increase its pricing in excess of the percentage increase described in the Contract.
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).
NEGOTIATION PROCEDURE 3.1 On or before September 1 of the prior year in which this agreement is to expire either party may initiate negotiations in accordance with RSA 273:A. The parties shall meet not later than September 15th, at which time the Association shall submit its proposals, unless another date is mutually agreed to by the parties. 3.2 The Negotiating Committee of the Board and the Negotiating Committee of the Association shall have authority to reach a complete agreement, subject to ratification by the Board and the qualified voting members of the Association covered by this Agreement. 3.3 Any agreement reached shall be reduced to writing and signed by the Board and the Association. Any agreement reached which requires the expenditure of additional public funds for its implementation shall not be binding on the Board, unless and until the necessary appropriations have been made by the Annual School District Meeting. The Board shall make a good faith effort to secure the funds necessary to implement said agreements. 3.4 If, after discussion of all negotiable matters, the parties fail to reach agreement, either party may declare impasse. In the event of impasse, the rules and procedures for “Resolution of Disputes” as outlined under RSA 273: A-12 shall be followed. 3.5 The cost for the services of the mediator and/or fact finder including per diem expenses, if any, will be shared equally by the Board and the Association. 3.6 Determinations and/or recommendations under the provision of Section 3.4 of this Article III will not be binding on the parties in accordance with RSA 273: A 3.7 If the monies to fund the economic provisions are not appropriated as provided in this Article III, Section 3.3 and/or if either party rejects the recommendations set forth in this Article III, Section 3.6, then the parties shall do the following: A. The appropriate party shall notify the other party of its intent to renegotiate the provisions of this Agreement, and: B. If either negotiating team rejects the neutral party’s recommendations, his/her findings and recommendations shall be submitted to the full membership of the employee organization and to the Board of the public employer, which shall vote to accept or reject so much of his/her recommendations as is otherwise permitted by law. C. If either the full membership of the employee organization or the public employer rejects the neutral party’s recommendations, his/her findings and recommendations shall be submitted to the legislative body of the public employer, which shall vote to accept or reject so much of his/her recommendations as otherwise is permitted by law. D. If the impasse is not resolved following the action of the legislative body, negotiations shall be reopened. Mediation may be requested by either party and may involve the Board of the public employer if the mediator so chooses. 3.8 The parties may, by mutual agreement, pass over mediation and go directly to fact finding. 3.9 Neither party in any negotiations shall interfere with the selection of the negotiating or bargaining representatives of the other party.
Contract Work Contract work means capital project work within existing plant facilities, major maintenance and/or revamp work, plant modifications and/or shutdown work, minor maintenance and/or repair work, breakdown maintenance.