Laserfiche WebLink
PR Opt 8 — Position <br />Control/Hist <br />Payroll Position Control and History <br />PR Opt 9 — State Retirement <br />State Retirement Tables <br />PR Standard <br />Payroll Employee Master <br />P &G Opt 1 <br />Project Ledger — actual account summary balances for up to 3 years <br />P &G Opt 2 <br />Project Ledger — budgeted account balances for up to 3 years <br />P &G Standard <br />Project Ledger Accounts <br />PO Standard <br />Open purchase orders with encumbrances <br />Tyler makes the following assumptions in providing a fixed -price data conversion approach: <br />• Legacy system data to be converted is provided in a non - proprietary format, such as fixed ASCII, <br />CS V or character - delimited <br />• Each legacy system data file submitted for conversion includes all associated records in a single <br />file layout <br />• Each legacy system data file layout submitted for conversion remains static for all subsequent <br />data submissions, unless mutually agreed upon in advance of the change. <br />CITY OF SAN MARCOS, TX PAGE 42 OF 62 <br />ERP PROJECT- FINAL SOW <br />Through analysis, fields in legacy systems and <br />Munis will be outlined for conversion. Tyler <br />Data Mapping <br />staff will use best efforts to direct the City on the <br />Share <br />Share <br />legacy source files and desired fields for <br />conversion mapping <br />The City is responsible for producing reports <br />Run Validation <br />from the legacy system at the time of data <br />None <br />Own <br />Reports <br />extraction. These reports are critical for use <br />during conversion validation <br />The City is responsible for extracting the data <br />Extract data <br />from a legacy system into the accepted Munis <br />None <br />Own <br />layout <br />Develop <br />Tyler will program conversion programs <br />conversion <br />programs based <br />according to the accepted file submission layout. <br />on City data <br />This layout must be maintained consistently for <br />Own <br />None <br />mapping and file <br />all future data submissions or additional charges <br />submission layout. <br />may apply <br />Load Data <br />Load all conversion passes as directed by Tyler <br />Lead <br />Assist <br />Conversion Passes <br />PM <br />Tyler will produce an error report outlining errors <br />Review Error <br />that result from running City's data through the <br />Participate <br />Lead <br />Reports <br />conversion program. The City is responsible for <br />reviewing the report and investigating solutions <br />Tyler makes the following assumptions in providing a fixed -price data conversion approach: <br />• Legacy system data to be converted is provided in a non - proprietary format, such as fixed ASCII, <br />CS V or character - delimited <br />• Each legacy system data file submitted for conversion includes all associated records in a single <br />file layout <br />• Each legacy system data file layout submitted for conversion remains static for all subsequent <br />data submissions, unless mutually agreed upon in advance of the change. <br />CITY OF SAN MARCOS, TX PAGE 42 OF 62 <br />ERP PROJECT- FINAL SOW <br />