My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2025-220
CBCC
>
Official Documents
>
2020's
>
2025
>
2025-220
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/27/2025 12:06:40 PM
Creation date
10/27/2025 12:04:31 PM
Metadata
Fields
Template:
Official Documents
Official Document Type
Agreement
Approved Date
10/07/2025
Control Number
2025-220
Agenda Item Number
9.S.
Entity Name
Communications International
Subject
Public Safety Communications System Maintenance Agreement
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
40
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).
View images
View plain text
10. Response Time. <br />Severity Level 1 outage is defined as <br />24x7x365 <br />Severity Level 1 <br />a complete system failure or a critical <br />First response within thirty <br />(Major Failures) <br />malfunction that causes: <br />(30) minutes to remotely <br />iagnose and attempt to resolve <br />otal loss of system functionality, or <br />he problem. <br />Inability to perform mission -critical <br />ve on-site within two (2) <br />operations, or <br />ours, if necessary. <br />Severe degradation of performance <br />that renders the system effectively <br />usable, such as a reduction in <br />channel capacity of 25% or more. <br />This includes (but is not limited to): <br />System crashes or hangs with no <br />available workaround. <br />Data corruption or loss of access to <br />essential data. <br />etwork or infrastructure failures <br />ffecting multiple users or locations. <br />Security breaches or vulnerabilities <br />requiring immediate mitigation. <br />24x7x365 <br />Severity Level 2 (Moderate Severity) <br />Within thirty (30) minutes to <br />everity Level 2 <br />outage is defined as a partial system <br />remotely respond to the <br />ZydeFate <br />allure or a significant issue that: <br />problem. Arrive on site <br />arhites)Degrades <br />system performance or <br />within four (4) hours, if <br />functionality, but <br />necessary. <br />Does not prevent core operations from <br />continuing, and <br />Has a workaround available, though it <br />inconvenient or inefficient. <br />ludes (but is not limited to): <br />ance issues impacting specific <br />or non-critical components. <br />Lailures <br />affecting a limited number of <br />locations. <br />errors that interrupt secondary <br />s but not mission -critical <br />
The URL can be used to link to this page
Your browser does not support the video tag.