Specifications and Change Control Sample Clauses

Specifications and Change Control a. The Specifications may not be changed without prior written approval of both parties.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Specifications and Change Control. (a) The Specifications may not be changed without prior written approval by APOLLO.
Sample 1Sample 2Sample 3
Specifications and Change Control. (a) Changes to the Specifications will be managed according to the classification reported in the Guidance for Industry “Changes to an Approved NDA or ANDA” — current version — paragraph VIII. For major proposed changes, Kala will assure an evaluation of the proposed changes within [**] days following its receipt of notice of the proposed changes. All the actions will be agreed between the parties. For moderate and minor changes, Supplier will commit to promptly share all the relevant information to Kala.
Sample 1Sample 2
Specifications and Change Control. (a) The Specifications may not be changed without prior written approval by KORU.
Sample 1

Related to Specifications and Change Control

  • AMENDMENT AND CHANGE CONTROL 35.1 Any amendment or change of any nature made to this Agreement and the Schedule of Requirements thereof shall only be valid if it is in writing, signed by both Parties and added to this Agreement as an addendum hereto. In this regard a Change Notice must first be defined and issued by the requesting Party. A Change Notice Response must then be issued by responding Party. A formal approval of the Change Request will then trigger the issue of the addendum to this Agreement.

  • Change Control All systems processing and/or storing PHI COUNTY discloses to 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 15 must have a documented change control procedure that ensures separation of duties and protects the 16 confidentiality, integrity and availability of data.

  • Change Control Procedure A. At any time during the term of this Agreement, either Party may propose a change or changes to any part or parts of this Agreement.

  • Change Control Procedures In the event that either party desires to change the terms of this Contract, the following procedures will apply:

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Implementation Report Within 120 days after the Effective Date, Xxxxxxxx shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • 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. No change in the Specifications shall be implemented by Cardinal Health, whether requested by Reliant 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. Cardinal Health shall respond promptly to any request made by Reliant 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. If after initial Product qualification, Reliant requests a change in the Specifications for its own benefit or to comply with the requirements of a Regulatory Authority, the Specifications shall be amended as soon as [***]: Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. possible after a request is made for any change in Specifications, and Cardinal Health shall notify Reliant of the costs associated with such change and shall provide such supporting documentation as Reliant may reasonably require. Reliant shall pay all costs associated with such Reliant-requested changes or changes required by a Regulatory Authority as may be agreed upon by the Parties. Changes, agreed to between the Parties, for the benefit of Cardinal Health, shall be at the expense of Cardinal Health. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

Time is Money Join Law Insider Premium to draft better contracts faster.