Voluntary Specification Changes Sample Clauses

Voluntary Specification Changes. 2.4.1.1 The Company may request a Specification Change but no such Specification Change shall be implemented unless both Parties agree in writing, such agreement not to be unreasonably withheld. Notwithstanding the foregoing, Pacira shall implement, at the Company’s expense, all Specification Changes requested by the Company relating to Product package and label branding, artwork and other non-regulatory changes. 2.4.1.2 As soon as is reasonable after notice of the proposed Specification Change is served by the Company, the Parties’ representatives will meet (either in person or by telephone conference) to discuss the proposed Specification Change. The Parties will confer in good faith as to the most cost-effective and efficient means to implement or to otherwise provide for the proposed Specification Change or to discuss any reasons as to why the proposed Specification Change cannot be made. 2.4.1.3 The Parties shall itemize in good faith best estimates of the relative costs and impacts, including capital expenses and potential impacts such expenditures will have on each Party and neither Party shall be required to implement a Specification Change (other than a Company-requested Specification Change described in Section 2.4.1.1 related to non-regulatory changes) unless agreement is reached in relation to the way in which costs, expenditures and other impacts will be apportioned between the Parties.
AutoNDA by SimpleDocs

Related to Voluntary Specification Changes

  • Election Changes The Executive may modify the amount of Deferrals annually by filing a new Deferral Election Form with the Employer. The modified deferral shall not be effective until the calendar year following the year in which the subsequent Deferral Election Form is received by the Employer.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • Term SOFR Conforming Changes In connection with the use or administration of Term SOFR, the Administrative Agent will have the right to make Conforming Changes from time to time and, notwithstanding anything to the contrary herein or in any other Loan Document, any amendments implementing such Conforming Changes will become effective without any further action or consent of any other party to this Agreement or any other Loan Document. The Administrative Agent will promptly notify the Borrower and the Lenders of the effectiveness of any Conforming Changes in connection with the use or administration of Term SOFR.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

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