My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2017 044 Ordinance
DOcument-Host
>
Mayfield Village
>
Ordinances Resolutions
>
2017 Ordinances
>
2017 044 Ordinance
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/19/2018 4:11:46 PM
Creation date
9/11/2018 5:50:21 AM
Metadata
Fields
Template:
Legislation-Meeting Minutes
Document Type
Ordinance
Number
044
Date
12/18/2017
Year
2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
73
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
deployed in ASTRO system releases covered by this SUS. Motorola does not control <br />when these updates are released, but current release schedules are listed for <br />reference: <br />McAfee Antivirus definitions- Weekly <br />Microsoft PC and Server OS patches -Monthly <br />Solaris, RHEL OS, VMware hypervisor patches -Quarterly <br />3.2 Each assessment will consist of no less than 36 hours of examination time to <br />evaluate the impact each update has on the system. <br />3.3 Testing of updates to verify whether they degrade or compromise system <br />functionality on a dedicated ASTRO test system with standard supported <br />configurations. <br />3.4 Address any issues identified during testing to support functionality by working with <br />Motorola selected commercial supplier and/or Motorola product development <br />engineering team. If a solution for the identified issues cannot be found, the patch <br />will not be posted on Motorola's site. <br />3.5 Pre-test STIG recommended remediation when applicable. <br />3.6 Release all tested updates to Motorola's secure extranet site. <br />3.71nclude documentation for installation, recommended configuration changes, and <br />identified issues and remediation for each update release. <br />3.8 Include printable labels for customers who download the updates to CD's. <br />3.9 Notify customer of update releases by email. <br />3.10 A supported SUS ASTRO release matrix will be kept on the extranet site for <br />reference. <br />4.0 The Customer has the following responsibilities: <br />4.1 Provide Motorola with pre-defined information prior to contract start date necessary <br />to complete a Customer Support Plan (CSP). <br />4.2 Submit changes in any information supplied in the Customer Support Plan (CSP) to <br />the Customer Support Manager (CSM). <br />4.3 Provide means for accessing pre-tested files (Access to the extranet website). <br />4.4 Deploy pre-tested files to the customer system as instructed in the "Read Me" text <br />provided. <br />4.5 Implement remediation(s) on customer system, as determined by Motorola. <br />4.6 Upgrade system to a supported system release as necessary to continue service. <br />4.7 Adhere closely to the System Support Center (SSC) troubleshooting guidelines <br />provided upon system acquisition. A failure to follow SSC guidelines may cause the <br />customer and Motorola unnecessary or overly burdensome remediation efforts. In <br />such case, Motorola reserves the right to charge an additional service fee for the <br />remediation effort. <br />4.8 Comply with the terms of the applicable license agreement between the customer <br />and the non-Motorola software copyright owner. <br />System Upgrade + Maintenance Services 9.30.13.doc 3 <br />Motorola Contract No. <br />
The URL can be used to link to this page
Your browser does not support the video tag.