Laserfiche WebLink
create a matching code or "map to" an already existing code. All codes must have a matching <br /> value, a mapped value, or a default value before the conversion can continue. <br /> CJS has included 1 service day for data checking. <br /> Test Data Load: <br /> CJS will perform two (2) Test Data Load iterations with limited volume case data provided by the <br /> City. <br /> Once the data conversion scripts have been developed, the City will provide a sample data set of <br /> approximately 1,000 cases which will be provided as per the Data Mapping Business Rules. CJS <br /> will run a test data load on this data set and provide a Data Issues Report detailing any required <br /> modification to source data and scripts. CJS will rerun the Test Data Load process with a new set <br /> of sample test data after identified issues have been remedied. <br /> CJS has included 2 service days to support test data load. <br /> Mock Implementation/ Run: <br /> Two (2) mock conversions will be performed emulating the final implementation. Each mock <br /> conversion will be performed per the project schedule. For each conversion, the City will provide <br /> files of data extracted from the legacy systems, formatted according to CJS specifications. <br /> Detailed statistics by script, source table and JWorks table guarantee accounting for each row of <br /> data. Benchmarks are set utilizing time estimates from each mock conversion run.Additional critical <br /> comments are tracked in order to ensure they are executed during implementation. <br /> Once the mock conversion is completed, the City will be required to review converted data and <br /> document corrections needed. As necessary corrections are found, they will be submitted to the <br /> CJS Project Manager and conversion team. Corrections may also be required for the source data. <br /> These corrections are the responsibility of the City. <br /> Detailed statistics by script, source table and JWorks table guarantee that the conversion effort has <br /> accounted for each row of data. A Data Statistics Report will be provided for each mock <br /> conversion. Benchmarks are set utilizing time estimates from each mock conversion run.Additional <br /> critical comments are tracked in order to ensure they are executed during implementation. <br /> CJS has included 2 1/2 service days to support mock data conversion. <br /> Final Conversion Implementation/Run: <br /> A final conversion will happen when all agreed upon data is migrated to the City's production <br /> environment. During the week of implementation, a conference call will take place to review the <br /> conversion steps, determine the resources required, and solidify outstanding conversion items. <br /> This will include reviewing all resource responsibility, acceptance documents and time estimates <br /> for the conversion. <br /> CJS will also be loading the incremental images since the image migration during Mock <br /> Implementation / Run and update the image index with this information. <br /> The database backups must be re-scheduled, and a final review of the database configurations is <br /> required. At the previously scheduled time, the affected City legacy databases must be shut down, <br /> and data entry will cease in preparation for the final data extract. When backups are completed, <br /> the conversion process will begin. <br /> CourtVIEW Page 1 12 <br /> JUSTICF SO STI ONS <br />