PROJECT FOUNDATION Sample Clauses

PROJECT FOUNDATION. 3 Project Governance 3 Project Scope Control 4 Managing Scope and Project Change 4 Change Control 4 Change Request Management 4 Acceptance Process 6 Roles and Responsibilities 6 Tyler Roles & Responsibilities 6 Xxxxx Executive Manager 7 Tyler Implementation Manager 7 Xxxxx Project Manager 7 Tyler Implementation Consultant 8 Tyler Sales 8 Tyler Technical Services 8 City Roles & Responsibilities 9 City Executive Sponsor 9 City Steering Committee 9 City Project Manager 9 City Functional Leads 11 City Power Users 11 City End Users 12 City Technical Lead 12 City Change Management Lead 12 PART 3: PROJECT PLAN 13 Project Stages 13 Initiate and Plan 14 Initial Coordination 14 Project/Phase Planning 15 Infrastructure Planning 16 Stakeholder Meeting 17 Intentionally left blank 18 Control Point 1: Initiate & Plan Stage Acceptance 18 Assess & Define 18 Solution Orientation 18 Current & Future State Analysis 19 Data Assessment 20 Conversion Assessment 21 Intentionally left blank 23 Intentionally left blank 23 Control Point 2: Assess & Define Stage Acceptance 23 Prepare Solution 23 Initial System Deployment 23 Configuration 24 Process Refinement 25 Conversion Delivery 27 Intentionally left blank 28 Intentionally left blank 28 Control Point 3: Prepare Solution Stage Acceptance 28 Production Readiness 29 Solution Validation 29 Go-Live Readiness 30 End User Training 31 Control Point 4: Production Readiness Stage Acceptance 32 Production 32 Go-Live 32 Transition to Client Services 34 Post Go-Live Activities 34 Control Point 5: Production Stage Acceptance 35 Close 36 Phase Closeout 36 Project Closeout 37 Control Point 6: Close Stage Acceptance 38 General Assumptions 38 Project 38 Organizational Change Management 39 Resources and Scheduling 39 Data 39 Facilities 40 Glossary 41 PART 4: APPENDICES 44 Conversion 44 ERP Pro Utility Billing Conversion Summary 44 Utility Billing - Standard 44 Utility Billing – Legacy/Historical Views 44 ERP Pro Financials Conversion Summary 44 General Ledger 44 Accounts Payable 44 Personnel Management 45 Additional Appendices 46 Intentionally left blank 46 Project Timeline 47 ERP Pro Financial Management Timeline 47 ERP Pro Utility Billing, CRM, and Community Development Timeline 48 My Civic Timeline 49 Intentionally left blank 49 Part 1: Executive Summary Project Overview Introduction Tyler Technologies (“Tyler”) is the largest and most established provider of integrated software and technology services focused solely on the public sector. Xxxxx’x...
PROJECT FOUNDATION. The objectives of this task are to: 1) gain a clear understanding of existing conditions, including physical conditions and use of Xxxxxxx Avenue and 2) establish project goals, process, scope, and schedule with the SC. It will be accomplished through the following subtasks and deliverables: Task 2.1 Data Collection and Plan Review ▪ The Kittelson team will obtain and review existing plans for Xxxxxxx Avenue, including approved development applications and site plans from the City, MMPO, MDT, and other members of the SC. The purpose of this review will be to identify planned and programmed projects that may affect the route, as well as each plan’s vision for the route (if applicable). The review will identify commonalities and discrepancies across the reviewed documents. ▪ The Kittelson team will request historical motor vehicle, pedestrian, and bicycle counts and parking inventory and utilization data and travel demand model forecasts from the City, MMPO, MDT, and other members of the SC. o Given the ongoing COVID-19 pandemic and construction on Xxxxxxx Avenue, our project team does not anticipate being able to collect new traffic or parking data. o The Kittelson team will assess count and parking coverage and applicability to current conditions. If necessary, the Kittelson team will extrapolate data to current conditions. o If there are intersections for which historical turning movement counts are not available, we will work with the City, MMPO, and MDT to determine how to best estimate volumes at the intersection(s). ▪ The Kittelson team will inventory on-street and off-street parking by block face/lot using aerial photography for the study area (see Figure 1). Special use parking utilization (e.g., motorcycle, loading, accessible spaces) on Xxxxxxx Avenue will be inventoried using Google Street View imagery and confirmed during a walking inventory completed during the visit to Missoula for Public and Stakeholder Engagement Round #1 and reported separately. Task 2.2 Project Base Mapping ▪ The Kittelson team will request existing mapping information from the City, MMPO, MDT, and utilities along the corridor, including: o Existing survey information o Aerial photograph o Right-of-way (GIS) o Utility locations (GIS) ▪ Wet utilities (sanitary and storm mains, water mains, and hydrants) will be obtained from the City). Dry utility data (power, phone, and fiber) will be requested from private utility providers. ▪ For locations where adequate topographic surv...
PROJECT FOUNDATION. Project Governance

Related to PROJECT FOUNDATION

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

  • 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

  • The Project The Project is the total construction of which the Work performed under the Contract Documents may be the whole or a part.

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