Laserfiche WebLink
1'VI~T®~~L~6 5~~UTIDN$ <br />1.14 As system releases become available, Motorola will provide up to once in a two-year period the <br />following software design and technical resources necessary to complete system release upgrades: <br />1.14.1 Review infrastructure system audit data as needed. <br />] .14.2 Identify additional system equipment needed to implement a system release, if <br />applicable. <br />l .14.3 Complete a proposal defining the system release, equipment requirements, installation <br />plan, and impact to system users. <br />1.14.4 Advise Customer of probable impact to system users during the actual field upgrade <br />implementation. <br />1.14.5 Program management support required to perform the system upgrade. <br />1.14.6 Field installation labor required to perform the system upgrade. <br />1.14.7 Upgrade operations engineering labor required to perform the system upgrade. <br />1.15 ASTRO 25 SUA II pricing is based on the system configuration outlined in Appendix B. This <br />configuration is to be reviewed annually from the contract effective date. Any change in system <br />configuration may require an ASTRO 25 SUA II price adjustment. <br />1.16 The ASTRO 25 SUA II applies only to system release upgrades within the ASTRO 25 7.x <br />platform. <br />1.17 Motorola will issue Software Maintenance Agreement ("SMA") bulletins on an annual basis and <br />post them in soft copy on a designated extranet site for Customer access. Standard and optional <br />features for a given ASTRO 25 system release are listed in the SMA bulletin. <br />2.0 Upgrade Elements and Corresponding Party Responsibilities <br />2.1 Upgrade Planning and Preparation: All items listed in this section are to be completed at least 6 <br />months prior to a scheduled upgrade. <br />2.l .1 Motorola responsibilities <br />2.1. ] .1 Obtain and review infrastructure system audit data as needed. <br />2.1.1.2 Identify additional system equipment needed to implement a system release, if <br /> applicable. <br />2.1.1.3 Complete a proposal defining the system release, equipment requirements, <br /> installation plan, and impact to system users. <br />2.1.1.4 Advise Customer of probable impact to system users during the actual field <br /> upgrade implementation. <br />2..1.1.5 Inform Customer of high speed intetnet connection requirements. <br />2.1.1.6 Assign program management support required to perform the system upgrade. <br />2.1.1.7 Assign field installation labor required to perform the system upgrade. <br />2.1.1.8 Assign upgrade operations engineering labor required to perform the system <br /> upgrade. <br />2.1.1.9 Deliver release impact and change management training to the primary zone <br /> core owners, outlining the changes to their system as a result of the upgrade <br /> path elected. This training needs to be completed at least 12 weeks prior to the <br /> scheduled upgrade. This training will not be provided separately for user <br /> agencies who reside on a zone core owned by another entity. Unless <br />ASTRO 25 System Upgrade Agreement II SOW <br />March 28, 2016 <br />19 <br />