Discretionary Specification Changes Sample Clauses

Discretionary Specification Changes. For changes to the Specifications that are not Required Specification Changes (collectively “Discretionary Specification Changes”), EUSA and Innocoll must each agree to any Discretionary Specification Changes and shall, to the extent commercially reasonable under the circumstances, cooperate in making such changes, and each agrees that it shall not unreasonably withhold its consent to such Discretionary Specification Changes.
AutoNDA by SimpleDocs
Discretionary Specification Changes. For changes to the Specifications that are not Required Specification Changes (collectively “Discretionary Specification Changes”), Adolor shall submit a request to Supplier for any such Discretionary Specification Changes. Upon receipt of such request from Adolor, Supplier shall determine (a) one-time and/or ongoing costs that would be incurred resulting from the Discretionary Specification Changes, (b) any resulting planned changes in timing for the delivery of the API Compound and (c) the estimated time of implementing any such Discretionary Specification Changes (the “Cost and Time Statement”). Supplier shall provide the Cost and Time Statement to Adolor setting forth the terms on which Supplier would be willing to make the Discretionary Specification Changes. Upon Adolor’s written approval of the Cost and Time Statement, the parties shall cooperate in making such Discretionary Specification Changes and Supplier shall implement such Discretionary Specification Changes.

Related to Discretionary 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.

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

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

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

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

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

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

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

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