Search

VV WV

Proposed traffic control plan.
Proposed methods for handling sewage flows from upsteam drainage areas.
Proposed methods for handling flow from sewer service connections during

construction of the sewer main.

>» Provisions the Contractor shall take in order to be able to immediately address
unforeseen backups that may occur in services during work on the project.

> The Contractor’s Work Plan shall comply with the following:

The Contractor shall provide access to local residents and businesses at all
times.

The main line sewer shall be reconnected and in service after work hours. By-
pass pumping over night and on weekends and holidays shall not be allowed.
The Contractor shall advise residents and businesses in advance and in writing
of any impact to utility services.

Methods proposed for maintaining flow in sewer mains and service
connections shall be described in detail, and shall have been proven by
successful use in similar past projects.

The trench shall be plated after work hours, and the work area shall be open to
traffic.

Temporary trench patch shall be placed on Friday of every work week prior to
weekend traffic usage.

Y. AVOIDING PIPE AND CATCH BASIN CONFLICTS WITH EXISTING UTILITIES

The Contractor shall excavate the trench for catch basins and associated pipe laterals in
advance of laying pipe in order to determine whether any utility interferes with the

proposed alignment of pipelines and/or location of catch basins. Any adjustments
required to avoid utility conflicts shall be approved by the Engineer prior to installation.
The Contractor shall have on hand several different 4’ diameter barrel sections for
possible adjustment to catch basin depth.

2022 Sewer Replacement Project

Nashua, NH

SC - 8 of 8

November 2015

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.

The terms and conditions of this Statement of Work (SOW) are an integral part of Motorola's
Service Agreement or other applicable agreement to which it is attached and made a part
thereof by this reference.

1.0 Description of Network Monitoring Services

Network Monitoring is a service designed to electronically monitor elemenis of a
communication system for events, as set forth in the Monitored Elements Table. When the
SSC detects an event, (based on the severity of the event) trained technologists
acknowledge and remotely diagnose the event, and initiate an appropriate response in
accordance with the customer handling procedure. Appropriate responses could include, but
are not limited to, continuing to monitor the event for further development, attempting remote
remediation via engagement of Technical Support resources, or initiating dispatch’ of a Fieid
Servicer for onsite remediation.

1.1 Availability

Network Monitoring service is available 24 hours a day, 7 days a week. Network Monitoring
availability is based on the level of coniracted service and defined in the Customer Support
Pian (CSP).

1.2 Geographic Availability

Network Monitoring is a globally provided service unless limited by data export control
regulations. Timeframes are based on the customer's local time zone.

1.3 Inclusions

Network monitoring service can be delivered on Motorola sold infrastructure as stated in
Monitored Elements Table,

1.4 Limitations and Exclusions

1.4.1. Does not include monitoring of anything outside of the radio network or
monitoring of infrastructure provided by a third party, unless specifically
stated. Monitored elements must be within the radio network and capable of
sending traps to the Unified Event Manager (UEM).

1.4.2 Additional support charges above and beyond the contracted service
agreements may apply if it is determined that system faults were caused by
the customer making changes fo critical system parameters.

1.4.3 The following activities are outside the scope of the Network Monitoring
service, but are optional services that are available to remote Network
Monitoring customers at an additional cost:

Approved by Motorola Solutions LGA&C 11/12/2014 1 Motorola 2015

Page 2 of 8

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.

1 Dispatch service with OnSite Response Is a separate service that Is required with Network Monitoring,

1.5 Motorola has the following responsibilities:

1.5.1. Provide dedicated connectivity through a network connection necessary for
monitoring communication networks. The Connectivity Matrix further describes the
connectivity options.

1.5.2 If determined necessary by Motorola, provide Motorola owned equipment for
monitoring system elements. If Motorola installs or replaces Motorola owned
equipment, the type of equipment and location installed is listed in the
Motorola Owned & Supplied Equipment Table.

1.5.3 Verify connectivity and event monitoring prior to system acceptance or start
date.

1.5.4 Monitor system continuously during hours designated in the CSP in
accordance with the pre-defined times specified in section 1.6.2 below.

1.5.5 Remotely access the customer's system to perform remote diagnosis as
permitted by customer pursuant to section 1.6.4.

1.5.6 Create a case, as necessary. Gather information to perform the following:
1.5.6.1 Characterize the issue
1.5.6.2 Determine a plan of action
1.5.6.3 Assign and track the case to resolution.

1.5.7 Cooperate with customer to coordinate transition of monitoring responsibilities
between Motorola and customer as specified in section 1.6.13 and 1.6.13.1.

1.5.8 Maintain communication with the customer in the field as needed until
resolution of the case

1.6 The Customer has the following responsibilities:
1.6.2 Allow Motorola continuous remote access to enable the monitoring service.

1.6.3 Provide continuous utility service to any Motorola equipment installed or
utilized at customer's premises to support delivery of the service.

1.6.4 Provide Motorola with pre-defined customer information and preferences prior
to Start Date necessary to complete the CSP, including, but not limited to:

1.6.4.1 Case notification preferences and procedure

Approved by Motorola Solutions LGA&C 11/12/2014 = Motorola 2015
Page 3 of 8

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.

1.6.6 Notify the SSC when customer performs any activity that impacts the system.
(Activity that impacts the system may include, but is not limited to, installing
software or hardware upgrades, performing upgrades to the network, or taking
down part of the system to perform maintenance.)

1.6.7 Allow Servicers access to equipment (including any connectivity or monitoring
equipment) if remote service is not possible.

1.6.8 Allow Servicers access to remove Motorola owned monitoring equipment upon
cancellation of service.

1.6.9 Provide all customer managed passwords required to access the customer's
system to Motorola upon request or when opening a case to request service

support or enable response to a technical issue.

1.6.10 Pay additional support charges above and beyond the contracted service
agreements that may apply if it is determined that system faults were caused
by the customer making changes to critical system parameters

1.6.11 Obtain all third party consents or licenses required to enable Motorola to
provide the monitoring service.

1.6.12 Cooperate with Motorola and perform all acts that are reasonable or
necessary to enable Motorola to provide the services described in this SOW.

1.6.13 Contact Motorola to coordinate transition of monitoring when monitoring
responsibility is to be transferred to or from Motorola. (1.e. normal business
hours to after-hours monitoring) as set forth in pre-defined information
provided by customer CSP.

1.6.13.1 | Upon contact, customer must provide customer name, site id, status
on any open cases, severity level, and brief description of case and action

plan to Motorola.

1.6.14 Acknowledge that cases will be handled in accordance with the times and
priorities as defined in the Event Definition table- Appendix A.

1.6.15 Cooperate with Motorola and perform all acts that are reasonable or
necessary to enable Motorola to provide the Network Monitoring service.

Approved by Motorola Solutions LGA&C 11/12/2014 is Motorola 2015
Page 4 of 8

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

o Remote Site/sub-system severed
o Site Environment alarms:

o Smoke

o Unauthorized access

o Temperature

o Power failure

Response provided 24 hours, 7
days a week, including US
Holidays.

This is defined as a moderate/minor
incident 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:

o Less than 33% of call processing
resources impaired

o Failure of a single redundant
component

Response provided 8 x 5 on
standard business days, which is
normally Monday through Friday
8AM to 5PM, excluding US
Holidays.

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

Response provided 8 x 5 on
standard business days, which is
normally Monday through Friday
8AM to 5PM, excluding US
Holidays.

Approved by Motorola Solutions LGA&C 11/12/2014

> Matorala 2015
Page § of 8

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

a . Set up and
System Type i Connectivity Maininpancel
ASTRO® 25 internet VPN Motorola
ASTRO® 25 T1 Motorola
Motorola Owned & Supplied Equipment Table
Equipment Type Location Installed
Firewall/Router Master Site ~~
| Service Delivery Management Server Master Site for each Zone
Approved by Motorala Solutions LGA&C 11/12/2014 « Motorola 2075

Page 6 of 8

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)

Radio Network Gateway Router Logging Replay Station
(RNG) (only within the RNI)

Zone Database Server (ZDS) Site Ambassador (AMB)
Gateway Router Gateway Router Client Station
Controller — Zone & Domain | Network Time Voice Processing Module

(VPM)

Converter (only the
converter, not the
legacy sites)

Firewall Manager Servers Firewall MCC 7500 IP Logging
Recorders
Air Traffic Router (ATR) SmartX Site MCC 7100 (only within the

RNI)

Unified Event Manager
(UEM)

Zone Statistical Server (ZSS) |

APSARA SN MLO tN Ae anbeN nah atin: MQ AMR NER

Install Server

“Some or ail of the above equipment may be monitored depending on system configuration and need. Other

equipment (not listed) may be monitored as an option, consuit with your Customer Support Manager for details.

Approved by Matorola Solutions LGA&C 11/12/2014

2 Motorola 2015
Page 7 of 8

August 2016

MOTOROLA SOLUTIONS Preventive Maintenance

Annual Preventive Maintenance Statement of Work — Level 1

The terms and conditions of this Statement of Work (SOW) are an integral part of Motorola's Service
Agreement or other applicable agreement to which it is attached and made a part thereof by this
reference.

Annual Preventative Maintenance will provide an annual operational test and alignment, on the
customer's infrastructure equipment (infrastructure or Fixed Network Equipment or “FNE”) to
monitor the Infrastructure’s conformance to specifications, as set forth in the applicable attached
Exhibit(s), all of which are hereby incorporated by this reference.

1.1 Scape

Annual Preventive Maintenance will be performed during standard business hours (unless otherwise
agreed to in writing). If the system or Customer requirements dictate this service must occur outside
of standard business hours, Motorola will provide an additional quotation. Customer is responsible
for any charges associated with unusual access requirements or expenses.

1.2 Inclusions

Annual Preventive Maintenance service will be delivered on Motorola sold infrastructure including
integrated third party products per the level of service as defined in Table 1: PM Tasks Performed.

1.3. Limitations and Exclusions

Unless specifically described in Table 1, the following activities are outside the scope of the Annual
Preventive Maintenance service, but are optional services that are available to Annual Preventive
Maintenance customers at an additional cost:

1.3.1. Emergency on-site visits required to resolve technical issues.
1.3.2. Third party support for equipment not sold by Motorola as part of the original
system.
1.3.3. System installations, upgrades, and expansions.
1,3.4. Customer training.
1.3.5. Hardware repair and/or exchange.
1.3.6. Network security services.
1.3.7. Network transport.
1.3.8. Information Assurance.
1.3.9. Motorola services not included in this statement of work.
1.3.10. Any maintenance required as a result of a virus or unwanted intrusion is excluded if
the system is not protected against these security threats by Motorcla’s Pre-tested
Security Update Service when applicable.
1.3.11. Tower climbs, tower mapping analysis or tower structure analysis
1.4 Motorola has the following responsibilities:

1.4.1 Notify the customer of any planned system downtime needed to perform this

Service,
1.4.2 Advise customer of any issue that requires immediate attention.

1.4.3. Maintain communication with the customer as needed until completion
{“resolution” implies a problem is being fixed} of the Annual Preventive
Maintenance.