Opening of Proposals - Utility Billing System - Systems & Software, Inc. - Part 1

Home Browse Search

We use a three -phased data conversion process to systematically understand, map and convert your legacy data to enQuesta. Assessment The assessment phase entails identification andl analysis of the data sources including defining a repeatable method for extracting data from the sources. We lead the assessment effort and provide documents describing the data required for successful import into enQuesta. The data conversion generally includes: 1. Service streets 2. Metering devices 3. In -stock meters 4. Balance table (converted as receivable only) 5. Premises 6. Customer accounts that are either active or that have balances 0 Personal information Contact information Account balances • Notes: Converted individually by date provided that each note currently has a date and is able to tie to a premise or account number. If not, they will be, converted into one large note. 7. Consumption history — 3 years 8. Billing history for individual transactions — 3 years 9. Unbilled meter readings 10. Deposits and prepayments 11. Services Design & Testing At the start of the Design & Testing phase, we lead an analysis of enQuesta data requirements and available legacy data to establish a conversion plain. S&S, will then hold a data mapping workshop with the Utility where trainingi will be provided on a) the enQuesta data model and b) how to provide legacy data in the format of the enQuesta data model. The Utility will then map the relevant legacy tables and fields to the enQuesta data structure and develop a repeatable process to extract the legacy data into templates that S&S provides. (Receiving the data in the S&S format ensures that the standard, tried and true conversion programs execute conversion iterations accurately and provide standard reports of data that needs to be cleansed. These routines are tested using the extracted legacy data and the results are verified. Execution During the execution phase, data is moved from the various sources to the target system using methods developed in the previous segments. There will be three (3) conversion runs, which will include: a test conversion, a simulation conversion and the final Go-Uve conversion. Extensive balancing tests are run to verify the conversion extracts match your legacy data, giving us a high degree of confidence on the final data conversion that is run immediately prior to production Go -Live. This effort estimates for data conversion based on our current understanding of data conversion requirements and assumptions based on our experience with similar implementations. M.