Laserfiche WebLink
equivant JWorks – Kittitas County District Attorney <br />Stateme nt of W ork <br /> <br /> <br />P a g e | 13 <br /> <br /> <br />executed during implementation. <br /> <br />Once the mock conversion is completed, the Customer will be required to review converted data and document <br />corrections needed. As necessary corrections are found, they will be submitted to the equivant Project Manager <br />and conversion team. Corrections may also be required for the source data. These corrections are the responsibility <br />of the Customer. <br /> <br />Final Conversion Run: <br />Final conversion will occur just prior to go-live. At this time, all agreed upon data will be migrated from legacy <br />systems to the Customer’s production JWorks environment as rehearsed during the mock conversions. During the <br />week prior to your go-live, a conference call will take place to review the migration steps, determine the resources <br />required, and solidify outstanding migration items. This will include reviewing roles, responsibilities and timelines <br />for the final data conversion. <br /> <br />The database backups must be re-scheduled, and a final review of the database configuration is required. At the <br />previously scheduled time, the affected Customer legacy databases must be shut down, and data entry will cease <br />in preparation for the final data extract. When backups are completed, the conversion process will begin. <br /> <br />In order to ensure that the conversion runs smoothly during the go-live run, the Customer may be requested to stop <br />day-to-day operations on the Thursday and Friday prior to the scheduled (weekend) conversions . This provides you <br />and equivant the time needed to effectively implement the conversion process. <br /> <br />Your resources must be available to validate the data the day prior to go -live so you can formally approve the data <br />for go-live. The Customer will not utilize JWorks to support production business process until such time as the <br />Customer has validated and approved the data conversion for go-live. <br /> <br />Stabilization: <br />Following the final conversion acceptance, the stabilization period begins. This typically lasts one week and includes <br />performance analysis and general clean up. Table and index statistics are updated to ensure efficient data entry and <br />retrieval. Any data attributes that are missing or formatted incorrectly will be addressed. Pending review of these <br />documents, resolution will be determined, and the attributes will be corrected. Any remedy outside the outlined <br />scope will go through the Change Management Process. <br /> <br />Deliverables for Data Conversion: <br /> Conversion Strategy Plan <br /> Data Mapping Business Rules <br /> Data Conversion Mapping Spreadsheet (Customer) <br /> Data Code Value Mapping (Customer) <br /> Data Files (Customer) <br /> Data Issues Report <br /> Data Statistics Report <br /> Data Loaded in JWorks <br /> Data Validation (Customer) <br /> <br />Payment Milestones for Data Conversion: <br />Data Migration-Conversion will be invoiced at $23,400.00, with $8,000.00 invoiced at the end of the month in <br />which the Test Load has been completed, $7,000.00 invoiced at the end of the month in which Mock Run 1 has <br />been completed, $6,000.00 invoiced at the end of the month in which Mock Run 2 has been completed, and <br />$2,400.00 invoiced at the end of the month in which the Final Run [Go-Live] has been completed. <br />