Laserfiche WebLink
LAWSN <br />For fields that hold codes (i.e. text or numeric values that have specific meanings), cross -maps between valid <br />codes and their meanings will be provided in separate tables, files or reports. <br />Clean Data from Legacy Systems <br />The City will clean up (close, complete, void) all outstanding service orders, in order to reduce the number of <br />service orders that will need manual entry post conversion. <br />The City will produce financial reports needed from the legacy CIS system prior to the enQuestaTm Go Live. <br />The City should also maintain a copy of their existing system or detailed reports in order to be able to access <br />historical data other than consumption history since it will not be converted. <br />The City will create and execute unit test plans to ensure validity of data extracted. The City will identify data <br />that does not meet data requirements of the data dictionary and will correct that data so that the files submitted <br />to Subcontractor only contain clean data. Examples of cleanup tasks include, but are not limited to: <br />Manually correcting invalid information <br />Writing off invalid transactions <br />Removal of duplicate records <br />Removal of obsolete records <br />Correction of data that falls outside acceptable values including codes and ranges <br />It is assumed that the City uses standard street names in their legacy system for the Service Premise <br />Addresses. This SOW assumes that Subcontractor will not be required to be involved in any data cleansing <br />activities regarding Service Premise Addresses. <br />General Roles & Responsibilities <br />Data Conversion Responsibility Matrix <br />P — Primary responsibility <br />S — Supporting role <br />The following table summarizes the most important deliverables and responsibilities for a successful <br />conversion: <br />Task <br />Lead data conversion effort <br />Subcontractor <br />P <br />Create data conversion plan <br />P <br />S <br />Provide list of data that needs to be converted along with major enQuestaTM tables <br />that will be populated and applicable valid codes /ranges. <br />P <br />Create data definition /dictionary <br />P <br />Perform data extraction from legacy systems <br />P <br />Unit test extracted data for validity <br />P <br />Cleanup of data in legacy systems <br />P <br />Map data between legacy system extract and enQuestaTM <br />P <br />S <br />SOW- SantaAna- 12Feb08 vF1na1_v2.doc Confidential 73 <br />