Laserfiche WebLink
equivant JWorks – Kittitas County District Attorney <br />Stateme nt of W ork <br /> <br /> <br />P a g e | 11 <br /> <br /> <br />Data Conversion <br /> <br />Data Migration enables the Customer to retain the electronic case histories that have been assembled over time in <br />the legacy system. Data will be converted from DAMION. This legacy data is processed and mapped to fit within the <br />JWorks data structures. <br /> <br />Data Conversion Overview <br />The conversion process will require a Customer review of legacy data and will provide the opportunity for the <br />Customer to perform data analysis and clean-up, plus mapping of legacy codes to the JWorks codes prior to moving <br />data into JWorks. <br /> <br />Identity Consolidation <br />The consolidation, or deduplication, of identity records from the legacy data source is not included in the scope of <br />work. equivant can provide an estimated cost for identity consolidation technical services if the Customer desires <br />to have equivant perform this service. <br /> <br />Conversion Strategy <br />This Statement of Work includes a high-level overview of the strategy that equivant utilizes for data conversion of <br />legacy data into the JWorks database. equivant will expand on this as well as update specific plans for the conversion <br />effort. Part of the planning effort will be to make final decisions as to what legacy data will be converted through an <br />automated data conversion effort. equivant will facilitate a data conversion planning session(s) with staff and <br />provide a Data Conversion Strategy Plan deliverable for review and approval. <br /> <br />The equivant conversion methodology includes seven distinct steps: <br /> Data Mapping Business Rules <br /> Script Development <br /> Data Checking <br /> Test Data Load <br /> Mock Implementation Run <br /> Final Conversion Run <br /> Stabilization <br /> <br />The activities of each of these conversion steps are described briefly below. <br /> <br />Data Mapping Business Rules Support <br />During the data mapping and business rule process, equivant and the Customer will analyze the legacy system data <br />model and determine which data needs to be migrated to JWorks and where it will be viewed within the application. <br />The Customer is required to place the data from the legacy system, which is to be migrated to JWorks, into the <br />equivant conversion data model. Detailed worksheets will be provided outlining the format (ASCII text files having <br />fixed length data attributes) of these files. <br /> <br />Some extraction files may be excluded, depending on the specifications of the existing legacy system . In addition, <br />during the extraction process, data exceptions will be discovered, allowing the Customer to identify potential data <br />constraints and cleanse legacy data. <br /> <br />The baseline code set-up must be completed prior to the initial mock conversion, including the Conversion Mapping <br />Utility, which allows the Customer to map its legacy codes to the corresponding JWorks codes. It is assumed that <br />equivant will provide the on -line mapping utility and that the Customer will use this utility to complete the actual <br />code value mapping. <br /> <br />Once all rules and mappings are established, a formal acceptance document is generated outlining the decisions