Timeline Changes Specification and CGMP Changes Sample Clauses

Timeline Changes Specification and CGMP Changes. 4.1 The parties may revise the Timeline by mutual agreement; provided, that the revised Timeline is in writing and agreed by the Project Team or the JSC. 4.2 In addition, AGC may revise the Timeline if a Non-Fault Delay occurs, keeping the revised Timeline as close as possible to the Timeline in effect immediately before the Non-Fault Delay. AGC is not liable for failure to meet the Timeline if any Non-Fault Delay contributes to the failure.
AutoNDA by SimpleDocs
Timeline Changes Specification and CGMP Changes 

Related to Timeline Changes Specification and CGMP Changes

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

  • Business Changes Change in any material respect the nature of the business of the Borrower or its Subsidiaries as conducted on the Effective Date.

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

  • Program Changes Contractor agrees to inform the County of any alteration in program or service delivery at least thirty (30) days prior to the implementation of the change, or as soon as reasonably feasible.

  • SCOPE CHANGES The Commissioner reserves the right to require, by written order, changes to the scope of the Contract, by altering, adding to or deducting from the Bid Specifications, such changes to be within the general scope of the Contract. If any such change causes an increase or decrease in the cost of, or the time required for, performance of any part of the work under the Contract, whether or not changed by the order, the Commissioner shall, upon notice from Contractor as hereafter stated, make an equitable adjustment in the Contract price, the delivery schedule or both and shall modify the Contract. The Contractor must assert its right to an adjustment under this clause within thirty days from the date of receipt of the written order. However, if the Commissioner decides that the facts justify it, the Commissioner may provide an adjustment without receipt of a proposal. Failure to agree to any adjustment shall be a dispute under the Disputes clause, provided, however, that nothing in this clause shall excuse the Contractor from proceeding with the Contract as changed.

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

  • Implementation of Changes If Tenant: (i) approves in writing the cost or savings and the estimated extension in the time for completion of Landlord’s Work, if any, and (ii) deposits with Landlord any Excess TI Costs required in connection with such Change, Landlord shall cause the approved Change to be instituted. Notwithstanding any approval or disapproval by Tenant of any estimate of the delay caused by such proposed Change, the TI Architect’s determination of the amount of Tenant Delay in connection with such Change shall be final and binding on Landlord and Tenant.

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

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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