Laserfiche WebLink
�1 <br />The following outlines major assumptions regarding the Contract and the commitment to Live Dates on <br />time and within budget: <br />• Tyler and the City will be responsible for providing required commitments identified in this <br />statement of work. Failure to provide appropriate support to the listed activities and tasks <br />described in this statement of work may result in change orders <br />• The City will schedule all applicable users to attend scheduled analysis, implementation and <br />training sessions <br />• Session topics are scheduled in advance. One session per topic will be covered within the scope <br />of the project. If the City chooses to have additional sessions repeated, these would be out of <br />scope and require a change order for additional implementation days. This does not include <br />scheduled topics that are repeated for different levels of users. For instance, Accounts Payable <br />Functional Leaders and Core Users will both have AP sessions; however, the level of analysis and <br />hands -on training differs for each group and are considered separate, scheduled sessions <br />• On -site assistance during Go -Live for the financials and payroll phases of the implementation <br />will be determined based on the total budget of days during project planning. Additional Go -Live <br />assistance beyond the budgeted days will be considered out of scope and will require a change <br />order for additional implementation days. Tyler will provide post go -live training for reporting, <br />month -end processing, etc., as defined in the project schedule that will be delivered by the Tyler <br />Project Manager. <br />• It will be the City's responsibility to train decentralized users. Tyler will train Functional <br />Leaders, End (core) users and will conduct a Train - the - Trainer session in order to prepare the <br />trainers to train their decentralized users. The City is responsible for scheduling the decentralized <br />training, developing customized user documentation (Tyler will provide standard documents that <br />may be modified), conducting the training, and assessing user understanding and acceptance. <br />• All project tasks will be assigned owners and due dates which correspond to the overall project <br />schedule. Project Tasks that are not completed by the due date may adversely affect the project <br />schedule and Go -Live Dates <br />• Decisions will be made in a timely fashion in order to achieve scheduled due dates on tasks and <br />prepare for subsequent training sessions. Decisions left unmade may affect the project schedule <br />as each analysis and implementation session builds on the decisions made in prior sessions <br />Project Planning and Kickoff <br />The following outlines major assumptions and activities surrounding the Project Initiation and Kickoff <br />phase of the Project: <br />• The City shall assign and authorize a Project Manager prior to the start of this phase. <br />• The City Project Manager, along with the Tyler Project Manager, shall participate in the review <br />and final revision of the Project management and planning documents, which include this <br />Implementation Project Scope Agreement, the Project Risk Register, and the Communications <br />Plan. <br />• The Tyler Project Manager and City Project Manager will develop the Project Plan. Tyler will be <br />responsible for providing the initial project plan and will maintain and update the project plan <br />throughout all phases of the project. The City's project team will approve the initial and all <br />CITY OF SAN MARCOS, TX PAGE 54 OF 62 <br />ERP PROJECT- FINAL SOW <br />