Laserfiche WebLink
• A source system that has data integrity issues greater than 301 o in more than 5 data elements fields will not <br />be considered as a potential interlace to the Lawson System until modification are made by the City to the <br />let!acv code to validate and clean the ;.rata. <br />Interfaces: <br />L,,w,on provided the lbllouing respon:,e rekaed to interfaces, and the Role of each party in the conversion <br />process. It is assumed this task will be split evenly between the City and Lawson. The list of interfaces that <br />are in scope is based upon this list provided by the City in Table 3.2 of the City's Request for Proposal. <br />Inter fat Tasks <br />'tbl <br />Uwner . <br />Asset' <br />!?rt#a# <br />Place <br />Conduct one -day session \\ ith City tecllnolo_>,y <br />Workshop <br />Lav son <br />Planning <br />resources to review conversion the layouts for <br />delivered <br />Lawvson- delivered API's <br />Document the current interfaces <br />Interface matrix <br />City <br />Design <br />Document the interface programs required and <br />System <br />Lawson <br />City <br />Design <br />the estimated work effort to complete those <br />Integration Plan <br />interlaces <br />Flow Chart the interfaces <br />Flow Chart <br />Lawson <br />City <br />Desium <br />Code program logic to map data from legacy or <br />Interface file <br />Lawson <br />City <br />Design <br />non - Lawson system to I -awson .API file layout <br />maps <br />formats <br />Create detailed program definitions, develop <br />Lit4VS011 <br />C:try <br />Desr�m <br />prototype, unit test, and document data access <br />methods <br />Complete data mapping <br />Lawson <br />City <br />Construction <br />Develop final data extract and mapping <br />Interface extract <br />Lawson <br />City <br />Construction <br />programs <br />programs <br />Validate data integrity in system test <br />System test sign <br />City <br />Lawson <br />Construction <br />off <br />Load final tables <br />Lawson <br />Citv <br />Construction <br />Validate data integrity in production <br />Final sign off <br />City <br />Activation <br />D. Please describe the workflows that are in the scope of this project. <br />Lawson Response: Lawson has not listed specific workflows within the scope of this project, although we <br />have provided a list of the standard delivered work -Hows earlier in this document. It is estimated that the City <br />will deploy 6 -8 worklows, which is average for a City of this size. Lawson has allotted 280 hours for this <br />effort to assist the City. <br />S &S Response: <br />Conversion <br />In terns of data conversion, the fbllowin« outlines what has been included as part of pricing proposal <br />The following information will be converted: <br />• Service streets (Geographical street names as related to service areas) <br />• Metering devices (Meters and related reading components) <br />• In -stock meters (Meters held in inventory, not installed) <br />• Balance table (All outstanding account balances, converted as receivable only. by date) <br />• Premises (All data associated with Service addresses) <br />• Customer accounts (Either active or that have balances) <br />• Personal information (All customer related account data) <br />• Contact information (Subset of personal information relating to contact address and phone <br />numbers) <br />• Notes (Converted individually by date provided that each note currently has a date and is able to <br />tie to a premise or account number. If not, they will convert into one large note.) <br />• Account balances <br />• Consumption history — 3 years <br />Lawson Software — Confidential 52 <br />