Laserfiche WebLink
equivant JWorks – Kittitas County District Attorney <br />Stateme nt of W ork <br /> <br /> <br />P a g e | 12 <br /> <br /> <br />reached. This document is used as a guideline throughout the conversion life cycle. Any items outside the outlined <br />scope will go through the Change Management Process. <br /> <br />It is expected that the Customer will complete detailed worksheets for each of the legacy systems as applicable. <br />equivant also assumes that the Customer will complete the required code mapping for all legacy systems to <br />incorporate legacy codes into one consolidated use of code values in the JWorks system. <br /> <br />Script Development <br />Script development (refinement) might be necessary where the Customer has specific business requirements for <br />handling legacy data that differ from standard equivant data conversion scripts . The scripting process is made up of <br />separate scripts from each of the primary components of the JWorks application. <br /> <br />This involves implementing all necessary business logic for JWorks as well as legacy rules, and data mappings <br />established to this point. The mappings and rules utilized for the Script Development were defined in the Data <br />Mapping Business Rules step. The output of this step is the completed data conversion scripts. <br /> <br />Data Checking <br />Once data has been provided in the agreed upon format, the data is loaded into conversion work tables for data <br />checking exercises. Referential integrity, correct date values, correct numeric values, and required values are all <br />checked during this process. A Data Issues Report identifying all issues is then sent to the Customer. There are two <br />main sections on the report. The first one (titled ‘Stop Issues’) shows the issues that must be corrected before the <br />data conversion can move forward. This may require correction of extract programs by the Customer and a new set <br />of files to be provided. The second section (titled ‘Observations’) shows issues that may affect the quality of the <br />data but do not necessarily have to be corrected in order for the conversion to continue. Customer may decide to <br />move forward with current data and cleanup observation issues at a later time. <br /> <br />During the data checking phase, codes will also be validated against existing JWorks code values. If a given code <br />does not have a matching value in JWorks, the Customer will have the opportunity to create a matching code or <br />“map to” an already existing code. All codes must have a matching value, a mapped value, or a default value before <br />the conversion can continue. <br /> <br />Data conversion does not include equivant staff fixing or scrubbing the Customer source data. <br /> <br />Test Data Load <br />equivant will perform one Test Data Load with limited volume case data provided by the Customer. <br /> <br />Once the data conversion scripts are developed, the Customer will provide a sample data set of approximately 1,000 <br />representative cases, defined as per the Data Mapping Business Rules. equivant will run a test data load on this data <br />set and provide a Data Issues Report detailing any required modification to source data and scripts . equivant will <br />rerun the Test Data Load process with a new set of sample test data after identified issues have been remedied. <br /> <br />A test data load is a predecessor activity to the start of System Administration Training and Configuration Assistance. <br /> <br />Mock Implementation Run <br />Two mock conversions will be performed emulating the final implementation. Each mock conversion will be <br />performed per the project schedule. For each conversion, the Customer will provide files of data extracted from the <br />legacy systems, formatted according to equivant specifications. <br /> <br />Detailed statistics by script, source table and JWorks table guarantee that the conversion effort has accounted for <br />each row of data. A Data Statistics Report is provided for each mock conversion. Benchmarks are set utilizing time <br />estimates from each mock conversion run. Additional critical comments are tracked in order to ensure they are