Laserfiche WebLink
D.I.6.7.1 Approval Process for Incorporation <br />Customizations and interfaces provided by Tyler Development staff become part of the general release of <br />the system. Contract Customizations and interfaces as well as post- contract programming changes follow <br />a formal Customization /Change Process. A Product Manager and the Vice - President of Development <br />evaluate each post- contract request for development quote. A written response is submitted to the City <br />evaluating the feasibility of the request, whether a solution is covered at no charge or involves a fee, an <br />estimated time frame for completion and the applicable MUNIS General Release version. We attempt to <br />provide a programming solution that has the ability to be used with parameters and settings to allow for <br />subsequent use and broad appeal. <br />D.I.6.7.2 Impact of Modification/Interface Delivery on Implementation <br />As code changes will be delivered approximately six (6) months after applicable project phase inception <br />there are certain logistics that must be factored into the project plan to accommodate this process. If <br />customizations require upgrading to a new release, plans must be made to introduce the new release into a <br />test environment and conducting thorough cross- module testing, especially for modules already in live <br />production. The City owns this testing and all of these activities must be carefully coordinated with other <br />ongoing phases of implementation. <br />D.I.6.7.3 Installation <br />At the time of software installation, the most current product available will be installed, but will not <br />contain the customizations ordered by the City. Customizations will be developed as part of the <br />implementation as defined in this Statement of Work. <br />D.I.6.7.4 Project Release Schedule <br />Customizations are delivered through Tyler Munis Internet Update utility to be loaded against releases in <br />accordance with Tyler's published release life cycle policy (see Appendix 1.1.4). This is done in order to <br />predict and schedule release upgrades during the planned implementation phases and to provide the <br />assurance of continually operating on a fully supported release for live modules. As such, the following <br />upgrade schedule will need to be followed to ensure timely delivery of agreed to go -live customizations: <br />Munis Release <br />Target Test System Deployment <br />Target Live System Deployment <br />Version 10.4 (General Availability) <br />Upon installation <br />Upon installation <br />Version 10.5 (General Availability) <br />April 2014 <br />April 2014 <br />1111111,1111 63 bii?2111111! <br />All customizations are listed in Exhibit 6. The following customizations have been identified as required <br />for go -live: <br />• Compa- Ration Modification <br />• Proration of LTD premiums Modification <br />• Worker Comp Modification <br />CITY OF SAN MARCOS, TX PAGE 38 OF 62 <br />ERP PROJECT- FINAL SOW <br />