Laserfiche WebLink
See Exhibit 6 for the interfaces that are considered in scope. The following interfaces have been identified <br />as required for go -live: <br />• There are no interfaces in the scope of this project <br />.1.6.10 Customizations & Interfaces Roles & Responsibilities <br />D1.6.10.1 Customizations <br />CITY OF SAN MARCOS, TX PAGE 39 OF 62 <br />ERP PROJECT- FINAL SOW <br />Responsibility <br />Discovery of <br />customization <br />Through analysis, functional requirements will be <br />Lead <br />Participate <br />defined <br />requirements <br />The City, Tyler Consultants and Tyler Development <br />Requirement Validation <br />Representatives verify Customization is necessary <br />Lead <br />Participate <br />through exploration of existing options <br />Create Customization <br />Tyler Development Representative will work with the <br />Summary <br />City to write a basic summary outline of customization <br />Lead <br />Participate <br />functionality <br />Tyler Development Representative review <br />Create Detailed <br />Customization Summary and create City Specification <br />Customization <br />document that describes how and where the program <br />Own <br />None <br />Specification Document <br />changes will occur in order to accomplish functional <br />requirements <br />Tyler will deliver a written specification to City, <br />Specification Sign -Off, <br />outlining functional changes, cost, timeline and version <br />None <br />Own <br />Authorization to Proceed <br />requirements. This document must be signed prior to <br />any work being performed by Tyler <br />Tyler will program changes as outlined in the signed <br />Development of <br />specification document. Changes subsequent to sign- <br />Own <br />None <br />Customization <br />off will be considered out of scope and may require <br />repetition of previous steps <br />Customization QA <br />Tyler's QA team will test customization within <br />Own <br />None <br />applicable, impacted modules <br />Customization Delivery <br />Tyler will deliver and demonstrate customization as <br />and Demonstration <br />scheduled. Demonstration will include validating <br />Lead <br />Participate <br />compliance with written specification <br />City will validate performance of customization <br />Test Customization <br />through repeated unit testing as well as process testing <br />Participate <br />Lead <br />throughout implementation <br />Tyler will deliver a written Acceptance Sign -Off for <br />Customization <br />the customization. Acceptance is expected within 30 <br />None <br />Own <br />Acceptance <br />days of delivery unless City notifies Tyler in writing of <br />non - compliance with specification <br />CITY OF SAN MARCOS, TX PAGE 39 OF 62 <br />ERP PROJECT- FINAL SOW <br />