Timmons Group 12/4/2020 - Laserfiche WebLink

for production conversion, the source systems will need to be taken offline or transitioned into a read only state. Multi-Staged Execution Once the scripts are developed, the project team will test our methodology through a 3-stage process. This process is designed so that after the first data migration run (Draft)we will meet with the City to review the data, note issues and errors, edit our scrips and process, and then repeat the process. The 3 stages will be: Draft Data Migration Pre-Final Data Migration Final Data Migration Although the details underlying each conversion may vary substantially, automation is assumed based on the volume indicated by the City within the RFP.As part of the process, the project team will be analyzing and evaluating the output to identify potential anomalies that are not sufficiently systematic to be detected or trapped by the scripts. The approach to addressing those anomalies will be documented and discussed with the City. Validation & Quality Control With the conversion process completed against a subset of the data, the project team will perform a series of validation and quality control processes to verify a successful migration. This task will largely focus on back-end analytics that compare data in both the source and target systems but will also consist of front-end testing prior to release to the City for testing. Results from this quality control process will be documented and shared with the City. Acceptance Testing In contrast with the validation and quality control phase, which is based on a review by the project team, the acceptance testing phase offers City staff the opportunity to review the data within the context of the proposed Cityworks system in contrast with the information contained in the source systems. The acceptance testing places more emphasis on the front-end testing, wherein users will interact with, interrogate and visualize data through the Cityworks interface. Feedback will be incorporated into a revision process that will guide modifications to the scripts and processes that initially drove the conversion. Upon completion of the testing process and acceptance by the City, the project team will prepare for the production conversion, which will coincide with the release of the proposed system and the retirement of the legacy solutions. Production Conversion The production conversion effort will encompass the migration of the full data sets from each of the source systems into Cityworks. The processes established through the crosswalk and encapsulated in the refined translation scripts will be executed as part of the production release management process. The conversion team will coordinate with the City to transition the source systems into a static state to ensure that no further data entry occurs that could result in data loss. The automated aspects of the conversion will be applied followed by any documented manual processes that are required to address data anomalies. The production conversion will wrap-up with a coordinated, but truncated, validation sufficient to verify a successful data migration. Based on the preceding step-wise approach with multiple points of quality control and an ongoing feedback loop, the final conversion process is anticipated to adhere to the expectations of the project team and the City and will result in a more consolidated system with centralized access to a wealth of historic information. Phase 7,Task 22: City Responsibility: • Gather information for data migration requirements(8-16 FTE Hours). . Additional meetings as required(approximately 16 FTE Hours per participant). Phase 7,Task 22:Timmons Group Responsibilities and Deliverables: . Orientation Workshop 32IPage