Equivant - Laserfiche WebLink

Home Browse Search

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