2020/12/02 Council Agenda Packet

• Database Crosswalk Schema Document • Conversion of Cassworks data only • Agreed upon Key data from all Cassworks Service Requests and Work Orders will be converted in this effort Phase 7, Task 22: Assumptions: • City will provide a conference room appropriately sized for the number of participants and review all documentation within 10 business days. Phase 7, Task 22: Estimated Timeframe: The conversion of the legacy data will require approximately 10-14 weeks P hase 7 Exit Criteria <, Data Conversion orientation workshop .} Database Crosswalk Schema document Conversion of Cassworks Oracle database Phase 8: User Acceptance testing P hase 8, Task 23: Develop Testing and Acceptance Plan The implementation team will work with the City to develop and administer a Testing and Acceptance Plan that addresses User Acceptance Testing (UA"r). Testing and Acceptance Plan objectives shall remain consistent with the application functionality detailed in the System Design and Configuration Plan and Application Design Document (for enterprise interfaces). The Testing and Acceptance Plan will address, in sufficient detail (as collectively deemed by the City and the implementation team) the elements required to support the City's testing of the Cityworks software functionality and database configuration, security matrix, documentation of application pei formance issues/errors experienced during the testing, documentation of the resolutions to noted issues/errors, and certification and acceptance of the final deliverable database configuration and software functionality. This will include testing for Cityworks Office, Respond and Mobile app. The test server and final production server environments will be measured against the results of the testing performed in accordance with this Testing and Acceptance Plan (for UAT only), and it is the baseline to which the scoped projects tasks will adhere. The Testing and Acceptance Plan (UAT only) shall be subject to the review and acceptance as to its reasonableness for its intended effort, which is defined herein as the ability to support the logical and thorough testing of the Cityworks application functionality, platform stability, and database configurations. Upon completion of development of the Testing and Acceptance Plan (UAT only), the Team shall submit said plan to the City for review and approval. It is important for City staff to review the draft plan for technical accuracy and completeness. Our configuration team will update the Draft Testing and Acceptance Plan, incorporating City comments and re -submit said plan as Final. Phase 8, Task 23: City Responsibility: • Review and comment on plan. (4 -8 FTE Hours Per Functional Group) • Identify and assign for user Acceptance Testing (UAT) • Perform UAT Phase 8, Task 23: Timmons Group Responsibilities and Deliverables: • Testing and Acceptance Plan drafts and final. • Addressing functional requirements not met/revealed by UAT that do meet defined functional requirements Phase 8, Task 23: Assumptions: City will review all documentation within 10 business days or mutually agreed upon timeframe. Phase 8, Task 23: Estimated Timeframe: The development of the Testing & Acceptance Plan will require 4-6 weeks P hase 8, Task 24: Acceptance Testing P rior to Go -live there will be a thirty (30) day acceptance testing period (the acceptance period is flexible based on input from the City's Project Manager). During this period the City will test the Cityworks