Laserfiche WebLink
Agreement for HdL Services Exhibit A — Scone of Services <br />1.5.2. Support Policy Regarding Reports - HdL will assist with modifications to <br />reports as needed during the term of this agreement. Typical report modifications <br />require 7 to 10 business days to complete. Very complex reports or reports <br />required in a very short time frame may incur development costs, in which case <br />an estimate will be provided for approval before the work is begun. <br />1.5.3. Software Upgrades - Except to the extent that upgrades of the software include <br />new modules or features not previously offered as part of the software as of the <br />date hereof, City is entitled to upgrades of the software within the terns of this <br />Agreement. Though rare, additional costs may apply depending on the extent of <br />the upgrade. Potential additional costs include training, consulting, configuration, <br />or other requested services. Additional charges must be mutually agreed to by <br />both parties prior to being invoiced <br />1.5.4. Software Maintenance - Software updates are typically available every two <br />months, with 5 to 6 software releases each year. The City's primary support and <br />IT contacts will be notified when an update is available, and City IT will be <br />responsible for downloading and applying the update. Most updates are optional, <br />allowing the City's primary support contact to determine if the updates included <br />are of interest to warrant an update. In the event that HdL releases a patch for a <br />critical vulnerability, the City will be notified that a priority update is available <br />and should be installed at the City's earliest convenience. HdL technical support <br />staff are available to assist with software update rollouts as required. <br />1.5.4.1.Delayed update cycle — The City may opt to take part in a delayed update <br />cycle. With this option, the City will only receive an update after it has <br />been deployed in production use amongst other HdL clients for at least <br />three months. This provides a potentially more stable release plan, at the <br />expense of delayed access to updates. Any City decision to take part in <br />any delayed update cycle shall be conveyed by written notice to HdL for <br />each instance. <br />1.5.5. Outside Connections to HdL Database - HdL programs rely on the integrity of <br />the database to operate properly. As such, it is critical that any outside connection <br />to the database be implemented with HdL's full knowledge and participation. <br />Only "read only" connections will be established to the HdL database. No <br />modifications will be made to the HdL database, including database/table design <br />and data content. Any repair work necessary due to violations of the above items <br />will not be covered by the Software Use Fee, and as such will be billable to the <br />client on a time and material basis. CITY shall contact HdL for instructions if any <br />added functionality is required, including reading additional data or writing to the <br />HdL database. <br />1.6. System Requirements — CITY will deploy the HdL system directly (On site) on CITY's <br />equipment in their VMWare Virtual Server environment. <br />1.6.1. On site deployment — The software and database will be installed on CITY's <br />network on hardware supplied by CITY. Any specifications provided below <br />indicate minimum requirements. It is CITY's responsibility to ensure that any <br />hardware used to host the software/database or run the client application meets the <br />specifications dictated by the operating system and any software/services hosted <br />by the hardware. For example, minimum operating system specifications will not <br />be sufficient if the file server is also hosting CITY's email system. <br />REV: 02-28-19 PR <br />ATTY/AGR.2019.049/HDL Prime Business License & TOT Software <br />