Initiating Interconnection 4.1 If Emergency determines to offer Telephone Exchange Services and to interconnect with Verizon in any LATA in which Verizon also offers Telephone Exchange Services, and in which the Parties are not already interconnected pursuant to this Agreement, Emergency shall provide written notice to Verizon of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.2 The notice provided in Section 4.1 of this Attachment shall include (a) the initial Routing Point(s); (b) the applicable technically feasible Point(s) of Interconnection on Verizon's network to be established in the relevant LATA, in accordance with this Agreement; (c) Emergency’s intended Interconnection activation date; and (d) a forecast of Emergency’s trunking requirements conforming to Section 14.2 of this Attachment; and (e) such other information as Verizon shall reasonably request in order to facilitate Interconnection. 4.3 The Interconnection activation date in the new LATA shall be mutually agreed to by the Parties after receipt by Verizon of all necessary information as indicated above. Within ten (10) Business Days of Verizon’s receipt of the Emergency’s notice provided for in Section 4.1 of this Attachment, Verizon and Emergency shall confirm the technically feasible Point of Interconnection on Verizon's network in the new LATA and the mutually agreed upon Interconnection activation date for the new LATA.
Project Initiation i - Upon final execution of the Agreement with the DISTRICT, the ARCHITECT shall: ♦ Review the Program Management Plan (PMP) with the DISTRICT and its representatives to familiarize them with the proposed tasks and schedule and develop necessary modifications. The PMP defines the Program Master Schedule and Budgets and each Project scope and budget. ii - Within the first week following execution of the Agreement, meet with the DISTRICT and its representatives to prepare a detailed task analysis and work plan for documentation in a computer-generated project schedule. iii - This task analysis and work plan will identify specific tasks including, but not limited to: ♦ interviews, ♦ data collection ♦ analysis, ♦ report preparation, ♦ planning, ♦ Architectural programming, concepts and schematic design preparation and estimating that are part of the work of the Project. Also identified will be milestone activities or dates, specific task responsibilities, required completion times necessary for the review and approval by the DISTRICT and by all regulatory agencies and additional definition of deliverables. iv - Participate in a general Project kick-off meeting to include the ARCHITECT, appropriate sub-consultants, and DISTRICT staff. v - The project kick-off meeting will introduce key team members from the DISTRICT and the ARCHITECT to each other, defining roles and responsibilities relative to the Project. vi - Identify and review pertinent information and/or documentation necessary from the DISTRICT for the completion of the Project. vii - Review and explain the overall project goals, general approach, tasks, work plan and procedures and deliverable products of the Project. viii - Review and explain the task analysis and Project work plan for all parties present; determine any adjustments or fine tuning that needs to be made to the work plan. ix - Review documentation of the Project kick-off meeting prepared by the DISTRICT’S representative and comment prior to distribution. x - Base Drawings and Site Survey Information
Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.
Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.