Equivant - Laserfiche WebLink

Home Browse Search

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