Negotiated Items Sample Clauses

Negotiated Items. The University and LUC–AAUP agree that superior and imaginative instruction in a supportive atmosphere is Xxxxxxx's best means for giving its students an outstanding educational experience. Learning cannot be taken for granted and, therefore, the University and LUC–AAUP agree to new procedures for determining effectiveness and efficiency in this joint educational enterprise, and to negotiate the impact of such new procedures on wages, hours, and other terms and conditions of employment.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Negotiated Items. 12.1. Any item not outlined in the Scope of Services may be subject to negotiations between the County and the successful Proposer. 12.2. After award of this proposal the County reserves the right to add or delete items/services at prices to be negotiated at the time of addition or deletion. 12.3. At contract renewal time(s) or in the event of significant industry wide market changes, the County may negotiate justified adjustments such as price, terms, etc., to this contract with the County, in its sole judgment, considers such adjustments to be in the best interest of the County.
Sample 1Sample 2Sample 3
Negotiated Items. Not applicable.
Sample 1Sample 2
Negotiated Items. All previously negotiated items within this Agreement shall remain in full force and effect unless altered during negotiations. The final Agreement shall supersede similar negotiated items from past negotiations.
Sample 1Sample 2
Negotiated Items. The University and LUC–AAUP agree that superior and imaginative instruction in a supportive atmosphere is Lincoln's best means for giving its students an outstanding educational experience. Learning cannot be taken for granted and, therefore, the University and LUC–AAUP agree to new procedures for determining effectiveness and efficiency in this joint educational enterprise, and to negotiate the impact of such new procedures on wages, hours, and other terms and conditions of employment.
Sample 1Sample 2
Negotiated Items. The Teams will negotiate terms and conditions of employment, compensation, hours, formulation of an agreement, and interpretation of existing agreement and in accordance with ND Century Code.
Sample 1Sample 2
Negotiated Items.  Avaya shall provide the Commonwealth a one-time discount of 100% off for the Network Monitoring Tool. The Commonwealth shall only be responsible for annual maintenance at 26.42% beginning after the first year of the contract. Avaya shall provide an installer for the implementation of the Network Monitoring Tool at no additional charge to the Commonwealth. The installer shall ensure that the tool is successfully implemented. Avaya shall also provide knowledge transfer/training on the Network Monitoring Tool.  Avaya shall provide the Commonwealth with a 58% discount off MSRP for all hardware and software products.  Avaya shall provide the Louisville Remote Data Center’s network equipment to include the 1st year of maintenance at a cost of $345,000. This price shall be valid twelve (12) months after the execution of the Contract.  Avaya shall provide a Maintenance Discount of 26.42% off MSRP for the 1st year annual maintenance paid quarterly.  Avaya shall provide a Maintenance Discount of 27% off MSRP for two (2) year paid upfront maintenance.  Avaya shall provide a Maintenance Discount of 31% off MSRP for three (3) – five
Sample 1
AutoNDA by SimpleDocs
Negotiated Items. The Commonwealth and Volta will finalize the Service Level Agreement (SLA) after contract award.
Sample 1
Negotiated Items. 12.1. Any item not outlined in the Scope of Work/Specifications may be subject to negotiations between the County and the successful Bidder. 12.2. After Award of this Bid, the County reserves the right to add or delete items/services at prices to be negotiated at the time of addition or deletion. 12.3. At contract renewal time(s) or in the event of significant industry wide market changes, the County may negotiate justified adjustments such as price, terms, etc., if in its sole judgment, the County considers such adjustments to be in their best interest.
Sample 1

Related to Negotiated Items

  • Disagreement Any dissension between the parties other than a grievance defined in the agreement and other than a dispute defined in the Labour Code.

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

  • Negotiated Agreement (1) This Settlement Agreement has been the subject of negotiations and discussions among the undersigned, each of which has been represented and advised by competent counsel, so that any statute, case law, or rule of interpretation or construction that would or might cause any provision to be construed against the drafter of this Settlement Agreement shall have no force and effect. The Parties further agree that the language contained in or not contained in previous drafts of this Settlement Agreement, or any agreement in principle, shall have no bearing upon the proper interpretation of this Settlement Agreement.

  • Excess Sales If the number or amount of Contract Securities attributable to an Underwriter pursuant to Section 4.1 hereof would exceed such Underwriter’s Original Underwriting Obligation reduced by the number or amount of Underwriters’ Securities sold by or on behalf of such Underwriter, such excess will not be attributed to such Underwriter, and such Underwriter will be regarded as having acted only as a Dealer with respect to, and will receive only the concession to Dealers on, such excess.

  • Engineering Support When requested by CLEC, CBT shall provide timely engineering support. CLEC shall pay CBT for the use of its engineering services at charges previously agreed to by CLEC.

  • Returned Items You are solely responsible for any Item for which you have been given provisional credit, and any such Item that is returned or rejected may be charged to your Account. You acknowledge that all credits received for deposits made through the Service are provisional, subject to verification and final settlement. Any Item that we return to you will be returned in the form of an Image or an IRD.

  • Excluded Items The following items are excluded from this sale:

  • Rejected Items; Abandonment (a) The Contractor may deliver, cause to be delivered, or, in any other way, bring or cause to be brought, to any State premises or other destination, Goods, as samples or otherwise, and other supplies, materials, equipment or other tangible personal property. The State may, by written notice and in accordance with the terms and conditions of the Contract, direct the Contractor to remove any or all such Goods (“the “Rejected Goods”) and any or all other supplies, materials, equipment or other tangible personal property (collectively, the “Contractor Property”) from and out of State premises and any other location which the State manages, leases or controls. The Contractor shall remove the Rejected Goods and the Contractor Property in accordance with the terms and conditions of the written notice. Failure to remove the Rejected Goods or the Contractor Property in accordance with the terms and conditions of the written notice shall mean, for itself and all Contractor Parties, that: (1) they have voluntarily, intentionally, unconditionally, unequivocally and absolutely abandoned and left unclaimed the Rejected Goods and Contractor Property and relinquished all ownership, title, licenses, rights, possession and interest of, in and to (collectively, “Title”) the Rejected Goods and Contractor Property with the specific and express intent of (A) terminating all of their Title to the Rejected Goods and Contractor Property, (B) vesting Title to the Rejected Goods and Contractor Property in the State of Connecticut and (C) not ever reclaiming Title or any future rights of any type in and to the Rejected Goods and Contractor Property; (2) there is no ignorance, inadvertence or unawareness to mitigate against the intent to abandon the Rejected Goods or Contractor Property; (3) they vest authority, without any further act required on their part or the State’s part, in the Client Agency and the State to use or dispose of the Rejected Goods and Contractor Property, in the State’s sole discretion, as if the Rejected Goods and Contractor Property were the State’s own property and in accordance with law, without incurring any liability or obligation to the Contractor or any other party; (4) if the State incurs any costs or expenses in connection with disposing of the Rejected Goods and Contractor Property, including, but not limited to, advertising, moving or storing the Rejected Goods and Contractor Property, auction and other activities, the State shall invoice the Contractor for all such cost and expenses and the Contractor shall reimburse the State no later than thirty (30) days after the date of invoice; and (5) they do remise, release and forever discharge the State and its employees, departments, commissions, boards, bureaus, agencies, instrumentalities or political subdivisions and their respective successors, heirs, executors and assigns (collectively, the “State and Its Agents”) of and from all Claims which they and their respective successors or assigns, jointly or severally, ever had, now have or will have against the State and Its Agents arising from the use or disposition of the Rejected Goods and Contractor Property. (b) The Contractor shall secure from each Contractor Party, such document or instrument as necessary or appropriate as will vest in the Contractor plenary authority to bind the Contractor Parties to the full extent necessary or appropriate to give full effect to all of the terms and conditions of this section. The Contractor shall provide, no later than fifteen (15) days after receiving a request from the State, such information as the State may require to evidence, in the State’s sole determination, compliance with this section.

  • Product Pricing Contract Prices are the sum of annual Base Prices and Quarterly fuel surcharges, as detailed below. Pricing for shipments each month should be based on the Contract Prices for the most recent quarter.

  • Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.

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