2020/12/02 Council Agenda Packet

Phase 6, Task 21: City Responsibility: • City will be responsible for assisting our implementation team with the generation of a comprehensive catalog of existing reports. (8-16 hours per Functional Group) • Review of reports once designed and configured (2-4 FTE hours per Functional Group) Phase 6, Task 21: Timmons Group Responsibilities and Deliverables: • Modification and development of reports based on a total budgeted allotment of 260 total hours. Phase 6, Task 21 • Assumptions: • City will designate a report writer/s who will work with our implementation team to generate the catalogued list of reports, review reports developed by our implementation team, and be trained on ad -hoc and leveraging Crystal for Cityworks report creation (not Crystal Reports training). • Timmons Group has applied 260 hours to accomplish the creation of new reports as information provided to make a definitive LOE calculation is not possible at this time. • City will provide review comments within 10 business days or a mutually agreed upon timeframe Phase 6, Task 21: Estimated Tmmeframe: • The development of reports will require approximate y 12-18 weeks P hase 6 Exit Criteria Modification and development of reports based on a total budgeted allotment of 260 total hours. P hase 7: Data Miqration/Conversion P hase 7 Task 22: Data Migration The data to be converted will consist of the City's legacy CASSWorks data within the Oracle database. Inherent to the process is establishing a strategy to deal with the data that is being managed in what will become a legacy system. Data Migration Approach The legacy datasets and systems targeted for possible conversion likely span multiple database schemas, database versions and possibly even database formats, which implies that each will be handled in a unique way. While this is true in many ways, the fundamental approach to successfully migrating data from one system to the other is, in fact, the same Coordination As is evident by this scope of work, the migration effort typically is just one facet of the system implementation and it is our recommendation that it is not undertaken independently. The reason for this is because it is much easier to define possible new locations for legacy data when the core system is being designed. The danger of converting data "down the road" is that there may not be a readily apparent place for data to be migrated to, thus necessitating a core system design change. However, if the City finds it necessary to perform a data migration in a future phase the schema targets should be considered within this scope of services so that the future data migration has a higher chance of not only being successful, but also requiring less effort (cost). The foundation of the proposed Cityworks solution needs to be in place in order for the data migration to be performed, but even then, the conversion may drive specific configuration items and changes. Coordination and communication between the project team members will be an ongoing element of the conversion process that starts with project kickoff and terminates with a successful migration of all data into the production environment. 30Jf'age