City Revision of Supporting Documentation Sample Clauses

City Revision of Supporting Documentation. Any revision by the City of Supporting Documentation provided to the Company that causes the Company to substantially redesign and/or substantially change its plans regarding new or modified service to City facilities shall be deemed good cause for a reasonable extension of time to complete the Relocation under this Franchise.
AutoNDA by SimpleDocs
City Revision of Supporting Documentation. Any revision by the City of Supporting Documentation provided to the Company that causes the Company to substantially redesign and/or change its plans regarding an undergrounding project shall be deemed good cause for a reasonable extension of time to complete the undergrounding project under this Franchise.

Related to City Revision of Supporting Documentation

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Escrow Format Specification 3.1. 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.

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

  • Instructional Materials A. The Board recognizes that appropriate texts, library reference facilities, maps and globes, laboratory equipment, audio-visual equipment, art supplies, athletic equipment, current periodicals, standard tests and questionnaires, computers, and similar materials are the tools of the teaching profession.

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