FACAR Revisions Sample Clauses

FACAR Revisions. E.9.5.1 FACAR Revisions shall include all previous FACAR submittals. At the contractors request, the Government CARB Chairperson may elect to waive the requirement to re-submit a FACAR for revised TIR if the Government CARB Chairperson determines that no significant change was recorded in the TIR.
AutoNDA by SimpleDocs

Related to FACAR Revisions

  • Classification Plan Revisions A. The Employer will provide to the Union, in writing, any proposed changes to the classification plan including descriptions for newly created classifications. Upon request of the Union, the Employer will bargain, in accordance with Article 37, Mandatory Subjects, the effect(s) of a change to an existing class or newly proposed classification.

  • Revisions With respect to Contracts that are “electronic chattel paper”, the related Receivables have been established in a manner such that (a) all copies or revisions that add or change an identified assignee of the authoritative copy of each such Contract must be made with the participation of the Trust Collateral Agent and (b) all revisions of the authoritative copy of each such Contract are readily identifiable as an authorized or unauthorized revision.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

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

  • Ongoing Review and Revisions As set forth in Section 35.7, the Parties have agreed to the coordination and exchange of data and information under this Agreement to enhance system reliability and efficient market operations as systems exist and are contemplated as of the Effective Date. The Parties expect that these systems and the technology applicable to these systems and to the collection and exchange of data will change from time to time throughout the term of this Agreement. The Parties agree that the objectives of this Agreement can be fulfilled efficiently and economically only if the Parties, from time to time, review and, as appropriate, revise the requirements stated herein in response to such changes, including deleting, adding, or revising requirements and protocols. Each Party will negotiate in good faith in response to such revisions the other Party may propose from time to time. Nothing in this Agreement, however, shall require any Party to reach agreement with respect to any such changes, or to purchase, install, or otherwise implement new equipment, software, or devices, or functions, except as required to perform this Agreement.

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

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Contract Revisions Notwithstanding Contract Exhibit C, Special Contract Conditions section 6.9, the following types of revisions can be made to the Contract without a formal Contract amendment, upon written notice: Revisions by the Contractor:

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

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