Section 3 – Specific Plan Sample Clauses

Section 3 – Specific Plan. Specific plans for providing the proposed software system including: • What, when and how the service will be performed. • Plan for Training of City staff • Time frame for completion of implementation of system and training to have the system fully operational by “Go-Live” dates identified by the City. • The City would like to hear about future plans, services and system modules that may become available during the contract period. • Describe the system warranty period.
AutoNDA by SimpleDocs
Section 3 – Specific Plan. Specific plans for providing the proposed software system including:  What, when and how the service will be performed.  Plan for Training of County staff  Time frame for completion of implementation of system and training to have the system fully operational by “Go-Live” dates identified by the County.  The County would like to hear about future plans, services and system modules that may become available during the contract period.  Describe the system warranty period.

Related to Section 3 – Specific Plan

  • Paragraph specific notes Notes following the numbered paragraphs

  • State Specific Provisions N/A. ATTACHED EXHIBIT. The Exhibit noted below, if marked with an "X" in the space provided, is attached to this Note: X Exhibit A Modifications to Multifamily Note

  • Section 1. General The Appointing Authority may authorize travel at State expense for the effective conduct of the State's business. Such authorization must be granted prior to the incurrence of the actual expenses. Employees affected under this Article shall be reimbursed for such expenses that had been authorized by the Appointing Authority in accord with the terms of this Article.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • TASK 1 GENERAL PROJECT TASKS PRODUCTS

  • Annual Work Plans (a) The Recipient shall prepare in accordance with guidelines acceptable to the Association and furnish to the Association not later than March 31 in each calendar year, a proposed annual work plan and budget for the Project for the following fiscal year of the Recipient, of such scope and in such detail as the Association shall reasonably request.

  • Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

  • For Lump Sum Change Order The payment and extension of time (if any) provided by this Change Order constitutes compensation in full to the Contractor and its Subcontractors and Suppliers for all costs and markups directly and indirectly attributable to the Change Order herein, for all delays related thereto and for performance of changes within the time stated.

  • Work Plan Coordinate a work plan including a list of the proposed meetings and coordination activities, and related tasks to be performed, a schedule and an estimate. The work plan must satisfy the requirements of the project and must be approved by the State prior to commencing work.

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