Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
Project Implementation 2. The Borrower shall:
Design Development Documents See Section 2, Part 1, Article 2.1.5.
Project Documents In addition to any other pertinent and necessary Project documents, the following documents shall be used in the development of the Project:
Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.
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.
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.
Project Overview The Statement of Work (SOW) documents the Project Scope, methodology, roles and responsibilities, implementation Stages, and deliverables for the implementation of Tyler products. The Project goals are to offer City of Xxxxx Creek, GA the opportunity to make the City more accessible and responsive to external and internal customer needs and more efficient in its operations through: Streamlining, automating, and integrating business processes and practices Providing tools to produce and access information in a real‐time environment Enabling and empowering users to become more efficient, productive and responsive Successfully overcoming current challenges and meeting future goals
Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet
Project Review A. Programmatic Allowances
