Skip to main content

Main navigation

  • Documents
  • Search

User account menu

  • Log in
Home
Nashua City Data

Breadcrumb

  1. Home
  2. Finance Committee

Finance Committee

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P68

Monitored Elements Table

Communication Path

Master Site Infrastructure RF Site Equipment Dispatch Site Equipment
Servers & Backup Servers (| Channels Consoles
MOSCAD (digital inputs & MOSCAD (digital AIS Servers
RS232 serial alarms) inputs & RS232 serial
alarms)
TRAK RF Site Operator Position (OP)

Si si gh SABA EL RE a BRIE RAW

Core LAN Switch

Switch

Motorola Gold Elite
Gateway (MGEG)

Packet Data Gateway (PDG)

Site Controller

Call Processor

Protocol (NTP)

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P67

o Faults that have no impact in how
the user perceives the system to
work

o Intermittent issues
o Requests for information

o Preventive Maintenance or upgrade
related work

Connectivity Matrix

Request connectivity 8 weeks in advance of service start date

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P66

The event types are based on the defined levels as follows:

Appendix A

Engagement Matrix

Severity
Level

Severity Definition

Engagement Times

1

This is defined as a critical/major incident
that causes the system and/or
infrastructure to experience a loss of call
processing functionality and no work-
around or immediate solution is available.

The following are examples of this kind of
failure:

o 33% of call processing resources
impaired

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P65

1.6.4.2 Repair Verification Preference and procedure
1.6.4.3 Database and escalation procedure forms.

1.6.4.4 Submit changes in any information supplied to Motorola and included
in the CSP to the CSM.

1.6.5 Provide the following information when initiating a service request:
1.6.5.1 Assigned system ID number
1.6.5.2 Problem description and site location
1.6.5.3 Other pertinent information requested by Motoroia to open a Case.

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P64

1.4.3.1 Emergency on-site visits required to resolve technical issues that cannot
be resolved by with SSC working remotely with the local customer
technical resource.

1.4.3.2 System installations, upgrades, and expansions.

1.4.3.3 Customer training.

1.4.3.4 Hardware repair and/or exchange.

1.4.3.5 Network security services.

1.4.3.6 Network transport.

1.4.3.7 Information Assurance.

1.4.3.8 Any services not expressly included in this statement of work.

1.4.4 Reference the event catalogue tc confirm monitored equipment.

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P63

wera oe ee

Network Monitoring Overview

Motorola's Network Monitoring Operations (NMO) within the Motorola Solutions Support
Center (SSC) provides real-time fault monitoring for radio communications networks on a
continuous basis. NMO utilizes sophisticated tools for remote monitoring and event
characterization of your communications networks. When an event is detecied, NMO
technologists acknowledge and assess the situation, and initiate a defined response.

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P62

November 2015

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P61

2.1. Severity Level Response Time Commitments
The response times are based on the defined severity levels as follows:

[SeverityLevel|

Response Time

Severity 1

A Motorola SSC Technician will make contact with the customer technical
| representative within one hour of the request for support being logged in

the issue management system. Continual effort will be maintained to
restore the system or provide a workaround resolution. Response
provided 24 x 7.

Severity 2

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P60

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

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

By dnadmin on Mon, 11/07/2022 - 10:19
  • Read more about Finance Committee - Agenda - 10/18/2017 - P59

1.5.8

Determine, in its sole discretion, when a case requires more than the
Technical Support services described in this SOW and notify customer of an
alternative course of action.

1.6 The Customer has the following responsibilities:

1.6.1

1.6.2

1.6.3

1.6.4

1.6.5

1.6.6

1.6.7

1.6.8

1.6.9

Provide Motorola with pre-defined information prior to contract start date
necessary to complete Customer Support Plan (CSP).

Pagination

  • Previous page ‹‹
  • Page 1523
  • Next page ››
Subscribe to Finance Committee

Footer menu

  • Contact