Laserfiche WebLink
• a , S i ; .{ r :23 <br /> . '� •..�. S � 5 ,�tis <br /> , vd .. .ea . ' ,,:**; meq" i`� ii. <br /> Note: The data conversion estimate does not include effort for identity consolidation. CJS can <br /> provide an estimated cost for identity consolidation technical services if the City desires to have <br /> CJS perform this service. <br /> Some extraction files may be excluded depending on the specifications of the existing legacy <br /> system. In addition, during the extraction process, data exceptions will be discovered, allowing the <br /> City to identify potential data constraints and cleanse legacy data. <br /> The code set-up must be completed prior to the initial mock conversion, including the Conversion <br /> Mapping Utility,which allows the City to map its legacy codes to the corresponding JWorks codes. <br /> It is assumed that CJS will provide the on-line mapping utility and that the City will use this utility to <br /> complete the actual code value mapping. <br /> Once all rules and mappings are established, a formal acceptance document is generated outlining <br /> the decisions reached. This document is used as a guideline throughout the conversion life cycle. <br /> Any items outside the outlined scope will go through the Change Management Process. <br /> It is expected that the City will complete detailed worksheets for each of the legacy systems as <br /> applicable. CJS also assumes that the City will complete the required code mapping for all legacy <br /> systems to incorporate legacy codes into one consolidated use of code values in the JWorks <br /> system. <br /> Note: The data migration estimates will be updated as part of the Data Mapping Business Rules <br /> activity and may result in a project change request if the data conversion efforts are different than <br /> currently assumed. <br /> CJS has included 1 service day for the support of data mapping business rules. <br /> Script Development: <br /> Script development (refinement) might be necessary where the City has specific business <br /> requirements for handling legacy data than for what CJS provides out-of-the box support. The <br /> scripting process is made up of separate scripts from each of the primary components of the <br /> JWorks application. <br /> This involves implementing all necessary business logic for JWorks as well as legacy rules, and <br /> data mappings established to this point.The mappings and rules utilized for the Script Development <br /> were defined in the Data Mapping Business Rules step. The output of this step is the completed <br /> data conversion scripts. <br /> CJS has included 1 service day for the update of data load scripts. <br /> Data Checking: <br /> Once data has been provided in the agreed upon format, the data is loaded into conversion work <br /> tables for data checking exercises. Referential integrity, correct date values, correct numeric <br /> values, and required values are all checked during this process. A Data Issues Report identifying <br /> all issues is then sent to the City. There are two main sections on the report. The first one (titled <br /> 'Stop Issues') shows the issues that must be corrected before the data conversion can move <br /> forward. This may require correction of extract programs by the City and a new set of files to be <br /> 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. City may <br /> decide to move forward with current data and cleanup observation issues at a later time. <br /> During the data checking phase, codes will also be validated against existing JWorks code values. <br /> If a given code does not have a matching value in JWorks, the City will have the opportunity to <br /> COurMEW Page 111 <br /> JUSTICE SOLUTIONS <br />