Local Project Delivery Application Sample Clauses

Local Project Delivery Application. The LOCAL GOVERNMENT has submitted its Local Project Delivery Application to administer the PROJECT attached hereto as Appendix A. The DEPARTMENT’S State TIA Administrator has reviewed, confirmed and approved the Local Project Delivery Application for the LOCAL GOVERNMENT to develop the PROJECT within the scope of its certification. Expenditures incurred by the LOCAL GOVERNMENT prior to the execution of this AGREEMENT or expenditures made pursuant to other funding agreements shall not be reimbursed by the DEPARTMENT.
AutoNDA by SimpleDocs

Related to Local Project Delivery Application

  • Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded Vendor under this Agreement when the TIPS Member desires goods or services awarded to the Vendor. Notification may occur via phone, the web, courier, email, fax, or in person. Upon notification of a pending request, the awarded Vendor shall acknowledge the TIPS Member’s request as soon as possible, but must make contact with the TIPS Member within two working days. Status of TIPS Members as Related to This Agreement TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.

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

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