Laserfiche WebLink
LAWSN <br />Interface ID <br />Interface Description <br />Functional Area <br />Complexity <br />Assumption <br />Interface ID <br />Inhouse based on SQL Server: Indirect <br />Interface until payroll conversion <br />Medium <br />Time and <br />Cost Allocation and Payroll and Benefits <br />HR <br />Medium <br />GLIS <br />Distribution <br />each interface <br />PD Alarm <br />PD 911 Call: To upload Alarm Invoices <br />Interface to Lawson AR for Alarm <br />Low <br />and Technical <br />to MAR for billing <br />Billin <br />for migrating data between the legacy <br />IVR and web- <br />Benefit questions and enrollment <br />HR <br />Low <br />based s stem <br />Nova <br />Cashiering- POS <br />Inbound Cash Receipts. Interface <br />Medium <br />to Lawson AR <br />systems to which Lawson needs to <br />CIS utility <br />Lawson to Systems & Software <br />General Ledger, Accounts Payable, <br />Medium <br />Billing <br />enQuesta- effort included in Appendix C <br />Accounts Receivable <br />Out of Scope: <br />Complexity Assumption is defined as follows. <br />Low Batch method with a one- to-one relationship between legacy system and Lawson tables. Field <br />mapping is fairly straightforward with little or no data translation required. Standard Lawson <br />methods are available to facilitate the data import. <br />Medium The interface may involve the batch method with a one -to -many or many- to-one relationship <br />between the legacy system and Lawson tables or a fairly simple real time interface. Some <br />complexities exist with respect to field mapping and data translation. Standard Lawson objects <br />are available to facilitate the data import or minimal custom programming is required. <br />High Method may be batch or real time. Many -to -many relationship between legacy system and <br />Lawson tables. Very complex field mapping and data translation required. Standard Lawson <br />methods are not available to facilitate the data import requiring complex custom programming. <br />Interface Activities <br />Activity <br />Responsible <br />Key Assumption <br />Complexity <br />Interface ID <br />Interface Description <br />Functional Area <br />Assumption <br />Time and <br />To be determined. (Time and <br />HR <br />Medium <br />Attendance <br />Attendance Vendor to develop interface <br />each interface <br />Software <br />to Lawson) <br />City will participate and provide <br />A document is created describing the plan <br />Complexity Assumption is defined as follows. <br />Low Batch method with a one- to-one relationship between legacy system and Lawson tables. Field <br />mapping is fairly straightforward with little or no data translation required. Standard Lawson <br />methods are available to facilitate the data import. <br />Medium The interface may involve the batch method with a one -to -many or many- to-one relationship <br />between the legacy system and Lawson tables or a fairly simple real time interface. Some <br />complexities exist with respect to field mapping and data translation. Standard Lawson objects <br />are available to facilitate the data import or minimal custom programming is required. <br />High Method may be batch or real time. Many -to -many relationship between legacy system and <br />Lawson tables. Very complex field mapping and data translation required. Standard Lawson <br />methods are not available to facilitate the data import requiring complex custom programming. <br />Interface Activities <br />Activity <br />Responsible <br />Key Assumption <br />Description <br />Define Business <br />City <br />Lawson will participate and <br />A document detailing interface <br />requirements <br />provide input <br />requirements with related file layouts for <br />each interface <br />Develop Functional <br />Lawson <br />City will participate and provide <br />A document is created describing the plan <br />and Technical <br />input <br />for migrating data between the legacy <br />Specification <br />systems and ERP software. <br />requirements <br />Design data mapping <br />City <br />City will be responsible for <br />Data will be mapped between the 3rd party <br />mapping to /from 3`d party <br />systems to which Lawson needs to <br />systems. Lawson will provide <br />interface and the Lawson interface format. <br />SOW- SantaAna- 12Feb08 vFinal v2.doc Confidential 32 <br />