PROJECT FOUNDATION Sample Clauses
The PROJECT FOUNDATION clause establishes the essential groundwork and initial requirements necessary for a project to commence. It typically outlines the baseline conditions, such as site readiness, provision of access, or completion of preliminary surveys, that must be met before substantive work can begin. By clearly defining these prerequisites, the clause ensures that all parties understand their responsibilities and that the project starts on a solid, agreed-upon basis, thereby minimizing misunderstandings and delays.
PROJECT FOUNDATION. Project Governance 3 Project Scope Control 4 Acceptance Process 6 Roles and Responsibilities 6 PART 3: PROJECT PLAN Project Stages 14 General Assumptions 40 Glossary 43 PART 4: APPENDICES 46 Conversion 46 Additional Appendices 53 Project Timeline 54
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 ▇▇▇▇▇ Executive Manager 7 Tyler Implementation Manager 7 ▇▇▇▇▇ Project Manager 7 Tyler Implementation Consultant 8 Tyler Sales 8 Tyler Technical Services 8 Village Roles & Responsibilities 9 Village Executive Sponsor 9 Village Steering Committee 9 Village Project Manager 9 Village Functional Leads 11 Village Power Users 11 Village End Users 12 Village Technical Lead 12 Village 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 Conversion Assessment 20 Intentionally left blank 21 Intentionally left blank 21 Control Point 2: Assess & Define Stage Acceptance 21 Prepare Solution 22 Initial System Deployment 22 Configuration 23 Process Refinement 24 Conversion Delivery 25 Intentionally left blank 27 Intentionally left blank 27 Control Point 3: Prepare Solution Stage Acceptance 27 Production Readiness 27 Solution Validation 28 Go-Live Readiness 28 End User Training 29 Control Point 4: Production Readiness Stage Acceptance 31 Production 31 Go-Live 31 Transition to Client Services 32 Post Go-Live Activities 33 Control Point 5: Production Stage Acceptance 34 Close 34 Phase Closeout 35 Project Closeout 36 Control Point 6: Close Stage Acceptance 37 General Assumptions 37 Project 37 Organizational Change Management 37 Resources and Scheduling 38 Data 38 Facilities 39 Glossary 40 PART 4: APPENDICES 43 Conversion 43 Enterprise ERP Conversion Summary 43 Accounting 43 Accounts Payable 43 Contracts 43 Project Accounting 44 Additional Appendices 45 Intentionally left blank 45 Project Timeline 1 ERP Project Timeline 1 Data & Insights Project Plan 2 Intentionally left blank 2 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. ▇▇▇▇▇’▇ end-to-end solutions empower public sector entities including local, state, provincial and federal government, to operate more efficiently and connect more transparently with their consti...
PROJECT FOUNDATION. Project Governance
PROJECT FOUNDATION. The objectives of this task are to: 1) gain a clear understanding of existing conditions, including physical conditions and use of ▇▇▇▇▇▇▇ 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 ▇▇▇▇▇▇▇ 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 ▇▇▇▇▇▇▇ 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 ▇▇▇▇▇▇▇ 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...