Skip to main content

Main navigation

  • Documents
  • Search

User account menu

  • Log in
Home
Nashua City Data

Breadcrumb

  1. Home
  2. Finance Committee - Agenda - 10/18/2017 - P60

Finance Committee - Agenda - 10/18/2017 - P60

By dnadmin on Mon, 11/07/2022 - 10:19
Document Date
Wed, 10/18/2017 - 00:00
Meeting Description
Finance Committee
Document Type
Agenda
Meeting Date
Wed, 10/18/2017 - 00:00
Page Number
60
Image URL
https://nashuameetingsstorage.blob.core.windows.net/nm-docs-pages/fin_a__101820…

1.7 Severity Level Definitions
The following severity level definitions will be used to determine the maximum response
times:

Severity
Level Severity Definition

| Severity 1 This is defined as a failure that causes the system and/or infrastructure a loss of

: voice functionality and no work-around or. immediate solution is available.

The following are examples of this kind of failure:

° 33% of call processing resources impaired
e Site Environment alarms:

o Smoke,

e Unauthorized access

o Temperature

o Power failure

Severity 2 This is defined as a fault that causes the system to operate with a continuous
reduction in capacity or functionality of core services (core services include, |
voice, data or network management).

| The following are examples of this kind of failure:

e Less than 33% of call processing resources impaired
e Failure of a single redundant component

Severity 3 This is defined as a fault which reduces the functionality, efficiency or usability of
core services (voice, data and network management) and there is a viable work-
around in place.

The following are examples of this kind of severity:
e Intermittent faults that are infrequent and minor impact to core
services
* Statistical reporting problems

| Severity 4 This is defined as a minor issue, which has littie or no impact on the functionality,
efficiency or usability of core services. The following are examples of this kind of

severity:

* Faults resulting in minor functions or features being unsupported
or unreliable in ways that are not noticeable to the user.

» Faults that have no impact in how the user perceives the sysiem
to work.

« Cosmetic issues.
Requests for information.
Preventive Maintenance

Approved by Motorala Contracts and Compliance Saplember 2013 i Motorola 2013

Page 6 of 7

Page Image
Finance Committee - Agenda - 10/18/2017 - P60

Footer menu

  • Contact