Laserfiche WebLink
• Billing history for individual transactions only — 3 years. Includes billed, pavnient and <br />adjustment amounts. Does not include breakdown by service, previous balances, statement totals <br />• Unbilled meter readings <br />• Deposits and prepayments <br />• Services (Service information relating to rnetcr.;) <br />• Meter testing, (Data rcl tin T to tlic Large Meter Testing System) <br />• Backtlow Devices (Backflow meter data from legacy backtloNv system) <br />The following information will not be converted, but entered in by Customer after the final conversion: <br />• Favnient arrangements, including installments <br />• All Outstanding pending service orders <br />All other data not specifically mentioned will not be converted -without a change order. This includes, but is <br />not limited to: <br />■ Valves, and Taps including but not limited to: <br />• 1 - HydranIs <br />■ 2 - Corp Taps <br />• 3 - Curb Stops <br />4 - Main Line Valves <br />■ 5 - Fireline Vales <br />■ Credit history <br />■ Billings ;Financial history not specifically outlined above, including but not limited to cleared <br />financial transactions such as charges, credits, payments, fees, bills <br />■ Historical completed service orders <br />Premises and accounts will not be consolidated as part of the conversion. <br />It is assumed that Santa Ana will provide all data files in one of the following formats: <br />• Oracle database <br />• Access database <br />• Fixed length ASCII files with numeric values unpacked (uncompressed) with the sign trailing <br />separate. <br />• Comma delimited ASCII Cite. Text strings to be enclosed within quotes and numeric values <br />unpacked (uncompressed) with the sign trailing separate. <br />• Excel file <br />It is assumed that Santa Ana will transfer data to S&S in one of the following ways: <br />• FTP <br />• 4nun, $rani, LTO or Magstar tapes using a method that is readable by AIX ( tar). Tapes used are <br />to be non - labeled tapes without header/trailer records. <br />• CD -ROMs or DVDs for small individual tiles or MS Access databases <br />If data is being pulled from multiple legacy systems, the extracts provided will all be in the same format, <br />includin g column names and attributes. <br />All data fields will be defined either in the database (for Oracle and Access data) or in a separate data <br />definition, dictionary in electronic format or by a legacy system doctinient that contains at a rnininium: <br />• Field name, matching field name in the data file provided <br />• Field length <br />• Business use of the data <br />• Data type ( e.g. text, numeric, date etc.) <br />• Data descriptions where it is not obvious or being used for a different description in the field <br />name <br />• Validation criteria: acceptable values and or valid numeric ranges <br />• Corresponding field names in the legacy system user interface (UI) <br />Lawson Software — Confidential 53 <br />