DISAGREEMENT WITH REJECTION Sample Clauses

DISAGREEMENT WITH REJECTION. If I3 disagrees with NeoRx's determination that a shipment of Product does not meet the Product Specifications and Requirements, the parties will (i) replace the rejected dose(s) as soon as practicable, and then (ii) meet to review all relevant data to determine the cause of such rejection. The parties will make every reasonable effort to resolve the disagreement amicably. If the parties cannot resolve the disagreement, the parties will select a mutually agreeable outside consulting firm to review all applicable and pertinent information and data to determine the cause of the rejection. The party against whom the consulting firm rules shall bear all costs associated with the rejected dose(s) and the consulting firm. If both parties are deemed to share responsibility for the rejection, then such costs shall be allocated on a pro-rata share of the assigned blame. If the cause cannot be determined then each party shall pay 50% of the costs. I3 cannot be in breach of this Agreement because of an improper rejection or the inability to promptly supply replacement Product after an improper rejection.
Sample 1

Related to DISAGREEMENT WITH REJECTION

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

  • Termination with Notice Either the Director or the Company may terminate this Agreement by providing at least thirty (30) days prior written notice to the other party.

  • Disagreements Any dispute or other disagreement arising from or out of ------------- this Consulting Agreement shall be submitted to arbitration under the rules of the American Arbitration Association and the decision of the arbiter(s) shall be enforceable in any court having jurisdiction thereof. Arbitration shall occur only in San Diego, CA. The interpretation and the enforcement of this Agreement shall be governed by California Law as applied to residents of the State of California relating to contracts executed in and to be performed solely within the State of California. In the event any dispute is arbitrated, the prevailing Party (as determined by the arbiter(s)) shall be entitled to recover that Party's reasonable attorney's fees incurred (as determined by the arbiter(s)).

  • Dispute Notice If there is a dispute between the parties, then either party may give a notice to the other succinctly setting out the details of the dispute and stating that it is a dispute notice given under this clause 17.1.

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

  • Initiation; Confirmation; Termination (a) An agreement to enter into a Transaction may be made orally or in writing at the initiation of either Buyer or Seller. On the Purchase Date for the Transaction, the Purchased Securities shall be transferred to Buyer or its agent against the transfer of the Purchase Price to an account of Seller. (b) Upon agreeing to enter into a Transaction hereunder, Buyer or Seller (or both), as shall be agreed, shall promptly deliver to the other party a written confirmation of each Transaction (a “Confirmation”). The Confirmation shall describe the Purchased Securities (including CUSIP number, if any), identify Buyer and Seller and set forth (i) the Purchase Date, (ii) the Purchase Price, (iii) the Repurchase Date, unless the Transaction is to be terminable on demand, (iv) the Pricing Rate or Repurchase Price applicable to the Transaction, and (v) any additional terms or conditions of the Transaction not inconsistent with this Agreement. The Confirmation, together with this Agreement, shall constitute conclusive evidence of the terms agreed between Buyer and Seller with respect to the Transaction to which the Confirmation relates, unless with respect to the Confirmation specific objection is made promptly after receipt thereof. In the event of any conflict between the terms of such Confirmation and this Agreement, this Agreement shall prevail. (c) In the case of Transactions terminable upon demand, such demand shall be made by Buyer or Seller, no later than such time as is customary in accordance with market practice, by telephone or otherwise on or prior to the business day on which such termination will be effective. On the date specified in such demand, or on the date fixed for termination in the case of Transactions having a fixed term, termination of the Transaction will be effected by transfer to Seller or its agent of the Purchased Securities and any Income in respect thereof received by Buyer (and not previously credited or transferred to, or applied to the obligations of, Seller pursuant to Paragraph 5 hereof) against the transfer of the Repurchase Price to an account of Buyer.

  • Disagreement on Decision Should the parties disagree as to the meaning of the Board's decision, either party may apply to the Chairperson of the Arbitration Board to reconvene the Board to clarify the decision, which it shall make every effort to do within seven days.

  • Termination Notice for Force Majeure Event 21.7.1 If a Force Majeure Event subsists for a period of 60 (sixty) days or more within a continuous period of 120 (one hundred and twenty) days, either Party may in its discretion terminate this Agreement by issuing a Termination Notice to the other Party without being liable in any manner whatsoever, save as provided in this Article 21, and upon issue of such Termination Notice, this Agreement shall, notwithstanding anything to the contrary contained herein, stand terminated forthwith; provided that before issuing such Termination Notice, the Party intending to issue the Termination Notice shall inform the other Party of such intention and grant 15 (fifteen) days time to make a representation, and may after the expiry of such 15 (fifteen) days period, whether or not it is in receipt of such representation, in its sole discretion issue the Termination Notice.

  • Negotiation Period The Parties shall negotiate in good faith and attempt to resolve any dispute, controversy or claim arising out of or relating to this Agreement (a “Dispute”) within 30 days after the date that a Party gives written notice of such Dispute to the other Party.

  • Legal Action Notice A prompt report of any legal actions pending or threatened in writing against Borrower or any of its Subsidiaries that could result in damages or costs to Borrower or any of its Subsidiaries of, individually or in the aggregate, One Hundred Thousand Dollars ($100,000) or more; and