Implementation Date of FHWA Regulations Sample Clauses

Implementation Date of FHWA Regulations. The program and its procedures shall be implemented on January 1, 1996.
AutoNDA by SimpleDocs

Related to Implementation Date of FHWA Regulations

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Change Orders and Contract Amendments 33.1 The Procuring Entity may at any time order the Supplier through notice in accordance GCC Clause 8, to make changes within the general scope of the Contract in any one or more of the following:

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

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

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

  • AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES 5352.201-9101 OMBUDSMAN (APR 2014) Para (c). Ombudsmen names, addresses, phone numbers, fax, and email addresses. 'Xx. Xxxx Xxxxxxxxxx, AFLCMC/AQP, Phone: DSN 000-0000 Comm (000) 000-0000, E- mail: Xxxx.xxxxxxxxxxxxxxx.0@xx.xx.xxx.' 5352.223-9000 ELIMINATION OF USE OF CLASS I OZONE DEPLETING SUBSTANCES (ODS) (NOV 2012) 5352.223-9001 HEALTH AND SAFETY ON GOVERNMENT INSTALLATIONS (NOV 2012) 5352.242-9000 CONTRACTOR ACCESS TO AIR FORCE INSTALLATIONS (NOV 2012) Para (b), Any additional requirements to comply with local security procedures '"to be cited in each individual task order"' Para (d). Additional requirements. '"any additional requirements to comply with AFI 31- 101, Volume 1, the Air Force Installation Security Program, and AFI 31-501, Personnel Security Program Management"' 5352.242-9001 COMMON ACCESS CARDS (CAC) FOR CONTRACTOR PERSONNEL-AF SYSTEMS (NOV 2012)

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

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

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

  • Implementation Program 1. The Borrower shall:

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