ESO Solutions, Inc. 12/8/2016 - Laserfiche WebLink

EXHIBIT D DATA CONVERSION I. Description of Services and Milestones The Customer desires a method of reporting legacy records within the ESO Solutions application suite for historical reference and reporting.The approach outlined in this document will allow access of these records in the ESO Fire application for historical references and through Adhoc,Canned,and Analytics for reporting. Milestones: • Validate NFIRS file(s)provided by customer and time to fix it, if needed. o Estimated 7 Days • Import NFIRS file(s)to staging area, prior to production migration o Estimated 5 Days • Historical Load of Agency Data o Varies based on number of records being migrated to ESO platform (2-3 secs/record) Deliverables Imported legacy records will be accessible from ESO's FIRE application where an imported record can be searched using the "Search" feature. Once located, the user is able to view/edit the Incident, associated Exposures and can perform all the operations in FIRE application as it was a record created using ESO's FIRE application. However, ESO doesn't recommend edit operation as it will change the integrity of imported data and may result in issues with "Validate and Lock"process. Imported records will also be accessible from all of ESO's reporting tools—Adhoc, Canned, and Analytics. Assumptions • To successfully complete the project described in this Statement of Work, ESO requires the data to be imported in single/multiple (if multiple files, then one file per year) valid NFIRS 5.0 files, with file being named with ESO's "AgencyCode_DateRangeofRecords" in the file. Currently, ESO doesn't have the capability to import the attachments associated with the records in the file. Customer will provide the source data in NFIRS 5.0 file format,either in "All-in-one"file or multiple files(one file per year). • Source files provided are to be valid NFIRS 5.0. If not, ESO will import file "As It Is" on customer approval. • ESO will check the integrity of the data as part of the process and will have Agency's missing demographics info (like Units, Stations and Personnel etc.) added to the system as "Inactive" before the import. • Existence of"Plus One"codes in source files will be converted to their"Base code"for import. • Incidents with multiple exposures will be imported as"Multiple Exposures"for an incident. • • :All the Incidents are imported as"Locked" Incidents. • None of the records imported to ESO platform will be exported as part of NFIRS reporting. H.Additional Terms and Conditions SHOULD CUSTOMER BE UNABLE MEET THE ASSUMPTIONS LISTED IN SECTION I OF THIS EXHIBIT, ESO MAY BE UNABLE TO COMPLETE THE PROJECT AS DESCRIBED. ESO Solutions.Inc. Subscription Agreement 092214 Page 13of13