TIMELINE, SPECIFICATION AND PROJECT MANAGEMENT Sample Clauses

TIMELINE, SPECIFICATION AND PROJECT MANAGEMENT. Timeline 4.1 AGC shall use its [***] to maintain the Timeline for each Batch. Notwithstanding that obligation, the Parties acknowledge and agree that the Timeline for a Batch may be varied as agreed by AGC and Customer in writing in order to accommodate delays or changes caused by or contributed to by (i) actions or omissions of the Customer (or its agents); and/or (ii) additional activities added to the Services; and/or (iii) force majeure events or other circumstances beyond AGC’s reasonable control (“Non-Fault Delays”). 4.2 In the event of any Non-Fault Delays described in Clause 4.1(i) or (ii), AGC shall update the Timeline for the applicable Batches as agreed in writing with the Customer and shall endeavor in good faith to keep the revised Timeline as close as possible to the Timeline in its form as it existed immediately prior to the Non-Fault Delays. 4.3 Notwithstanding Clause 18.4, the Timeline (for one or more Batches, or prospectively for all future Batches) may be amended by agreement between AGC and Customer provided that the revised Timeline is set out and agreed in writing by the Project Team. 4.4 Where the Timeline has been amended in accordance with this Clause 4, it shall be automatically binding upon the Parties. AGC shall keep Customer updated as to its conformance with the Timeline for Batches then in production on a reasonable frequency. Customer may at any time on a reasonable basis request an update on performance of the Services against the current Timeline. 4.5 The Parties agree that the Specification may be modified and updated by the Parties if agreed to by the Project Team in writing and signed by an authorized representative of each Party. Each Party shall consider any proposed modifications to the Specification, including those that may be requested by a Regulatory Authority, in good faith. For the avoidance of doubt, where the Parties cannot agree to modify, amend or update the Specification, the previous Specification as agreed to by the Parties shall apply.
Sample 1
AutoNDA by SimpleDocs
TIMELINE, SPECIFICATION AND PROJECT MANAGEMENT. Timeline 4.1 CMC shall use Commercially Reasonable Efforts to maintain the Timeline. Notwithstanding that obligation, the Parties acknowledge and agree that the Timeline may be varied as agreed by CMC and the Customer in writing in order to accommodate delays or changes caused by or contributed to by (i) actions or omissions of the Customer (or its agents); and/or
Sample 1
TIMELINE, SPECIFICATION AND PROJECT MANAGEMENT. Timeline 4.1 CMC shall use commercially reasonable efforts to meet the Timeline set forth in each a Work Document or Firm Order as well as the Timeline set forth in Appendix Four. Notwithstanding that obligation, the Parties acknowledge and agree that the Timeline may be varied as agreed by CMC and the Customer in order to accommodate delays or changes caused by or contributed to by (i) actions or omissions of the Customer (or its agents); (ii) additional activities added to the Services; (iii) CMC’s inability to procure Raw Materials despite its using the Standard to mitigate or minimize the possibility of such shortfall (through establishing secondary sources, stockpiling, adding lead time and the like), and/or (iv) Force Majeure Events (collectively, "Non-Fault Delays"). 4.2 CMC shall inform Customer in writing immediately ([*]) of any anticipated delays of more than [*] Calendar Days in the final shipment of any Batch, including Non-Fault Delays that it [*] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24b-2 of the Securities Exchange Act of 1934, as amended. determines in good faith are likely to occur. CMC shall use commercially reasonable efforts to mitigate and minimize any such anticipated or actual delays, including by increasing manufacturing activities in the CMC Facility. If necessary, CMC shall update the Timeline as agreed with the Customer and, shall endeavour to keep the revised Timeline as close as possible to the Timeline in its form as it existed immediately prior to the Non-Fault Delays. 4.3 Notwithstanding Sections 18.5 and 18.6, the Timeline may be amended by agreement between CMC and Customer provided that the revised Timeline is set out in writing and agreed by the Project Team. 4.4 Where the Timeline has been amended in accordance with this Section 4, it shall be automatically binding upon the Parties. CMC shall keep Customer updated as to the current Timeline on a reasonable frequency. Customer may at any time on a reasonable basis request an update on performance of the Service against the current Timeline.
Sample 1
TIMELINE, SPECIFICATION AND PROJECT MANAGEMENT 
Sample 1Sample 2

Related to TIMELINE, SPECIFICATION AND PROJECT MANAGEMENT

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

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

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

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

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

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

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Project Implementation The Borrower shall:

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

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