Laserfiche WebLink
�����`���l �� ������J����� ������|��h��NT� <br />`~-~~~~.~~~. ~_ RESPONSES .~~~-.~.�.. ..~~��.',~,,._-._8.1. NOTES AND AssuMPTIONS <br />8.1.1 TYLERREPOKUNGS2RNCES <br />Wherever Tyler Tech no logies, Inc, has responded affirmatively to certain fun ctiona I checkfist <br />questions/requirements/specifications as requiring the use of Tyler Reporting Services, (6SR5),the <br />City �s solely responsible for development of the necessary/required report(s), unless specifically <br />indicated otherwise. <br />8.1.7 IQTERFX[IS/CUSTOMIZATIONS <br />Interface requirements agreed to by Tyler within this response will depend onthe customer <br />maintaining an active support agreement with the identified third party system aswe | as a current <br />version actively supported by the manufacturer/developer of the product installed. <br />8.1.3 CUSTOM MODIFICA-1 IONS <br />Custom modifications, if quoted with a specific doflar value, are priced based upon the total proposed <br />software package and the requirements set forth inthe KFP. Tothe, extent system components <br />� and/or requirements change, pricing for custom modifications may also change. Afacustom <br />modification, is identified without a price, that identification is provided as an alert that the <br />functionality is not available "out ofthe box," and additional information is required from the <br />customer before Tyler can price the modification. DuNmQthe contract negotiation process, Tyier <br />expects to work with the customer to identify the custom modifications that will be considered within <br />the project scope, and toMnahzethe associated price. Those modifications will bedelivered during <br />the project on the schedule the parties mutually agree to during the contracting and/or project <br />planning process(es), Any custom modifications that the customer requests post -contracting will be <br />subject iqanamendment orchange order ,whichwlUaddress etleast the prldngand schedule <br />impa�sofadding the nu��ectmodi�catimn�othe original project scope and schedule. <br />�.�.4 FUTURLFUNC0ONALOY <br />Future Functionality, when and if provided, will be na|oosod onthe same timeline asthe functionality <br />is made generally available to customers under a maintenance agreement with Tyler. Qacustomer <br />requires that such functionality becommitted towithin the contract, the functionality wiN be treated <br />asocustom modlficut�mn,payable bythe customer. <br />Please reference the Functional Requirements onthe following pages. <br />B <br />� (Ily Qf South Bend, IN <br />