Motorola Technical Original

Table of Contents
Section 1. Executive Summary ______________________________________________1-1

Section 2. Required Signed Forms ___________________________________________2-1
Section 3. Point-by-Point Response __________________________________________3-1
Section 4. Customer References _____________________________________________4-1
Section 5. ASTRO 25 System Description _____________________________________5-1
5.1 ASTRO 25 Fixed Network Equipment Design _________________________________ 5-2
5.1.1 Zone Core _____________________________________________________________________ 5-2
5.1.2 Integrated Voice and Data (IV&D) System Description _________________________________ 5-5
5.1.3 ASTRO 25 Prime Site Design______________________________________________________ 5-8
5.1.4 RF Site Overview ______________________________________________________________ 5-10
5.1.5 MCC7500 ASTRO 25 Dispatch Console ____________________________________________ 5-14
5.1.6 On-site Digital P25 Repeaters at Jail and Prison ______________________________________ 5-18
5.1.7 MIP 5000 Jail Dispatch Console___________________________________________________ 5-19
5.1.8 MC1000 Desktop Control Stations_________________________________________________ 5-19
5.1.9 Fire Station Alerting (FSA) ______________________________________________________ 5-22
5.1.10 Regional Interoperability with Surrounding Agencies________________________________ 5-23
5.1.11 Hot Stand-by Microwave System _______________________________________________ 5-24
5.2 ASTRO 25 System Features _______________________________________________ 5-28
5.2.1 Simulcast ____________________________________________________________________ 5-28
5.2.2 700/800 MHz Operation _________________________________________________________ 5-28
5.2.3 Centralized System Management __________________________________________________ 5-29
5.2.4 Vocoder-Based Encryption_______________________________________________________ 5-29
5.2.5 ASTRO 25 Trunking Call Services_________________________________________________ 5-30
5.2.6 Network Management System ____________________________________________________ 5-31
5.2.7 MCC7500 System Description ____________________________________________________ 5-45
5.2.8 MIP 5000 Dispatch Console ______________________________________________________ 5-96
5.2.9 ISSI Interface ________________________________________________________________ 5-101
5.2.10 MC1000 Desktop Handset ____________________________________________________ 5-103
5.2.11 ASTRO 25 System Failure Mode Analysis _______________________________________ 5-104
5.3 ASTRO 25 System Options_______________________________________________ 5-114
5.3.1 Transportable Trunked Repeater (Site on Wheels)____________________________________ 5-114
5.3.2 Mobile Repeaters (Digital Vehicular Repeater System) ________________________________ 5-117
5.3.3 InterZone System Connectivity compared to ISSI.1___________________________________ 5-119
5.3.4 Dual Prime Site Option_________________________________________________________ 5-124
5.3.5 Supplemental Rural RF Coverage Site Options ______________________________________ 5-125
5.4 P25 PH1 Trunked System Feature Matrix __________________________________ 5-126
Floyd County, Georgia

Project 25 Digital Public Safety Radio Network
RFP# 101216
December 16, 2010
Table of Contents -1-

5.5 Subscriber Radios _______________________________________________________5-131
5.5.1 End User Radios Proposed ______________________________________________________ 5-131
5.5.2 Features of All Proposed Motorola Radios _________________________________________ 5-132
5.5.3 APX Portable and Mobile Radios ________________________________________________ 5-134
5.5.4 XTS/XTL Portable and Mobile Radios ____________________________________________ 5-144
5.5.5 Control Stations ______________________________________________________________ 5-149
5.5.6 Minitor V Pagers _____________________________________________________________ 5-150
5.5.7 Customer Programming Software (CPS) ___________________________________________ 5-151
5.1 Diagrams ______________________________________________________________ 5.1-1
Section 6. Functional Acceptance Test Procedures _____________________________ 6-1
In-Field Draft6.1 Wide Area Trunking - FDMA Only Sites _____________________________6-1
6.1 Wide Area Trunking - FDMA Only Sites _________________________________________6-2
6.1 MCC 7500 Features ______________________________________________________6-49
6.2 System Management Tests _________________________________________________6-95
6.3 Radio Control Manager (RCM) Features____________________________________6-121
6.4 Report Generation Tests__________________________________________________6-133
6.5 System Reliability Features _______________________________________________6-137
6.6 Fault Management Features ______________________________________________6-149
6.7 Integrated Voice and Data (IV & D) ________________________________________6-158
6.8 MOSCAD Fault Management System ______________________________________6-169
6.9 Site Trunking – _________________________________________________________6-188
FDMA Only Sites ______________________________________________________________6-188
6.10 Analog Conventional Tests________________________________________________6-198
6.11 ISSI.1 Network Gateway _________________________________________________6-206
6.12 Wide Area Trunking Features _____________________________________________6-212
6.13 Signoff Certificate _______________________________________________________6-215
Section 7. Coverage Acceptance Test Plan ____________________________________ 7-1
7.1 Overview ________________________________________________________________7-1
7.1.1 CATP Definitions_______________________________________________________________ 7-3
7.1.2 CATP Method _________________________________________________________________ 7-4
Section 8. Coverage Description_____________________________________________ 8-1
8.1 Coverage Description and Modelling _________________________________________8-1
8.1.1 Coverage Maps_________________________________________________________________ 8-1
8.1.2 Hydra Overview ________________________________________________________________ 8-1
8.2 Summary ________________________________________________________________8-7
Section 9. Statements of Work ______________________________________________ 9-1
9.1 Systems Integration Statement of Work _____________________________________ 9.1-1
9.1.1 Systems Integration Overview ___________________________________________________ 9.1-1

RFP# 101216
-2- Table of Contents

9.1.2 Project Management ___________________________________________________________ 9.1-3
9.1.3 Integration Management - System Implementation Work Plan __________________________ 9.1-8
9.1.4 System Training _____________________________________________________________ 9.1-31
9.1.5 System Programming and Optimization ___________________________________________ 9.1-32
9.1.6 Functional Acceptance Testing__________________________________________________ 9.1-32
9.1.7 Coverage Acceptance Testing___________________________________________________ 9.1-33
9.1.8 Summary___________________________________________________________________ 9.1-36
9.1.9 Change Order Plan ___________________________________________________________ 9.1-36
9.1.10 Preliminary Project Schedule_________________________________________________ 9.1-36
9.2 Site Development Statement of Work 9.2-1

9.2.1 Civil Work __________________________________________________________________ 9.2-1
9.2.2 Site Development at Leonard Road Site ____________________________________________ 9.2-4
9.2.3 Site Development at Fouche Gap Site _____________________________________________ 9.2-8
9.2.4 Site Development at Cave Spring Site ____________________________________________ 9.2-11
9.2.5 Site Development at Hillindale Site ______________________________________________ 9.2-15
9.2.6 Site Development at Shannon Site _______________________________________________ 9.2-21
9.2.7 Site Development at Blossom Hill Site____________________________________________ 9.2-25
9.2.8 Site Development at Rocky Mountain Site_________________________________________ 9.2-31
9.2.9 Site Development at Taylor’s Ridge (NWGA) Site __________________________________ 9.2-32
9.2.10 Site Development at Floyd County 911 Site _____________________________________ 9.2-36
9.3 System Migration and Cutover Plan ________________________________________ 9.3-1
9.3.1 Overview ___________________________________________________________________ 9.3-1
9.3.2 Subscribers __________________________________________________________________ 9.3-1
9.3.3 Designing an Effective Fleetmap and Flexible Talkgroup Structure ______________________ 9.3-1
9.3.4 Programming and Distributing Radios _____________________________________________ 9.3-2
9.3.5 Maintaining Operations During Cutover ___________________________________________ 9.3-2
9.3.6 Dispatch ____________________________________________________________________ 9.3-2
9.3.7 Trunking Infrastructure_________________________________________________________ 9.3-2
9.3.8 Fire & EMS Station Alerting Conventional Infrastructure ______________________________ 9.3-3
9.3.9 Floyd County Jail _____________________________________________________________ 9.3-3
9.3.10 Conclusion ________________________________________________________________ 9.3-4
9.4 Motorola Project Team Resumes ___________________________________________ 9.4-1
9.5 Subcontractor Profiles ___________________________________________________ 9.5-1
9.5.1 Coosa Valley Communications___________________________________________________ 9.5-1
9.5.2 Ceragon Networks ____________________________________________________________ 9.5-1
9.5.3 United Tower Co., LLC ________________________________________________________ 9.5-3
9.5.4 MACTEC ___________________________________________________________________ 9.5-4
9.5.5 Motorola Service Partners ______________________________________________________ 9.5-7
9.6a Project Schedule Summary_______________________________________________ 9.6a-1
9.6b Project Schedule _______________________________________________________ 9.6b-1
Section 10. Training ______________________________________________________10-1
10.1 Overview_______________________________________________________________ 10-1
10.2 Courses Proposed _______________________________________________________ 10-1
10.2.1 System Administrator ________________________________________________________ 10-2
10.2.2 Technical Maintenance Training ________________________________________________ 10-4
10.2.3 Console End User Training ____________________________________________________ 10-6
10.2.4 Radio End User Training ______________________________________________________ 10-7

RFP# 101216
December 16, 2010
Table of Contents -3-

10.3 Course Descriptions _____________________________________________________10-10
10.3.1 Bridging the Knowledge Gap for ASTRO 25-System Administrator Course _____________ 10-10
10.3.2 ASTRO 25 IV&D System Networking (w/labs) ___________________________________ 10-11
10.3.3 ASTRO 25 IV&D Trunked System Overview (M Core still in development) ____________ 10-13
10.3.4 ASTRO 25 IV&D Introduction to Radio System Administration ______________________ 10-14
10.3.5 ASTRO 25 IV&D Radio System Administration Workshop _________________________ 10-16
10.3.6 ASTRO 25 IV&D Telephone Interconnect _______________________________________ 10-17
10.3.7 ASTRO® 25 IV&D ISSI.1 Network Gateway Overview ____________________________ 10-18
10.3.8 Point-to-Point Overview _____________________________________________________ 10-19
10.3.9 ASTRO 25 IV&D with M Core Workshop _______________________________________ 10-20
10.3.10 ASTRO 25 IV&D IP Based Digital Simulcast ____________________________________ 10-22
10.3.11 ASTRO 25 IV&D –GTR 8000 Repeater Site Workshop ____________________________ 10-24
10.3.12 MCC7500 Dispatch Console __________________________________________________ 10-26
10.3.13 MOSCAD NFM Programming, Maintenance and Operator __________________________ 10-28
10.3.14 APX CPS Programming and Template Building___________________________________ 10-29
10.3.15 APX Technical Subscriber Academy ___________________________________________ 10-31
10.3.16 MCC7500 Supervisor _______________________________________________________ 10-32
10.3.17 MCC7500 Operator _________________________________________________________ 10-33
10.3.18 MIP5000 Console Operator___________________________________________________ 10-35
10.3.19 APX7000 Portable and APX7500 Mobile Train-the-Trainers_________________________ 10-37
10.3.20 ASTRO 25 Mobile and Portable Train-the-Trainers ________________________________ 10-39
10.3.21 CCSA IP-10/IP-10G class curriculum ___________________________________________ 10-41
10.3.22 Ceragon Training Agenda ____________________________________________________ 10-44
Section 11. Warranty and Customer Support __________________________________ 11-1
11.1 System Warranty ________________________________________________________11-1
11.2 Warranty Services________________________________________________________11-2
11.2.1 Network Monitoring Service ___________________________________________________ 11-2
11.2.2 Security Monitoring Service ___________________________________________________ 11-3
11.2.3 Security Update Service ______________________________________________________ 11-4
11.2.4 Dispatch Service ____________________________________________________________ 11-4
11.2.5 OnSite Infrastructure Response _________________________________________________ 11-5
11.2.6 Network Preventative Maintenance______________________________________________ 11-6
11.2.7 Technical Support ___________________________________________________________ 11-6
11.2.8 Infrastructure Repair Service with Advanced Replacement ___________________________ 11-7
11.2.9 Software Maintenance Agreement (SMA) ________________________________________ 11-7
11.2.10 Subscriber Support __________________________________________________________ 11-8
11.3 Summary _______________________________________________________________11-8
11.4 Post Warranty Maintenance Services ________________________________________11-8
Section 12. Pricing _______________________________________________________ 12-1
Section 13. Contractual Documentation ______________________________________ 13-1
Communications System Agreement _________________________________________________________1
Section 14. Product Literature ______________________________________________ 14-1
Section 15. Appendix _____________________________________________________ 15-1

RFP# 101216
-4- Table of Contents

Proposal for

RFP # 101216
Project 25 Digital Public Safety Radio

Network
December 16, 2010
Technical Proposal
Data Restrictions
This proposal is considered Motorola confidential and restricted. The proposal is submitted with the restriction that it is to be used for
evaluation purposes only, and is not to be disclosed publicly or in any manner to anyone other than those employed by Floyd County,
Georgia required to evaluate this proposal without the express permission of Motorola. MOTOROLA and the Stylized M Logo are registered
in the U.S. Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2010
1700 Belle Meade Ct., Lawrenceville, GA 30043

This page left intentionally blank.
Section 1. Executive Summary
Please see attached Executive Summary

RFP# 101216
December 16, 2010
Executive Summary 1-1


RFP# 101216
December 16, 2010
1-2 Executive Summary

B
City of Rome and Floyd County, Georgia
P25 Digital Public Safety Radio Network
Request for Proposal
Executive Summary
The City of Rome and Floyd County share the common vision for a
public safety communications network that will provide an enhanced
level of coverage reliability and interoperability to support public safety
and public service personnel. As reflected in your RFP specifications,
the City of Rome and Floyd County are formally endorsing the following
key elements for your new public safety communications network:
Commitment to
.....the consolidation of communications technology and facilities
guaranteeing seamless interoperability between the City and
County and the efficient delivery of public safety and first
responder resources.
.....the public safety and public service personnel within Floyd

County; endorsing a mission critical communications lifeline that
provides both enhanced radio coverage and audio quality.
.....the community by ensuring radio coverage throughout schools

and other critical buildings thereby supporting public safety’s
ability to respond effectively and safely.
.....the long term protection of your investment, which is ensured

through the P25 open architecture. Motorola’s software driven
platform guarantees a migration path to future capabilities that
eliminates the requirement for the “forklift” upgrades of the past.
..…the regional interoperability between Floyd County first

responders with adjacent municipal and county jurisdictions.
There is much more to making a system work effectively for the
user than just using the Project 25 interface. Simply put, not all
Project 25 systems are created equal. Motorola has combined
years of incremental improvement, product evolution, and an
unwavering focus on the details to ensure our systems work when
you need them. Not only does the Motorola ASTRO 25 network
meet the P25 standard, but the system performance has been
perfected over decades of experience deploying regional and
statewide systems that ensure optimal performance.
2
PROPOSED SYSTEM DESIGN
P25 Open Standard Infrastructure

Motorola is proposing a P25 Open Standard 700 / 800 MHz Digital Trunked
system. The system provides a Common Air Interface that allows all
users with Project 25 compliant radios in the 700 and 800 MHz bands to
interoperate regardless of the radio manufacturer. The proposed design
includes the following components and equipment:
Rome-Floyd System Design

+ Eight (8) site, ten (10) channel linear IP simulcast digital trunked infrastructure
+ Leveraging three (3) existing sites and constructing five (5) new sites
+ Robust, redundant loop Microwave network
+ 1,342 end-user subscribers
+ Redundancy Features:
+ Zone Controller
+ Core Network
+ Prime Routers, Switches, and Frequency Standard
+ Remote Routers, Switches, and Frequency Standard
+ Console site Routers and Switches
+ Loop/Star Protected Microwave
+ 48 VDC Charger-Rectifier and Battery Bank
Dispatch Consoles
Eleven (11) MCC7500 IP console positions provide both a forward-looking solution for the
P25 Open Standard system as well as supports new flexibility for existing conventional
systems. The console also provides a state of the art graphical user interface for the dispatch
professional.
Mobile and Portable Radios

Designed specifically for law enforcement, firefighters, emergency medical, military, and
federal agencies, Motorola Project 25 digital radios are the preferred tool of life-saving
professionals. The proposed radios are capable of the most advanced wireless technology
available today, including features such as dual band (700/800 MHz) operation, FDMA/
TDMA dual access capabilities, a robust number of operating modes to enable radio user
interoperability, and over-the-air-programming (OTAP) to facilitate radio management.
Motorola offers several Project 25 subscriber models allowing the City of Rome and Floyd
County the opportunity to select the radio price points and radio features appropriate for
each user.
3
EXPERIENCE: PROVEN TRACK RECORD = LOWER RISK
Not just any company can implement an advanced network of the scale
Floyd County requires and get it right; Motorola’s experience allows us
to exceed your expectations in critical areas as highlighted throughout
our proposal.
Our proposal reflects compliance to the RFP specifications with

special attention to coverage, interoperability, redundancy &
reliability, and future capacity & growth.
Motorola understands the critical importance of coverage to the City of Rome

and to Floyd County. Our design supports your desired level of coverage, which
has been carefully predicted based on decades of experience designing, building,
and delivering two-way radio communications in demanding environments similar
to Floyd County.
Regional interoperability starts with first responders and how compatible

their subscribers perform while on one another’s systems. When roaming to a
neighboring system, unfamiliar functions and sounds can create confusion for the
users, inhibiting the effectiveness of a response. Emergency response efforts
within the region can benefit from deploying a technological platform that is
consistent with other local and regional neighboring systems statewide.
As noted in the RFP, the reliability and hardening of communications network

infrastructure is of critical importance to combat potential acts of vandalism and
regional natural and environment hazards such as fires, floods, and tornadoes. The
Motorola ASTRO solution provides a robust mission critical network with multiple
elements of redundancy to ensure system performance and delivery of your
customer specific capabilities during the most critical times.
Motorola’s proposal directly addresses the RFP requirements for

future capacity and growth on all infrastructure. The City and County
are currently licensed for an adequate number of channels to support current
operational requirements as well as to support future growth. The Motorola
ASTRO solution supports expansion capabilities up to 30 channels per site and
offers easy software migrations to incorporate future P25 standard interfaces
such as Phase 2 TDMA. The Motorola solution is immediately capable of 700/800
MHz operation guaranteeing future expansion utilizing 700 spectrum as it
becomes available.
4
Motorola has designed, manufactured, and installed hundreds of
successful large-scale networks for statewide communications as well
as a host of locally installed and accepted systems. Several of these
local and regional systems are comparable to the scope of the system
proposed. We guarantee that our solution will meet your acceptance
testing requirements and meet your overall system needs.
Towns Rabun
Catoosa Fannin
Dade Murray Union
Whitfield Habersham
Gilmer White
Walker
Lumpkin
Stephens Cobb / UASI Regional System
Chattooga Gordon Pickens Hart
Dawson BanksFranklin
Hall
CherokeeForsyth
Bartow Jackson Madison Elbert
Tennessee Valley Regional Floyd
Radio System Oconee Area Regional Radio System
Barrow Clarke
Polk Cobb Gwinnett Oglethorpe OARRS
Paulding Oconee Lincoln
Wilkes
Haralson De Kalb Walton
Douglas Columbia
Rockdale Greene Taliaferro
Fulton Clayton Morgan McDuffie
Carroll Newton
Warren Richmond
Henry Independent Countywide
Fayette Jasper Putnam
Hancock Glascock 800Mhz Trunked Radio Systems
Coweta Butts
Heard Spalding
Jefferson Burke
Western Area Regional Radio System Pike
Lamar
Baldwin
Meriwether Jones Washington
WARRS Troup Monroe
Jenkins
Upson Screven
Bibb Wilkinson
Johnson
Crawford Twiggs Emanuel
Harris Talbot
Peach Bulloch
Taylor Laurens Effingham
Bleckley Treutlen Candler
Muscogee
Houston
Marion Macon Montgomery Evans
Chattahoochee Pulaski Bryan
Schley Chatham
Dodge Wheeler Toombs
Dooly Tattnall
Columbus Regional System Stewart Sumter
Wilcox
Webster Telfair Liberty
Crisp Jeff
Appling Long
Quitman Terrell Lee Ben Hill Davis
Turner
Randolph Wayne McIntosh
Irwin Coffee Bacon
Clay Calhoun Dougherty
Tift Pierce
Worth Glynn
Early Baker Berrien Atkinson Brantley
Colquitt Ware
Mitchell Cook
Area 2 / Albany Regional System Miller Lanier Camden
Thomas
Clinch Charlton Southeast Ga Regional
Seminole Brooks Lowndes
Decatur Grady
Radio System
Echols SEGARRN
Local Experience and Commitment

Our experience and success is only achieved through the careful up-front selection
of these partners, rigorous oversight of their work, and the integration of their team
members as part our core project team. Motorola requires our partners to meet the
same standards we apply to ourselves. We involve our subcontractors in Statement
of development, and clearly identify the subcontractor’s role in the design, schedule
resources, and service level agreements.
5
COVERAGE
The need for enhanced portable radio coverage and audio quality is a key driver behind the Rome/
Floyd P25 project.
The Motorola ASTRO proposal will meet and exceed your current radio coverage requirement for
DAQ 3.4 portable on street and DAQ 4.0 mobile coverage to extend throughout 95% area within
the geographic borders of Floyd County. Motorola’s proposed ASTRO P25 system also guarantees
portable radio communications within the 176 critical buildings located throughout Floyd County
as designated by the City and County. The Motorola proposal further takes into consideration your
future P25 Phase 2 expansion and is designed to meet your Phase 2 coverage expectations.
As noted in your RFP: “The most important aspect of any public safety radio network is coverage
reliability coupled with clearly understood audio quality delivered to users throughout their various
working environments.” Motorola’s linear simulcast design will deliver the required coverage and
audio quality demanded by the City and County public safety agencies.
Motorola’s Coverage Advantage - Linear Simulcast Modulation

Motorola’s P25 digital narrowband system will provide unparalleled coverage in critical buildings
and throughout Floyd County. This will be accomplished using Linear Simulcast Modulation (LSM)
technology. In order to provide more efficient use of the available radio spectrum, APCO’s Project 25
Phase I digital standard requires the use of narrowband 12.5 kHz channels. Without the use of linear
simulcast techniques, narrowband channels have a smaller tolerance for dealing with interference in
overlapping areas. This can reduce the actual usable signal thereby decreasing coverage. More sites
may also be required to achieve the same coverage as a wideband system. To address this issue,
Motorola invented LSM. Motorola is the only company with LSM currently implemented for
Project 25. It provides an excellent technical foundation for guaranteeing a high level of coverage
performance and audio quality throughout Floyd County.
6
PROFESSIONAL PROJECT MANAGEMENT
Project management is the application of knowledge, skills, tools, and techniques to address our
customer’s contractual requirements. To this end, there are nine practices that are key to project
management, highly interrelated, with each as important as the others:
• Scope management
• Schedule and time management
• Cost management
• Quality management
• Risk management
• Subcontracts and procurement management
• Resources management
• Communications management
• Integration management (System Implementation Work Plan)
Local Motorola Service Shop (MSS)

Motorola will utilize our experienced system technologists supported by Coosa Valley
Communications to provide field installation, optimization, subscriber unit programming, and
warranty support. Our MSS personnel will be fully involved in the system implementation,
integration, and cutover. Motorola and Coosa Valley Communications’ collective commitment to
the Floyd County project will ensure your overall satisfaction.
Local Experience and Commitment

Our experience and success is only achieved through the careful up-front selection of these
partners, rigorous oversight of their work, and the integration of their team members as part
our core project team. Motorola requires our partners to meet the same standards we apply to
ourselves. We involve our subcontractors in Statement of development, and clearly identify the
subcontractor’s role in the design, schedule resources, and service level agreements.
7
SYSTEM IMPLEMENTATION
Motorola will commit to a 17-month system implementation of the
proposed ASTRO P25 Mission Critical Communications Network.
The proposed Motorola implementation plan reflects opportunities to accelerate
the required 18 month project schedule. The Motorola ASTRO technology platform
is ready to ship today. The Motorola team of project implementation experts will
ensure a timely and efficient deployment allowing for a rapid transition to the new
network. This commitment to an enhanced deployment will ensure that the users
have access to the enhanced system deliverables as quickly as possible.
Detailed System Engineering

Motorola’s Project Engineer will be responsible for system design and
performance. The Project Engineer will oversee all coverage analysis, Acceptance
Test Plan (ATP) development, preparing for path and frequency coordination,
developing site design parameters, and system programming parameters for the
City of Rome and Floyd County. Additionally, the Project Engineer will participate
in the system staging process and will be available to assist the City and County in
determining subscriber unit configurations.
System Integration
Systems Integration is a key process in Motorola system implementations and
in the way we do business. Motorola’s Systems Integration process will be used
to effectively address the requirements of the City of Rome and Floyd County.
This complex system solution proposal requires a high degree of technical
coordination and attention to the smallest details. The Motorola team has a
tremendous track record delivering sophisticated communications solutions on
time and on budget.
8
PROVEN TECHNOLOGY & SYSTEM INTEGRATION
Motorola has been delivering P25 compliant IP-based trunked systems sinces 2001.
Motorola has deployed more regional and statewide systems - includingg 243 P25 trunked
systems - than any other vendor with a 100% system acceptance rate. W We are the
vendor of choice for 32 of the 37 statewide systems currently in place aand the ONLY
vendor with contractually complete, customer accepted 700/800 MHz P25 P compliant
systems in place and operational today that reflect a similar size and scoope to your
specific network requirements. Our extensive P25 system implementatioon experience
will translate into a smooth and expedient implementation for the Floyd County project.
Simply put, Motorola continuously earns our customer’s confidence throough our ability
to implement these complex systems in a timely and cost-conscious manner.
APX 6000
Single-band operation
SMARTNET/SMARTZONE
P25 Phase 1 FDMA
P25 Phase 2 TDMA
Dual microphone
Single speaker
Smallest Phase 2 TDMA radio
9
PROJECT 25 AND BEYOND
FUNCTIONALITY BEYOND P25
Motorola has refined the operation of our wide-area trunked radio networks to provide the most
reliable and highest-quality mission-critical voice communications available. There is much more to
making a system work effectively than just using the Project 25 interface. Simply put, not all Project
25 systems are created equal. Years of incremental improvement and product evolution, combined
with an unwavering focus on the details, means our systems will work in the moments that matter
most. Not only does the Motorola ASTRO 25 network meet the P25 standard, but the system
performance has been perfected over decades of experience deploying wide area systems ensuring
optimal performance. Motorola specific features include:
Voice Priority
Motorola’s ASTRO P25 system provides voice priority over data so that emergency calls are not
missed due to a data operation such as Over-The-Air Programming. In a Motorola P25 network,
critical voice calls ALWAYS have priority. Other vendor’s networks cannot deliver this same feature.
Emergency Preemption
Motorola’s system will pass an emergency through right away, even if all the system channels are
busy with other voice traffic. Other systems do not offer the ability to pre-empt an existing call to
ensure an emergency gets through right away, instead users on those systems have to wait for a
voice channel to become available — wasting precious time in an emergency.
Regional Interoperability
Many regional partners that interact with Rome/Floyd during emergency response efforts use
Motorola P25 systems today or are in process of migrating to a Motorola P25 system. As Rome/
Floyd looks to maximize regional interoperability, a Motorola P25 system provides the greatest
overall value. With regional consistency across network platforms and end-user radios, first
responders will know exactly how their radios will work during critical mutual aid scenarios. No
matter the response situation, radio system performance will be second nature to the user. Second
guessing coverage reliability or radio performance during critical moments is NOT an option.
10
WHY MOTOROLA FOR ROME/FLOYD?
Motorola’s unique combination of unmatched experience, proven
technology, APX radios, and local partners make us the best
value, lowest risk decision for Rome/Floyd. We look forward to
the opportunity to deliver Rome/Floyd’s vision of a state of the
art standards-based communications solution to serve the needs
of the City of Rome and Floyd County agencies and support the
regional plan for many years to come!
EXPERIENCE + TECHNOLOGY + LOCAL PARTNERS

= GREATER VALUE & LOWER RISK
11
11
MOTOROLA HELPS PEOPLE BE THEIR BEST IN THE MOMENTS THAT MATTER.
MORE COVERAGE DESIGN EXPERIENCE, GUARANTEED

MORE IMPLEMENTATION SUCCESS
MORE INVESTMENT IN NEXT GENERATION ARCHITECTURE
MORE INVESTMENT IN STANDARDS
MORE GEORGIA AGENCIES RELY ON MOTOROLA
MORE BENCH STRENGTH
MORE EQUIPMENT CONFIGURATIONS, OPTIMIZED FUNCTIONALITY
MORE SERVICE & MAINTENANCE CENTERS
MORE SUSTAINABILITY.
Section 2. Required Signed Forms
As required by this RFP, Motorola has provided the following documents and forms
in this section.
Required Signed Forms

Bid Bond
Certificate of Assistant Secretary, Motorola, Inc.
Delegation of Authority
Proposal Authorization Form
Non-Collusion Affidavit
Contractor Affidavit and Agreement
Certificate of Ethics
Certificate of Non-Discrimination
Floyd County Board of Commissioners Drug-Free Workplace Certificate
MACTEC Engineering and Consulting, Inc. Subcontractor Affidavit
United Tower Company Subcontractor Affidavit
Coosa Valley Communications Subcontractor Affidavit
Ceragon Networks Subcontractor Affidavit

RFP# 101216
December 16, 2010
Required Signed Forms 2-1

Floyd County, Georgia Motorola Confidential Restricted

Project 25 Digital Public Safety Radio Network Use or disclosure of this proposal is
RFP# 101216 subject to the restrictions on the title page
December 16, 2010
2-2 Required Signed Forms

Section 3. Point-by-Point Responses
In compliance with the RFP, we are providing this section to aid Floyd County’s
evaluation of our Proposal.

RFP# 101216
December 16, 2010
Point-by-Point Responses 3-1


RFP# 101216
December 16, 2010
3-2 Point-by-Point Responses

Section 3. Point-by-Point Response
The following pages contain Motorola’s response to the Floyd County, Georgia Turnkey
Community Wide 800/700 MHz Digital Trunking (P25) Simulcast System RFP #
101216.
Motorola Confidential Restricted Floyd County, Georgia

Use or disclosure of this proposal is Project 25 Digital Public Safety Radio Network
subject to the restrictions on the title page December 16, 2010
Point-by-Point Response 3-1


December 16, 2010 subject to the restrictions on the title page
3-2 Point-by-Point Response

1.0 General Proposer Response Provisions

1.1 Purpose

This Specification encompasses a turnkey project to provide the County of Floyd, Georgia with
an APCO P-25 compliant new 800MHz digital simulcast trunked radio network capable of
meeting current and future communication needs, both reliably and functionally. County public
safety agencies, as well as some Floyd County governmental departments, are utilizing a
combination of existing VHF and UHF conventional analog technology that is outdated and
capacity limited, which is no longer meeting the communication objectives of the County.
Understood
A key desire of Floyd County is to transition away from channel inefficient solutions and to
embrace new, emerging radio technology that is in full compliance with Industry-recognized open
standards. A second, critically important aspect of this communications network
procurement involves infrastructure reliability and hardening in response to heightened
terrorism activities, worldwide, and to regional natural and environmental hazards such as
winter type snow or ice storms and tornadoes.
Understood
This Specification defines key functional and technical aspects of a standards-based
enhanced digital radio communications network, aligned toward full Project-25 compliance
within a fixed time period. Public Safety agencies that will immediately utilize this new
digital radio network include the County Fire, Police, and EMS, as well as many of the
Floyd County municipal departments. It is envisioned that other, non-public safety agencies will
likewise participate in this new digital radio network.
Understood
Floyd County recognizes that the most important aspect of any public safety radio network is
coverage reliability coupled with clearly understood audio quality delivered to users
throughout their various working environments. Floyd County appreciates the need for
Proposers to have adequate flexibility in these Specifications, such that proposed solutions can
be technically optimized to meet user desires and coverage expectations. Accordingly, this
Specification does not define a required use of any specific 800MHz antenna site
placement, antenna system hardware or minimum number of sites to achieve the desired
coverage performance. That is, these Specifications are designed to functionally describe user
expectations, reliability and the Floyd’s desire for near-term APCO Project-25 infrastructure
compliance.
Understood
Interoperability between Floyd County first responders and other adjacent municipal and
county jurisdictions is another area of concern that is addressed by these Specifications.
Understood


Floyd County is also aware that the voluntary development and user adoption of APCO
Project-25 open-standards has been a laboriously slow one. APCO Project-25 standards
develop commenced nearly eighteen years ago and has only has recently achieved the
ratification of switch interconnectivity standards for networks. Additionally, it is recognized that
final development of narrowband Project-25 Phase-II 6.25KHz specifications is nearing
completion.
Understood
Due in large part to the protracted development of Project-25 standards, vendor development of
high-capacity voted/simulcast Project-25 infrastructure solutions (necessary to provide reliable
in-building portable radio support) has been slow and has not achieved the same degree of
competitive availability as exists for VHF/UHF conventional Project-25 needs. Fortunately,
the federal government’s desire for all military and federal agency radio networks to
transition to Project-25 narrowband technologies has fueled both the standards- completion
process and has accelerated development of complex network infrastructures, inclusive of
simulcast technology, by the radio vendor community.
Understood
Following the federal government’s lead, it is perceived that significant and tangible
improvements to local-area 700/800MHz operations as well as wide area interoperability can
be achieved, minimally, through the application of Project-25 technologies. This
Specification addresses those functional, operational, and to a limited extent, technical
requirements for Floyd's envisioned new Project-25 digital radio communications network.
Understood

1.2 Instructions

This Specification is a complete document and must be returned intact as well as
any addenda, which are released subsequent to the issuance of this Specification package.
The RFP Authorization Form in Section 16 must be completed. The Appendices do not
need to be returned. All responses and attachments should be placed into the RFP
Response immediately behind the page, on which the information was requested, in the
form of a point-by-point response. Supplementary material may not be substituted for
direct responses to questions.
Per Addendum 1, released October 21, 2010:
Question:
1. Will the County accept point-by-point responses submitted following each paragraph in lieu of
each page as long as the vendor responds to the RFP in its entirety? Alternatively, will the County
allow the vendors to alter the RFP so that requirements that currently are broken apart from one
page to the next fall entirely on one page?
Response: Yes, this is acceptable.
Harris Question:
1. Section 1.2 contains instructions on the format of the response. Inserting responses immediately
after each RFI Specification page may detract from the flow of the information and is a manually
intensive process. May we submit our responses in the more commonly used format of inserting


our response after each point?
Response:
In addition, may we include attachments to each section as necessary (i.e., coverage maps,
drawings, etc.)?
Response: Yes, this is acceptable.
Comply
If supplementary materials are inserted, each inserted page must be labeled in the bottom
margin with the number of the Specification page behind which it is being placed. If more than
one page is inserted behind a particular Specification page, then each must be labeled with the
appropriate page number plus a letter designator, e.g. 121a, 121b, 121c, etc.
Comply
1.2.1 Procurement Process
Floyd County has determined that the procurement of a high technology 800MHz trunked
radio network shall be accomplished by response to these Specifications rather than through the
receipt of unsolicited proposals. Responses in the form of a unsolicited proposal or of a type
that offer technology solution approaches other than those ultimately resulting in minimally
a Project-25 Phase I compliant network will be rejected without further consideration.
Understood
Proposer Responses must be adequate to cover all expenses related to compliance with all
applicable requirements of this Specification. Any related costs, direct or indirect, must be
clearly identified in the Proposal Response. All cost related to the preparation or submittal of
the response to this Specification is the responsibility of the Proposer.
Understood
1.2.2 The Proposal Process
1.2.2.1 Proposal Release
The Proposal will be publicly advertised and released in accordance with applicable Floyd
County Procurement policy and State of Georgia laws and shall include the notification of the
time and place when and where the Proposal is due. Additionally, these Specifications may be
directed to those businesses that are known to be a potential offerer of goods or services of the
type required.
Understood


1.2.2.2 Pre-Proposal Conferences
Floyd County and Consultant will hold one mandatory Pre-Proposal Conference with
potential Proposers concerning the requirements. This Conference will be held at the Floyd
County Administration Building at a date and time to be determined. Any verbal
agreements or representations made at this Conference or at any other time during the
Proposal period will not be binding on Floyd County. Official statements concerning the
Proposal will be issued in writing as an RFP Specification Addenda.
Understood
1.2.2.3 Proposal Questions
If during the review or preparation of the Proposal submittal, a Proposer discovers any
errors, omissions or ambiguities, they should submit, in writing, their questions to the
Consultant. Written questions that are submitted at least 48-hours in advance of the Pre-
Proposal Conference will be addressed during the Conference. Written questions submitted after
this time period will be addressed in a written addendum to the Floyd County
Procurement Department, forwarded to the Consultant and if received by the Consultant at least
seven days prior to the Proposal Submission Date. Direct contact with any Floyd County
public safety or local government departments concerning this Proposal must have prior
approval as identified in Section 1.9.
Understood
Failure to follow this contact procedure may result in Proposer disqualification.
Understood
1.2.2.4 Late Proposal Submission
Any Proposal Response submitted after the specified submission due date and time, as
publicly advertised, will not be accepted and will be returned unopened to the submitting
organization. Any Proposal Response may be withdrawn by the Proposer prior to the
scheduled Proposal Submission Date.
Understood
1.2.2.5 Proposal Submittal
All copies of the Proposal, in the indicated quantities and including all requested materials,
should be provided to the address listed below by the date specified in Proposal
Advertisement or as may be amended by addendum:
Purchasing Director, Floyd County Administration Building, Suite 106
#12 East Fourth Avenue
Rome, GA 30161
Comply


Proposal Response submittals shall be valid for a period of one hundred and twenty days (120)
days after Proposal submission date. Exceptions taken on any part of the stated functional or
operational requirements, particularly to those that directly relate to coverage reliability and
delivered audio quality, may disqualify the Proposer.
Comply
1.2.2.6 Proposer Qualifications
Floyd County reserves the right to discontinue consideration of a Proposer’s submittal if

information requested on the Proposer’s ability to perform is not submitted or is otherwise
unacceptable. Floyd County may, at any time prior to Contract Award, request proposal
clarification information submitted on other similar systems or the specific hardware/software
solution. Proposers shall not be allowed to enhance, add/remove services or otherwise alter
their proposal configuration submittal beyond that described in their initial Proposal response.
Understood
Floyd County may enter into discussions with qualified Proposers concerning their
submission during the proposal evaluation process. These discussions will be closed to third
parties including other Proposers, unless such discussions are prohibited by the State of
Georgia’s Law. During these discussions, clarifications or minor corrections to their
Proposal Submittals, with the exception to price charges, will be considered, as appropriate,
within Floyd County, Georgia’s Procurement Policy.
Understood
Proposer(s) may be disqualified if there is reason to believe that: some form of collusion exists
between Proposers; the Proposer is involved in litigation with Floyd County; and the Proposer is
not performing on another contract of similar scope or has previously defaulted on another
City/County contract, within the last five years.
Understood
1.2.2.7 Recommendation
After all qualified Proposals have been evaluated, the Consultant and Floyd's Radio Project
Committee (FRPC) will provide to Floyd County an evaluation of all responsive proposals and
a written recommendation. Proposal response submittals will not be publicly released until
Floyd County has authorized the granting of a Contract to the responsive and best Proposer.
Understood


1.2.2.8 Contract Award
Upon notification of Contract Award, the Contractor shall provide Performance and
Payment Bonds and Proof of Insurance as set forth herein. Failure to provide the required
bonds or proof of insurance within ten (10) days after notification of Contract Award shall
entitle Floyd County to rescind the award and retain any Proposal security. If Floyd County then
must re-advertise the project because of this failure to timely execute the Contract, the defaulting
party shall not be eligible to submit a subsequent Proposal response.
Comply
Motorola will comply with the following clarifications:
Remove the words “and Proof of Insurance” and “or Proof of Insurance” as Motorola will
provide a Certificate of Insurance as evidence within three business days of an executed contract.
Floyd County shall authorize award of the Contract to the best responsive Proposer that is
compliant with these Specifications. No Contract shall be binding on Floyd County until it has
been approved as to form by the County’s Legal Counsel and executed by both
responsible parties (Floyd County and Contractor).
Understood
A Pre-Construction Conference will be held at which time all required Contractor
documents must be submitted. Upon Floyd County's approval of these documents, a Notice to
Proceed will be issued to the Contractor.
Understood
1.2.2.9 Proposal Response
The Proposal Response shall be divided into three sections: Technical, Infrastructure Pricing and
User Equipment Pricing. Twelve (12) copies of the Technical Response and six (6) copies of
the Infrastructure and Subscriber Equipment Pricing Responses are to be submitted. The
Pricing Responses shall be separated from the Technical Response and independently sealed.
Comply
Each Proposal Response shall be submitted in standard 8 1/2" x 11" three ring binders.
Additionally, Proposers shall also submit their Proposal Response in a digital format
(Portable Data File – PDF- format) on a CD-ROM, placed within the Proposal Response
Binder. The entire Response package must be submitted in a sealed container addressed to:
Purchasing Director, Floyd County Administration Building, Suite 106, #12 East Fourth
Avenue, Rome, Georgia 30161 and identifying the title and RFP Number of the
procurement. The time and date of the Proposal Opening must be plainly marked on the
container as well as the Proposer’s name, address and Georgia Contractor's License
Number. All Proposal Responses should be delivered by hand, with receipt requested, or by
certified or registered mail.
Comply


Any confidential/proprietary information contained in the Proposals must be contained in a
separate section. All Proposal Responses become property of Floyd County. A cover letter
transmitting the Proposal Response must accompany the package.
Comply
1.2.2.10 Proposal Evaluation and Selection by Consultant
Technical and Pricing Proposals shall be evaluated separately using a weighted point system
whereby out of a maximum 100% Overall Project Score, 70% shall be allocated to Technical
Proposal evaluation scores with 30% being allocated to life cycle system cost.
Understood
Technical Proposals will first be evaluated for overall responsiveness and completeness to the RFP
Specifications. Proposals that are determined responsive and complete will be evaluated by
the Consultant.
Understood
Technical Proposals will be graded in the following areas, listed in relative order of
importance, with respect to the requirements as outlined in this RFP:
Understood
1. Performance, compatibility, expansion capabilities and versatility (30%).
Understood
2. Reliability, redundancy and warranty (18%).
Understood
3. Proposer qualifications, history of product support and RFP deviations (10%).
Understood
4. Equipment repair, installation, and implementation (10%).
Understood
5. Interoperability (15%).
Understood
6. Training (7%).
Understood
7. Maintenance and time limit of availability of service parts (6%).
Understood
8. Organization, scope and detail of proposal (4%).
Understood
The scored results of this Technical Evaluation will be multiplied by 0.70, thereby yielding a
weighted technical project-total score. The results of this portion of the Evaluation shall be
submitted to the Floyd Purchasing Department.
Understood


At the direction of the Floyd's Radio Project Committee (FRPC) as to the suitability and
acceptability of the Technical Evaluation Results, the Consultant, will next open and
evaluate costs for each responsive Technical Proposal Submittal.
Understood
The relative cost differences between responsive Cost Proposals shall be compared and
evaluated by simple percentage. The Proposer Submittal receiving the highest Overall
Project Score shall be recommended by the Consultant as being the most responsive, best
proposal. In the case of a tied Overall Project Score, the Consultant shall recommend that
Proposal Submittal having the highest Technical Proposal evaluation score.
Understood
1.2.2.11 Total Costs
Floyd County reserves the right to evaluate total project price on the basis of initial cost and life
cycle analyses. Any deviations by Proposers from the pricing requirements herein shall be
approved in advance of Proposal Submittal or they will be construed as being non-
conforming and the Proposal Submittal will not be given further consideration.
Understood
1.3 Definitions
Definitions as used herein:
(a) Proposer:
Any organization, company, vendor, or supplier responding to this specification.
Understood
(b) Contractor:
The Proposer to whom a Contract is awarded.
Understood
(c) Proposal, Proposal Response, Submittal:
Correspondence or material furnished by Proposers in response to this specification.
Understood
(d)County of Floyd, Georgia, E911: System Owner/Client

Understood
(e)Tusa Consulting Services, TCS or Consultant:
75757 Old Military Road (Hwy 1082) Covington, LA 70435
(985) 249-6467, Telephone (985) 249-6468, Fax
Understood


1.4 Proposer Standards

The Proposer must have manufactured, delivered and installed several radio systems of
equivalent technology (700/800MHz IMBE digital voice simulcast transmit/receiver voted)
having comparable size and scope. Proposer's referenced systems shall be described with
enough information that Floyd County or its Consultant can reasonably determine their
project equivalency. The Proposer shall prepare a summary report for a minimum of three of
the installed and fully operational systems that best emulates that being proposed for Floyd.
These reports should include a detailed summary of the system and its significant operational
features/components as well as a current customer contact including name, address, and
phone number, title, department and system responsibility.
Comply
Motorola exceeds the above stated requirements.
Motorola has deployed more local, regional and statewide systems - including 243 P25 trunked
systems – than any other vendor with a 100% system acceptance rate. We are the vendor of choice
for 32 of the 37 statewide systems currently in place. Motorola is including a significant number (
or we can insert our total count here ) of Project 25 references that reflect comparable size and
scope and many that exceed the size and scope of the proposed Floyd County network. The
references provided reflect key elements required by the Floyd County RFP including 700/800
P25 capabilities, simulcast operation, challenging coverage environment, skillful and timely
implementation and most importantly customer satisfaction. Please refer to Section 4 of the
Technical Proposal for the detailed system summary information.
Radio spectrum allocations now occupied by commercial television broadcast interests
within the 700MHz band have become available solely to public safety operations.
Proposers will likewise be required to provide sufficient information necessary to support
claims that both proposed infrastructures and user equipment will be functionally and
operationally compatible with these new channels (764-767MHz and 773-776MHz, paired with
794-797MHz and 803-806MHz, respectively). Failure to propose equipment capable of
operations on this new spectrum shall be considered non-responsive and that proposal
submittal shall be given no further consideration.
Comply
All Motorola’s proposed infrastructure and user equipment is functionally and operationally
compatible with both 700 and 800 MHz operation, including the new channels (764-767MHz and
773-776MHz, paired with 794-797MHz and 803-806MHz, respectively) without hardware
modification.
Motorola is the only responding radio manufacturer currently offering this capability without
hardware modification. The specification sheets provided in Section 14 provide detailed
documentation.
A factory authorized service center that is fully staffed and trained to support the proposed
infrastructure network, and all related subsystem equipment, must be located within the 100
miles of Floyd County and duly registered and licensed to conduct business within the State of
Georgia to be considered adequate to satisfy initial installation, implementation,
optimization, warranty and ongoing maintenance needs. The Contractor and all
subcontractors, if any, must be able to legally conduct business within the State of Georgia.
Comply


The following standards shall apply, as a minimum, to all equipment, installation methods and
materials:
A. EIA/TIA–Electronic/Telecommunications Association
B. NEC - National Electric Code
C. NEMA - National Electrical Manufacturer's Association
D. IEEE - Institute of Electrical and Electronic Engineers, Inc. E. FCC - Federal
Communications Commission
F. FAA – Federal Aviation Administration
G. NFPA – National Fire Prevention Association
H. Building Codes for Floyd County, Georgia
I. OSHA - Occupational Safety and Health Administration
J. IBC – International Building Codes, Rev. 2009
Understood
1.5 Workmanship

All workmanship must conform to normal and accepted standards for the telecommunications
industry and will be thoroughly examined by Floyd County Representatives and its
Consultant at various stages during project implementation and before final network
acceptance. All fixed site equipment, including electronic communications infrastructure,
dispatch consoles; alarm system consoles, network management consoles, electrical
wiring, towers, antennas, mounts etc. must be installed by or under the supervision of the
Contractor.
Comply
The Contractor must completely remove and properly dispose of residue due to its work,
return the site to a useable state and will be responsible for the cost of repairing all damage
caused by the Contractor or its Sub-Contractors during network installation.
Comply
Floyd County and its Consultant reserve the right to halt the installation process due to poor
workmanship, housekeeping, scheduling, work interruptions, etc. Work halts that have
resulted from poor workmanship shall not relieve the Contractor of their responsibility to
conform to the installation time requirements as stated in this Specification.
Understood


1.6 Materials

All equipment, except with the expressed written permission of Floyd County and its
Consultant, must be new and unused, meet telecommunications industry standards, and,
where applicable, be registered with and approved by the Federal Communications
Commission. Floyd County or its Consultant reserves the right to reject and require the
return, at the Contractor's expense, of any and all components which are defective or fail to
comply with this Specification. Such rejections and/or returns will neither validate nor
invalidate the remainder of the Contract. Rejections of material for cause shall not provide an
extension of time to the Contractor.
Comply
Motorola complies with the following clarification:
Motorola will provide only new equipment to the Customer. In accordance with
established commercial practice, any components, parts or assemblies internal to the
equipment are either new or refurbished in accordance with Motorola’s high quality
standards and will perform like new, are warranted as new, and are not of an age or
condition as to impair their performance, usefulness, and safety. Motorola should
make no representations concerning the raw materials in manufactured goods;
however, under normal installation processes, the installation materials are new when
installation occurs.
1.7 SubContractors

It is intended that a single Contractor have total turnkey responsibility for the project so as to
assure a fully operational network. Therefore, any Proposer desiring to use Sub-
Contractor(s) must include within their Proposal Response a list and description of the
qualified Sub-Contractor(s). Floyd County will require documentation and references,
including a thorough background investigation, to ensure the qualification of a Sub-
Contractor. Any Sub-Contractor or person that is determined by the County to be
unqualified or unacceptable to perform their duties, may at the County's sole discretion, be
barred from working on the project. The Sub-Contractor(s) cannot be changed after
submission of the Proposal Response except with the written permission of Floyd County.
Comply
Please refer to Section 9 of the Technical Proposal (Statement of Work) for the
detailed description of the following qualified subcontractors:
· Microwave- Ceragon
· Architectural and Engineering - MACTEC
· Tower crew- United Tower
· MSS- Coosa Valley


Changes in Sub-Contractors shall not provide an extension of time to the Contractor.
Understood
1.8 Premises Visits

Proposers, before submitting a Proposal Response, may desire to visit selected public safety
premises in order to familiarize itself with conditions, which may affect the work. Floyd, it’s
designated local representative or the Consultant will coordinate access and escort to the
various sites. If more than one visit to a site is requested and time allows, Floyd County
designee will make the necessary arrangements.
Question:
Is the county able to make structural drawings available for the tower at the Shannon Site?
Response: Negative, no structural drawings are available for the tower at the Shannon site.
Proposers are welcome to schedule another site visit to the Shannon site as outlined in section 1.8,
Premises Visits, of the RFP in order to gather the necessary information needed for their
proposals.
Understood
Proposers must indicate any special requirements, i.e., architectural, mechanical, electrical, civil
or structural modifications, that their equipment may need at either County-owned or non
County-owned locations that are intended to be utilized.
Comply
All requirements are identified in the Civil Statement of Work, Section 9.2.
The costs for these special requirements shall be disclosed in the Proposal Submittal as this is a
turnkey project whereby the costs to furnish and install the proposed network infrastructure are
fixed to the Proposal amount.
Comply
1.9 Contact
All contact and inquiry concerning this Specification shall be directed to: Dominic F. Tusa
Tusa Consulting Services, TCS or Consultant:
75757 Old Military Road (Hwy 1082) Covington, LA 70435
(985) 249-6467, Telephone
(985) 249-6468, Fax
Understood


All contact requiring Floyd County input shall be directed to:
Nancy Lam, Purchasing Director, Floyd County Administration Building, Suite 106
#12 East Fourth Avenue Rome, GA 30161 lamn@floydcountyga.org
Understood
1.10 Notification

Proposers will be notified of Floyd's selection according to Floyd County's Procurement
Policy.
Understood
1.11 Installation

1.11.1 Project Time Frame for Completion
The Project's time frame for completion is not greater than eighteen months from the Notice to
Proceed. The Project will not be deemed completed until a fully-compliant Project-25
simulcast infrastructure has been installed; all system functionality, audio quality and
mandatory coverage testing has satisfactorily been completed to the reasonable satisfaction of
Floyd County and their Consultant; and a Certificate of Substantial Completion has been issued
by Floyd.
Comply
Motorola meets and exceeds this requirement.
Motorola’s proposed project schedule supports a 17-month implementation. Further reductions to
the implementation schedule may be realized through the Contract Design Review to be conducted
with Floyd County.
1.11.2 Installation Delays
If, at any time after the Contract Award, the Contractor becomes aware of any problems that may
result in a delay in completing installation and system acceptance, the Contractor must
immediately notify the designated Floyd County Representative and the Consultant by
telephone, with confirmation in writing, citing the cause, probable effect and potential time
delay's duration with recommendations for alternative action. This paragraph does not relieve
the Contractor of contractual responsibilities; however, failure to notify promptly will be a basis
for determining the Contractor negligent of an otherwise excusable delay.
Understood
1.11.3 Installation Damage
The Contractor shall be responsible for the repair of any damage to County property caused by
the Contractor or its Sub-Contractors during installation, implementation, optimization,
maintenance, or de-installation of any equipment or services.
Understood


1.12 Training

Floyd County considers training to be of paramount importance. User and dispatcher
training shall be completed on-site by the Contractor's personnel. Dispatcher training shall be more
extensive than user training and will involve all designated regular and relief dispatchers
employed by the County at the time of system operational testing.
Question:
2. How many “users” need mobile and portable radio training?
Response: Each person will need mobile and portable training the total number the total number
is approximately 1,078.
Question:
3. Does the County have staff with previous two-way radio and training experience that would
accommodate a Train-the-Trainer type format for mobiles and portables?
Response: No
Question:
4. How many Dispatch Supervisors and Operators/Dispatchers need console training?
Response: 32
Per Addendum 3, released November 19, 2010:

Question:
1. Of the 32 Dispatch Supervisors and Operator/Dispatchers, how many are supervisors, and how
many Operator/Dispatchers are at the jail?
The Jail only needs 1 supervisor to receive supervisor console training.
Comply
Detailed user and dispatcher training information and course descriptions are provided in
Training, Section 10.
The Contractor shall provide administrative training for six (6) Communication Network
Managers. Software training shall be provided which will enable these personnel to perform
functionality/feature changes to fixed site equipment and portables/mobiles; poll the
network diagnostics; perform traffic and feature usage studies; etc. It is the desire of Floyd
County that such training is to commence within 30 days upon completion of contract
negotiations and execution, and be completed prior to the Customer Design Review (CDR)
meeting.
Per Addendum 1, released October 21, 2010, Question 5:
Question:
5. Since all technical field training requires a live operational system for training, does the
County want to send the 6 System Managers to Schaumburg, IL for technical Resident training?
Response: No.


If the County is looking for a foundational ASTRO System Manager Overview prior to the CDR,
Motorola would like to ask the County to consider alternative training opportunities. 1) We can
offer a 1-2 day tailored ASTRO Technical Overview, 2) There are two ASTRO System Overview
courses that are offered online/self-paced and can be completed at any time, and 3) With
customer approval, we can offer System Manager Orientation type training on one of the
neighboring ASTRO P25 Systems (e.g. TVRS in Chattanooga, TN, Cobb County, GA, Carroll
County, GA or Forsyth County, GA).
Response: No training prior to the CDR is required.
Comply
Tennessee Valley Radio System (TVRS) has agreed to allow Motorola to host a system
overview/system manager orientation to aide in the preparation for the Customer Design
Review.
The Contractor shall provide comprehensive maintenance training whereby County

service/support personnel are qualified in the proper diagnostic, maintenance and repair
service skills needed to quickly resolve P-25 700/800MHz communications equipment
malfunctions as well as microwave backhaul operational problems. The Contractor shall
provide operational and full maintenance training for all County radio maintenance
personnel, either on site or at remote factory locations. This level of training will be
essentially equivalent to the level of service training required by the Contractor for its
proposed Maintenance Providers. Additionally, the Contractor shall develop and train radio
maintenance personnel in those aspects of maintenance necessary to ensure the highest
availability and reliability of infrastructure and subscriber equipment resources. Preventive
maintenance training shall encompass all elements of supplied infrastructure equipment,
inclusive of standby generator equipment, battery plants, battery charging systems, tower light
systems, site grounding systems, alarm systems and all other subsystems directly or indirectly
related to infrastructure reliability and operations.
Question:
6. How many technicians does the County want trained?
Response: 3
Comply
Detailed comprehensive maintenance training information and course descriptions are provided in
Training, Section 10.
The Contractor shall be responsible for all direct or indirect costs of user, dispatcher,
maintenance personnel and communications network manager training, such as meeting
rooms, travel, lodging and transportation as necessary for County personnel.
Question:


7. Does the County have onsite training rooms available to facilitate training of County staff and
trainers?
Response: Yes, the County does have training rooms available.
Comply
The Contractor agrees that the Consultant and appropriate Floyd County personnel will be
permitted to observe user equipment installation, network implementation and all
optimization/testing phases.
Comply
The Contractor agrees that, upon network system acceptance, designated Floyd County
maintenance personnel shall be provided with security and access codes, which will allow
Floyd County to make routine operational changes and conduct radio profile maintenance. The
Contractor shall continuously notify Floyd County of any computer and radio network software
code revisions and any recommended equipment modifications. All such code revisions,
upgrades and modifications shall be automatically incorporated into the project, through the
commencement of acceptance testing and up to the date of formal system acceptance.
Comply
The Contractor shall coordinate with Floyd County all training sessions. All training must be
approved by the County. Dispatch, users/operators, maintenance personnel and network
manager follow-up training shall be provided and scheduled no more than ninety (90) days after
network acceptance for the purpose of training reinforcement.
Comply

1.13 Parallel Implementation

The new network must be installed in a parallel implementation. That is, infrastructure
equipment will be fully installed and operationally ready before the existing analog voice
system can be decommissioned. The current VHF/UHF conventional analog systems are the
only Public Safety Voice communications systems and must operate 24/7/365. No
interruptions in service of any duration may be allowed without prior approval of the Floyd
County or their designee. Therefore, fully duplicated voice radio systems will coexist for some
period of time. The period of time of parallel installation will be used to perform testing of
operational functionality of the entire network, dispatch consoles, mobiles, portables,
network features, high capacity receiver-voting and simulcast transmitter operations.
After the new network has been tested on a subset of radio channels and later accepted, the
Contractor must remove the existing decommissioned VHF/UHF system mobile equipment,
inclusive of any antenna system components and power/control wiring, as identified and
directed by the Floyd County designee.
Harris Question:
2. Will the County have a designated storage area for the decommissioned equipment or does the
County want the vendor to dispose of the equipment?


Response: The County will have a designated storage area for the decommissioned equipment.
Comply
Since existing dispatch console equipment will potentially control the old system during the
parallel phase, the Contractor is responsible for developing a plan to accommodate both
existing and proposed systems during the parallel and transitional periods of installation and
implementation.
Comply
Detailed migration plans for all subsystems are identified in the Cutover Plan, which is provided
in the Statement of Work, Section 9.

1.14 Manufacturer Support

Proposers shall provide a letter from sub-system manufacturer(s) which guarantees
manufacturer's support in the case of any conditions or problems which can not be remedied by
the Contractor or in case the Contractor defaults on its warranty and/or maintenance
agreements.
Comply
The required letter is provided at the end of this subsection.
1.15 Parts Availability

The Proposer shall provide written guarantee that all proprietary backbone components and
repair parts shall be available for at least fifteen (15) years from the date of network
acceptance. End user equipment (i.e. portables, mobile, etc.) repair parts shall be available for
at least five (5) years from the date of cessation of equipment manufacturer.
Comply
Motorola will use commercially reasonable efforts to provide replacement parts for Motorola
manufactured subscriber equipment for five years and for Motorola manufactured fixed
infrastructure equipment for seven years, both from the date of last manufacture. Motorola
reserves the right to supply either assemblies or piece parts.
Proposers shall fully disclose the end-of-life status of each major equipment grouping
proposed in response to this Specification. That is, end-of-production dates should be
provided, minimally, for base stations, microwave radios, network controllers, power
supplies, dispatch consoles, audio switches, simulcast optimization subsystems and all
models of user equipment. It is the intent, to the maximum extent possible, for Floyd
County to avoid the purchase of any network equipment that is nearing (within 24 months) the
end of its production cycle.


Comply
Motorola will comply with the following clarification:
Motorola is committed to supporting the ASTRO 25 platform for an extended period of time.
Support coverage for the platform is aligned with the typical system lifespan customers’ experience
which often spans across multiple decades. To sustain the platform lifespan, Motorola makes on-
going investments to regularly refresh the underlying components to address normal technology
obsolescence and apply security safeguards. Certain components within the platform are expected
to undergo more regular updates, while others are expected to be available for 10 or more years
from initial availability. A primary goal of technology refreshment is to maximize backward
compatibility with major hardware components to maintain equivalent system functionality, thus
mitigating the need to replace the entire platform.
Motorola will use commercially reasonable efforts to provide replacement parts for Motorola
manufactured subscriber equipment for five (5) years and for Motorola manufactured fixed
infrastructure equipment exclusive of third party IT equipment (e.g. servers, pc’s) for seven (7)
years, both from the date of last manufacture. By making regular system updates, customers can
extend their support period well beyond these timelines.
Although there is no planned end of life date for the ASTRO 25 platform, based on the current
platform roadmap Motorola expects to continue to support ASTRO 25 system releases and
subsystem components through at least the end of 2025. Due to the pace of technology
advancement and standards updates, it is difficult for any technology platform to forecast beyond
5 to 7 years. In the coming years, Motorola will be able to look beyond the 2025 date and will be
able to update our ASTRO 25 customers accordingly with platform support timelines.
1.16 Warranty of Network Performance

In submitting their Proposal Response, the Proposer acknowledges that it has carefully
reviewed the functional requirements and warrants to Floyd County that the 800MHz P-25
radio network installed shall function according to equipment specifications, industry
standards and the minimum operative characteristics specified in Sections 4.0 and 5.0 of this
Specification.
Comply
The Contractor is further responsible for providing radio network coverage as specified in
Section 7.0. All costs incurred in order to comply with the functional, operational and
technical requirements of this Specification shall be the responsibility of the Contractor.
Comply


1.17 Remedies

Remedies shall be negotiated with the apparent responsive and best Proposer, as part of
contract negotiations.
Comply
1.18 Contracts

This Specification and the Proposer’s Response will be an integral part of the Contract. Any and
all statements made in the Proposal Response will automatically become part of the final Contract
for equipment and services. Inability to contractually guarantee any statement made in their
Proposal Response will result in Proposer disqualification.
Comply
Omission in the Proposal Response of any equipment, services or provisions herein
prescribed shall not be construed so as to relieve the Contractor of any responsibility or
obligation necessary to the complete and satisfactory installation of any and all systems,
equipment, and services specified. The network price and any optional prices quoted must
include all equipment, service, features, materials, labor, etc. necessary to make all the
features, services, and equipment, which are included, fully functional. The Proposer agrees that
the cost of additional equipment, materials, or labor necessary to meet these
requirements, which was not otherwise calculated in his Proposal Response, shall be solely at
the Contractor's expense.
Comply
Each Proposal Response must be signed by a duly authorized officer who is empowered to
contractually bind the Proposer.
Comply
Floyd County shall enter into contract negotiations with the apparent responsive and best
Proposer. Should Floyd County be unable to negotiate a Contract with the apparent
responsive and best Proposer, Floyd County may exercise the right to enter into Contract
negotiations with the apparent responsive Proposer having the next-highest evaluation score.
Understood

1.19 NonAppropriation of Funds

In the event no funds or insufficient funds are appropriated and budgeted by the County or are
otherwise unavailable for fulfilling the requirements of the Contract, the obligations of Floyd
County shall terminate on the last day of the fiscal period for which appropriations are received
without penalty or expense to the County of any kind whatsoever. Floyd County will
immediately notify the Contractor or its assignee of such occurrence. In the event of such
termination, Floyd County agrees to peaceably surrender possession of the equipment to the
Contractor or its assignee on the date of such termination. The Contractor will be responsible
for packing all equipment and any freight charges. Floyd County will not cancel if any funds are
appropriated to it, or by it, for the acquisition, retention or operation of the equipment or other


equipment performing similar functions for the current fiscal period in which the termination
occurs or the next succeeding fiscal period thereafter and that it will not during the funding
period give priority to other functionally similar equipment or services. The Contractor
shall covenant and agree to indemnify and hold Floyd County harmless against any loss,
damage liability, cost, penalty or expense, including attorney's fees, which it is not otherwise
agreed to by Floyd County in the equipment Contract and which is incurred and arises upon
a failure of Floyd County to appropriate funds in the manner described herein for a
continuation of the Contract or exercise of the option to purchase the equipment.
Comply
Motorola is providing a general indemnity for performance of the work in its response. Motorola
understands the non-appropriations clause above, however, complies with the understanding that
it does not agree to the following, requests that it is deleted, and Motorola does not understand
why a vendor would have to indemnify a customer for the customer’s failure to have or continue to
have funding: “The Contractor shall covenant and agree to indemnify and hold Floyd County
harmless against any loss, damage liability, cost, penalty or expense, including attorney's fees,
which it is not otherwise agreed to by Floyd County in the equipment Contract and which is
incurred and arises upon a failure of Floyd County to appropriate funds in the manner described
herein for a continuation of the Contract or exercise of the option to purchase the equipment.”
Motorola understands that if funding is not appropriated, the County will have to terminate the
contract. The County will only need to notify Motorola promptly and pay for all equipment and
services up to the date of termination, Motorola will agree to cease work, shipments, and use
reasonable efforts to mitigate any damages caused by an abrupt termination.
1.20 Acceptance

Acceptance testing procedures shall be negotiated with the apparent responsive and best
Proposer as part of Contract negotiations.
Understood

1.21 Purchase Payment Schedule
The following payment schedule shall apply:
10% - at Contract execution.
25% - at delivery of and inventory by Floyd County designee of network
infrastructure components to Floyd County designated location(s).
10% - upon infrastructure installation completion.
25% - upon satisfactory completion of audio quality and range coverage testing.
15% - upon issuance of subscriber equipment and satisfactory completion of all
training.
15% - upon Final System Acceptance.
Comply
Motorola reserves the right to make partial shipments of equipment and to request
payment upon shipment of such equipment. In addition, Motorola reserves the
right to invoice for installations or civil work completed on a site-by-site basis,
when applicable.


The Proposer agrees that all prices quoted in its Proposal Response are valid for one year from
the Contract execution date. Future price discounts are valid for the time periods indicated
in Section 16.
Comply

1.22 Right of Refusal

Floyd County reserves the right to reject any and all Proposals received. Acceptance of any
Proposer’s Response will not place Floyd County under any obligation to accept either the
lowest priced or most technologically advanced response.
Understood

1.23 Contractor's Insurance

The Contractor shall be responsible for any and all loss of material connected with the
construction due to unexplained disappearance, theft or misappropriation of any kind or
nature. The foregoing provisions shall not obligate to relieve the Contractor and any
Subcontractors of responsibility for loss or damage to their own or rented property or
property of their employees of whatever kind or nature, including but not limited to tools,
equipment, forms, scaffolding and temporary structures including their contents. Floyd
County shall in no event be liable for any loss or damage to any of the aforementioned items or
any other property of Contractor and any Subcontractors, which is not included in the
permanent construction. The Contractor and any Subcontractors hereby waive any right of
recovery they may have against Floyd County for damage or destruction of property of
whatever kind or nature whether it is their own property or property of their employees.
Comply
The first sentence and the last two sentences are deleted. The risk of loss will govern this matter.
The Contractor shall procure and maintain for the duration of the Contract the following
insurance policies as mandated by and with minimum limits set by the County of Floyd,
Georgia Procurement Policy with coverage for occurrences and claims that may arise from or in
connection with the performance of the obligations hereunder by the Contractor, its agents,
employees, representatives and subcontractors:
Comply
The words “agents, representatives and subcontractors” should be deleted because Motorola will
insure the entire project. Motorola will require that its subcontractors have insurance; however,
the insurance requirements will be limited to the work the subcontractors perform and not the
overall project.
1. A policy or policies to insure the Contractor for legal liability on account of

personal injury “bodily injury” (including death resulting wherefrom) or loss of or


damage to property however arising in the execution of this Contract and specifically
including explosion, collapse, and underground damage. The combined liability limits
shall not be less than $1,000,000. This insurance shall include coverage for (a) Premises -
Operations; (b) Broad Form Contractual Liability; (c) Products and Completed
Operations; (d) Use of Contractors and Subcontractors; (e) Personal Injury; (f) Broad
Form Property Damage. "Claims made" form shall not be acceptable. The
"occurrence form" shall not have a "sunset clause".
Comply
Motorola will comply with the clarification that “personal injury” is changed to “bodily injury”.
2. The policy or policies for this combined liability shall also include products/completed
operations liability for one year after completion of the work and “until” acceptance by
Floyd.
Comply
Motorola will comply with the clarification that the words “for one year after completion of the
work and” are deleted and replaced with “until”.
3. A policy to cover the full liability of the Contractor in accordance with the
provisions of the Worker's Compensation Law of the State of Georgia. The
Contractor shall also maintain employer's liability coverage with limits of not less than
$1,000,000 per year. The Contractor shall also obtain from its Workers'
Compensation Insurance carrier a waiver of subrogation in favor of Floyd “; provided that
there has been no judicial determination that the County was the party at fault.”.
Comply
Motorola will comply with the clarification that the following words are added to the last sentence
“; provided that there has been no judicial determination that the County was the party at fault.”
4. The Contractor will provide evidence of automobiles liability coverage for owned, non-
owned and/or hired vehicles in limits not less than $1,000,000 combined single limit per
occurrence for bodily injury and property damage.
Comply
The policies or certificates evidencing the coverage provided above shall be submitted at a Pre-
Construction Conference prior to commencing any work or Floyd County issuance of a formal
Notice to Proceed. Such policies or certificates shall provide that insurance will not be
materially altered or canceled without thirty (30) days prior written notice to Floyd.
Comply
Motorola will comply with the clarification that the words “policies or” are deleted. Motorola
cannot provide copies of its proprietary and confidential policies, just a Certificate of Insurance to
evidence coverage.


1.23.1 Other Provisions
The insurance policies required by the Contract shall contain, or be endorsed to contain, the
following provisions:
1. Floyd, its officers, agents, servants and employees, shall be added “included,” as
"additional insureds" under the Comprehensive “Commercial,” General Liability and
Automobile Liability “Business Automobile Liability” Coverages.
Comply
Motorola will comply with the clarification that the words “agents” and “servants” are deleted.
The word “added is replaced with the word “included,” the word “Comprehensive” is changed to
“Commercial,” and the “Automobile Liability” is changed to “Business Automobile Liability”.
2. The Workers' Compensation and Employer's Liability coverage shall c o n t a i n “a

Blanket” an express waiver of all rights of subrogation against Floyd, its officers, agents,
servants, and employees, for losses arising from work performed by the Contractor for
Floyd.
Comply
Motorola will comply with the clarification that the words, “an express” are replaced with the
words “a Blanket” and the words, “against Floyd, its officers, agents, servants, and employees for
losses arising from work performed by the Contractor for Floyd” are removed.
3. All insurance policies required by this Contract shall be endorsed to state that
coverage shall not be suspended, voided, canceled by either party, or reduced in
coverage or in limits except after thirty (30) days prior written notice by certified mail has
been “materially”. given to Floyd.
Comply
Motorola will comply with the clarification that the words, “be endorsed to” are deleted, and the
words “by certified mail” is removed, and the word “materially” is inserted between “been” and
“given”.
1.23.2 Acceptability of Insurers
All insurance required by this Section shall be placed with insurers that are authorized to do
business in the State of Georgia and have a rating of no less than A- in the most current
edition of the A.M. Best Insurance Report. Insurers shall have a minimum financial size
category of VIII according to A.M. Best.
Comply
1.23.3 Certificates of Insurance
The Contractor shall furnish to the Floyd County Certificates of Insurance affecting coverage
required by this Contract. The certificates are to be signed by a Georgia licensed agent
authorized by that insurer to bind coverage on its behalf and endorsements. The certificates and


endorsements must be received and approved by Floyd County prior to the Contract's effective
date.
Comply
1.24 Indemnity

Indemnity shall be negotiated with the apparent responsive and best Proposer as part of
Contract negotiations.
Comply

1.25 Performance and Payment Bonds
A Performance Bond in the amount of one hundred percent (100%) of the Contract Price shall
be provided by the Contractor in the event the Proposer is awarded a contract. The
Performance Bond shall be exercised by Floyd County for failure of the Contractor to
perform according to the terms of the Contract and this Specification.
Comply
Motorola complies with the clarification that it will provide a performance bond within 10
business days of contract execution and prior to commencing work, per the requirements of the
surety.
A Payment Bond in the amount of one hundred percent (100%) of the Contract price shall be
provided by the Contractor. The Payment Bond submitted must be from a surety company
authorized to do business in Georgia with a rating of A- or better in the most current edition of
the A.M. Best Insurance Report. The Payment Bond must be countersigned by a Georgia
licensed agent authorized to represent the surety company writing the Payment Bond. That
agent's power of attorney must be attached to the Payment Bond submitted.
Comply
Motorola complies with the clarification that it will provide a payment bond within 10 business
days of contract execution and prior to commencing work, per the requirements of the surety.
The cost of these Performance and Payment Bonds are the responsibility of the Contractor. Bonds
shall be executed on statutory forms acceptable to the Floyd County. They shall be maintained
in force through completion of the work and its acceptance by Floyd County and the Consultant.
They shall guarantee the Contractor's remedying any defects and damages due to faulty
workmanship and/ or material for one year after the date of Final System Acceptance. The
Surety Company issuing bonds in connection with this project must be approved by the client
and authorized to do business in the State of Georgia. All bonds must be presented prior to
Contract execution.
Comply
Motorola complies with the clarification that it will provide a performance and payment bond
within 10 business days of contract execution and prior to commencing work, per the requirements
of the surety.


1.26 Certificate of Ethics
Proposers are required to provide a Certificate of Ethics acceptable to the Floyd County
Procurement policy stating that no commission or any other compensation has been or will be
paid to Consultant or to Floyd County or its employees in regards to the selection and
purchase of this radio communications network.
Comply
1.27 Proposal Pricing Summary Sheets
Proposers shall provide detailed price breakdown submittals for infrastructure and subscriber
equipment items, system integration/project management and installation/engineering
services. Additionally, Proposers shall furnish a Proposal Summary Sheet for each of the two
required Price Proposals. The entries on the Proposal Summary Sheets must agree with the
same entries provided elsewhere in the Proposer's Response to these Specifications. In the
event of any discrepancies, and not as a result of simple arithmetic of submitted prices, the
lowest figure will prevail. Any errors or omissions in submitting pricing for the equipment or
services shall be the responsibility of the Proposer.
Comply
1.28 NonCollusion Affidavit
If the following affidavit on Page 21 is not properly executed and notarized, your Proposal
Response will not be considered:
Comply
NON-COLLUSION AFFIDAVIT STATE OF

COUNTY OF
, Being first duly sworn, deposes and says that:
(1)Executor is (Owner) (Partner) (Officer) (Representative) or (Agent), of , the Proposer that has
submitted the attached Proposal Response:
(2)Such Proposal Response is genuine and is not a collusive or sham Proposal:
(3)Neither the said Proposer nor any of its officers, partners, owners, agents, representatives,
employees or parties of interest, including this affiant, has in any way colluded, conspired,
connived or agreed, directly, or indirectly with any other Proposer, firm or person to submit a
collusive or sham Proposal in connection with the Contract for which the attached
Proposal Response has been submitted or to refrain from proposing in connection with such
Contract, or has in any manner, directly or indirectly sought by agreement or collusion or
communication or conference with any other Proposer, or to fix any overhead, profit or cost
element of the Proposer price or the Proposer price of any other proposer, or to secure
through any advantage against Floyd County, Georgia or any person interested in the
proposed Contract; and
(4)The price or prices quoted in the attached Proposal Response are fair and proper and are not
tainted by any collusion, conspiracy, connivance or unlawful agreement on the part of the
Proposer or any of its agents, representatives, owners, employees, or parties in interest,
including this affiant.
Subscribed and sworn to, this day of _, 201 .

Comply


1.29 Brokerage Fee

The Contractor warrants that he has not employed any person to solicit or secure this
Contract upon an agreement for a commission, percentage, brokerage or contingent fee.
Breach of this warranty shall give Floyd County the right to terminate the Contract, or, at the
discretion of Floyd, to deduct from the Contract price or consideration, the amount of such
commission, percentage, brokerage or contingent fee. This warranty shall not apply to
commissions payable by contractors upon contracts or established commercial or selling
agencies maintained by the Contractor for the purpose of securing business. No elected
official or employee of Floyd County, Georgia shall be permitted to share any part of this
Contract or any benefit that may arise there from, and any contract made by Floyd County in
which such individual(s) shall be personally interested shall be void, and no payments shall be
made thereon by Floyd County or any officers thereof.
Comply
1.30 Conflict of Interest

In the interest of ensuring that efforts of the Contractor do not conflict with the interests of
Floyd, and in recognition of the Contractor's professional responsibility to Floyd, the
Contractor agrees to decline any offer of employment if its independent professional work on
behalf of the County is likely to be adversely affected by the acceptance of such employment. The
initial determination of such a possibility rests with the Contractor. It is incumbent upon the
Contractor to notify Floyd County and provide full disclosure of the possible effects of such
employment on the Contractor's independent, professional work on behalf of Floyd. Final
decision on any disputed offers of other employment for the Contractor shall rest with Floyd.
Comply
1.31 Corporate Resolution

Proposal Response submittals must contain a Corporate Resolution or Power of Attorney
authorizing and identifying agents to sign their Proposal or other documents as required by this
Specification, the Floyd County Procurement Office or the State of Georgia. This Corporate
Resolution or Power of Attorney must be certified and notarized.
Comply
1.32 Bid Bond

Proposal Response submittals must contain a five percent (5%) bid guarantee to be submitted with
their Proposals. The bid guarantee shall consist of a firm commitment such as a Bid Bond,
certified check, or other negotiable instrument accompanying the proposal as assurance
that the Proposer will, upon acceptance of his proposal, execute such services as required. Such
bid security shall be held by Floyd County until the earlier of the end of the proposal validity
period, or award, or rejection of proposals, after which said securities will be returned to the
unsuccessful Proposals.
Comply




2.0 Existing Network Configuration
2.1 General

Floyd County operates an enhanced E911 system and a conventional radio system, which was
installed in the early 1960's. This system consists of a single tower and a shelter containing
the base stations and repeaters on top of Mount Alto. Floyd County and the City of Rome
agencies operate on VHF (Rome) and UHF (Floyd County) frequencies which cause difficulty
within these jurisdictions.
Understood
The call signs of the existing VHF and UHF systems are as follows:
KNCG426 Floyd County Police

KNCG425 Floyd County Sheriff
WPMT948 Floyd County Sheriff (Detention Center)
WPMT477 Floyd EMS
WPSJ241 Floyd County Animal Control
WPXD408 Cave Spring Police & Fire
WXP689 Cave Spring Public Works
WPTZ995 Redmond EMS
KRL288 Rome Fire
KIC242 Rome Police
Understood
All of these agencies utilize a local communications shop to provide support for public safety and
local government communications needs. Coosa Valley Communications (10 Bale
Street, Rome, Georgia), maintains all of Floyd County’s and most of Rome’s radio equipment.
Mr. Lamar Smith is the owner of Coosa Valley Communications and can be reached either by
electronic mail (lamarcvc@bellsouth.net) or telephone (706-291-0034) if necessary.
Understood
2.2 Emergency Medical Services

Redmond EMS and Floyd EMS provide emergency and non-emergency pre-hospital care and
transportation services for Floyd County. Redmond EMS and Floyd EMS also services parts of
Polk County.
Understood
The EMS departments operate on the VHF repeaters (Redmond) and UHF repeaters (Floyd)
located near the city at the summit of Mount Alto near Rome, Georgia. These EMS agencies
operate a fleet of approximately 77 subscriber radio units. Each of the EMS personnel is
assigned a portable radio and could potentially utilize the radio system at any given time. Each
EMS vehicles is assigned a mobile radio.
Understood


Currently the EMS agencies have eight base stations throughout the County. Both EMS
agencies use the radios nearly 95% of the time with cell phones and PDAs used the remaining 5%
for non-emergency communications.
Understood
Radio dispatch services are countywide and both EMS services are dispatched from the
County E911 Center. Since the radio traffic is principally on a small number of UHF band
channels there is channel congestion. Occasionally some users do inadvertently interfere with
on-going operations.
Understood
Functionally, EMS desires the following features: Unit ID display; Emergency call notification;
automatic vehicular location, status/test messaging; and the radio disable feature. Additionally,
the departments would prefer to retain on-scene communications ability via vehicular
repeaters as this provide for both wide area (via main system linkage) and highest-reliability
local area conventional coverage.
Comply
These features are available with specific subscriber options
In terms of radio interoperability, EMS must maintain efficient, reliable communications with
the Fire services. The EMS personnel currently interoperate with all emergency agencies in Floyd
County. Outside Floyd County the EMS agencies need to interoperate with all surrounding
counties. A separate air medical channel is desired, however, this operation can result in
wide-spread communications interference.
Understood
2.3 Rome Floyd County Fire Department
The Rome - Floyd County Fire Department provides fire protection to all of the City of
Rome and all of Floyd County, except in the unincorporated area in the southwest part of the
County around Cave Spring. The Department has 149 employees with ten stations. The dispatch
function of the Rome - Floyd County Fire Department is provided by the Floyd County E911
Center.
Question:
8. Which Fire Stations have existing IP/Ethernet LAN connectivity? Please provide information
on the network topology with respect to which sites are connected and where each site can be
accessed from.
Response: The County will not provide any network/IP/Ethernet LAN connections to any of the
Fire Stations.
Understood
The Rome - Floyd County Fire Department operates on the VHF repeaters located near the
summit of Mount Alto near Rome, Georgia. The Department also operates a fleet of
approximately 78 subscriber radio units. Each of the FD personnel has access to a portable
radio and could potentially utilize the radio system at any given time. Portable radios are not
assigned to individuals except in a few cases.


Understood
The Fire Department has a requirement for analog communications, particularly at fireground
locations. To accomplish this, the Rome – Floyd County Fire Department has determined that
they want to use an analog mode of communications as their proposed mode for fireground
communications. This mode would be a simplex mode rather than using the infrastructure
equipment at the tower sites.
Comply
An additional requirement is the ability to perform the Fire Station alerting to specific fire
stations. This should be accomplished through a separate 800MHz analog system or through a
separate IP network.
Comply
Fire Station alerting will be accomplished using a VHF analog repeater, while EMS Station
alerting will be accomplished using an 800MHz analog repeater.
Functionally, the various fire departments desire those same features as identified by EMS: Unit
ID display; Emergency call notification; automatic vehicular location, status/test messaging; and
the radio disable feature. Additionally, the departments would prefer to retain on-scene
communications ability via vehicular repeaters as this provide for both wide area (via main
system linkage) and highest-reliability local area conventional coverage.
Comply
These features are available with specific subscriber options
The Department regularly has the need for interoperable radio communications with all
emergency agencies in the County, neighboring counties (Walker, Gordon, Bartow, Polk and
Chattooga), Cherokee County in Alabama and the Georgia Forestry Commission. In addition,
the Rome-Floyd Fire has a mutual aid agreement with Cave Spring Fire.
Understood

2.4 Floyd County Police Department

The Floyd County Police Department is responsible for responding to all calls outside of the City
of Rome and the City of Cave Spring. In addition, Floyd County Police are charged with the
responsibility of patrolling parks within the City of Rome.
Understood
The Floyd County Police Department operates on UHF repeaters located near the summit of
Mount Alto near Rome, Georgia. They also operate a fleet of approximately 208 subscriber
radio units. All PD personnel are assigned a portable radio and could potentially utilize the
radio system at any given time. Each vehicle is assigned a mobile radio. The Floyd County
Police Department does not currently employ base stations.
Understood


The dispatch function of the Floyd County Police Departments is provided by the Floyd
County E911 Center.
Understood

2.5 Floyd County Sheriff’s Office

The Floyd County Sheriff’s Office serves warrants, houses inmates in the detention center (820
inmates) and provides security for the courts. The Floyd County Sheriff’s Office has a staff of
153 full time personnel.
Understood
The Floyd County Sheriff’s Office operates on UHF repeaters located near the summit of
Mount Alto near Rome, Georgia. In addition, the Sheriff’s Office operates a UHF repeater at
the Jail. The Floyd County Sheriff’s Office operates a fleet of approximately 237 subscriber radio
units. Each of the Sheriff’s Office personnel is assigned a portable radio and could potentially
utilize the radio system at any given time. Each Sheriff’s Office vehicle is assigned a mobile
radio.
Understood
The Sheriff’s Office has a dedicated repeater at the jail that is used for all communications of
prisoner movements. This radio is hard wired to a number of base stations throughout the jail.
This system will need to be replaced with an 800MHz analog repeater.
Question:
9. Would a desktop remote controller meet the requirements of the hard wired base station?
Response: No. A control station is required.
Question:
How many base stations/desktop remote controllers are required at the FC SO Jail?
Response: 14
A desktop remote controller can control (via hard wire) up to 4 radios providing a selection of up
to 16 frequencies with Tone Remote Control. Up to 10 desktop remote controllers can be connected
in parallel, allowing multiple controllers to be connected to the same radio. Parallel units will see
a busy indication when other controllers are active and an intercom facility between the units is
provided.
Comply
A P25 800MHz digital repeater is provided to meet the Sheriff’s Office requirements.
The Sheriff’s Office personnel currently interoperate with all emergency agencies in Floyd
County to include the Rome PD, Floyd County PD, Cave Spring PD, Rome FD, both EMS
departments, County Public Works, Rome Public Works, the Magistrate Court, the Metro Task
Force, EMA and Animal Control.
Understood
Outside the county the Sheriff’s Office interoperates with other Sheriff agencies in the state. This


is currently accomplished by using VHF radios that have access to the state band.
Understood
2.6 Rome Floyd Metro Task Force

The Rome Floyd Metro Task Force is a multiagency drug task force consisting of seven full time
investigators and is tasked with enforcing the drug and vice laws in the City of Rome and Floyd
County.
Understood
The Rome Floyd Metro Task Force operates on UHF repeaters located near the summit of
Mount Alto near Rome, Georgia. Each of the Task Force personnel is assigned two portable
radios, one on the City’s VHF system and the other on the County’s UHF system. Each Task
Force vehicle is assigned a mobile radio for each band. The Task Force does not currently
utilize base stations.
Understood
The Metro Task Force personnel currently interoperate with all emergency agencies in Floyd
County. This includes the Floyd County PD, Rome PD and the Sheriff’s Office.
Understood
Outside the county, the Metro Task Force would need to interoperate with The Georgia
Bureau of Investigation, the DEA, FBI and ATF.
Understood
2.7 Floyd County E911 Center

The Floyd County E911 Center receives and dispatches all calls for service for most of the
agencies in Floyd County.
Understood
The Floyd County E911 Center uses a RF link to the radio repeaters on Mount Alto. The
Floyd County E911 Center personnel currently interoperate with all agencies in Floyd County,
and with all agencies that communicate regularly with police, sheriff, EMA, EMS and fire
services.
Understood
2.8 Floyd County Magistrate Court

The Floyd County Magistrate Court is tasked with serving papers for the jurisdiction of
Floyd County and executing court orders.
Understood
The Court, like most agencies, operates on UHF repeaters located near the summit of Mount Alto
near Rome, Georgia. They have been assigned a portable radio and could potentially utilize the
radio system at any given time. Vehicles may already contain mobile radios from other agencies.
Understood


The Magistrate Court personnel currently interoperate primarily with the Rome PD, Floyd
County PD, the Sheriff’s Office and Animal Control.
Understood
Outside the county the Magistrate Court does not need to interoperate with any agency.
Understood
2.9 Floyd County Prison

The Floyd County Prison Department is responsible for housing and supervising 448 inmates that
perform work in Floyd County. The department also operates a work release center which is
capable of housing 100 residents. Currently the Floyd County Prison Department has 70
employees.
Understood
The Floyd County Prison Department operates on UHF repeaters located near the summit of
Mount Alto near Rome, Georgia. The Floyd County Prison Department operates a fleet of
approximately 53 subscriber radio units. Each of the Prison personnel is assigned a portable
radio and could potentially utilize the radio system at any given time. The Floyd
County Prison Department does not utilize base stations.
Understood
The Prison Department does have inmates on work details around the county and utilizes a
prisoner count when prisoners are on the work detail. These prisoner counts take place over the
air and are conducted at 10AM, Noon and 2PM. Prison personnel are therefore required to carry
a radio.
Understood
The Floyd County Prison has a need for an 800MHz analog repeater that can be used for all
communications of prisoner movements, similar to the Floyd County Jail. Currently the Floyd
County Prison does not have a radio repeater. This new radio system should be hard wired to a
number of base stations throughout the prison. This system should also be an
800MHz analog repeater.
Question:
10. Would a desktop remote controller meet the requirements of the hard wired base station? How
many base stations/desktop remote controllers are required at the Prison?
Response: 3
provided.
Comply
A P25 800MHz digital repeater is provided to meet the Floyd County Prison requirements


The Prison Department personnel currently interoperate with all emergency agencies in
Floyd County including the Floyd county PD, Rome PD, the Sheriff’s Office as well as
County and City Public Works.
Understood
There are no agencies outside the county that the Prison would need to interoperate with.
Understood
2.10 Rome Police Department

The Rome Police Department provides police services for a population of approximately
35,000 with a daytime population of 50,000 plus. The department performs patrol, traffic stops
and investigations of crimes of persons and property inside the City of Rome.
Understood
The Rome Police Department operates on VHF repeaters located near the summit of Mount
Alto near Rome, Georgia. The Rome Police Department operates a fleet of approximately
210 subscriber radio units. Each of the PD personnel is assigned a portable radio and could
potentially utilize the radio system at any given time. Each Floyd County Police Department
vehicle is assigned a mobile radio. The Rome Police Department does not utilize base
stations.
Understood
The Rome Police Department is currently using mobile data and will need additional bandwidth
in the future for streaming video.
Understood
The Rome Police Department personnel currently interoperate with emergency the Floyd
County PD and Rome FD. There are no agencies outside Floyd County, at this time that the
Rome PD needs to communicate with.
Understood
2.11 City of Cave Spring

The City of Cave Spring provides its own Fire, Police, and Emergency Services in addition to
having its own Water department and Maintenance Department. The City of Cave Spring does
provide extraterritorial Fire and Water services.
Understood
The City of Cave Spring operates on VHF repeaters located near the City of Cave Spring,
Georgia. The City of Cave Spring operates a fleet of approximately 77 subscriber radio units. Each
of the City of Cave Spring personnel is assigned a portable radio and could potentially utilize
the radio system at any given time. Each of the City of Cave Spring vehicles is assigned a
mobile radio.
Understood


Currently the City of Cave Spring has a base station at the Fire Department and one at the
Police Department. A new one is needed at City Hall.
Comply
The City of Cave Spring personnel currently interoperate with emergency agencies in Floyd
County including the Floyd County PD, Rome - Floyd FD and the Floyd County Sheriff’s
Office. In addition, Cave Spring Fire has a mutual aid agreement with the Rome-Floyd Fire.
Understood
Outside Floyd County the City of Cave Spring needs to interoperate with Polk County, GA
and Cherokee County, AL.
Understood
The City of Cave Spring has a separate VHF repeater in Cave Spring that is primarily used by
the Fire Department.
Understood
2.12 Floyd County EMA

The Floyd County EMA is the coordinating agency for emergency response in the City of
Rome and Floyd County. The department has two full time employees and 50 volunteers. The
Floyd County EMA has the capacity to operate on all of the repeaters located near the summit
of Mount Alto near Rome, Georgia. The Floyd County EMA operates a fleet of approximately
35 subscriber radio units. Each of the Floyd County EMA vehicles is assigned a mobile radio.
Understood
Currently the Floyd County EMA does utilize one base station.
Understood
EMA needs to interoperate will all agencies on the radio system, both inside the county and
outside the county. The County EMA agency will most likely be the department to maintain the
radio system.
Understood
2.13 The nonpublic safety agencies

The non-public safety agencies for Rome and Floyd County are Animal Control, the Floyd
County Board of Education, Floyd County Public Works, the Floyd County Water Department,
Rome Public Works, the Rome-Floyd Parks and Recreation Authority, Rome Water and Sewer,
Rome Transit and Rome Board of Education.
Understood
The majority of these agencies operate on the UHF and VHF repeaters located near the
summit of Mount Alto near Rome, Georgia. These agencies also operate a fleet of approximately
444 subscriber radio units. Rome-Floyd Parks and Recreation Authority, Rome Public Works,
Floyd County Public Works, and Animal Control will have to have contact with the prison
dispatchers and E911. There are no agencies that needed to communicate with agencies outside of
Floyd County.
Understood
Attachment A contains an Interoperability Matrix covering all the agencies inside of Floyd


County and how they should interoperate with each other. Attachment D contains subscriber
radio quantities that are needed per agency.
Understood
3.0 Identified User Needs

3.1 General

The Floyd County, Georgia has operated a legacy VHF/UHF analog conventional networks
supporting public safety users for over 20 years. The issues with this system are interoperability,
call waiting and radio propagation coverage. As a result of the lack of interoperability and
coverage County firefighters, sheriff’s deputies, medical responders, police and the E911
dispatchers had to resort to relaying messages through whoever could hear the call in other
agencies or by depending on cell phones instead of their radios. This event underscored the
difficulties in coordinating efforts between agencies in areas of the county where there is little to
no radio communications coverage. These capacity and coverage deficiencies must be resolved
by the newly proposed 800 MHz P-25 compliant radio network.
Understood
A full description of the network’s current configuration is described by the Specification
Document in Section 2. Proposers are strongly encouraged to thoroughly review that information
and to conduct as many on-site inspections as necessary to gain a comprehensive understanding
of existing-network performance. It is critically important to the success of this digital P-25
project that Proposers have a clear understanding of expectations and to propose a comprehensive
set of equipment and services that fully satisfy and expand upon this network’s baseline level of
performance.
Comply
3.2 Public Safety Needs

3.2.1 Talk Paths
Each of the Public Safety agencies utilizes individual analog conventional channels that are
optimized for existing operations. Additionally these agencies share several channels that allow
for some interoperability between agencies during special events and local-area emergencies. For
the purpose of this RFP, Proposers shall develop new profiles, plus a nearly 100% future
growth factor, in the development of their proposed solution.
Comply
3.2.2 Automatic Telephone Interconnect
The new system shall incorporate a limited number of telephone gateways and telephone-
interconnect features for emergency operations use. Limitations must include the ability to
dynamically control the total number of lines available, priority allocation by user, and call
duration restrictions according to user priority. In addition, the availability of telephone
interconnect features shall be continuously monitored and controlled by the County radio
network manager. That is, as dispatch-traffic activity increases on the system, the availability of


telephone interconnect features must correspondingly be restricted. This shall be accomplished in
such a manner that degradation in system access time is solely a function of the total number of
users attempting to pass voice traffic at a given period in time and not a result of channels
dedicated to telephone transactions. The telephone interconnect feature is considered of
significantly lesser importance to clear or encrypted voice communications.
Question:
2. What type of phone lines are going to be interfaced to the Radio Network? Analog (POTS)
Digital (PBX) or VoIP?
Response: The types of phone lines that will be interfaced into the radio network are analog.
Comply
Motorola’s Dynamic Resource Manager has been included.
For the purpose of sizing the telephone interconnect subsystem’s hardware components, a
maximum of four simultaneous telephone interconnect calls shall be supported.
Comply
The proposed system includes four analog (POTS) line interfaces.
3.2.3 Call Privacy
Floyd's existing VHF/UHF analog conventional radio network is intrinsically open to

transmission monitoring with any radio equipment operable on those VHF/UHF frequencies (i.e.,
scanning receivers, etc.).
Understood
The ability to monitor in certain instances is desirable and encouraged. Dispatchers, in

addition to their normal dispatch function can also monitor unit-to-unit traffic. This ability to
monitor allows the dispatcher to develop a mental picture of ongoing operations. In times of
emergency, where public safety personnel may need outside assistance, the dispatcher often has
heard and remembered information critical to personnel safety that would otherwise have been
unavailable.
Understood
Likewise, field users can hear on-frequency traffic and modify their use of the radio as
conditions dictate. As an example, when emergency calls are in progress, channel protocol
would require users to refrain from lower-priority transmissions. Competition for air-time may
increase, but users moderate calls, both in frequency and duration, in response to simply
hearing more channel activity. In such a situation, the ability to monitor is desirable.
Comply
In the present analog conventional VHF/UHF radio system, it is impossible to control who
monitors calls outside of the network. Command and investigative conversations may involve
topics of a legally restricted or sensitive nature where eavesdropping by outside, unidentified
persons is undesirable or unacceptable.
Understood
Accordingly, the new digital voice radio network shall include provisions for call privacy
whereby identified users within the network can be excluded from certain talk groups or
individual conversations. This provision must offer sufficient flexibility such that the desirable


features of monitoring can be retained while permitting privacy to conversations that are
potentially confidential. Finally, the new network shall incorporate technical features that prevent
unauthorized listeners from monitoring any network calls. Ideally, the new network should
inhibit the ability of non-network users from monitoring actual voice transmissions of any type
(inclusive of telephone interconnect calls) as well as preventing such persons from monitoring
those call assignments transacted via the network’s digital control channel.
Comply
Proposers shall describe the scope and operation of such provisions inherent within their
proposed solution that prevent the types of undesired radio monitoring discussed above.
Comply
Radio subscribers, console dispatch positions, and telephone interconnect equipment has been
priced to include AES encryption, which can be utilized to provide end-to-end call privacy.
Conversations with essential personnel can be restricted using ASTRO 25 features, private call,
and dynamic regrouping.
3.2.4 Encryption
Digital voice encryption, using Improved Multi-band Excited (IMBE) vocoder technology
coupled with federally approved digital encryption schemes, is a required feature of the new
network.
Comply
Motorola’s APX radios and MCC 7500 dispatch consoles are equipped with the P25 Enhanced
dual-rate vocoder, which is backwards compatible with the P25 IMBE vocoder.
Three modes of encrypted digital voice operation are desired:
1. Unit-to-unit, where conversations in an encrypted talk group are secure. These cannot
be monitored at a dispatch or control point.
Comply
2. Dispatcher-to-unit, where conversations between the County’s E911 Center, future
Backup 911 Center and field units are secure.
Comply
3. Unit-to-telephone network, where conversations between encrypted units and the
switched telephone network are secure.
Comply
The new network shall provide encrypted transmission so that system access delays are equal to
those in the clear mode. Encrypted transmissions shall not degrade the operation of clear- voice
features nor lengthen system access or audio transport delays to other users. Encryption shall not
degrade the range or coverage less than normal digital performance.
Comply
3.2.5 End User Equipment
It is the County's intention to purchase a fully P-25 800MHz network. Proposers shall
demonstrate such P-25 compliancy by demonstrating at a minimum, three different manufacture’s


radios work on the P-25 system. These approved radios will then be made available to the
different services.
Question:
3. Is the P25 Compliance Assessment Program (CAP) test program acceptable for demonstration
that at least three different vendors’ radios work on our P25 Network?
Response: Yes, P25 Compliance Assessment Program (CAP) testing results will be acceptable.
Comply
Motorola fully supports and participates in the P25 Compliance Assessment Program (CAP) that
is being facilitated by the Department of Homeland Security DHS). This testing program requires
the testing of equipment in NIST assessed, DHS approved P25 Test Laboratories. Motorola had
one of the first DHS approved CAP laboratory test facilities. Verification of Motorola’s
compliance to the P25 CAP testing program is documented in the SDOCs and STR documents.
Official SDoCs and STRs for all of the documentation relating to Motorola’s P25 CAP tested
equipment is provided in Appendix A. This information is also available for download on the
Responder’s Knowledge Base (RKB) website www.rkb.us.
Police communications needs have generally shifted from patrol car based, with equipment fixed
within vehicles to patrolman based where portable equipment is assigned to individual officers.
These same user trends exist within the Fire Service and related public safety agencies.
Understood
This migration to portable units, with their reduced output power and often-degraded antenna
performance, has placed greater technical demands on radio communications network
infrastructures. The coverage needs for mobile-based systems are relatively straightforward as the
available effective radiated power from a mobile unit can closely approach that of a base
station. Talk-in/talk-out balance can thus be easily achieved with simple backbone system
configuration.
Understood
Portable radio coverage problems are further compounded by the fact that users often operate
within radio-resistant areas such as warehouses, office buildings, apartment structures and single-
family dwellings. The need for reliable communications within building structures requires
increased talk-in/talk-out system gain.
Understood
Further complicating the design of portable-based systems are desired mechanical and ergonomic
features, as summarized below:
Understood
1. The radio package, itself, must be simple to operate and have a minimum of
operator controls or feature selections.
Comply
2. Radios contain a microphone, speaker, talk group selector, volume control, power
switch, emergency button, and normal transmit push-to-talk button. All of these
input/output devices are subject to near-constant physical abuse within a public safety
environment.


Comply
3. User must be able to disable message authorization tones.
Comply
4. The volume control must be fully adjustable from zero to maximum audio output
level.
Comply
5. Unit must be extremely rugged to withstand shock and vibration typical of public
safety operations. For the Fire Service, other features such as Intrinsically-Safe
operation and the ability for the equipment to survive short-term water submersion are
required.
Comply
6. Units must be operable, within the coverage requirements of Section 7.0, using the
smallest flexible antenna available.
Comply
7. Radio unit battery packs must operate to provide sufficient power for a full twelve- hour
work period. A range of accessories must be available for support in-field battery
charging.
Comply
8. Radio units must be equipped with alphanumeric displays to more readily identify
selected talk groups and operating modes, i.e. clear voice, encrypted voice, etc.
Comply
9. Radios must be capable of operation with traditional speaker/microphones as well as

sub-miniature radio surveillance accessories.
Comply
10. In addition to the specific desired features indicated above, all furnished equipment
must meet minimum equipment requirements identified in Section 5.0.
Comply
11. Floyd County desires programmable front buttons and some sort of status message.
Comply
12. Floyd County requires a backlit display as a standard feature on all portable and
mobile subscriber equipment.
Comply
3.2.6 Interoperability
As this new network’s coverage footprint will duplicate or partially overlap outside-of- network
agency radio communication systems, direct unit-to-unit interoperability is a desired feature.
Special talk groups must be provided so that certain public safety users can have access to
outside-agency radio networks, regardless of frequency band or communications technology in
place.
Comply
The methodology of network access is to be accomplished by transparent radio and/or audio links


(computer controlled) where the need for linkage is frequent. In those cases where the need for
interoperability is relatively infrequent, links can be established manually by the E911 Center
or the backup 911 Center. In any case, proposed interoperability linkage systems shall be
configured such that multiple and successive, narrow bandwidth vocoder schemes are avoided.
This is necessary to prevent excessive audio quality degradation as is the cumulative effect of
multiple and successive IMBE/AMBE vocoding.
Comply
Surrounding Networks:
Walker County, Georgia Gordon

County, Georgia Bartow County,
Georgia Polk County, Georgia
Chattooga County, Georgia
Cherokee County, Alabama
Georgia Forestry Commission
Georgia State Patrol
Georgia Bureau of Investigation
Georgia Department of Natural Resources
Berry College
Drug Enforcement Administration
Federal Bureau of Investigation
Bureau of Alcohol, Tobacco, Firearms and Explosives

Question:
11. Are dedicated resources required to access each of these agencies? Can multiple systems be
consolidated into several access resources? For example, can 2 VHF resources be used to access
Polk, Chatooga, Cherokee, GSP, and GBI interoperability systems?
Response: No. Individual control stations linked to the Floyd radio system would be required.
Understood

4.0 Minimum Operative Characteristics

4.1 General

Section 3.0, Identified User Needs, described the minimum functionality required by the
County's various user agencies. In this Section, channel usage characteristics for departments now
operable on Floyd’s analog conventional VHF/UHF radio networks, will be presented. From
this information Proposers can better determine the scope of services needed to satisfy talk
group structure requirements for this project.
Understood


4.2 Public Safety Departments

The Floyd County Police, Fire, and EMS have utilized the existing analog radio system for
many years. During that time, the various channel structures for each have been modified to better
suit individual department needs.
Understood
Proposers should assume that the current channel assignment/usage will be replaced with the
new digital radio network with an entirely different trunked radio talkgroup structure.
Attachment A contains an Interoperability Matrix covering all the agencies inside of Floyd
County and how they should interoperate with each other.
Understood
5.0 Minimum Equipment Requirements

This Section describes the minimum-acceptable requirements for mobile, portable, control
station, and fixed-site radio. All radio equipment installed by Contractor shall be FCC type
accepted under Part 90 of the FCC Rules and Regulations. Additionally, all supplied equipment
shall be in current production and shall meet or exceed the requirements of this Section.
Comply
Base station/repeaters shall support APCO Project-25 Phase I and Phase II modulation
formats and shall support trunked mobile data technology. If substantial upgrading is involved to
support trunked mobile data operations, Proposers shall clearly identify what will be required
to "upgrade" a repeater to support mobile data computing and supportive application software.
Proposers shall be specific in their responses and shall avoid ambiguous statements such as "digital
capable, digital ready", P-25 capable”, etc.
Comply
Motorola’s offering includes the required infrastructure hardware and software licensing
to provide mobile data via IV&D. All GTR8000 radios include the IV&D option and all
IP networking equipment for interfacing to the radio network is provided.
The stated minimum requirements, below, for end-user equipment will not necessarily be
required on all individual units assigned to differing user agencies. Section 16.0, Pricing
Considerations contains those user radio configurations required for each agency/department.
Understood
5.1 Mobile Radio Equipment

A. Meet APCO minimum recommendations and EIA/TIA standards for Project-25
Public Safety 700/800MHz trunked radio systems. Furnished equipment must be
operable on both Phase I and Phase II infrastructures.
Question:
12. Are all tiers of subscriber products required to have the TDMA AMBE vocoder?
Response: All radios used by public safety agencies must have this Phase I/II capability.


Comply
B. Incorporate heavy-duty construction, weather-sealed enclosures and weather- sealed
controls to meet Military Standard 810 C, D, E and F for water, shock, vibration,
dust, humidity and high/low temperature performance.
Comply
C. Allow operations on P-25 trunked and conventional (analog/P-25) systems with

priority scan of talk groups or channels.
Comply
D. Front mount and rear mount, dual control-head with single rear mount radio and dual
radios with single control-head configurations must be available to meet the needs of
the different public safety departments. Rear mount radios may require weatherproof
control heads, speakers, microphones and other accessories (specific for fire operations).
Dual-band mobile radio configurations (using one control head/speaker/microphone to
simultaneously control two mobile radio transceivers) must be available to allow
800MHz trunked/800MHz conventional; VHF/800MHz; UHF/800MHz or VHF/UHF
operations, depending upon the types of radio transceivers employed.
Comply
Motorola is currently the only public safety manufacturer/vendor shipping
mobiles in a dual-band trunked configuration.
E. Incorporate electronic, backlit alphanumeric displays (minimum of eight characters) to

provide visual indication of system availability, channel/talk group selection, incoming
user ID, call alerts and operational status such as scan and channel busy.
Comply
F. Emergency priority button on mobile radio control panels to initiate an emergency
priority call.
Comply
G. External alarm dry-contact closure to provide activation of a horn, light, etc.
whenever the radio unit is individually called.
Comply
H. Data transmission capability.

Comply
I. Digital voice encryption, using P-25 Phase I and Phase II vocoder technology and
federally approved AES/DES coding, to provide security during transmission and
reception of sensitive communications.
Comply
APX mobiles are capable of supporting AES or DES encryption algorithms with a
Phase I and II compliant vocoder.


J. Radio operating information shall be contained in an electrically erasable memory
device. Unit will be fully programmable from an IBM-compatible computer. Sufficient
quantities of programming cables shall be part of the delivered equipment.
Comply
K. Transmit Time-Out Timer to warn the user of excessive transmission length. Time
out timer should automatically disable the radio’s transmitter after a predetermined
period; thereby eliminating talk group/channel interference caused by either a defective
speaker/microphone or PTT button.
Comply
L. Minimum Electrical Specifications as follows:
• Channel Capacity: 24 channels/system (8-systems/tiers, min.)
• Talk Group Capacity: 16, minimum, per system
• Primary Input Voltage: 11 to 16VDC, negative ground
• Battery Drain: Standby: 1.5 amperes, max.
• Receive: 4.0 amperes, max.
• Transmit: 15.0 amperes, max.
• Environmental: MIL-STD 810 C, D, E and F for shock, vibration,
humidity and high/low temperature.
• Transmitter
• Frequency Range: 764 to 870MHz (standard post rebanding public safety
frequencies)
• Channel Capacity: 24 channels per system (8 systems, min)
• Talk group Selection: 16 talk groups per system
• RF Output Impedance: 50 ohms
• Output Power: Sufficient power to achieve required coverage, not less than
10 watts.
• Channel Spacing: 25/12.5/6.25 KHz/NPSPAC
• Spurious/Harmonic: At least 64db below carrier
• Frequency Stability: 1.5 PPM from -30°C to 60°C
• Modulation: 11K0F3E;8K10F1E;16K0F3E; 8K10F1D
• Modulation Deviation:
o +/- 5KHz for 25KHz Channel
o +/- 2.5KHz for 12.5KHz Channel
o +/- 3KHz for NPSPAC
• Audio Distortion: Less than 5% @ 1 KHz
• Audio Response: +1, -3db of a 6dB/octave pre-emphasis characteristic from
300 Hz to 3 KHz.
• Duty Cycle (EIA):
o Transmitter 20%
o FM Hum and Noise: -40db


• Receiver
• Channel Capacity: 24 channels per system (8 systems, min)
• Channel Spacing: 25/12.5 KHz/6.25KHz; NPSPAC
• Sensitivity:
o 20db Sinad 0.50 microvolts
o 5% BER 0.50 microvolts
o Selectivity: -70db
• Frequency Stability: 1.5-PPM from -30° to 60°C
• Modulation Acceptance: +/-7KHz
• Intermodulation: -70db
• Spurious/Image: -70db
• Audio Output: 10 watts, no more than 3% distortion at 1KHz
o Duty Cycle (EIA): Receiver 100%
Comply
5.2 Portable Radio Equipment

A. Meet APCO minimum recommendations and EIA/TIA standards for P-25 Public Safety
700/800MHz trunked radio systems. Furnished equipment must be operable on both Phase
I and Phase II infrastructures.
Question:
13. Are all tiers of subscriber products required to have the TDMA AMBE vocoder?
Comply
B. Heavy duty construction and weather-sealed cases to meet Military Standards 810 D, E
and F for shock, vibration, dust, humidity, high/low temperature and blowing rain.
Comply
C. Allow operations on P-25 trunked and/or conventional (analog/P-25) systems with priority
scan of talk groups or channels.
Comply
D. Top-mounted rotary controls with positive stops for volume and channel selection. Control
placement must be sufficient to allow gloved-hand operation, as is typically needed by the fire
service.
Comply
E. Incorporate electronic, alphanumeric (minimum eight-character) backlit display to provide
visual indication of system availability, channel/talk group selected, incoming user ID, call alerts
and operational status such as scan, transmit or low battery.
Comply


F. Transmit Time-Out Timer to warn the user that the radio may be transmitting longer than a
predetermined time limit and then disable the transmitter.
Comply
G. No protruding push-to-talk switch, thereby preventing accidental transmitter operation or
damage to the switch as caused by impact.
Comply
H. Protected emergency button to allow easy access when needed but incorporating an
ergonomic design whereby the emergency function could not be accidentally activated.
Comply
I. An accessory receptacle shall be provided for the connection of external devices such as
remote microphones or combination remote speaker/microphone units (with or without
antenna), vehicular adapters and mobile data computer equipment.
Comply
J. Radio operating information shall be contained in an electrically erasable memory device. Unit
will be fully programmable from an IBM PC compatible computer, via the accessory
receptacle. Sufficient quantities of programming cables shall be part of the delivered equipment.
Comply
K. Portable radios, batteries and accessories (used by the fire service) proposed must be
approved by Factory Mutual as intrinsically safe for the following hazardous environments:
Class I and II Division I, groups C, D, E, F and G and non-incentive for Class I, Division 2,
Groups A, B, C and D.
Comply
L. Carrying case options should include leather-carrying case with swivel mounts, as well as
chemical-resistant cases (nylon or similar plastic material) for use by hazardous material
groups. Additionally, a quantity of battery belt clips should be included to match the
number of non-public safety portable radios supplied for all agencies.
Comply
M. Optional surveillance accessories such as miniature microphones, earpieces and remote
microphones and headset speaker microphones must be available.
Comply
N. Digital voice encryption, using Improved Multi-Band Excited (IMBE) vocoder and federally
approved AES/DES coding, to provide enhanced security during transmission and reception of
sensitive communications.
Comply
O. Provide single-unit 120VAC rapid charger capable of fully charging a discharged high
capacity battery pack within a one-hour period. Provide optional single-unit 12VDC rapid
charger for vehicular operation
Comply
P. Battery shall operate the proposed radio equipment a minimum of twelve-hours using a duty
cycle of 5% transmit, 5% receive and 90% standby.
Comply


Q. Radios must be operable on new rebanded 800MHz NPSPAC frequencies as well as
700/800 MHz conventional and trunked frequencies.
Comply
R. User programmable audio alert in the event of loss of control channel. Must be a
standard feature in present and all future-proposed public safety models.
Comply
S. Minimum electrical specifications as follows:
Understood
• Channel Capacity: 24 channels/system (8-systems/tiers, min.)
• Talk Group Capacity: 16 talk group/system
• Duty Cycle: Intermittent
• Temperature Range: -30°C to +60°C
• Humidity: 95% relative humidity @ 50°C
• Shock, Vibration, Humidity: Shall meet or exceed MIL STD 810 C, D, E and F
for
• High/low temperature and blowing rain.
o Frequency Range: 764 to 870MHz (standard post rebanding public safety
frequencies)
• Talk group Selection: Rotary-knob style
• Transmitter
frequencies)
• RF Output Impedance: Sufficient power to achieve required coverage, but not
less than 2.5 watts.
• Frequency Stability: 1.5-PPM from -30°C to +60°C
o +/-5KHz for 25KHz Channel
o +/-3KHz for NPSPAC
• Emissions: 11K0F3E;8K10F1E;16K0F3E; 8K10F1D
• Audio Response: Within +1, -3db of a 6db/octave
• Audio Distortion: Less than 5% @ 1 KHz, rated system deviation
• Spurious/Harmonic: -50db
• FM Noise: -40db
• Receiver
frequencies)
• Channel Spacing: 25/12.5/6.25 KHz/NPSPAC Mod. Acceptance: +/-7KHz
• Selectivity: -70db (25KHz channel)


o Sensitivity: 20 db Quieting 0.5 microvolts
o Intermodulation: -70db Spurious/Image: -70db
• Frequency Stability: 1.5-PPM from -30° to +60°C
• Audio Output: 500 milliwatts @ no more than 3% distortion
Comply
5.3 Control Station Equipment

A. Available either as integrated 120VAC-powered desktop radio cabinet or a remotely
located, AC-powered radio package with separate remote control unit.
Comply
B. Control station and control unit shall have optional provision to operate from standby
12VDC source upon failure of AC power.
Comply
C. Provision shall be provided for local and remote control operation of the control station.
Comply
D. Meet APCO minimum recommendations and EIA/TIA standards for P-25 Public Safety
700/800MHz trunked radio systems. Furnished equipment must be operable on both Phase
I and Phase II infrastructures.
Comply
E. Allow operations on P-25 trunked and conventional (analog/P-25) systems with priority scan
of talk groups or channels.
Comply
F. Digital voice encryption, using Improved Multi-Band Excited (IMBE) vocoder and federally
approved AES/DES coding, to provide enhanced security during transmission and reception of
sensitive communications.
Comply
G. Incorporate electronic, alphanumeric displays (minimum of eight characters) to provide
visual indication of system availability, channel/talk group selection, incoming user ID, call
alerts and operational status such as scan and channel busy.
Comply


H. Transmit Time-Out Timer to warn the user that the radio may be transmitting longer than a
predetermined time limit and then disable the transmitter.
Comply
I. Control station packaging shall incorporate sufficient electro-magnetic shielding of radio and
power supply components to allow multiple control stations to be located at the same site
without causing unit-to-unit interference.
Comply
J. Proposed control station radios must be operable on new rebanded 800MHz NPSPAC
frequencies as well as 700/800MHz conventional and trunked frequencies.
Comply
K. Minimum electrical specifications as follows:
• Channel Capacity: 24 channels per system (8 systems/tiers)

• Talk Group Capacity: 16 talk groups per system/tier, minimum
• RF Power Output: Sufficient power to provide required radio coverage, but not
less than 10 watts.
• Primary Input Voltage: 120VAC, 60Hz, single-phase with 3 conductor grounded
line cord.
• Optional Battery: 12VDC designed for 4-hrs operation
• Shock and Vibration: MIL STD 810 C, D, E & F
frequencies)
• Transmitter
frequencies)
• Talk group Selection: 16 talk groups per system
• Channel Spacing: 25/12.5/6.25KHz;
• NPSPAC Spurious/Harmonic: At least 70db below carrier
• Frequency Stability: 1.5 PPM from -25°C to 60°C
• Modulation: 11KOF3E;16KOF3E;8K10F1E; 8KF10D
• +/-5KHz for 100% @ 1KHz
• +/-3KHz NPSPAC
• Audio Distortion: Less than 3% @ 1KHz
• Audio Response: +1/-3dd of a 6db-per-octave pre-emphasis characteristic,


• 300Hz to 3KHz.
• Duty Cycle (EIA): Transmitter 20%
• Receiver
frequencies)
• Channel Capacity: 24 channels per system (8 systems, min.)
• Channel Spacing: 25/12.5/6.25 KHz/NPSPAC
• Sensitivity:
• EIA SINAD (20 dB) 0.50 microvolts
• Selectivity: -70db
• Frequency Stability: 1.5 PPM from -25° to 60°C
• Modulation Acceptance: +/-7KHz
• Intermodulation: -70db
• Audio Output: At least 1.5 watts, no more than 3% distortion at 1KHz
• Duty Cycle (EIA): Receiver 100%
Comply
5.4 Fixed Site Equipment Radio

A. Meet APCO minimum recommendations and EIA/TIA standards for P-25 Public Safety
700/800MHz trunked radio systems. Furnished equipment must be operable as a combined
Phase I and Phase II infrastructure.
Question:
14. Is it the intent of the RFP for vendors to respond with a Phase 2 TDMA operational
system within the 18 month implementation? The system should be configured and
operational for Phase 1 FDMA but fully hardware capable of Phase 2 TDMA. Furthermore,
the coverage design must accommodate Phase II without coverage degradation.
Comply
Motorola meets and exceeds this requirement.
The GTR 8000 base station infrastructure is operable in Phase 2 TDMA mode via
a software upgrade. Pricing for the Phase 2 TDMA software upgrade may be
provided.
Both the GTR 800 and the tower top amplifier provided support two receive
antennas for receive branch diversity. Receiver diversity helps to compensate for
the difference in coverage between TDMA and FDMA. Fixed site equipment not


supporting diversity receive would have to be replaced or require additional sites
when upgrading to TDMA.
B. Equipment must comply with FCC Part 90 Rules and Regulations for stability, deviation,
spurious and harmonic emissions.
Comply
C. Base/repeater stations shall be designed for continuous-duty, 100% operation at full
manufacturer’s specification.
Comply
D. Infrastructure shall incorporate site monitor and infrastructure alarm systems having the
ability to report major/minor infrastructure functionality alarms on multiple dispatch- located
alarm console display devices. Additionally, the alarm reporting system shall have the capability
of being remotely accessed for the monitoring and remote-interrogation of field/site related
alarms, using a laptop configuration from any node within the network.
Comply
E. All transmitter sites shall utilize 48VDC or 24VDC battery backup subsystems sized for a
minimum 8-hour full load capacity and must include auto/transfer natural gas/LPG or diesel
fueled standby generator systems.
Comply
A 48VDC rectifier system is included at each RF site
F. The proposed infrastructure shall include a "Fail-Soft" trunking scheme designed to maintain
network performance as critical site components fail. Proposed network solutions must be fault
tolerant with redundant levels of computer hardware/software, as necessary, to maintain trunked
operation during equipment failures.
Comply
G. System infrastructure equipment shall support special services, i.e. encrypted voice, data
transmission, multiple Computer Aided Dispatch (CAD) system interfaces, Automatic Vehicle
Location (AVL) interfaces, telephone interconnect, audio recording of talk groups, and
collection of system operational data.
Comply
Motorola’s proposal includes encryption, mobile data, and interfaces for: CAD,
AVL, telephone interconnect, logging to the Verint AudioLog, and email
notification.
H. The proposed infrastructure solutions shall have the ability to be expanded, without
having to replace previously-installed like equipment. The proposed infrastructure hardware must
be configured to readily accept the installation of additional infrastructure sites above that
included in the Proposer’s design, to accommodate future population expansion and growth
within the County.


Comply
Each RF site can be expanded to 24 channels and the Simulcast system can be
expanded to 15 sites
I. Minimum electrical specifications as follows:
• Number of Frequencies: One transmit; one receive

• Power Input: Configured for either 48VDC or 24VDC operation per Section 6.2.3.1.
• Operating Temperature: -30°C to +60°C
• Humidity: 95 % relative humidity @ 50°C (typical)
• Duty Cycle: 100 % Continuous Operation
• Transmitter
• RF Power Output: Sufficient power to achieve desired coverage, but not less than
100 watts.
• Frequency Stability: 0.001PPM from -30°C to +60°C ambient.
• Referenced to GPS-disciplined local oscillator frequency standard.
• Emission Designator: 11K0F3E;8K10F1E;16K0F3E; 8K10F1D
• Audio Response: Within +1, -3db of a 6db per-octave pre-emphasis from 300Hz
to 3KHz, per EIA standards.
• Audio Distortion: Less than 2% @ 1KHz
• Spurious/Harmonic: More than 70db below carrier.
• Modulation Deviation: 0 to +/-5KHz P-25 Compliant per TIA 102 CAAB
frequencies)
• FM Hum and Noise: -55db below carrier, or better
• Receiver
frequencies)
• Channel Spacing: 25/12.5/6.25 KHz; NPSPAC
• Mod. Acceptance: +/-7 KHz minimum
o Frequency Stability: 0.001PPM from -30° to +60°C ambient.
o Reference to GPS-disciplined local oscillator frequency standard in
simulcast configurations.
• Sensitivity:
• 20 dB Quieting Less than 0.5 microvolts
o 5 % BER Less than 0.50 microvolts
o Selectivity: -70db minimum
Intermodulation: -80db


• Audio Output: 1-watt into 8-ohms with no more than 5% distortion at 1KHz (for
local speaker) 600 Ohm line level output, adjustable -20 to +3dBm.
Comply
5.5 Fixed Station Equipment Microwave Requirements

A. Digital voice/data technology shall be used to minimize audio-phase delays and/or
incompatibility of audio levels within the proposed network solution. Where VoIP techniques are
used to interconnect infrastructure sites, in lieu of traditional PCM multiplex channel schemes, a
robust means shall be provided thereby assuring that the highest priority possible is given to voice
packet delivery.
Comply
VLANs are utilized to provide the highest prioritization to voice packets
B. Redundant transmit, receive and base band equipment for each site, configured for automatic
hot standby operation, shall be provided. This redundant equipment must automatically switch to
the hot standby component(s) upon failure of the primary equipment. Loop-switched
configurations, where proposed, shall also incorporate monitored hot standby radio components.
Comply
All links are equipped with hot standby radios
Additionally, all links on the loop are loop protected via SNCP (for T1 loop
protection) and RSTP (for Ethernet protection)
C. A Microwave Alarm System shall be provided to monitor microwave site functions and to
provide alarm status of abnormal operational parameters of equipment associated with the
microwave system.
Comply
D. An order wire channel with individual site handsets must be provided to link all microwave
locations for testing and troubleshooting.
Comply
E. A separate 24VDC or 48VDC microwave standby battery system shall be provided and sized
for 24-hours of continuous microwave/multiplex equipment operation at each infrastructure site.
An automatic low-voltage disconnect system shall be employed to protect the battery plant from
deep-cycle discharge damage.
Comply
F. The proposed microwave subsystem system shall be initially configured for 100% excess
capacity to allow for future radio communication needs.
Comply


Motorola’s loop design allows for 600% growth, and our spur designs allows for a minimum
of 300% growth.
G. The operating frequency for the microwave system shall be no higher than 18GHz. All FCC
frequency coordination, license application preparation and engineering activities associated with
the development of the FCC license submittal, including path surveys, as necessary, shall be
the responsibility of the Contractor. Any proposed use of unlicensed, spread spectrum
microwave links is unacceptable.
Comply
H. Microwave system availability shall be no less than 99.99975% (78.8 seconds outage per
year).
Comply
J. Proposed microwave antennas, radomes, and antenna mounts must be capable of maintaining
reliable operations during sustained storm force winds of up to 120mph. Each furnished antenna
system shall be equipped with dual stiff arms/mounts to limit antenna vibration and flexing
during high wind events. If space diversity is required because of the necessity for higher
frequencies and the engineering constraints of longer distances, these requirements and all
necessary materials shall be part of the Proposal.
Comply
I. Floyd County desires the microwave links to be capable of a total bandwidth configuration of
155Mbps (OC3) and scalable to provide up to ten (10) isolated Ethernet ports with
programmable bandwidth.
Comply
J. Minimum operational service parameters of each microwave link shall be as follows:
• Unfaded Bit Error Rate (BER): Not Less Than 10-10

• Calculated RF Link Fade Margin,
• Including Circulator, Connector, and Transmission Line Losses: Not Less Than
40db.
• Maximum Faded BER: Not Less Than 10-6
• Link Outage Level: To coincide with 10-3BER, to occur at a signal level not less
than 3 db in excess of the calculated RF link fade margin.
Comply
Note: APCO minimum recommendations for Project-25 digital trunked radio systems include, but
are not necessarily limited to, the following operational and functionality characteristics:
• Digital 9.6 kb control channel; digital working channels.
• Automatic Unit Identification
• Call Privacy
• Emergency communications priority routing
• Centralized System Controller with Management Capabilities


• Multiple, Software-Controlled Talk Groups
• Priority Talk Path Scanning
• Lost/Stolen Radio Inhibit
• User Priority Levels
• Dynamic user regrouping
• Telephone interconnect operation
• IMBE digital voice coder
• Encrypted digital voice operation
• Interoperability with outside conventional/trunked radio networks
• Direct interconnectivity with other Project-25 compliant network switches
Comply

6.0 Infrastructure System Configuration

6.1 General

Floyd County has two existing 800MHz licenses for this project, WQLD890 which is licensed for
18 frequency pairs between 806 – 809MHz and WQKA969 which is licensed for 2 frequency pairs
above 809MHz. The winning vendor will be required to do all the license modifications.
Comply
Proposers are required, by Section 6.2, to provide a comprehensive functional and technical
proposal for a multi-site Project-25 compliant 800MHz simulcast trunked radio network. This
radio network should be deployed to operate as a P25 Phase 1 FDMA system. In addition,
this 800MHz radio network is required to be capable of doing both P25 Phase 1 FDMA & P25
Phase 2 TDMA without the elimination or addition of any existing hardware.
Comply
The proposed Phase 1 FDMA system infrastructure can be upgraded to Phase 2
TDMA via a software upgrade. Pricing for the Phase 2 TDMA software upgrade
has not been included.
Phase 2 TDMA uses different vocoders from Phase 1 FDMA. Consequentially, in
Floyd County, there is a difference between inbound coverage between FDMA
and TDMA. To better equalize the coverage between FDMA and TDMA, Motorola
has included a receive branch diversity tower top amplifier (TTA). Should the
County elect to upgrade to TDMA, a second receive antenna and would need to be
added which would utilize the included branch diversity TTA. A non-diversity
tower top amp would need to be replaced when upgrading to TDMA. Motorola
believes we are the only vendor who can currently provide this product.


The new digital voice network shall utilize the necessary number of infrastructure sites, as
determined by the Proposer, to meet Floyd County’s coverage requirements.
Comply
Proposers shall indicate a guaranteed level of portable and mobile area coverage and delivered
audio quality indicative of their design. Alternative multi-site design submittals using radio
technologies other than a spectrally efficient simulcast prime component will not be considered as
acceptable. The topography of Floyd County, coupled with user expectations for highly-reliable
portable radio coverage within buildings, can be most efficiently and optimally resolved using the
inherent antenna space diversity and receiver- voting characteristics intrinsic of simulcast
trunked radio configurations as compared to multisite-switched trunked radio configurations.
Question:
4. Section 6.0 states that alternative multi-site design submittals using radio technologies
other that simulcast prime components will not be acceptable. Section 6.2.1 states that
alternative multi-site design submittals using radio technologies other that simulcast prime
components will be acceptable. Section 6.2.1 then states that proposers should submit a
proposal options for a full simulcast system and a hybrid system with two sites having a
multisite configuration. Please clarify conflicting requirements.
Response: Correction, Rocky Mt. & Scout Camp sites have the proposal option of being part
of a full simulcast design and part of a hybrid multi-site/simulcast design.
15. Please clarify the requirements for the core Simulcast system.
Response: Section 6.0 fully covers the requirements.
Comply
Motorola has provided a “Simulcast Only” design and a “Hybrid” design
Proposers are required to furnish and install transmit and receive site equipment/configurations to
meet Section 7.0 (Coverage Requirements) and that adhere to those minimum technical
requirements identified in Section 5.0 for fixed site and microwave equipment.
Comply
Physical plant modifications to newly proposed County-owned sites, rental sites or existing
County-owned sites, as necessary, to accommodate newly proposed network solutions, shall be
the responsibility of the Contractor and must be factored into each Proposal Submittal’s cost
estimate. A Proposer’s failure to disclose physical plant modification cost is contrary to Floyd
County’s turnkey-project requirement and shall result in an unfavorable evaluation of that
Proposer’s Submittal.
Comply
Proposers shall provide all pertinent information concerning their equipment, relative to
electrical, mechanical, structural and physical space requirements. Proposers must consider
enhanced security and environmental issues in preparing their Proposal Response. Any known
deficiencies in County-owned sites, as well as for any newly proposed sites, that factor into
the proposed solution (inclusive of electrical or lightning protection systems) shall be stated in the
Proposal Response.
Comply


It shall be the responsibility of the Proposer to provide a turnkey system and to install
industry accepted standard electrical grounding systems and lightning protection devices to
protect proposed equipment from damage due to electrical transients on antenna systems,
power, telephone and/or control cables.
Comply
Sites determined by the Proposer to be potentially prone to flooding or other environmental

problems must be so noted by the Proposer in their Proposal Response. Engineering remedies
must be based on 100 Year Flood Plain data.
Comply
This P-25 800MHz digital trunked radio system will initially be sized to support the existing
analog network system user load (approximately 1,500 users) but is anticipated to grow by
approximately 25% additional capacity within the next five years. Therefore, the proposed new
radio network shall be capable of straightforward channel expansion via 700/800MHz, without
the addition or elimination of any existing previously installed equipment, to support ever-
increasing user needs.
Comply
Motorola has included 2,000 radio user licenses (33% additional capacity) and 10
channel capacity at each Simulcast site to support the anticipated growth
Floyd County has determined that standards-based APCO Project-25 digital voice radio
technology will adequately serve present and anticipated future needs for Floyd County and local
government agencies and shall be provided by the Contractor.
Comply
The delivery to and installation of: equipment shelters, security systems, standby and emergency
power systems, towers, antenna systems, electrical grounding systems, lightning protectors,
transmission lines, cable attachment hardware, ice shields, tower-to-building cable tray hardware
and all necessary permitting is part of this project and must be furnished by the Contractor.
Comply
All transmit/receive site-related equipment shall be remotely controlled via digital microwave
from Floyd County’s existing 911 dispatch center located in Rome, as well as their planned
backup center in Rome. Any proposed use of leased telephone interconnectivity in lieu of a
licensed microwave subsystem or County-owned fiber-optic facilities (if any at the time of
implementation) for all or any portions of this digital radio infrastructure, unless otherwise
allowed by this Specification, is unacceptable. It is desired that the radio network's
infrastructure be supported by a microwave loop(s) configuration. The vendor is encouraged to
provide alternative licensed microwave configurations with the pro and cons of each
configuration, ultimately that cannot lead to any one single point of failure caused by technical
or catastrophic loss of any site.
Comply
All links are equipped with hot standby radios (per RFP section 5.5)


Alternative microwave designs have been considered, all solutions meet the
99.99975% reliability requirements, please see the microwave section of the system
description for these options
The Contractor shall furnish and install all wiring, wiring hardware, interface electronics and
materials necessary, and at no additional cost than that identified in their Proposal/Contract, to
complete the successful implementation and operation of their proposed P-25 800MHz digital
radio network and its related equipment groupings.
Comply
6.2 Simulcast Configuration

6.2.1 General
Section 2.0 of this Specification generally describes the Floyd County’s existing VHF and UHF
conventional analog voice radio network. Proposers are required, by Section 6.2, to provide a
comprehensive functional and technical proposal for a multi-site Project-25 compliant 800MHz
simulcast trunked radio network. The new digital voice network shall utilize the necessary
number of infrastructure sites, as determined by the Proposer, to meet County’s coverage
requirements.
Per Addendum 1, released October 21, 2010, Harris Question 4:
Question:
4. Section 6.0 states that alternative multi-site design submittals using radio technologies
other that simulcast prime components will not be acceptable. Section 6.2.1 states that
alternative multi-site design submittals using radio technologies other that simulcast prime
components will be acceptable. Section 6.2.1 then states that proposers should submit a
proposal options for a full simulcast system and a hybrid system with two sites having a
multisite configuration. Please clarify conflicting requirements.
Response: Correction, Rocky Mt. & Scout Camp sites have the proposal option of being part
of a full simulcast design and part of a hybrid multi-site/simulcast design.
Comply
Proposers shall indicate a guaranteed level of portable and mobile area coverage and delivered
audio quality indicative of their design. Alternative multi-site design submittals using radio
technologies other than a core simulcast prime component will be considered. The topography
of Floyd County, coupled with user expectations for highly-reliable portable radio coverage
within buildings, can be most efficiently and optimally resolved using the inherent antenna
space diversity and receiver-voting characteristics intrinsic of simulcast trunked radio
configurations as compared to multisite-switched trunked radio configurations.
Comply


Therefore, it is desired that the new Project-25 compliant 800MHz simulcast trunked radio
system incorporate infrastructure pricing options for both an integrated digital simulcast
network configuration (i.e., Rocky Mt. & Scout Camp sites as full-channel simulcast sites) and
an integrated digital hybrid simulcast/multisite system configuration (i.e., Rocky Mt. & Scout
Camp sites as multisite sites).
Comply
Proposers are required to furnish and install transmit and receive site equipment/configurations to
meet Section 7.0 (Coverage Requirements) and that adhere to those minimum technical
requirements identified in Section 5.0 for fixed site and microwave equipment.
Comply
Physical plant modifications to newly proposed County-owned sites, rental sites or existing
County-owned sites, as necessary, to accommodate newly proposed network solutions, shall be
the responsibility of the Contractor and must be factored into each Proposal Submittal’s cost
estimate. A Proposer’s failure to disclose physical plant modification cost is contrary to Floyd
County’s turnkey-project requirement and shall result in an unfavorable evaluation of that
Proposer’s Submittal.
Comply
Proposers shall provide all pertinent information concerning their equipment, relative to
electrical, mechanical, structural and physical space requirements. Proposers must consider
enhanced security and environmental issues in preparing their Proposal Response. Any known
deficiencies in County-owned sites, as well as for any newly proposed sites, that factor into
the proposed solution (inclusive of electrical or lightning protection systems) shall be stated in the
Proposal Response.
Comply
It shall be the responsibility of the Proposer to provide a turnkey system and to install
industry accepted standard electrical grounding systems and lightning protection devices to
protect proposed equipment from damage due to electrical transients on antenna systems,
power, telephone and/or control cables.
Comply
Sites determined by the Proposer to be potentially prone to flooding or other environmental
problems must be so noted by the Proposer in their Proposal Response. Engineering remedies
must be based on 100 Year Flood Plain data.
Comply
This 800MHz digital trunked radio system will initially be sized to support the existing
analog network system user load but is anticipated to grow by approximately 25% additional
capacity within the next five years. Therefore, the proposed new radio network shall be
capable of straightforward channel expansion via 700MHz, without requiring the
replacement of previously installed equipment, to support ever-increasing user needs.
Comply
Motorola is proposing the GTR 8000 Expandable Site Subsystem at all sites. Our
loading analysis determined that 9 channels would provide sufficient capacity. The
Simulcast sites are equipped with 10 channels and can be expanded to 12 channels
within the proposed cabinets, providing 33% growth.


Floyd County has determined that standards-based APCO Project-25 digital voice radio
technology will adequately serve present and anticipated future needs for City and local
government agencies and shall be provided by the Contractor. Initial service requirements
involve the continued support of mobile data technologies. Proposers must include a description
on how their backbone infrastructure equipment can support mobile data hardware, in a manner
that voice and data operations are integrated within the same infrastructure component(s), and
application software.
Comply
The delivery to and installation of: equipment shelters, security systems, standby and emergency
power systems, towers, antenna systems, electrical grounding systems, lightning protectors,
transmission lines, cable attachment hardware, ice shields, tower-to-building cable tray hardware
and all necessary permitting is part of this project and must be furnished by the Contractor.
Comply
All transmit/receiver site-related equipment shall be remotely controlled via digital microwave
from Floyd County’s existing dispatch center and the EOC/Back-up Center. Any proposed use of
leased telephone interconnectivity in lieu of a licensed microwave subsystem or County-owned
fiber-optic facilities (if any at the time of implementation) for all or any portions of this digital
radio infrastructure, unless otherwise allowed by this Specification, is unacceptable.
Comply
It is desired that the radio network‘s infrastructure be supported by a microwave loop(s)
configuration. The vendor is encouraged to provide alternative licensed microwave configurations
with the pro and cons of each configuration, ultimately that cannot lead to any one single point
of failure caused by technical or catastrophic loss of any site.
Comply
All links are equipped with hot standby radios (per RFP section 5.5)
Alternative microwave designs have been considered, all solutions meet the
99.99975% reliability requirements, please see the microwave section of the system
description for these options
The Contractor shall furnish and install all wiring, wiring hardware, interface electronics and
materials necessary, and at no additional cost than that identified in their Proposal/Contract, to
complete the successful implementation and operation of their proposed 800MHz digital radio
network and its related equipment groupings.
Comply
6.2.2 Control Point (Prime Site) Equipment
The Control Point equipment site shall contain, minimally, the following major equipment
groupings:
System Controller
Simulcast Equalization/Sync Equipment


Console Electronics/Audio Controller Remote
Sites Microwave Link
Redundant local area network routers/switches
Battery & Inverter Systems
Adequately sized standby power Connectivity to
accessed Emergency Power Interoperability Link
Base Stations
Link Control Equipment
Radio/Microwave Alarm System
HVAC System
Inert Gas Fire Suppression System
Comply
The Contractor shall furnish and install all wiring hardware, cable trays, interface electronics,
terminal blocks, and materials necessary to complete the successful implementation and operation
of this site and its equipment groupings. Infrastructure equipment proposed for the Control Point
must meet the minimum requirements specified by Sections 5 and 6.
Comply
It is acceptable for the Control Point site to also serve as a co-located simulcast radio site.
However, Floyd County has expressed concern over the potential vulnerability of a single
Control Point location, as it could inadvertently become a single-point failure mode for the new
digital radio network. Therefore, Proposers are required to incorporate an optional dual-Prime
Site, Redundant Control Point design into their proposed solution. This submittal requirement is
mandatory and those proposals failing to include such a dual-site redundancy option will be
considered as being unresponsive to these Specifications.
Comply
The prime simulcast control site provides the simulcast synchronization and
receiver voting selection for the system. Motorola has provided an optional dual-
Prime site to be located at the Floyd 911 center. This option will allow this site to
assume the control of the simulcast system in the event that the Mt. Alto prime site
is rendered out of service. Since multiple redundancies have been built into the
system, the dual-Prime will require manual activation by someone at Floyd 911.
6.2.3 Typical Simulcast Infrastructure Site Deployment
Proposers are required to supply, turnkey, all technical support, equipment, material and labor
necessary to develop each proposed simulcast infrastructure site into a functional P-25 800MHz
digital radio facility, fully incorporated into the specified communications system.
Comply
Floyd County desires for Proposer to include language that ensures initial beneficial pricing that
will be offered to the Floyd County for the periods described in Section 16.
Comply
The County has the following locations, that may be but not limited to, the consideration for
infrastructure sites for the new P-25 800MHz digital simulcast trunked radio network:


• Mt. Alto Site (+34˚14' 01.01" -85˚ 13' 54.70")
o The County has an option on this property and is near the VHF/UHF site on
Mount Alto. This property has no tower, shelter or generator but is near an access
road.
• Leonard Road Site (+34˚07' 52.17" -85˚ 11' 55.08")
o Property owned by the County and is shared by County water tanks. This
property has no tower, shelter or generator, but does have an access road.
• Fouche Gap Site (+34˚ 18' 56.00" -85˚ 18' 32.00")
o The County has an option on this property. This property has no tower, shelter
or generator but is near an access road.
Correction to Section 6.2.3, (Page 52) Typical Simulcast Infrastructure Site
Deployment:
•Fouche Gap Site (+34° 18' 35.00" -85° 19' 39.00")
The County has an option on this property. This property has no tower, shelter or
generator but is near an access road.
• Cave Spring Site (+34˚06' 28.56" -85˚ 19' 30.43")
o The County has an option on this property. This property has a 160ft guyed
tower, but no shelter or generator, does not require an access road.
• •Shannon Site (+34˚20' 18.60" -85˚ 02' 59.00")
o This site is a former AT&T microwave site. The County has an option on
this property. This property has a 100ft freestanding tower, shelter and access
road, but no generator.
• Hillindale Site (+34˚12' 20.64" -85˚ 06' 35.08")
o Property owned by the City of Rome, and is shared by City water tanks and
a cellular tower. This property has no tower, shelter or generator but does have
an access road.
• Rocky Mt. Site (+34˚21' 02.77" -85˚ 17' 33.84")
o This site owned by Oglethorpe Power Corporation, however, the County has
negotiated an agreement to use the shelter, tower and generator at this location.
This site has a 120ft tower with an 800MHz antenna system, shelter, generator and
access road.
• Scout Camp Site (+34˚31' 32.70" -85˚ 05' 58.70")
o Property owned by the Boy Scouts, however, the County has negotiated an
agreement to place the site at this location. This property has no tower, shelter
or generator but does have an access road.
Understood
The construction of site access roads shall be the responsibility of the County. The availability of
electric and gas utilities shall be the responsibility of the Contractor. Improvements to the land
spaces utilized by the towers, equipment shelters, site grounding, site civil work, security
systems, all permitting, including, but not limited to NEPA, SHPO, FAA etc., on-site electrical


services and standby power systems shall be the total responsibility of the Contractor.
Per Addendum 3, released November 19, 2010, Question 3:
Question:
3. This requirement was discussed at the pre-bidders’ conference. It was Motorola’s
understanding from the dialogue between Tusa Consulting and Floyd County that Floyd
County will be responsible to bring any required power, utilities, etc. to within 50 feet of the
shelter location. Please clarify this requirement to the RFP.
Response: The construction of site access roads, the availability of electric and gas utilities
shall be the responsibility of the County. Improvements to the land spaces utilized by the
towers, equipment shelters, site grounding, site civil work, security systems, all permitting,
including, but not limited to NEPA, SHPO, FAA etc., on-site electrical services and standby
power systems shall be the total responsibility of the Contractor.
Comply
Proposers shall refer to Sections 9.0, 10.0 and 11.0 for specific requirements pertaining to
equipment shelters, towers and standby generator systems.
Understood
A typical P-25 digital simulcast radio infrastructure site equipment shelter shall contain,
minimally, the following major equipment groupings:
800 MHz Simulcast Transmitters (no less than 6 channels)

800 MHz Simulcast Receivers (no less than 6 channels)
GPS-disciplined local oscillator
Simulcast timing/delay equipment
Receiver Multi-coupler System
Transmitter Combiner System
Transmitter Antenna Systems
Receiver Antenna System
Tower top preamplifiers
Remote site
Microwave Links Site
Alarm Equipment
Battery & Inverter Systems
Adequately sized standby power
Connectivity to accessed Emergency Power
Comply
Motorola’s design incorporates redundant configurations for the remote simulcast
sites. The use of a Branch Diversity Tower Top Amplifier (TTA), multiple
transmitter combiners and receiver multicouplers, fully redundant GPS Rubidium
based frequency standards, dual site routers, and LAN switches have been
provided. Since this is an IP based system, there are no remote site controllers like


the current analog simulcast system. The network connections are distributed in
an odd channel and even channel configuration for redundancy
Infrastructure equipment proposed for all simulcast sites must meet or exceed the minimum
requirements specified by Sections 5.0 and 6.0.
Comply
6.2.4 Site Power Systems
The digital radio infrastructure sites shall operate from a 24VDC or 48VDC power source, sized
to sustain full trunked-feature operation for a minimum eight-hour period. The battery system
shall utilize sealed lead-calcium cells and 100% redundant battery charger components rated
for telecommunication service. An automatic low voltage disconnect device shall be provided to
protect the battery plant from discharge-related damage. Electrical power switching/disconnect
capability shall exist at all sites such that rectifiers, batteries as well as commercial power
sources may be separately isolated in a manner whereby each component may be worked on
safely. This switching/disconnect capability shall be designed and configured such that radio
network operation is unimpaired and uninterrupted during any repair or maintenance cycle.
Comply
Motorola’s design incorporates a -48 VDC power system for all prime and remote site
equipment. The majority of equipment: base radios, remote site gateways, GPS
frequency standards, TTAs and alarm Remote Terminal Units (RTUs) operate directly
from -48 VDC. The prime site routers and LAN switches operate from 120 VAC only
and thus will be powered by inverters that will be powered from the -48 VDC source.
Motorola’s charger-rectifier design incorporates the noted disconnects so the batteries
may be tested and charger-rectifier may be serviced.
Repeater stations shall be housed in forced-air ventilated equipment cabinets. Cabinets shall be
free standing and incorporate drilled rails to accept standard 19” rack panels.
Comply
A minimum of six DC-operated repeater stations shall be housed in any equipment cabinet. No
more than eight repeater stations should be located within a single equipment cabinet. Each
cabinet shall be power-supported by redundant, metered DC/DC power converters (if required
by equipment design) sufficient to sustain the continuous operation of all repeater stations
installed within that one cabinet.
Per Addendum 3, released November 19, 2010, Question 4:
Question:
4. Section 6.2.4 paragraph 3 states that 6, 7, or 8 repeaters must be housed in a single equipment
cabinet. If a loading analysis shows only 9 channels are required (for example), could this
requirement be modified to allow fewer than 6 repeaters in a single cabinet?
Response: If a site requires more than eight repeater stations, distribution of the repeater stations
in the equipment cabinets should be as equal as possible. Sites requiring less than six repeater
stations should use only one equipment cabinet to house the repeater stations.


Comply
Each Simulcast site has two cabinets, with 5 repeaters in each cabinet
Each equipment cabinet shall incorporate a circuit-breaker power distribution panel incorporating
protection for power amplifier, exciter and receiver groupings. Individual repeater station
ventilation fan(s), if required, shall be DC powered and thermostatically controlled.
Additionally, each cabinet shall be equipped with a DC-operated fan and air filtration
components. Each equipment cabinet shall be protected by a DC-power circuit breaker, sized
for nominal load plus 35% overload factor.
Comply
The primary battery chargers, low voltage disconnects and a primary DC circuit breaker panel
shall be installed in a freestanding enclosed relay rack unit. Likewise, the system controller
and console/audio controller equipment shall be housed in freestanding equipment cabinets
similar to those used for repeater stations.
Comply
Each controller shall be powered either directly from the DC Battery Plant or by individual,
redundant DC/120VAC power inverters whose minimum site/system capacity shall be twice that
of calculated controller loads, i.e., if calculated controller load is 1KW the inverter shall be rated
for no less than 2KW.
Comply
Site Controllers are 48VDC powered directly from the DC plant
Auxiliary site loads essential to proper system operation, i.e. tower-top preamp, redundant GPS
reference oscillators and receiver multi-coupler, shall be interconnected directly to the site's
battery system. Additionally, the redundant GPS reference oscillators shall have a properly
sized UPS between the oscillator and the battery supply.
Comply
The GPS frequency standards utilize a -48 VDC source and have redundant power
modules (separate DC breakers on the charger-rectifier), thus a UPS is not used.
6.2.5 Infrastructure Functionality
The proposed digital radio solution shall utilize a P-25 Common Air Interface (CAI) digital
control channel scheme, whereby user-initiated feature requests and talk group/working
channel assignments are processed digitally over a single control channel. The remaining
channels shall operate as working channels for analog or digital voice traffic.
Comply
The proposed Motorola design is a fully Project 25 compliant system as required by
this RFP. The system does not provide analog trunked operation as this is not part of
Project 25.


Use of infrastructure solutions involving embedded control signaling in lieu of this single
digital control channel concept are contrary to Project-25 requirements and are not acceptable.
Additionally, the single digital control channel shall have a level of redundancy sufficient to
meet the overall requirements and intent of this specification for a no-break, life- critical radio
communications network. Redundant control channels must automatically rotate in sequence
to “exercise” this support capability in a controlled scheme. When not in use as a control
channel, the previously-assigned control channel will operate in the trunked pool of digital voice
channel.
Comply
The proposed solution must be robust in design to assure continued operation should any of the
following failures (or combination thereof) occur:
A. Loss of transmitter(s) operation

B. Loss of receiver(s) operation
C. Failure of dispatch console terminal(s)
D. Failure of console/audio controller
E. Failure of one site controller
F. Loss of DC-DC power converter(s)
G. Failure of entire single site.
H. Loss of Control Channel(s)
I. Loss of Prime Site/Control Point
J. Loss of single/multiple microwave path connectivity
Comply
Proposers shall furnish a description of the effect each of the above listed failure modes
would have on their proposed network configuration. Proposers shall also describe appropriate
mitigation/restoration steps to return the network to full operational capability in response to
each of the above listed failure conditions.
Comply
The following describes the effects of the above failures on the proposed system:
A. Loss of transmitter(s) operation - Channel(s) are taken out of service system
wide until repaired.
B. Loss of receiver(s) operation - Channel(s) are taken out of service system wide
until repaired.
C. Failure of dispatch console terminal(s) - The console operator position(s) are
out of service until repaired.
D. Failure of console/ audio controller - The Motorola system has no
console/audio controllers since it is a totally IP based infrastructure. The Zone
Core has all of the servers that operate the IP system. If connection to the Zone
Core is lost or the Zone Core is down, Motorola has provided backup control
stations for each console position per the RFP.


E. Failure of one site controller - The prime site is the only site that has site
controllers. The remote sites have no site controllers. The prime site controller
(GCP8000) configuration is fully redundant (two complete controllers). If one
should fail, the standby takes control. This is transparent to the users on the
system.
F. Loss of DC-DC power converter(s) - The Motorola design uses redundant
Charger-Rectifier configuration that has multiple power modules that are
independent of each other. If one should fail, the others can handle the load.
Motorola has used inverters in the N+N configuration (for routers and LAN
switches on the prime and remote sites), the failure of one inverter will not impact
the Trunking system.
G. Failure of entire single site. – Only the failed single remote site will be affected,
the remaining remote sites will remain operational. A reduction in RF coverage
will be experienced primarily in the area served by that failed site.
H. Loss of Control Channel(s) – The system is configured with 4 control channels
and will automatically role to the next available control channel. The controller
will immediately use the next channel (1, 2, 3, or 4).
I. Loss of Prime Site/ Control Point - The loss of the prime control point would
render the simulcast system down. ITAC channels can be utilized in the event of a
Prime Site failure. However, a dual-Prime site option has been provided to address
the Simulcast failure scenario.
J. Loss of single/multiple microwave path connectivity – The loss of a single
microwave path within the loop would cause the traffic to switch and therefore all
the sites in the loop would remain operational. The loss of a single microwave
path for a spur will render that microwave link inoperable. The microwave system
proposed is protected against such failure because it is equipped with hot-standby
radios.
6.2.6 Simulcast Site Antenna Systems
The Contractor shall furnish and install antenna systems specifically designed to meet the
coverage requirements and objectives described by Section 7.
Comply
The Contractor shall equip all antennas, with gas tube lightning arrestor devices (Polyphasor or
equivalent). All coaxial cable elements used as interconnecting jumpers for outdoor- mounted
equipment or transmitter components shall be 1/2" Andrew FSJ4-50B or equal. Receiver multi-
coupler interconnecting cables shall be 1/4" Andrew FSJ1-50A.
Comply
Contractor shall furnish and install hot dip galvanized side mount hardware sufficient to
extend the transmitter/receiver antennas a minimum of 60-inches from the nearest tower-
structure element. Transmission lines shall be grounded at the antenna, at 100ft tower
intervals, at the top most part of the tower location, at the mid point (for all towers greater than


200-feet in height), at the location where the transmission lines enter the cable bridge and at the
equipment shelter’s transmission line copper entry port. Only grounding strap kits, manufacturer-
approved for the type of transmission line installed, shall be provided. All cable shall be
neatly run down a single leg of the tower on tower cross brace brackets. All connecting
hardware will be hose clamp type of a size sufficient for the cable. No tie wraps or electrical tape
will be allowed for attaching cables to towers.
Comply
Antenna system mounting brackets, components and associated transmission line
attachment hardware shall be either stainless steel or hot-dipped galvanized steel.
Comply
6.2.7 System/Audio Control Scheme
The proposed radio network must incorporate high levels of redundancy to assure continued
trunked system operation. To provide the highest level of trunked reliability, site/system
control schemes shall be IP-based, fully redundant and utilize distributed processor technology to
the maximum extent possible.
Comply
Site/System control schemes must include protected power supply units so that the loss of a
single power supply will not interrupt control scheme operations.
Comply
Site/System controllers shall minimally provide the following features:
1. Working channel assignment.

2. Verification of user identification.
3. Assignment of call priority.
4. Electronic documentation of call type, caller/called, call time, channel
assignment, etc.
5. Monitor/control of special system features such as unit-specific calls, telephone
interconnect and talkback paging operations.
6. Ability to disable/enable call access to specific field units.
The system controller shall provide the capability of dynamically varying the total number of
simultaneous unit-specific calls (i.e., Private Calls/Individual Calls) allowable via the radio
network. This feature must allow the System Owner the ability to allow unit-specific calls to
be continuously variable on as few as one working channel to as many as the total number of
working channels provided within the radio network’s potential configuration.
Comply
The console/audio control scheme shall be equipped to initially support the current dispatch
console deployment operable in the existing analog conventional VHF/UHF radio systems. It is
envisioned that a newly constructed 911 backup Communication Center will be designed and


implemented within the next two years. Therefore, the proposed console/audio control
scheme must be sized to support a 100% increase in console devices (to facilitate a potential
dual-migration/implementation scheme for this new backup Center).
Comply
The console/audio control scheme shall be configured to provide the necessary T-1 connection(s)
to a shared radio traffic audio recording device. This device shall be of a trunk-tracking
design whereby all radio traffic conducted over the proposed number of voice channels and the
digital control channel will be archived. This recording device is part of this voice radio
communications network project and should be considered for migration to the proposed system.
The current logging recorder is a sixteen channel Verint model purchased two years ago and is
integrated into the existing Positron Front Line VIPER CAD dispatch consoles, that is shared by
all users of the County's radio system.
Comply
6.2.8 Radio Network Alarm System
The Contractor shall furnish and install an automatic alarm system to monitor and alert, as a
minimum, status (per site) on the following radio system operating parameters:
Major Alarm Conditions

1. Site Controller Failure.
2. Control Channel Failure.
3. Console/Audio Controller Failure
4. Receive Amplifier Failure
5. AC Power Failure
6. High Reflected Power, Tx Ant.
7. Battery Charger Failure, Major
8. Generator Failure
9. Tower Light Failure
10. Over/under temperature alarm (HVAC failure)
Comply
Motorola has provided RTUs to collect all of the site and system information detailed
above. It can be displayed on both the Network Manager’s terminal and the Motorola
MOSCAD Graphic Master Central Screen.
Minor Alarm Conditions

1. Door Alarm
2. Tripped DC Breakers(s)
3. Low Transmitter Output (each transmitter)
4. Battery Charger Failure, Minor
5. Low Fuel
Comply


Motorola has provided RTUs to collect all of the site and system information detailed
above. It can be displayed on both the Network Manager’s terminal and the Motorola
MOSCAD Graphic Master Central Screen.
A summed major/minor alarm indication should be displayed on each alarm system terminal
position. This alarm indication should appear as a flag at a conspicuous area on the flat-screen
display field. Determination of specific alarm point conditions shall be obtainable from any
dedicated alarm system terminal position.
Question:
16. Which customer site locations (non-radio sites) will the alarm point monitoring be required?
Response: The E911 Center & the EOC/Back-up E911 Center.
Question: How many total alarm system terminal positions are needed?
Response: A total of 2 (two) are needed, 1 (one) at the E911 Center and 1 (one) at the
EOC/Back-up E911 Center.
Comply
6.2.9 Regional Interoperability via Project-25 ISSI
Currently, the nearby counties operate a variety of conventional and trunked radio
communication systems on different frequency bands. Please refer to Section 3, user needs
interoperability requirements with surrounding radio networks. Floyd County is, by virtue of
this Specification, planning its radio network modernization toward Project-25 Phase I
compliancy. Other jurisdictions within the Region are either actively considering the use of
Project-25 technology or, are currently in the procurement processes.
Understood
In any case, the critical importance placed on seamless interoperability between Project-25
digital voice radio networks, of various manufacture, cannot be overstated.
Understood
The set of minimally-acceptable feature and protocol standards to facilitate the linkage of
distributed Project-25 radio systems has been defined as the Inter Sub System Interface, or ISSI.
In 2006 a series of protocols and procedures for an initial layer of multi-network
interoperability was approved by the APCO Standards Committee. This initial ISSI release
defined trunked group and individual call transport between multiple systems as well as
subscriber user roaming and unit authentication. Future ISSI releases, will encompass other
features such as Over-the-Air Rekeying; data transport; cross-network console operability and
conventional radio system interoperability.
Understood
In February 2010 Floyd County applied for a $2.4 million Georgia Homeland Security
Grant titled Northwest Georgia Interoperable Communications. The purpose of the grant is to
increase coverage, expand mutual aid interoperability and facilitate future growth of the NW


GA/TN Valley Regional Communication System further into Georgia. Floyd County has
identified a tower site location in northwest Gordon County that will enhance network
coverage in South Walker County, and extend system coverage into Whitfield, Floyd and
Gordon Counties. The County has had discussions with key public safety officials from each
of these entities, and has confirmed their cooperation and commitment to incorporating 800MHz
interoperability into their mutual aid response plans. The grant request adds one 10-channel,
simulcast site with microwave connectivity to the NW GA simulcast cell. By extending
coverage southward this will not only enhance first responder interoperability and encourage
future growth, but will also make significant strides toward achieving a long-range goal of master
site connectivity with Cobb County, Georgia.
Understood
Once the NW GA/TN Valley Regional Radio System is connected to the Cobb County/UASI
Master Site the County will establish seamless roaming from Atlanta to Knoxville on I-75, and
multi-State Emergency Operations Center voice communication.
Comply
The current ISSI standard will not provide seamless roaming, only Motorola’s
InterZone connectivity can currently provide seamless roaming and other Trunking
features across multiple systems. Please refer to the ISSI section of the system
description for an ISSI comparison and alternative InterZone offering.
With the selection of the alternative InterZone offering, Motorola exceeds the basic
ISSI functionality.
Floyd County has taken great care to insure alignment between local, regional and state
interoperable communication plans. Just as the State of Georgia’s vision for statewide
interoperability is connecting 700/800MHz wide area trunked radio systems and
conventional VHF systems through the statewide (GIN) MotoBridge network, so is the
intent of the NW GA/TN Valley Regional Radio System and GEMA Area 6.
Understood
Prior to the application for this grant (Phase III), the State was awarded a Public Safety
Interoperable Communications Grant (PSIC) for $5.7 million for Phase II (Catoosa County
began Phase I without any grant assistance.). In 2007, Catoosa County executed Memorandums
of Understanding with two other North Georgia Counties, Walker and Dade, to join the NW
GA/TN Valley Regional Radio System, and submitted an application for FY07 funding. This
system design incorporates three 10-channel simulcast sites while upgrading and relocating the
Catoosa 5-channel repeater site. This project was awarded and is in the final stages of
completion. The north GA site will serve as the primary voice communication network for
public safety in Catoosa, Walker and Dade Counties and provide wide area, SAFECOM Level 6
interoperability for the various disciplines, cities, and counties operating on the NW GA/TN
Valley Regional Radio System. To date, there are three Georgia counties and nine Tennessee
counties utilizing this wide area radio system.
Understood
It is the intention of the County that this grant will initiate Phase III of the Northwest Georgia
Interoperable Communications project. The system design proposed for FY09 increased the
number of simulcast sites for North Georgia from three to four. It provides countywide


coverage of the Northwest Georgia Regional Radio System throughout the combined Catoosa,
Walker and Dade counties and offers substantial overlap coverage into Whitfield, Floyd and
Gordon counties. The overlapping coverage will add unit to unit, emergency mutual aid
communications throughout most of Whitfield County and the City of Dalton by adding a few
control stations to interface their consoles or the State’s (GIN) MotoBridge equipment. This
also facilitates connectivity of the funded Floyd County P25 System, which is strategic to
interoperability throughout GEMA Area 6, and facilitates future expansion into Gordon
County, Bartow County, and the State of Alabama. Additional coverage, beyond Floyd
County jurisdictional boundaries, is key to facilitating future system growth.
Understood
Proposers shall be required to:
A. Describe how their proposed Floyd County radio network solution shall be
immediately interfaced to the existing Tennessee Valley Regional Communications
System radio networks.
Comply
Please refer to the ISSI section of the system description for details on Motorola’s
offering
B. Describe how their proposed Floyd County radio network solution can be interfaced to
other regional Project-25 radio networks now under development or procurement
planning.
Comply
Please refer to the ISSI section of the system description for details on expansion to
neighboring systems.
C. Provide a commitment to support and provide migration paths for Floyd County
network solutions whereby adoption of new ISSI features and functionality (beyond
those described above) does not require “forklift” replacement of network
infrastructure.
Comply
The standards for next generation ISSI are still being developed and Motorola will
have a migration path for it, but the exact details of the migration can not be
determined until the next generation ISSI standards are completed.
D. Provide a commitment to cooperatively help resolve ISSI interface issues between the
proposed Floyd County radio network and those radio vendors supporting other Regional
participants, if portions or all of those agencies utilize Project-25 radio networks
manufactured by other parties.
Comply


6.3 Subscriber Equipment

Mobile, portable and control station equipment requirements are identified in Sections 4 and 5.
Specific equipment groupings and quantities are contained in Section 16, Pricing.
Understood
It is likely that a majority of indicated user equipment will be ordered at some point during the
implementation process but may not be part of the initial system order. Quantities indicated
are only approximate estimate and are likely to change.
Understood
6.4 Legacy Interoperability and Backup Radio(s) System

Computer-controlled (radio user initiated) and dispatcher-controlled interoperability link stations
shall be located at the most appropriate infrastructure tower location to achieve no less than
DAQ 3.4 audio quality into the distant host network. The Floyd County preference for
interoperability link station placement is at Floyd County-owned sites, if any are proposed in the
design.
Comply
All interoperability sub-system antenna transmission lines shall be 1/2" Andrew LDF4-50A
or equal and equipped with suitable lightning and electrical surge protection devices.
Comply
The proposed network shall include all computer-controller interfaces, control station(s) and
antenna systems necessary to successfully provide the interoperability described above and by
Section 3.2.6. Proposers should consider the re-use of existing non-obsolete Floyd County-owned
VHF, UHF and/or 800MHz base station equipment to meet identified interoperability
requirements. Should a Proposer intend to reuse existing equipment, those types of equipment
must be identified in the Proposal Response. If such interoperability equipment is a current
component of the analog system, those items may not be removed from regular operational
use if doing so would degrade existing conventional VHF/UHF analog capabilities. Such
equipment, however, may be tested during installation and implementation of the proposed
system solution and at the conclusion of user migration, may be converted to a resource of the
new digital radio network.
Comply
Computer-controlled interoperability links shall become active only whenever a user has
specifically selected, from its portable/mobile unit, any one of the interoperability link talk
groups defined by Section 3.2.6. These links shall also be available for dispatcher monitoring
and/or selection.
Comply
6.5 Voice Encryption

Each of the proposed P-25 trunked digital RF channels shall be equipped to support voice
encryption using the Improved Multiband Excited (IMBE) Vocoder.
Comply


The number and tiers of radios requiring encryption has been provided in Section 16, Pricing
Considerations. Encrypted mobile and portable units shall be of the same physical size and
general configuration as non-encrypted units. Accessory equipment shall work compatibility with
both types of units.
Comply
Proposed radio coverage throughout the identified Floyd County Service Area, in the digital
encrypted mode, shall be equal to that in the digital clear mode. Proposers shall be required, as
part of an oral presentation, to demonstrate both clear and encrypted voice (IMBE) audio quality
using portable/mobile equipment identical to that offered in their Proposal Response.
Comply
6.6 Transportable Repeater Systems
Public Safety agencies also desire portable repeater systems to support various special operations
involving large structure fires, police surveillance actions or disaster response events. A
combination of small, single-channel repeater systems as well as larger, easily transported
trunked communication systems are desired. The following information provides a functional
description of both Mobile Repeater and Transportable Trunked Repeater configurations.
Understood
6.6.1 Mobile Repeaters
Floyd County public safety agencies may require single-channel repeater stations at the scene of
large structural fires, out-of-area mutual aid responses and other localized events. In the event
of a structural fire, building amplifier systems (Bi-directional Amplifiers or BDAs) are often
rendered inoperable, thereby severely degrading in-building coverage at a time when it is needed
most urgently.
Understood
It is envisioned that key tactical response vehicles could be configured with a compact, easily
operated repeater system designed to enhance portable coverage within such small geographic
areas.
Understood
Functionally, the desired Mobile Repeater should be configured as follows:
• Relatively low transmitter power, i.e., 15 watts
• Compact size
• Use of unity gain, low profile antenna
• Self-contained within a waterproof, easily transportable housing
• Have a minimum of operator controls
• Operable on up to five frequencies
• Operable using 12VDC and 120VAC power sources
Comply


It is envisioned that such systems could operate within selected vehicles or could alternatively be
deployed in fixed field locations.
Understood
Proposers shall provide a full technical description of a representative Mobile Repeater
device, and per-unit pricing, as part of their Proposal Submittal.
Comply
The Digital Vehicular Repeater (DVR) is a self-contained, fully integrated, easy to
deploy in the field package that provides more flexibility in handling the radio
communications during tactical situations inside buildings or other enclosed areas.
The DVR extends radio communications for portable users in areas where the
portable radios are subject to either intermittent or complete lack of System Radio
Coverage. The DVR features easily accessible programming connectors for both the
DVR and the Mobile Radio.
Motorola has included a complete description of our DVR in the system description
and technical literature provided in Section 14.0.
6.6.2 Transportable Trunked Repeater
Floyd County also has interest in obtaining fully mobile, field deployable Transportable
Trunked Repeater package(s). These packages shall be a self-contained unit that can be
tailored to a disaster scene. Each package shall be designed to be towed by both a full-sized
pickup truck and sports utility vehicle. The trunked repeater configuration shall utilize six P-25
compatible 700/800MHz repeater stations (6 channels) and meet the same functional and
technical specifications contained in Section 5.0. The design shall incorporate an easily
raised, pneumatic antenna mast, no less than 60 ft. and no greater than 80 ft. extended, that will
support a 6db omni-directional antenna system.
Comply
Motorola’s offering provides all of the above except a hydraulic antenna mast is
provided instead of the requested pneumatic antenna mast. A pneumatic mast is
telescoping and requires the antennas and lines to be removed when the mast is
collapsed, whereas a hydraulic mast folds and the antennas can remain installed for
quick deployment and setup.
The Transportable Trunked Repeater package shall also include a power generator of sufficient
size to operate all communications equipment, area lights, HVAC and other supportive electronic
systems. The package shall include an integral fuel tank sized to support 24-hours of continuous
operation at full load. The transportable system shall have full lightning and electrical surge
protection capability and a method of easily deploying/integrating a reliable electrical
ground system for safe operation. The Transportable Trunked Repeater configuration shall
have the capability to seamlessly utilize a separate generator in case of primary generator failure.
Comply


The RF Site on Wheels includes HVAC for the enclosure, and a power generator and
an integrated fuel tank sized to support 24 hours of continuous operation at full load.
Each unit also offers ports for external ancillary power and telecommunications
network connections
Proposers shall provide a full technical description of a representative Transportable Trunked

Repeater device, and per-unit pricing, as part of their Proposal Submittal.
Comply
RF Site On Wheels is a customized, deployable solution for Mission Critical response.
It is used to temporarily replace permanent network equipment that is inoperative due
to natural disasters or terrorist acts; as well as for short term needs of added capacity
for special events and added coverage for remote disaster recovery operations. Besides
a trailer, enclosure, and articulated tower, each individual unit also includes HVAC
for the enclosure, and a power generator. Each unit also offers ports for external
ancillary power and telecommunications network connections.
The articulated 65-foot tower feature of the RF Site on Wheels supports a 6 dB omni-
directional antenna system. The antenna is hydraulically controlled and deployable by
a single individual in 30 minutes or less. The trailer can be towed by both a full-sized
pickup truck or sports utility vehicles with a bumper mounted hitch. The Site on
Wheels is designed to withstand extreme environmental conditions such as
hurricanes, sleet, hail, flooding and salt air. The enclosure proposed offers 81 19-inch
rack units that are fully adjustable for efficient storage. Motorola has included a
standalone trunked ASTRO 25 six (6) channel repeater system to be housed in the
trailer as requested by the RFP.
Motorola’s offering provides all of the above except a hydraulic antenna mast is
provided instead of the requested pneumatic antenna mast. A pneumatic mast is
telescoping and requires the antennas and lines to be removed when the mast is
collapsed, whereas a hydraulic mast folds and the antennas can remain installed for
quick deployment and setup.
Please refer to the Transportable Trunked Repeater section of the System Description
for more details.
6.6 Fire Station Alerting System

The Rome – Floyd Fire Department desires the continued ability to perform individual fire
station alerting. The Department’s fire station alerting is currently accomplished using various
tones that were broadcast over the existing analog radio system. Once a particular fire station
received its unique tone, a pre determined response would be automatically enabled, such as
setting of light and/or audible alarms, in addition to routing the audio of the station’s 800MHz
radio to the PA system.
Question:


5. During the pre-bid conference, it was discussed that the best solution for Fire Paging would be
for the Fire Department to retain their existing pagers and for each vendor to replace their VHF
paging channel with a narrow banded VHF repeater. In lieu of the requirements in Section 2.3 to
alert the Fire Stations "through a separate 800MHz analog system", is there any reason that the
Fire Stations can't be alerted using the same VHF repeater? The dispatch fire traffic call will be
simultaneously transmitted on the 800MHz Trunking system and the VHF fire/pager repeater.
Response: Proposals can include, as an option, alerting Fire and EMS stations with UHF/VHF
repeaters in addition to the 800MHz radio system. However, alerting EMS stations must use a
separate repeater than the repeater used to alert Fire stations.
Comply
Motorola is providing an integrated Fire Station Alerting interface incorporated into the MCC
7500 console system.
The County desires the new fire station alerting system to activate fire stations at all eleven (11)
locations throughout the county. As alerts are sent to the fire stations, an audible signal needs to
be heard on the County fire dispatch talk group. The locations of the Rome – Floyd Fire Stations
are as follows:
Rome - Floyd Fire Dept Station 1 617 w 1ST Street, Rome, GA 30161
Rome - Floyd Fire Dept Station 2 1601 Cave Spring Road, Rome, GA 30161
Rome - Floyd Fire Dept Station 3 411 E 12th Street, Rome, GA 30161
Rome - Floyd Fire Dept Station 4 3 Wilshire Road, Rome, GA 30161
Rome - Floyd Fire Dept Station 5 750 John Davenport Dr., Rome, GA 30165
Rome - Floyd Fire Dept Station 6 6Burnett Ferry Rd., Rome, GA 30165
Rome - Floyd Fire Dept Station 7 85 Woods Road, Rome, GA 30165
Rome - Floyd Fire Dept Station 8 90 Little Texas Valley Road, Rome, GA 30165
Rome - Floyd Fire Dept Station 9 152 Burlington Dr. Shannon, GA 30172
Rome - Floyd Fire Dept Station 10 1522 Wax Road, Silver Creek, GA 30173
Cave Spring Fire Dept Station 16 3 Georgia Ave., Cave Spring, GA 30124
Comply
6.7 EMS Alerting System

The Redmond EMS and Floyd EMS also desire the ability to perform individual EMS
station alerting similar to the fire station alerting system. As alerts are sent to the EMS
stations, an audible signal needs to be heard on the County EMS dispatch talk group.
Comply
Motorola is providing an integrated Fire Station Alerting interface incorporated into the MCC
7500 console system.


The County desires the new EMS alerting system to activate EMS stations at all eight (8)
locations throughout the county. The locations of the Redmond EMS and Floyd EMS
Stations are as follows:
Floyd EMS Headquarters 500 Riverside Parkway, Rome, GA 30161

Floyd EMS Station 2 101B Elliot Drive, Rome, GA 30165
Floyd EMS Station 3 11 Highway 411, Rome, GA 30161
Floyd EMS Station 4 1933 North Broad Street, Rome, GA 30161
Redmond EMS Headquarters 100 John Maddox Dr. Rome GA 30165
Redmond EMS Station 1 80 Redmond Rd. Rome Ga.30165
Redmond EMS Station 2 304 Russell Field Dr Bldg 800B, Rome, GA 30165
Redmond EMS Cave Spring 123 Fincher Street Cave Spring, Ga. 30124
Comply

6.8 Analog Fireground Operations

The Rome – Floyd County Fire Department has determined their need for analog
communications for fireground operations. This will be confined to unit-to-unit, non- repeated
simplex operations rather than for county-wide communications via the infrastructure
equipment sites.
Comply
6.9 Floyd County Sherriff Detention Center Operations

The Floyd County Sheriff’s Office serves warrants, houses inmates in the detention center (820
inmates) and provides security for the courts. The Floyd County Sheriff’s Office has a staff of
153 full time personnel.
Understood
The Sheriff’s Office has a dedicated UHF repeater (call sign WPMT948) at the detention
center that is used for all communications of prisoner movements and is hard wired to a
number of base stations throughout the jail facility.
Understood
The Sheriff’s Office has determined the need for a localized 800MHz repeaters on-site to
perform this function. By so doing, one or more 800MHz radios could be provisioned for local
jail use, wide-area coverage (via the trunked radio network) for prisoner transport and
interoperability with local, county and adjacent county police operations. The emergency
button operation of the portable radios should be contained to the Detention Center repeater
system, except when the portable radios are using the County 800MHz P25 trunked simulcast
radio system and the emergency button function should be part of the county-wide system.
Question:
17. Would a desktop remote controller meet the requirements of the hard wired base station?
Response: No.


Question:
How many base stations/desktop remote controllers are required at the Floyd Co Sheriff’s Office
Jail?
Response: 14
Question: How many 800MHz repeaters are required at the SO jail?
Response: However many are needed to meet the in-building coverage requirements as described
for in-building operations.
provided.
Comply
6.10 Floyd County Prison Operations
The Floyd County Prison is responsible for housing and supervising 448 inmates that perform
work in Floyd County. The department also operates a work release center which is capable of
housing 100 residents.
As with the Floyd County Sheriff’s Office, the Floyd County Prison will require an 800MHz
analog repeater for communications of prisoner movements. Currently, there is no repeater
communications system at the Floyd County Prison. The 800MHz analog repeater system for
the Floyd County Prison will be a completely new installation. The emergency button
operation of the portable radios should be contained to the Prison repeater system, except
when the portable radios are using the County 800MHz P25 trunked simulcast radio system and
the emergency button function should be part of the county-wide system.
The Floyd County Prison is responsible for housing and supervising 448 inmates that perform
work in Floyd County. The department also operates a work release center which is capable of
housing 100 residents.
As with the Floyd County Sheriff’s Office, the Floyd County Prison will require an 800MHz
analog repeater for communications of prisoner movements. Currently, there is no repeater
communications system at the Floyd County Prison. The 800MHz analog repeater system for the
Floyd County Prison will be a completely new installation. The emergency button operation of the
portable radios should be contained to the Prison repeater system, except when the portable radios
are using the County 800MHz P25 trunked simulcast radio system and the emergency button
function should be part of the county-wide system.
Analog requirements for the Floyd County Prison Operations Repeater are now removed as
outlined above.
Comply


6.11 Floyd County Mutual Aid System

Proposers shall provide an 800MHz Mutual Aid System consisting of the ICALL channel and
all four (4) ITAC channels. The 800MHz Mutual Aid System infrastructure will be located at
the Mount Alto site and must be capable of being patched to any of the P-25 800MHz Digital
Trunked Radio System talk groups. Proposers should also include services needed in obtaining
the needed FCC licensing for the 800MHz Mutual Aid System.
Comply
The 800MHz Mutual Aid System will not be required to meet the coverage requirements of the
P-25 800MHz Digital Trunked Radio System, however, proposers shall provide coverage maps of
their proposed 800MHz Mutual Aid System. The coverage maps should include both mobile
(talkout & talkback) and portable outdoor (talkout & talkback) down to a level of -106dBm.
Comply
6.12 Floyd County Fire Paging

The Rome – Floyd Fire Department desires the continued ability to receive the dispatch talk
group while having the ability to receive and transmit on the tactical talk group. The Rome –
Floyd Fire Department is currently accomplishing this function using pagers monitoring the
dispatch frequency.
Question:
5. During the pre-bid conference, it was discussed that the best solution for Fire Paging would be
for the Fire Department to retain their existing pagers and for each vendor to replace their VHF
paging channel with a narrow banded VHF repeater. In lieu of the requirements in Section 2.3 to
alert the Fire Stations "through a separate 800MHz analog system", is there any reason that the
Fire Stations can't be alerted using the same VHF repeater? The dispatch fire traffic call will be
simultaneously transmitted on the 800MHz Trunking system and the VHF fire/pager repeater.
Response: Proposals can include, as an option, alerting Fire and EMS stations with UHF/VHF
repeaters in addition to the 800MHz radio system. However, alerting EMS stations must use a
separate repeater than the repeater used to alert Fire stations.
Comply
Motorola’s offering will reuse a decommissioned VHF MTR2000 repeater to provide
800MHz Trunking dispatch traffic to the existing fire pagers.



7.0 Coverage Criteria

Question:
8. During the pre-bid conference, we requested more details on the typical user response situations
in areas on the edge of the county. Please provide anticipated number of users and user groups
that would typically operate in the following three scenarios:
a. During normal operation
b. A typical accident/fire situation
c. Any emergency disaster scenario response
Areas of particular interest are:
a. The pocket (around Scout Camp)
b. Halls Valley
c. Texas Valley
d. GA-1/US-27 at the Chattooga County border
e. The valley of Lake Marvin and Everett Springs Roads
Response: The County does not have experience with trunking systems in order to make an
adequate response to this question. Vendors are more experienced in this area and should put
forth a best effort determination of the needed requirements to meet the scenarios described above.
Understood
7.1 General

The new Floyd County P-25 Digital Trunked Radio Network shall be designed to support
portable hand-carried radio equipment, operated both on street and within residences/building
structures, at physical locations throughout the County plus a three-mile perimeter boundary.
Proposers must fully identify and guarantee the coverage predicted for their proposed solution,
per the functional and operational requirements of this Specification. The County has also
identified those critical structures which shall have in- building portable coverage, and shall be
included in the proposers Functional Test Plan and Coverage Test Plan for both signal strength
and DAQ testing.
Question:
5. Please provide the proposers with a boundary file identifying Rome’s Central Business
District.
Response: See attached map. (As provided in Addendum 1)
The additional three mile perimeter coverage area into adjacent bordering counties is now
removed as outlined above.
Comply


Per Addendum 2, Motorola will provide mobile radio coverage and portable radio
in-building coverage for no less than 95% of Floyd County. In-building coverage
is based upon a typical 2500 sq. ft. residential home with 4 dB of loss. In-building
coverage will be no less than 95% for representative buildings contained in RFP
Attachment C.
Proposers must take into account the following operating parameters in the development of their
coverage guarantee:
A. Shoulder/microphone units without antennas will be used in most instances and shall
be the normal configuration considered for the purpose of coverage design. Body and
obstruction losses must therefore be considered in the proposed network design for both
talk-in/talk-out coverage analyses.
Comply
B. Flexible, quarter wavelength antennas shall be required for portable units. Coaxial-skirt
type antennas are not acceptable due to size and other mechanical limitations.
Question:
18. Can the Coverage ATP be conducted with the antenna configuration being purchased and
used by Floyd County's users? Motorola recommends using a flexible-half wavelength antenna on
the hip with a remote speaker microphone, which will be presented at the pre-bid conference.
Response: The Specification is to be followed. If Motorola intends to offer an alternative design
using this antenna, it should be provided as an alternative solution only and not the primary
solution as that would be viewed as an exception to the RFP..
Question:
6. This section requires a quarter wavelength antenna to be used for portable units. Based on
coverage analysis to date this requirement could result in more sites needed than indicated by the
RFP. Can a half wavelength flex whip antenna be used for portable units with regards to the
coverage requirements?
The subscriber antenna configuration plays a large part in the solution offered. The half
wavelength flex whip antenna is approximately seven (7) inches in length which is only three (3)
inches longer than the quarter wavelength antenna as it is approximately four (4) inches long. The
flexibility of the half wavelength flex whip antenna aids in the comfort when the radio is worn on
the hip. It should also be noted that the half wavelength flex whip antenna is significantly more
comfortable to wear than the helical antennas that the Floyd County VHF and UHF users may be
using today.
Response: The County will accept a half wavelength antenna or a quarter wavelength antenna for
Section 7.1.B.
Comply
Motorola will utilize a flexible half wavelength antenna to meet the coverage requirements.


C. Building obstructions exist throughout the Floyd County Service Area. The
majority of dense building structures are located within Rome’s Central Business
District. These must be considered in the development of the Proposer’s coverage
guarantee. As mentioned above, a listing of specific structures requiring in-building radio
coverage is contained in Attachment C.
Comply
Motorola has added an additional Simulcast site at Blossom Hill to maximize in
building coverage in the downtown district. The Blossom Hill site is not needed to
meet the 95% county-wide mobile and portable coverage requirement, but provides
a substantial amount of additional coverage for the buildings listed in Attachment
C of the RFP.
7.2 Service Area

Both mobile radio and portable radio on-street coverage must extend throughout no less than 95%
of that area within the land region inclusive of Floyd County, plus a three-mile perimeter
overlapping area extending into its adjacent bordering counties. Desired in- building portable
coverage shall be no less than 95% within the entire land area encompassing the County.
Question:
7. Sections 7.2, 7.3, & 7.4, identify the coverage requirement to be 95% of the area. Section 7.5
requires that 97% of grids must meet or exceed the defined requirements. Please clarify the
conflicting requirements.
Response: Should read “Ninety-five percent of grids must meet exceed these defined requirements
for the system to be considered coverage compliant.”

The additional three mile perimeter coverage area into adjacent bordering counties is now
removed as outlined above.
Comply
Per Addendum 2, Motorola will test signal strength throughout 95% of the county for portable in-
residence. Motorola will provide mobile radio coverage and portable radio in-building coverage
for no less than 95% of Floyd County.


Equipment Configuration % Service % Service % Service Area
Area Area Reliability of
Reliability Reliability Central Business
of Floyd of City of District
County Rome
Mobile w/unity gain ≥95 ≥95 ≥95%
ant. % %
Portable (SMA) ≥95 ≥95 ≥95%
Outside % %
Portable (SMA) 4 dB ≥95 ≥95 ≥95%
loss % %
Coverage is defined as the minimum usable signal necessary to provide a clearly readable voice
signal without repetition (no syllables lost) from locations within building structures and
outdoors, at street level, within the defined service area. Using the Delivered Audio Quality
representations described EIA/TIA TSB-88B; the delivered audio quality throughout the service
area shall be no less than DAQ 4.0 for mobile operations and DAQ
3.4 for portable operations.
Comply
All references to coverage reliability in this Specification refer to statistical area reliability. For
example, the phrase "95% coverage" indicates that the total area described shall exhibit at least
95% statistical probability that coverage areas, if tested, would be found to support electrical
performance which equals or exceeds that minimum signal level necessary to deliver
Contracted delivered audio quality, as specified by this Specification and the Contract. However, it
will not be acceptable to provide a coverage guarantee which includes a relatively large number
of failed points within any one vicinity, while still meeting the overall goal of 95% coverage.
Comply
7.3 Building/Residence Coverage

Coverage shall be no less than 95% inside of the listing of representative buildings contained in
Attachment C. It is desired that the majority of these building structures shall be supported by the
proposed network’s fixed infrastructure (tower sites). However, Proposers shall exercise good
judgment in balancing the proliferation of costly infrastructure tower sites with the number of
building sites improved per new installation. The use of building amplifier systems, while
necessary in some instances, shall likewise be minimized to the most practical and fiscally
responsible extent possible
Question:


Comply
Motorola has added an additional Simulcast site at Blossom Hill to maximize in building
coverage in the downtown district. This reduces the need for in-building amplifier systems,
therefore providing the most cost effective hardware solution.
Proposers shall specifically address those City/County buildings identified in Attachment C

requiring building amplifier systems and shall provide a comprehensive turnkey cost to furnish
and install such coverage enhancement equipment on a per-building basis.
Comply
Please refer to the Cost Proposal, submitted separately.
Motorola has performed a detailed coverage analysis and determined that four (4)
buildings have a high probability of needing a BDA system. These buildings and the
associated BDA system costs are provided in the Cost Proposal, submitted under
separate cover.
Shorter University See Cost
Proposal
Berry College See Cost
Proposal
Winthrop Manner See Cost
Proposal
Kid's World Learning Center See Cost
Proposal
Total See Cost
Proposal
It is possible that some of these buildings could meet the coverage requirements
without a BDA system and then some other buildings could fail and therefore need a
BDA system. Therefore once the coverage testing for the buildings are completed
based on the CATP included in this proposal it will be determined exactly which
buildings will need BDA systems. Motorola will then use the cost included in this
proposal for BDA systems to install BDA systems in those buildings in order to meet
the coverage requirements.
If any of these representative buildings fail to demonstrate 95% reliable coverage (DAQ 3.4
Audio Quality per section 7.5), the following procedure will be followed:
A. Measurements will be made from every failed test point to determine if in- building loss


exceeds 25db for that specific test point.
Comply
B. If penetration loss exceeds 25db, that specific test point will be omitted from
reliability calculations.
Comply
C. If penetration loss is equal to or less than 25db, that specific test point will remain
included in the reliability calculations.
Comply
D. After determining which (if any) test points are omitted, reliability calculations will
be repeated. At that time, reliability of less than 95% for the structure represents a failure
for the building.
Comply
If insufficient coverage is identified, the Contractor will be responsible for modifying the
system, at no additional cost to Floyd County, as may be necessary to achieve the required
reliability within the failed building. This may include any or all of the following approaches:
1. Bi-directional amplifier (BDA) system installed in the building.*

2. Passive repeater systems installed in the building.
3. Satellite receiver systems in or near the building.
4. Modifying/adjusting repeater site antenna systems.**
Comply
(*Note 1) The determination to utilize a BDA within any structure will be engineered as a part
of a comprehensive system design. BDA systems shall not be installed in structures in such a
manner or proliferation that creates interference with the overall digital radio network’s operation.
Comply
(**Note 2) If any changes are made to the fixed sites (such as re-orienting antenna patterns) in
order to resolve building coverage failures, then a complete re-test of coverage shall be required
at no additional cost to Floyd County.
Comply
The Digital Radio Network shall support no less than 95% in-residence portable radio coverage
reliability throughout the land area of Floyd County. For the purpose of defining in-residence
portable radio loss factors, Proposers shall assume that the typical in-residence structure
occupies up to 2,500 square feet and utilizes single-floor, wood-framed brick veneer type
construction.
Question:
Please provide the proposers with the building loss factor to be used in analyzing in-building
coverage for the in-residence building defined in the RFP.


Response: For the purpose of defining in-residence portable radio loss factors, Proposers shall
assume that the typical in-residence structure occupies up to 2,500 square feet and utilizes single-
floor, wood-framed brick veneer type construction.
Comply
Motorola has determined that the typical loss for the residence structure is 4 dB.
7.4 Propagation Analysis

Proposers, as part of their Proposal Submittal, shall provide a formal statement that the
coverage objectives specified in Section 7.1 - 7.3 are met by their proposed solution. ANY
exception taken to the specified coverage requirements must be clearly identified with a
detailed description of the extent of the exception and the reason for which it was taken, in
order for full consideration to be given to the Proposer during the evaluation process.
Comply
Proposers shall provide written descriptions of the processes and propagation models used to
calculate proposed area coverage objectives.
Comply
HydraSM is an innovative software tool developed by Motorola to accurately predict
coverage, model traffic (voice and data), analyze interference, plan channel re-use,
and perform other design tasks for Motorola’s diverse portfolio of radio networks.
This description concentrates on Hydra’s coverage planning aspects.
Motorola has presented in this proposal, some typical Hydra coverage analysis for
Floyd County, GA (“County”).
Inputs to Hydra’s simulations include system architecture, equipment characteristics,
service area boundaries, areas of various building losses, subscriber unit distribution
density for Traffic analysis, etc.
Hydra’s coverage map outputs are created and displayed using ESRI’s shapefiles, an
industry-standard GIS file format. Shapefiles from many sources (GIS vendors, the
Internet, your own GIS department, etc.) can be loaded, displayed, and used in Hydra
to enhance mapping, and to define service area polygons. Hydra’s coverage analyses
can be limited to specified service area polygons (e.g., a county, a city, or a dispatch
territory), so coverage reliability can be analyzed exclusively within the boundaries of
your operating area.
Coverage maps and other pertinent calculations must be submitted with the following minimum
information clearly defined for each map or submittal:
A. Transmitter site power output

Comply


This is indicated in the RF Site Table in Section 7.01
B. Antenna gain and type (Include transmission line losses)
Comply
C. Effective signal level necessary, at both infrastructure and user radio antenna ports,
to produce DAQ 4.0 and 3.4 delivered audio quality in the typical land mobile radio
environment
Comply
DAQ 3.4 Effective
DAQ 4.0 DAQ 3.4 Effective Radiated
Sensitivity Sensitivity Sensitivity Power
-109.44
GTR 8000 dBm -112.9 dBm N/A N/A
APX / XTL -105.07 -108.53
Mobile dBm dBm N/A N/A
APX / XTS -108.53 -100.83
Portable N/A dBm dBm 26.3 dBm
C. Antenna height
Comply
D. Portable unit effective radiated power

Comply
Reference the table inserted above.


E. Portable unit effective receiver sensitivity
Comply
Reference the table inserted above.
F. Transmitter site talk out range, individual site as well as composite coverage
Comply
G. Portable unit talk-in range, individual receiver sites as well as composite coverage
Comply
I. Signal level contours for on-street, in-residence and in-building portable coverage as
well as 95% mobile/portable on-street coverage. In-building coverage maps shall depict
6db, 15db, 20db and 25db loss profiles.
Question:
Comply
Please see Section 8 for all coverage maps.
In addition to the coverage objectives defined herein, the proposed network must be in
compliance with the appropriate: 700/800MHz Public Safety Radio Communication Plan,
GEMA Region 6.
Comply

7.5 Coverage Acceptance Criteria

Verification of the installed system's coverage is a component part of the Test and Acceptance
criteria described in Section 14.0, Phasing and Implementation.
Understood
In order to avoid subjective interpretation of coverage test results to the maximum extent
possible, mobile coverage testing (performed within a road vehicle during terrestrial coverage
testing or water craft when performing river coverage testing) shall be done with computer-
controlled test equipment. This equipment shall automatically record the position of the test
vehicle (by means of GPS positioning) at the time of a reading, and records the signal


strength of at least 200 signal samples over a 40-wavelength period for each reading taken
within a test grid. Signal strength measurements shall be made continuously along the drive route.
Comply
Test grid sizes within the City of Rome's densely-constructed central business district, and
governmental areas shall be no greater than 400ft x 400ft. Grids throughout the other areas of the
City shall utilize grid sizes no greater than 2,000ft x 2,000ft. Grids sizes outside the City’s
boundaries shall be no greater than 4,000 ft x 4,000 ft. A minimum of 1,000 accessible grids shall
be tested. Floyd County or designee and the Contractor shall mutually determine the
size/location of grids and a suitable drive route that encompasses the entirety of accessible grids.
Question:
7. Can you please provide a contact with the County GIS department, who could provide data
files pertaining to the city/county boundaries and road/streets information?
Response: The County will provide a set of County boundary files. Road and street information is
commercially available from multiple sources.
Comply
Field strength test results obtained throughout the coverage area, in accordance with minimally
required reliability percentages, shall be of sufficient level to produce a Delivered Audio Quality
(DAQ) rating of 3.4 (4.0 for mobile radio units) or higher throughout the predicted service
area to be considered passing. Mobile radio signal strength measurements shall be made from
either a terrestrial (land) vehicle moving at approximately 35 mph, or a water craft (river) vehicle
traveling at approximately 20-knots.
Question:
8. Please revise the DAQ voice quality descriptions to agree with Voice Quality definitions from
TSB 88.
Response: DAQ voice quality requirements will remain.
Comply
The device used to measure field intensity shall be stable and have a dynamic range suitable for
the conditions under test. Prior to the execution of these test activities, all test equipment and data
gathering equipment to be used shall be fully certified by an independent testing laboratory
having calibration tools traceable to the National Bureau of Standards. These certification
documents shall be presented to Floyd County's technical staff, or their consultant and/or
technical representative, prior to coverage testing for verification.
Comply
Motorola will perform the test radio calibration procedure in the presence of an
independent testing lab or facility using their calibrated signal generator.


The test output shall be fed into a laptop computer or an equivalent computer device. The
Contractor shall submit a written and/or graphical report containing an analysis of the test
results to the Floyd County or designee and Consultant daily, and a formal report at the
conclusion of the test. The results shall be depicted for mobile, portable in-residence and
portable in-building coverage. The analysis shall include maps of the coverage area divided into
grids, with the test results for drive tests displayed in each grid on a separate map. All test data,
in its raw form, shall also be made available to the Consultant for independent inspection.
Comply
Floyd County or its designee reserves the right to disapprove any instrumentation or
procedures. During these tests, the network’s simulcast transmitter(s) output power shall be
monitored by the County or its consultant/technical representative and no adjustments shall be
made to the transmitter(s), portable/mobile radio units or test instrumentation after appropriate
calibration of all involved equipment.
Comply
For portable radio voice quality testing, at least 800 grids shall be functionally tested within
the defined coverage area. Floyd County’s Project Representative, Consultant and Contractor
will jointly determine those grid areas to be tested.
Comply
The portable radio voice quality testing shall be performed using a minimum of ten phonetically
balanced phrases, to be supplied by the Contractor. A successful test measurement shall be one
which requires no repetition to understand the spoken phrase and with a DAQ of 3.4 (4.0 for
mobile radio units). A successfully tested grid is defined as one whereby communications from
a dispatch console to a portable radio unit, as well as for the reverse path, are not less than
DAQ 3.4 as described below.
Question:
In Section 7.2 (Page #65) coverage is defined using reference to the Voice Quality definitions as
described in TSB-88B yet the definitions illustrated contradict those as defined in TSB-88B. For
example, the TSB88.1-C definition for DAQ3.4 is “Speech understandable with repetition only
rarely needed. Some Noise/Distortion” whereas the RFP definition for the same DAQ 3.4 is
“Reception is clear, but with slight background noise. Message is readable and understood with
few / occasional missing syllables.” The difference is that there is no provision for repetition.
Please provide some way of resolving this discrepancy, particularly when it comes to repetitions,
which are allowed by the TSB-88 definitions, but not by the RFP.
Response: The County will modify the definition of DAQ 3.4 to the following: “Reception is
clear, but with slight background noise. Message is readable and understood with few/occasional
missing syllables and with repetition only rarely needed.”
Comply


DAQ DESCRIPTION
5 Reception is very clear and message is perfectly readable. No background noise
is present and every word is understood.
4 Reception is clear, but with slight background noise. Message is readable and
every word is understood.
3.4 Reception is clear, but with slight background noise. Message is readable and
understood with few/occasional missing syllables.
3 Background noise is evident. Message is readable and understood even with

missing syllables.
2 Background noise is prevalent. Message is readable with difficulty and requires
repetition.
1 Evidence that transmission being made. Voice message is barely discernible
and no words are understood. Unusable.
Comply
Per this RFP “Using the Delivered Audio Quality representations described
EIA/TIA TSB-88B; the delivered audio quality throughout the service area shall
be no less than DAQ 4.0 for mobile operations and DAQ 3.4 for portable
operations.
Ninety-seven Ninety-five percent of grids must meet exceed these defined requirements for the
system to be considered coverage compliant.
Question:
19. Please clarify that all coverage requirements are 95% of grids, not “Ninety-seven percent
of grids must meet exceed these defined requirements for the system to be considered coverage
complaint.”
Response: Should read “Ninety-five percent of grids must meet exceed these defined
requirements for the system to be considered coverage compliant.”
Comply
Motorola has provided 95% coverage throughout Floyd County for DAQ4.0
Mobile, DAQ3.4 Portable Outdoors, and SSI Portable in Residence.
Audio quality testing within those representative buildings listed in Section 7.3 must be
conducted manually, using the voiced procedure described above. Portable audio quality
testing for building structures shall be considered successfully completed if of the number of
tested areas meeting the previously indicated DAQ audio requirements equals or exceeds
95% of the total number of tested areas. That is, if a hypothetical 100 areas are tested within a


given building, then 95 of those tested areas must exhibit audio quality of DAQ 3.4 or
greater to be considered acceptable.
Comply
Floyd County shall designate the test team to participate in coverage testing. The team shall
include, at a minimum in each team, a Consultant representative, a Floyd staff person, two
Public Safety representatives and a Contractor representative. All test vehicles shall be
provided by the Contractor and be off-road capable. Testing shall commence daily at 9 AM and
will cease at 5 PM. At least three teams will conduct the tests in the interest of timely
completion. Each test team shall have a suitably equipped Marked Public Safety vehicle as an
escort for the entirety of all hours of testing. Failure of Contractor test equipment shall not be
considered as an acceptable reason for a Contract time extension. Floyd County will not pay for
retesting caused by delays or equipment failures. Testing will proceed through weekends until
concluded.
Comply
Final System Acceptance shall not be achieved until the constructed radio network successfully
concludes performance test requirements the as-built radio network equals or exceeds the
coverage performance guaranteed by the Successful Proposal or as otherwise amended by the
Contract. Testing will only be scheduled in period of peak seasonal vegetation/foliage periods,
i.e., June through August. Therefore, it is critical to the acceptance testing phase that Installation
and Implementation is conducted on a schedule that facilitates coverage and performance testing
during these specified months.
Comply
8.0 Dispatcher Console Requirements
Question:
20. Is it required that the console systems at the E911 Center and the EOC/Back-up E911 Center
share common electronics and/or the same console manufacturer and model?
Response: Yes.

Question:
8. During the pre-bid conference, we requested more details on the typical user response situations
in areas on the edge of the county. Please provide anticipated number of users and user groups
that would typically operate in the following three scenarios:
a. During normal operation
b. A typical accident/fire situation
c. Any emergency disaster scenario response
Areas of particular interest are:
a. The pocket (around Scout Camp)


b. Halls Valley
c. Texas Valley
d. GA-1/US-27 at the Chattooga County border
e. The valley of Lake Marvin and Everett Springs Roads
Response: The County does not have experience with trunking systems in order to make an
adequate response to this question. Vendors are more experienced in this area and should put
forth a best effort determination of the needed requirements to meet the scenarios described above.
Understood

8.1 General

It is a functional requirement that the existing VHF/UHF conventional analog systems
remain operational during the installation and acceptance phases of the new Project-25
Digital voice radio network. Any proposal that would cause the temporary interruption of the
VHF/UHF analog conventional systems for any duration must be reviewed and approved, in
advance, by Floyd County or their designee. The County currently uses the Positron Front Line
Viper CAD (version 1.5.0.15) dispatch console. They are satisfied with its reliability and
performance, and will be the benchmark upon which any replacement console is judged.
Question:
21. The IPC Console with T5 operating system was cancelled in April 2009, and that equipment
for expansion of existing systems would be available through January 29, 2010. The serviceable
life for this console ends April 30, 2014. Will this change the County’s desire to maintain their
existing dispatch console?
Response: No change to the RFP requirements is granted, however, Motorola is free to offer
alternative solutions.
Understood
It is the desire of the County to keep their existing dispatch console and have seamless
integration with the newly proposed P-25 800MHz radio network. For those proposals that
incorporate the replacement of the existing dispatch console with a proprietary console
solution, careful consideration must be given to the cost benefits of replacement, functionality of
newly proposed dispatch console when compared to the existing console, future warranty costs
and vendor support. Proposals that do not provide a pathway for integration of the existing
console solution shall provide a cost and functional comparison of the existing console solution
with the newly proposed dispatch console solution. Such cost and functional comparison shall
provide adequate justification to the County for replacement. Additionally, any newly proposed
console shall be seamlessly compatible with the County's existing audio logging recorder, a 16
channel Verint model purchased two years ago and capable of being upgraded to a maximum of
48 channels.
Question:


22. How many channels on the Verint 16 channel logger are currently in use for radio logging? Is
the Verint 16 channel logger recording any telephone or 9-1- 1 audio? If yes, how many channels
are used? How many of the 16 channels are not used currently?
Response: The County's existing Verint model audio logging recorder can actually hold 48
channels. Currently it is configured to use 17 channels. It is currently recording the telephone and
9-1-1 audio.
Comply
The IPC Console with T5 operation system was cancelled in April 2009, and equipment for
expansion of existing systems is only available through January 29, 2010. The service life for
this console ends April 30, 2014. Per Addendum 1 of the RFP Motorola is providing an
alternate console solution which maximizes the Trunking features and provides
unprecedented dispatch control and extends the service life.
Please reference the Positron cancellation memo dated Feb 2, 2009 in Appendix B.
Motorola has included the Genesis GenWatch3 Trunking Interface system to integrate the
proposed P25 system to the existing Verint logger.
Installation of new radio dispatcher equipment must, likewise, be completed in a manner that
causes no interference with the operation of the existing VHF/UHF analog conventional systems.
Therefore existing dispatch facilities for Police, Fire, and EMS operations must be evaluated by
Proposers to determine the most effective means to install and implement their proposed new
dispatch console equipment and associated subsystems.
Comply
Note: All consoles, wherever located shall be properly and adequately grounded and surge
protected to industry standards for operator safety.
Comply
8.2 Radio Console Locations

8.2.1 Floyd County E911 Center
The Floyd County Police, Fire, and EMS Department dispatching facilities are located at the
Floyd County E911 Center, in Rome. The mailing address of the 911 center is:
Understood
Floyd County-E911 Center
5 Government Plaza
Rome, GA 30162-0946
Understood
The main Public Safety Answering Point (PSAP) is a single room, separated into functional
dispatch positions (pods) by cubical dividers, is provided for County and City Police, National
Crime Information Center (NCIC), Fire, and EMS operations. A total of six radio dispatcher
shall be provided. There are a total of three spare dispatch pods available to the E911 center for
use in an emergency. The new radio dispatch and fallback control station equipment must be
housed within the Center’s existing console furniture.


Comply
Motorola has included one (1) supervisor/radio dispatch console and five (5) radio dispatch
consoles (total of six) at the Floyd E911 center.
Each dispatcher position shall be equipped to selectively monitor and control any combination of
talk groups, NPSPAC mutual aid and interoperability radio channels. Additionally, dispatch
consoles must have the capability of establishing and/or disabling dispatcher-controlled
RF/audio interoperability service links as described in Section 3.2.6.
Comply
The display equipment at each dispatcher position must be of a compact, solid-state liquid-
crystal design (Flat Panel 19-inch, minimum, screen) and capable of presenting a real-time
alphanumeric display of pre-configured talk groups; call status and per-call user identification.
Comply
Each supervisory dispatch console position shall have the capability to monitor and control pre-
configured talk groups, NPSPAC mutual aid channels, and dispatcher-controlled interoperability
links. In addition, this console position shall be equipped to perform, at a minimum, the
following system management tasks:
Question:
23. How many supervisory dispatch console positions will be required at the primary 911 center?
How many at the Back-up EOC? A total of 2 (two) are needed, 1 (one) at the E911 Center and 1
(one) at the EOC/Back-up E911 Center. Will any additional supervisor positions be required in
other physical locations?
Response: No.
Comply
A. Emergency unit identification in real time.

Comply
Dispatch Application - available on all consoles
B. Retrieval of system activity i.e. the types of calls, call duration, when made, user
identification, etc.
Comply
Activity Log - available on all consoles
C. Retrieval of special feature activity, i.e. interconnect usage, encrypted voice

transmissions, etc.
Comply
Historical Reports – available on supervisor console


D. Ability to remotely disable and re-enable selected field units.
Comply
Radio Control Manager – available on supervisor console
E. Ability to regroup individual radios into special talk groups.
Comply
Dynamic regroup – available on all consoles
User Configuration Manager – available on supervisor console
F. Assignment of user priority levels.
Comply
User Configuration Manager – available on supervisor console
G. Ability to monitor summed major site/network alarm status.

Comply
Unified Event Manager – available on supervisor console
The supervisory console position shall be equipped with solid-state liquid crystal flat screen
monitor(s) to display real-time transactions at each dispatcher position and the system
management information described above. Additionally, printer equipment shall be provided to
prepare hard copy reports of accumulated system records.
Comply
8.2.2 EOC/Back-up E911 Center
The proposed Floyd EOC/Back-up E911 Center, will be located at 417 E 12th Street, Rome, GA
(+34˚14' 18" -85˚ 09' 53"). A schematic (preliminary) design is found in Attachment B for the
EOC/Back-up E911 Center. There is an enabling project (Fire Station #3) that will have to be
constructed prior to beginning construction on the EOC/Back-up 911 center. The new
EOC/Back-up 911 center should be fully integrated with the proposed 800MHz radio system.
The EOC/Back-up 911 center requires the capability to access, maintain and monitor the 800MHz
radio system from this location.
Question:
24. The spec references the addition of 3 radio operator positions including CAD to be located at
the back-up center. Is it correct to assume that 9-1-1 is not part of this response?
Response: No, a total of 9 (nine) radio operator console positions are needed, 5 (five) at the E911
Center and 4 (four) at the EOC/Back-up E911 Center in addition to the supervisory dispatch
console positions.


Comply
There will be a total of three (3) console/dispatch positions and there (3) CAD positions. This
center will require connectivity to the existing network infrastructure via the microwave network.
A total of three RF control stations should be at this location.
Comply
Per Addendum 1, Motorola is providing one (1) supervisor/radio dispatch console and four
(4) radio dispatch consoles (total of five) at the Back-up EOC.
Motorola will manage the implementation of the CAD equipment at no additional cost as part
of this project. Cost of the CAD equipment is provided; however Motorola recommends that
the County purchase the CAD equipment directly from the vendor.
The EOC/Backup 911 center will be connected to the radio core via a Hot Stand-by
microwave link. Since final plans for this site were not available, Motorola has assumed that
a microwave dish antenna can be located on the roof or a county provided tower at a
centerline of 85 feet. Motorola has provided optional tower pricing for the county’s
convenience.
8.3 Desired Functionality

8.3.1 Dispatch Console Reliability
Due to the critical nature of the communications services provided by these multiple public
safety dispatch facilities, a high degree of reliability for the new radio dispatch console
subsystem is required. The console subsystem, to the greatest extent possible, shall:
1. Be automatically self-correcting.
Comply
2. Provide continuous and automatic self-testing and diagnosis.
Comply
3. Alert the operator in the event of component or sub-system failure.
Comply
4. Allow continued operation of the remaining consoles in the event of failure to a
specific console, through isolation of the defective console device.
Comply
5. Be of a design that eliminates single points of failure.
Comply
6. Interconnectivity between consoles and dispatch locations shall utilize to the greatest
extent possible packet-based, in lieu of traditional circuit-switched, technologies


Comply
A high degree of modularity is likewise envisioned to reduce the number of sub-systems
affected by a single component failure. Repair of sub-systems without totally disabling
multiple radio console positions shall be required, as continued console operation is necessary
during repair.
Comply
8.3.2 Diagnostics
The new dispatch console subsystem shall be equipped with a number of self diagnostic
elements that continuously monitor and verify the correct operation of each distributed
microprocessor, each audio path in the console electronics and between the console electronics
and the new radio network, itself.
Comply
Diagnostic capability shall be distributed among independent and redundant subsystems and shall
not rely on one central diagnostic circuit.
Comply
Motorola is providing three divers monitoring systems:
♦ MOSCAD NFM
♦ Unified Event Manager
♦ Microwave Monitoring
8.3.3 Power Supply
It is a critical requirement that power loss or surges shall not affect radio dispatch operations.
Power loss or surges shall not alter the system software or operating parameters at the radio
dispatch positions. External power to each console shall be supplied by a nominal 120VAC,
60Hz, single-phase power source. An uninterruptible power supply, capable of supporting
consoles, fallback radios and related equipment for a minimum 45-minute period shall be
provided at each dispatch center facility. All dispatch console equipment, in whatever facility,
shall be connected to an outlet on a circuit that is supported by the building primary emergency
power generator, if so equipped. It is not the responsibility of the Proposer to supply either the
emergency generator or the designated circuits.
Comply
8.3.4 Flat Panel Display
A state-of-the-art color, non-interlacing, 19-inch minimum Flat Panel (solid-state) display shall
be provided. Each operator shall have the ability to change screen displays to suit operator
preferences. No less than eight console preferences shall be configurable for each console.
Comply


8.3.5 Headset Jack Configuration
All radio consoles shall be configured for headset and local-microphone operations. Each
console shall provide independent transmit audio level settings for audio inputs from the
headset microphone and a desktop microphone, such that dispatchers may freely switch
operation without affecting dispatch audio quality. Dual headset jacks shall be provided at each
position for training and supervisory purposes.
Comply
8.3.6 Footswitch
Each of the radio consoles shall include a footswitch for PTT operation of the selected
channel(s). The footswitch shall be heavy duty, rated for constant and continuous use, and shall
be designed so as not to skid on a smooth flooring surface. The Contractor shall supply and install
a switch for each console.
Comply
8.3.7 Master Time Source
A time generator system shall be provided, by the Contractor that references the Global
Positioning System to synchronize all dispatch, CAD and audio recorder clocks at all radio
console positions/centers. This time generator system shall be made to fully interface to and
control the event-time display of the radio consoles, console audio recorder, radio network
management tools, radio network alarm system, microwave alarm system and CAD systems at
each radio dispatch location. This time generator shall have an adequately sized UPS,
connected into an emergency powered circuit outlet.
Comply
8.3.8 Dispatch Console Positions
Each of the radio dispatch consoles shall include all controls that apply to the various
channel/talk groups and auxiliary functions for the console. Each console position shall
contain as a minimum:
• Select Speaker – for audio from selected channels/talk groups, with volume control.
• Unselect speaker – for audio from unselected channels/talk groups, with volume
control.
o Transmit Function – a color-coded transmit function to control
the push to talk (PTT) function for the selected transmitter(s)
and/or talk group(s).
• CTCSS Monitor or Disable Function – shall disable the receiver CTCSS decoder of
selected conventional base station(s) for monitoring purposes.
• Clock – shall display time in twenty four-hour format.
• VU Meter or Audio Level Display.
• Keypad or screen representation of a keypad for numeric data entry.
• Microphone – desktop microphone type. This microphone shall be resistant to
interference, such as transmitting hum for lights, cathode ray tube terminals, or other


devices used in the proximity of the console.
• Dual Headset Jack – a dual headset jack shall be provided which will allow for use of
a headset equipped with RJ-327 type plug with modular adapter. Separate headset
volume controls for radio and telephone audio output shall be provided.
• Intercom – intercom between operator positions shall be provided. A visual display
shall be provided to identify both the calling and called parties by console name.
Multiple simultaneous intercom conversations between individual consoles shall be
possible.
• Private Call – Selected users and dispatchers shall have the ability to selectively
communicate “privately” with another individual on the system regardless of what
talk group either unit is in. The call shall allow the two users to utilize a single
channel resource to communicate without the participation of other units in their
respective talk group.
• ID Display on the channel window for standard calls and emergency calls.
• All Receiver Mute Function – a function, which will mute the received
audio from all unselected channels, shall be provided. This muting function
shall be programmable in predetermined increments.
• Simultaneous Select and Instant Transmit Function – controls shall be provided
that allows the operator to manually select any combination of console controlled
base stations for simultaneous transmissions. Three selectable combinations shall be
allowed at the discretion of the dispatcher. The patch shall utilize a single trunked
channel when patching more than one talk group.
• Emergency/Reset – consoles shall receive emergency alerts from the trunked radio
system regardless of the status of the channel control window. Emergency messages
shall be indicated by a flashing ID, and emergency ID character and an audible alert.
Dispatcher acknowledgment of the message shall silence the audible alert and stop
the flashing display. Multiple emergency messages shall be queued in the display
tack and the emergency ID character shall continue to flash until all messages have
been viewed and subsequently cleared by the dispatcher.
• Alert Tones – the console shall be provided with three distinct tones used for
alerting purposes over the air. Each alert tone shall be immediately broadcast, when
activated, on the selected radio channel. The following selections shall be available as
a minimum:
o Alert 1 – Steady Alert Tone – shall generate a nominal 1000 Hz steady tone.
o Alert 2 – Warbling Tone – shall generate a warbling tone.
o Alert 3 – Pulsed Alert Tone – shall initiate an automatic sequence, consisting of
a nominal 1000 Hz tone, for a period of two (2) seconds.
• Paging Encoders – Each console shall include a multi-tone paging/signaling encoder
that is accessible, minimally, through the data entry keyboard.
• Call Indication – a color-coded status call indicator shall be provided for each
receiver in a channel control window on the display screen.
• Individual Volume Adjust – shall be provided for each channel on the console.
Associated color-coded status indicators shall continuously show whether the channel
is in the full or adjustable volume control shall be automatically bypassed when a
channel is placed in select status.


•
Talk group/Channel Cross Patch
•
Channel/Group Name – designated channel/group control modules shall include a
minimum of eight character alphanumeric display symbols to identify the
channel/group.
• Talk Group/Channel Busy Indication
Comply
8.3.9 Video Display Installation
The installation of the Video Display(s) used for the radio dispatch positions shall be desk
mounted on furniture provided by Floyd. Contractor-furnished cabling shall be installed in a neat
manner, which is approved by Floyd and protected from physical damage. Cable raceways shall
be used where possible. No cabling shall create a safety or mobility problem for dispatch
personnel
Comply
8.4 Console Electronics

8.4.1 Description
Console electronic circuitry shall be housed in an equipment cabinet/enclosure specific for each
dispatch console position. When installed by the Contractor, sufficient space for front and rear
servicing of this equipment shall be provided. The use of a centralized console electronic bank
that supports audio and control signaling between multiple dispatch console positions is
discouraged.
Comply
Console electronic enclosures shall contain the various microprocessors, console interfaces,
auxiliary function interfaces and other interfaces needed for system operation. If multiple circuit
cards are required in the Proposer’s solution, these shall be of plug-in design and shall be able to
be inserted and/or removed with power applied and the location’s dispatch
positions/equipment remaining on-line.
Comply
8.4.2 System Interfaces
The digital voice network’s radio dispatch subsystem shall include that circuitry required to
operate remotely-controlled base stations and the trunked simulcast repeaters as described by this
Specification and in the Proposer’s Submittal. At a minimum, each base station interface shall
consist of a plug-in circuit card (or the software equivalent) containing VoIP- related circuitry,
line driver amplifiers, two-wire and four-wire receive amplifiers, digital automatic level
adjustment circuitry and fault-diagnostic circuitry. The interface shall be capable of remotely
controlling base stations via E/M multiplex-channel and 2175Hz tone- burst signaling.
Comply


8.4.3 Auto Diagnostics/Self Healing and Diagnostic Features
The radio dispatch subsystem shall be equipped with a number of self diagnostic capabilities that
shall be configured to continuously monitor and verify the correct operation of each distributed
microprocessor, each audio path in the console electronics and between the electronics and
each radio network base station site. In the case of voice transactions using the Internet Protocol,
specialized coding shall be used to assure the timely delivery of audio packets to destinations
such that recovered or transmitted audio is absent of noticeable voice delays or audio truncation.
Comply
8.4.4 Console Auxiliary I/O Functions
Unless otherwise specified within this document, all external auxiliary input and/or output
(logic or relay) functions shall be controlled through an auxiliary interface module. These
functions shall be controlled from the console position as required.
Comply
8.5 Fallback Control Stations

Each dispatch and supervisory position shall be equipped with a 800MHz trunked control
station to permit radio dispatch operations to continue in the event of radio console equipment or
connectivity failures. These control stations, in addition to the minimum requirements
specified by Section 5.3, must contain an alphanumeric display to provide information on talk
group selection and emergency call alerts.
Comply
9.0 Special System Requirements

9.1 Generator Equipment Requirements
Standby power generator systems shall be furnished by the Contractor for each newly proposed P-
25 800MHz simulcast infrastructure and prime site/control point site. If a proposer plans to
reuse any existing (in place) standby power generation equipment at any site, the Proposer shall
insure that the loading capacity and functionality of existing equipment will meet and/or exceed
the power and run time requirements of any newly proposed standby power generation
equipment as outlined below.
Comply
For all newly proposed infrastructure sites, the Proposer shall include the necessary labor and
materials, as required, to furnish and install LPG fuel tanks, diesel fuel tanks, gas line
attachments (where natural gas service is available), automatic transfer switches, manual-
operated auxiliary generator connector facilities, generator/fuel tank foundations/platforms,
alarm functionality and electrical wiring services to provide fully operational standby power
systems. Generators shall be housed within outdoor equipment enclosures in accordance with
the manufacturer’s specifications for shock and vibration mounting, ventilation, fuel supply and
electrical connections.


Question:
25. When and how will the specific fuel source be determined?
Response: It is the responsibility of the Proposer to make that determination as defined by the
RFP.
Comply
9.1.1 General Requirements
It shall be the responsibility of the Contractor to provide, install and test a complete and
operable standby power generator with automatic transfer switch. Equipment shall be new,
factory tested @ 0.8 power factor for 3-hours, and shall be installed adjacent to the required radio
equipment shelters, in accordance with local area building and electrical codes.
Comply
9.1.1.1 Documentation
The following documentation shall be supplied by the Contractor for the generator set and
transfer switch supplied:
• Specification and data sheets for the exact type and model generator and transfer
switch supplied pursuant to this procurement, including all options and accessories
included.
• Manufacturer's certification of prototype testing.
• Manufacturer's warranty documents.
• Shop drawings showing plan and elevation views of the equipment.
• Interconnection wiring diagrams showing all external connections required; with
field wiring terminals marked in a consistent point-to-point manner.
• Manufacturer's installation instructions.
• Operator's and maintenance manuals that outline routine maintenance and
troubleshooting procedures.
• Transfer switch manual and wiring diagram.
Comply
9.1.1.2 Start-Up Service
A factory authorized service representative shall provide initial start-up service and shall
conduct on site acceptance testing. Load test records for the installed generator system shall be
furnished to Floyd.
Comply
9.1.1.3 Type of Generator
Each generator package shall include a dual-fuel (natural/LP Gas fueled) four-cycle, or diesel


(2 or 4-cycle) with tank underneath the generator, engine-driven set coupled with low reactance,
brushless 120/240vac single-phase generator. Each generator package shall be equipped with a
temperature compensated automatic voltage regulator; under/over-speed protection function; a
control panel; and high ambient-temperature cooling system.
Comply
9.1.1.4 Ratings
Output power rating of each generator shall be sized for the full calculated load for the
affiliated site, inclusive of a 50% excess load factor. In no instance, however, shall any
generator set be configured for less than 45KW output. Each generator shall be capable of
continuous 24-hour operation, full single phase output @ 1.0 pf. The following specifications shall
also apply:
• Voltage Regulation: Maintained with +/- 2% of rated voltage for constant load
between no load and full load.
• Frequency Regulation: Maintained within 0.5% from steady state no load to steady
state rated load.
• Single-Step Load Pickup: 100% of rated output power, less applicable derating factors,
with the engine generator at operating temperature.
9.1.1.5 Generator Set Control
Each generator shall be a remote-start type compatible with the automatic transfer switch to be
supplied pursuant to this procurement. Manual starting and stopping shall be provided from the
control panel.
Comply
Cranking control: Shall provide a minimum of three cranking cycles of at least 15-seconds
before lockout and activation of an over-crank alarm condition.
Comply
Each generator shall automatically shut down and lock out upon:
Failure to start (over-crank) Over speed
Low lubricating oil pressure
High engine temperature
Other factors that may be harmful to the generator
Comply
Alarm contacts shall be provided to allow transmission of fault alarms for any of the above
conditions, plus low oil pressure pre-warning, high coolant temperature pre-warning, low
coolant temperature, low fuel and an alarm indication when the generator set is running. These
alarm contacts shall be wired into and shall be reported by the radio network alarm system
being supplied pursuant to this procurement.
Comply
Meters shall be provided, and located both at the generator and within the equipment shelter, to


indicate output voltage, output current, running time, and frequency/RPM. An AC rheostat
shall be supplied for fine tuning of the generator’s output voltage. These devices shall be mounted
either on the transfer switch door or a separate, remote panel.
Comply
9.1.1.6 Fuel Supply
The Contractor shall supply a new, fully painted, LP gas storage tank to be installed and
secured to a concrete pad at a location near the equipment shelter and which is accessible for
refueling. In some instances, depending upon local conditions, Contractor shall be required to
elevate the fuel tank as necessary (depending upon Contractor’s flood determination, to a height
equal to the equipment shelter. The fuel tank shall provide sufficient fuel to provide six days of
continuous operation of the generator set, at full load under low ambient temperature 20-degrees
Fahrenheit). The tank shall be refilled after the conclusion of radio network acceptance tests.
Fuel lines shall be buried below the frost line. At any point at which the fuel line exits above
grade, the line shall be insulated to reduce condensation at the regulator. A low fuel level alarm
shall be provided.
Comply
All regulators and fuel supply lines will be sized accordingly for the generator running at full load.
All necessary regulators, drip pots, piping, meters, or other supplies needed for an installation
which meets local fire and building codes shall be furnished and installed.
Comply
Contractor shall supply a full fuel tank at time of System Acceptance.
Comply
9.1.1.7 Exhaust System
A residential-grade exhaust silencer shall be installed on the generator.

Comply
9.1.1.8 Battery and Charger
A lead acid starting battery, rated for the engine type to be supplied, shall be furnished and
installed with each generator package. This battery shall be float charged by a 10-ampere,
voltage-regulated charger which is powered by a protected 120VAC source. Float, taper and
equalize charge settings shall be provided. Battery charger shall be physically located within the
generator transfer switch enclosure.
Comply
Form-C charging system alarm contacts shall be provided and connected to the radio network’s
alarm system to report loss of AC power, low battery voltage and excessively-high battery
charging current.
Comply


9.1.1.9 Cooling System
A radiator-cooled engine is required. The radiator shall be filled with a water/coolant

mixture in accordance with the engine manufacturer's recommendations.
A thermostatically-controlled water jacket coolant heater shall be provided and installed in
accordance with the manufacturer's recommendations.
Comply
9.1.1.10 Base
The generator set shall be mounted on a heavy duty steel base which is, in turn, anchored to a
Contractor-furnished generator foundation. The base shall maintain alignment between
generator set components and shall include vibration isolators.
Comply

9.2 Transfer Switch Requirements

An automatic transfer switch which provides switching of the equipment shelter electrical load
between commercial power and generator power shall be supplied and installed for each
installed standby generator. Each transfer switch shall be completely factory assembled and shall
contain electronic controls designed for surge voltage isolation, with voltage sensors on all phases
of both input power sources. Permanently attached manual handles shall also be installed on
the transfer switch. The switch shall provide positive mechanical and electrical interlocking and
mechanically-held contacts. Quick-make and quick-break contact mechanisms shall be provided
for manual transfer under load.
Comply
Each transfer switch shall be installed in a key locking, UL listed, NEMA cabinet to be
mounted on a wall within the radio equipment shelter. The switch shall be fully wired and
integrated with the engine generator set in accordance with local electrical and fire codes.
A manually-operated transfer switch, as well as appropriate power connectorization, shall be
provided to allow the interconnection of an auxiliary, trailered generator set should the
permanently-located generator fail in operation.
Comply
All transfer switches and accessories shall be U.L. listed and labeled, tested per U.L. Standard
1008 and CSA Approved.
Comply
9.2.1 General Specifications
Transfer switches shall be double-throw electrically and mechanically interlocked and

mechanically held in both positions.
Comply
Main switch contacts shall be high-pressure silver alloy. Contact assemblies shall have arc
chutes for positive arc extinguishment. Arc chutes shall have insulating covers to prevent inter
phase flashover.


Comply
Form-C contacts shall be provided in each main switch position for alarm reporting purposes.
These contacts shall be connected to the radio network’s alarm system for reporting transfer status.
Comply
Each transfer switch shall be continuously rated for operation in ambient temperature ranges of -
40 to +50 degrees Celsius. Transfer switches shall be rated, minimally, to carry the generator’s
full rated output, inclusive of the 50% added capacity over calculated equipment loading.
Comply
The Line-In; Generator-In and Load site termination for the automatic transfer switch shall be
protected from lightning transients using a combination of MOV and varistor technologies. All
alarm and instrumentation wiring from the generator, that enters the equipment shelter, must
likewise include appropriate lightning surge protection in the form of solid-state, fast-acting
voltage clamp devices whose clamping voltage is closely matched to normal individual-alarm
signal amplitudes.
Comply
9.2.2 Automatic Control
Transfer switch control shall be solid state and designed for a high level of immunity to
power line surges and transients. The device shall be tested in accordance with IEEE
Standard 587-1980 (or latest revision). Controls shall have optically isolated logic inputs, and
isolation transformers for AC inputs. Relays shall be installed on all outputs.
Comply
Solid state under voltage sensors shall simultaneously monitor all phases of the standby
power source and the commercial power source. Pick up and drop out voltage settings shall be
adjustable. Voltage sensors shall allow for adjustment to sense partial loss of voltage on any
phase.
Comply
Controls shall be provided with solid state over voltage sensors, adjustable from 100-130% of
nominal input voltage to monitor the source. An adjustable time delay shall be provided.
Comply
Automatic controls shall signal the engine-generator to start upon signal from normal source
sensors. A time delay start, variable from 0 to 5 seconds, shall be provided to avoid nuisance start
ups. Battery voltage starting contacts shall be gold, dry type contacts which have been factory
wired to a field wiring terminal block.
Comply
The switch shall transfer when the emergency source reaches the set point voltage and
frequency. A time delay shall be provided for transfer that shall be continuously variable from 0
to 120 seconds.
Comply


The switch shall retransfer the load to commercial power after a time delay. This time delay shall
be variable (adjustable) from 0 to 30 minutes to avoid short engine run times. The retransfer
time delay shall be immediately bypassed if the emergency generator fails.
Comply
A control shall automatically signal the engine generator to stop after a time delay, which shall
be adjustable from zero to ten minutes, the time starting upon return to commercial power.
Comply
Power for transfer operation shall be from the source to which the load is being transferred.
Diagnostic indicators shall be provided to allow the last successful step in the sequence of
control functions to be pinpointed. The present status of the control functions shall also be
indicated. These functions, at a minimum, shall include:

Source 1 OK
Start generator set
Source 2 OK
Transfer timing
Transfer complete
Retransfer timing
Retransfer complete
Timing for stop
Comply
9.2.3 Front Panel Control Devices
A key-operated selector switch shall be provided which will provide the following functions:
• Test - to simulate commercial power loss to allow testing of the generator set with
or without transfer of the load.
• Normal - leaves the transfer switch in its normal operating position.
• Retransfer - a momentary position which will provide an override of the
retransfer time delay and cause immediate return to the commercial power source (if
available).
Comply
9.2.4 Exerciser Clock
Each transfer switch shall be equipped with an exerciser clock which allows setting the day, time
and duration of a generator set exercise/test period. Tests under load or with no load shall be
selectable.
Comply


10.0 General Equipment Shelter/Tower Requirements

10.1 Shelter Design Considerations

10.1.1 Equipment shelters shall be of a skid-mounted, bullet-resistant, prefabricated concrete
aggregate type designed to house radio communications and sensitive electronic equipment.
Comply
10.1.2 The interior wall measurements shall be no less than 10ft high, 12ft wide and 20ft long.
9 feet 8 inches for Section 10.1.2. Exterior dimensions shall include nominal wall, roof and skid
dimensions, to be determined by Proposer.
Per Addendum 4, released December 7, 2010:
Question:
15. The specification states: The interior wall measurements shall be no less than 10 ft high, 12 ft
wide and 20 ft long. Would the county consider 9’8” as an acceptable interior ceiling height to
avoid a special configuration with additional manufacturing cost?
Response: Yes, the County will allow the minimum interior ceiling height to be reduced to 9 feet 8
inches for Section 10.1.2.
Comply
10.1.3 Equipment shelters must provide an interior climate suitable for the operation of
sensitive electronic equipment, that is, it must be dust proof, watertight and airtight.
Comply
10.1.4 Each equipment shelter shall be supported by a concrete pad with attachment devices
appropriate for securing the building assembly to survive hurricane force (no less than 120-
mph) winds. In the case of sites determined by the Contractor as requiring elevation due to
potential flooding, the affected equipment shelter shall be set on poured concrete piers. The
finished length of piers shall extend, minimally, four feet above ground level but otherwise in
accordance with Contractor’s calculated flood plain elevation plus a two-foot contingency
margin. The flood plain data shall be 100 Year data for the location.
Comply
10.1.5 Skid components, attachment hardware, cross-braces and lifting eyes shall be hot-
dipped galvanized after fabrication.
Comply
10.1.6 Shelters shall be designed to withstand sustained hurricane force winds not less than
120-mph.
Comply
10.1.7 The exterior wall finish shall be exposed aggregate. Seeding of aggregate for an exposed
aggregate finish is not acceptable. Exterior walls must be bullet proof as defined below.
Comply


10.1.8 The roof shall be a flat, tapered type having a minimum slope of 1/2" per foot from the
roof centerline.
Comply
10.1.9 All exterior wall, floor and roof joints shall be sealed using a compressible, resilient
sealant. There shall be no exposed roof-to-wall or wall-to-floor joints.
Comply
10.1.10 Cement used in concrete shelters shall be standard Portland cement conforming to the
requirements of the “Standard Specification of Portland Cement”, ASTM Designation C150.
Concrete aggregate shall conform to the requirements of the “Specifications for Concrete
Aggregates” ASTM C33 and “Specifications for lightweight aggregates for structural concrete”
ASTM C330.
Comply
10.1.11 Exterior concrete surfaces shall be sealed with a minimum of two coats of
Thoroglaze H Sealer or equal.
Comply
10.1.12 The shelter’s interior floor shall be covered with 1/8" x 12" x 12" industrial weight solid
vinyl floor tile. Floor color shall be light beige.
Comply
10.1.13 Walls shall have a minimum thermal insulation factor of R11.
Comply
10.1.14 The shelter’s roof shall have a minimum thermal insulation factor of R19.
Comply
10.1.15 Interior wall surfaces shall be faced with white vinyl/coated wood paneling.
Comply
10.1.16 The interior ceiling surface shall be a white, vinyl coated plywood. Seams in the
plywood shall be trimmed with batten strips painted to match the ceiling.
Comply
10.1.17 Building openings for the door, air-conditioners, transmission line entrance and other
entries shall be framed and sealed in such a manner that moisture cannot penetrate the
insulation within the walls or the interior walls of the structure.
Comply
10.1.18 A single 36"W x 72"H x 3” thick insulated bulletproof steel door, equipped with a three-
point latch, shall be provided. All door hardware shall be stainless steel and incorporate three
external hinges. Door shall open outward to maximize internal building utilization.
Comply
The term ‘bulletproof” is defined, for this Specification, as unable to be penetrated by a.30-06
or. 308 commercial cartridge firing a lead tipped, 160-grain projectile, at not more than 2600 fps
muzzle velocity. The projectile will be test-fired at a range of 100 yards. The
structure/material must not be completely penetrated at that distance.
Comply


10.1.19 Stainless steel reinforced, fiberglass coated exterior awnings shall be provided to
protect the door entrance and air-conditioner units.
Comply
10.1.20 All hardware used on the exterior surfaces of this shelter shall be either hot-dipped
galvanized or stainless steel.
Comply
10.1.21 Wafer or particleboard wood products are not an acceptable construction material for
this project.
Understood
10.1.22 Contractor shall provide detailed fabrication drawings for the pier concrete foundation,
designed to adequately support the proposed building structures and wind loads. Additionally, the
building frame shall be mechanically bonded to the concrete foundation. Generators and fuel
tanks shall be similarly elevated for protection against rising water effects, if building locations
are flood prone. Fuel tanks shall be restrained from floating and must be secured with adequate
metal straps and anchors to prevent buoyancy of a tank of the required capacity at a 95% fuel
empty status. Strapping and anchor materials shall be hot- dipped galvanized protected.
Comply
All building and foundation detail drawings and related calculations must be reviewed and
approved by a Georgia-registered professional engineer.
Comply
All newly proposed construction (building and tower) shall conform to local, municipal,
township and state requirements. This includes, but is not limited to, GPS Survey, FAA Study,
Engineering Tower Design, Building Design, Land Survey, Structural Analysis, Site Layout,
Construction Drawings, Environmental and Endangered Species Study, Archeological Study,
Indian Burial Ground Study, US Fish and Wildlife Study, Wetlands Study, Georgia Game
Commission Study, Georgia Fish Commission Study, State Historical and Museum Commission
Study.
Comply
10.2 Shelter Electrical Requirements

10.2.1 Each shelter shall be equipped with overhead cable trays located above all planned
equipment cabinet groupings. Auxiliary cable trays shall be provided to support transmission lines
and telecommunications cables, as necessary. All cable tray joints shall be electrically bonded
using No. 6 AWG copper wire jumpers with approved compression fittings. Trays shall be
bonded to interior ground halo.
Comply
10.2.2 Individual, properly grounded 120VAC, 20A electrical circuits shall be provided to each
of the equipment racks/cabinets. Each shall be terminated as a single, duplex outlet mounted
on the cable tray directly above the center of each planned equipment cabinet.
Comply


10.2.3 Individual, properly grounded 120VAC, 30A electrical circuits shall be provided for each
battery charger unit. Sufficient flexible conduit shall be provided above the rack to permit
interconnection to chargers located at the bottom of the rack.
Comply
10.2.4 DC wiring for the radio network’s battery plant and interconnection to the various
equipment groupings shall be furnished and installed, as required.
Comply
10.2.5 Two 240VAC electrical circuits shall be provided for the HVAC system. Sizing of these
circuits shall be determined by the Proposer.
Comply
10.2.6 Install six quad 120VAC convenience outlets equally spaced along interior walls. A total
of three 15-ampere circuit breakers shall be provided (two quads per breaker).
Comply
10.2.7 Furnish and install a 120/240VAC automatic generator transfer switch and LPG
generator set, per Section 9.2, Generator Equipment Requirements. All circuits and outlets for
all equipment installed in the shelter shall be on the Emergency power system
Comply
10.2.8 The Contractor shall furnish and install one circuit breaker panel board. Panel board shall
be sized for all of the indicated branch circuits, equipment loads plus a fifty-five percent growth
factor.
Comply
10.2.9 The Contractor shall furnish and install an interior and exterior electrical ground halo
and power surge protection for each location, as follows:
Comply
A. A single No. 2AWG copper conductor ground halo shall be installed on all four
interior walls, spaced approximately six-inches below ceiling level. The halo shall
include a twelve-inch gap/break at the furthest point from the single-point ground
attachment.
Comply
B. Ground halo shall be mounted on six-inch standoffs, located on twelve-inch centers. It
shall be affixed to the transmission line ground entry port, buss bar.
Comply
C. All equipment cabinets, racks, transmission line entrance and cable trays shall be
individually bonded to the halo using No. 6AWG copper conductors with approved
compression fittings.
Comply
D. Interior halo shall be bonded to an exterior, buried ground network using low
impedance copper conductors.
Comply


E. Electrical lightning protector shall be Polyphasor model IS-IL 240BP or equal.
Comply
F. A single, stranded No. 00AWG copper exterior ground system shall be installed
about the building and tower perimeter, located approximately 18" below grade and
exothermically bonded to the building frame, interior halo, transmission line ladder,
generator system and radio tower legs. All grounding shall meet a required 3 Ohms or
less. All grounding practices and methods shall meet a recognized standard such as IEEE
or Motorola R 56.
Comply
10.2.10 Install 4-foot, 2-bulb, 80-watt fluorescent light fixtures as necessary to provide effective
illumination for each equipment cabinet. Emergency exit and inter lighting as required by fire
code. Exterior lights above the door and area lights on each of the exterior shelter corners shall
be controlled by at a maximum of two light switches located just inside the door opening on the
side away from the hinges at shoulder height.
Comply
10.3 HVAC Requirements

10.3.1 The Contractor shall furnish and install a dual, wall-mounted heating and air- conditioning
system appropriately sized for each shelter/equipment heat load. Each HVAC unit shall
incorporate circuitry to ensure that both compressors do not attempt to restart at the same time.
There shall be timer circuits to rotate use of the air conditioner units on a weekly basis.
Additionally, sensors may cause both air conditions to run simultaneously as needed to reduce
the internal temperature to a safe operating level.
Comply
10.3.2 Equipment shall be furnished with compressor anti-cycle circuitry to prevent short- cycle
starts against high compressor head pressure.
Comply
10.3.3 Equipment shall be furnished with a compressor hot gas bypass to minimize electrical
power surges as a result of compressor cycling.
Comply
10.3.4 Design of HVAC system shall take into consideration the following environmental
conditions:
Desired Interior Temperature: 72 degrees F Maximum

Outdoor Temperature: 98 degrees F Minimum Outdoor
Temperature: 10 degrees F Transmitter Power
Dissipation: 5,000 watts System Controller: 850 watts
Battery Charger/Inverter: 2,000 watts
Lighting: 650 watts (Intermittent)
Comply


10.3.5 Buildings shall incorporate a thermostatically controlled fan system designed to operate in
the event of a total HVAC failure and where the building’s interior temperature exceeds 98°F.
This system shall incorporate appropriate dampers, screens and filters to limit dust and insect
entry into the building.
Comply
10.4 Alarm Systems

10.4.1 The Contractor shall furnish and install an over/under temperature sensor, continuously
adjustable over the range of 30°F to 98°F, having independent Form-C output contacts suitable
for high/low temperature alarm activation.
Comply
10.4.2 The Contractor shall furnish and install a door entry alarm sensor, magnetic type,
having a Form-C contact closure output.
Comply
10.4.3 The Contractor shall furnish and install a single-loop smoke/fire alarm system.
Comply
10.4.4 Smoke/fire alarm sensors shall be mounted above battery charger equipment, and in
vicinity of AC power distribution panel board.
Comply
10.4.5 Smoke/fire alarm panel shall have visual indicators depicting individual alarm sensor
status.
Comply
10.4.6 Smoke/fire alarm panel shall operate from both 120VAC and 12VDC battery power
sources.
Comply
10.4.7 All shelters shall be equipped with an inert gas fire suppression system (FM 200 or
similar) that is environmentally approved and not injurious to communications staff. The system
shall be connected to the communications and shelter fire/smoke system alarms. Trigger of the
system causing a gas discharge shall cause the air conditioners to automatically shut off. The air
conditioner units must be manually restarted to purge the shelter of the gas, after all evidence
of combustion is resolved. All necessary plumbing and overhead dispersal equipment shall be
provided. The system shall have modes for test and maintenance that do not trigger activation.
The system shall be installed and delivered with a primary tank, on line and a spare, full tank,
off line. In the event of a discharge during testing by the vendor, Floyd shall not be responsible
for replacement or refill of the system. Refill of the system primary tank, by the vendor, due to
an actual event, the spare tank shall be placed in line and the discharged tank shall be refilled and
returned as the spare within 48 hours by the vendor.
Comply


10.5 Tower Requirements

10.5.1 The basic standard for the design of newly required steel antenna towers, wave guide
bridges and supporting structures, shall be ANSI/EIA-222-G or latest version.
Comply
10.5.2 Towers shall be either a self-supporting or guyed triangular shaped, solid-rod structure
having an overall height to be determined by the Proposer, based on the requirements of area
coverage and availability of clear Microwave paths for site connectivity. Limits of available space
in certain areas may dictate the use of Self-support towers.
Comply
10.5.3 Each tower shall be designed for a minimum sustained 120-mph wind speed, 0.5” ice load,
with the full complement of necessary antennas and required lights and other Federally-required
equipment. Proposal must take into consideration any current antennas that must be retained by
the County for other communications needs
Comply
10.5.4 Antenna loads shall be as determined by Proposer, however, the design shall include a
minimum 30% growth factor.
Comply
10.5.5 All fabricated tower assemblies and parts shall be hot-dipped galvanized after fabrication
per ASTM Standard A123. Hardware shall be galvanized per ASTM Standard A153 and B695.
Other types of zinc coating or plating are not acceptable.
Comply
10.5.6 Towers shall be supplied with a full-length transmission line ladder designed to accept
all transmission lines needed for the proposed design plus a 50% growth factor.
Comply
10.5.7 Towers shall be equipped with an outside climbing ladder/cable type safety device and
strobe-lighted in accordance with FAA and OSHA requirements.
Comply
10.5.8 Antennas, tower top pre-amps and transmission lines as specified by the licensed
frequencies and system design, shall be provided and installed by the Contractor.
Comply
10.5.9 Electrical Grounding Systems to meet industry standard, as specified above, shall be
furnished and installed by the Contractor in accordance with the following minimum practices:
Comply
• Install a ground ring around the base of the tower, consisting of 8’x 5/8” ground
rods driven to a depth necessary to meet the required resistance measurement of the
specifications, adjacent to the foundation of the tower at each leg. Ground rods are to
be interconnected by a minimum #00AWG stranded copper wire, which is Cadwelded
to each top most ground rod. Copper wire and ground rods are to be installed in a
trench of a minimum depth of 18-inches below finished grade. Maximum spacing
between rods shall be 15-feet. Each tower leg shall be bonded to the ground ring by
#00 stranded copper wire, which has been Cadwelded to the factory provided tab,
manufactured onto the tower leg and to the closest ground rod, avoiding any acute


bends in the wire. All paint shall be removed from the tab on the tower leg (if painted)
at the point the ground connection is made. At the completion of the Cadwelding
process, the welded area shall be resealed with a cold galvanizing compound and
repainted if originally painted.
Comply
•
The ground rod/ring system shall extend around the perimeter of the equipment
shelter, transmission line copper entrance port into the shelter and to the perimeter
fence.
Comply
•
Bond all transmission line outer shields to the structure at the top of the tower
immediately below the antenna pig tail, mid point if the tower is over 200-feet tall,
and at the bottom section of the tower at a point one foot above the bend made in the
line to attach it to the Waveguide Bridge and at the copper plate at the entry port into
the tower.
Comply
•
Fencing shall be grounded to the ground ring via #2AWG solid copper wires,
bonded, using Cadweld fittings at each fence post. All Cadwelding locations shall be
cold galvanized as above
Comply
o Antenna mounts shall be grounded to the tower. A copper ground rod shall be
mounted to the topmost part of the tower to be the highest point on the structure.
A #00AWG stranded copper wire shall run down the tower leg closest to the
shelter entrance port and all to ground connections of antenna cables and fixtures
on the tower shall be made to this copper wire. This shall terminate at the copper
ground rod at that closest leg foundation and be fully bonded into the ground ring.
Comply
o The shelter’s interior halo ground and transmission line copper inside entrance port
(buss bar) shall be bonded to the outdoor ground system.
Comply
•
A ground test well shall be provided at a minimum of two points along the ground
ring. The test wells shall consist of 4”x 2’ PVC pipe, with a screw type cap installed.
The test well shall allow measurement of ground system resistance at opposite corners
of the tower.
Comply
•
Grounding system resistance shall be measured to be 3-ohms or less between any
point on the ground system and earth ground.
Comply
10.6 Required Tower Submittals

10.6.1 The Contractor shall furnish wind-load stress and foundation calculations used in the
design of the proposed tower structure. These calculations must have been developed and
approved by a Professional Engineer registered in the State of Georgia.
Comply


10.6.2 The Contractor shall furnish documentation approved by a registered professional
engineer, licensed in the State of Georgia, certifying that the proposed tower and foundation
meets the requirements of ANSI/EIA-222G or latest version and is in accordance with these
Specifications.
Comply
10.6.3 Prior to proposal submission, Proposers shall, at their own expense, make such
additional investigations on site conditions, as necessary, for the successful and accurate
completion of their Proposal Submittal. Floyd County shall permit site inspection access
during normal business hours.
Comply
10.6.4 Proposers shall furnish documentation as to any special condition or restriction applied to
the use of materials, products or equipment contained in their Proposal. Contractor shall provide
to the County a minimum of two sets of completed as-builts on each tower and shelter
installed in this project. This shall include engineering and design document from the tower and
shelter manufacturer.
Comply
10.6.5 The Contractor shall furnish written certification that all installed tower components have
been assembled and hot-dipped galvanized in accordance with these minimum requirements.
Comply
10.6.6 The Contractor shall provide a detailed report of electrical ground resistance measurements
of the completed, as-installed, electrical grounding system, on a per-site basis with field drawings
to indicate the measurement at a specific location.
Comply
10.6.7 All newly proposed tower construction shall conform to local, municipal, township and
state requirements. This includes, but is not limited to, GPS Survey, FAA Study, Engineering
Tower Design, Building Design, Land Survey, Structural Analysis, Site Layout, Construction
Drawings, Environmental and Endangered Species Study, Archeological Study, Indian Burial
Ground Study, US Fish and Wildlife Study, Wetlands Study, Georgia Game Commission
Study, Georgia Fish Commission Study, State Historical and Museum Commission Study.
Comply

11.0 Site Work Requirements

11.1 Site Preparation and Subgrading

11.1.1 General
Site clearing, initial earthwork and rough grading and final grading as needed for installation of
towers and equipment shelters is the responsibility of the Contractor. The following describes
a set of minimum requirements for the execution and completion of site-related construction
activities.
Comply


11.1.2 Performance
1. Dewatering:
a. Control grading around excavations to prevent surface water from flowing into
excavation areas.
Comply
b. Drain or pump as required thereby maintaining all excavations, trenches and pier
holes free of water from any source and discharge to approved drains or channels.
Commence dewatering action when water first appears and continue until work is
complete to the extent that no damage will result from hydrostatic pressure, flotation, or
other causes.
Comply
c. Use pumps of adequate capacity to insure rapid drainage of area, and construct and
use drainage channels and sub-drains with sumps as required.
Comply
d. Remove unsuitable excessively wet sub-grade materials and replace with approved
backfill material.
Comply
2. Compaction:
a. Compact sub-grades, fills, embankments and backfills using spreading equipment,

tamping rollers, rubber-tired rollers, vibratory compactors, or power tampers, as required
to obtain reasonable uniformity. Nuclear soil testing results are required to be provided
in a report to the Consultant.
Comply
b. Perform within moisture content range as specified to obtain required results with
equipment used.
Comply
c. Achieve minimum densities specified as references to:
Comply
1) Cohesive soils - 95 percent maximum density at optimum moisture, AASHTO
T99.
Comply
2) Cohesionless Soils – 70 percent of maximum relative density.
Comply
a) ASTM, STP 479 Bunnister method.
Comply


b) USBR - E12 relative density.
Comply
c) Relative density, ASTM D2049.
Comply
3) Cohesionless Soils
Comply
a) Floyd County or designee may approve the use of AASHTO T99 for
certain cohesionless soils using at least 100 percent of maximum density.
Comply
4) Compact control fill and backfill in not over 8-inch lifts/layers and compact to
between 90 % to no more than 96 % of maximum density at optimum
moisture AASHTO T99.
Comply
11.2 Drilled Pier Foundations

11.2.1 General
1. Extent of Work:
a. Perform all drilling and excavation and supply all labor and materials to construct
drilled pier foundations, as necessary.
Comply
11.2.2 Performance
1. Quality Assurance:
a. Field Inspection by County designee - quality control.

Comply
1) Floyd County's Project Representative will be designated to be responsible for
field inspection of the drilled pier foundations. He will transmit, in writing, to
consultant and Contractor any materials or methods observed by him, which do
not conform to this specification and, if required, will not be considered for
payment. The County's Project Representative must inspect each drilled pier.
Specific responsibilities of the County's Project Representative will be to:
Understood
a) Observe drilling excavation of drilled pier foundations. Ensure the
placement of anti-caving physical barriers or the use of special drilling mud
to prevent excessive cavitation.
Understood


b) Inspect material and equipment used in construction of drilled piers.
Understood
c) Inspect bearing elevation of drilled piers.
Understood
d) Observe placement of concrete and rebar within the drilled pier
foundation to match design specification. Ensure that no excessive earth
contamination occurs. Contamination of poured concrete is sufficient to
cancel the pour and request engineering inspection.
Understood
e) Floyd’s representative shall photograph or film all foundation
excavation and pouring activities.
Understood
2. Contractor Qualifications
a. A minimum of two years experience in drilled pier construction, including experience

with similar subsurface material, water conditions, shaft sizes, and special techniques as
required.
Comply
3. Drilled Pier Details
a. Drilled shaft dimensions and top elevations shall be in accordance with foundation
design calculations and drawings.
Comply
b. The drilled shaft bearing or bottom elevation shall be at the elevation indicated,
unless it is determined by the County's Project Representative that the bearing elevation
should be adjusted.
Comply
4. Drilled Pier Excavation
a. Excavate drilled shaft to dimensions and required elevations as indicated. Maintain

sidewall stability during drilling and extend excavation to suitable material.
Comply
b. Determine suitability of supporting material for drilled piers as follows:
Comply
1) Inspection of each pier will be by the County's Project Representative and
Contractor.
Comply
c. Remove from bottom of drilled piers, loose material or free water in quantities
sufficient to cause settlement or affect concrete strength as determined by the County's


Project Representative.
Comply
d. Install temporary casing, where required, to prevent caving of drilled pier sides or
excessive seepage.
Comply
e. Dewater all drilled pier excavations prior to cleaning, inspection, and placing
concrete.
Comply
f. Each drilled pier must be inspected and approved by the County’s Project
Representative before any concrete may be placed.
Comply
5. Excavated Material
a. Dispose of any excavated material at locations approved for that purpose.
Comply
6. Reinforcing Steel
a. Place reinforcement for drilled piers in accordance with foundation design documents.
Comply
b. Place bars as shown on foundation drawings with concrete cover of not less than 3-
inches where exposed to soil.
Comply
c. A reinforcing cage shall be designed as a structural element and braced to retain its
configuration throughout the placing of concrete and the extraction of the casing (if
used) from the shaft.
Comply
7. Concreting
a. Dewater drilled piers and maintain the excavation free of water prior to placing
concrete.
Comply
b. Place concrete immediately after final inspection.

Comply
c. Place concrete immediately after completion of excavation and after County's
Project Representative has completed his inspection. Do not leave uncased excavations
open over night.
Comply


d. Free fall concrete (not over 6') may be used provided it is directed through a
hopper, or equivalent; such that fall is vertical down center of shaft without hitting
sides. Vibrate concrete, but only after casing, if used, has been pulled.
Comply
e. Place concrete in pier in one continuous pour operation from bottom to top.
Comply
f. The County's Project Representative will provide inspection during the removal of
casing and placing of concrete. Withdraw casing, if used, only as shaft is filled with
concrete. Maintain adequate head of concrete to balance outside soil and water
pressure above the bottom of the casing at all times during withdrawal. Specific
procedures that the Contractor will follow to accomplish this objective shall be submitted
for approval.
Comply
g. Where casing is removed, provide specifically designed concrete with a minimum
slump of 5-inches and with a retarder to prevent arching of concrete (during casing
pulling) or setting concrete until after casing is pulled. Check concrete level prior to,
during, and after pulling casing. Pull casing before slump decreases below 5-inches as
determined by testing.
Comply
h. During casing extraction, upward movement of the reinforcing steel shall not be
permitted. Downward movement should not exceed 2-inches per shaft length.
Comply
i. Remove all water and concrete contaminated with soil, or water before resuming
concrete placement.
Comply
j. Center reinforcing cages in the drilled pier excavation and suspend them in an
approved manner prior to placement of concrete to the cutoff elevation.
Comply
k. Leave forms on pier for a period of three days.
Comply
l) Set anchor bolts to the manufacturer’s required tolerances, using substantial
templates or other approved method.
Comply
11.3 Concrete, Forms and Reinforcement

11.3.1 General
1. This Specification includes concrete, forms, and steel reinforcement as used for:
a. Drilled pier foundations with square caps for steel structures.
Comply


b. Concrete pads for transformers and breakers.
Comply
c. Equipment shelter and tower foundations.
Comply
d. Cable trench.
Comply
2. Quality Assurance
a. Applicable Standards
Comply
1) American Concrete Institute (ACI)
Comply
a) ACI 304 - Recommend Practice for Measuring, Mixing, and
Placing Concrete.
Comply
b) ACI 305 - Committee Report on Hot-Weather Concreting.
Comply
c) ACI 306 - Committee Report on Cold-Weather Concreting.
Comply
d) ACI 315 - Manual of Standard Practice for Detailing Reinforced
Concrete Structures.
Comply
e) ACI 318 - Building Code Requirements for Reinforced Concrete.
Comply
2) American National Standards Institute (ANSI)
Comply
a) B 1 8.2.1 - Square and Hex Bolts and Screws, Including Askew
Head Bolts, Hex Screws, and Lag Screws.
Comply
b) B 1 8.2.2 - Square and Hex nuts.
Comply


3) American Society for Testing and Materials (ASTM).
Comply
a) A36 - Structural Steel.
Comply
b) A82 - Cold-Drawn Wire.
Comply
c) AI 85 - Welded Steel Wire Fabric for Concrete Reinforcement.
Comply
d) A307 - Low-Carbon Steel Externally and Internally Threaded Standard
Fasteners.
Comply
e) A615 - Deformed Billet Steel Bars for Concrete Reinforcement.
Comply
f) C31 - Making and Curing Concrete Compression and Flexure Test
Specimens in the Field.
Comply
g) C33 - Concrete Aggregates.
Comply
h) C39 - Compressive Strength of Cylindrical Concrete Specimens.
Comply
i) C94 - Ready-Mixed Concrete.
Comply
j) C 143 - Slump of Portland Cement Concrete.
Comply
k) C 150 - Portland Cement.
Comply
m) C309 - Liquid Membrane-Forrning Compounds for Curing
Concrete.
Comply
n) C494 - Chemical Admixtures for Concrete.
Comply
4) Midwest Concrete Industry Board (MCIB).
Comply


11.3.2 Equipment and Materials
1. Concrete Materials
a. Cement
1) Conform to ASTM C 150. Portland cement Type 1.

Comply
b. Water
1) Water shall be clean and free from injuries amounts of oil, acids, alkalines, or
other deleterious substances. Any potable drinking water will be acceptable.
Comply
c. Fine Aggregates
1) Clean natural sand. Manufactured sand may be used upon written approval of
Floyd County’s designee. Conform to ASTM C33.
Comply
d. Coarse Aggregates
1) Clean crushed stone or processed gravel, not containing organic materials.

Conform to ASTM C33.
Comply
e. Air Entertainment
1) 4-6 percent air shall be used in all concrete.
Comply
f. Water Reducing Admixture
1) Conform to ASTM C494, Type A.

Comply
2. Concrete Mix
a. Ready-mixed Concrete
Comply
1) Concrete shall meet requirements of ASTM C94, and of materials and
proportions specified.
Comply


2) Ready-mixed concrete plant shall be subject to approval of Floyd County’s
Project Representative.
Comply
3. Forms
a. Form materials; use one of the following:
1) Exterior grade plywood 5/8 inch thick.

Comply
2) Approved wood fiberboard.
Comply
3) Dressed lumber, free of loose knots.
Comply
4) Approved preformed economy forms.
Comply
5) Forming materials may be treated with approved form oil for ease of form
removal.
Comply
b. Form Ties
1) Approved break-back type.

Comply
4. Steel Reinforcement
a. Reinforcement Bars
Comply
1) Conform to ASTM A615, Grade 60 for all bars No.4 or larger.
Comply
b. Tie and-All No.3 Bars
Comply
1) Conform to ASTM A615, Grade 40.
Comply
c. Welded Wire Fabric
1) Conform to ASTM A185, using bright basic wire conforming to ASTM

A82. Wire gauge No. 11 or smaller shall be galvanized.


Comply
5. Grout
Comply
Use unshrink, easy flow type grout as approved by Floyd's Project Representative.
Comply
6. Anchor Bolts
a. Provide all anchor bolts required for complete installation.

Comply
b. Anchor bolts and accessories shall conform to ASTM A307 using A36 steel.
Comply
c. Use hexagonal bolts and nuts conforming to ANSI B 1 8.2.1 and B 1 8.2.2.
Comply
d. All exposed area of anchor bolts and nuts, plus a minimum of three inches of
embedded area, shall be hot-dipped galvanized.
Comply
e. Install as indicated on foundation drawings.
Comply
11.3.3 Performance
1. Field Testing
a. Field testing of concrete and making of concrete test cylinders will be performed by
an independent testing laboratory approved by the Floyd County Permit Department.
Comply
b. Laboratory Testing
1) Laboratory for testing shall be selected and paid by Floyd County.

Comply
2) Laboratory will furnish cylinder molds with cap seals or adequate means of
identification.
Comply
3) Cylinders shall be tested conforming to ASTM C39. Average strength of two
test cylinders (at 28 days) shall be used as result of the test. Break one test cylinder
after 7-days curing, one after 14-days, and two after 28-days.
Comply


4) Results shall be provided to the Project Representative in a formal report. A
copy shall be provided to the Consultant and Contractor.
Comply
2. Low Strength Concrete
a. Defined as concrete whose 7-day and 14-day test (average of 2 cylinders) is less than
70% and 85%, respectively, of the specified minimum 28-day compressive strength. If
concrete does not meet the 4000 lb. test in twenty-eight days, the Contractor shall pay for
the cost of the core test.
Comply
b. Disposition of Concrete
1) Concrete shall remain accessible with no other work performed that relates to or
depends upon the questionable concrete until a formal decision as to the
disposition of the concrete is given by Floyd’s Project Representative.
Comply
2) Low strength concrete shall be removed and replaced if so requested by
Floyd County’s designee.
Comply
3. Placing of Concrete
a. Preparation
1) Clean bonding surfaces free from laitance and foreign materials.

Comply
2) Place concrete on property prepared and unfrozen sub grade and only in
dewatered excavations.
Comply
3) Do not deposit partially hardened concrete or concrete contaminated by
foreign materials.
Comply
b. Placing Concrete
1) Conform to ACI 304.

Comply
2) Place within 60 minutes after mixing, except the County’s designee may
extend the period to 90 minutes (maximum) dependent upon weather conditions.
Comply
3) Place in horizontal layers not exceeding 18-inches.
Comply


4) Vibrate concrete to produce solid mass without honeycomb or surface air
bubbles.
Comply
c. Curing Concrete
1) Cure with liquid membrane-forming compound conforming to ASTM

C309, Type I. Apply according to manufacture’s recommendations.
Comply
2) Apply curing compound to all exposed surfaces immediately after removing
form or after finishing concrete.
Comply
3) Keep formwork wet until stripped.
Comply
d. Cold Weather Placing
Comply
1) Conform to the practice recommended in ACI 306 when the temperature is
below 40-degrees F or is likely to fall below 40-degrees F during a twenty- four
hour period after placing.
Comply
2) Protect pier caps and other concrete from freezing by the use of insulating
blankets.
Comply
e. Hot Weather Placing
Comply
1) Conform to practices recommended in ACI 305 when temperature is 90-
degrees F or above or is likely to rise above 90-degrees F within a twenty-four hour
period after placing.
Comply
4. Construction Joints
a. Locate where indicated. Conform to AC 318.

Comply
b. Clean and break laitance or other foreign material from bonding surface. Bed with 1-
inch of grout for bonding in horizontal joints.
Comply
5. Surface Finishes
a. Float Finish
Comply


1) Compact, accurately screed, and wood float all slabs to a true uniform
surface.
Comply
2) Test surface with straightedge and eliminate high and low spots of more than
1/8 inch in ten feet.
Comply
3) Use this finish in addition to the finishes specified below for all surfaces as
indicated.
Comply
4) Use a final finish for footing slabs not exposed.
Comply
b. Hand-troweled Finish
Comply
1) Finish surface as in Float Finish and in addition, trowel and steel trowel to
obtain a smooth dense finish after concrete has hardened to ring under the
trowel.
Comply
2) Use this finish on all floors, slabs, and equipment bases not specifically
designated for a different finish.
Comply
c. Broom Finish
Comply
1) Finish surface as in Float Finish and, in addition, draw a stiff bristled
broom across the previously floated surface.
Comply
2) Corrugations shall be uniform in appearance, not more than 1/16-inch in
depth and shall be perpendicular to direction of traffic.
Comply
3) Use this finish on all outdoor slabs subject to vehicular or pedestrian traffic and
areas to receive grout.
Comply
d. Burlap Finish
Comply
1) Apply burlap surface treatment to exposed edges of slabs, curbs and
foundations.
Comply


2) Wet and fill all voids using mortar with the same sand-cement ratio as
original concrete. Use approximately 20 percent white cement to match
concrete color.
Comply
3) Strike off all excess mortar flush with the surface using a burlap or canvas cloth
with a circular motion.
Comply
4) Remove all rough spots and rub with cloth to leave a surface of uniform
texture and appearance.
Comply
5) Finish shall result in a coating of mortar that will fill all small voids and air holes
leaving a smooth surface.
Comply
6) Cure as specified under Curing Concrete.
Comply
6. Defective Surface Treatments
a. After removal of forms, remove all fins, projections and form ties.
Comply
b. Grout and cure all voids, damaged areas, and tie holes.
Comply
7. Forms
a. Treat forms with an approved oil or lacquer prior to placing reinforcement.
Comply
b. Wet forms with clean, clear water prior to placing concrete.
Comply
c. Adequately brace and stiffen forms to prevent deflection and settlement.
Comply
8. Steel Reinforcement
a. Place accurately, tie at intersection, and support on chairs. Conform to ACI 318.
Comply


b. Tie securely with 16 gauge or larger annealed iron wire.
Comply
c. Splice steel not less than 30 bar-diameters for A615, Grade 40, and 42 bar-
diameters for A615, Grade 60, unless otherwise indicated.
Comply
d. Splice plain bars not less than twice that for deformed bars.
Comply
e. Lap welded wire fabric not less than the length of one mesh.
Comply
f. No.3 bars to be Grade 40, with all others to be Grade 60.
Comply
g. Provide ¾-inch chamfer for all exposed edges of concrete, vertical and horizontal.
Comply
11.4 Fences and Gates (ChainLink Security Type)

11.4.1 General
1. Description
a. This section covers chain-link fabric fence and gates.
Comply
Comply
1) Federal Specifications (FS)
Comply
a) FF-BO-575 - Bolts, hexagon and square.
Comply
b) RR-F-191 - Fencing, wire and post, metal and gates, chain-link fence
fabric, chain-link and accessories.
Comply


c) RR-F-221 - Fencing, wire, barbed wire, woven-wire and netting, fence
post and accessories.
Comply
11.4.2 Requirements
a. Manufacturer’s standard materials where such materials conform to these

Specifications or have been approved by Engineer.
Comply
b. Conform to FS RR-F-191 except as indicated or specified otherwise.
Comply
c. Fence height – 8 ft high galvanized chain link with 4-strand barbed wire at top (9½ feet
overall height).
Comply
d. Gate widths as indicated on layout drawings.
Comply
e. Finish for framework and appurtenances (excluding fabric) – Galvanized with
minimum weight for zinc per square foot as follows:
Comply
1) Pipe – 1.8 ounces.
Comply
2) Hardware and accessories – conform to FS RR-F-191.
Comply
3) Barbed wire – 0.80 ounce.
Comply
f. Finish for fabric
1) Galvanized per ASTM A392, Class-2 with 1.8-ounce, minimum weight, for
zinc per square foot or
Comply
2) Aluminum coated per ASTM A491, Class-2 with 0.40-ounce, minimum
weight, for aluminum per square foot.
Comply
g. All fence and gates to have 4-strand barbed wire at top.
Comply
h. All materials furnished shall comply with the above requirements.
Comply


11.4.3 Fabric
a. No.9 gauge, 2-inch diamond mesh chain-link fabric.
Comply
b. Top and bottom selvage twisted and barbed.
Comply
c. Fabric fastenings of 9-gauge galvanized wire ties.
Comply
11.4.4 Posts, Top Rail and Braces
a. Posts
1) End, angle, corner or pull posts – 3-inches O.D. at 5.79 pounds per foot.
Comply
2) Line posts – 2.5-inches O.D. at 3.65 pounds per foot.
Comply
3) Gate posts – 4.0-inches O.D. at 9.10 pounds per foot.
Comply
b. Top rail
1) 1.625-inch O.D. standard weight steel pipe.

Comply
2) 18-foot minimum length of each section.
Comply
3) Expansion type coupling for each joint.
Comply
c. Post bracing
1) Diagonal truss rods 3/8 inch in diameter equipped with truss tightener.
Comply
2) Horizontal braces – 1.660-inch O.D. at 2.27 pounds per foot.
Comply
d. Post tops


1) Designed as a weather tight closure cap for tubular posts.
Comply
2) Malleable iron or pressed steel.
Comply
e. Barbed wire supporting arms
1) Single arm at 45-degrees with vertical, sloping to outside of fence.

Comply
2) Constructed for attaching four rows of barbed wire to each arm and designed as
a weather tight closure cap for tubular posts.
Comply
3) Designed for 200-pound minimum pull down load.
Comply
4) Attached to steel posts or integral with post top.
Comply
5) Provided with openings to receive top rail.
Comply
6) Malleable iron or pressed steel.
Comply
f. Stretcher bars
Comply
1) One piece, full height of fabric.
Comply
2) 3/6 inch x ¾ inch, galvanized.
Comply
3) Bands of galvanized steel or malleable iron.
Comply
g. Bolts
1) Zinc coated.
Comply


2) Conform to FS FF-B-575.
Comply
11.4.5 Barbed Wire
Comply
a. Two-strand, l2½ gauge wire with 4-point barbs 5 inches O.C.
Comply
b. Conform to FS RR-F-221, Type 1, Style 2.
Comply
c. Four rows required on all fence and gates.
11.4.6 Gates
a. Framing
1) Frames of tubular members, 2-inch O.D. at 2.72 pounds per foot.

Comply
2) Intermediate horizontal and vertical members for proper gate operation and
for attachment of fabric, hardware and accessories.
Comply
3) Frames assembled by welding or watertight galvanized steel rigid fittings.
Comply
4) Diagonal cross bracing of 3/8 inch diameter adjustable truss rods to provide
frame rigidity.
Comply
5) Gate end members extended one foot above top members to receive four rows
of barbed wire.
Comply
b. Hardware
1) Hinges of pressed or forged steel, or malleable iron, non-lift-off type, 1 1.2 pair
per leaf.
Comply
2) Latches and gate stops – double leaf.
Comply


a) Plunger-bar type latch, full gate height, designed to engage gate stop
of flush-plate type with anchors.
Comply
b) Locking device and padlock eyes an integral part of latch.
Comply
c) Keeper to automatically engage gate leaf and secure free end of gate
in full 90-degrees open position.
Comply
3) Latches – single leaf.
a) Forked type to permit operation from either side of gate.
Comply
b) Padlock eye as integral part of latch.
Comply
11.4.7 Performance
1. Installation
a. Fence
Comply
1) Follow general contour of ground and properly align.
Comply
2) Posts
Comply
a) Set in concrete retaining wall. Trowel finish tops of footings and dome
to direct water away from posts.
Comply
b) Install plumb and in straight alignment.
Comply
c) Space ten feet center-to-center maximum.
Comply
d) Temporarily brace until concrete in bases has set.
Comply
3) Post Bracing
Comply


a) Install at each end and gatepost, and on each side of comer posts.
Comply
b) Install after concrete in post bases has set.
Comply
c) Install so posts are plumb when diagonal rod is under tension.
Comply
4) Top Rails
a) Run continuously through post caps or barbed wire supporting arms.

Comply
b) Install expansion coupling at each joint.
Comply
5) Tension Wire
a) Weave through the fabric and tie to each post with minimum 6 gauge
galvanized wire.
Comply
6) Fabric
a) Stretch taut with equal tension on each side of line posts.
Comply
b) Fasten to top rail and steel posts with wire ties.
Comply
c) Space wire ties at 12-inches O.C. maximum on posts and at 24-
inches O.C. maximum on top rail.
Comply
7) Stretcher Bars
a) Thread through or clamp to fabric 4-inches O.C.

Comply
b) Secure to posts with metal bands spaced 15-inches O.C. maximum.
Comply
c) Install at each gate, pull and end post, and each side of comer post.
Comply


8) Barbed Wire
a) Attach four rows to each barbed wire supporting arm. Pull wire taut
and fasten securely to each arm.
Comply
b) Install four rows above fabric and on extended gate end members of
gates.
Comply
b. Gates
1) Install plumb, level, and free swinging through full opening without interference.
Comply
2) Install all hardware, including keepers, ground set items and flush plate in
concrete to engage gate stop.
Comply
3) Furnish and install gate alarms.
Question:
26. Please specify type of gate alarm.
Response: It is the responsibility of the Proposer to make that determination as defined by the
RFP.
Comply
4) Adjust and lubricate as necessary for smooth operation.
Comply
c. Repairing Damaged Coatings
1) Repair any damaged coating in the shop or field by recoating with compatible
and similar coating.
Comply
2) Apply per manufacturer’s recommendations.
Comply
d. Danger Signs
Comply


1) Furnish and install signs as approved by Floyd County’s designee.
Note: All fencing at any site must be exothermically bonded to the site’s electrical grounding
system. All major posts, gates and fabric must be integrated into this bonding scheme. All
locations of exothermic bonding must be properly treated by recoating with a compatible and
similar coating to prevent corrosion.
Comply
11.5 Crushed Rock Surface

11.5.1 General
1. Description
a. This section includes crushed rock surface and method of depositing for the placement
of permanent crushed rock surfacing in equipment shelter areas.
Comply
b. Related work specified elsewhere.
Comply
1) Site preparation and earthwork – Section 10.1.
Comply
2) Herbicide application – Section 10.6.

Comply
Comply
1) American Society for Testing and Materials
Comply
a) C117– Test for Materials Finer than No. 200 Sieve in Mineral
Aggregate by Washing.
Comply
b) C131– Test for Abrasion of Coarse Aggregates by Use of Los
Angeles Machine.
Comply
c) C136 – Test for Sieve or Screen Analysis of Fine and Coarse
Aggregates.
Comply


d) D423 – Test for Liquid Limit of Soils.
Comply
e) D4242–Test for Plastic Limit and Plasticity Index of Soils.
Comply
f) D75 – Sampling Stone, Slag, Gravel, Sand and Stone Block for Use as
Highway Materials.
Comply
2) American Association of State Highway and Transportation Officials
(AASHTO).
Comply
a) T99–Test for the Moisture Density Relations of Soils Using a 5.5-
Pound Rammer and a 12-Inch Drop.
Comply
b) Samples and Testing.
Comply
1) Test to determine conformance with all requirements for
material quality and properties specified herein will be performed
by an independent laboratory approved by Floyd County and
compensated by the Contractor.
Comply
2) Obtain representative samples of material in accordance with
ASTM D75 for testing. Furnish Floyd’s designee sufficient
materials for testing from each sample at the time obtained.
Comply
3) Furnish specific schedule for sampling to provide Floyd’s
designee the opportunity to observe sampling.
Comply
4) Quality control testing will be performed during construction by
a testing laboratory retained by Floyd County.
Comply
3) Submittals
a) Includes, but not limited to, the following:
1) Test result reports from testing laboratory indicating

conformance with the specifications.
Comply
2) Certification of conformance with the specifications.
Comply


11.5.2 Equipment
1. General
a. Crushed rock surface shall consist of ¾” aggregate placed on top of a 6-mil

polyvinyl.
Comply
2. Aggregate
a. Crushed limestone or crushed natural gravel, free from lumps or balls of clay or
other objectionable matter, and reasonably free from thin and elongated pieces of dirt.
Aggregates shall consist of angular fragments, durable and sound, and shall be
reasonably uniform in density and quality.
Comply
11.5.3 Performance
1. General Requirements a. Stockpiles
1) Only with approval of Floyd County’s designee in specified locations.

Comply
2) Clear and level storage sites prior to stockpiling.
Comply
3) Place in a manner and at locations designated by Floyd County, providing
separate stockpiles for materials from separate sources.
Comply
b. Preparation of sub-grade
Comply
1) Clean off all foreign substances.
Comply
2) Correct any ruts, depressions, or soft yielding spots and areas with inadequate
compaction.
Comply
3) Treat all sub-grade areas with soil sterilant.
Comply
4) The County’s Project Representative will inspect, prior to placing crushed rock
surface, for adequate compaction and surface tolerances.
Comply
c. Grade control
1) Establish and maintain by means of grade stakes, properly spaced so string lines


may be stretched between stakes.
Comply
2. Placing, Shaping and Compaction of Materials
a. Placing
1) Deposit and spread material in a uniform lift/layer and compact to the

thickness indicated and as specified. Spread material uniformly on the prepared
sub-grade from moving vehicles or spreader boxes.
Comply
2) Level material to the required contour and grades.
Comply
3) Remove those portions of the layer, which became segregated or mixed with
sub-grade material in spreading and replace with new material as required by
Comply
4) Hauling which may damage the sub-grade or surfacing will be restricted by
Comply
5) Remove and repair sub-grade areas damaged during application of the
crushed rock surface.
Comply
b. Shaping and Compacting Materials
1) Compact layers no less than 3-inches or more than 6-inches thick.

Comply
2) Roll to specified compaction requirements throughout full depth of layer with
power rollers, rubber-tired rollers or combination.
Comply
3) Shape and smooth by blading and rolling with power roller, rubber-tired
roller, or both.
Comply
4) Hand tamp in places not accessible to rolling equipment.
Comply
5) Degree of compaction shall be as follows:
Comply


a) Base compaction on weight per cubic foot of material passing ¾ inch
sieve and compact to at least 100 percent of maximum density at optimum
moisture.
Comply
b) Determine and control compaction in accordance with AASHTO T99.
Comply
6) Smoothness test shall be as follows:
a) Surface shall show no deviation in excess of 3/8 inch in any 10 feet

when tested with a 10 foot straightened applied parallel with and at right
angles to the center lines of the paved area.
Comply
b) Correct any deviation in excess of this amount of loosening, adding or
removing material, reshaping, watering, and compacting as requested by
Comply
11.6 Herbicide Applications

11.6.1 General
1. Description
a. This Section includes a type of herbicide and method of placing on all areas to
receive crushed rock surfacing prior to placing crushed rock.
Comply
Note: Herbicides may be only applied by an individual/firm certified in the manufacturer’s
recommended proper and safe application methods.
Comply
11.6.2 Equipment and Materials
1. Sprayers and applicators shall be suitable for intended use.

Comply
2. Mix herbicide per manufacture’s recommendations.
Comply
3. Herbicide shall be Krover (1) as manufactured by Dupont, Inc., or an approved equal.
Comply
4. Do not apply herbicide if it is too windy or where other adverse weather conditions exist.
Comply


5. Apply at a rate of 10 pounds of product per acre, or in accordance with manufacturer’s
recommendations.
Comply
11.6.3 Performance
1. Apply only after final sub-grade has been established.

Comply
2. Apply before installation of vegetation barrier cloth and placement of crushed rock.
Comply
3. Follow manufacturer's recommendations on timing of application with respect to weather and
barrier/crushed rock placement.
Comply

12.0 Installation Guidelines

12.1 Engineering Drawings

12.1.1 Contractor shall furnish detailed drawings prior to installation of each major portion of the
system as follows:
A. Transmitter Site(s)
Comply
B. Receiver Site(s)
Comply
C. Site Antenna, Tower, and Grounding System(s)
Comply
D. Receiver Voter Equipment
Comply
E. System Controller Equipment
Comply
F. Dispatcher Console Equipment
Comply
G. Microwave Equipment Terminal(s)
Comply


12.1.2 Drawings shall, as a minimum, illustrate:
A. Relative cabinet/rack locations
Comply
B. Equipment power wiring (primary and emergency)
Comply
C. Equipment interconnection wiring (signal and control)
Comply
D. RF component interconnection details i.e. transmitter, combiner, antenna, etc.
Comply
E. Appropriate signal/voltage levels to facilitate alignment of level-sensitive components.
Comply
12.1.3 Civil drawings showing location details of equipment to be placed in existing or new
facilities shall be provided by Contractor.
Comply
12.1.4 Contractor shall provide a comprehensive test record of alignment levels, settings and
software versions installed within both infrastructure and user equipment. The scope and detail
of the comprehensive equipment test and acceptance plan shall be completed prior to Contract
Execution with the Successful Proposer. Prior to commencement of acceptance testing
procedures, the Contractor shall ensure that all installed equipment has been furnished with the
latest software releases available for those equipment items/groupings.
Comply
12.1.5 Contractor shall supply true copies of Final Project Record Documents which will
include the Engineering Drawings, software releases and alignment details listed above, but
amended to show system and equipment "as built" at the time of acceptance by Floyd
County. The total number of document sets to be provided shall include one site-specific set for
each infrastructure site and three comprehensive network sets for County use. Final Project
Record Documents must be submitted to Floyd County’s Project Representative within forty-
five days after system acceptance testing has been successfully concluded. Submissions shall also
include electronic versions of all documents submitted. Final payment for Contracted services shall
not be released by Floyd County until this documentation submittal has been successfully
completed by the Contractor and reviewed and approved by Floyd County’s Project
Representative and Consultant.
Comply


12.2 Workmanship

All workmanship shall be of the highest standard, in accordance with Industry-accepted
practices and the National Electric Code. Work areas shall be maintained in a neat, orderly
fashion. Work sites shall incorporate Contractor-provided trash containers and residue of the
work shall be discarded as the work is underway. All sites will be cleaned up at the end of each
work day, swept clean, tools picked-up, and walkways free of obstacles and obstructions.
Comply
The installation of audio, signal, data and control cables within equipment cabinets, enclosures,
racks and cable trays must be properly routed such that wires/cables do not cross over each
within cable bundles. Cables must be properly labeled, routed and secured. To the maximum
extent possible, cables carrying AC power, low-level audio, RF and digital signals must be
grouped separately.
Comply
All DC wiring, particularly those areas where battery terminals and power distribution bus bars
are located, must incorporate insulation barriers to prevent the accidental short- circuiting of
otherwise exposed conductors.
Comply
Floyd County’s Project Representative and Consultant shall have the ability to temporarily stop
work progress by the Contractor if workmanship falls below acceptable levels and shall have the
authority to require the Contractor to remove and/or correct all observed instances of poor wiring
practice, inappropriate use of installation materials and other obvious installation defects as a
result of apparent poor workmanship. Approval to resume installation work activities shall be
provided to the Contractor once agreement is reached in resolving observed workmanship
defects.
Comply
The determination of Contractor workmanship acceptability, as well as the suitability of any
proposed rework plans offered by the Contractor, shall remain with Floyd County’s Project
Representative and the Consultant.
Comply

13.0 Phasing/Implementation

13.1 Phasing of New Network

13.1.1 Contractor must prepare and submit a comprehensive migration plan that will prevent
disruption of communication on the existing analog conventional radio network and provide a
smooth transition to the new Project-25 digital voice radio network:
Comply
Please see the Migration Cutover Plan in Section 9.3 of this proposal.


A. Contractor must supply a sequence of events for the installation of the new
network showing any effect the different stages of installation may have on existing
systems. Any relocation or modification to existing equipment must be stipulated and
prior approval obtained from Floyd County’s Project Representative.
Comply
Please see the Migration Cutover Plan in Section 9.3 of this proposal.
B. Proposers shall provide a completion time period (in days) for the project, based on
Floyd County’s execution of a Notice to Proceed. Proposers shall provide a schematic
representation of the implementation process as well as a hypothetical migration plan.
These required proposal submittals will be used by Floyd County’s designee and
Consultant to evaluate the Proposer’s ability and understanding of Specification
requirements to perform this work in a manner that offers no disruption to ongoing public
safety communications operations.
Comply
Please see the Project Schedule in Section 9.6 of this proposal.
C. Contractor shall provide a time schedule for the training of system managers,
dispatchers, County Radio System Maintenance Personnel in addition to managers and
user personnel. Contractor will supply time schedules for the orderly transfer of
departments onto the new network and the estimated time period when the transfer
could be completed.
Comply;
Please see the Project Schedule in Section 9.6 of this proposal.
13.1.2 Contractor shall coordinate the orderly transfer of services to the new network only after
having successfully concluded equipment alignment and installation procedures, successful
completion of the network acceptance test and completion of manager, dispatcher, user and staff
training programs.
Comply
13.1.3 Contractor must not dismantle or modify the existing analog radio systems without prior
approval of Floyd County’s Project Representative. Some portions of the existing network
may remain operational after acceptance of the new system. Floyd County’s Project
Representative will notify the Contractor when elements of the old analog infrastructure
equipment may be reallocated to meet interoperability needs or otherwise can be
decommissioned.
Understood
13.1.4 Contractor shall assist Floyd County and all user agencies in preparing user talk
groups, initial priority levels and shall complete the necessary user equipment installation,
programming and record keeping, as required. This activity must be completed prior to service
cutover. All fleetmapping documentation will be surrendered to the County by the Vendor.
Comply


13.1.5 Prior to Contract execution, the Successful Proposer must commence negotiations with
Floyd County’s Project Representative and its Consultant to develop a comprehensive test and
acceptance plan that addresses, minimally, the following major functionality and operability
issues:
A. Transmitter Equipment
1. Provide RF power stage measurements at different levels of the transmitter

system such as transmitter, filters, combiner, cable, antenna, etc.;
Comply
2. Test R.F. components for specified insertion loss;
Comply
3. Test for proper frequency, modulation, digital signaling and stability;
Comply
4. Test and report of delivered audio quality and signal margins throughout
proposed service area, in all required configurations (portable in-vehicle, portable
on-street, portable in-buildings, etc.);
Question:
9. Section 13.1.5 A 4. Requires testing the reporting of delivered audio quality for all required
configurations, which include portable in-vehicle configuration. This requirement is not specified
in the RFP. Please remove the portable in vehicle requirement.
Response: The portable in vehicle requirement will be removed.
Comply
B. Receiver Equipment
1. Test of compliance to specifications of equipment provided;

Comply
2. Provide log of signal gain or loss to equipment within the receiver system such
as antenna, cable, preamp, splitter, or receiver antenna port;
Comply
3. Test of audio quality and level (reciprocal of that required for the transmit
path) of system balance;
Comply


C. Console Audio/System Controllers
1. Test of compliance to manufacturer’s published specifications of equipment

provided;
Comply
2. Test of audio quality and level;
Comply
3. Verification of network failure modes in response to forced failures of
individual communications/control lines and complete site failures complete
written explanation is required;
Comply
4. Verification of compliance to TIA/EIA Project-25 ISSI Standards that allow
for seamless interoperability with Project-25 radio networks fielded by other
manufacturers;
Comply
D. Dispatch Centers
1. Provide written results of testing of operational features per dispatch position;

Comply
2. Test system operation during simulated failures of system components i.e.
console electronics, power loss, etc.
Comply
E. Subscriber Equipment
A random field test of three different manufacturer's (non-Proposers) i.e. portable radio
devices (of varying tiers) shall be required to determine P-25 compatibility of Proposers
new 700/800MHz network. This test shall use approximately 10 portable devices per tier
per manufacturer, or a total of 120 portable non-Proposer portable radios tested. If ten
(10%) percent or more of each type or model of equipment tested fails to meet the
manufacturer's specifications, then the Contractor shall be required to perform a test of
one hundred (100%) percent of that type or model. If more than two units fail to perform
adequately, and the units are determined by the manufacturer to meet P-25 compatibility,
the Proposers network will be deemed non- P-25 compliant. All replacements for failed
units shall also be tested in the same manner as outlined above. All mobile radio
installations shall require 100% operational test verifications:
Question:
3. Is the P25 Compliance Assessment Program (CAP) test program acceptable for demonstration
that at least three different vendors’ radios work on our P25 Network?
Question:


10. Section 13.1.5 E requires the testing of 120 non-proposer P25 portable radios. Can this
requirement be waived for vendors who have met the P25 Compliance Assessment Program (CAP)
test program for their infrastructure?
Comply
Motorola fully supports and participates in the P25 Compliance Assessment Program (CAP) that
is being facilitated by the Department of Homeland Security DHS). This testing program requires
the testing of equipment in NIST assessed, DHS approved P25 Test Laboratories. Motorola had
one of the first DHS approved CAP laboratory test facilities. Verification of Motorola’s
compliance to the P25 CAP testing program is documented in the SDOCs and STR documents.
Official SDoCs and STRs for all of the documentation relating to Motorola’s P25 CAP tested
equipment is provided in Appendix A. This information is also available for download on the
Responder’s Knowledge Base (RKB) website www.rkb.us.
1. Verify compliance with vendor specifications for transmitter, receiver and
control circuitry;
Comply
2. Check for compliance with RFP requirements and originally proposed
functionality;
Comply
3. Check for proper user profile programming of equipment and operation on the
system;
Comply
4. Testing of supportive equipment, i.e., speaker/microphone, DTMF
signaling, chargers, batteries etc.
Comply
F. Contractor shall provide all test equipment, diagnostic services, documentation,
software, personnel, vehicles and other items as necessary to test the delivered and
installed radio network in accordance with the Contracted Test and Acceptance Plan,
inclusive of operational features, to complete a total system functional test.
Comply
G. Proposer shall disclose test procedures and equipment that will be used to verify radio
system coverage as specified in Section 7.0.
Comply
H. Proposers shall submit within their Proposal Submittal a sample test and acceptance
plan that is representative of the scope and complexity of the proposed radio system.
This plan must address those items described in Section 13.1.5, A – G.
Comply
Please see the Factory Acceptance Test Plan (FATP) in Section 6.0 of this proposal.


13.2 Implementation

13.2.1 Contractor is responsible for the provisions and cost of warehousing, insurance, storage
and security of radio network infrastructure and user equipment prior to and during the
construction and installation phases of the project.
Comply
Motorola will comply with the clarification that the words, “Per the terms in Section 1.23,
entitled Contractor’s Insurance” are inserted after the words “warehousing, insurance,”.
13.2.2 Contractor will assign a Project Manager as a single point of contact between Floyd
County’s Project Representative and the Contractor. Contractor’s Project Manager shall be
approved by the County or designee prior to assignment. Floyd County or its designee
reserves the right to require replacement of the Contractor’s Project Manager at any time
during the project. Contractor’s Project Manager must be resident within the County Monday
through Friday, during normal business hours and for the term of the Contract. Project
Manager may be required to remain in the area during periods of Installation and
Implementation failure, ATP and System Cut over, as required by Floyd County’s Project
Representative. The Proposal Response shall include pricing options for extending the Project
Manager’s term for periods of three total years and five total years.
Replace 13.2.2 with the following:
13.2.2 Contractor will assign a Project Manager as a single point of contact between Floyd
County’s Project Representative and the Contractor. Contractor’s Project Manager shall be
approved by the County or designee prior to assignment. Floyd County or its designee reserves the
right to require replacement of the Contractor’s Project Manager at any time during the project.
Contractor’s Project Manager must be resident within the County Monday through Friday,
during normal business hours and for the term of the Contract. Project Manager may be required
to remain in the area during periods of Installation and Implementation failure, ATP and System
Cut over, as required by Floyd County’s Project Representative. The Proposal Response shall
include pricing options for extending the Project/System Manager’s term for periods of one, two,
three, four and five total years.
Question:
27. What functions is the county looking for the Project Manager to fulfill?
Response: To manage the project for the Contractor.
Question:
28. Would a System Manager be desired versus a Project Manager?
Response: No.
Comply
13.2.3 Prior to installation of any portion of system, Floyd County, its designee and/or
Consultant must approve Contractor furnished detail drawings as specified in Section 12.0.
Comply


13.2.4 Each portion of the new network must be in compliance with those technical parameters
specified in the approved Testing and Acceptance plan.
Comply
13.2.5 Contractor must supply comprehensive training on user operation of portable radios,
mobile radios, control stations, and other user equipment as required by the Contract Contractor
must also supply comprehensive training for system diagnostics, management systems,
preventative and routine maintenance and system operation for System Managers, County Radio
System Maintenance personnel, and appointed staff.
Comply
13.2.6 Contractor is responsible for any site modifications required to accommodate infrastructure
equipment proposed for location in County-owned as well as in non County- owned properties.
Comply
13.2.7 Contractor shall provide technical support/engineering as required to modify existing FCC
licenses or to acquire additional licenses required to facilitate operation of the proposed digital
radio network. This activity shall include all FCC licensing application development, frequency
coordination and engineering fees.
Comply
13.2.8 Any modification or relocation of existing equipment will require prior approval by Floyd
County’s Project Representative. Contractor shall supply "as built" drawings and complete
written documentation of modifications or relocation to existing systems to facilitate maintenance
of this County-owned equipment in the future.
Comply

14.0 Warranty and Maintenance Guidelines

14.1 Warranty

14.1.1 Equipment Warranty
Proposer shall warrant all provided network equipment furnished as part of the Contract and
associated radio infrastructure, subscriber and related user equipment and software for a
period of one year, after the date of system acceptance. Warranty will commence at the time of
final acceptance and shall provide all labor and parts for maintenance and repair, including
preventive maintenance, of the network provided. All cost for the one-year warranty will be borne
by the Contractor. Floyd County desires Proposer to provide a cost proposal for a long term
(minimum five years) maintenance agreement through the major communications equipment
manufacturer for all system materials and functionality. Floyd County may elect to accept or
deny this additional cost maintenance agreement
Comply
Motorola’s offering exceeds the requirements specified in 14.1.1 above.
Warranty year support includes special services which ensure that the proposed system exceeds the
operational and functional expectations of the County. In addition to preventative maintenance,
technical support, advanced replacement, subscriber support and software updates, Motorola has


included:
Network Monitoring – 24x7 fault monitoring and diagnostics
Security Monitoring – 24x7 protection against security breaches
Security Update Service – pre-tested anti-virus and security updates
Dispatch Service – 24x7 call tracking and escalation
Motorola will also provide a technical resource with "hands on" experience on ASTRO P25
systems assigned to the Floyd County project. This individual will work with the local Motorola
Service Partner to ensure that all shop technical responsibilities are implemented correctly and
expediently.
The following conditions shall additionally apply:
A. Replacement parts must be of new or current manufacture and meet or exceed the
specifications of the original supplied equipment (OEM).
Comply
B. Contractor shall have qualified technicians available by telephone with one (1) hour
of reported service outage (24/7/365), and on-site, in response to a reported service
outage, within two (2) hour during normal working hours (8AM to 5PM Monday
through Friday and within one hour between the hours of 5PM and 8AM, weekends and
holidays). Major communications equipment manufacturer shall have a fully qualified,
staffed and equipped service facility located within Floyd County, Georgia during the
contract, warranty and maintenance agreement period.
Question:
29. Please confirm the required response times for normal business hours, 8AM through 5PM
Monday through Friday and for non-normal business hours, between 5PM and 8AM, weekends
and holidays.
Response: Contractor shall have qualified technicians available by telephone with one (1) hour of
reported service outage (24/7/365), and on-site, in response to a reported service outage, within
two (2) hours during normal working hours (8AM to 5PM Monday through Friday and within
three (3) hours between the hours of 5PM and 8AM, weekends and holidays).
30. Please confirm what holidays are being referenced.
Response: Floyd County holidays are: New Year's Day, Martin Luther King's Birthday,
National Memorial Day, Independence Day, Labor Day, Thanksgiving Day, Veteran's Day
(observed the Friday after Thanksgiving), Christmas Eve & Christmas Day.
The Proposal Response shall include pricing options by the Contractor for providing a qualified
technician to report directly to Floyd County, Georgia during normal working hours (8AM to
5PM Monday through Friday) for periods of one, two, three, four and five total years after the
date of system acceptance.
Comply with Clarification.


Per Addendum 1, in the event of a major system failure, Motorola will provide remote telephone
support within one hour of the initial call notification to Technical Support. Motorola will also
provide on-site field support within two hours of the initial call notification during normal
working hours (8am to 5 pm Monday through Friday) and within three hours between the hours
of 5 pm and 8 am, weekends and holidays.
Motorola will also provide a technical resource with "hands on" experience on ASTRO P25
systems assigned to the Floyd County project. This individual will work with the local Motorola
Service Partner to ensure that all shop technical responsibilities are implemented correctly and
expediently.
Motorola’s offering exceeds the requirements specified in 14.1.1 B above.

In addition to continuously monitoring your system, Motorola’s authorized service provider Coosa
Valley Communications will provide 7x24 local onsite support of the proposed system. In the
event that an incident cannot be remotely corrected, Motorola will dispatch the local on-call Coosa
Valley service technician to the site with the information of the severity of the outage. The service
technician will respond to the customer site based on pre-determined severity levels and response
times. Motorola maintains contact with the on-site service technician until the system is restored
and the case is closed.
Coosa Valley Communications is the largest and most experienced two-way communications
service provider in Floyd County and is located at 10 Bale Street in Rome, GA. They specialize
in the sale, installation and maintenance of radio communication networks, wireless broadband,
and 9-1-1 systems for Public Safety, Commercial, and Industrial users in the area.
As the authorized Motorola service facility in the Floyd County area for over 34 years, Coosa
Valley Communications is a certified Motorola Service Partner with two ETA certified
technicians supervised by an ETA certified Journeyman Technician who is currently completing
Motorola's P25 training. Two full-time installers perform mobile and fixed equipment
installations, along with tower, antenna, and transmission line installations.
For more detailed information, please refer to Subsection 9.4
Response default penalties:
In the event of default on the response time on reported service outages, the Contractor
agrees to pay Floyd County the following response penalties: Contractor shall pay $500
for each occasion that its fails to meet the response time obligation for a reported
infrastructure service outage. Contractor shall pay $1,000 per twenty-four hour period in
which a defective infrastructure site is not restored to operational status.
Question:
31. In the statement "…a defective infrastructure site is not restored to operational status." Please
define "operational status".
Response: Operational status as defined at the time of acceptance.
Comply
Motorola will comply with this clarification: Any liquidated damages assessed will be cumulative
and capped at $10,000.


Should any specific equipment item (such as a specific portable radio, repeater station,
station circuit board, power amplifier, etc.) fail three times during the warranty period,
Contractor will replace that equipment item and warranty the replacement for one
additional year from the time of replacement.
Comply
C. The Contractor must make available replacement parts for all Contractor-
manufactured components of the digital radio infrastructure for 10 years following
acceptance. Post-warranty replacement parts service for infrastructure equipment shall
be available within 24-hours of parts order replacement. Failure to provide parts for
contractor-manufactured items shall result in a 5% cost reduction penalty for each day
parts are delayed, capped to a maximum 100% cost reduction.
Comply
Motorola is committed to supporting the ASTRO 25 system platform for an extended period of
time. We fully comply with the 10-year parts availability requirement for all new Motorola-
manufactured ASTRO 25 network equipment supplied as part of this proposal. The platform life
cycle is expected to be supported for at least 25 years from its initial 2000 release, and in fact may
go beyond as new technologies are developed which are compatible with the ASTRO 25 platform.
During the product’s lifespan, Motorola will make investments to regularly refresh the underlying
technology to address product obsolescence. A primary goal of the technology refreshment is to
maximize backward compatibility of system’s functionality and major hardware components, thus
mitigating the need to replace the entire platform.
Certain system components are expected to undergo regular updates, while others are expected to
be available for 10 years or more from initial availability. Updates and replacements to the system
components are made available in system release updates.
Motorola expects to continue to support ASTRO 25 system releases and subsystem components
through at least the end of 2025. Although there is no planned end of life date for the ASTRO 25
platform, at least one year of advance notice will begin before cancellation. Access to replacement
parts for Motorola-manufactured infrastructure will continue for seven years from the date at
which new ASTRO 25 systems are no longer shipped.
Proposers shall provide, as part of Infrastructure Pricing, a list of quantities and costs for
recommended spares and specific diagnostic, test and repair equipment of Infrastructure
and major system components, including antennas and cabling. This list should be based
on the best knowledge and experience of the Proposer’s engineering, manufacturing and
service personnel. This price submittal shall be in compliance with the requirements
indicated by Section 16, Pricing.
Comply
D. The Contractor must guarantee the radio network’s operating software, inclusive of
user equipment software, for a one-year period following network acceptance. The
Contractor shall provide all software updates, at no additional cost, for the entire period
under which Floyd County has committed for Contractor-provided after- warranty
maintenance services. Contractor shall fix by either update or upgrade any and all known
software “bugs” to installed software even if such warranty period has expired.
Question:


32. Please supply a definition for the term "guarantee" as used in this paragraph.
Response: Installation of supplied software will cause no harm to operations. Should an
operational or functional defect occur as a result of newly-installed software, the Contractor shall
restore the radio network or equipment affected to the previous software level. This remedial work
would be completed at no additional cost to Floyd County.
Question:
33. Is it the intent of the statement, "Contractor shall fix by either update or upgrade…", that
Software, Software Installation and any required Hardware be supplied at no additional cost?
Response: The cost charged for software services of infrastructure systems must include all
necessary hardware to successfully utilize.
Comply
Motorola’s offering exceeds the requirement of this specification.
During the first year warranty period, Motorola has included the software, hardware and labor to
implement one upgrade bringing the system to the latest technology release.
The Contractor further guarantees that it has good title to any material and software supplied and
that it will defend Floyd County from any third party claims concerning such material or software
Comply
Motorola complies with the clarification that Motorola has the right to sublicense third-party
software but does not have title to it.
PATENT AND COPYRIGHT INFRINGEMENT:
Motorola will defend at its expense any suit brought against Floyd County to the extent it is based
on a third-party claim alleging that the Equipment manufactured by Motorola or the Motorola
Software (“Motorola Product”) directly infringes a United States patent or copyright
(“Infringement Claim”). Motorola’s duties to defend and indemnify are conditioned upon: Floyd
County promptly notifying Motorola in writing of the Infringement Claim; Motorola having sole
control of the defense of the suit and all negotiations for its settlement or compromise; and Floyd
County providing to Motorola cooperation and, if requested by Motorola, reasonable assistance in
the defense of the Infringement Claim. In addition to Motorola’s obligation to defend, and subject
to the same conditions, Motorola will pay all damages finally awarded against Floyd County by a
court of competent jurisdiction for an Infringement Claim or agreed to, in writing, by Motorola in
settlement of an Infringement Claim.
If an Infringement Claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its
option and expense: (a) procure for Floyd County the right to continue using the Motorola
Product; (b) replace or modify the Motorola Product so that it becomes non-infringing while
providing functionally equivalent performance; or (c) accept the return of the Motorola Product
and grant Floyd County a credit for the Motorola Product, less a reasonable charge for
depreciation. The depreciation amount will be calculated based upon generally accepted
accounting standards.
Motorola will have no duty to defend or indemnify for any Infringement Claim that is based
upon: (a) the combination of the Motorola Product with any software, apparatus or device not
furnished by Motorola; (b) the use of ancillary equipment or software not furnished by Motorola
and that is attached to or used in connection with the Motorola Product; (c) Motorola Product
designed or manufactured in accordance with Floyd County’s designs, specifications, guidelines or
instructions, if the alleged infringement would not have occurred without such designs,


specifications, guidelines or instructions; (d) a modification of the Motorola Product by a party
other than Motorola; (e) use of the Motorola Product in a manner for which the Motorola Product
was not designed or that is inconsistent with the terms of this Agreement; or (f) the failure by
Floyd County to install an enhancement release to the Motorola Software that is intended to
correct the claimed infringement. In no event will Motorola’s liability resulting from its
indemnity obligation to Floyd County extend in any way to royalties payable on a per use basis or
the Floyd County’s revenues, or any royalty basis other than a reasonable royalty based upon
revenue derived by Motorola from Floyd County from sales or license of the infringing Motorola
Product.
14.2 Maintenance

14.2.1 During the initial warranty period, the Contractor shall be responsible for:
A. Preventive maintenance of infrastructure and end-user equipment;
Comply
B. Repair maintenance of infrastructure equipment, inclusive of antenna systems;
Comply
C. Repair maintenance of subscriber and related user equipment;
Comply
D. Installation of mobile-mounted radio equipment.
Comply
14.2.2 Contractor-provided maintenance during the warranty period will be monitored by Floyd
County or its designee.
Understood
The Contractor must supply monthly service logs listing the site(s) where service is performed, the
equipment involved and service details. Failure of individual units, sub- assemblies and/or
components must be reported in writing to the County. This report must, as a minimum, include
unit identification (description and serial number), explanation and cause of failure and
corrective action taken. Contractor is responsible for all actions of its employees or
subcontractors. Any equipment failure(s) caused by any act or omission of Contractor's
employee or subcontractor shall be the responsibility of the Contractor, including any costs
associated with repair, even if such damage and repair is not to Contractor's equipment,
discovered after network installation and acceptance, and shall also be subject to unspecified
liquidated damages.
Comply
The Contractor shall submit a maintenance work plan that identifies the tasks required in
accordance with Section 14.2.1, a listing of Contractor supplied personnel and identification of a
single 24/7/365 contact point responsible for Contractor maintenance issues.
Comply


Please refer to Subsection 9.4 for resumes of Sub-Contractor supplied personnel.
Motorola’s offering exceeds the requirements specified in 14.2.2 above.
Motorola’s System Support Center (SSC) is the single point of contact for all service issues. With
one phone call to the SSC, the system response and restoration process begins immediately. This
ensures that local, trained and qualified technicians will arrive on location within hours to
diagnose and restore the communications network. In addition, Motorola will monitor your
system 24 hours per day, 7 days per week, 365 days per year without exception. Potential
network disruptions can be identified and often remotely diagnosed and fixed before there is any
impact to your communications system.
All required service logs and repair reports must be submitted to the County or its designee.
Comply

15.0 Radio Programming and Spare Parts Requirements

15.1 Radio Programming

15.1.1 Contractor shall assist Floyd County’s designee and various user agencies in determining
user identification and talk path assignments.
Comply
15.1.2 Contractor shall program all portable, mobile and control station radios, all network or site
controllers and all other equipment supplied by the Contractor to operate on the FCC- licensed
operating frequencies and the talk paths determined in Section 15.1.1, above.
Comply
15.1.3 Contractor shall prepare and furnish to Floyd County’s Project Representative "as
programmed" records for each radio (infrastructure & subscriber) placed on the system.
Comply
15.1.4 Contractor shall provide training for System Managers sufficient to permit Floyd
County designee, System Managers and County Radio System Maintenance personnel to add
users, create new or delete obsolete talk paths and to access all other system software
controlled features.
Comply


15.1.5 Provisions shall be incorporated into the system to allow the Contractor, from its Home
Office to remotely interrogate the operating system and provide software assistance if requested
by Floyd County designee, or System Manager. Access, for this purpose, must be secure and
under the control of the P-25 Project Manager.
Comply
15.1.6 Contractor must provide six sets of radio and equipment programming software,
appropriately equipped laptop computers, and all other support equipment and special cables
necessary to program each type of user equipment supplied by the Contractor.
Comply
15.2 Spare Parts

15.2.1 Contractor must maintain an initial stock of spare parts, as determined necessary, to
maintain all components of the network’s infrastructure for a one-year period. These spare parts
shall be located either at selected Floyd County radio infrastructure sites or at the
Contractor’s local-area Maintenance Service Station facility.
Comply
15.2.2 As spare parts are consumed in the course of routine or repair maintenance, the
Contractor shall immediately replenish its stock of locally housed spare parts, where necessary. A
report of the utilization frequency and rate of all spare materials shall be made available. If at any
time the Contractor is aware of any equipment repair or recall notifications the Contractor shall
notify the County by electronic and routine mail. Trends of unusual system or component failure
shall be brought to the attention of Floyd County by the Contractor.
Comply

16.0 Pricing Considerations

16.1 General Pricing Information

This infrastructure and subscriber equipment-pricing portion of this Specification is
developed as a guide for Proposers so that the necessary information is provided to Floyd
County, their designee and Consultant for it to conduct an accurate assessment of proposed cost.
This information is illustrative of the detail required for each infrastructure site, inclusive of
sites having only dispatch-related equipment. As this is a turnkey system, any pricing omission
of a scope that is normally considered part of a multisite or simulcast trunked radio system,
will be provided for by the Contractor at no additional cost to Floyd County.
Comply
Subscriber equipment (mobiles, portables and accessories) is intended to be purchased as
part of this Specification. Some or all user equipment purchases and quantities ordered
may be delayed or not ordered depending on Floyd County financing options and
capabilities. The pricing of this equipment for both initial and future purchases will
be considered in determining the most advantageous price. Floyd County shall perform a
life-cycle analysis in determining the best price-value.
Comply


In the case of manufacturers of low-tier Project-25 compliant subscriber (user)
equipment devices desiring to offer such equipment for consideration, Floyd County
welcomes such participation. This procurement, however, is structured for the
purchase of both infrastructure and user equipment from a turnkey provider.
Therefore, manufacturers of Project-25 compliant subscriber equipment shall have
entered into formal sales/service agreements with established infrastructure providers
(i.e., Motorola; Harris; EF Johnson, etc) for their equipment to be considered for this
procurement. Furthermore, such third- party equipment shall be proposed only by
those providers offering a responsive infrastructure proposal.
Comply
Proposals for subscriber equipment only shall not be accepted.
Comply

16.2 Site Modification Costs

16.2.1 Floyd County-Owned Sites
For equipment to be installed at Floyd County-owned sites which have requirements for site
preparatory work involving architectural, mechanical, electrical, civil or structural
construction modifications, a description and cost of the modifications required must
be provided by the Proposer for each individual named site.
Comply
16.2.2 Rental Sites
For equipment installed at rental sites which have requirements for site work
involving architectural, mechanical, electrical, civil or structural modifications in order
to meet the functional requirements stated herein, the Contractor shall be responsible for
all work. It is the Proposer’s responsibility to insure that the selected site can be
modified for the equipment selected to occupy that site.
Comply
The Proposer shall also provide the annual operating costs of any proposed rental
site, inclusive of space rental, antenna placement rental and utilities. Additionally, the
Proposer shall provide a letter for the Rental Site Owner that confirms the availability of
the necessary space to accommodate the proposed facilities and that such space has been
reserved for the full duration of the Proposal Evaluation and Contract Award Period.
Comply
16.3 Maintenance Costs

It is the intention of Floyd County to use County resources (County Radio
Maintenance Personnel) and rely minimally on outside contract labor, for maintaining its
infrastructure equipment and subscriber equipment.
Comply


An annual maintenance cost for each infrastructure-related site, to become effective
after expiration of the initial warranty period, must be provided. Total site maintenance
costs are to be subdivided by the individual major components groupings that comprise
each site. All site (backbone infrastructure) maintenance costs should be totaled.
Additionally, Proposers are required to provide the percentage of maintenance cost
escalation through the twentieth year of network ownership and to indicate their
methodology for determining the percentage cost escalation.
Question:
13. Can the County please clarify if they would like Emergency On-Site Response as well as
annual Preventive Maintenance included in the optional maintenance costs beginning in Year 2
after the First Year Warranty period?
Response: The same level of service included in the first year warranty period should be included
in the optional maintenance costs.
Comply
16.4 Pricing Summaries

Pricing Summaries for Infrastructure and Subscriber equipment shall be provided as part
of the Proposal Submittal.
Comply
16.5 Future Purchase Considerations

It is the intent of Floyd County to operate this new radio communications network
for, minimally, the next twenty years. As some portions of the equipment purchased may
only be available from one vendor, it is important that Floyd County receive
reasonable safeguards with regard to future pricing.
Comply
16.5.1 Immediate Future Discounts
Floyd County requires within the Proposal a certainty of continued purchase, at

the beneficial initial contract costs, of all equipment, components, parts, materials,
software and service agreements for a minimum of 5 years.
Comply
For all purchases within five (5) years after the network acceptance date, the
discount percentage received by Floyd County will be identical to the discount
percentages derived from list-price unit equipment costs and proposed unit costs. The
Proposer shall define the discount structure for radio infrastructure, subscriber
equipment, Contractor-furnished technical services as well as markup percentages used for
outside subcontractor services. The list unit price for equipment will be determined by the
manufacturer's published equipment list price, as delivered to their authorized sales agents,
at the time of actual purchase.
Comply


16.5.2 Purchase Price Discount Years 6 - 10
For years six (6) through ten (10) after the network acceptance date, Floyd
County’s discount from the manufacturer's published equipment list price, as
delivered to their authorized sales agents, shall be as follows:
Fixed Site Equipment
Microwave Related
Equipment
Console Equipment
Control Station
Equipment
%
Subscriber Equipment
Accessories
Spare Parts
Maintenance Agreement
Comply
16.5.3 Price Discount Years 11 - 15
For years eleven (11) through fifteen (15) after the network’s acceptance date,
Floyd County’s discount from the manufacturer's published equipment list price as
Fixed Site Equipment %
Microwave Related Equipment %
Console Equipment %
Control Station Equipment %
Subscriber Equipment %
Accessories %


Spare Parts _%
Maintenance Agreement %
Comply
16.5.4 Price Discount Years 16 - 20
For years sixteen (16) through twenty (20) after the network’s acceptance date,
Floyd County’s discount from the manufacturer's published equipment list price as
Fixed Site Equipment
Microwave Related
E i t
Console Equipment
Control Station
E i t
Subscriber Equipment
Accessories
Spare Parts
Maintenance Agreement
Comply
16.6 Infrastructure Pricing Analysis Worksheets

The following pricing worksheets are to be used as a guide to developing the
Infrastructure Price Submittal. These worksheets are indicative of the detail required and
may be amended or expanded as necessary. Proposers shall develop and submit
individual pricing sheets for each infrastructure site, inclusive of dispatch site locations,
for their Price Proposal to be considered responsive. Any omission or error in
developing the pricing proposal, as per Section 1.16 of this Specification, shall be
the sole responsibility of the Proposer (Contractor).
Comply


Simulcast System
Control Point #1:
N Li R E Mai
Equipment R C C C Cos
Network Controller $ $ $ $
Console/Audio $ $ $ $
Simulcast Sync. Eq. $ $ $ $
PCM Mux Equipment $ $ $ $
Receiver $ $ $ $
DVIU Interface $ $ $ $
System Manager $ $ $ $
Microwave Link $ $ $ $
Standby Battery Plant $ $ $ $
Emergency Generator $ $ $ $
Site Engineering $ $ $ $
Project Management $ $ $ $
Equipment $ $ $ $
i
Subtotal Equipment $
Subtotal Labor $
Total Equipment/Labor $
Total Annual Maintenance $
Comply
Simulcast System
Optional Control Point #2:
Number List Unit RFP Unit Extended Maintenance

Equipment Description Req’d Cost Cost Cost Cost
Network Controller 1 $ $ $ $
Console/Audio Control 1 $ $ $ $
Simulcast Sync. Eq. Lot $ $ $ $
PCM Mux Equipment Lot $ $ $ $
Receiver Voter/Selector Lot $ $ $ $
DVIU Interface Equipment Lot $ $ $ $
System Manager Terminal 1 $ $ $ $
Microwave Link Equipment 1 $ $ $ $
Standby Battery Plant System 1 $ $ $ $
Emergency Generator System 1 $ $ $ $
Site Engineering 1 $ $ $ $
Project Management 1 $ $ $ $
Equipment Installation Lot $ $ $ $
Subtotal Labor $
Comply


Simulcast System
Transmit/Receiver Site # :
N Li R E Mai
Equipment R C C C Cos
Transmitters $ $ $ $
Transmitter Antenna $ $ $ $
Combiner Package(s) $ $ $ $
Receiver Antenna $ $ $ $
Tower-top Preamp $ $ $ $
Multicoupler $ $ $ $
Receivers $ $ $ $
800 MHz Interop $ $ $ $
VHF Interop Links $ $ $ $
Protected Microwave $ $ $ $
Microwave Antenna $ $ $ $
PCM Mux Equipment $ $ $ $
Standby Generator $ $ $ $
Battery/Charger $ $ $ $
M/W Installation $ $ $ $
Site-Civils $ $ $ $
Equipment Shelter $ $ $ $
Tower $ $ $ $
Shelter Installation $ $ $ $
Project Management $ $ $ $
System Engineering $ $ $ $
Subtotal Labor $
Comply

16.7 Subscriber Equipment Pricing

Floyd County envisions several tiers of portable and mobile radio units for use by the
various public safety and non-public safety agencies. Those non-public safety users having
minimal interoperability needs, such as the Water Department, may benefit from lower-
tiered, less costly radios having smaller talk group capacities and a limited list of feature
options. Public Safety agencies, however, may require highest-tier devices capable of
voice encryption, telephone interconnect calling, private call, GPS location, status
messaging and other specialized features.
Comply
Proposers shall develop cost proposals for low, mid and high-tier radio products using
the following general format:
Comply


High-Tier Portable
1. At least 250 modes/talk groups/channels

2. 700/800MHz operation
3. Multi-line alpha-numeric LCD text display
4. Radio/ Network status icons
5. 9-button keypad
6. Private/Individual Call
7. DES/AES voice encryption
8. IMBE vocoder
9. Emergency Button
10. Programmable option buttons
11. Talk group scan
12. System Scan
13. Intrinsically Safe
14. Integrated voice/data capability
15. Wide range of optional accessories
Comply
Mid-Tier Portable
1. At least 120 modes/ talk groups/ channels

2. 700/800MHz operation
4. Radio/Network status icons
5. 3-button keypad
8. IMBE vocoder
9. Emergency Button
11. Talk group scan
12. System Scan
Comply


Low-Tier Portable

2. 800MHz operation
3. Single-line alpha-numeric LCD text display
5. No keypad
6. IMBE vocoder
7. Emergency Button
10. Limited list of optional accessories
Comply
High-Tier Mobile Radio

2. 700/800MHz & VHF (150-170 MHz) operation
3. Remote Control Head/ Rear Mount Configuration
6. 9-button keypad
9. IMBE vocoder
10. Emergency Button
12. Talk group scan
13. System Scan
Comply
Mid-Tier Mobile Radio

2. 700/800MHz
3. Remote Control Head/Rear Mount Configuration


6. 9-button keypad
9. IMBE vocoder
10. Emergency Button
12. Talk group scan
13. System Scan
Comply
Low-Tier Mobile Radio
1. 800MHz Operation
2. Front-Mount Package
4. Two-Line alphanumeric display
5. Network/Radio Icons
6. IMBE vocoder
8. Emergency Button
9. Limited range of optional accessories
Comply
The following illustrates the approximate quantities, types and tiers of subscriber
equipment that could potentially be used on the P-25 Digital Voice Radio Network:
Police Departments
• High Tier Portables

• Mid Tier Portables
• High Tier Mobiles
• Mid Tier Mobiles
• Control Stations
Comply


Fire Departments
• High Tier Portables (submersible)

• Mid Tier Portables (submersible)
• High Tier Mobiles
Comply
Emergency Medical Services
• High Tier Portables

• Mid Tier Portables
• Low Tier Portables
• Mid Tier Mobiles
• Low Tier Mobiles
Comply
Additionally, Proposers shall prepare a detailed optional equipment catalog that
describes the full range of options available for all Tiers and indicated portable and
mobile radio configurations. The submitted catalog shall include list prices and the
proposed discount percentage-reduced initial purchase price.
Comply


16.8 Proposal Authorization Form

(To be submitted with each Price Proposal)
I (or we) do hereby declare that I (or we) have carefully examined this RFP Specification
and the annexed Addenda numbered , and I (or we) have a clear understanding of said
Specifications, and shall provide the required communications equipment and the
necessary permits and authorizations, tools, machinery, apparatus, and other means
of construction, and to furnish all labor, materials, and services specified in the Contract
or called for in the said Specifications (including all taxes/fees) necessary for the
completion of the work described herein.
Respectfully submitted,
By:
Authorized Signature Title
Business Name Business Address
Telephone Number Date
Comply


Attachment A
Floyd County Interoperability Matrix

Comply


Floyd County Georgia Request for Proposal Specifications
P-25 Digital Public Safety Radio Network


Attachment B
Floyd County EOC/911 Center Floor Plan

Comply




Attachment C
Floyd County Critical Buildings Requiring Coverage
Question:
14. In regards to Attachment C, Floyd County Critical Buildings Requiring Coverage, has the
County already reached consent with the respective building owners to install in-building
amplification systems? Also, will the County provide an escort for the surveying of these
buildings?
Response: The County has not reached consent with the building owners and will not provide an
escort for the surveying of these buildings. However, the County will assist in providing contact
information of the respective building owners.

Comply


Floyd Co Crtical Facilities
Agency Address City Zip TYPE

Rome Middle 1020 Veterans Mem Hwy Rome 30161 School
Coosa High School 4454 Alabama Highway Rome 30165 School
Armuchee Elementary 5075 Martha Berry Hwy Rome 30165 School
Pepperell High 3 Dragon Dr Lindale 30147 School
Pepperell Elem 270 Hughes Dairy Rd Lindale 30147 School
Pepperell Middle 200 Hughes Dairy Road Lindale 30147 School
South East Elementary 1400 Crane St Rome 30161 School
East Central Elementary 1502 Dean Ave Rome 30161 School
West Central Elem 402 Lavender Rome 30165 School
North Heights Elem 26 Atteiram Dr Rome 30161 School
St Mary's 401E 7th St Rome 30161 School
Montessori School 165 Dodd Blvd Rome 30173 School
Unity Christian School 95 Burton Rd Rome 30161 School
Darlington School 1014 Cave Springs Rd Rome 30147 School
Darlington Middle School 1014 Cave Springs Rd Rome 30147 School
Model Elm 3200 Calhoun Hwy Rome 30161 School
Georgia School for Deaf 232 Perry farms Rd Cave Spring 30124 School
Cave Spring Elementary School 13 Rome Rd Rome 30161 School
Model Middle 164 Baron Rd Rome 30161 School
Northwest Georgia Tech 1Maurice Culberson Dr. Rome 30147 College
Berry College 2277 Martha Berry Hwy Rome 30149 College
Ga Highlands College 3175 Cedartown Hwy Rome 30147 College
Shorter University 315 Shorter Ave Rome 30161 College
Alto Park 528 Burnett Ferry Rd Rome 30165 Shelter
Forum Civic Center 2 Government Plaza Rome 30161 Shelter
Glenwood Primary 75 Glenwood School Rd Rome 30149 Shelter
Floyd Co Transitional Acada 1910 Morrison Rome 30161 Shelter
Floyd Co Tech High School 100 Vocational Drive Rome 30161 Shelter
Elm St 8 Elm St Rome 30165 Shelter
Coosa Middle 212 Eagle Drive Rome 30165 Shelter
Armuchee Middle and High 4203 Martha Berry Hwy Rome 30105 Shelter
Anna K Davie 310 Nixon Ave Rome 30161 Shelter
Main Elementary 3 Watters St Rome 30161 Shelter
West End Elementary 5 Brown Fox Rome 30165 Shelter
Model High 3252 Calhoun Hwy Rome 30161 Shelter
North Broad Baptist Church 1309 North Broad ST Rome 30161 Shelter
First Baptist Church of Rome 100 East 4th Ave Rome 30161 Shelter
New Antioch Baptist Church 4553 Calhoun Rd Rome 30161 Shelter
Floyd County Baptist Ass 300 Chatillon Dr Rome 30161 Shelter
First Assembly of God 3330 Callier Springs Rd Rome 30161 Shelter
First Baptist Cave Spring 4 Cedartown St Rome 30161 Shelter
Trinity United Methodist 606 Turner McCall Rome 30161 Shelter
Hollywood Baptist Church 112 Lombardy Way Rome 30161 Shelter
Cosmopolitan United Methodist 109 Fincher St Rome 30124 Shelter
Cave Spring United Methodist 32 Alabama St Cave Spring 30124 Shelter
Rome High School 1000 Veterans Mem Hwy Rome 30161 Shelter


Star House 212 1/2 North Broad Rome 30161 Shelter
Open Door Home Boys 792 John Davenport Dr. Rome 30165 Shelter
Open Dorr Home Girls 5 Leon Street Rome 30161 Shelter
Greenwood Homes 21 Widgeon Way Rome 30161 Shelter
Salvation Army 317 East Main Rome 30161 Shelter
Calvary Baptist Church 101 Broadus Rd Rome 30161 POD
Georgia Highlands College 3175 Cedartown Hwy Rome 30161 POD
Georgia School for the Deaf Perry Farm Rd Cave Spring 30125 POD
Rome/Floyd Recreation Authority 1 Shorter Ave Rome 30161 POD
New Armuchee Baptist 5385 Martha Berry Hwy Rome 30165 POD
Second Ave Baptist 823 E 2nd Ave Rome 30161 POD
West Rome Baptist Church 610 Shorter Ave Rome 30161 POD
Rebbecca Blaylock Day Care 500 Cedar Ave Rome 30161 Daycar
Tallatoona-Floyd Early Childhood Dev 309 Reservoir Street Rome 30161 Daycar
Lisa 's Daycare 14 Gore Drive Rome 30161 Daycar
North Rome Christian Learning Center 1929 North Broad Street Rome 30161 Daycar
Cave Spring Day Care Center 10A Georgia Ave Cave Spring 30124 Daycar
Just Kids Learning Center 1010 N 5th Ave Rome 30161 Daycar
Winthorp Academy 10 Hwy 411 East Rome 30173 Daycar
Rebecca Blaylock West 608 Graham St Rome 30165 Daycar
Reach for the Satrs 201 East 19th St Rome 30161 Daycar
My Little World 62 Wax Rd Se Silver Creek 30173 Daycar
Cave Spring Day Care Center 10-A Georgia Ave Cave Spring 30125 Daycar
Childrens Academy 4 Colonial Drive Rome 30161 Daycar
Small Wonders Learning Center 3890 Rockmart Hwy Silver Creek 30173 Daycar
Kiddie Corral 408 Grover Street Rome 30161 Daycar
First Baptist Church of Rome 100 East 4th Ave Rome 30161 Daycar
Kid's Stop learning Center 2 Mathis Dr Rome 30161 Daycar
Kid's Stop learning Center 1700 Dean Ave Rome 30161 Daycar
Kid's World Learning Center 3700 Martha Berry Hwy Rome 30161 Daycar
Kid's World Learning Center 108 John Maddox Dr Rome 30161 Daycar
Wee Care Daycare 141 East 14th St Rome 30161 Daycar
Lil Miracles 202 Lavendar Dr Rome 30161 Daycar
North Rome Christian 1929 N Broad Rome 30161 Daycar
Northside Preschool and Early Learning 75 North Floyd Park Armuchee 30165 Daycar
Our Little World 1709 Maple ST Rome 30161 Daycar
Super Kids Early Learning 100 Huffaker Rd Rome 30161 Daycar
Tender Loving Care Daycare 9 S 4th St Lindale 30147 Daycar
Toddlers Inn 203 Division St. Rome 30161 Daycar
Wiggles and Giggles 16 O'Neil St Rome 30161 Daycar
Beverly Healthcare 1345 Redmond Rd Rome 30165 Nursing Home
Sunbridge at Mt Berry #2 Three Mile RD Rome 30149 Nursing Home
5th Ave Nursing Home 505 North 5th Ave Rome 30161 Nursing Home
Chulio Hills Nursing Home 1170 Chulio Rd Rome 30161 Nursing Home
Hospice Care 540 Broad St. Suite B Rome 30161 Nursing Home
Evergreen Health Care 139 Moran Lake Rd Rome 30161 Nursing Home
Golden Living Center 1345 Redmond Rd Rome 30161 Nursing Home
Winthrop Manner 12 Chateau Dr. SE Rome 30161 Nursing Home
Grace's Home Two 5 Raintree Silver Creek 30173 Nursing Home


Etowah Landing Care and Rehab 809 South Broad Rome 30161 Nursing Home
Golden Living Center 1345 Redmond Circle Rome 30165 Nursing Home
Summit Health Care 2 Three Mile Road Rome 30165 Nursing Home
Rome Fire Training Center North Ave Rome 30161 Fire
Cave Spring Fire Dept 123 Fincher St Cave Spring 30124 Fire
Rome Fire Dept 617 w 1ST St Rome 30161 Fire
Rome Fire Dept station 2 1601 Cave Spring St Rome 30147 Fire
Rome Fire Dept Station 3 411 E 12th St Rome 30161 Fire
Rome Fire Dept Station 4 3 Wilshire Road Rome 30161 Fire
Rome Fire Dept Station 5 750 John Davenport Rome 30165 Fire
Rome Fire Dept Station 6 621 Burnett Ferry Road Rome 30165 Fire
Rome Fire Dept Station 7 85 Woods Road Rome 30105 Fire
Rome Fire Dept Station 8 90 Little Texas Valley Road Rome 30172 Fire
Rome Fire Dept Station 9 152 Burlington Rome 30173 Fire
Rome Fire Dept Station 10 1522 Wax Road Rome 30165 Fire
Ga Forestry Commission Wilshire Rd Rome 30161 Fire
Ga District Forestry 3086 Martha Berry Blvd Rome 30165 Fire
US Marshalls 600 East 1st Rome 30161 Police
FBI 600 East 1st Rome 30161 Police
Sheriff's Office 3 Gov Plaza Rome 30161 Sheriff
Cave Spring Police Dept 10 Georgia Ave Cave Spring 30124 Police
Floyd County Jail 2526 New Calhoun Hwy Rome 30161 Jail
Floyd Co Prison 329 Blacks Bluff Rd Rome 30161 Prison
Floyd County Work Release Center 324 Blacks Bluff Rd Rome 30161 Work Release Center
Floyd Medical Center 304 Turner McCall Blvd Rome 30161 Hospita
Redmond Regional 501 Redmond Rd Rome 30165 Hospita
North West GA Regional Hos 1305 Redmond Circle Rome 30165 Hospita
Floyd Co Public Health 6 E 12th St Rome 30161 Health Dept
Floyd EMS Admin/Communication 500 Riverside Parkway Rome 30161 EMS
Floyd EMS 1207 Martha Berry Blvd Rome 30165 EMS
Floyd EMS 101 B Elliott Dr Rome 30165 EMS
Floyd EMS 11 Hwy 411 Rm 237 Rome 30161 EMS
Floyd EMS 1933 North Broad St Rome 30161 EMS
Redmond EMS Dispatch 100 John Maddox Dr Rome 30165 EMS
Redmond EMS Station 1 18 Redmond Rd Rome 30165 EMS
Redmond EMS Station 2 304 Russell Field Rd Rome 30165 EMS
Redmond EMS Station 16 123 Fincher St Cave Springs 30124 EMS
Recycle Center 405 Watters St Rome 30161 Recycle
City of Rome Filter Plant Blossom Hill Rome 30161 Water Treatment
Federal Building 600 East 1st Rome 30161 Gov
Rome City Hall 601 Broad St Rome 30161 Gov
Rome Transit 168 North Ave Rome 30161 Gov
Rome Filter Water Filter Plant Blossom Hill Rome 30161 Gov
Landfill 433 Walker Mtn Road Rome 30161 Gov
Waste Water Treatment Facility 212 Blacks Bluff Rd Rome 30161 Gov
Sarah Hightower Library 205 Riverside Drive Rome 30161 Gov
Rome Housing Authority 800 N 5th Ave Rome 30161 Gov
Cave Spring City Hall 10 Georgia Ave Rome 30124 Gov
Floyd County Gov Bldg 12 4th Ave Rome 30161 Gov


Floyd County Courthouse 3 Government Plaza Rome 30161 Gov
Cave Spring Water Dept 3 Georgia Ave Cave Spring 30124 Gov
Cave Spring Rehab Center 7 Georgia Ave Cave Spring 30124 Gov
Talmadge Gymnasium 14 Georgia Ave Cave Spring 30124 Gov

Rome City Police Training Center 2626 Callier Springs Rome 30161 Gov
Floyd PD/ Rome PD/ EMA/E911 5 Government Plaza Rome 30161 EOC
Floyd Co Extension Office 12 E 4th Ave Suite 107 Rome 30161 Gov
Floyd Co Water Department 217 Calhoun Ave Rome 30161 Gov
Floyd Co Public Works 337 Blacks Bluff Rd Rome 30147 Gov
Rome City Public Works Vaughn Drive Rome 30161 Gov
Russell Regional Airport 304 Russell Field Rd Rome 30165 Airport
Rocky Mtn./ Oglethorpe Pow Big Texas Valley Rd Rome 30165 Power Plant
Plant Hammond 5963 Alabama Hwy Rome 30165 Power Plant
Untied States Post Office 5 Mill Street Cave Spring 30124 Post office
United States Post Office 361 Burlington Drive Shannon 30172 Post Office
United States Post Office 4565 Rockmart Rd Silver Creek 30173 Post Office
United States Post Office 4000 Alabama Hwy NW Rome 30165 Post Office
United States Post Office 502 Park Ave Lindale 30147 Post Office
US Army Reserve 209 Public Affairs 2405 Redmond Circle Rome 30161 Gov
US Army Reserves 342 AG Detach 2405 Redmond Circle Rome 30161 Gov
National Guard 340 Wilshire Rd, Rome 30161 Gov
First Baptist Church of Lindale 9 Park Avenue Lindale 30147 Church
Pleasant Valley South Baptist Church 702 Pleasant Valley Rd. SE Silver Creek 30173 Church
F&P Georgia Mfg. Inc. 88 Enterprise Drive Rome 30161 Industrial
Pirelli Tire LLC 2 Industrial Blvd Rome 30161 Industrial
Kellogg's 452 Old Lindale Road SE Rome 30161 Industrial
Sara Lee 10 Darlington Drive SW Rome 30161 Industrial
Southeastern Mills 100 East 1st Ave Rome 30161 Industrial
Steel King 30 Industrial Blvd SE Rome 30161 Industrial
Packaging Products Corporation 2 Superior Drive SE Rome 30161 Industrial
Zartic Inc. 438 Lavender Dr. NW Rome 30165 Industrial
Bekaert Corporation 301 Darlington Drive Rome 30161 Industrial


Attachment D
Floyd County Subscriber Radio Quantities per Agency

Comply


Floyd County Radio Inventory
Portable Radios Mobile Radios TYPE Radio
Floyd County 10 14 NPS
Floyd County Public Works 73 14 NPS
Floyd County Magistrate Court 5 0 NPS
E911 9 0 NPS
Floyd County Police Dept 10 10 PS
Floyd County Police Dept (SWAT) 13 PS/Encrypted
Floyd County A/C 7 3 NPS
Floyd County Sheriff's Office 16 44 PS/25 Encrypted Portables
Floyd County Sheriff's Office (SWAT) 8 PS/Encrypted
Floyd County EMA 25 10 NPS
Floyd County Water 28 0 NPS
Rome Police Dept 12 85 PS
Rome Police Dept (SWAT) 10 PS/Encrypted
Rome Fire Department 50 40 PS/Intrinsically Safe/20 Pagers
Rome Water Dept 22 0 NPS
Rome Public Works 85 0 NPS
Cave Spring Fire 15 8 PS/Intrinsically Safe
Cave Spring Police 10 4 PS
Cave Spring Public Works 9 6 PS
Rome Floyd Metro Task Force 20 0 PS/Encrypted
Redmond EMS 18 7 PS
Redmond EMS (SWAT) 3 PS/Encrypted
Floyd EMS 20 11 PS
Rome City Schools 11 0 NPS
Floyd County Schools 25 0 NPS
Rome Floyd Rec Authority 26 2 NPS
Facilities Maintenance 12 0 NPS
District Attorney"s Office (SWAT) 1 PS/Encrypted
TOTAL 99 34 134
Non Public Safety 42 43 47
Public Safety 56 30 87


Floyd County Radio Inventory (continued)
Base Stations
Rome Fire Dept 10
Redmond EMS 4
Floyd EMS 6
Floyd SO 14
Floyd A/C 1
Magistrate Court 1
Rome Water 4
Floyd Water 2
Floyd Prison 2
Cave Spring Fire 1
Cave Spring Police 1
Cave Spring PW 1
Rec Authority 1
Floyd EMA 1
Mobile Repeaters
30


* crftA*o*
Motorola December 15, 2010
1301E. Algonquin Road
Schaumburg, lL 60L96-1078
United States
RE: Support Guarantee
Dear Sir and/or Madam,
Ceragon Networks, lnc. guarantees that it will provide manufacture support to Floyd County, Georgia
directly in the event of any conditions or problems which can't be remedied by Motorola, or in case
Motorola defaults on its warranty and/or maintenance agreements.
Please let me know if you require anything else. Thank you for this opportunity to be of service.
s Courtney
or of Strategic
Section 4. Customer References
Please see attached customer references.

RFP# 101216
December 16, 2010
Customer References 4-1


RFP# 101216
December 16, 2010
4-2 Customer References

Cobb County Board of Commissioners
140 N Marietta Parkway, Marietta, GA 30060
Synopsis
Since 1993, Cobb County has utilized a 3 site, 21 channel Motorola
SMARTNET system to provide communications to all City and County agencies
throughout Cobb County. The County began their migration path to their new
P25 system by deploying a 5-site, 18-channel ASTRO 25 system alongside the
existing analog system and then created interoperable talkgroups between the
two systems at the console; therefore enabling direct interoperability between
the two systems. 2,500 County users exist on the new Project 25 system
while the remaining 2,000 City users exist on the SMARTNET system, yet all
users benefit from the increased functionality of interoperability.
• All County users share the system with all Cites in the County providing
seamless interoperability.
• Project 25 system deployed in an overlay configuration with existing analog
technology using shared interoperable talkgroups on both systems.
• Motorola was the prime integrator providing new site construction,
radio integration and CAD in a single contract.
• The Motorola site development team overcame many site development
and implementation challenges represented by a site that was located in a
National Park.
Motorola System Description

• 800 MHz Frequency Band
• 5 Sites
• 18 Channels
• 2500 Subscribers
• 34 Gold Elite Consoles
Contract Date: October 2003 Acceptance Date: July 2006
Customer Contact:
Tony Wheeler Tracy Roberts
9-1-1 Director
770.590.5711
System Manager
770.499.4167
B
m
twheeler@cobbcounty.org troberts@cobbcounty.org
Reference Sheet
Gwinnett County, Georgia
Gwinnett County Police Department
770 Hi Hope Road, Lawrenceville, GA
Synopsis
Gwinnett County had operated one of the oldest
analog trunked systems in America for 20 years
and purchased the new digital P25 system via an
RFP, awarded price of $33M. The County, with a
population of over 800,000 wanted their new system
to provide in-building coverage throughout the County
and to support a total of 2000 voice and data users.

• 10 Sites
• Simulcast
• Project 25
• IV&D Data Technology
• Trunked Voice Technology
Contract Date: September 2006

Completion Date: March 2008
Customer Contact:
Paula Criss
Information Technology
Phone: 770-822-7020
B
m
Paula.Chriss@gwinnettcounty.com
Reference Sheet
Hall County, Georgia
Hall County 911
470 Cresent Drive, Gainesville, GA
Synopsis
Hall County is in northeast Georgia with a population of
189,000. The county purchased their system via an RFP
Motorola, MA/Com and EF Johnson responded, awarded
price of $13.4M This was the county’s first trunked radio
system and was designed to provide in building portable
coverage throughout the County with over 800 users.

• 7 Sites
• Simulcast
• Project 25

Completion Date: March 2007
Customer Contact:
Marty Nix
Phone: 770-654-9369
mnix@hallcounty.org
B
m
Reference Sheet
SEGARRN- Southeast Georgia Regional Radio System
Chatham County
124 Bull Street, Savannah, GA
Synopsis
This system began with the vision of the jurisdictions of the coastal
Georgia area collaborating to develop a regional network to serve
the critical needs of all the citizens of the area. They used their
plan to apply for Federal Grants to offset the cost of constructing
the network and have been successful in deploying it in phased
since 2007. This multi-Jurisdictional regional radio system designed
to cover Savannah, Chatham County Effingham County, Bryan
County, Liberty County, Glynn County and ultimately the entire
GEMA Region 5. It supports over 1500 users today.

• 8 Sites
• Simulcast
• Project 25
Contract Date: June 2008

Completion Date: December 2009
Customer Contact:
Lewis Leonard
Information Technology
Phone: 912-652-7344
B
m
llleonar@chathamcounty.org
Reference Sheet
City of Atlanta
Atlanta Police Department
226 Peachtree Street, Atlanta, GA
Synopsis
The City of Atlanta with a population of over
540,000, purchased their new P25 System via an
RFQ/RFP, awarded price of $41M. This replaces
their old analog Motorola trunked system which had
been in service for nearly 20 years. The new system
was designed to improve city wide in-building
coverage, ATP included testing in 350 buildings.

• 9 Sites
• Simulcast
• Project 25
Contract Date: December 2007

Completion Date: June 2009
Customer Contact:
George Turner
Chief of Police
Phone: 404-614-6544
B
m
rjstanionis@atlantaga.gov
Reference Sheet
Walton County, Georgia
Walton County 911
1425 South Madison, Monroe, GA
Synopsis
Walton County is in east Georgia and has a population of
87,000. The P25 system was purchased to replace the
County’s previous Motorola SMARTNET Trunked system
that was 17 years old. The new system was designed
to provide better county wide portable coverage and to
also support their mobile data needs.There are currently
over 800 users on the system. Recently, Walton has
partnered with Green and Oconee Counties to add
six 700 MHz sites in their counties to form a regional
network. The new sites are currently undergoing testing.

• 4 Sites
• Simulcast
• Project 25

Completion Date: September 2009
Customer Contact:
Wendra Williams
Phone: 770-464-1915 B
m
Reference Sheet
Houston County, Georgia
200 Carl Vinson Parkway, Warner Robins, GA 31088
Synopsis
Houston County has a 4 Site, 11 Channel, 6.5 IV&D, Project 25,
800 MHz network; 10 Position Gold Elite Radio Console System
integrated with a 12 Position Vesta Pallas System. They have
approximately 350 XTL 5000s with Data option; 400 XTS 5000s
and 160 ML850s using the IV&D as their data pipe. They use OSSI
CAD and Records. They run mobile to mobile messaging, CAD,
Records, Field Reporting, AVL and GCIC / NCIC over their IV&D
network. Three of the eleven channels can pass data.

• 4 Sites
• 11 Channels
• Integrated Voice & Data Technology
• 10 Position Gold Elite Radio
Console System
• 12 Position Vesta Pallas System
Customer Contact:
Tim Ealer
System Manager
Office: 478-542-9916
B
m
Cell: 478-447-0696
Reference Sheet
DeKalb County, Georgia ASTRO 25 System
DeKalb County, Georgia Police Communications
1960 West Exchange Place, Tucker, GA 30084
Agencies and Jurisdictions Involved in this Project

Munincipalities - Decatur, Avondale Estates, Dunwoody, Stone
Mountain, Lithoinia, Chamblee, Clarkston.
Fire, Sheriff, Marshall, DA, Animal Control, Parks & Recreation,
Roads & Drainage, Sanitation, DeKalb Medical Hospital
Synopsis
DeKalb County, GA is one of the largest counties in
Georgia and has a population base of over 800,000 people.
More than 5000 radios are supported by the system. IV&D
was purchased but not currently in use.

• 11 Microwave and 9 RF Sites
• Simulcast
• Project 25
• Dispatch Integration
• HPD Data Technology
• CAD Vendor: Interact
Contract Date: May 2006 Installation Date: June 2009

Completion Date: May 2010
Customer Contact:
Darryl Scott
Radio/Telecommunications Manager
Phone: 404-379-5303
B
m
djscott@co.dekalb.ga.us
Reference Sheet
Tallahassee - Leon County P25 System
City of Tallahassee; Leon County; Leon County Sheriff
300 S. Adams Street, Tallahassee, Florida 32301

All City / County local government • City Police and Fire County Sheriff
EMS and Volunteer Fire • Florida State University • Tallahassee Community College
Florida A&M University Police
Synopsis
System replaces current Motorola SmartNet six-site simulcast system.
The goal was to upgrade the radio network capable of meeting current
and future public safety and other communications needs, both as
to reliability and functionality. Motorola’s system is a state-of-the-art
Project 25 system. The robust design increases the coverage footprint
improving communications reliability. Sites are designed to operate
under battery power for eight hours, plus generator backup power. All
agencies received new subscribers that provide the capability to add
advanced features as needed. The system totally integrates all public
safety agencies in Leon County including the local University Police
Departments onto one system.

• Trunked Voice Technology • 8 Sites
• CAD Vendor: Motorola • Simulcast
• 800 MHz Frequency Band • Project 25
• Automatic Vehicle Locator (AVL) • Dispatch Integration
• Service Population: 172,000

Completion Date: November 2009
Customer Contact:
Ron Wostel, City of Tallahassee
800 MHz System Manager
Phone: 850-544-4868
B
m
Ron.Wostel@talgov.com
Reference Sheet
Polk County, Florida
Polk County Department of Public Safety Emergency Management Division
202 Bartow Municipal Airport, Bartow, Fl 33830
Synopsis
The Polk County Astro P25 system is comprised
of 9 simulcast sites with 13 channels and 2 ASR
sites. The simulcast network delivers countywide
mobile and portable coverage for all public safety
and public service providers in the county. The
ASR sites allow for optimum coverage and direct
interoperability with Polk Aviation and neighboring
Hardee County. The network is supported by
a robust microwave network and includes 20
console positions and over 4000 subscriber radios.

• Simulcast
• 700 & 800 MHz Frequency Band
• 11 Sites (9 simulcast, 2 ASR)
• Project 25

Completion Date: August 2010
Customer Contact:
Ben Holycross
Radio Systems Manager
Phone: 863-559-6902
B
m
Fax: 863-519-3929
benholycross@polkfl.com Reference Sheet
Nassau County, Florida
96135 Nassau Place, Yulee, FL 32097
Synopsis
Nassau County implemented a 5 Site, 5 Channel, Project
25, 800 MHz simulcast trunking network. The ASTRO 25
solution delivered by Motorola also included microwave,
MOSCAD, consoles and all subscriber equipment.

• ASTRO 25 Simulcast
Trunking System
• Project 25
• 5 Sites
• 5 Channels

Completion Date: December 2006
Customer Contact:
Sam Young
Fire Chief
Office: 904-491-7525
B
m
Cell: 904-753-1134
Reference Sheet
Marion County, Florida
2630 SE 3rd Street, Ocala, FL 34471
Synopsis
800 MHz P25 Simulcast Public Safety
Communications System. Contracted on
August 1, 2005 and accepted on February
2007.

• Project 25
• 5 Site Simulcast
• 12 Channel
• 2,600 Subscribers
Contract Date: August 2005

Completion Date: February 2007
Customer Contact:
Karl Oltz
Communications Director
Marion County Sheriff’s Office
B
m
Phone: 352-671-8460
Reference Sheet
Lake County, Florida
Lake County Department of Public Safety
315 W. Main St., Suite #411, Tavares, FL 32778
Synopsis
The Lake County Intergovernmental County-wide Radio
system is a Motorola ASTRO P25 digital integrated voice
and data system consisting of 3 Simulcast Cells (Zones)
composed of 18 sites and 36 channels total. Each cell
has 12 channels with a mix of 700 MHz and 800 MHz
channels. Users in one cell can talk to anyone in another
cell and have the capability of seamlessly roaming from
cell to cell achieving a county-wide network.

• 700 and 800 MHz Frequency Band
• Simulcast • Project 25
• 3 Simulcast Cells (Zones) composed of 18 sites and
36 channels total. Each cell has 12 channels.
• IV&D Data Technology • Trunked Voice Technology

Completion Date: October 2009
Customer Contact:
Gregory Holcomb
Division Director/E911 Coordinator
Communications Technologies
B
m
Phone: 352-253-1818
Fax: 352-253-1815 Reference Sheet
GHolcomb@lakecountyfl.gov
Regional Customer Reference
System Name: City of Independence, Missouri
Customer Name: 223 N Memorial Drive
Independence, MO 64050
Customer Contact: Jim Lenchioni

• Independence Police Department • Independence Fire Department
• Independence Health Department • Independence Public Works
• Independence Power & Light • Independence Water Polution Control
• Independence Water Department • Independence Parks Department
• United States Army at Lake City • Central Jackson County Fire
Synopsis
The City of Independence chose a Motorola 700 MHz Astro 25 Digital Trunk Radio System
to support communications for all City Departments. This was the first 700 MHz Project 25
general use system implemented in the United States. The City implemented a Master Site
Controller designed to not only serve the existing six-site, seven-channel simulcast network
for the City, but to extend the technology and capabilities of this controller and their network
to neighboring government entities, regional and state partners. A number of municipali-
ties, public safety agencies, fire districts and EMS operations have either joined the existing
Independence network or intend to connect to the Master Site Controller or expand on the
network to provide for their specific communications requirements and proliferate regional
interoperability throughout the MARC (Mid America Regional Council) eight county region.

• 700 MHz Frequency band • 6 Sites
• Simulcast • Simulcast
• Project 25 • 8 Channels
• Trunked Voice Technology • 1300 Users
Contract Date: September 2005 Completion Date: September 2006
Customer Contact:
Jim Lenchioni
Technology Coordinator
B
m
Phone: (816) 325-7314
jlencioni@indepmo.org
Lucas County Radio System
Lucas County Sheriff’s Office
2144 Monroe Street, Toledo, OH 43604
Synopsis
The City of Toledo partnered with Lucas County in April 2005 to
migrate the City’s analog 800 MHz system to the new countywide
Digital P25 platform.
The system has 3100 radios in operation with 8 dispatch centers

and 53 Operator Positions. An IV&D and POP25 upgrade was
completed in Spring 2010.
One year following system acceptance, Lucas County chose to

expand their service maintenance contract to incorporate an onsite
Motorola Service Manager responsible for maintaining the system.

• 12 Sites
• Simulcast
• Project 25
• CAD Vendor: PRC
Contract Date: May 2005

Completion Date: January 2008
Customer Contact:
Mike Koontz
Director
Phone: (419) 213-6550
B
m
Mkoontz@co.lucas.oh.us
Reference Sheet
Austin/Travis County Regional Radio System
1006 Smith Road, Austin, TX 78721
Representative List of Users

100+ Agencies in Greater Austin area and along the Texas-Mexico border, including:
• City of Austin • Travis County • Texas DPS • Austin Energy
• University of Texas • City of Pflugerville • City of Round Rock • City of Cedar Park
• City of Leander • Middle Rio Grande Development Council • Williamson County
Synopsis
The Austin/Travis County Project 25 Regional Radio System serves the greater Capital
Area Planning and Council of Governments in central Texas as well as the Middle Rio
Grande Development Council that includes nine Counties along the Texas Mexico border.
The urban areas have extensive portable in-building coverage with several large 700/800
MHz simulcast subsystems and repeater sites. VHF Project 25 trunking that is used along
the border region provides mobile coverage.
Motorola was the prime contractor and provided: the radio system design, the radio
system infrastructure, site improvements, mobile and portable radios, and dispatch
consoles. Subcontractors were used for the civil construction, including construction
of the tower, equipment shelter, as well as provisioning and microwave connectivity.
Motorola directly supervised the subcontractors efforts, and installed, programmed,
optimized and tested the network. The network has been accepted and continues to
expand.

• 700/800/VHF ASTRO 25 Project 25 Trunked System
• 22+ Simulcast Transmitter Sites
• 15+ Trunked Repeater Sites
• 100+ Dispatch Operator Positions
• 10,000 Project 25 Mobiles and Portables
Operational Status: Accepted, continuing to expand
Customer Contact:
Chuck Brotherton
Emergency & Wireless Communications Manager
Phone: (512) 854-4895
B
m
Fax: (512) 854-4786
Charles.Brotherton@ci.austin.tx.us Reference Sheet
STARCOM21, Illinois State Police
531 Sangamon Avenue, Springfield, IL 62702

• Illinois Toll Highway Authority • Illinois Secretary of State
• Illinois Commerce Commission • Illiniois Emergency Management Agency
• Illinois Department of Transportation • Illinois Department of Revenue
Synopsis
STARCOM21 is a Project 25-compliant ASTRO 25 SmartZone
system operating on the 700/800 MHz frequency bands and
serving the state of Illinois. The system consists of over 197
simulcast and IR sites, three zones, and integrates Computer
Aided Dispatch (CAD) technology from Printrak.

• 700/800 MHz Frequency Band • Project 25
• Simulcast & IR Sites • 197+ Sites
• CAD Vendor: Printrak
• Dispatch Integration: Gold Elite Consoles
• Service Population: 14 Million
• 1,800 Subscriber Radios

Completion Date: February 2007
Customer Contact:
Gary Cochran
Assistant Bureau Chief of Communications
Phone: 217-558-6363
B
m
Gary_Cochran@isp.il.us
Reference Sheet
Calhoun County, Alabama
507 Francis Street West, Jacksonville, AL 36265

• Calhoun County, AL • Talladega County, AL
Synopsis
Calhoun County has an ASTRO 25 (Rel 7.4) system (7 sites, 18
channel Simulcast system with 2 repeater sites). There are two
separate and independent Simulcast over-lay systems. One for the
Tone Alert Radio System (TARS) to alert in home monitors in the
event of a chemical disaster from CSEPP. The second is for alerting
the MOSCAD sirens which send out live voice traffic through the
siren PAs. The system has 11 separate dispatch locations with a total
of 30 MCC7500 console OP positions. All sites are connected using 6
GHz microwave.

• ASTRO 25 Digital • Project 25
Trunking System • Simulcast
• 800 MHz Frequency Band • 11 Dispatch Centers
• 7 Sites • 31 Operator Positions
• 18 Channels • 4000 Field Radios
• 1 Simulcast Cell • 95% Portable Coverage
• 112,000 Population Served in 6 dB Buildings
Contract Date: August 2006

System Acceptance: February 2007
Customer Contact:
Jerry Jackson
EMA Director
Phone: 256-435-0540
B
m
Reference Sheet
Section 5. ASTRO 25 System Description
This document provides a general overview of the mission critical ASTRO® 25
simulcast trunked system proposed by Motorola for Floyd County, Georgia. The
proposed system consists of equipment capable of supporting eight radio
infrastructure sites. The primary offering is an eight-site, 10-channel simulcast cell
with the option of changing Rocky Mountain to a five-channel ASTRO 25 repeater
site. Included are six (6) console positions at Floyd 911 and five (5) console positions
at Floyd Back-up 911. ISSI is also included or if so desired Floyd can select Multi-
zone instead at no additional cost. The System Topology Figure 5-1 below gives a
high level overview of the system.
Figure 5-1: System Topology

RFP# 101216
December 16, 2010
ASTRO 25 System Description 5-1

Each remote simulcast transmitter site is composed of a radio subsystem containing
GTR 8000 simulcast base stations, the appropriate antenna-combining equipment,
redundant site routers and Ethernet switches, and a Global Positioning System (GPS)
time and frequency reference in order to keep the network timing synchronized.
Each ASTRO 25 repeater transmitter site includes a radio subsystem containing GTR
8000 simulcast base stations, the appropriate antenna-combining equipment and a site
router.
The following sections will describe the ASTRO 25 system components in detail.
5.1 ASTRO 25 Fixed Network Equipment Design
5.1.1 Zone Core

The ASTRO 25 Zone Core is the main control point for the proposed
communications system. The Zone Core contains the computing backbone for the
system and all the components necessary for controlling voice calls and data
messages within the proposed system. In addition, the Zone Core provides the
hardware and software components used for network management and system
configuration.
The system architecture is designed with inherent fault distribution, ensuring that a
single point of failure will not cause the complete disruption of communications. The
ASTRO 25 architecture ensures that voice operation is maintained despite any single
component failure anywhere on the network. In the case of a fault, the system can
reroute the IP voice and data packets among the various redundant router
configurations, and notify the supervisor / network management terminal of the fault.
Redundant Zone Controllers (Sun Netra T5220 Server)

The proposed system offers redundant Zone Controllers. This platform is deployed
with the Sun Netra T5220 servers (shown in Table 5-1).
The two Zone Controller servers contain the Zone Controller and Network
Management applications. The T5220 supports a multi-threading environment with
up to 32 simultaneous processes. This platform enables multiple applications to
reside on the same platform. T5220 specifications are provided in Table 5-1.

RFP# 101216
December 16, 2010
5-2 ASTRO 25 System Description

Table 5-1: Sun Netra T5220 server specifications
Type Netra T5220 Specifications

Height 87.1mm (3.43 in.) 2RU
Width 445mm (17.52 in.)
Depth 501mm (19.72 in.)
Depth (including power supply 526mm (20.71 in.)
handles)
Weight 17.5 kg (38.5 lbs.)
Operating Temperature 5° C to 40° C (41° F to 104° F), short-term -5° C to
55° C (23° F to 131° F)
Non-operating Temperature -40° C to 70° C (-40° F to 158° F)
Operating Relative Humidity 5-85%, non-condensing
Operating Altitude Up to 3,000m (9,850 ft.) at 40° C
Non-operating Altitude Up to 12,000m (40,000 ft.)
Operating Input Voltage Range 100-240V AC
DC Power -48V DC or -60V DC
AC Power 100-240V AC, 50-60 Hz
Power Supplies Two 1+1 redundant DC or AC hot-swappable 650W
power supply units
Power Consumption 346W, Max @ 110V
Input Current Drain 4.5A @ 100-120V/2.25A @ 200 - 240V
Each Netra T5220 server is equipped with 32 GB RAM, two 300 GB hard drives, and
redundant, hot-swappable power supplies. The hard drives are configured in a high-
availability arrangement so if one of the two drives fails, the server can operate on the
remaining drive until the defective drive is replaced.
5.1.1.1 Zone Core LAN Switch Configuration

The Zone Core equipment includes a set of HP ProCurve 2610-48 series switches
(shown in Figure 5-2 that are the aggregate of all the Ethernet interfaces for all
servers, clients, and routers at the Zone Core. Additional HP ProCurve 2610-24 LAN
switches are also used for remote site access aggregation and in other capacities
within the proposed ASTRO 25 system, including at the Prime Site, the Primary and
Backup Dispatch Centers, and each of the remote RF Sites.

RFP# 101216
December 16, 2010

Figure 5-2: HP ProCurve Switch 2610-48
Core Routers
The core routers perform the routing control of audio, data, and network management
traffic in and out of the zone, replicating packets while achieving the fast access
levels required by real-time voice systems. To increase availability, two core routers
are used. The Zone Core audio, data, control, and network management equipment
interfaces to the remote RF Sites via the remote site aggregation LAN switches,
through the core router.
Gateway Routers
Redundant gateway routers are used for devices that forward packets beyond their
local LAN. To provide increased availability, gateway routers are provided in a
redundant configuration.
ISSI.1 Gateway System
Motorola’s ISSI.1 Network Gateway Application is a connectivity solution that

utilizes an available ASTRO 25 Zone Controller Site Link to connect a P25 Inter RF
Subsystem Interface (ISSI) over an Ethernet transport medium, to another network
with another ISSI gateway similarly connected. Each ISSI.1 Network Gateway
Application allows 27 simultaneous trunked calls between systems and 60
interoperability talkgroup pairs.
ASTRO 25 System Licenses

Many ASTRO 25 system features are offered through a licensing structure giving the
County the ability to purchase only those features that are needed. The proposed
system is configured with sufficient licenses for up to 2,000 individual radio user IDs
to accommodate for current and future expansion needs. The County may purchase
additional licenses for individual radio user IDs beyond the 2,000 that are included.
The Automatic Vehicle Location solution provided includes licenses for GPS
tracking of up to 100 individual radios. The MCC7500 console system includes
licenses for the eleven (11) proposed consoles and four (4) console expansion
licenses. The system is licensed for the following applications which meet the
requirements of the RFP: Unified Network Configuration, User Configuration
Manager, Unified Event Manager, Network Fault Manager, Zone Historical Reports,
and Radio Control Manager.
RFP# 101216
December 16, 2010

5.1.1.2 Zone Core Equipment at Floyd 911
The following lists major components at the Floyd 911 center:
♦ Redundant T5250 Zone Controllers and Network Management Servers
♦ Redundant LAN Switches
♦ Redundant Core Routers
♦ Redundant Gateway Routers
♦ Network Firewall and Firewall Management Server
♦ GPS sourced NTP for syncing all Ethernet-based computer systems
♦ MOSCAD Network Fault Management (NFM) Server
♦ (2) Network Management Workstation
♦ (2) links of Monitored Hot Stand-by Microwave Radio in a loop configuration
♦ (1) ISSI.1 Gateway system including:
ISSI.1 Gateway Application Server
ISSI.1 Firewall and Ethernet Switch
ISSI.1 Site Gateway for WAN access to the City of Chattanooga Zone Core
♦ Packet Data Gateway
Zone Core Equipment at City of Chattanooga 911

♦ (1) ISSI.1 Gateway system including:
ISSI.1 Gateway Application Server
ISSI.1 Firewall and Ethernet Switch
ISSI.1 Site Gateway for WAN access to the Floyd County Zone Core
5.1.2 Integrated Voice and Data (IV&D) System Description

IV&D is Motorola’s integrated mobile data and is supported on the ASTRO® 25,
Project 25 trunking system. Motorola’s ASTRO 25 IV&D capability enhances the
Project 25 system by adding packet data capability to subscriber units. This system
enhancement will provide voice and data communications throughout the County
service area, without the extra expense of installing and maintaining separate systems
for voice and data. The IV&D enhancements to the ASTRO 25 voice system included
in Motorola’s proposal are Automatic Vehicle Location (AVL) and Over-the-Air
Programming (Programming Over P25 – “POP25”). A number of optional data
centric applications such as Data Message Support (Text Messaging) and Over-the-
Air Rekeying (OTAR) of encryption codes can be added if desired.

RFP# 101216
December 16, 2010

5.1.2.1 RF Infrastructure
ASTRO 25 IV&D uses the same infrastructure components needed for Project 25
voice communications. The simulcast and repeater sites that form the backbone of the
County communications network will support both voice and data communications.
This will allow the system to allocate resources to voice and data communications,
depending on user demands. Allowing sites to exchange both voice and data
information ensures that system resources are used as efficiently as possible. This
capability also minimizes the number of separate components that the system will be
required to support.
5.1.2.2 Subscriber Units

ASTRO IV&D features a single subscriber capable of supporting both voice and data.
As described in the section on subscriber units, this feature is available on selected
Motorola mobile and portable radios. These next generation subscribers are data
capable and only require a software option and data cable to implement ASTRO 25
IV&D.
5.1.2.3 GPRS Gateway Support Node (GGSN)

The GPRS Gateway Support Node (GGSN) is a special purpose router that provides
various services in support of trunked data operation. Among those are separation of
IP address spaces between the trunked radio system network and external customer
networks, DHCP address management, and tunneling of radio system packets into
and out of customer networks.
The GGSN was first developed to provide General Packet Radio Service for GSM
cellular subscribers. The device is used in the ASTRO 25 system to provide
connectivity between the trunked radio system network and other private or public
networks. The proposed system requires only one GGSN (per system).The GGSN
interfaces between the Motorola radio network and Customer Enterprise Networks
(CEN). It is used to “tunnel” datagrams from a CEN(s) to the appropriate PDG,
which ultimately passes the datagram on to a specified subscriber unit operating on
the “closed” Motorola radio network. A GGSN does the following:
♦ Isolates the Motorola radio network IP address plan from the IP plans of any
CENs to which it enables a connection.
♦ It either sources or provides access to DHCP services.
♦ It can support VPN connections into external networks.

RFP# 101216
December 16, 2010

5.1.2.4 Packet Data Gateway (PDG)
The County’s trunked IV&D system enhancement contains a product new to the
trunked system, called a Packet Data Gateway (PDG). PDG is made up of two
separate functional elements – a Radio Network Gateway (RNG) and a Packet Data
Router (PDR). Those familiar with other Motorola wireless data systems may
recognize an “RNC” and a “WNG” in the descriptions of the RNG and the PDR.
There are similarities between the new devices and the old, but there are also
substantial differences. The Packet Data Gateway (PDG) interfaces between the
GGSN and the Motorola Radio Network. See the following sections for more details.
5.1.2.5 PDR
The PDR is one of two components in the PDG. It interfaces with the GGSN and its
home RNG as well as other zones’ RNGs and controls the routing of data messages
between serving RNGs and the GGSN. Additionally, based on home zone mapping,
the PDR maintains a database of data-capable SUs.
The PDR provides a packet data “home” for all subscriber units that have been Home
Zone mapped to that zone for voice operation. It sends packets to, and receives
packets from, any of the RNGs in the system. It also operates with the GGSN to
terminate the trunked system’s IP address space and provide address translation
between the trunked system’s IP network and external networks.
PDR technical specifications are:
♦ MCG MCP750 processor card
♦ Linux operating system, SC/EM PDG environment
♦ Hard drive/RAID, CDROM
♦ 100baseT Ethernet
5.1.2.6 Applications Utilizing the IV&D (mobile data) System

Enhancement
ASTRO 25 Outdoor Location Solution (AVL)

The ASTRO 25 Outdoor Location Solution is a resource tracking solution that uses
Global Positioning System (GPS) satellites to provide operators with the ability to
locate and track OUTDOOR personnel and assets.
AVL provides location information of properly equipped subscriber radios while they
are located outdoors. Motorola’s AVL solution provides a server receives disparate
GPS protocols in & translates them into a unified protocol out to your application.
AVL programming documentation is also included, which provides 3rd party vendors
the ability to process the AVL information within their application.

RFP# 101216
December 16, 2010

Unlike public network solutions, Motorola’s AVL allows Floyd County to further
utilize their ASTRO 25 IV&D system to enhance officer safety and increase their
operational efficiencies.
POP25
POP25 is an application that is enabled by the ASTRO 25 integrated data pipe.
Motorola is committed to delivering a solution to help customers maintain their
ASTRO 25 Trunked Integrated Voice and Data subscribers such that the customer
can update specific radio information via the ASTRO 25 trunked data infrastructure.
POP25 is designed to allow a radio manager expert to use a traditionally styled
Customer Programming Software (CPS) solution installed on a computer attached to
the radio IP infrastructure to read and write a codeplug from an ASTRO 25 trunked
data-capable fielded radio via the ASTRO Common Air Interface (CAI). The
technician can update any of the CPS based radio configuration information and send
the updated codeplug back to the radio over the ASTRO 25 trunked data system.
For radios purchased initially without POP25, a FLASHport upgrade is available to
add the capability.
OTAR (available, but not included)

OTAR of AES encryption keys requires the ASTRO 25 integrated data functionality
on the trunked infrastructure. Secure users operating on the proposed ASTRO 25
trunked system via IV&D and OTAR are able to deliver new AES encryption keys
“over the RF channel” instead of manually re-keying through a Key Loader. As it is
generally recommended to perform periodic updates to the encryption keys for
security reasons, this option works well for large numbers of encrypted subscribers
that require updated keys. OTAR is compatible with subscriber radios equipped with
the AES OTAR option.
On December 16, 2003, the U.S. National Institute of Standards and Technology
(NIST) and Canada’s Communications Security Establishment (CSE) issued a joint
statement accepting AES OTAR as a FIPS-approved mode of operation. Motorola
offers both AES and AES OTAR, now validated to FIPS 140-2.
5.1.3 ASTRO 25 Prime Site Design

The Prime Site acts as a control and digitized audio center for the simulcast
subsystem. The Prime Site will be at the proposed Mount Alto site. Motorola has also
included an option for a redundant Prime Site to be located at the Floyd 911 Center.
The microwave links route IP packets containing control and audio information from
the Prime Site to each simulcast remote site.

RFP# 101216
December 16, 2010

5.1.3.1 Redundant GCP 8000 Controller
The redundant GCP 8000 controller is designed for use in ASTRO 25 trunking
systems. The GCP 8000 controller provides call processing and acts as a site link
between the simulcast subsystem and the Zone Controller. The GCP 8000 is capable
of supporting up to 30 channels and up to 15 simulcast sub-sites. The GCP 8000
controller communicates with interconnected ASTRO 25 infrastructure elements,
such as the GTR 8000 base radio subsystem and the GCM8000 comparator, which
are also designed to be Project 25 compliant.
The GCP 8000 controller will be implemented in a fully redundant configuration of
with two controllers. The redundant (standby) controller automatically takes over site
link or site control operations when the active GCP 8000 controller has failed.
Communications between the active and standby controllers are configured through
an Ethernet link. Channel status information will be kept consistent between the
active and standby site controller to assure that accurate channel capability
information will always be sent to the zone controller.
5.1.3.2 Redundant Prime Site Routers

The Prime Site router provides a WAN interface that carries all of the traffic between
the Prime Site to the Zone Core including voice, control, and network management
traffic. The router provides direct IP packet network management connectivity for the
remote sites to the Zone Core as well as:
♦ Traffic prioritization – the router applies the correct prioritization marking to the
packets leaving the site.
♦ Fragmentation – the router fragments large IP packets as necessary.
♦ Dynamic Host Configuration Protocol (DHCP) service – this service allows the
technician with a properly configured computer running Windows to connect to
the LAN at the site.
Used with the NMS, the Prime Site Router provides a proactively managed system
and a means of receiving and reporting failure alarms, all of which increase router
availability. Motorola has designed this system with redundant Prime Site routers.
5.1.3.3 GCM8000 Channel Comparators

The GCM8000 comparator is a band-independent device that acts as a subsystem-
wide signal collector, voter, and distributor. The GCM8000 comparator is designed
for use in ASTRO 25 IP Simulcast trunking systems. With multiple base stations
operating on the same frequency, it is possible for multiple RF sites to receive a
single field unit transmission.

RFP# 101216
December 16, 2010

The GCM8000 compares the various voice traffic signals and interprets and selects
the best audio samples and assimilates an enhanced audio signal for simulcast
broadcasting. By simultaneously transmitting the enhanced audio signal from
multiple sites within the system, both coverage and signal quality are improved.
5.1.3.4 Redundant Prime Site Ethernet LAN Switches

A pair of interconnected LAN switches is required to connect GCM8000 comparators
and GCP8000 controllers to the Prime Site router. Two switches are used at the site
to increase availability, and they are interconnected via Gigabit Ethernet trunks. Each
of the two Prime Site controllers is connected to its own switch. Therefore, if one
switch should fail at least one controller will have connectivity.
5.1.3.5 TRAK 9100 Time and Frequency Standard

The Prime Sites includes a GPS-based time and frequency standard that provides a
frequency/timing device for synchronized simulcast transmissions. In addition, the
GCM8000 comparator will receive timing information from the GPS. Each Simulcast
Remote Site will also utilize a GPS to provide the frequency/timing data needed to
allow synchronization of simulcast transmissions.
5.1.3.6 Simulcast Prime Site Equipment at Mt. Alto

♦ Redundant GCP 8000 Prime Site Controllers
♦ (10) GCM8000 Comparators
♦ (2) S6000 Zone Core Access Routers
♦ (2) Prime-site LAN Switches
♦ TRAK 9100 GPS with Redundant Rubidium Oscillators
♦ MOSCAD NFM SDM 3000 Alarm and Monitoring RTU
♦ (2) S6000 Sub-site Access Routers
♦ (2) Ethernet Sub-site fan-out LAN Switches
♦ (2) Links of Monitored Hot Stand-by Microwave Radio in a loop configuration
5.1.4 RF Site Overview

Motorola’s design includes either eight simulcast RF sites or seven simulcast RF sites
with one ASR (hybrid) site as shown in Table 5-2. One RF site will be co-located
with the Prime Site at Mount Alto.

RFP# 101216
December 16, 2010

Table 5-2: Simulcast RF Sites
Site Name Site Type Latitude Longitude Chnls

1 Mount Alto Simulcast Prime/RF Site 34-14-1.01N 85-13-54.7W 10
2 Fouche Gap Simulcast RF Site 34-18-56N 85-18-32W 10
3 Cave Springs Simulcast RF Site 34-06-25.56N 85-19-30.43W 10
4 Leonard Rd Simulcast RF Site 34-07-52.65N 85-11-54.87 10

5 Hillindale Simulcast RF Site 34-12-20.64N 85-06-35.08W 10
6 Shannon AT&T Simulcast RF Site 34-20-18.6N 85-02-59W 10
7a Rocky Mtn Sim Simulcast RF Site 34-21-2.8N 85-17-33.9W 10
7b Rocky Mtn ASR ASTRO 25 Repeater Site 34-21-2.8N 85-17-33.9W 5
8 Blossom Hill Simulcast RF Site 34-15-56.2N 85-09-50.63W 10
5.1.4.1 Redundant Remote Site Routers

Remote Site Routers provide an interface that routes all of the IP network traffic to
and from the Prime Site for communication with the Zone Core. The Site Routers
provide the following function for the network management packets:
♦ Layer 3 routing which restricts local traffic from accessing the Microwave system
and forwards important voice and data information to the prime site
♦ DHCP service: This service allows the technician with a properly configured
computer running Windows to connect to the LAN at the site.
Used with the system’s Network Management, the Remote Site Router provides a
proactively managed system as well as a means of receiving and reporting failure
alarms.
5.1.4.2 Ethernet LAN Switches

The simulcast sub-site LAN switch performs two main functions at the simulcast
remote site. The switch provides a 10BaseT LAN interface for the GTR Expandable
Site Subsystem and a 10BaseT port for the site router. The switch also provides a port
for interfacing MOSCAD.
The service technicians using CSS software use a switch port to gain access at the site
to service the site and access the system’s GUIs to maintain the system. DHCP
service allows the technician with a properly configured computer running Windows
to connect to the LAN at the site. The site router will assign the computer running
Windows an IP address that will allow the computer access to the ASTRO 25
network.

RFP# 101216
December 16, 2010

5.1.4.3 GTR 8000 Expandable Site Subsystem (ESS)
The GTR 8000 ESS is a self-contained RF site in a single rack. Each ESS provides
the radio frequency (RF) transmitter/exciter/power amplifier, receiver, multicoupler,
transmitter combiner, and networking (LAN) equipment for up to six channels within
a single rack. Each Simulcast Remote Site will be configured with two GTR 8000
Expandable Site Subsystem racks, the channels will be split into an odd/even
configuration. Then, when the County decides to add additional channels, two more
radios can be added to the existing ESS racks.
5.1.4.4 TRAK 9100 Time and Frequency Standard

Each simulcast RF site will house a GPS-based time and frequency standard to
provide the critical frequency/timing data needed to allow synchronization of
simulcast transmissions.
5.1.4.5 Antenna System

Each site will include a Transmit and Receive antenna and distribution system.
Mount Alto will also include an additional 800MHz Transmit distribution system and
a VHF antenna system, for the ITAC repeaters / EMS alerting repeater and Fire
paging/alerting repeater, respectively.
Motorola proposes to relocate and narrowband the County’s existing VHF MTR2000
and re-use the duplexer currently utilized for Fire paging and communications.
5.1.4.6 Co-located Simulcast and Conventional Site RF Equipment at

Mount Alto
♦ (2) Sub-site LAN Switches
♦ Redundant GGM8000 Sub-site Gateways
♦ (2) GTR8000 ESS cabinets containing
(10) GTR 8000 Base Stations
(2) Six-channel Transmit Combiners
(1) Transmit antenna and distribution network with Reflected Power
Monitoring system
(1) eighteen-channel Receiver Multicoupler system
♦ (1) Dual Diversity Tower Top Amp (TTA)
♦ (1) Receive antenna and distribution network
♦ (6) GTR8000 Conventional Analog Repeaters
♦ (1) Six-channel Transmit Combiner and antenna distribution network

RFP# 101216
December 16, 2010

♦ (1) Relocated MTR2000 VHF Repeater
♦ (1) VHF antenna and transmit / receive duplexer network
♦ (1) -48VDC Rectifier Plant with N+N redundancy and Batteries
5.1.4.7 Remote Simulcast Site Equipment

♦ TRAK 9100 GPS with Redundant Rubidium Oscillators
♦ (2) Sub-site LAN Switches
♦ Redundant GGM8000 Sub-site Gateways
♦ (1) Link of Monitored Hot Stand-by Microwave Radio
♦ (2) GTR8000 ESS cabinets containing
(2) Six-channel Transmit Combiners
Monitoring system
(1) Twelve-channel Receiver Multicoupler system
5.1.4.8 ASTRO 25 Site Repeater (ASR) Equipment

♦ GGM8000 Gateway
♦ (1) Link of Monitored Hot Stand-by Microwave Radio
♦ (1) GTR8000 ESS cabinet containing
(1) Six-channel Transmit Combiner
Monitoring system
(1) Six-channel Receiver Multicoupler system

RFP# 101216
December 16, 2010

5.1.5 MCC7500 ASTRO 25 Dispatch Console
To take full advantage of all the capabilities of the ASTRO® 25 trunked digital voice
system, and to support the wide variety of dispatch needs, Motorola offers the
MCC7500 IP console system. The MCC7500 console subsystem is tightly integrated
to the ASTRO 25 digital voice system. The MCC7500 is our ASTRO 25 IP console,
and the most advanced offering in Motorola’s line of radio dispatching products. The
MCC7500 is a state-of-the-art console system that will be installed in accordance
with recognized industry standards of police and fire dispatch centers. The new
console system will meet public safety dispatching needs for the County.
The various hardware elements that which comprise the dispatch console are
described in the following sections.
5.1.5.1 Personal Computer (PC)

The dispatch console uses a customized Motorola-certified PC running the Microsoft
Windows operating system. The PCs used in ASTRO 25 systems have a mini-tower
form factor.
5.1.5.2 Voice Processor Module (VPM)

The Voice Processor Module (VPM) is a device that combines the functions of a
voice card, encryption card, and a general purpose input/output module in an MCC
7500 Console subsystem. The VPM provides the necessary interfaces to connect
analog devices to the MCC 7500 digital console and it is responsible for audio
routing between the dispatch operator, peripherals, and the local network. It contains
both digital and analog (audio) circuits to support secure and clear voice processing.
The VPM connects to the console site LAN switch and communicates with the
dispatch console PC via Ethernet. There is a one-to-one relationship between the
VPM and the PC. Each dispatch position has its own PC and its own VPM. The
VPM provides all the audio processing services and encryption/decryption services
for the VPM-based dispatch console. These include:
♦ Vocoding services - Capable of supporting AMBE and IMBE (for ASTRO 25),
ACELP (for Dimetra IP) and G.728 (for analog resources) vocoder algorithms
♦ Audio processing services - Capable of supporting audio level adjustments,
summing and filtering and multiple simultaneous streams of audio.
♦ Encryption and decryption services - Capable of supporting multiple
simultaneous encryption/decryption sessions using multiple algorithms and
multiple secure keys.
The VPM provides the connections for the following items.

♦ Speakers
♦ Headset Jacks

RFP# 101216
December 16, 2010

♦ Microphone
♦ Footswitch
♦ Headset
♦ Instant Recall Recorder for Radio
The connections for the above items use RJ45 connectors except for the headset jack
connectors, which are DB15. The audio inputs and outputs are 600 Ohm, balanced
and transformer coupled, except for the microphone, which is 2000 Ohm, balanced
and does not use a transformer. They accept or provide audio levels appropriate for
the devices being connected.
The VPM-based dispatch console provides a suite of application programming
interfaces (APIs) that may be used by third parties to interface computer aided
dispatch (CAD) systems, non-Motorola dispatch consoles or other devices with the
Motorola radio system.
Desktop Dispatch
Desktop Speakers
Microphone Console
Monitor
PC
Analog
VPM
Footswitch
Local Logging Recorder
Instant Recall Recorder
External Paging Encoder
External Telephone System Ethernet
Ethernet
Cable 2 Ethernet Cables per
Cable Dispatch Console
Analog
Headset Jacks
LAN Console Site

Switch Router
MCC 7500
Dispatch Console
Consoles Site Link
2 Ethernet Cables per (WAN)
Dispatch Console
Figure 5-3: MCC 7500 Dispatch Site Block Diagram

RFP# 101216
December 16, 2010

5.1.5.3 Desktop Gooseneck Microphone
The dispatch console is capable of supporting a single desktop gooseneck

microphone. The desktop microphone contains a microphone cartridge on a flexible
shaft and two buttons in its base. One button controls the General Transmit feature
and the other controls the Monitor feature.
5.1.5.4 Headset Jack

An MCC7500 dispatch console is capable of supporting up to two headset jacks. A
headset jack allows a dispatch console user to use a headset while operating the
dispatch console. The headset jacks ship from the factory configured for 6-wire
headsets. When a headset is plugged into a headset jack, the selected receive radio
call audio is typically removed from the speaker(s) and routed to the headset
earpiece. The radio resource may be configured to output receive audio through the
speaker and not to the headset earpiece when a headset is in use. If two headsets are
connected to a dispatch console, the same radio audio appears in the earpieces of both
of them.
When an external telephone set connected to a dispatch console’s external telephone
port and is taken off hook while a headset is connected to a dispatch console, the
selected radio audio is removed from the headset earpiece and routed to the
appropriate speaker. The received telephone audio is routed to the earpiece of the
headset connected to the first headset jack. The microphone of the headset connected
to the first headset jack becomes live and its audio is routed to the external telephone
set. This allows the dispatch console user who is using the headset connected to the
first headset jack to talk and listen on the telephone set in a hands free full duplex
mode. A headset connected to the second headset jack cannot be used with the
external telephone set; it may only be used with the radio channels on the dispatch
console.
5.1.5.5 Dispatch Speaker
Each speaker on a dispatch console contains unique audio; that is, an audio source
cannot appear in multiple speakers at a single dispatch console. The speaker is
designed for use near computer monitors or mounted on a computer monitor. It
contains an amplifier which provides a maximum of two watts of power.

RFP# 101216
December 16, 2010

5.1.5.6 Footswitch
The footswitch allows a dispatch console user to access the General Transmit feature
or Monitor feature without using his/her hands. This is useful in situations where the
dispatcher's hands are not free for activating those features.
5.1.5.7 MCC7500 Console Site Equipment at Floyd 911

♦ (6) MCC7500 Certified Workstations
♦ (6) 19” LCD Black Monitors
♦ (6) Keyboards
♦ (6) Optical Wheel Mice
♦ (6) MCC7500 Series Voice Processor Modules (VPM)
♦ (6) MCC7500 Series Gooseneck Microphones
♦ (12) MCC7500 Series Headset Jacks
♦ (6) MCC7500 Series Footswitches
♦ (6) Headset Bases with Push-To-Talk
♦ (6) Supraplus Noise canceling Single Muff Headset
♦ (12) Speakers
♦ (3) Conventional Channel Gateways (CCGWs)
♦ (1) SDM3000 AUX I/O
♦ (2) Console Site Switches
♦ (6) Control Stations
♦ (1) Control Station Combiner with eight ports
♦ (1) Antenna System
5.1.5.8 Floyd 911 Logging:

♦ (1) GenWatch3
♦ (1) GenWatch computer workstation running GenSpout software
♦ (11) Control stations
♦ (1) Control Station Combiner with 12 ports

RFP# 101216
December 16, 2010

5.1.5.9 MCC7500 Console Site Equipment at Back-up 911 / EOC
♦ (5) MCC7500 Certified Workstations
♦ (5) 19” LCD Black Monitors
♦ (5) Keyboards
♦ (5) Optical Wheel Mice
♦ (5) MCC7500 Series Voice Processor Modules (VPM)
♦ (5) MCC7500 Series Gooseneck Microphones
♦ (10) MCC7500 Series Headset Jacks
♦ (5) MCC7500 Series Footswitches
♦ (5) Headset Bases with Push-To-Talk
♦ (5) Supraplus Noise canceling Single Muff Headset
♦ (10) Speakers
♦ (2) Conventional Channel Gateways (CCGWs)
♦ (1) SDM3000 AUX I/O
♦ (1) Console Site Switch
♦ (1) Console Site Router
♦ (5) Control Stations
♦ (1) Control Station Combiner with eight ports
5.1.6 On-site Digital P25 Repeaters at Jail and Prison

Based on the RFP and customer visits, Motorola has included two on-site repeaters.
One repeater will be located at the Floyd County Jail and one will be located at the
Floyd County Prison. These repeaters will allow for radio-to-radio signaling to
include Unit ID display and Emergency alarms with Unit ID for on-site operation.
When subscribers are utilizing the local repeater, all voice traffic, Unit ID
information, and Emergency alarms will be limited to local repeater users and will
not utilize Trunking system resources. Users will also have the ability to utilize the
ASTRO 25 Trunking system should the need arise.
5.1.6.1 P25 Conventional Repeater Equipment at Floyd County Jail

♦ (1) P25 800MHz GTR8000 Conventional Repeater

RFP# 101216
December 16, 2010

5.1.6.2 P25 Conventional Repeater Equipment at Floyd County Prison
♦ (1) P25 800MHz GTR8000 Conventional Repeater
5.1.7 MIP 5000 Jail Dispatch Console

The MIP 5000 dispatch console will provide the Jail Dispatcher the ability to monitor
and control six local control stations affiliated to the ASTRO 25 Trunking system
monitoring Talkgroup traffic for Courts, Warrants, Sheriff’s TAC, PD, Fire and
Public Works, in addition to the on-site P25 repeater.
5.1.7.1 MIP 5000 Equipment at Floyd County Jail

♦ (1) MIP 5000 Console Position which consists of the following equipment:
(1) MIP 5000 VoIP Dispatch Software
• Includes the software and a license for 8 channel radio console.
• Allows a dispatcher to access and control seven MIP 5000 Tone
Gateways
• Includes a USB HASP key for license activation that must be
inserted into the PC
(1) Monitor
(1) MIP 5000 workstation
(1) Keyboard and mouse/trackball
(1) Desktop microphone
(2) Desktop speakers
(2) Disconnect headsets
(1) USB-connected headset jackbox
♦ (1) HP Switch
♦ (5) Tone-controlled control stations
5.1.8 MC1000 Desktop Control Stations
5.1.8.1 Jail
In order to provide communication options at various locations throughout the Jail,
several system components will be installed, including a MIP5000 dispatch console,
control stations, and desksets.
A complicated system of wireline control station desktop handsets are currently in
use today. These units provide Jail personnel the ability to communicate with the on-

RFP# 101216
December 16, 2010

site repeater, the SO TAC repeater on Mount Alto, and the State Band VHF channel.
Motorola has proposed to replace these units with newer model MC1000 desksets
and control stations, which will provide access to the new on-site repeater, new
Sheriff’s TAC Talkgroup, new Warrants Talkgroup, new Court Talkgroup, and
current VHF state band channel.
Motorola will re-use existing wiring when possible and add wiring for new units as
indicated in the diagram on page 5 of Addendum 2 (29 Oct 2010). Based on the
diagram, the following components are included:
5.1.8.2 Wire-line Desktop Handset and Control Station Equipment at

Floyd County Jail
♦ (15) Wired MC1000s controlling the on-site digital P25 repeater located at:
Towers 1, 2, 3, 4, 5, 6 (replacements)
Medical Unit (replacement)
Front Lobby (replacement)
Booking (replacement)
Warrants (replacement)
Sheriff (replacement)
Chief Deputy (replacement)
Jail Administrator (replacement)
Assistant Jail Administrator (new)
Lt. Blanton’s Office (new)
♦ (1) Control Station for aggregating physically remote MC1000 units to access the
on-site digital P25 repeater
♦ (7) Wired MC1000 units to access the SO TAC equivalent Talkgroup on the
ASTRO 25 system. MC1000 units will be located at:
Jail Administrator (replacement)
Assistant Jail Administrator (replacement)
Lt. Blanton’s Office (replacement)
♦ (4) Wired MC1000 units to access the Warrants Talkgroup on the ASTRO 25
system. MC1000 units will be located at:

RFP# 101216
December 16, 2010

♦ (4) Wired MC1000 units to access the Courts Talkgroup on the ASTRO 25
system. MC1000 units will be located at:
5.1.8.3 Court House – Sheriff Office

Motorola has proposed four new MC1000 desksets and one control station, which
will provide access to the new Sheriff’s TAC Talkgroup, and one control station
which will provide access to the new Court Talkgroup (installation location - to be
determined).
5.1.8.4 Wire-line Desktop Handset and Control Station Equipment at

Court House
ASTRO 25 system will be located at:
Captain Ely’s Office
Peggy’s Office
Tina’s Office
Court Holding
♦ (1) Control Station - SO TAC equivalent Talkgroup
♦ (1) Control Station - Court Talkgroup
5.1.8.5 Floyd County Prison

Motorola has proposed three new MC1000 desksets and one control station, which
will provide access to the new Sheriff’s TAC Talkgroup, and three new MC1000
desksets and one control station which will provide access controlling the on-site
digital P25 repeater.

RFP# 101216
December 16, 2010

5.1.8.6 Wire-line Desktop Handset andControl Station Equipment at
Floyd County Prison
♦ (3) Wired MC1000 units to access the on-site P25 repeater will be located at:
Admin Office
Main Control Room
Work Release Control Room
♦ (1) Control Station – P25 On-site Repeater
ASTRO 25 system will be located at:
Admin Office
Main Control Room
Work Release Control Room
♦ (1) Control Station - SO TAC equivalent Talkgroup
5.1.9 Fire Station Alerting (FSA)

Motorola’s proposal provides alerting infrastructure using one relocated VHF
MTR2000 repeater and one 800MHz analog repeater. The MCC7500 consoles will
provide any dispatch position alerting control to both Fire and EMS stations.
Additionally, Motorola’s radio-based Fire and EMS Station Alerting System:
♦ Utilizes a VHF stand alone repeater to alert the 11 Fire stations
♦ Utilizes an 800MHz stand alone repeater to alert the eight EMS stations
♦ Supports single or multiple station alerting
♦ Utilizes the proposed MCC7500 dispatch consoles to broadcast dispatch audio
over ASTRO 25 Trunking Talkgroups and the conventional repeater alerting
channels
♦ Allows alerting from multiple MCC7500 operator positions
♦ Includes a new PA in stations that currently do not have public address amplifiers
to match the PA’s installed in some of the Fire stations
♦ Delivers dispatch audio to station’s speaker system
♦ Allows setting of light and/or audible alarm at each station
Motorola has made every effort to create a Fire/EMS alerting system that is easy to
operate under stress and which provides the operator the confidence needed when
emergency situations demand flawless performance. The FSA system is controlled
by the MCC7500 consoles. The console provides an easy to access call list and quick
buttons for fast alerting of multiple stations. Integrating the Fire/EMS alerting
system into the MCC7500 console maximizes dispatcher efficiency and eliminates
any required ancillary computer systems required for station alerting.
RFP# 101216
December 16, 2010

Due to the critical nature of Fire and EMS response times, the alerting system utilizes
high reliability radio components for each station. The CDM1250 VHF (MHz) radio
with local audio output and light and/or alarm control and the XTL2500 800MHz
radio with local audio output and light and/or alarm control have been selected to
provide this functionality. After receiving a station-specific two-tone alert, each
radio will be programmed to close a digital output and open a relay to allow audio to
be sent to the station’s distributed speaker system. Based on Motorola’s
understanding of Floyd County’s operation, ‘day/night’ override switches have not
been included. Should the County desire for all stations to be notified of each
dispatch call, the all-call feature can be utilized to alert all stations simultaneously.
5.1.9.1 FSA Radio Equipment at each Fire Station

Each station radio will include:
♦ (1) antenna and RF cables required to provide reliable communications from the
Mount Alto repeater site
♦ (1) CDM1250 Control Station
♦ (1) Public Address (PA) Amplifier
♦ Associated wiring to connect CDM1250 output to PA and to existing Light and/or
Audible Alarm
5.1.9.2 FSA Radio Equipment at each EMS Station

Each station radio will include:
♦ (1) antenna and RF cables required to provide reliable communications from the
Mount Alto repeater site
♦ (1) XTL2500 Control Station
♦ (1) Public Address (PA) Amplifier
♦ Associated wiring to connect XTL2500 output to PA and to existing Light and/or
Audible Alarm
5.1.10 Regional Interoperability with Surrounding Agencies

As part of Motorola’s response, a complex network of radio access equipment has
been included to provide interoperability to each of the agencies identified in the
RFP. Neighboring agency radio communications are accessed with geographically
and frequency band appropriate control stations. The audio from these control
stations is wired directly into Motorola’s Conventional Channel Gateways (CCGWs),
which convert analog audio from the control station into ASTRO 25 IP audio
packets. Each neighboring communications channel can be linked to the ASTRO 25
users in one of two ways: 1) automatic “computer-controlled” audio links or 2)
manual “patching” by dispatchers at Floyd E911 or Floyd EOC. The automatic
scenario requires a specific Talkgroup to be permanently assigned to each

RFP# 101216
December 16, 2010

surrounding agency channel. The manual patch can be monitored by dispatch and
linked to the appropriate Floyd County ASTRO 25 Talkgroup to assist in joint agency
communications. Motorola’s response is based on our understanding of the RFP and
surrounding agency’s operations. Some assumptions have been made; however,
equipment has been included at the following sites to provide access to the following
systems and agencies (located on adjacent radio towers).
♦ Mount Alto RF site
Georgia Bureau of Investigation
Georgia Department of Natural Resources
Federal Bureau of Investigation
Bureau of Alcohol, Tobacco, Firearms and Explosives
♦ Floyd County 911 Dispatch Center
Georgia Forestry Commission
Georgia State Patrol
♦ Rocky Mountain RF site
Chattooga County, Georgia
Walker County, Georgia (also available via ISSI.1 interface)
Berry College
♦ Cave Springs RF site
Polk County, Georgia
Cherokee County, Alabama
Drug Enforcement Administration
♦ Shannon AT&T RF site
Gordon County, Georgia
Bartow County, Georgia
5.1.11 Hot Stand-by Microwave System

To provide the required site connectivity for the Motorola P25 radio system,
Motorola will provide and install a digital microwave system. This digital
microwave system will operate in the FCC licensed 6 GHz and 11 GHz bands and
will consist of the following links:
• Floyd Co E911 to Fouche Gap
• Fouche Gap to Cave Springs
• Cave Springs to Leonard
• Leonard to Hillindale
• Hillindale to Shannon AT&T
• Shannon AT&T to Mount Alto
• Mount Alto to Floyd Co E911
RFP# 101216
December 16, 2010

• Mount Alto to EOC Backup 911
• Mount Alto to Rocky Mountain
• Rocky Mountain to Taylor’s Ridge (Walker County)
• Blossom Hill to Floyd Co E911
The layout of these 11 links will consist of seven links in a “ring” configuration and
four “spur” links off of the ring. All radios, both within the ring and in the spurs, will
be configured for a “Hot Standby” mode of operation, in which the link will
automatically switch to a redundant radio upon failure of the primary radio. In
addition to the equipment redundancy already provided by this Hot Standby
configuration, sites within the ring will have the additional protection available
within a ring configuration of both the T1 connections via Sub-network Connection
Protection (SNCP) and the Ethernet connections via Route Spanning Tree Protocol
(RSTP). The microwave system has been configured with the Controllers and Hot
Standby radios mounted within the same cabinet and elliptical waveguide connecting
the radios to the high performance microwave dish antennas on the tower. This
design offers significant diversity and redundancy provided by the “1+1” Hot
Standby radios and loop microwave design. Should one radio fail, the other radio
will maintain operations without the reduction of bandwidth. Additionally, if both
radios should fail within the loop, the data would re-route itself around the opposite
side of the loop. Alternative radio configuration are available, including tower-
mounted radios with indoor controllers and a loop switched design without Hot
Standby radios. This configuration is available for Hot Standby hops and/or loop
designs and provides a higher fade margin using smaller microwave dish antennas
and reduces the load on the tower, while providing a significant cost savings.
Preliminary path design for this microwave system has been performed to insure that
each of the links will meet the performance requirements requested by Floyd County.
Each of the links has been designed to meet or exceed 99.99975% reliability, with
less than 78.8 outage seconds per year, and a minimum fade margin of 40dB. The
unfaded Bit Error Rate (BER) of the microwave radio equipment is less than 10-10
and the links have been designed for a maximum faded BER of 10-06. The link
outage level (10-3 BER) will not occur at less than 3 dB in excess of the calculated
fade margin. Specific path details have been included in Table 5-3 below:
Table 5-3: Preliminary Microwave System Availability Data
Path Band Availability Annual Outage

(GHz) (%) (sec)
Loop Configuration (7 Sites) 6 & 11 99.99985 46.2
Blossom Hill – Floyd Co E911 11 99.99999 5.9
Mount Alto ‐ Rocky Mtn – Taylor’s 6 99.99988 38.7
Ridge
Mount Alto – EOC Backup 911 11 99.99997 9.7

RFP# 101216
December 16, 2010

The microwave network design provides a hybrid TDM/Ethernet solution, with full
Layer-2 switch capabilities, on a bandwidth that exceeds SONET throughput on a 30
MHz channel. Each link is currently configured for Ethernet, with two GigE ports
and five Fast Ethernet ports. The only exception to this is the Floyd 911 site, which
has been configured with two GigE ports and ten Fast Ethernet ports. Each link has
also been configured with a 16xDS1 port. Some of the key features of this
microwave network are:
♦ Industry leading system gain
♦ Full Layer-2 Ethernet Switching
♦ Native T1 and Native Ethernet (minimal latency)
♦ Dynamic bandwidth reallocation (T1’s that aren’t used are dynamically
reallocated to the Ethernet stream)
♦ High bandwidth efficiency
♦ GigE and Fast Ethernet ports
♦ Built-in SNCP and RSTP, to allow for ring protection for T1 and Ethernet
without the use of external routers or switches
♦ Adaptive Coding and Modulation (ACM)
♦ Link Aggregation
♦ Full Quality of Service (QOS) and Class of Service (COS) functionality
♦ Full OA&M functionality
♦ Software capable expansion
Power for the microwave system will be provided by -48VDC rectifier plants, which
have been included at each of the locations. To provide continued operation of the
microwave equipment, in the event of a power outage, each of the locations will also
include a standby battery system sized for 24-hours of operation. An automatic
low-voltage disconnect system will be utilized to protect the battery plant from
deep-cycle discharge damage.
The microwave system has been designed for ease of testing, troubleshooting and
repair of network components. Network Management and alarming of the
microwave system will be integrated into the overall Network Management of the
radio network, but may also be made available at a separate server dedicated to the
microwave system. A set of microwave equipment spares has been included with the
system, to provide for quick replacement of equipment failures. An Orderwire
channel will be available on the microwave network and an Orderwire handset has
been included at each microwave radio site, to further aid technicians in the testing
and troubleshooting of the network.
5.1.11.1 Microwave Link Equipment for each Hop

The following equipment is included in each Microwave Link
♦ (2) Digital microwave radios.

RFP# 101216
December 16, 2010

Equipped for Hot Standby operation
(16) DS1 Interfaces
(2) Gigabit Ethernet Interfaces
(5) Fast Ethernet Interfaces (scalable to 10)
Configured for Orderwire operation (handset included)
♦ (1) Seven-foot, 19-inch equipment rack
♦ (2) Antenna-waveguide networks
(2) Antennas
Flexible waveguide
Waveguide accessories
• Connection adapters
• Hanger kits
• Grounding kits
• Entry boots
• Dehydrators
♦ (1) -48VDC Rectifier plant (independent of RF infrastructure)
♦ (1) Battery plant
Sized for 24-hour equipment runtime
Equipped for low-voltage disconnect
The proposed solution, which is fully compliant with the requirements of Floyd
County, consists of a Hot Standby microwave radios installed within the equipment
shelter connected to tower mounted dishes by waveguide. Motorola has identified
several potential alternative solutions, which would reduce the overall cost of the
transport system. The details of each of these alternatives are listed below and the
cost reductions are included in the pricing summary.
♦ In the proposed solution, all microwave radio, network and control equipment
would be installed within the equipment shelter, with waveguide connecting the
radio equipment to the dishes mounted on the towers. While this will simplify
repair and replacement of any malfunctioning radio equipment, it does add to the
expense of the transport system. An alternative solution would be to “split” the
equipment between the shelter and the tower, with network and control within the
shelter and the radio installed on the tower with the dish. This would eliminate
the need for the installation of waveguide on the tower and reduce the size of
dishes needed to meet the required 40 dB of fade margin on each link. These two
factors combined would not only reduce the overall cost of the transport system,
but would reduce the loading on the towers. While this limits the accessibility of
the radios, when paired with Hot Standby radios, the failed radio can be repaired
without impacting operation.

RFP# 101216
December 16, 2010

♦ In the proposed design, Hot Standby radios are utilized on each link within the
microwave transport network, as requested by Floyd County. While this
configuration is preferred for spur links, it provides a potentially unnecessary
level of redundancy on links within the loop. The protection inherent to the ring
configuration would provide an adequate level of link redundancy for sites within
the ring. An alternative solution would be to provide Hot Standby radios on the
spur links, while leaving the links within the loop in a standard configuration.
This will reduce the cost of the microwave transport network infrastructure.
♦ A third alternative configuration for the microwave transport network would be to
combine the first two suggested alternatives. Installing the microwave radio
equipment in a “Split-Mount” configuration and removing the Hot Standby
configuration from radios within the Loop would provide a more significant cost
savings than either alternative alone.
5.2 ASTRO 25 System Features

The ASTRO 25 system features Project 25 compliant trunking, as described in the
TIA 102 standard. In order to achieve this compliance, Motorola optimizes custom
solutions for mission-critical voice communications performance, more efficiently
than solutions that use commercial-off-the-shelf network components. When public
safety life or death decisions depend upon clear uninterrupted voice, Motorola has the
correct IP solution.
5.2.1 Simulcast
Capable of supporting up to 15 remote sites and 30 channels per site, our ASTRO 25
simulcast solution allows for extended system coverage, especially in areas where
spectrum is scarce. Motorola’s digital simulcast technology is IP-based and extremely
cost-effective, eliminating the typical audio distribution equipment found in previous
generation simulcast networks. The simulcast and repeater site designs offer ease of
radio operator use over large geographic areas throughout Floyd County.
The proposed solution also takes advantage of Motorola’s proven narrowband 12.5-
kHz 800-MHz platform, and adds IP-based network design for the highest degree of
reliability and flexibility.
5.2.2 700/800 MHz Operation

The proposed 800MHz system is comprised of network infrastructure and RF
distribution systems that are capable of operating as both 700MHz and 800MHz
frequencies. As requested, pricing options for an integrated digital “simulcast-only”
system and a “hybrid” simulcast/multi-site system have been provided. Both designs
utilize the same eight radio sites and provide seamless roaming for subscriber users
RFP# 101216
December 16, 2010

traveling throughout the County. Motorola has completed system loading studies
based on information provided in the RFP and considered the 25% increase in users
over the next five years. It was determined that 10 channels would provide enough
capacity to provide reliable public safety grade of service and a mean wait time of
less than one second. The hybrid multi-site solution minimizes infrastructure costs
and capitalizes on the reduced population and day-to-day County operations in the
Rocky Mountain/Texas Valley and northern “pocket” areas. These repeater sites
provide a five- channel trunking solution offering capacity for daily operation or
potential disaster response situations as explained by Floyd County during the pre-bid
conference in October. Both of these solutions have been designed to allow
straightforward channel addition of 700MHz channels or TDMA operation and will
not require replacement of any proposed RF distribution equipment.
5.2.3 Centralized System Management

Alerts, diagnostics, and faults in the system will be reported to two supervisor /
network management consoles. One supervisor console will be located at the Floyd
County 911 Zone Core / dispatch site and the other will be located at the Backup 911
/ EOC center, as per the RFP requirement. These consoles allow centralized system
monitoring and management to keep the system healthy.
The network management subsystem is made up of two Zone Servers which host the
necessary system-wide applications and databases required to maintain the ASTRO
25 system. The Zone Servers incorporate server virtualization technology, which
maximizes the utilization of the servers, provides adaptability to technology
enhancements, and better provides for future communication needs and migration.
The primary Zone Server combines the Primary Zone Controller with the Air Traffic
Router and the Zone Database Server. The second Zone Server hosts the backup
Zone Controller and the Network Management system. The Network Management
system is comprised of the software and infrastructure required for user management,
system management, fault management, and performance management and is
comprised of the following applications.
♦ Unified Network Configuration (UNC)
♦ User Configuration Manager (UCM)
♦ Unified Events Manager (UEM)
Additional information on the Network Management and alerting can be found in the
Network Management section of this proposal.
5.2.4 Vocoder-Based Encryption

Digital operation in general offers some level of security to system users. However,
the proposed ASTRO 25 simulcast system can support several standards-based

RFP# 101216
December 16, 2010

algorithms such as DES-OFB and AES. Motorola has selected AES Encryption for
all infrastructure, dispatch, and subscriber operation. Encryption keys must be
routinely changed to keep communications secure. Key loading is performed using
the Key Variable Loader (KVL) for each subscriber and console position in the
system.
5.2.5 ASTRO 25 Trunking Call Services

Motorola’s ASTRO 25 trunking system offers a wide range of advanced call services
to meet the demanding communications needs of a diverse, mission-critical
workforce. Several key calling features and benefits are described in the following
subsections.
5.2.5.1 Call Categories

Talkgroup Call is the primary communication level in an ASTRO 25 trunked system
as the majority of conversations take place within a talkgroup. Talkgroup Call
provides the effect of a “dedicated channel” for each talkgroup.
Emergency Alarm/Call provides users the ability to inform personnel of a life-
threatening situation by depressing the radio’s emergency alarm button. The
emergency indication is also logged and cleared at the network management client
terminal.
If all voice channels are occupied, the system is capable of functioning in one of the
following two modes.
♦ Emergency Top-of-Queue places the unit initiating the emergency at the top of
the busy queue list and allows access to the next available voice channel.
♦ Emergency Ruthless Preemption allows the unit initiating the emergency access
to the voice channel with the lowest priority user currently assigned. Once the
non-emergency user de-keys, the channel belongs to the emergency user.
Private Call allows selective call to another individual user in the system regardless
of what talkgroup either unit has selected.
Call Alert allows selective sending of a signal to another user to call back the
alerting party. Call alert remains enabled until cleared by the alerted party. This
feature helps ensure that important messages get through, even if the called party is
away from the radio. Call alert signaling takes place over the system control channel,
so it is no burden on the valuable voice channels.
Busy Queuing and Callback

Although ASTRO 25 trunking systems are considerably more frequency efficient
than conventional radio systems, there may still be times when all of the voice
RFP# 101216
December 16, 2010

channels are busy. If a radio user attempts to initiate a call while all the system
channels are in use, the requesting user will be put into a busy queue and then
automatically notified when a channel becomes available. This feature allows the
radio user to place the microphone down during a busy situation instead of
continually re-keying in an effort to gain channel access.
Multiple Priority Levels

ASTRO 25 IP provides multiple levels of priority allowing system access to the most
critical users during busy periods. Individual users and talkgroups may be assigned
specific priority level(s), with up to ten levels supported for each, which will allow
higher priority users to be placed higher in the busy queue for quicker system access.
The ASTRO 25 IP system allows for flexible assignment of priority levels to meet
your organizational needs.
Continuous Assignment Updating

This feature is designed to assure that a radio just coming into service during an
active talkgroup conversation will be immediately assigned to the appropriate voice
channel. The user will be included in his or her active talkgroup call with no special
action required. To achieve this, the ASTRO 25 IP system control channel
continuously transmits the channel assignment for talkgroups involved in active calls.
5.2.6 Network Management System

The Network Management System (NMS) can be viewed as a set of software
applications or tools used to manage the ASTRO 25 wide area trunked radio system
and its constituent components.
The NMS supports the following services:
♦ Network Monitoring – Applications are included for monitoring the status of the
transport network and the individual infrastructure components; displaying status
information; forwarding alert information; and performing diagnostic procedures.
♦ Configuration Management – Facilities are provided for entering and
maintaining the operational parameters of the infrastructure components and user
devices (i.e., the mobile and portable radios).
♦ Accounting Management – NMS supports the tracking of radio usage of the
system by providing an optional interface to third party accounting and/or billing
applications.
♦ Performance Management – Standard and optional applications are available for
monitoring, reporting, controlling, and optimizing the use of system resources.
♦ Security Management – NMS includes features for setting user privileges and
controlling their access to view and/or modify information contained in the
configuration databases.

RFP# 101216
December 16, 2010

The NMS subsystem includes the following virtual servers within the zone core of
the ASTRO 25 system.
♦ NMS Zone-level Servers – Zone Database Server, Unified Event Manager, and
Zone Statistics Server.
5.2.6.1 Air Traffic Router

The Air Traffic Router (ATR) hosts a variety of real-time, data processing
applications to support user and system applications. The ATR server receives air
traffic information from the Zone Controller. This includes processing real-time call
transactions, logging all data to disk, routing RCM command and status packets
to/from the Zone Controller.
5.2.6.2 Zone Database Server

The Zone Database Server (ZDS) handles a variety of tasks; including hosting the
zone configuration database, administering applications licenses, authenticating
network manager users accessing the system, and performing back-end support for
user applications.
The ZDS performs the following database server functions:
♦ Maintains the infrastructure (zone configuration) database for the zone.
♦ Exports the infrastructure information from its database to the Zone Controller
where it is stored as the local infrastructure database.
♦ Maintains a replica of the current UCS database and home zone map.
♦ Exports the radio information it receives from the UCS to the Zone Controller.
The ZDS also performs all network management and fault management polling of
system devices to support the network management clients. The fault management
information that the ZDS collects is passed on to the Unified Events Manager (UEM)
server.
The ZDS handles a variety of administrative tasks, including the following:
♦ Administering the standard and optional applications licenses.
♦ Authenticating network manager users accessing the system.
♦ Performing back-end support services for user applications.
♦ Handling telephone interconnect record processing.
5.2.6.3 Zone Statistics Server

The statistics server is the data repository for data statistics necessary to drive
Historical Reports. Statistics such as the number of calls, push-to-talks, and busies are
accumulated over preset time intervals.

RFP# 101216
December 16, 2010

5.2.6.4 User Configuration Server
The UCS provides database storage and back-end processes required for most
system-wide functions. The UCS makes it possible for management personnel to
configure home zone maps, users, radios, talkgroups, critical sites, Adjacent Control
Channels (ACC), security information at a system-level, and other system-level
parameters. Group and Unit ID home zone assignments are also made at the UCS
level. This information is configured using the UCM application and is saved in the
UCS database.
5.2.6.5 Unified Event Manager

The UEM provides a central location for managing all radio, transport, and
environmental devices on the system.
The application automatically discovers devices on the network to determine their
real-time status. Color-coded symbols displayed on a topography map provide a
geographical and hierarchical representation of the entire network. The UEM allows
each user to filter out and customize the pertinent information important to their roles
and responsibilities. Features and benefits of the UEM are outlined in Table 4-4.
Table 5-4: Benefits of the UEM
Feature Benefit
Centralized View of Entire Network Managers can view the entire ASTRO 25
Communications Network system status and quickly isolate problems to the board
level.
Intuitive Graphical User Network Managers can be quickly notified of failures on
Interface (GUI) the system and diagnose device problems, utilizing a
display and an intuitive GUI.
Auto Discovery of Devices Components are automatically discovered and map
views are created to show the overall health of the
network.
Active Alarms View and Alarm Persistent single view all failure conditions in the network
Summary and a quick reference summary of alarms by severity
allows users to quickly pinpoint the highest priority
failures.
Secure Device Access SNMPv3 protocol with Triple DES and AES 256 bit
(optional) encryption to prevent security breach attempts.
Northbound Interface Real time event stream using a standard industry
(optional) protocol that can be used to forward events to a higher-
level management application for added flexibility.
Email Notifications User specified event notifications sent via email – which
can also be forwarded to a portable mobile device –

RFP# 101216
December 16, 2010

Feature Benefit
allows System Managers to simultaneously address
other tasks.
Network Monitoring Archive and export event history data for analysis.
Capabilities
Remote Command Operation Remote state change capability helps to avoid
unnecessary sites trips.
The UEM gives the Network Manager virtually instantaneous notification of any
system deficiency or element failure.
5.2.6.6 UEM Event Browser

Figure 5-4 illustrates the UEM Event Browser screen.
Figure 5-4: UEM Event Browser sample screen
All events (or a filtered subset of events) that are received by UEM is viewable via
the UEM event browser. By default, when viewing an event, the event browser
displays Severity, Date/Time, Managed Resource, Entity, and Message. Additional
display properties are available. Up to 10,000 of the most recent events from any
managed device within a zone can be displayed.

RFP# 101216
December 16, 2010

5.2.6.7 UEM Alarm Browser
The UEM alarm browser (Figure 5-5) allows the user to view all alarms, or a filtered
subset of alarms. By default, when viewing an alarm, the alarm browser displays
Severity, Date/Time, Managed Resource, Entity, Message, and Owner/Assignee
information. Additional display properties are available. UEM supports exporting
events and alarms for future analysis.
Figure 5-5: UEM Alarm Browser sample screen
5.2.6.8 Network Management Terminals

The NMS Windows-based client/server architecture distributes most of the user
application processing to the client PC workstations. The following applications run
on or may be accessed from the Network Management terminal:
♦ System Profile
♦ UCM
♦ Software Download
♦ Zone Profile
♦ Zone Configuration Manager

RFP# 101216
December 16, 2010

♦ ZoneWatch (optional)
♦ Affiliation Display
♦ Historical Reports
♦ RCM
♦ RCM Reports
5.2.6.9 User Configuration Server (UCS)

The UCS allows management personnel to configure home zone maps, users, radios,
talkgroups, critical sites, Adjacent Control Channels (ACC), system-level security
information, and other system-level parameters.
5.2.6.10 User Configuration Manager

The User Configuration Manager (UCM) provides data entry screens for the mobile
and portable radio units authorized to use the system. The UCM is also used to set
security information at a system level. The user interface is Java-based and has
Explorer-like managed object navigation features. Configuration reports can be
generated. A sample UCM Screen is shown in Figure 5-6.
The subscriber profiles feature allows the replication of parameters that are common
to multiple radio units, thereby reducing the time and effort to load the user
configuration database. Working in concert with the UCS, radio unit data is entered
once only for each unit and automatically distributed to the user configuration
database residing in the ZDS at its resident zone and all other zones in a multi-zone
system.
Figure 5-6: Sample UCM Screen

RFP# 101216
December 16, 2010

5.2.6.11 Network Management Terminals and Licenses
The following SmartZone™ network management terminal option applications are
available. One license is provided for: Radio Control Manager, Zone Historical
Reports, Unified Events Manager, and Configuration Management. More licenses
may be purchased for specific features if desired. This single license can be used by
either of the NM clients attached to the system.
Radio Configuration/Radio User Report (Included)
Basic Radio Control Manager (RCM)

The RCM application provides two types of functions: radio commands can be
initiated (e.g., Dynamic Regrouping and Selective Inhibit) and radio events are
displayed (e.g., Status and Emergency Alarm). A sample RCM screen is shown in
Figure 5-7. The RCM has the following features:
♦ Dynamic Regrouping – Dynamic Regrouping allows a dispatcher or system
manager to dynamically program an affiliated radio user to a particular talkgroup.
The dynamic regrouping function is implemented within one second per
regrouped radio. A companion function “Cancel Regroup” cancels the regrouping
command and removes the radio from the regrouped talkgroup. When a radio is
regrouped, the subscriber will acknowledge (ACK) the command, and the ACK is
sent to the initiating terminal. The subscriber will generate an audible noise
indicating to the user that the radio has been regrouped.
♦ Storm Plans – Storm Plans provide the system with a consistent procedure for
special or emergency situations. A completed Storm Plan can have a maximum of
four commands, each containing a maximum of 100 individual radio tasks.
♦ Selective Inhibit/Un-inhibit – Selective Radio Inhibit enables a user to
functionally disable a subscriber unit that is currently affiliated to the system.
This feature can be used to disable stolen radios or invalid users. If the initial
inhibit command fails within 30 seconds, a notice is sent to the initiating terminal
to select either endless search or quit. The companion function “Cancel Inhibit”,
reactivates the radio in the same manner.
Other features include:
♦ GUI for ease of use
♦ Status function
♦ Online help

RFP# 101216
December 16, 2010

Figure 5-7: RCM Screen Example
ZoneWatch Grid and Control (Optional)

ZoneWatch Grid and Control is available, but not proposed. A sample screen is
shown in Figure 5-8.
ZoneWatch Grid and Control is a performance management tool with customizable
displays and graphs to monitor real-time communications activity in a zone. The
information displayed can help system managers be proactive in making better
resource planning decisions, such as when additional channels need to be added to
busier sites.
♦ ZoneWatch Grid Screen – Air traffic within a single zone is displayed on a
Site/Channel grid. Real-time call activity for each channel is displayed in its
respective cell.
♦ ZoneWatch Control Display – This display presents call activity messages. These
can be used to isolate errors, trace the progress of a call and troubleshoot or
analyze current system activity. It also provides information about activity
occurring on the control channel, such as rejects, emergency alarms, and unit
affiliations.

RFP# 101216
December 16, 2010

Figure 5-8: ZoneWatch Control Display Example
System Historical Reports (Included)

System Historical Reports are available, but not proposed.
This application produces reports on radio infrastructure and radio resource usage
across multiple zones. A predefined set of reports, with field selection capability, is
supplied to produce “standard” or tailored reports. This option is not necessary in
systems of only one zone.
Historical reports are generated automatically or on demand. Automatic reports are
produced at a specific scheduled time and date or on a recurring time and date
interval. Reports can be sent to the monitor screen, a printer, Hyper Text Markup
Language (HTML), or CSV files.
This display provides zone-level, real-time line charts or 3D bar graphs that illustrate
channel utilization for all call types – group, private, control channel, and
dynamically blocked calls.

RFP# 101216
December 16, 2010

5.2.6.12 MOSCAD Network Fault Management (NFM) System
The ASTRO 25 system management tools, along with Motorola’s MOSCAD NFM
server, provide the ability to display and log detailed information on a variety of RF
and non-RF site equipment. MOSCAD provides high-resolution graphics of the
devices connected to MOSCAD SDM3000 Remote Terminal Units (RTUs) at sites
within the system. Information presented allows system operators easy access to
detailed equipment views.
Motorola is proposing a MOSCAD™ (Motorola Supervisory Control and Data
Acquisition) Fault Management for the monitoring and control of the County’s radio
sites. The Motorola MOSCAD system will provide the County with the ability to
continuously monitor non-SNMP devices and inputs for both normal and exceptional
conditions from each on the radio sites. This task is made very easy through
MOSCAD’s SDM3000 Node Translator (SNT), Graphic Master Central (GMC), and
Graphical Workstation (GWS).
Motorola’s MOSCAD provides real time monitoring and remote control for the
County’s various subsystems. It monitors equipment faults and diagnostic messages
in the following:
1. RS-232 Alarming of Third Party Equipment
TRAK GPS
Microwave Radio
2. Discrete Alarms at Remote RF Sites, such as
Door entry
Temperature limits
Power failures
The SDM3000 RTU forwards the faults to the MOSCAD GMC, where they are
graphically displayed. The SDM3000 RTUs also forward the faults to Motorola’s
FullVision Network Manager via SNMP.
Basic Alarm Operation

When the MOSCAD system detects a fault from any of the County sites and
monitored elements, the GMC and GWS computer will change the alarmed device
icon from green to red. Critical alarms will generate an audible alert tone. The
audible alert tone will sound even if a user is not logged into the InTouch™ software.
If the alarm condition goes away, the alert tones will not reset on its own accord, this
feature is included so that a County operator is forced to view the system status and
acknowledge the alarm. The site icon will remain red until corrective action is taken
on all alarms at the site.

RFP# 101216
December 16, 2010

All discrete alarm point reporting and control functions are accomplished through
SDM3000 RTUs and SDM3000 Node Translator (SNT). Each of the County RF sites
will be equipped with a MOSCAD SDM3000 RTU and IP Interface.
The MOSCAD SDM3000 RTU is a universal microprocessor controlled device that
serves as the actual equipment interface at the sites for the alarm and control
subsystem. The SDM3000 RTU will read faults and send them to the SDM3000
Node Translator (SNT) location. The SDM3000 RTU will receive control commands
from the GMC via the SDM3000 Node Translator (SNT) and provide serially
interfaced commands to RF equipment or contact closure to outside equipment to
carry out commands.
Fault Reporting (Polling and Contention)

The GMC will verify the SDM3000 RTU’s functional status periodically and
automatically polls each of the SDM3000 RTUs. Any faults that are detected during
polling tests are immediately reported to, and alarmed by, the GMC and GWS.
CPU Alarm Diagnostic Interface

The MOSCAD CPU is part of the SDM3000 RTUs at the remote sites and the control
sites. The CPU provides RS-232 serial alarm diagnostic interfaces to various
processor based RF communication devices for the purpose of receiving and
reporting faults from the devices. The serial interface can allow remote
troubleshooting and remote parameter programming changes to processor based
equipment such as the TeNSr and TRAK.
Graphic Work Station

The GWS provides a remote user with access to all of monitoring functionality of the
GMC but lacks the GMC’s ability to configure the system hardware. One GWS will
be located at the Floyd County 911 supervisor position and one will be located at the
EOC Backup 911 supervisor position to give the supervisor the ability to monitor the
system.
Operator Interface
The operator interface will utilize graphical user interface and text messages to
present information to the user. The users will log on to the system by entering a user
name and password. If the user name and password are valid, further navigation and
activity choices will be presented to the user. If a critical alarm is detected at any of
the sites, a site icon will flash red on the GMC and GWS system screen. When one
navigates to the affected site, a flashing red light will indicate the specific entity at
the site that is presenting the alarm. The alarm will remain in red text until the alarm
has been corrected. The alarm and acknowledgment will be recorded to log for later
reference. All alarm data will also be printed out as it is recorded.

RFP# 101216
December 16, 2010

Graphic Master Central
The GMC interfaces with the SDM3000 Node Translator (SNT) and provides a
graphical user interface for monitoring and controlling devices in each subsystem.
The GMC will run InTouch by WonderWare, a Windows-based software package. It
will present a graphical representation of the physical devices used to monitor
equipment at remote sites.
The GMC is virtualized on a Zone Core servers and it will allow viewing and
controlling of the entire system. The GMC will be located at the Floyd County 911
and connects into the MOSCAD system via the ASTRO IP backbone. The graphic
display and database is based upon the InTouch Windows-based application. This
software package resides on the GMC. The custom graphic screens depict current
system status where the user can easily navigate from a system view down to the
individual site details. All system alarms, Change of States (COS), and controls are
time stamped and stored in the alarm history file. History files allow for retrieval of
important information at all times.
Remote Dialup Laptop (available, but not proposed)

MOSCAD also provides the capability for a remote dial-up Graphic WorkStation
(GWS) with identical custom graphics as the GMC. The GWS uses the same InTouch
graphics application and custom display files but is reliant on the GMC databases for
MOSCAD SDM3000 RTU information update and control. Real-time system alarms,
status, and control are provided to the remote access GWS via a physical dial-up
modem link interfacing to the GMC. WonderWare’s NetDDE™ for Windows is the
communication protocol for this type of system operation. If the custom screens for
the GMC are modified, added, or deleted, then the remote GWS computers will
require similar software updates as well.
GMC Security
Security on the GMC will be based on a user’s login name and password. These
functions are provided with the InTouch software package and will be implemented
based on a list of users and access levels. A logon screen will be provided that will
allow a user to log on to the system by entering their access name and password.
When no user is logged on, no information will be displayed on the screen and no
controls will be able to be sent. The audible alarm will still sound even if no user is
logged on. If a user forgets to log off, the system will automatically log the person off
after 30 minutes (this time is configurable).
GMC Graphic Screens

The GMC node will be programmed to provide several layers of screens depending
on the preference of the customer. The first layer will typically consist of a single
operator screen called a System Overview Screen. The information is in tabular or
map form showing the site locations and is push button selectable. The second screen
RFP# 101216
December 16, 2010

layer will typically display an individual site in tabular/graphic form and again push
button selectable. A third layer of screens will be the individual site component itself
(channel bank, RF network, microwave radio, other site support equipment, etc.),
showing all status information for the particular system component. A final layer
would break down the other site alarms.
A System Health Screen will also be provided to give MOSCAD system-related
status information such as internal SDM3000 RTU status. Also available from the
system health screen are communication statistics relative to number of COS, retry
percentage, and polling frequency. The final screen provided is an alarm summary,
which provides a list of any outstanding alarms and unacknowledged alarms that
have returned to normal.
GMC Screen Navigation

The following is a typical alarm navigation procedure. If an alarm occurs at a
particular site, the system overview screen will indicate a flashing alarm condition for
that site. The operator will then pull up the Site Screen for the alarming system
component. By locating the flashing system component, the operator can determine
the affected equipment. Finally, the operator will pull up the System Component
screen to determine the alarming item and acknowledge the incoming alarm
condition. The System Health screen will be accessed though the System Overview
screen. Access will be available to the Alarm Summary screen from any of the other
screens.
MOSCAD SDM3000 Node Translator (SNT)

The MOSCAD SDM3000 Node Translator (SNT) is the bridge between the GMC
and the MOSCAD SDM3000 RTU network, via the ASTRO 25 IP communication
backbone. MOSCAD will communicate over the backbone using the MOSCAD
seven-layer MDLC protocol. MDLC is a Motorola protocol designed in accordance
with the Open System Interconnection (OSI) model recommended by the
International Organization for Standardization (ISO).
The MOSCAD Programming ToolBox

The MOSCAD SDM3000 Node Translator (SNT) and SDM3000 RTU(s) are
programmed via a DOS-based software package known as the MOSCAD
Programming Toolbox. Each MOSCAD can be programmed locally or remotely
(dialup) via a DOS-compatible laptop computer. One MOSCAD CPU has an external
auto-answer modem for remote ToolBox access. The ToolBox does NOT have a GUI
for these local or remote dial-in devices; therefore, the user must be
experienced/trained with the ToolBox application for this mode of system operation.
These remote dial-in links are also used for system maintenance and upgrades by
means of the ToolBox upload/download capability.

RFP# 101216
December 16, 2010

MOSCAD SDM3000 RTU
The MOSCAD Network Fault Management (NFM) SDM3000 RTU acts as the
primary interface to the site devices. The SDM3000 RTU acts as an intelligent site
management terminal that allows for continuous monitoring of critical site
components and alarms. These include environmental indications, Premisys (TeNSr)
channel bank and TRAK GPS equipment. Additionally, the MOSCAD NFM
SDM3000 RTU allows remote configuration, remote diagnostics, and remote
programming of the TeNSr.
The NFM SDM3000 RTU communicates with GMC via the IP Interface and
forwards any alarms or events to the GMC over the ASTRO 25 WAN.
The NFM SDM3000 RTU also routes alarms information to the FullVision INM and
to the Motorola System Support Center via the IP-interface at each remote site,
located on the ASTRO 25 LAN.
As proposed, this system includes a MOSCAD NFM SDM3000 RTU for each RF
site in the system. Each of the MOSCAD NFM SDM3000 RTUs is provided with
digital and analog alarm inputs, and relay outputs for control of external devices.
These inputs and outputs may be used by the County to interface to site alarm devices
such as power, intrusion, lights, and other site alarms.
Inputs and Outputs Included On Each MOSCAD SDM3000 RTU

48 Digital Inputs (DI) providing 48 dry-contact inputs; any of the inputs may be used
as low-speed counters under application control. The module provides an isolated
current so that the open/closed state of the sensor may be determined. Each of the
inputs is opto-isolated from the remaining circuitry on the module to provide
maximum input surge immunity.
Eight Analog Inputs (AI), can be provided in various options supporting wither eight
4-20 ma inputs; eight ±1 ma inputs; eight ±2 ma inputs; eight ±1 VDC inputs; eight
±2.5 VDC inputs; or eight ±5 VDC inputs. Each of the eight inputs, plus ground and
temperature, are opto-switched into a precision A-to-D converter; ground is measured
so short-term drift may be cancelled and temperature is measured so that the
temperature drift associated with all silicon-based chips may be negated.
16 Digital Outputs (DO) providing 16 low-current relay outputs; 12 of the relays have
Form A contacts and four relays have Form C contacts. Magnetically latched relays
should be used in systems that require long operation from the backup battery when
the mains power fails; electrically energized relays should be used when it is
mandatory that the relays open following loss of power or when the module is
removed from the SDM3000 RTU. Each relay has an internal feedback contact that
the application may use to verify that the relay is open or closed. All connections to
the relays are made via plug-in screw terminals on the module, and all relays have
surge arresting devices installed.

RFP# 101216
December 16, 2010

Example of Local Discrete Alarms
The following Table 5-5 shows various site equipment alarms collected via
MOSCAD I/O modules. MOSCAD is not limited to these alarms. They are just
examples.
Table 5-5 : Typical Site Alarms
Site Environmental Alarms Site Environmental Alarms

Remote Site Intrusion Battery Charger Alarms
Remote Site Smoke Alarm Trunking System Auxiliary Alarms
Building Temperature Alarm Zone Controller Auxiliary Indications/Alarms
Building Humidity Alarm Tower Lights
AC Failure UPS Status/Alarms
AC Arrestor Failure Generator Status/Alarms
5.2.7 MCC7500 System Description

The MCC7500 console features an intuitive, Graphical User Interface (GUI) which ,
operates under the Microsoft Windows® platform and follows the same standards as
other Windows programs around the world. The screen layout is simple and uses
valuable space efficiently. Key information and critical functions are clearly
identified with easy to understand icons. Dispatchers can quickly recognize these
icons instead of reading text, hence maximizing their productivity.
Many tasks can be completed more quickly and easily than ever before with the
MCC7500 consoles. Channels or talkgroups are displayed in on-screen “folders” for
prioritization. Flashing red indicators easily identify incoming emergencies.
Dispatchers can see information about who is calling, such as the time and call type.
Trunked callers can be identified by real names versus numerical IDs.
5.2.7.1 Architecture Overview

The MCC7500 Dispatch Console is Motorola’s IP high-tier radio dispatch console
system designed for use in our ASTRO 25 trunking systems.
Some of the more important features of the MCC7500 Console include:
♦ Seamless integration with ASTRO 25 trunking systems:
Supports the IP protocols of the trunking system’s transport network; no
circuit-switched network to packet-switched network conversion equipment is
necessary

RFP# 101216
December 16, 2010

Encryption and decryption is performed within the dispatch consoles, which
allows true end-to-end encryption in the radio system.
Participation in the radio system’s agency partitioning functionality.
Configuration of the console subsystem via the radio system’s centralized
configuration subsystem (Network Manager) so the user has a single point to
configure the radio system. The configuration subsystem may be accessed
from multiple remote locations so users can still have convenient access while
enjoying the benefits of centralized configuration.
Management of the console subsystem via the radio system’s centralized
network management subsystem so the customer has a single point for
managing faults, accounting, performance, and security of the radio system.
The network management subsystem may be accessed from multiple remote
locations so customers can still have convenient access while enjoying the
benefits of centralized management.
♦ Centralized and/or distributed logging of conventional and trunked radio audio
associated radio call information and certain radio system events.
♦ Higher capacities in numerous areas (64,000 talkgroups, thousands of logging
“tracks”).
5.2.7.2 Connection of MCC7500 to IP Network

Motorola MCC7500 console equipment connects directly to the trunking system’s IP
transport network. It uses the IP packet protocols for passing call control data and call
audio through the system. Figure 5-9 shows a high-level diagram of how Motorola
MCC7500 equipment fits into the ASTRO 25 system.

RFP# 101216
December 16, 2010

Master Site
ZDS
Zone Controller
ATIA
Third Party UCS
Remote Analog ATIA Analyzer Network
LAN Switch
Conventional Management
Station
Router
WAN Router w/
Router w/ Control Station CCGW Playback
CCGW Station
4W Analog
4W Analog Lines Logging
Site
Lines Summing Recorder
Controller
Amplifiers
LAN
LAN
Switch Archiving
Parallel Switch
Non-MCC 7500 Interface
Console Server
Local Analog MCC 7500

MCC 7500
Conventional Console #1
Console #4
Station
Trunking
Local Analog Conventional Stations MCC 7500 MCC 7500
Stations Console #3 Console #2
Console Site (w/ Conventional)

RF Site (Trunking & Conventional)
Router w/
CCGW
4W Analog
Lines Conventional Only Site
Analog Conventional Stations
Figure 5-9: ASTRO 25 Trunking System w/ Motorola MCC7500 Consoles
Elite Dispatch GUI

The Motorola MCC7500 dispatch console uses the Elite Dispatch GUI for displaying
information to and accepting commands from the dispatch console user. The Elite
Dispatch GUI is efficient, easy to use and intuitive, having been refined and proven
through years of use in public safety dispatch center’s around the world.
An example of the Elite Dispatch GUI is shown in Figure 5-10.

RFP# 101216
December 16, 2010

Tool Bars
Resource Radio
Folders Resources
Patch &
Radio
Multi-Select
Resource
Folders
Auxiliary
Inputs/Outputs
Radio
Radio
Resources
Resource
Activity Log
Window
Status Bar
Figure 5-10: Elite Dispatch GUI
The Elite Dispatch GUI is based on Microsoft Windows GUI programming standards
and contains many controls, displays, and features, which are familiar to anyone who
has used Windows-based applications. These features are described in detail in the
following sections.
Pull Down Menus

The Elite Dispatch GUI provides the following pull down menus on a menu bar
across the top of the dispatch window:
♦ Configuration - Provides access to the configuration files used by the Elite
Dispatch GUI. Also allows the dispatch application to be exited.
♦ Edit - Allows various aspects of how audio, resources, and features are presented
to the user on the Elite Dispatch GUI to be edited. Changes made using this menu
are not permanent and are lost when the dispatch application is exited.
♦ View - Allows the dispatch console user to control whether or not the Activity
Log and Auxiliary I/O Windows are shown.
♦ Folders - Allows the dispatch console user to switch between folders, add folders,
and change the folder tab width. Changes made using this menu are not
permanent and are lost when the dispatch application is exited.
♦ Help - Provides access to detailed on-line help for using the Elite Dispatch GUI.
The user may customize which menus are displayed and what they contain via the
Elite Admin application.
RFP# 101216
December 16, 2010

Toolbars
Up to two toolbars may be present across the top of the dispatch window and may be
used to provide quick access to frequently used features. The following are examples
of the items that may be placed in the toolbars:
♦ Clock
♦ General Transmit Button
♦ Monitor Button
♦ All Mute Button
Many other items may be placed in the toolbars. The Elite Admin application is used
to define how many tool bars are displayed and what they contain.
Status Line
A status bar is provided across the bottom of the dispatch window for viewing the
status of the dispatch console as well as various error messages. The most current
status or error message is displayed in the status line until cleared by the dispatch
console user. The dispatch console user may scroll through the last 10 statuses/error
messages to view them and may clear them by using the Features menu on the menu
bar.
Resource Folders
The Elite Dispatch GUI provides up to six resource folders for organizing the various
resources (radio resources, auxiliary input/output resources, etc) which are assigned
to the dispatch console. These folders may be given descriptive names to simplify the
organization of the resources.
The resources on a folder are displayed when the dispatch console user clicks on the
folder tab. Resources on folders that are hidden behind the one being displayed
continue to operate in a normal manner. Radio resource audio on a hidden folder
appears in the appropriate speakers/headsets along with a visual call indication on the
folder tab. If an emergency alarm or call is received on a radio resource that is located
on a hidden folder, a visual emergency indication is displayed on the folder tab.
A resource may be placed on more than one folder at the same time. This allows
customers to create folders for special situations without having to move resources
back and forth between folders.
The Elite Admin application is used to configure how many folders appear on the
Elite Dispatch GUI and which resources appear on each folder. It is also used to put
descriptive names on the folder tabs.
During dispatch operations the dispatch console user may, if so configured by the
Elite Admin application, be able to add, remove, or move resources on the folders. If

RFP# 101216
December 16, 2010

this is done, these changes are not saved if the user logs off or changes configuration
files for the dispatch application.
Up to 36 compressed radio resources may be viewed on one folder when the program
is run in the standard 800 x 600 resolution and there is no patch or multi-select
folders. If patch and multi-select folders are used and are set to the minimum height,
then 31 compressed resources may be viewed. To figure the number of auxiliary
input/output resources that could also be viewed, use the rule of thumb that two
auxiliary resources can fit in the same space as one radio resource. In other words,
instead of 10 radio resources, 20 auxiliary resources could fit in the same space. If the
program is run in 1024 x 768 resolution, there is room for even more radio and
auxiliary resources per folder.
Radio Resources
Voice communication paths in the radio system are represented as radio resources on
the Elite Dispatch GUI. Radio resources are also referred to as “tiles” on the Elite
Dispatch GUI. These radio resources are used by the dispatch console user to
communicate on and control the radio system.
The following radio resources are supported:
♦ Trunked Talkgroups
♦ Trunked Announcement Groups
♦ Trunked Private Calls
♦ Analog Conventional Channels
Indicators and Controls

A radio resource contains indicators and controls that allow the dispatch console user
to monitor and control various aspects of the radio channel. Examples of the
indicators and controls that may appear on a radio resource include:
♦ Instant Transmit Button
♦ Transmit Active/Transmit Busy Indications
♦ Patch Active/Patch Busy Indications
♦ Received Call Indication
♦ Received Call Stack
♦ Individual Volume Control
The types of indicators and controls that appear on the radio resource depend on the
type of radio channel it represents and how it has been configured in the Elite Admin
application. The radio resource may be configured to always show the indicators and
controls or to allow the dispatch console user to hide them when not in use to save
space on the screen.

RFP# 101216
December 16, 2010

Compressed, Larger Compressed, and Expanded Resources
Figure 5-11 shows a radio resource that allows the dispatch console user to hide the
indicators and controls. This is also called a “compressed” resource. Notice the small
arrow button that allows the resource to be opened and closed to show the controls
and indicators.
Flap Closed Flap Open
Figure 5-11: Compressed Radio Resource
Figure 5-12 shows a radio resource that always shows some of the indicators and
controls, but allows the dispatch console to hide some of the others. This is also
called a “larger compressed” resource.
Flap Closed Flap Open
Figure 5-12: Larger Compressed Radio Resource

RFP# 101216
December 16, 2010

Figure 5-13 shows a radio resource that always shows the indicators and controls.
This is also called an “expanded” resource. Notice there is no arrow button on the
resource.
Figure 5-13: Expanded Radio Resource
Full parallel status for radio resources is reflected across all the dispatch consoles that
have these radio resources assigned on them. That is, any activity or change on a
radio resource appears on all dispatch consoles that have that resource assigned on
them.
Received Call Stack

The received call stack provides the dispatch console user with a visual record of the
most recent inbound calls on radio resources. This allows the dispatch console user to
keep track of calls during busy traffic periods.
Outbound calls on radio resources from dispatch consoles (both the dispatch console
containing the received call stack or parallel dispatch consoles) are not shown in the
received call stack.
The calls are displayed in list format on a radio resource with the most recent calls at
the top of the list. The number of calls displayed in the list is configurable as is the
type of information displayed. The types of information that can be displayed are unit
ID, unit ID alias, site ID, zone ID and, type of call and time. If an alias is available
for a piece of information it is displayed, otherwise the raw information is displayed.
Figure 5-14 shows a radio resource containing a received call stack.

RFP# 101216
December 16, 2010

Received
Call Stack
Figure 5-14: Received Call Stack on a Radio Resource
The received call stack provides a quick way for a dispatch console user to respond to
calls in the stack. Various types of mouse clicks on calls in the stack provide the
dispatch console user with different ways to reply to the call.
The received call stack is configurable on a per-resource per-console basis, so a
resource on one dispatch console can have it while the same resource on another
dispatch console does not have it.
The received call stack has a fixed memory of 25 calls, but the number of calls that
are displayed is configurable via the Elite Admin application. The number displayed
may be set anywhere from three to 24 calls in increments of three. Regardless of how
many calls are actually displayed, the dispatch console user can always scroll through
all 25 calls in the stack’s memory.
Stack display size is configured on a per radio resource per dispatch console basis.
That is, each resource on a dispatch console may have different sized stack displays
and the same resource on different dispatch consoles may have different sized stack
displays.
The dispatch console user can delete individual calls from the received call stack. All
of the calls listed in a received call stack can also be deleted with a single action.
Auxiliary Input and Output Resources

Control relays and input buffers are represented as auxiliary input and output
resources on the Elite Dispatch GUI. These auxiliary input and output resources are
used by the dispatch console user to monitor the state of input buffers and
monitor/control the state of control relays.
The auxiliary input and output resources are represented by various graphical icons
that change their appearance based on the state of the resource. The particular icon
that is associated with an input or output is configured by the Elite Admin
application. Examples of some of the icons that may be used are shown in Figure
5-15

RFP# 101216
December 16, 2010

Icon for Input Buffer (shown in Active State)
Icon for Control Relay (shown in Active State)
Icon for Control Relay (shown in Inactive State)
Figure 5-15: Auxiliary Input/Output Resource Icons
Auxiliary input and output resources may be grouped together so that they can be
moved or assigned/de-assigned as a group. This is useful for situations where the
auxiliary input output resources are being used to interface to comparators or other
devices that require multiple control relays or input buffers.
Auxiliary output resources may be protected by a “safety switch” to help prevent
unintended activation or deactivation. In order to activate or deactivate an auxiliary
output that is protected by a safety switch, the dispatch console user must first press
the safety switch and then press the auxiliary output.
Latched auxiliary input resources may also be protected by a “safety switch” to help
prevent unintended clearing of an active input. In order to clear a latched auxiliary
input that is protected by a safety switch, the dispatch console user must first press
the safety switch and then clear the auxiliary input.
Full parallel status for auxiliary inputs and outputs is reflected across all the dispatch
consoles that have the auxiliary inputs and output resources assigned on them. That
is, if an auxiliary input or output changes state, the change of state is reflected on all
the other dispatch consoles that have that auxiliary input or output assigned on them.
Auxiliary input and output resources may also be placed on a separate auxiliary input
and output window that is capable of being hidden when not needed. A button on one
of the tool bars is used to open and hide the window. This allows the dispatch console
user too easily and quickly access auxiliary input and output resources that are
infrequently used without permanently consuming space on the screen.
Patch and Multi-Select Folders

The patch and multi-select features are accessed via a set of dedicated folders on the
Elite Dispatch GUI. These folders are smaller than the resource folders and may be
placed on the screen to suit the dispatch console user’s preferences. The placement is

RFP# 101216
December 16, 2010

done in the Elite Admin application. There can be up to sixteen patch folders and
three multi-select folders.
Patch Folders
Clicking on one of the patch folder tabs brings it into view. The patch group is then
opened by clicking on the left-most button on the folder. Once the patch group is
open, the patch group is editable and members may be added or removed from the
patch group by clicking on the desired radio resources. Note that patch groups are
active whenever there are members assigned to them. This is true even if the patch
group is not open.
The members of the patch group are shown on the patch folder along with the status
of each member (patched or pending). The resources in the patch also show an
indication that they are in a patch group.
Some patch groups contain members that were pre-assigned by the Elite Admin
application. These patch groups become active as soon as possible after the dispatch
console begins using the configuration file that contains the pre-assigned patch
groups. The dispatch console user can add/remove members from the pre-assigned
patch group, but these additions/removals are lost when the dispatch console either
re-loads the configuration file or changes to a different configuration file.
A patch transmit button is provided on the patch folder to allow the dispatch console
user to easily transmit on all members of the patch group with a single button press.
Figure 5-16 shows an example of a patch folder containing some radio resources.

RFP# 101216
December 16, 2010

Figure 5-16: Patch Folder
Multi-Select Folder
Clicking on one of the multi-select folder tabs brings it into view. The multi-select
group is then opened by clicking on the left-most button on the folder. Once the
multi-select group is open, the multi-select becomes active and members can be
added or removed from the group by clicking on the desired radio resources. Closing
the multi-select folder (by clicking on the left-most button a second time) deactivates
the multi-select group.
Note that this operation is different from that of the patch folders. A dispatch console
can only have one multi-select group active at a time, but it can have multiple patch
groups simultaneously active.
The members of the multi-select group are shown on the multi-select folder.
Some multi-select groups contain members that were pre-assigned by the Elite
Admin application. The dispatch console user can add/remove members from the pre-
assigned multi-select group, but these additions/removals are lost when the dispatch
console either re-loads the configuration file or changes to a different configuration
file.
Figure 5-17 shows an example of a multi-select folder containing some radio
resources.

RFP# 101216
December 16, 2010

Figure 5-17: Multi-Select Folder
Activity Log Window

The activity log window can be used by the dispatch console user as a point of
reference for all calls coming into the dispatch console. The activity log shows call
information associated with all incoming radio calls such as the name of the radio
resource and the time of the call. Incoming calls from all radio resources assigned to
the dispatch console are displayed in the activity log.
Figure 5-18 is an example of an activity log window.
Activity Log
Resource
Tile
List of Calls
Figure 5-18: Activity Log Window
Up to 1,000 calls can be held in the activity log. The most recent call is on the top of
the list and the oldest at the bottom. Once the list is filled, the oldest calls are
discarded as new calls come in. The dispatch console user may resize the activity log
to show various numbers of calls. For example, when there is light activity, the
dispatch console user may choose to show only a few calls. During busy hours, the
dispatch console user may view more calls by simply dragging the lower right hand
corner of the activity log (making it longer) to see additional calls.
Dispatch console users may respond to incoming calls simply by clicking on a call in
the list. When this is done, the entry appears highlighted and the name of the radio
resource appears on the activity log resource tile at the top of the activity log. The
dispatch console user can then press the instant transmit button on the activity log
resource tile to communicate with that radio resource.
The information displayed by the activity log can be customized to suit the dispatch
console user’s needs. The activity log can be configured to show combinations of
Resource Name, Unit ID or Alias, Status Number or Alias, Receiving Site ID,
Receiving Zone ID and Time. This configuration is done via the Elite Admin
application and, if so configured, via the dispatch console user interface.
There are two levels of control over whether or not the activity log is displayed on a
dispatch console. The first level is via the Elite Admin application, which controls

RFP# 101216
December 16, 2010

whether or not a dispatch console has the capability of displaying the activity log.
The second level is via the dispatch console user interface where the dispatch console
user can choose to view or not view the activity log. Note that if the dispatch console
has not been given the capability of displaying the activity log, then the dispatch
console user cannot see the activity log at all.
The number of lines that are initially displayed by the activity log is configurable via
the Elite Admin application or the dispatch console user interface. The number of
lines that are displayed may also be changed in real time by changing the size of the
activity log window using standard Microsoft Windows resizing techniques. The user
can scroll through all the entries in the activity log even if they cannot all be
displayed at once.
The information listed in the activity log can be stored in a text file on the dispatch
console’s hard disk. The size of the text file can be specified to be between 1 MB and
20 MB. When the file fills up, new data overwrites old data beginning with the oldest
data. All data associated with a call is logged to the file, regardless of what portion of
the data is actually shown in the activity log window.
Help
The dispatch console is designed to allow the dispatch console user to quickly access
information on how to use its features. This help is available right on the dispatch
console graphical user interface.
There are three types of help available to the dispatch console user: On Line, Micro,
and Tool Tips.
Online Help
Online Help provides detailed information on how to use the dispatch console. The
user accesses Online Help via the Help menu on the menu bar. The user can search
for topics or keywords to quickly find the desired information or the user can use a
table of contents to find the information. The information is displayed in a pop-up
window on the dispatch user interface.
Online Help allows new dispatch console users to shorten their learning curve and
more experienced dispatch console users to quickly remember how to operate
seldom-used features.
Micro Help
Micro Help provides information about the state of controls or indicators in a
resource tile. When the cursor is placed over a control or indicator on a resource tile,
a description of the control or indicator’s state is given across the bottom of the
resource tile. Figure 5-19 illustrates Micro Help text on a radio resource. The text
across the bottom of the resource describes the icon to which the cursor is pointing.

RFP# 101216
December 16, 2010

Micro Help
Text
Figure 5-19: Micro Help on a Radio Resource
The text displayed by the Micro Help feature may be edited via the Elite Admin
application.
Micro Help allows a dispatch console user to view the status of a control or indicator
textually instead of graphically.
Tool Tips Help

Tool Tips Help provides information about tool bar buttons and menu bar menus to
the dispatch console user. When the cursor is placed over a toolbar button, the
button’s name appears in a small pop-up window next to the cursor and a short
explanation of the button appears in the status bar at the bottom of the dispatch user
interface window. When the cursor is moved across a menu item in a menu, a
description of the menu item appears in the status bar at the bottom of the dispatch
user interface window.
The text displayed by the Tool Tips feature may be edited via the Elite Admin
application.
Tool Tips allow a dispatch console user to see a short explanation of the button or
menu item of interest quickly.
Elite Admin Application

The manner in which resources and audio are presented to the dispatch console user
on the MCC7500 dispatch console is managed by the Elite Admin application. The
look and feel of the Elite Dispatch GUI, as well as how received audio is routed on
the dispatch console, can be optimized to meet customers’ needs.
The following sections describe how configurations for the Elite Dispatch GUI are
managed and what can be configured on the dispatch console via the Elite Admin
application.

RFP# 101216
December 16, 2010

Managing Dispatch Screens
When it first starts running, the Elite Dispatch GUI application reads a configuration
file that tells it what should appear on the GUI and how received audio should be
routed on the dispatch console. These configuration files are created by properly
trained personnel using the Elite Admin application. They are often called “ELT”
files because their file names have an “.elt” suffix.
Multiple ELT files may be created to address different situations. For example,
different ELT files can be created for different shifts in a dispatch center if the scope
of dispatching changes significantly between shifts. Alternatively, different
configuration files can be created for individual dispatch console users to meet their
personal preferences.
A dispatch console user may switch between ELT files during normal operations, but
cannot access any resources while the original file is being closed and the new file is
being opened.
The ELT files may be stored locally on the dispatch console computer, on a different
dispatch console computer, or in a central location. The choice on where to store the
files depends on many factors such as:
♦ Accessibility to the files - Do all dispatch console users need to access all the
ELT files? If multiple agencies share a dispatch center, do they want to be able to
access each other’s files?
♦ Ease of managing the files - Are the dispatch consoles located in one physical
location or are they geographically separated? Is one person managing the files or
are multiple people managing them?
♦ The topology of the radio system’s IP network - Are there servers (such as
Domain Controllers) located at the dispatch console location that can be used to
store the files? If the files are stored on a server, do the dispatch consoles have to
retrieve them across WAN links?
By default, when the Elite Dispatch GUI application starts up it asks the dispatch
console user to specify which ELT file it should use. If this is not the customer’s
preferred mode of operation, the dispatch console can be configured so that it
automatically opens a particular ELT file.
Admin Capabilities
The Elite Admin application allows a properly trained user to do the following:
♦ Create new configurations
♦ Modify existing configurations
♦ Save configurations
♦ Determine how many toolbars are present

RFP# 101216
December 16, 2010

♦ Determine items that should go on the toolbar(s) and where on the toolbar(s) they
should go
♦ Determine the number of resource folders
♦ Determine the number of patch/multi-select folders
♦ Name the resource folders and patch/multi-select folders
♦ Determine the location of patch/multi-select folders
♦ Determine the height of patch/multi-select folders (e.g., taller if there are many
members in the groups)
♦ Create pre-assigned patch/multi-select/primary groups
♦ Determine if dispatch console users have the ability to assign and de-assign
resources
♦ Determine if the activity log is shown initially and where on the screen it is
shown (dispatch console users may still hide or show the activity log)
♦ Assign/unassign radio and auxiliary input/output resources to various folders
♦ Determine location of radio and auxiliary input/output resources in the folders
(dispatch console users may temporarily change the locations by dragging and
dropping the resources)
♦ Determine where features are placed on each radio resource
♦ Modify the icons used for resource features
♦ Add a safety switch on radio resources
♦ Determine the size of each radio resource (compressed, larger compressed, or
expanded)
♦ Determine whether selected radio audio stays in a speaker or moves to a headset
when headsets are used (this is done on a per-resource, per-console basis)
♦ Determine border color for each radio resource
♦ Determine audio routing of resources to speakers
♦ Determine icons used for auxiliary input and outputs
♦ Determine if auxiliary inputs and outputs appear in a separate window
♦ Set initial volume level of each radio resource
♦ Determine if auxiliary outputs are safety switch protected
♦ Determine border color for each auxiliary input and output
♦ Modify Tool Tips and Micro Help text
Conventional Channel Gateway

Conventional channels are much more integrated into the trunking systems than in
previous radio – console configurations. The zone controller manages conventional
channels in a manner similar to how it manages trunked talkgroups. The physical

RFP# 101216
December 16, 2010

interface to the analog conventional stations also changes from previous radio
systems. RF site routers are fitted with 4-wire interface cards, which are connected to
the analog stations.
Doing this provides two key benefits:
♦ It allows the conventional audio to use the same transport network as the trunked
audio
♦ It reduces the number of individual interface devices in the radio system
The portion of the router hardware and software that support the conventional
stations is called the Conventional Channel Gateway (CCGW).
To interface to analog conventional stations, the routers must be able to vocode and
de-vocode the conventional audio, key the station, detect when the station sends
audio to the router and detect when a parallel deskset console transmits on the station.
This capability has been added to the routers used in Motorola’s trunking systems.
Motorola has proposed CCGW equipment to support eight (8) of the conventional
stations.
Physical Interface to Station

The Motorola MCC7500 conventional channel gateway provides four ports (per
router) to which analog conventional base stations may be connected. Each port
contains the following inputs and outputs.
♦ 600 Ohm, balanced analog audio input - Used to accept radio audio from the base
station
♦ 600 Ohm, balanced analog audio output - Used to send console transmit audio to
the base station
♦ Input buffer - Used to detect Carrier Operated Relay (COR) closure in the base
station
♦ 1 Amp, 24 VDC relay output - Used for relay keying of the base station
Each port is manifested as an RJ45 connector on the router.
Supported Configurations
The Motorola MCC7500 conventional channel gateway supports the following types
of analog conventional base stations.
♦ R1
♦ T1R1
♦ T1R1 w/Paging
♦ T2R2
♦ T4R4
RFP# 101216
December 16, 2010

♦ T8R8
♦ T12R12
♦ T14R14
TnnR channels must be supported using combinations of T1R1 channels.
Auxiliary Inputs and Outputs

The MCC7500 supports the ability to control or monitor Auxiliary inputs and outputs
(Aux I/Os) that allow customers to control external devices via relay closures and
sense the state of external devices via input buffers from the dispatch console. These
Aux I/O’s are referred to as Public Aux I/Os. Public Aux I/Os are accessible by more
than one dispatch console. A change in state of the Aux I/O is reflected across all of
the dispatch consoles that have it assigned on their user interfaces. These Aux I/Os
are typically physically located in a common location that is shared by all the
dispatch consoles.
The Motorola MCC7500 dispatch console supports Public Aux I/Os by accessing and
controlling MOSCAD RTUs and displaying the status of the RTUs’ inputs and
outputs on its user interface. A separate window to display the MOSCAD inputs and
outputs is not required on the dispatch console.
Graphical icons provided by the dispatch console GUI are used to represent both the
function and state of relay outputs. For example, an icon consisting of a light bulb
may be used to represent a relay output that is controlling lighting of some type. The
dispatch console user would click on the button associated with the icon to change
the state of the relay output and the icon would change between a lighted bulb and an
unlighted bulb to reflect the state of the lighting.
Graphical icons are also used to provide a visual indication of both the function and
state of external inputs. For example, an icon consisting of a door may be used to
represent an external input that is connected to a door position sensor. The door can
be shown in the open state when the sensor says the door is open and it can be shown
in the closed state when the sensor says it is closed.
Multiple dispatch consoles may monitor and control the same relay output and/or
external inputs. In this case, state changes are indicated across all dispatch consoles
simultaneously.
Individual relay outputs can be configured so that they require a safety switch to be
pressed before they respond to any commands from the dispatch console user. A
relay output on one dispatch console can be protected by a safety switch while the
same relay output on a different dispatch console is not. The resetting of latched
inputs may also be protected by using the safety switch.

RFP# 101216
December 16, 2010

Supported Aux I/O Configurations
The following Aux I/O configurations are supported.
♦ Momentary Input - This is an input where the user interface always shows the
true state of the input. If the input is active, it is shown as active. If it is not active,
it is shown as not active.
♦ Latched Input - This is an input where the user interface does not necessarily
show the true state of the input. When the input goes active, the user interface
shows the state as active. The display will continue to show the state as active
even if the input changes to the inactive state. A dispatch console user must
manually reset the display to return it to the inactive state. Note that a dispatch
console user cannot clear the display until the input itself is in the inactive state.
♦ Momentary Output - This output relay is activated when the dispatch console user
presses the button on the user interface and deactivated when the dispatch console
user releases the button.
♦ Latched Output - This output relay changes state only when the dispatch console
user presses the button. The release of the button has no effect on the state of the
relay. One press activates the relay; the next press deactivates the relay.
♦ Interlocked Latched Output - This latched output relay is part of a group of
latched output relays. Only one of the relays in the group may be active at a time.
Pressing the button for a relay automatically deactivates the previously active
relay. Pressing the same button twice does not deactivate that relay. There is
always one and only one relay active in the group at all times. Interlocked relays
work in a “break before make” fashion; that is, the previously active relay is
deactivated before the new relay is activated.
Aux I/O Hardware

The MOSCAD SDM 3500 RTU is used to support most dispatch console Aux I/O
needs. The SDM 3500 RTU is rack mountable in a standard 19-inch rack and is one
rack unit high.
The SDM 3500 RTU is capable of supporting up to 16 outputs and 48 inputs.
Expansion chassis can be added to increase the number of inputs and outputs. The
output relays are capable of switching 1A @ 24VDC or 1A @ 24VAC. Input buffers
are capable of sensing a dry closure through 1000 feet or less (round trip) of 24 AWG
wire.
The RTUs can be physically located at console sites, trunking RF sites or analog
conventional RF sites. The dispatch consoles and RTUs communicate with each other
across the radio system’s IP transport network. This allows much greater flexibility in
putting Aux I/Os where they are needed compared to CENTRACOM Gold Series,
which required all the Aux I/Os to be located in the CEB.

RFP# 101216
December 16, 2010

The RTU provides single pole Form A relay outputs. Double pole, Form B, or Form
C relays must be implemented using external relays that are controlled by the RTU
relays.
5.2.7.3 Feature Descriptions

High-level descriptions for all the features supported by the Motorola MCC7500
dispatch console are given in this section.
Centralized System Management

The Motorola MCC7500 console system is configured and managed by the trunking
system’s configuration manager, fault manager, and performance reporting
applications. This provides the customer with a single point for configuring and
managing the entire radio system, including the console portion.
The Motorola MCC7500 console system is able to control certain conventional
resources in addition to the trunking system. The trunking system’s configuration
manager, fault manager, and performance reporting applications also configure and
manage the parts of the system interfacing to the conventional resources.
End to End Encryption

The addition of secure capability to the dispatch console allows true end-to-end
encryption in the radio system. This provides the highest degree of security possible
to those customers who wish to take advantage of this feature.
The dispatch consoles support multiple encryption algorithms and multiple secure
keys to allow them to access and control talkgroups from different agencies, if
necessary.
Gaining Access to Resources in the Communication System
Resource Assignment
Resource Assignment is a feature that allows a dispatch console user to choose which
radio resources are monitored and controlled by the dispatch console. Resources must
be assigned before they can be monitored and controlled. Once the assignment is
made, the dispatch console starts receiving audio and status updates for the resource.
The resource assignment feature works in conjunction with the security group feature
of the radio system’s network manager. The security group feature determines which
radio resources a given dispatch console user has the right to access. Those radio
resources are then eligible to be assigned on a dispatch console via the resource
assignment feature.

RFP# 101216
December 16, 2010

Resource Assignment allows the flexibility to change which resources are monitored
and controlled at a dispatch console. This can be useful, for example, on shift
changes. It does not force one shift to deal with resources that are only used by a
different shift.
Resources can be unassigned when they are no longer needed at a dispatch console.
Once resources are unassigned, the dispatch console stops receiving audio and status
updates for the resource.
Aux I/O Assignment

Aux I/O Assignment is a feature that allows a dispatch console user to choose which
Aux I/Os are monitored and controlled by the dispatch console. Aux I/Os must be
assigned before they can be monitored and controlled. Once an Aux I/O assignment
is made, the dispatch console starts receiving status updates for the Aux I/O.
Aux I/O Assignment allows the flexibility to change which Aux I/Os are assigned at
a dispatch console. This can be useful, for example, on shift changes. It does not
force one shift to deal with Aux I/Os that are only used by a different shift.
Aux I/Os can be unassigned when they are no longer needed at a dispatch console.
Once Aux I/Os are unassigned, the dispatch console stops receiving status updates for
the Aux I/O.
Resource Status
The Resource Status feature informs a dispatch console user of the operational
condition of radio resources and Aux I/Os. This gives the dispatch console user
greater control by knowing which resources are available and which are not available.
Operational failures of the resources and Aux I/Os can be displayed to the dispatch
console user so the lack of operational ability is known.
Configuration of Audio Presentation for Resources
Audio Destination Assignment

A dispatch console supports multiple speakers and can be configured so that the
audio associated with different resources is routed to different speakers at the
dispatch console. Audio Destination Assignment is a console feature that allows a
dispatch console user to choose which audio destinations (speakers) are to be used for
a given resource.
Audio for a resource is generally directed to one of two destinations, depending upon
the resource’s current select status. Selected resources have their audio sent to the
speaker designated as the select audio destination for that resource. When a resource
is not selected, its audio is sent to the speaker designated as the unselect audio
destination for that resource. In most cases, a single speaker is designated as the

RFP# 101216
December 16, 2010

select audio destination for all resources monitored by that console. In this case,
whichever resource is currently selected has its audio presented in that speaker.
On some console installations, it may be desirable to route audio for a resource to a
particular destination regardless of that resource’s select status. This is accomplished
by setting a resource’s select audio destination to be the same as its unselect audio
destination. Speakers configured in this way are often referred to as “dedicated” or
“monitor” speakers.
Basic Audio (Talk/Listen) Functions
Single-Select
The Single-Select feature allows only one radio resource to be selected at a time.
When a resource is single-selected, the previously selected resource becomes
deselected.
The Single-Select feature is active when there are no Multi-Select groups open. When
a Multi-Select group is closed without opening another Multi-Select group, the
Single-Select feature becomes active, and the resource that had been selected prior to
opening a Multi-Select group is once again selected.
Single-Selecting a resource routes the inbound audio on the resource to the
designated speaker allowing that audio to be easily distinguishable from the other
audio at the dispatch console. It automatically raises the resource’s individual volume
level to full so inbound audio on that resource can be heard clearly. It also designates
that resource as the one to be used by console features such as General Transmit,
Monitor, and Page PTT.
The main advantage of the Single-Select feature over the Multi-Select feature is that
the previously selected resource is deselected when another resource is selected. This
saves having to deselect one resource before selecting another.
Multi-Select
The Multi-Select feature allows a dispatch console to define groups of selected radio
resources. When a Multi-Select group is opened, all of the resources in the group are
simultaneously selected. A dispatch console can support multiple Multi-Select
groups, each of which supports multiple, potentially overlapping, resources
If a Multi-Select group is opened while another Multi-Select group is open, the first
group is closed and all of its resources deselected before the second group is opened.
If a Multi-Select group is opened while no other Multi-Select group is open, the
Single Selected resource is first deselected.
When a Multi-Select group is closed without opening another Multi-Select group, the
Single Select feature becomes active and the resource that had been selected prior to
opening the Multi-Select group is once again selected.
RFP# 101216
December 16, 2010

Resources can be added or removed from a Multi-Select group while it is open or
while it is closed.
Multi-Selecting a group of resources routes the inbound audio on the resources to the
resources’ select audio destinations, allowing that audio to be easily distinguishable
from the other audio at the dispatch console. It automatically raises the resources’
individual volume level to full, so inbound audio on the resources can be heard
clearly. It also designates those resources as the ones to be used by console features
such as General Transmit, Monitor, and Page PTT.
The Multi-Select feature has two advantages over the Single Select feature. It allows
multiple resources to be selected simultaneously. It also allows groups of resources to
be defined and stored so that multiple resources can be conveniently selected and
deselected. The resources of Multi-Select groups can also easily be simultaneously
transmitted on without having to open the Multi-Select group by using the APB
Transmit feature.
Inbound Call Indication

The Inbound Call Indication feature is used to indicate audio activity on a radio
resource. If the resource is selected on the dispatch console, the indication flashes
when inbound audio is detected. If it is not selected on the dispatch console, the
indication does not flash. The indication is not affected by the select status of the
resource on any other dispatch console.
It is also used to associate audio being heard from the dispatch console’s speakers
with a resource.
The Inbound Call Indication can have different sources depending on the type of
resource on which it appears. For trunked resources, the source is the trunking
controller. For some conventional resources, the source can be an input that detects
an external dry closure. This is called a Carrier Operated Relay (COR) Input. For
some conventional resources, the source is audio activity on the receive path from the
station. This is called VOX detection.
Individual Resource Volume Control

The Individual Resource Volume Control feature allows the dispatch console user to
change the level at which each resource is mixed into a speaker. (It is common to
have the audio from many resources routed to the same speaker, especially when
these resources are unselected.) The Individual Resource Volume Control feature can
be used at individual dispatch consoles to lower the volume level of less important
resources and raise the volume level of resources as they become important.
The initial volume level is set when the resource is assigned. The volume level for a
resource is automatically raised to the full volume level when the resource is selected.
If the volume level is adjusted while a resource is selected, it remains at the new

RFP# 101216
December 16, 2010

volume level even after the resource is deselected. If the resource’s volume level is
not adjusted while the resource is selected, deselecting the resource restores its
volume level to its volume level in effect prior to being selected.
All Mute
The All Mute feature is used to mute all of the audio on resources that are not
currently selected at a dispatch console. When the All Mute feature is activated, all
audio on resources that are not selected is muted until the All Mute feature is
deactivated or a certain amount of time elapses, typically 30 seconds. The amount of
time the All Mute feature stays active and the amount of attenuation it applies to the
audio are programmable through the radio system’s configuration application.
If a resource’s individual volume setting is such that it is lower than the All Mute
feature’s attenuated level, the resource’s volume setting will not be changed by the
All Mute feature. That is, the dispatch console will not increase the resource’s
volume setting above the level set by the dispatch console user.
The All Mute feature is used when the dispatch console user does not want to be
disturbed by the audio from the unselect resources. Using the All Mute feature is
better than turning down the volume of the Unselect speaker because the volume is
restored automatically when the All Mute feature is deactivated.
Acoustic Cross Mute

The Acoustic Cross Mute feature is used to prevent acoustic feedback from occurring
when dispatch consoles are physically located near each other. Dispatch consoles that
are monitoring the same radio resource can normally hear each other’s outbound
audio transmissions. This is called parallel operator audio. If two dispatch consoles
are physically close to each other and the parallel operator audio appears in a speaker,
the potential exists for a feedback condition between the speaker on the non-
transmitting dispatch console and the microphone on the transmitting dispatch
console.
The Acoustic Cross Mute feature provides the means to specify groups of dispatch
consoles, which mute parallel operator audio on all radio resources that they have in
common.
High Speed Mute

The High Speed Mute feature allows an external device to provide a dry contact
closure to the dispatch console subsystem that, when activated, mutes the receive
audio of a conventional radio resource at all dispatch consoles monitoring that
resource. The audio received remains muted as long as the closure is present, and un-
mutes when it is removed.

RFP# 101216
December 16, 2010

The High Speed Mute feature provides the customer with the means to control what
audio appears at the dispatch consoles for a given conventional radio resource.
General Transmit
General Transmit is a feature that initiates a voice transmission on the currently
selected resources. General Transmit is one of the most convenient methods for
transmitting since it can be initiated with the footswitch, the headset transmit button,
the microphone transmit button, or the General Transmit API functions.
General Transmit is a medium-priority transmission. Please refer to the Transmission
Priority Levels feature on the following page for more information on transmit
priorities.
It is important to note that a dispatch console can transfer control of an active General
Transmit freely between the General Transmit API functions, the headset transmit
button, the microphone transmit button and the footswitch while not losing the
transmission. This can be used to free up a dispatch console user’s hands for other
activities such as writing notes.
The General Transmit feature provides easy access to transmitting on the selected
resources.
Instant Transmit
Instant Transmit is a feature that allows a dispatch console user to initiate a
transmission on a specific resource regardless of its select state. It is the most direct
method of transmitting on a resource.
Instant Transmit is a high-priority transmission. Please refer to the Transmit Priority
Levels feature on the following page for more information on transmit priorities.
It is important to note that the dispatch console user can Instant Transmit even when
the dispatch console user is currently performing a General Transmit or APB
Transmit. In this case, microphone audio will be sent to both the selected resource(s)
and the one upon which is being instantly transmitted.
The Instant Transmit feature gives the dispatch console user an additional level of
control that is not available with the General Transmit feature. It gives a dispatch
console user the ability to transmit quickly on a resource that is not selected. It allows
a dispatch console user to monitor the audio from the selected resources in the
headset, and simultaneously transmit to another resource. It also allows a dispatch
console user to take over a lower-priority transmit from a parallel dispatch console.
Instant Transmit Safety Switch

Instant Transmit Safety Switch is a feature that requires a dispatch console user to
press a “safety switch” before initiating an instant transmit on a specific resource

RFP# 101216
December 16, 2010

(regardless of whether it is selected or not). This helps ensure the dispatcher does not
accidentally instant transmit on a particular radio channel.
APB Transmit
APB (All Points Bulletin) Transmit is a feature that initiates a voice transmission on
the resources of a Multi-Select group. An APB Transmit control on a dispatch
console must have one and only one Multi-Select group associated with it.
APB Transmit is a high-priority transmission. Please refer to the Transmit Priority
Levels feature in the following section for more information on transmit priorities.
The APB Transmit feature allows transmission to all resources in its associated
Multi-Select group even when the group is closed.
The APB Transmit feature provides easy access for transmitting to a pre-selected
group of resources. APB Transmit is commonly used to make an announcement to
many radio users. It also allows a dispatch console user to take over a lower priority
transmit from a parallel dispatch console.
Transmit Priority Levels

The Transmit Priority Levels feature is a hierarchy of transmit privileges for different
types of transmissions on the same dispatch console or between dispatch consoles. It
provides an orderly and consistent method for allowing higher priority transmissions
to take over resources from lower priority transmissions.
The priority levels from highest to lowest are:
♦ Primary supervisor console instant transmit or APB transmit
♦ Secondary supervisor console instant transmit or APB transmit
♦ Non-supervisor console instant transmit or APB transmit
♦ General transmit on any type of console (single- or multi-select)
♦ Patch transmit on any type of console
♦ Console Transmits While Receiving Audio
The Console Transmits While Receiving Audio feature allows a dispatch console to
receive audio from other radio resources while transmitting on a particular radio
resource. This allows a dispatch console user to hear audio from other resources
while transmitting.
Note that this is different from full duplex audio on a single radio resource.

RFP# 101216
December 16, 2010

Resource Transmit Status - Transmitting
The Resource Transmit Status - Transmitting feature is used on a per dispatch
console basis to indicate when a dispatch console is transmitting on a resource. A
visual indication is provided on the user interface to indicate it is transmitting.
Each dispatch console uses the Resource Transmit Status - Transmitting feature to
display its own transmit status. It is not used to display the status of parallel dispatch
consoles. Refer to the Resource Transmit Status - Parallel MCC7500 Op Busy feature
for more information about parallel dispatch console status.
Resource Transmit Status - Parallel MCC7500 Op Busy

The Resource Transmit Status - Parallel MCC7500 Op Busy feature is used to
indicate when a parallel Motorola MCC7500 dispatch console is transmitting on a
resource. A visual indication is provided on the non-transmitting dispatch consoles to
indicate a parallel dispatch console is transmitting. This feature, in conjunction with
the Resource Transmit Status - Parallel Non-MCC7500 Op Busy feature, provides the
means for a dispatch console user to know if a particular resource is available for use.
The dispatch console user can see the alias of the parallel Motorola MCC7500
dispatch console that is transmitting on either trunked or conventional resources.
Each dispatch console uses the Resource Transmit Status - Parallel MCC7500 Op
Busy feature to display the parallel console transmit status of each resource to which
it has been assigned.
Resource Transmit Status - Trunking Busy/Callback

The Resource Transmit Status - Trunking Busy/Callback feature is used to indicate
when a trunking resource is not available for a dispatch console user to use and to
alert the user when it becomes available. Audible indications are provided on the
dispatch console to indicate a trunking resource is not available and when it becomes
available. This feature allows the dispatch console user to know when a trunked
resource is available again without having to try to transmit on it continuously.
Trunked Base Station/Repeater Control

The Repeat Control feature (also known as Repeat Enable) allows a dispatch console
user to enable and disable the ability of radio users in a talkgroup to hear the
transmissions of other radio users in that talkgroup. When the feature is enabled on a
talkgroup, transmit audio from a radio is made available to all of the radios
monitoring the talkgroup. If the feature is disabled on a talkgroup, transmit audio
from a radio is not made available to other radio users monitoring the talkgroup. In
either case, the radio’s transmit audio is routed to the dispatch consoles.

RFP# 101216
December 16, 2010

When repeat control is enabled or disabled, all dispatch consoles with this resource
assigned are updated with the current status of the feature. This feature can be
controlled from any dispatch console.
System Access Priority Select (Normal/Tactical)

The System Access Priority Select feature allows a dispatch console user to select the
relative system access priority of a trunked resource within the resource’s
communication system. Currently, there are only two possible priorities: NORMAL
priority and TACTICAL priority. Call requests from a trunked resource with
TACTICAL priority have priority over call requests from a trunked resource with
NORMAL priority in obtaining a repeater for communications. Only emergency calls
have a higher priority than TACTICAL.
When the System Access Priority status of a resource is changed, it is updated at all
dispatch consoles in the systems that are monitoring that trunked resource.
The System Access Priority Select feature can be used to change the system access
priority status of a trunked resource to TACTICAL in order to give the resource a
better chance of gaining communication access in a busy system. If, during a repeater
busy condition, two call requests are queued with one as NORMAL and the other as
TACTICAL priority, then the one with TACTICAL priority gains access to the
system when the next repeater becomes available.
Supported Types of Analog Conventional Base Stations

A Motorola MCC7500 dispatch console is capable of accessing and controlling the
following types of analog conventional base stations.
♦ R1
♦ T1R1
♦ T2R2
♦ T4R4
♦ T8R8
♦ T12R12
♦ T14R14
The above types of base stations are referred to as TnRn stations. A TnRn station has
one n-frequency transmitter and one n-frequency receiver.
The dispatch console can process audio received from the station and present it to the
dispatch console user via speakers or headsets key the station’s transmitter and
provide it with audio to be transmitted over the air (except for R1 stations which
don’t have a transmitter) control various features on the stations such as frequency
selection, PL selection, repeater on/off, etc.

RFP# 101216
December 16, 2010

Voice Call Types on Radio Resources
Conventional PTT Call

The Conventional PTT Call feature allows a dispatch console user to initiate and
receive normal PTT calls on conventional radio resources. A normal PTT call is not
directed to any specific individual or talkgroup and does not carry any special
importance. It is intended to be heard by all users listening to that radio resource.
Trunking Talkgroup Call

The Trunking Talkgroup Call feature allows a dispatch console user to initiate and
receive talkgroup calls on trunked radio resources. A trunking talkgroup call is a
method for communicating with a specific set of users on a trunked radio system.
Users only hear the audio associated with talkgroups with which they are currently
affiliated.
This feature allows a user to speak with a specific group of users without disturbing
other users.
Trunking Announcement Group Call

The Trunking Announcement Group Call feature allows a dispatch console user to
initiate and receive announcement group calls on trunked radio resources. A trunking
announcement group call is a method for communicating with multiple trunking
talkgroups simultaneously. An announcement group is composed of multiple
talkgroups that have been grouped together. The association of talkgroups to an
announcement group is done by the trunking system’s configuration subsystem.
This feature allows a user to speak quickly and easily with multiple trunking
talkgroups simultaneously.
Trunking Emergency Call

Trunking Emergency Calls are high-priority voice transmissions initiated by radios or
dispatch consoles that allow them to communicate with each other in critical
situations. Trunking emergency calls initiated by dispatch consoles reserve a voice
channel for the duration of an emergency.
A trunking emergency call is initiated by a radio when the radio transmits while it is
in emergency mode. Trunking emergency calls are typically presented at a dispatch
console using visual indications.
Dispatch consoles are notified when another dispatch console starts a trunking
emergency call.

RFP# 101216
December 16, 2010

In ASTRO 25 trunking systems, priority is given to allocating a voice channel to a
trunking emergency call over a regular call regardless of whether the regular call is at
either a tactical or normal priority level.
Trunking emergency calls can be initiated from a dispatch console on ASTRO 25 IP
trunking resources only. When a trunking emergency call is started from a dispatch
console, the call is assigned a voice channel for an indefinite period. This guarantees
a path for voice communication for the duration of an emergency. The voice channel
is released only when a dispatch console ends the call.
A dispatch console user can take responsibility for an emergency by recognizing the
trunking emergency call. All dispatch consoles are notified that the call has been
recognized.
Trunking emergency calls initiated by a dispatch console are automatically reported
to all dispatch consoles as being “recognized” since a dispatch console user took an
explicit action to initiate the trunking emergency call.
When an emergency is over, a dispatch console can end the trunking emergency call.
All dispatch consoles are notified that the call has been ended. When a dispatch
console ends a trunking emergency call, the voice channel allocated for the call is
released.
Ending the trunking emergency call at the dispatch console has no effect on the state
of the radio that initiated the call. Any radio units that initiated trunking emergency
calls remain in emergency mode until the radio users explicitly return them to a
normal mode of operation. If a radio that is in emergency mode transmits after a
dispatch console user has ended the trunked emergency call, the trunked emergency
call will be reestablished.
The Trunking Emergency Call feature is used by radios and consoles for high priority
voice communication. A dispatch console generally initiates a Trunking Emergency
Call to guarantee a voice channel for the duration of an emergency.
Received Emergency Call Indication

The Received Emergency Call Indication feature allows a dispatch console user to be
quickly informed that an emergency call has been received on a trunked resource.
The indication is a visual indication on the user interface.
The visual indication continues until the emergency call has been ended by a dispatch
console.
The Received Emergency Call Indication feature allows the dispatch console user to
quickly identify on which resource an emergency call has occurred.

RFP# 101216
December 16, 2010

Auto-Open of Quick List
The Auto-Open of Quick List feature allows a dispatch console user to quickly access
the controls necessary to handle a trunking emergency call. The Quick List contains
controls for recognizing an emergency call, initiating an emergency call, and ending
an emergency call.
The Auto-Open of Quick List feature automatically opens the quick list when a
resource with an unacknowledged emergency on the dispatch console’s user interface
is expanded by the dispatch console user.
The Auto-Open of Quick List feature allows the dispatch console user to begin
handling an emergency with a minimum of actions.
Emergency End (Knockdown)

The Emergency End (Knockdown) feature allows a dispatch console user to
terminate an emergency call. After an emergency call has been recognized and the
situation has been addressed, the dispatch console user ends the emergency call by
using the Emergency End feature. When the dispatch console user does this, the
visual emergency indication on the dispatch console’s user interface is removed, and
the dispatch console informs the trunking controller and all other dispatch consoles
that the emergency has been terminated. Parallel dispatch consoles then clear their
own emergency status indications for the resource if no other emergencies are active
on it.
Emergency Automatic Audio Level Control

The Emergency Automatic Audio Level Control feature ensures that the audio
associated with an emergency call is not missed due to its volume being too low.
When an emergency call is received by a dispatch console, the volume of the
received audio associated with the call is raised to its maximum level. When the
emergency call is acknowledged by a dispatch console user, the volume is returned to
its normal level.
The Emergency Automatic Audio Level Control feature allows the dispatch console
user to hear the emergency call audio while the emergency call audible alarm is
active.
Trunking Individual Call

The Trunking Individual Call feature allows a dispatch console user to initiate and
receive individual calls on trunked radio resources. A trunking individual call is a
method for allowing a call to be placed to a specific user on the trunking system.
A dedicated individual call resource on the dispatch console user interface allows the
dispatch console user to initiate or answer an individual call. All types of individual

RFP# 101216
December 16, 2010

calls are initiated from the dispatch console in the same way. When an individual call
request is received by the target radio, the dispatch console user receives an
indication that the target radio is ringing. At this point, the dispatch console is waiting
for the radio user to “answer” the ring. Once the individual call is answered, the call
is allowed to proceed.
A dispatch console user may use an individual call to communicate privately with
either a single radio user or a single MCC7500 dispatch console user.
If the target radio or dispatch console is not available when an individual call is
attempted, the dispatch console user receives an indication that the call could not be
completed.
All inbound individual calls are announced to the dispatch console user. A ringing
inbound call must be answered explicitly by the dispatch console user.
At a dispatch console, individual calls can be ended by a request from the dispatch
console or by the expiration of an audio activity timer. The audio activity timer
expires when there has been no audio activity on an active individual call for an
extended period. This time is specified via the configuration application at the
network manager. If there is no audio activity on an active individual call for the
specified amount of time, the individual call is automatically ended.
When an individual call is ended by the radio user or the other dispatch console user,
the console individual call resource automatically hangs up. Similarly, when an
individual call is ended by the dispatch console user, the radio or other dispatch
console automatically hangs up. This is known as the Cancel Service characteristic of
individual call.
The Trunking Individual Call feature is designed to allow a dispatch console to
engage in private conversations with individual radio or dispatch console users. Once
an individual call is established on a resource, the resource can be added to a patch
group with another type of resource.
Semi-Duplex or Full-Duplex Operation

Depending on the type of radio unit and the type of trunking system, an individual
call can be either semi-duplex or full-duplex. The console subsystem is capable of
supporting both types of calls with no configuration changes or dispatch console user
intervention required.
When a dispatch console user is involved in either type of individual call, the
dispatch console user is required to activate a PTT to talk. This is required to prevent
unexpected results if a telephone resource is off-hook while an individual call is in
process. A telephone resource does not require a PTT because it has hands-free full-
duplex operation when the dispatch console user is using a headset. If the individual
call also had hands-free full-duplex operation, the dispatch console would not be able

RFP# 101216
December 16, 2010

to tell to which destination (telephone resource or individual call) the microphone
audio should be sent. Therefore, a PTT is required to indicate to the dispatch console
that the dispatch console user desires to speak on the individual call instead of the
telephone resource. (In this context, the term “telephone resource” refers to two
different types of telephone services. It refers to the external telephone that can be
connected to a dispatch console so the dispatch console’s headset can be used for
both radio and telephone communications. It also refers to the console telephony
interface, which will be added in a future release.)
The dispatch console always allows receive audio to be presented to the dispatch
console user, but in a semi-duplex call, the radio system does not provide the receive
audio while the dispatch console user is transmitting.
Advanced Signaling on Trunked Radio Resources
Display Radio’s Unit ID

The Display Radio’s Unit ID feature allows a dispatch console to display the unit ID
associated with an inbound radio call. Unit IDs are unique numbers assigned to each
radio and dispatch console in certain types of radio systems. A radio can send its unit
ID when it makes a call.
The dispatch console user interface can be configured to display the unit ID of the
source radio on inbound calls. This configuration is done at the local administration
application. The unit ID can appear in a Received Call Stack, the Three Line Display,
the Resource Header, and the Activity Log window. Note that if an alias for the unit
ID is available, the dispatch console will display the alias instead of the unit ID.
The unit ID of a parallel dispatch console is also displayed on the dispatch console
when the parallel dispatch console transmits on radio resources which are common to
both consoles or when the parallel dispatch console places a call to the dispatch
console.
If an inbound call is received on a radio resource that does not support the concept of
unit IDs, no unit ID is displayed on the dispatch console even if it has been
configured to display unit IDs.
Send Console’s Unit ID

The Send Console’s Unit ID feature allows a dispatch console to send its unit ID
when it transmits on a radio resource. Unit IDs are unique numbers assigned to each
radio and dispatch console in certain types of radio systems. The unit ID allows the
radios to display the ID of the dispatch console that is the source of the transmission.
The dispatch console’s unit ID is sent when the dispatch console user transmits on a
radio resource and when the user initiates an individual call to another dispatch
console.

RFP# 101216
December 16, 2010

ID Conservation
The ID Conservation feature prevents dispatch consoles from consuming an
inordinate amount of unit IDs in a trunked radio system. The ID Conservation feature
allows a dispatch console to use a single unit ID for all the trunking talkgroup
resources and individual call resources that it controls.
Emergency Alarm
An Emergency Alarm is sent by radio users to alert dispatch console users of a
critical situation needing immediate attention.
When an Emergency Alarm is received by a dispatch console, an audible indication is
sounded. A visual indication is also displayed to direct a dispatch console user’s
attention to the specific resource with the emergency alarm active on the dispatch
console.
Any dispatch console user can take responsibility for an emergency by Recognizing
the Emergency Alarm. All dispatch consoles are notified that the Emergency Alarm
has been recognized.
The audible emergency indications are typically ended once all Emergency Alarms at
a dispatch console are recognized. The audible emergency indications may also be
ended by the dispatch console user without recognizing the Emergency Alarm.
When an emergency is over, a dispatch console can end the Emergency Alarm. All
dispatch consoles are notified that the Emergency Alarm has been ended.
The emergency mode persists on the initiating radio unit until it is ended by the radio
user explicitly.
The Emergency Alarm feature is used by radios to alert dispatch consoles of an
emergency without the use of voice communication. This is generally followed by a
voice transmission.
Received Emergency Alarm Indications

The Received Emergency Alarm Indications feature allows a dispatch console user to
be quickly informed that an emergency alarm has been received on a trunked
resource. The indications are audible and visual in nature.
The audible indication continues until either a dispatch console has recognized the
emergency alarm or the dispatch console user mutes it. The visual indication
continues until the emergency alarm has been ended by a dispatch console.
The Received Emergency Alarm Indications feature allows the dispatch console user
to be quickly alerted that an emergency alarm has been received and to identify
quickly on which resource it occurred.

RFP# 101216
December 16, 2010

Emergency Recognize
The Emergency Recognize feature allows a dispatch console user to assume
responsibility for an emergency call or emergency alarm. When a dispatch console
user recognizes an emergency, all other dispatch consoles are notified that the
emergency has been recognized.
When an emergency has been recognized, the audible indications for that emergency
are silenced at all dispatch consoles monitoring the emergency.
The Emergency Recognize feature is often confused with the Acknowledge feature.
Recognize is used when a dispatch console user takes a specific action to assume
responsibility for an emergency. Acknowledge is used when a piece of equipment
(trunking controller or dispatch console) automatically sends a message to a radio
telling it that its emergency message was received.
Mute Tones at Single Op

The Mute Tones at Single Op feature allows a dispatch console user to mute the tones
associated with an emergency alarm only at his/her dispatch console. This feature
does not recognize the emergency alarm, so other dispatch consoles continue to
generate the emergency tones.
The Mute Tones at Single Op feature is used to silence the emergency alarm tones
without recognizing the emergency. This would be used in a situation where one
agency is monitoring a channel that belongs to another agency. If an emergency
alarm comes in on the second agency’s channel, the first agency could mute the tones
at their dispatch consoles without having to wait for the second agency to recognize
it.
Emergency End (Knockdown)

The Emergency End feature allows a dispatch console user to terminate an
emergency alarm. All dispatch consoles are notified that the emergency alarm has
been ended and which dispatch console ended it.
Call Alert
The Call Alert feature lets a dispatch console or radio leave a “page” at an unattended
radio or dispatch console. Upon returning to the radio or dispatch console, the called
user knows who called. Additionally, a Call Alert can be used to trigger an activity.
For instance, a Call Alert may cause a vehicle’s horn to sound and its lights to flash.
Typically, the “page” appears at a radio as a series of beeps along with the unit ID of
the sender. Traditionally, at a dispatch console, the received “page” is presented as a
series of beeps along with a visual indication of who sent the Call Alert.

RFP# 101216
December 16, 2010

When a Call Alert is sent to an individual radio or dispatch console, the receiving
radio or dispatch console is expected to acknowledge it automatically. A sent Call
Alert can be aborted by the initiator before an acknowledgment is received. If after a
period an acknowledgment is not received, the Call Alert is automatically terminated
and the sender is notified that it was not successful.
The Call Alert feature provides the ability for a dispatch console or radio user to
contact someone who is away from their radio or dispatch console, and hence cannot
hear a voice message. Call Alert eliminates the need to tie up airtime trying to reach
an unattended radio.
If a dispatch console receives a Call Alert, the identity of the caller can be displayed
as a numeric Unit ID, or an alphanumeric alias for the calling radio.
Secure Trunked Radio Communication Functionality
Secure Capability in the Dispatch Console

The Secure Capability in the Dispatch Console feature allows radio voice messages
to be encrypted and decrypted in the dispatch console itself. This feature allows the
radio voice messages to be encrypted the entire time they are being transported
between the dispatch console and the radio.
The dispatch console is capable of supporting up to four different encryption
algorithms simultaneously. This allows dispatch console users to talk and listen on
radio resources that have different encryption algorithms without any manual
intervention or delay.
Trunked radio resources (talkgroups and private calls) can be configured with the
ability to work in the secure mode. Secure-capable resources on a dispatch console
may be configured so they always operate in secure mode or so the user can manually
change between secure and non-secure modes.
The Secure Capability in the Dispatch Console feature allows conversations between
a dispatch console user and a radio user to remain encrypted during the entire journey
between the two users.
Advanced Encryption Standard (AES) Algorithm

The AES Algorithm feature allows the dispatch console and archiving interface
server to process radio voice messages using the AES encryption algorithm. AES is a
United States government encryption/decryption standard defined in Federal
Information Processing Standard 197 (FIPS-197).
The dispatch console can encrypt and decrypt voice using the AES algorithm.

RFP# 101216
December 16, 2010

Secure Transmit Mode Selection
The Secure Transmit Mode Selection feature allows the dispatch console user to
control the secure mode of transmissions on a trunked resource. The dispatch console
user can choose whether his/her transmissions on a particular trunked resource are
encrypted.
This feature applies to trunked resources individually; that is, different trunked
resources on a dispatch console are independently configured to have or not have this
feature. This feature can be configured differently for the same trunked resource on
different dispatch consoles; that is, a trunked resource may have this feature on one
dispatch console but not on another dispatch console.
When set to the secure mode, all transmissions on that trunked resource from that
dispatch console are encrypted. When set to non-secure mode, no transmissions on
that trunked resource from that dispatch console are encrypted.
This feature only applies to the dispatch console on which it is located. Radios and
other dispatch consoles can have their secure modes set differently.
Receive Cross-Mode Indication

The Receive Cross-Mode Indication feature is used to indicate when an inbound (to
the dispatch console) radio call is in a different secure mode than the dispatch
console’s setting for outbound (from the dispatch console) transmissions on a trunked
resource. This helps prevent dispatch console users from responding to an inbound
call in the wrong mode.
Clear Audio Alert

The Clear Audio Alert feature provides visual and audible indications when a trunked
radio call is in the clear mode. The dispatch console can be configured to provide the
indications on dispatch console transmissions, on radio transmissions received at the
dispatch console or both. This alerts the dispatch console user that a call is
unencrypted.
Multi-Select Cross-Mode Alert

The Multi-Select Cross-Mode Alert feature is used to inform a dispatch console user
that there are trunked resources with different secure modes in a multi-select group.
This helps prevent dispatch console users from transmitting the same audio in both
secure and non-secure modes.
This feature does not prevent the dispatch console user from having trunked
resources with different secure modes in a multi-select group; it merely informs the
user that this is the case.

RFP# 101216
December 16, 2010

Patch Cross-Mode Alert
The Patch Cross-Mode Alert feature is used to inform a dispatch console user that
there are trunked resources with different secure modes in a patch group. This helps
prevent the transmission of encrypted audio in an unencrypted state in a patch.
This feature does not prevent the dispatch console user from having trunked
resources with different secure modes in a patch group; it merely informs the user
that this is the case.
Key Fail Indication

The Key Fail Indication feature is used to indicate when the dispatch console is
unable to decrypt or encrypt a trunked radio voice message due to a problem with an
encryption key. This indication is provided on the Elite Dispatch GUI status bar.
Reasons for a key failure include a missing key or no keys match the key used to
encode the incoming voice message.
Panic Key Zeroizing

The Panic Key Zeroizing feature allows all the encryption keys in a dispatch console
to be erased (zeroized) with the push of a button. The button is recessed in a panel to
reduce the chance of accidentally pressing it.
Erasing the keys on one dispatch console has no effect on the keys at other dispatch
consoles.
Keyset/Indexset Selection via GUI

The Keyset/Indexset Selection via GUI feature allows the dispatch console user to
manually select the Keyset/Indexset used by the dispatch console. This allows the
dispatch console user to transmit to radios that are using a different keyset. (The
dispatch console will automatically use the appropriate keyset to decrypt audio being
received from a radio, so the Keyset/Indexset Selection feature does not really have
an effect on received audio.)
The control for doing this is incorporated into the dispatch console’s graphical user
interface so no extra devices (such as a KVL) are required to change which
Keyset/Indexset is being used.
This feature does not apply to the archiving interface server since it does not have a
graphical user interface and it does not transmit encrypted audio.
Key Management via KVL

The Key Management via KVL feature provides the ability to manage all the keys for
a dispatch console or archiving interface server using only a KVL (key variable
loader).

RFP# 101216
December 16, 2010

Crosspatch Functionality
Standard Patch
The Standard Patch feature allows a dispatch console user to set up a communication
path between two or more resources that are normally unable to communicate with
each other. These could be trunked resources and/or conventional resources. When a
dispatch console detects call activity on one resource in a patch group, it
automatically transmits that audio to all other resources in the patch group.
Resources are patched by being included in a console patch group. A dispatch
console supports a maximum of 16 patch groups. A resource can be a member of
only one patch group in the entire console system at a time.
The Standard Patch feature can be used to allow radios within the same or different
radio systems to communicate even though they use different resources in that
system. For example, it can allow members of different talkgroups in a trunking
system to communicate or it can allow conventional radio users to be able to
communicate with other conventional radio user and/or with trunked radio users.
Patch Auto-Start
The Patch Auto-Start feature allows a dispatch console to automatically start up pre-
determined patches after a power cycle or reboot on the dispatch console computer.
If a dispatch console experiences an operating system reboot or an interruption in its
AC power, this feature causes the dispatch console to automatically start the dispatch
application, log into the dispatch console, and start up patches for all the patch groups
that have been configured to use the Patch Auto-Start feature.
Patch groups that are configured to use this feature need to be pre-configured with the
radio resources that are members of the patch group. A dispatch console user may
add/delete members to/from the patch group during real time operation, but if a
reboot or power cycle occurs, only the pre-configured members are included when
the patch is restored.
If a dispatch console user manually logs out of the dispatch application, this feature
does not try to automatically restart it. It waits until the operating system is rebooted
or the power is cycled off and on.
The combination of the Patch Auto-Start and the Patch Auto-Restore After Resource
Interruption features provides a highly resilient patch service that may be used for
long-term patch applications.

RFP# 101216
December 16, 2010

Patch Auto-Restore After Resource Interruption
The Patch Auto-Restore After Resource Interruption feature allows the dispatch
console to provide as much patch functionality as possible during and after service
interruptions in the radio system.
If a service interruption occurs on a resource that is in a patch group, the dispatch
console keeps the patch active with the remaining members of the patch group. The
interrupted resource is shown as being in a patch pending state for the duration of the
interruption. If the interrupted resource is restored to service while the patch group is
still active, the dispatch console attempts to add the resource back into the patch.
If a service interruption occurs that affects all the resources in a patch group, the
dispatch console keeps the patch active with no members in it. Resources are shown
as being in a patch pending state for the duration of the interruption. If resources are
restored to service while the patch group is still active, the dispatch console attempts
to add the resources back into the patch.
The word “attempts” is used in the previous paragraphs because there are conditions
outside the control of the dispatch console, which may prevent it from adding a
resource to a patch. Examples of these include the resource may not be available for
use or another dispatch console placed it in a patch first.
The Patch Auto-Restore After Resource Interruption feature allows the dispatch
console to provide as much patch functionality as possible after service interruptions
without human intervention. This is useful for patches that are desired to be active for
long periods.
The combination of the Patch Auto-Restore After Resource Interruption and the
Patch Auto-Start features provides a highly resilient patch service that may be used
for long-term patch applications.
Permanent Patch
The Permanent Patch feature has been replaced by a combination of the Standard
Patch, the Patch Auto-Start and the Patch Auto-Restore After Resource Interruption
features. Please refer to those features for information about what they do.
Patch Transmit
Patch Transmit is a console feature that allows a dispatch console to initiate a
transmission on all resources contained within a patch group.
Patch transmit is considered a low priority transmission; its priority is less than that
of all other transmit functions. A dispatch console using a higher priority
transmission can take control of a resource from another dispatch console using a
lower priority transmission. Note that this does not mean the higher priority

RFP# 101216
December 16, 2010

transmission becomes the audio source for the patch. It only becomes the audio
source for the channel(s) upon which it is transmitting.
A dispatch console can only patch transmit to one patch group at a time.
Note that if a dispatch console user does any type of transmission on a member of a
patch group, the dispatch console will automatically transmit on all the other
members of the patch group as well. While this operation does not involve the patch
transmit feature, it does provide similar results.
The patch transmit feature allows a dispatch console user to send a voice transmission
to all members of a patch group. This can be a convenient way for a dispatch console
user to inform members of a patch group when a patch has been established between
resources, or when the patch group is about to be dissolved.
Patch Busy Indication

The Patch Busy Indication feature provides a dispatch console user with an indication
that a resource is a member of an active patch group on any dispatch console in the
radio system. This is important because a resource can only be a member of one
active patch group at a time.
Patch Reserved Indication

The Patch Reserved Indication feature provides a dispatch console user with an
indication that a resource is a member of an active patch group on his/her dispatch
console. This is important because a resource can only be a member of one active
patch group at a time.
Patch Pending Indication

The Patch Pending Indication feature provides a dispatch console user with an
indication that a resource the user is trying to place into a patch is not available. Some
reasons a resource may not be available include:
♦ It is already a member of an active patch group on another dispatch console in the
radio system
♦ It may not be affiliated with the trunking system’s controller
♦ A hardware failure may be rendering it unavailable
The dispatch console will continue to monitor the status of the resource and will
attempt to include it in the patch if it becomes available.
Patching Op Indication
The Patching Op Indication feature allows the dispatch console user to see which
dispatch console patched a resource. This is useful in control rooms with many

RFP# 101216
December 16, 2010

dispatch consoles and a user wants to quickly find out which dispatch console is
controlling a patch.
Pausing the cursor on the Patch Busy Indication on a radio resource shows which
dispatch console set up the patch group.
Communication System Request Rejections
Resource Reject
The Resource Reject feature informs the dispatch console when a requested
operation, such as General Transmit, Instant Transmit, Call Alert, etc., has been
rejected by the radio system. This feature provides information regarding the reason
the request has been rejected by the radio system for the affected resources. Resource
Reject messages differ from error messages in that a reject comes from the radio
system whereas an error is generated within the dispatch console.
In certain situations, a single request might result in reject messages being received
for multiple resources. For example, multiple rejects might be the result of resource
regrouping done by a trunked radio system.
Resource Rejects are directed to the dispatch console that attempted the rejected
operation. Parallel dispatch consoles do not receive the rejects.
Resource Rejects provide dispatch console information as to why the radio system is
not allowing an attempted action to be performed. In many cases, the reject is
because of a temporary condition within the system (e.g., all resources are busy, or
the target radio is involved in another operation) which does not necessarily require
corrective action. In other situations, a Resource Reject message informs the dispatch
console of a system problem, indicating the need for a “system administrator” to
correct the problem in the radio system. When an action is rejected, the Resource
Reject feature provides a specific reason for why the request was denied.
Announcement/Intercom Functionality
Selective Op Intercom via Individual Call

The Selective Op Intercom via Individual Call feature allows a dispatch console user
to speak privately with another dispatch console user through the dispatch consoles.
This feature is based on the Trunking Individual Call feature that allows a dispatch
console user and a radio user to engage in a private conversation.
The user interface and operation of the Selective Op Intercom via Individual Call
feature are the same as for the Trunking Individual Call feature. Please refer to the
description text for the Trunking Individual Call feature for more information.

RFP# 101216
December 16, 2010

The Selective Op Intercom via Individual Call feature allows two dispatch console
users to speak privately with each other through their dispatch consoles. It is useful
for situations where two dispatch console users need to talk with each other, but are
not close enough to talk face to face.
Group Op Intercom via Talkgroup Call

The Group Op Intercom via Talkgroup Call feature allows a group of dispatch
console users to speak with each other through their dispatch consoles.
This feature is based on the Trunking Talkgroup Call feature. A talkgroup containing
only dispatch consoles as members can be created. Any dispatch console transmitting
on this talkgroup would be heard by all the dispatch consoles monitoring that
talkgroup. Multiple talkgroups can be created to create different intercom groupings.
This does not require any additional hardware beyond what is required for the rest of
the trunking system.
The user interface and operation of the Group Op Intercom via Talkgroup Call
feature are the same as for the Trunking Talkgroup Call feature. Please refer to the
description text for that feature for more information.
The dispatch console user groupings are created by assigning trunking talkgroup to
the desired dispatch consoles. All dispatch consoles that share such a resource may
talk with each other. A dispatch console may be part of multiple groups.
The Group Op Intercom via Talkgroup Call feature allows a group of dispatch
console users to speak with each other through their dispatch consoles. It is useful for
situations where a specific group of dispatch console users need to talk with each
other, but are not close enough to talk face to face.
All Op Intercom via Talkgroup Call

The All Op Intercom via Talkgroup Call feature is identical to the Group Op
Intercom via Talkgroup Call feature. The only difference is the Trunking Talkgroup
Call resource appears on all dispatch consoles. Thus, all dispatch consoles can
participate in the discussion.
The All Op Intercom via Talkgroup Call feature allows all dispatch console users to
speak with each other through their dispatch consoles. It is useful for situations where
all dispatch console users need to talk with each other, but are not close enough to
talk face to face.
System Maintenance and Supervisory Functions
Primary/Secondary Supervisor Levels

The Primary/Secondary Supervisor Levels feature provides a means for establishing a
hierarchy of authority between the users of dispatch consoles. This hierarchy is used
RFP# 101216
December 16, 2010

by the Transmit Priority Levels feature to determine the priority level of each
transmission in a console subsystem.
There are three levels of dispatch consoles - primary supervisor, secondary
supervisor, and non-supervisor. A primary supervisor is the highest level and has
transmit priority over all secondary supervisors and non-supervisors. A secondary
supervisor is the second highest level and has transmit priority over all non-
supervisors. A non-supervisor console is the lowest level and has no transmit priority
over any other console.
The primary and secondary supervisor designations are associated with users, not
with physical dispatch consoles. A console subsystem can have multiple dispatch
consoles of each level.
The Primary/Secondary Supervisor Levels feature allows supervisory personnel to
have the transmit priority necessary to carry out their responsibilities in a console
subsystem.
Multiple Primary Supervisors

The Multiple Primary Supervisors feature allows multiple dispatch console users to
be designated as primary supervisors in the same radio system. Refer to the
description text for the Primary/Secondary Supervisor Levels feature for more
information about primary supervisors.
This feature is useful when multiple customers are sharing a radio system and each
customer wishes to have their own primary supervisor.
Console Disable
The Console Disable feature allows a dispatch center supervisor to send a disable
command from the radio system’s network manager to a particular dispatch console.
Once the target dispatch console receives the disable command, the dispatch console
becomes inoperable. None of the console features or resources can be used, and no
call activity can be initiated or received on the disabled dispatch console. In addition,
all the current activity on the dispatch console is ended. For example, if there is any
kind of transmission active on the dispatch console, the transmission is aborted. If
resources are patched by this dispatch console, the resources are removed from the
patch group.
A dispatch center supervisor can send an enable command from the radio system’s
network manager to a previously disabled dispatch console in order to make it
operable.
The Console Disable feature can be used to disable a dispatch console that is not
being used in order to prevent unauthorized personnel from misusing it. For example,

RFP# 101216
December 16, 2010

if a dispatch console is located in a remote site and is not being supervised, the
dispatch console can be disabled.
Supervisor Takeover
The Supervisor Takeover feature allows a supervisor in a dispatch room to control
whether or not a non-MCC7500 dispatch console (e.g., a deskset) can access an
analog conventional base station that is controlled by an MCC7500 dispatch console.
A relay is used to physically disconnect the transmit wireline pair from the non-
MCC7500 dispatch console from the station.
This feature can be used while the non-MCC7500 dispatch console is actively
transmitting on the channel. This has the effect of immediately de-keying the
transmitter. The feature may be configured so the parallel non-MCC7500 dispatch
console is still able to hear any audio being received by the base station from radios.
This feature allows a supervisor to prevent unauthorized individuals from using
parallel non-MCC7500 dispatch consoles to transmit on conventional stations.
Aliasing
In a console dispatch environment, it is desirable for users to have the ability to use
familiar names in place of various numbers that are used in radio systems. Names can
be recognized quickly and are easier to remember than numbers.
An alias is an alphanumeric text string that is associated with some element of a
console subsystem (e.g., a conventional channel, a talkgroup, a user, a “button” on a
user interface, etc.). Typically, aliases are defined by users during the configuration
of the console subsystem and do not change very often.
Aliases are used in the configuration, operation, and management of the console
subsystem.
Trunking Talkgroup Resource

A Trunking Talkgroup Resource is capable of having a single 16-character alias
associated with it. The aliasing system is capable of providing an alias for each
Trunking Talkgroup Resource in the radio system.
The Alias feature allows dispatch console users to identify Trunking Talkgroup
Resources by names rather than numbers. This allows dispatch console users to easily
and efficiently operate the dispatch console.
Trunking Announcement Group Resource

A Trunking Announcement Group Resource is capable of having a 16-character alias
Trunking Announcement Group Resource in the radio system.

RFP# 101216
December 16, 2010

The Alias feature allows dispatch console users to identify Trunking Announcement
Group Resources by names rather than numbers. This allows dispatch console users
to easily and efficiently operate the dispatch console.
Trunking Individual Call Resource

A Trunking Individual Call Resource is capable of having a 16-character alias
Trunking Individual Call Resource in the radio system.
The Alias feature allows dispatch console users to identify Trunking Individual Call
Conventional Channel Resource

A Conventional Channel Resource is capable of having a 16-character alias
Conventional Channel Resource in the radio system.
The Alias feature allows dispatch console users to identify Conventional Channel
Conventional Channel Frequency Selection Control

A Conventional Channel Frequency Selection Control is capable of having multiple
16 character aliases associated with it. Each frequency can have a unique alias within
the control. The aliasing system is capable of providing an alias for each
Conventional Channel Frequency Selection Control in the radio system.
The Alias feature allows dispatch console users to identify frequencies by names
rather than numbers. This allows dispatch console users to easily and efficiently
operate the dispatch console.
Conventional Channel PL Selection Control

A Conventional Channel PL Selection Control is capable of having multiple 16-
character aliases associated with it. Each PL code can have a unique alias within the
control. The aliasing system is capable of providing an alias for each Conventional
Channel PL Selection Control in the radio system.
The Alias feature allows dispatch console users to identify PL codes by names rather
than numbers. This allows dispatch console users to easily and efficiently operate the
dispatch console.

RFP# 101216
December 16, 2010

Unit ID
A Unit ID is capable of having a 16-character alias associated with it. The aliasing
system is capable of providing an alias for each Unit ID in the radio system.
The Alias feature allows dispatch console users to identify Units by names rather than
numbers. This allows dispatch console users to easily and efficiently operate the
dispatch consoles.
Aux I/O Resource

An Aux I/O Resource is capable of having a 16-character alias associated with it. The
aliasing system is capable of providing an alias for each Aux I/O Resource in the
radio system.
The Alias feature allows dispatch console users to identify Aux I/O Resource by
names rather than numbers. This allows dispatch console users to easily and
efficiently operate the dispatch consoles.
Security Management
User Accounts and Passwords

Radio system user accounts are used in radio systems to provide access to resources,
simplify the use of certain features, and assist in ensuring security. The radio system
allows an administrative user to create accounts for the various users of the system
and assign different capabilities and access rights to them. One such account is for the
users of the console subsystem.
A dispatch console requires that a valid radio system user account name and
password be entered before it can be used on the radio system. The dispatch console
validates the user account name and password with the radio system’s network
manager and allows the user to access only the resources for which the user has
access rights. This also applies to third party applications that use the dispatch
console’s API.
Note that these radio system user account names and passwords are in addition to any
user account names and passwords required to log into the Windows operating
system on the dispatch console PCs.
Agency Partitioning
The radio system provides users with the ability to create groups of users and assign
system resource access rights to those groups. This allows users to control which
users have access to which resources in the radio system. This is how agency
partitioning is supported in the radio system.

RFP# 101216
December 16, 2010

Agency partitioning allows radio systems, which are used by multiple agencies, to be
configured in such a way that the users from each agency only have access to their
agency’s resources. This helps keep an agency’s resources available for its users, and
it prevents unauthorized people from making any changes to the agency’s resources.
The console subsystem participates in this agency-partitioning scheme. Access to the
various parts of the console subsystem is managed by the access rights given to user
accounts.
A dispatch console checks with the network manager for the access rights assigned to
the user and allows access to only the resources for which the user has access rights.
This also applies to third party applications that use the dispatch console API.
The radio system network manager checks the access rights assigned to the user
wishing to configure the console subsystem and allows access to only the portions of
the console subsystem for which the user has access rights.
Network Security Enhancements

The radio system’s IP transport network is protected against viruses, hackers and
other unauthorized activities by a set of enhancements that are applied to each
product connected to the network. The dispatch consoles support these
enhancements.
Fault Management
Hardware Element Monitoring

The radio system’s fault manager monitors and reports the status of all the hardware
elements in the console subsystem. This allows the console subsystem to be fault
managed from the same point at which the rest of the radio system is fault managed.
The specific hardware elements that are monitored are the dispatch console and any
networking equipment that supports the console elements. Each of these hardware
elements monitors critical internal hardware sub-elements and reports their status.
This allows a failure within a hardware element to be detected. The hardware
elements in the console subsystem are also periodically polled to request their status.
This allows a failure of an entire hardware element to be detected.
Software Process Monitoring

The console subsystem monitors and reports the status of all the critical software
processes running on the various hardware elements that comprise the subsystem.
Changes in the status of software processes on a device are recorded internally. These
internal records are primarily intended for use by qualified technical personnel in
troubleshooting problems with the console subsystem. Status changes, which are

RFP# 101216
December 16, 2010

useful for understanding the console subsystem’s overall status, are also reported to
the radio system’s fault manager.
If a failure of a software process is detected, self-healing actions may be initiated to
correct the failed process. Refer to the Self-Healing Actions feature for more
information.
Network Link Integrity Monitoring

The network elements, which are used by the console subsystem, are monitored in the
same manner as the network elements for the rest of the radio system. Any failures in
these links are reported to the radio system’s fault manager.
Automatic Discovery of Console Elements

The console subsystem supports the automatic discovery of console elements by the
radio system’s fault manager. This saves the user from having to manually gather and
enter the necessary data into the radio system fault manager.
The radio system fault manager automatically discovers all network elements (both
Motorola-manufactured elements and Motorola-supported third party elements) that
are included in the system and adds them to the map of network elements in a
topologically descriptive manner.
Outputting of Monitoring Results (SNMP)

The console subsystem supports the reporting of fault status to the radio system’s
network manager via the SNMP protocol.
Self-Healing Actions
The console subsystem automatically takes certain actions to try to remedy failures
detected by its fault management routines. These actions are intended to provide as
much functionality to the user as possible.
These actions include restarting failed software processes, resetting internal hardware
or reloading software into internal hardware.
Configuration Management
Configuration Application
The console subsystem is configured by an application residing on the radio system’s
network manager. This configuration application is used to configure all console
subsystem elements in the radio system. Using the configuration application, the user
defines what hardware is present at each element and the capabilities of each element.

RFP# 101216
December 16, 2010

This configuration application is used in conjunction with the Elite Admin
application.
The configuration application is used to define what is potentially available at each
console subsystem element.
The Elite Admin application is used to define exactly which resources are available to
the dispatch console user and how they are presented to the dispatch console user.
Automatic Distribution of Configuration Changes

When a change is made to the configuration information for the console subsystem,
the radio system’s network manager automatically distributes the changed
information to all the console subsystem elements that require it.
As-Configured Documentation
The configuration management system generates documentation that allows the user
to verify the configuration that was entered and provide information necessary for
installation of the console subsystem.
The following information is contained in the documentation generated by the
configuration management system:
♦ Console subsystem information - A listing of which dispatch consoles have been
created in the console subsystem.
♦ Dispatch console information - A listing of the peripherals, peripheral port
assignments, capabilities and audio destination assignments for each dispatch
console.
♦ Conventional channel gateway information - A listing of the channels, channel
capabilities, channel connection information, and main/alternate designation for
each conventional channel gateway.
♦ Trunked resource information - A listing of the type of and capabilities for each
trunked resource controlled by the console subsystem.
♦ Conventional resource information - A listing of the type of and capabilities for
each conventional resource in the console subsystem.
♦ Aux I/O information - A listing of the type of capabilities for each auxiliary input
or output in the console subsystem.
Date and Time
Date and Time Synchronization

The console subsystem synchronizes its time and date information with the radio
system’s time source via Network Time Protocol (NTP) on the radio system’s IP
network. This ensures that the time displays at the dispatch consoles and any time
stamps on events in log files are accurate.

RFP# 101216
December 16, 2010

Adjustments for 12/24 hour format, different time zones, and Daylight Savings Time
are automatically made if the operating system on the dispatch consoles and other
console subsystem elements is configured to support them.
Time Display
The dispatch console provides the user with the ability to display the current time on
the user interface. The time is synchronized with the radio system’s time source.
Please refer to the Date and Time Synchronization feature for more information about
how it is synchronized.
The time displayed on the user interface is the PC clock time. Adjustments for 12/24
hour format, different time zones, and Daylight Savings Time are automatically made
if the operating system on the dispatch consoles is configured to support them.
5.2.8 MIP 5000 Dispatch Console

Motorola’s MIP 5000 Voice over Internet Protocol (VoIP) Radio Console is a
robustly featured IP based radio console that installs on a standard PC or laptop
computer and provides the following key features and benefits:
♦ Bandwidth – Low network bandwidth requirements.
♦ Channel Resource – The MIP 5000 Graphical User Interface (GUI) displays up
to three or fourlines of text on a channel resource.
♦ Dispatch Operator Capacity – Dispatchers are able to access and control up to 24
channels (gateways/radio control stations).
♦ Network Error Indicator – The MIP 5000 VoIP Radio Console includes a
Network Indicator Status Bar at the bottom of the program window.
♦ Operating System – Each standard PC or laptop computer runs on a Windows XP
SP3 or Vista Business SP1 operating system.
♦ System Capacities – The MIP 5000 VoIP Radio Console System supports up to
128 gateways (local, tone, and/or digital) and up to 100 radio console positions.
♦ Virtual Private Network (VPN) – VPN is a method for accessing a private/secure
intranet using a public network such as the Internet, where a manager can power
up a laptop in the middle of the night and communicate directly on the network
without leaving home. The MIP 5000 VoIP Radio Console supports hardware
based (i.e., router to router) VPN.
♦ Acts as a virtual control head for specific Motorola radios giving access to
proprietary features such as console priority, alias ID, frequency select,
emergency, selective call, and radio enable/disable.
♦ Enables communication on any conventional and trunked radio system (VHF,
UHF, and 800 MHz).

RFP# 101216
December 16, 2010

5.2.8.1 System Architecture
The MIP 5000 architecture uses VoIP (Voice over IP), a digital format for voice and
control instead of the traditional analog format. There are three main components in
a MIP 5000 system:
♦ GUI Application
♦ Ethernet Network
♦ Radio Gateway
5.2.8.2 GUI Application

The MIP 5000 GUI runs on a Windows PC utilizing the Microsoft Windows XP SP2
or SP3 Operating System or the Microsoft Windows Vista Business SP1 Operating
System. The system interfaces with a NIC Card (Network Interface Card) and a
Sound Card. The NIC card provides the interface between the computer (radio
console position) and the Ethernet network enabling data communication with other
radio console positions and gateways. The Sound Card provides the audio interface
between the dispatcher and the computer, using standard computer speakers, a
headset, and microphone audio accessories. The primary functions of the MIP 5000
VoIP software application include:
♦ Provides an ergonomic Command and Control interface between the dispatcher
and the radio system.
♦ Encodes and decodes Command and Control Ethernet data packets for reliable
distribution to and from the Ethernet network.
♦ Processes and converts dispatcher analog voice (radio transmit audio) to VoIP
data packets using a G.711 vocoder.
♦ Processes and converts subscriber radio (radio receive audio) G.711 VoIP data
packets into analog voice.
♦ Maintains a jitter buffer for audio quality.
5.2.8.2.1 Flexibility
The MIP 5000 VoIP Radio Console provides an extremely flexible interface. The
GUI can be tailored for each dispatcher, not only in terms of resources and
functionality but also in layout and color schemes. Separate configuration files can
be associated with each login ID, where a dispatcher’s configuration comes up
automatically at login. Multiple configuration files can also be saved at each radio
console position.
5.2.8.3 Ethernet Network

The second main component in a MIP 5000 system is the Ethernet network. The
Ethernet network is the communication medium by which all Command and Control
RFP# 101216
December 16, 2010

data packets and VoIP G.711 voice packets are distributed between radio console
positions and gateways. Command and Control data packets are sent using the
TCP/IP protocol. Due to the “real time” nature of voice, the UDP protocol is used for
VoIP G.711 voice packets. To minimize the number of voice packets on the network,
Multicast has been chosen as the method for voice packet distribution between the
MIP 5000 GUI application and the MIP 5000 Radio Gateway. Multicast requires that
all router and switches on the network be configured to pass these multicast voice
packets.
The proposed system includes a HP switch that will be used as the network that
interfaces to the MIP 5000 workstations and tone gateways. The proposed system is
designed to have the tone gateways located in the same rack as the HP switch.
5.2.8.4 MIP 5000 Radio Gateway

The third main component in the MIP 5000 system is the radio gateway. The MIP
5000 Radio Gateway provides a unique interface between the Ethernet network and a
radio. Each MIP 5000 Radio Gateway supports and connects to a maximum of one
radio. The radio gateway is available in three models:
♦ Local Control Model – Supports a direct cable connection to the radio. Typically
used in mobile in a tray applications. Supports up to 16 frequencies per radio
channel control. Features supported include MDC 1200 IDs and paging.
Features not supported include ASTRO IDs and limited channel change
depending on the radio type. NOT INCLUDED IN THIS PROPOSAL
♦ Tone Control and E&M Model – Supports a two-wire or four-wire connection

via leased 600 Ohm phone lines. Supports up to 16 frequencies per radio channel
control. Features supported include MDC 1200 IDs, paging, and eight mode
selections (frequency or talkgroups). Features not supported include ASTRO
IDs. INCLUDED IN THIS PROPOSAL
♦ Digital (SB96000/SBEP) Control Model – The Motorola protocol is used to

control specific radios (i.e., the ASTRO W9 consolette). The radio console uses
this protocol to mimic the operation of the control head. For digital control, the
maximum number of frequencies is limited by the number of frequencies that are
programmed in the radio. Features supported include ASTRO IDs, all mode
changes, and all soft keys. Additional features include the PTT ID (not Alias)
being displayed in the Activity Log Window during normal transmissions. If a
digital junction box is used in conjunction with the ASTRO W9 consolette, the
PTT ID or Alias from the subscriber unit will show in the Activity Log Window
for normal transmissions. For emergency calls, the PTT ID from the subscriber
unit will show in the Activity Log window. NOT INCLUDED IN THIS
PROPOSAL

RFP# 101216
December 16, 2010

5.2.8.5 High Level Architecture
Figure 5-20 provides a high level explanation of how the MIP 5000 VoIP Radio
Console System works.
MIP 5000 VoIP Radio Console

Console
sends Digital
Voice packets
Customer
Network
Mobile radio
transmits audio
Gateway translates
digitized voice packets
into analog & re-transmits
as analog voice
Figure 5-20: Overview of MIP 5000 VoIP Radio Console System
The radio console provides the interface between the dispatcher and the IP network,
while the MIP 5000 Gateway provides the interface between the IP network and the
two-way radio.
5.2.8.6 Headset Jackbox

The Headset Jackbox (HSJB) is available in two versions:
♦ The Basic Version provides the following functions: One USB computer
interface for a dual prong headset, a dual pedal footswitch, and a desktop
microphone. INCLUDED IN THIS PROPOSAL
♦ The Enhanced Version provides the same features as the Basic Version plus a
USB interface to the computer for Call Director, an external paging encoder, and
an analog logging recorder. Customers are limited to three HSJBs per computer
and can choose between any combination of the Basic and Enhanced Version.
NOT INCLUDED IN THIS PROPOSAL

RFP# 101216
December 16, 2010

The Basic and Enhanced Version of a HSJB is limited to the following capacities:
♦ (1) headset interface per HSJB
♦ (1) footswitch interface per HSJB
♦ (1) microphone interface per HSJB
♦ Supports only one desktop microphone per radio console position
♦ Supports up to two headsets per radio console position
♦ Supports up to two footswitches per radio console position
♦ Provides one logging recorder output port per Enhanced HSJB
♦ Provides one Call Director interface port per Enhanced HSJB
♦ Provides one paging encoder input port per Enhanced HSJB
♦ Supports up to two analog logging recorders per radio console position
♦ Supports only one Call Director per radio console position
♦ Supports only one external paging encoder per radio console position.
5.2.8.7 Console System Database Manager

The Console System Database Manager (CSDM) is a powerful configuration tool for
the MIP 5000 system. The CSDM software application runs on a Microsoft
Windows Vista Business SP1 operating system and can be installed on a radio
console position or a dedicated PC on the network. For this proposal the CSDM is
installed on the radio console position and runs on Vista.
The CSDM has the ability to configure up to 128 radio resources. This enables
customers with a large number of radio resources, but with distributed or segmented
dispatch operations to access all of their radio channels on a single MIP 5000 system.
While each console position can see and control up to 24 radio resources at one time,
different console positions can be configured to control different radio resources. In
addition, a single console position can have multiple configurations saved on the
computer. One configuration could be used for primary dispatch operations, while
alternate configurations with different radio channels can be called up in emergency
scenarios or storm plans.
The CSDM provides the following capabilities:
♦ Adding a console
♦ Adding a radio channel
♦ Configuring tone signaling
♦ Setting up a custom page
♦ Setting up page format
♦ Setting up radio channel Cross Muting
♦ Generating configuration files.
The CSDM computer can be accessed remotely provided there is access to a
computer on the network. There can only be one CSDM associated with the MIP
5000 system.
RFP# 101216
December 16, 2010

5.2.9 ISSI Interface
Each ISSI.1 Network Gateway Application allows 27 simultaneous trunked calls
between systems and 60 interoperability talkgroup pairs. The network gateway
architecture has some distinctive advantages, which are outlined below.
A high-level, generic use case of how two systems are connected is shown in Figure
5-21.
Figure 5-21: ISSI.1 Network Gateway Solution
The ISSI.1 network gateway application enables the connectivity across the two (or
more) systems by “mapping” talkgroup IDs from one System A to another System B.
In the example talkgroup100 on System A is associated in the gateway to be
connected to talkgroup 150 on System B. Should any of the users (“Art”, “Les”,
“Andy”, “Roy”, or “Jon”) key up in either network, the Zone Controllers send the call
to the site gateways which then send the audio and signaling to the other network and
initiate the associated talkgroup traffic, thereby creating a “virtual” inter-system
talkgroup operation.
In the roaming case shown in Figure 5-22, the roaming user, “Les”, “manually
roams” into the other system. Once “Les” notices that the signal from his current
system (System A) begins to decline, he would initiate a mode change on his radio,
either by changing the knob or through the keypad. This process is also known as
“fingertip roaming”. He also would need to know the “associated” talkgroup 150 on
System B.

RFP# 101216
December 16, 2010

Once he has selected talkgroup 150 on System B, “Les” would be operating on the
virtual talkgroup spanning the two systems. Readers familiar with P25 roaming will
recognize this operation to be identical to system-to-system roaming used today. The
important enhancement for “Les” is that after he roams into System B, he will
continue communications with his home dispatcher in System A as well as any users
who are still on talkgroup 100 in System (“Art”).
Figure 5-22: ISSI.1 Network Gateway Solution – Roaming
Advantages of the ISSI.1 Network Gateway Application Architecture:

♦ Connects systems with different system IDs – The ISSI.1 Network Gateway
Application enables two systems, each using a different system and WACN ID to
be connected over a wireline connection.
♦ Can be added to existing ASTRO 25 Networks (‘bolt-on’) – The ISSI.1 Network
Gateway Application can be added to an existing and deployed ASTRO 25
network without requiring that the network be upgraded to a new version.
The gateway enables two systems to be connected together of virtually any
Motorola vintage (ASTRO 25 6.9 or higher), effectively decoupling systems
and avoiding inter-agency funding dependences.
An ancillary benefit of the ‘bolt-on’ implementation is ease of installation.
Because the gateway connected at the site link layer, the ISSI.1 Network
Gateway application(s) can be installed and configured in the network in a
few days, rather than weeks for a zone link.

RFP# 101216
December 16, 2010

♦ Roaming enabled without upgrading subscribers – The ISSI.1 Network Gateway
Application enables wireline connectivity using the P25 ISSI without requiring
software upgrade to the subscriber devices to enable roaming.
♦ Networks connect while retaining control of their individual systems’ UCS – The
ISSI.1 Network Gateway Application preserves the User Configuration
Subsystem databases on each side of the gateway enabling users to retain
operational autonomy over their system.
♦ Cost effective implementation – The ISSI.1 Network Gateway is a very cost
effective implementation of system interoperability as a result of its site link layer
architecture, installation ease and limited feature set.
♦ Wireline-based solution enables end-to-end encryption/Does not require
Transcoding – The wireline connectivity enables end to end encryption, lower
audio delay and does not require transcoding or double-vocoding. This advantage
is experienced in lower delays, better audio quality and more robust call services
than can be accomplished by analog audio-based connections.
Operational Capacities of the ISSI.1 Gateway Application Architecture

♦ Features Supported – The ISSI.1 Network Gateway Application supports the
following features: ISSI Group Call, ISSI Emergency Call, End-to-End
Encryption, and ISSI Manual (“finger tip”) Roaming are supported.
♦ Capacity – Each ISSI.1 Network Gateway Application allows 27 simultaneous
trunked calls between systems and 60 interoperability talkgroup pairs.
♦ Console Priority – The ISSI.1 Network Gateway Application does not support
Console Priority across the interface.
Motorola is providing a single ISSI.1 Network Gateway connection from the

proposed Floyd County ASTRO 25 Zone Core to the Tennessee Valley Radio
Communications System ASTRO 25 Zone Core in Chattanooga, Tennessee. At each
of these two Zone Cores, Motorola will provide an ISSI.1 Network Gateway
application as well as the necessary server and networking equipment to support the
P25 ISSI connection.
Each server provided at the two Zone Cores (Floyd County, Georgia and
TVRCS/Chattanooga, Tennessee) will support up to three ISSI.1 Network Gateway
applications, but will only be licensed for one application on each server. Adding a
second or third ISSI application to an additional system will require additional
networking equipment.
5.2.10 MC1000 Desktop Handset

The MC1000 Desktop Controllers allow remote access to the functions
of a compatible station (base station, repeater, or control station). These
desktop controllers support tone and E&M signaling (off-hook/on-hook) for keying
and control of stations. The MC1000 Desktop Unit supports the following features:

RFP# 101216
December 16, 2010

♦ Single Frequency and Single Station Control
♦ Push-to-Talk Handset
♦ Speaker
♦ Speaker on/off (receive audio is heard through handset and speaker
simultaneously)
♦ Volume Control
♦ Full Duplex Capability
♦ Internal Mic (for use without handset)
♦ Transmit Button with LED
♦ Monitor Button with LED
♦ Front panel programming (easy setup – no software required)
♦ Intercom between MC1000 units and stations
♦ Operator cross mute
♦ 10 units can operate in parallel
♦ Parallel Operator Busy Indication
♦ 4 Frequency Single Station Control
♦ 2- or 4-Wire Audio
♦ Takeover/Line Select allows a supervisory unit to override other parallel units or
allows connection of two base stations for back-up control (Main/Alt operation)
The application specific installation for the Jail, Prison and Court House will utilize
Tone Remote Control and will be configured similar to the generic Figure 5-23
below.
Figure 5-23: Remote Control Configuration
5.2.11 ASTRO 25 System Failure Mode Analysis

Motorola’s ASTRO 25 trunking networks have three modes of operation for
increased reliability. The normal mode of operation is Wide Area Trunking. In the
event of multiple component failures that lead to system disruption, the system is

RFP# 101216
December 16, 2010

equipped to continue operation in two reduced feature operational modes: Site
Trunking and Failsoft.
The following pages include a detailed description of each of these operational
modes, as well as a comprehensive analysis of the possible infrastructure failure
scenarios and the system redundancy for mitigating each scenario.
5.2.11.1 Wide Area Trunking

Wide Area Trunking is the ASTRO 25 system’s normal mode of operation. Wide
Area Trunking implies that the Fixed Network Equipment is operating properly. All
Simulcast cells and ASTRO 25 Repeater Sites are communicating with the Zone
Core. Subscriber units automatically roam between the various network RF cells.
Talkgroup calls occur in the appropriate RF cells if users are distributed throughout
multiple cells. Data applications are properly assigned channels for communication
between the subscriber units and the host application.
5.2.11.2 Site Trunking

Site Trunking is the first failover mode of operation. Site Trunking impacts individual
RF cells within a network. In multiple RF cell systems, one RF cell can be in Site
Trunking, while the rest of the system remains in Wide Area Trunking. Site Trunking
implies that the Simulcast Prime Site Controller or the ASTRO 25 Repeater Site has
lost connectivity with the Zone Core. Talkgroup calls initiated in the RF cell that is in
Site Trunking will only be broadcast in that RF cell. Dispatch consoles use control
stations or the operators use portable radios to communicate on a Site Trunking RF
Cell. Console priority is not available in Site Trunking. Data applications are not
available on a site in Site Trunking and will have to be reinitiated once the system
reverts to Wide Area Trunking.
Radios detect if a site is in Wide Area Trunking or site trunking. Radio models with a
display will indicate to the user when the site is operating in site trunking. The radio
alternately displays the selected talkgroup and “Site Trunking”. Depending on how
the system and user equipment are programmed, subscriber units will try to roam to
an RF cell that is in Wide Area Trunking.
5.2.11.3 Failsoft by Talkgroup

Subsystem/Site Failsoft is the final fallback means of communication if a site no
longer maintains Wide Area or Site Trunking operation. Multiple failures have to
occur for the system to enter Failsoft. Failsoft impacts individual RF cells within a
network. In multiple RF cell systems, one RF cell can be in Failsoft, while the rest of
the system remains in Wide Area Trunking. The subsystem goes into Failsoft mode
in any of these scenarios:
♦ The site controllers are not functioning properly.

RFP# 101216
December 16, 2010

♦ When all control channels are disabled or malfunctioned.
♦ When only one channel is enabled.
Failsoft operation provides communications in conventional mode via repeaters/base
radios in order to maintain vital communications. In an IP multisite Simulcast
subsystem in subsystem-wide Failsoft, received audio is routed to the comparator for
voting and redistributed to all of the sites for Simulcast transmission.
The subscriber’s operation in Failsoft mode is determined by the subscriber’s
programming. A subscriber can be programmed to behave in the following manner:
♦ Failsoft by control channel operation – The subscriber first scans for alternate
control channels outside the multisite subsystem, then scans the control channel
frequencies for Failsoft data.
♦ Failsoft by working group – The subscriber looks for Failsoft data on a pre-
programmed frequency after a scan for alternate control channels outside the
multisite subsystem is unsuccessful. If the subscriber cannot decode Failsoft data
on the pre-programmed frequency, the subscriber then scans the control channels
in the Simulcast subsystem for Failsoft data.
Subscriber units in an RF cell that is in Failsoft will try to roam to an RF cell that is
in either Wide Area Trunking or Site Trunking. Dispatch Consoles use control
stations or the operators use portable radios to communicate on a Site Trunking RF
cell. Console priority is not available in Site Trunking. Data applications are not
available on a site in Failsoft and will have to be reinitiated once the system reverts
back to Wide Area Trunking.
5.2.11.4 Individual Component Failure Scenarios
Table 5-6: Failure of Zone Controller A at the Zone Core
Scenario: Failure of Zone Controller A at the Zone Core

Result: Motorola has provided redundant Zone Controllers at the Zone Core.
Failure of the active Zone Controller at the Zone Core will result in
automatic switchover to the redundant Zone Controller. As the switchover
process takes place, the system will temporarily enter site trunking mode for
a period less than 60 seconds. Only active calls at the time of switchover
will be dropped. Wide area trunking will be restored when the switchover
process is complete. Any and all calls generated after automatic switchover
to the redundant controller will not observe any change of service. During
the transition, the dispatch operators will revert to operating on optional
Control Stations that can be selected from the MCC 7500 console.
The Zone Controllers have redundant power supplies as a standard feature,
which will help keep the controllers operational in case of a failure of that
component. The redundant controller is regularly updated with all pieces of
critical information so that if it needs to become the active controller, the
current system configuration and operational characteristics are maintained.

RFP# 101216
December 16, 2010

Scenario: Failure of Zone Controller A at the Zone Core
Protection: Redundant Zone Controllers at the Zone Core and spare boards for the
Zone Controllers.
Detection: Alarm on Manager Terminal.
Table 5-7: Failure of Zone Controller A and B at the Zone Core
Scenario: Failure of Zone Controller A and B at the Zone Core.

Result: In the unlikely event that both the active and redundant Zone Controllers
fail, the system will automatically switch over to Site Trunking at all ASTRO
25 Simulcast or Repeater Sites. The ASTRO 25 Trunked Simulcast or
Repeater sites will continue to trunk in their respective cells and coverage
areas; however, there will be no direct linking of calls between the ASTRO
25 Trunked Simulcast Sites and/or Repeater Sites. Users within an RF cell
will be able to operate in the trunking mode with their respective dispatch
centers (using wireless connectivity via backup control stations). When the
Zone Controllers come back online, the system will return to Wide Area
Trunking.
Protection: Spare boards, optional Backup Zone Core at a geographically separate
location. Backup WAN links at each remote Simulcast site, ASTRO 25
Trunked Repeater Site, and dispatch sites.
Table 5-8: Failure of a Zone Core Enterprise Switch
Scenario: Failure of a Zone Core Ethernet Switch at the Zone Core

Result: Motorola’s ASTRO 25 system employs dual Zone Core Ethernet Switches
at the Zone Core. All equipment critical for wide-area voice communications
has connections to both switches. Failure of one Ethernet Switch on the
active Zone Core will cause the LAN traffic to use the other switch. The
entire system remains in the Simulcast Wide Area Trunking mode. The
failure is transparent to all system users.
Protection: Dual Zone Core Ethernet Switches, Spare Switch.
Table 5-9: Failure of both Zone Core Enterprise Switches
Scenario: Failure of both Zone Core Enterprise Switches at the Zone Core
Result: In the unlikely event that both Zone Core Enterprise Switches fail at the
Zone Core, the system will automatically switch over to Site Trunking at all
ASTRO 25 Simulcast and Repeater Sites. The ASTRO 25 Trunked
Simulcast and Repeater sites will continue to trunk in their respective cells
and coverage areas; however, there will be no direct linking of calls
between the ASTRO 25 Trunked Simulcast and/or Repeater Sites and
dispatch centers. Users within an RF cell will be able to operate in the
trunking mode with their respective dispatch centers (using wireless
connectivity via control stations). When the Enterprise switches come back

RFP# 101216
December 16, 2010

Scenario: Failure of both Zone Core Enterprise Switches at the Zone Core
online, the system will return to Wide Area Trunking.
Protection: Spare Enterprise Switch.
Table 5-10: Failure of a Zone Core Core Router
Scenario: Failure of a Zone Core Core Router at the Zone Core

Result: The Zone Core configuration for the proposed Floyd County system
consists of redundant Core Routers. The Core Routers are configured so
that all RF cells and dispatch centers are connected to both Core Routers.
Failure of one Core Router at the active Zone Core will result in automatic
switchover to the redundant Core Router. The entire system remains in
Wide Area operation. The failure is transparent to all system users.
Protection: Redundant Core Router, Optional spare Core Router, Redundant site links.
Table 5-11: Failure of Both the Main and Redundant Core Routers
Scenario: Failure of Both the Main and Redundant Core Routers at the Zone
Core
Result: The Zone Core configuration for the proposed Floyd County system
consists of two Core Routers. The Core Routers are configured so that all
RF cells and dispatch centers are connected to both Core Routers. In the
unlikely event that both Core Routers fail at the Zone Core, the system will
automatically switch over to Site Trunking at all ASTRO 25 Simulcast and
Repeater Sites. The ASTRO 25 Trunked Simulcast and Repeater sites will
continue to trunk in their respective cells and coverage areas; however,
there will be no direct linking of calls between the ASTRO 25 Trunked
Simulcast and/or Repeater Sites and dispatch centers. Users within an RF
cell will be able to operate in the trunking mode with their respective
dispatch centers (using wireless connectivity via control stations). When the
Core Routers come back online, the system will return to Wide Area
Trunking.
Protection: Redundant Core Router, Optional spare Core Router. Redundant Site
Links.
Table 5-12: Failure of the Network Management Servers
Scenario: Failure of the Network Management Servers at the Zone Core

Result: There are several Network Management servers on the ASTRO 25 Network
LAN. The failure of any specific server on the LAN at the active Zone Core
will result in loss of the management function associated with the server,
while the entire system will remain in the Wide Area Trunking mode. The
failure is transparent to all radio and dispatch console users. The failure will

RFP# 101216
December 16, 2010

Scenario: Failure of the Network Management Servers at the Zone Core
affect the Network Management system user.
Protection: Multiple servers running separate applications. Synchronized servers at an
optional geographically separated Zone Core. Spare components for server
computers.
Table 5-13: Failure of Microwave Radio
Scenario: Failure of a Microwave Radio

Result: The proposed microwave radios are arranged in a Loop configuration on
the backbone in addition to hot standby on all links. The failure of a
microwave radio at any site on the network backbone will result in
automatic reroute of traffic around the opposite direction on the loop, which
will allow the system to continue to function in wide-area trunking while the
radio is down. The failure of a microwave radio at any link will result in
automatic switchover to the hot-standby/redundant radio. The entire system
remains in the wide-area trunking mode. The failure is transparent to all
system users. Dispatch console operation remains unaffected.
Protection: Loop microwave radio links and/or hot standby radio configuration.
Table 5-14: Failure of Single Base Station at an ASTRO 25 Simulcast or Repeater Site
Scenario: Failure of a Single Base Station

Result: In a trunking system, multiple channels inherently provide redundancy. The
failure of one base station will be transparent to all system users. The
failure of a repeater will result in the ASTRO 25 Zone Controller removing
the channel from the system, resulting in some reduced channel capacity.
Any calls in progress on the failed channel will be lost, and on the next
push-to-talk, radio traffic will be restored. All other channels in the ASTRO
25 repeater site or Simulcast cell remain unaffected. The entire system
remains in the Wide Area Trunking mode. Dispatch console operation
remains unaffected.
Protection: Multiple channels, multiple potential control channels, spare modules.
Table 5-15: Failure of a Single Control Channel
Scenario: Failure of a Single Control Channel

Result: Motorola trunking systems provide up to four possible control channels in
an ASTRO 25 Simulcast or Repeater Site. If the currently active control
channel fails, another channel automatically takes over and the control
channel as the failed channel is automatically taken out of service. All other
channels within the ASTRO 25 repeater or Simulcast cell remain

RFP# 101216
December 16, 2010

Scenario: Failure of a Single Control Channel
unaffected. The ASTRO 25 repeater or Simulcast cell remains in the wide-
area trunking mode. The failure is transparent to all system users. Dispatch
console operation remains unaffected.
Protection: Multiple potential control channels
Table 5-16: Failure of a Single Dispatch Operator Position
Scenario: Failure of a Single Dispatch Operator Position

Result: The failure of a dispatch operator position will result in that particular
dispatcher moving to another operator position or reverting to the fallback
control station or portable radio. All other dispatch terminals operate
normally and remain unaffected. The entire system remains in the
Simulcast trunking mode.
Protection: Fallback control stations, multiple independent dispatch positions.
Detection: Console user detection, console diagnostics.
Table 5-17: Failure of a Dispatch Center Ethernet Switch
Scenario: Failure of a Dispatch Center Ethernet Switch

Result: The ASTRO 25 network was designed with dual Ethernet switches that
connect the operator positions to the network. Any operator positions
connected to the failed switch will be taken out of service. Upon notification
of the switch failure, the impacted operator positions can be moved to the
functional Ethernet switch.
Protection: Dual switches. Spare switches.
Detection: Console user detection, console diagnostics.
Failure Indications at Supervisory Console

The radio system's fault manager monitors and reports the status of all the hardware
elements in the radio and console subsystems. The supervisory console at each
dispatch center is provided with a fault management terminal, allowing the entire
radio and console network to be fault managed from the same point the rest of the
radio system is fault managed. The specific hardware elements that are monitored are
the dispatch consoles and any networking equipment that support the console
elements. Each hardware element monitors critical internal hardware sub-elements
and reports its status. Failures within a hardware element are detected and displayed
on the fault management terminal.

RFP# 101216
December 16, 2010

Table 5-18: Failure Mode Analysis Matrix
Event Typical Strategy to Extraordinary Mitigation Strategy Proposed for

Causing Mitigate the Network Floyd County
Failure Failure
Failure of Redundant Zone Motorola has provided redundant Zone Controllers
Zone Controllers at the at the Zone Core. Failure of the active Zone
Controller A Zone Core and spare Controller at the Zone Core will result in automatic
at the Zone boards for the Zone switchover to the redundant Zone Controller. As
Core Controllers the switchover process takes place, the system
will temporarily enter site trunking mode for a
period less than 60 seconds. Wide area trunking
will be restored when the switchover process is
complete. Any and all calls generated after
automatic switchover to the redundant controller
will not observe any change of service. During the
transition, the dispatch operators will revert to
operating on desktop Control Stations. The Zone
Controllers have redundant power supplies as a
standard feature, which will help keep the
controllers operational in case of a failure of that
component. The redundant controller is regularly
updated with all pieces of critical information so
that if it needs to become the active controller, the
current system configuration and operational
characteristics are maintained.
Failure of Spare boards, In the unlikely event that both the active and
Zone Optional Backup Zone redundant Zone Controllers fail, the system will
Controller A Core at a automatically switch over to Site Trunking at all
and B at geographically ASTRO 25 RF Sites. The ASTRO 25 Trunked RF
the Zone separate location, sites will continue to trunk in their respective cells
Core Backup WAN links at and coverage areas; however, there will be no
each remote direct linking of calls between the ASTRO 25
Simulcast site, Simulcast Cell and Rocky Mtn Repeater Site.
ASTRO 25 Trunked Users within an RF cell will be able to operate in
repeater site, and the trunking mode within their respective site’s
dispatch sites coverage. When the Zone Controllers come back
online, the system will return to Wide Area
Trunking.
Failure of a Dual Zone Core Motorola's ASTRO 25 system employs dual Zone
Zone Core Ethernet Switches Core Ethernet Switches at the Zone Cores. All
LAN Switch equipment critical for wide-area voice
at the Zone communications has connections to both
Core switches. Failure of one Ethernet Switch on the
active Zone Core will cause the LAN traffic to use
the other switch. The entire system remains in the
Simulcast Wide Area Trunking mode. The failure
is transparent to all system users.

RFP# 101216
December 16, 2010

Failure Failure
Failure of Spare Enterprise In the unlikely event that both Zone Core LAN
both Zone Switch, Backup Zone Switches fail at the Zone Core, the system will
Core LAN Core at a physically automatically switch over to Site Trunking at all
Switches at separate location ASTRO 25 RF Sites. The ASTRO 25 Trunked RF
the Zone sites will continue to trunk in their respective cells
Core and coverage areas; however, there will be no
direct linking of calls between the ASTRO 25
Simulcast Cell and Rocky Mtn Repeater Site.
Users within an RF cell will be able to operate in
the trunking mode within their respective site’s
coverage. When the LAN switches come back
online, the system will return to Wide Area
Trunking.
Failure of a Redundant Core The Zone Core configuration for the proposed
Zone Core Router, Spare Core Floyd County system consists of redundant Core
Core Router, Redundant Routers. The Core Routers are configured so that
Router at site links all RF cells and dispatch centers are connected to
the Zone both Core Routers. Failure of one Core Router at
Core the active Zone Core will result in automatic
switchover to the redundant Core Router. The
entire system remains in Wide Area operation.
The failure is transparent to all system users.
Failure of Redundant Core The Zone Core configuration for the proposed
Both the Router, Spare Core Floyd County system consists of two Core
Main and Router, Redundant Routers. The Core Routers are configured so that
Redundant Site Links all RF cells and dispatch centers are connected to
Core both Core Routers. In the unlikely event that both
Routers at Core Routers fail, the system will automatically
the Zone switch over to Site Trunking at all ASTRO 25 RF
Core Sites. The ASTRO 25 Trunked RF sites will
continue to trunk in their respective cells and
coverage areas; however, there will be no direct
linking of calls between the ASTRO 25 Simulcast
Cell and Rocky Mtn Repeater Site. Users within
an RF cell will be able to operate in the trunking
mode within their respective site’s coverage.
When the Zone Controllers come back online, the
system will return to Wide Area Trunking.
Failure of Multiple servers The failure of any specific server on the LAN at
the running separate the active Zone Core will result in loss of the
Network applications, management function associated with the server,
Manageme Synchronized servers while the entire system will remain in the Wide
nt Server at at an optional Area Trunking mode. The failure is transparent to
the Zone geographically all radio and dispatch console users. The failure
Core separated Zone Core, will affect the Network Management system user.
Spare components for
server computers

RFP# 101216
December 16, 2010

Failure Failure
Failure of a Loop microwave radio The proposed microwave radios are hot standby
Microwave links or hot standby all links. The failure of a microwave radio at any
Radio radio configuration site on the network backbone will result in
automatic switchover to the hot-standby/redundant
radio. The entire system remains in the wide-area
trunking mode. The failure is transparent to all
system users. Dispatch console operation remains
unaffected.
Failure of a Loop-path The failure of a microwave path between any site

Microwave configuration, on the backbone loop will cause the loop traffic to
Path Redundant T1 links reroute around the break and the system will
remain in Wide Area Trunking. The failure of a
microwave path between any spur site will result
in loss of dispatch connectivity for the site
separated by the break on the spur. The system
will remain in Wide Area Trunking and the affected
dispatch center(s) will switch to control stations for
dispatch operations. Motorola has also proposed
redundant site routers.
Failure of a Multiple channels, In a trunking system, multiple channels inherently
single Base multiple potential provide redundancy. The failure of one base
Station control channels, station will be transparent to all system users. The
spare modules failure of a repeater will result in the ASTRO 25
Zone Controller removing the channel from the
system, resulting in some reduced channel
capacity. Any calls in progress on the failed
channel will be lost, and on the next push-to-talk,
radio traffic will be restored. All other channels in
the ASTRO 25 repeater cell remain unaffected.
The entire system remains in the Wide Area
Trunking mode. Dispatch console operation
remains unaffected.
Failure of a Multiple potential Motorola trunking systems provide up to four
Single control channels possible control channels in an ASTRO 25 RF
Control Site. If the currently active control channel fails,
Channel another channel automatically takes over and the
control channel as the failed channel is
automatically taken out of service. All other
channels within the ASTRO 25 RF cell remain
unaffected. The ASTRO 25 RF cell remains in the
wide-area trunking mode. The failure is
transparent to all system users. Dispatch console

RFP# 101216
December 16, 2010

Failure Failure
operation remains unaffected.
Failure of a Fallback control The failure of a dispatch operator position will

Single stations, multiple result in that particular dispatcher moving to
Dispatch independent dispatch another operator position or reverting to an
Operator positions optional fallback control station or portable radio.
Position All other dispatch terminals operate normally and
remain unaffected. The entire system remains in
the trunking mode.
5.3 ASTRO 25 System Options
5.3.1 Transportable Trunked Repeater (Site on Wheels)

Motorola is proposing a deployable Pepro trailer which will be equipped with an
ASTRO 25 Express system. An ASTRO 25 Express system is a single-site,
standalone P25 Phase I Compliant trunking system. The trailer will be equipped with
three 800 MHz GTR 8000 stations and three 700 MHz GTR 8000 stations in an ESS
(Expandable Site Subsystem) configuration. The primary ESS rack will be
configured with three 800 MHz GTR 8000 stations, redundant site controllers, one
six-port 800 MHz combiner, and a six-port multicoupler. The secondary ESS rack
will be configured with three 700 MHz GTR 8000 stations, one six-port 700 MHz
combiner, and a six-port multicoupler.
5.3.1.1 Proposed Equipment Configuration

The deployable Pepro Low Profile SMRS-650 3-Bay trailer is a 3-bay trailer that can
accommodate up to four 19-inch racks with 24 rack units each for a total of 96 rack
units of space.
♦ The Pepro trailer will be built to meet Motorola’s R-56 standards.
♦ Some allowances will have to be made due to the physical size and mobility of
the trailer.

RFP# 101216
December 16, 2010

♦ All of the proposed deployable site equipment will be powered by 120 Volt single
phase power.
♦ The three 800 MHz stations and the 700 MHz stations will be programmed using
frequencies licensed by Floyd County specifically for the deployable site.
♦ Two 700/800 MHz 6 dB omni directional antennas, one transmit and one receive,
will be mounted on the trailer’s antenna mast.
The SMRS-650 3-Bay deployable trailer comes equipped with the following:
Power Distribution Assembly Module

♦ Shore power connection with Manual Transfer Switch
♦ Surge Suppressor
♦ 120/240 Volt Single-Phase – 100 Amp Load Center
♦ Main transitional ground lug
60 foot Un-guyed Articulated Tower
♦ Meets or exceeds TIA/EIA-222-G specifications for permanent antenna sites

♦ Tower raised and lowered hydraulically
♦ Includes four antenna mounting brackets
♦ Can be deployed by two people within 30 minutes
Generator
♦ 12kW diesel generator

♦ Maximum of 7825 watts of equipment load
♦ 100-gallon diesel fuel tank (provides 3-4 day runtime)
Trailer
♦ 21-foot trailer length, diamond plate deck

♦ Corner hydraulic leveling jacks and tongue jack
♦ All-electric braking system
♦ Bumper hitch
♦ Self-grounded with deployment of downriggers
♦ Trailer GVWR (Gross Vehicle Weight Rating) of 18,400 lbs

RFP# 101216
December 16, 2010

Figure 5-24 below is an example of the SMRS-650 3-Bay deployable trailer in
stowed state.
Figure 5-24: SMRS-650 3-Bay Deployable Trailer – Stowed State
Towing Vehicle Specifications

The Trailer Gross Vehicle Weight Rating (GVWR) for the SMRS-650 3-Bay model is
18,400 lbs. The tongue weight (based on 15% of the GVWR) is 1650 lbs. Based
upon these specifications, it will be the responsibility of Floyd County to contact their
dealership to ensure an appropriate vehicle is used.
*Motorola will not be providing a vehicle to be used with the trailer.
♦ The assumptions made are as follows:
• No specific coverage guarantee is made due to the deployable nature of the
site.
• Price does not include furnishing plot plans, legal descriptions, or site
surveys.

RFP# 101216
December 16, 2010

• No costs have been included for the development of any additional subscriber
equipment, subscriber fleetmaps or templates or any subscriber programming.
If requested, Motorola can provide a quote for these items.
5.3.2 Mobile Repeaters (Digital Vehicular Repeater System)

Motorola is proposing a Futurecom Digital Vehicular Repeater System (DVRS) to
meet Floyd County’s requirements for a Mobile Repeater.
The P25 DVRS allows Portable Subscriber Units (PSU) to be used in areas where
only Mobile Subscriber Unit (MSU) coverage is available and PSU coverage is either
intermittent or non existent. Installed in the trunk of a car, fire truck, armored
vehicle, ambulance or configured as a Transportable DVR, the DVRS extends radio
communications when the PSU users are outside of the vehicle, inside a nearby
building or in any marginal portable coverage areas.
5.3.2.1 Proposed Equipment Configuration

The DVRS proposed utilizes the mobile radio installed in the vehicle and can be
enabled or disabled when required. Some features include:
5.3.2.2 DVRS Modes of Operation

When a “DVRS Enabled” TG / Channel is selected on the Control Head, the DVR
can be switched to one of the following Modes – OFF, LOCAL or SYSTEM.
OFF mode is used when the DVRS repeat is not required (for example while the PSU
user is in the vehicle driving).
LOCAL mode is used in some tactical applications when only portable-to-portable
communications are required. Inbound calls are not repeated to the system in the
LOCAL mode i.e. the calls received by the DVRS are repeated locally but the MSU
does not key up. As an option, the DVRS can be programmed to repeat System
outbound calls to the local PSU users. As an option the MSU can be programmed to
key up when the DVR is receiving inbound calls from the local PSUs.
SYSTEM mode enables full DVRS repeat – locally and to the System. Outbound
calls received by the mobile radio are repeated by the DVRS to the local PSUs over
the DVRS channel. Inbound calls received by the DVRS are repeated locally
(portable-to-portable) as well as to the system users (by keying up the mobile radio).
Power ON/OFF
The DVRS is powered ON / OFF when the mobile radio is powered ON/OFF.
Activation
The DVRS can be activated by any of the following:

RFP# 101216
December 16, 2010

♦ External contact closure (external switch, provided by others)
♦ MDC1200 Emergency Alarm received from portable radio
♦ Preprogrammed activation DTMF code sent from portable radio (no feedback to
the portable will be provided when the system is disabled)
Deactivation
The DVRS is switched OFF (and ON) by using an external lit up switch (due to
various mounting requirements switch is to be provided by installer).
Wideband & Narrowband Operation

The DVRS supports programmable 12.5kHz and 25kHz adjacent channel spacing
operation.
PSU Group Calls

When the Digital Vehicular Repeater System (DVRS) is ON, a local Portable
Subscriber Unit (PSU) call received by the DVRS is repeated to the System by the
mobile on the currently selected mobile mode / channel (if steering is not enabled).
If steering is enabled, the mobile is steered to a pre-programmed mode, determined
by the PL sent by the PSU. In this case the inbound PSU call is repeated on the new
(steered) mode.
Outbound calls received by the mobile are repeated by the DVRS to the analog PSUs.
PSU Emergency Alarm

An MDC1200 Emergency Alarm sent by the PSU is decoded by the DVRS and the
DVRS triggers the mobile radio emergency. If steering in Emergency is enabled, the
DVRS steers the MSU to the proper channel and then triggers mobile emergency.
The dispatcher receives the emergency Alarm with the mobile radio ID, not with the
PSU ID.
The PSU user can receive an acknowledgement tone indicating Emergency Alarm
has been received by the DVRS.
If the DVRS is OFF and it receives Emergency Alarm (requires PSU and DVRS to be
on the same channel and PSU emergency retries programmed to exceed the DVRS
counter), it automatically switches to ON mode to process the Emergency Alarm to
the System.
If programmed for VRS-EP compatible operation, the DVRS supports PL emergency
alarm and does not support MDC1200 signaling.

RFP# 101216
December 16, 2010

Trailing Tones
At the end of each call (when the PSU user releases the PTT), the DVRS sends
trailing tones over the air to advise the PSU user if the call was successfully
transmitted by the APX6500 to the system (the mobile radio was keyed up) or not. A
short high pitched tone indicates to the PSU user that the mobile radio did key up
while a low pitched tone indicates that the call was not transmitted to the system (the
mobile radio did not key up). The trailing tones are transmitted over the air and
received by all PSUs that are on the same DVRS channel and in the coverage range
of the DVRS. When the PSU user is alerted by the tones that the transmission to the
system was not successful, he/she can repeat the call.
5.3.3 InterZone System Connectivity compared to ISSI.1

This section of the system description has been developed to specifically address the
differences between Motorola’s “InterZone” solution and the P25 ISSI.1 product.
This section will discuss the user equipment, system infrastructure and the P25 ISSI
connectivity equipment.
Terminology: Definitions and Acronyms

It is necessary to provide some basic terminology and acronym definitions. These
terms are consistent with those used in the Standard, to the best of our knowledge and
except where noted.
P25 ISSI (Project 25 Inter/Intra RF Subsystem Interface) – The P25 ISSI
standard supports both single and multiple System ID configurations and enables two
or more disparate, trunked, P25 networks (RFSSs) to be connected at the network
layer, in order to provide voice and data services, end to end AES encryption and
intersystem roaming.
CCH – Control Channel
CSSI (Console Subsystem Interface) – This rides “on top of” the ISSI and enables a
Console Operator to control a call which is operating across two systems using a
CSSI/ISSI interface. This was previously a separate standard but has recently been
integrated into the ISSI standards documents suite.
RFSS (RF Subsystem) - Defined as an entity which terminates a P25 interface, such
as the P25 Phase 1 CAI, or in this document, a P25 ISSI.
Motorola RFSS - A network which has a single System ID and could be a single
zone system or multiple zones connected using an InterZone interface and using a
single System ID.
InterZone – A zone level end to end solution which connects multiple zones at the
peer to peer “zone level”. InterZone manages and arbitrates call control among zones.

RFP# 101216
December 16, 2010

Motorola uses the terms “InterZone” and “multi-zone” interchangeably. Both refer to
an end-to-end solution embedded in our core network, stations and subscribers.
ISSI TG – A talkgroup which is enabled on more than one system, operates across a
P25 ISSI interface, and enables a radio user affiliated to the ISSI TG to connect to a
Serving RFSS or move between systems while staying connected to their Home
RFSS.
Home RFSS - An ISSI TG can have only one Home RFSS; it is the call control
entity which controls the call and manages "floor control", regardless of which
system the radios are operating. Home RFSS is not the same as the “Home Zone”
inside a Motorola network.
Serving RFSS – This is an RFSS which has an active ISSI TG users affiliated to it,
but is not the Home RFSS for the ISSI TG.
"Embedded ISSI" - An ISSI-capable RFSS which has ISSI messages on CCH and
in Subscribers. For full operation it requires that the entire network (core, CCH,
radios) be upgraded so that radios understand new messages and can roam between
systems without touching them. This is not a term used in the standard.
Next Generation ISSI (NGI) - Motorola's planned implementation for the
"embedded" ISSI version which requires changes to the zone level interface, network
and control channel messages.
ISSI.1 Gateway Application - Motorola's ‘bolt on’ implementation which operates
without changing network, CCH or radios
Long IDs - This is the major change in the embedded ISSI, noted here as ("TG
1000000"); these are unique across systems.
Subscriber Unit (SU)
Notes and Assumptions

The discussion of the differences between the ISSI and Motorola’s Interzone is based
upon the following assumptions.
♦ The Project 25 ISSI standard is fully implemented with the current definition of
Scope 1 and Scope 2 as described in this document. This content is subject to
change based upon the P25 committee actions.
♦ That when connecting two networks of the same manufacturer, solutions other
than a P25 ISSI could also be used.
♦ Other manufacturers will eventually implement all features in the P25 ISSI Scope
1 and Scope 2. Although Motorola has been told by the other manufacturers that
the features will “phased in over time”, this document assumes the “final” ISSI
release such that the manufacturer has implemented all the capabilities in the
standard.

RFP# 101216
December 16, 2010

♦ This document assumes only the features in the standard are implemented.
♦ To a Motorola system user the term “Supplementary Data Services” may be
unfamiliar. This functionality refers to capabilities enabled by Control Channel
messages. Most of these features originated in Motorola’s SmartZone platform
and are in the Radio Control Manager and were carried over into the ASTRO 25
architecture.
General Cautionary Notes

♦ All of the issues associated with the ISSI are highly complex. This is an
unfortunate reality of the complex issues involved.
♦ To connect to any given Project 25 manufacturer, the only technology capable of
connecting to that Project 25 trunked system is a gateway from that manufacturer.
(Only a Motorola ISSI gateway can connect to a Motorola network, only a
competitor A ISSI gateway can connect to competitor A, etc.)
♦ Regardless of how many features an ISSI gateway manufacturer implements, the
end-to-end functionality across an ISSI among different manufacturers will
always be confined to the lesser functionality of the two. We call this the “least
common denominator.” This implies that in order to get all of the features
specified in the ISSI standard, multiple manufacturers will have to implement
ALL of them. It is Motorola’s view that this is an impractical assumption given
the level of investment required by each. Still, for the purposes of this document
we are ignoring this factor.
♦ Requesting a comparison of “InterZone and ISSI” essentially requires us to
project an ISSI implementation which would ultimately rely upon our
competitors’ ISSI implementation. Just as no competitor should speak to
Motorola’s implementation, we are profoundly uncomfortable predicting another
supplier’s solution.
♦ InterZone is an existing end to end solution, addressing multiple layers of the
network, has been shipping since 1998 and has been operating with mission
critical users every day for almost ten years.
♦ The ISSI addresses a relatively small part of the technology required to actually
implement a solution which utilizes the P25 ISSI interface. More specifically, for
our initial release, the ISSI.1 Gateway Application, the P25 ISSI specification
affects only about 10% of the technology which must be built to enable
deployment on live networks.
♦ Motorola is planning to implement two tiers of ISSI implementations, which
further confuses this issue. For the purposes of this paper, we are not referring to
either implementation. More information on our specific plans is available upon
request.
♦ The Console Subsystem Interface or CSSI was previously seen as a separate
standard. As of the January TIA meetings this Console Priority functionality has
been integrated into the ISSI standard.
♦ In order to enable the complete set of defined ISSI features, an “embedded ISSI”
will be required. As noted in the definitions, the Embedded ISSI implementations
RFP# 101216
December 16, 2010

require changes to the P25 Phase 1 CAI control channel (additional messages),
corresponding changes to P25 Phase 1 subscribers and changes to the P25 trunked
network core. Although manufacturers will phase these changes in over time, it
should be understood that no manufacturer of P25 CAI compliant equipment has
the total solution implemented and shipping today.
♦ Many, many of the features which will operate over the ISSI will do so in a
manner different from how the features operate on a single P25 or ASTRO
network today. In most cases the operation on the ISSI is limited in some fashion.
We are offering some detail on these limitations and in areas where we do not
articulate these details; we are still in the process of understanding them
ourselves.
♦ At this juncture, we must assume the ISSI standard is essentially a fixed scope
and that any feature which is planned to be added to the ASTRO 25 network will
not be included in the current version of the standard.
♦ Some of the capabilities articulated as “beyond” the ISSI could, in practice, be
supported for the situation in which a Motorola radio is the terminating device
operating over the ISSI. Still, these are beyond the ISSI definition.
♦ The feature detail information is preliminary and subject to change.
Features in the Standard

Based upon the content in the following existing or planned documents, the Trunked
ISSI standard is assumed to include the feature scope articulated below.
TIA-102.BACA-A (replaces TIA-102.BACA, TIA-102.BACA-1 Errata, TIA-
102.BACA-3 Addendum)
Trunked ISSI Scope 1

♦ Group Registration
♦ Subscriber Mobility
♦ Trunked Call Control
♦ IP Protocol selection (SIP, RTP)
♦ Talkgroup Call
♦ Unit to Unit Call (aka P25 Private Call)
Trunked ISSI Scope 2

♦ Console Dispatch traffic over the ISSI (CSSI), includes ONLY:
• Console Priority over SU transmissions
• Console Takeover of another console transmission
• Acoustic Cross-mute of adjacent audio (in dispatch room)
• Detection that multiple received audio streams are from the same audio source
♦ Project 25 Packet Data
♦ Supplementary Data Services
• Emergency Alarm

RFP# 101216
December 16, 2010

• Call Alert
• Status Message
• Selective Radio Inhibit
• Dynamic Regrouping
Capabilities Offered by InterZone beyond ISSI

With a baseline of understanding of the many caveats and assumptions related to this
question, the follow section articulates the features enabled by an InterZone solution
which will not be available on a P25 ISSI connection.
General Attributes of InterZone Which go Beyond the ISSI
♦ InterZone has Multiple Layers of Failure Mode Handling at the Call
Processing Layer built into the call processing architecture. This includes
fallback scenarios involving the Home and Participating Zones, Zone level
trunking, and more importantly, robust recovery modes which enable maximum
connectivity as the network comes back online. These capabilities are beyond the
scope of this section.
♦ Dispatch Console Features – The CSSI has only (4) features defined. By
comparison our MCC 7500 console has over 400 features; an itemized
comparison is beyond the scope of this section.
♦ Full Network Redundancy for 5NINES reliability (redundant links, devices,
automatic switchover, etc.) for robust end to end connectivity, and management
of Quality of Service and performance.
♦ Information Assurance for Network Security among connected networks,
including firewall support, integrated router encryption and encrypted
management links.
♦ Integrated and intelligent Fault Management, Monitoring and Configuration
♦ InterZone will have better end to end delay performance due to the required
connectivity between systems and additional processing time required to manage
the calls over a SIP-based call control protocol.
♦ InterZone Systems use today’s radios which can roam without changes to
software.
Features and Call Services beyond the ISSI

♦ MultiGroup Call
♦ Telephone Interconnect Service
♦ Enhanced Private Call (different than P25 Private Call)
♦ Busy Queuing and Callback
♦ AllStart™ Call Set-up
♦ FastStart™ Call Set-up
♦ Fully-capable Group Call Scan
♦ Priority Monitor of Affiliated Talkgroups (limited)

RFP# 101216
December 16, 2010

♦ Coordinated Aliases Across networks
♦ 10 Talkgroup Priority levels – Limited (have to be manually coordinated or will
be different)
♦ Critical Site using FastStart
♦ Recent User Priority
♦ Dynamic Site Assignment
♦ Adjacent Site Information for Fast Roaming (can be addressed by manually
configuring a fixed “primary” control channel for all boundary sites)
♦ Packet Data Applications such as OTAR, POP25 and Text Messaging
♦ Active Call Continuation (can be improved by manually configuring a fixed
“primary” control channel for all boundary sites, otherwise CCH scan required to
roam)
♦ InterSystem Roaming While in Busy Queue
♦ Continuous Assignment Updating
♦ Dynamic System Resilience
♦ High Performance Data
♦ SuperGroup (Group ReGrouping)
♦ Console Busy Indication and Callback
♦ Call Alert through Paging from a Console
♦ Console Normal/Tactical
♦ Talkgroup Repeat Disable
♦ Adjacent Control Channel OSW (outbound signaling word)
♦ Zone Manager Configuration Services
♦ Monitoring via ZSS
♦ InterZone Control Path configuration
♦ ZDS Backup and Restore
♦ Fault Alarm Browser
♦ Alert Information Access
♦ Secure OmniLink Air Traffic Information
♦ System Level ATIA
♦ ZoneWatch Interzone Channel Grid Display
♦ Bidirectional CADI
♦ System Wide Historical Reports
5.3.4 Dual Prime Site Option

The benefit of Simulcast is the ability to vote incoming transmissions and repeat the
best signal at all remote sites. The limitation of Simulcast is the remote site’s
dependence on the Prime Site to provide all audio and control guidance. In order to
limit Floyd County’s exposure, Motorola has proposed the main Prime site to be co-
located at the Mt. Alto site. In the event that Mt Alto is isolated from the rest of the
Simulcast sites, Mt Alto will continue to provide Trunking to the field users without
the other remote sites. However, should something catastrophic occur at Mt Alto, the

RFP# 101216
December 16, 2010

Simulcast system would be rendered useless, and the field users would be forced to
use the ITAC channels.
However, Motorola has provided optional pricing for adding a dual-Prime site at the
Floyd 911 center. This alternate Prime site would be manually activated upon
verification of a catastrophic failure at Mt Alto. The Simulcast system would then be
restored to provide full Trunking features and would provide Trunking coverage
using eight channels at all Simulcast RF sites (except Mt Alto).
The dual-Prime solution will eliminate any single point of failure remaining in the
Simulcast system.
5.3.5 Supplemental Rural RF Coverage Site Options

Motorola has provided our best interpretation of the RFP coverage requirements and
has met the 95% county-wide coverage. However, Motorola has provided several
site solutions to provide additional levels of coverage beyond the ability of the
Transportable Trunked Repeater and Mobile Repeater. Motorola has identified a 3-
channel ASTRO25 Trunking repeater site for seamless Trunking access and a single-
channel conventional P25 repeater (similar to the Jail and Prison repeaters) for
regional communications. Both solutions can be integrated into the dispatch console
wirelessly or using microwave. Microwave is not included in each site cost.
5.3.5.1 3-Channel ASTRO25 Trunking Repeater Site
ASTRO 25 Site Repeater (ASR) Equipment

♦ GGM8000 Gateway
♦ (1) GTR8000 ESS cabinet containing
(3) Three GTR 8000 Base Stations
(1) One six-channel Transmit Combiner
Monitoring system
(1) One six-channel Receiver Multicoupler system
♦ (1) One Tower Top Amp (TTA)
♦ -48VDC Rectifier Plant with N+1 redundancy and Batteries
♦ (1) 170 foot Monopole
♦ (1) Pepro Outdoor Enclosure

RFP# 101216
December 16, 2010

5.3.5.2 Conventional P25 Repeater Site
Conventional P25 Repeater Site Equipment

♦ (1) One GTR 8000 Base Station
♦ (1) One Duplexer Transmit and Receive antenna
♦ -48VDC Rectifier Plant with N+1 redundancy and Batteries
♦ (1) 170 foot Monopole
♦ (1) Pepro Outdoor Enclosure
5.4 P25 PH1 Trunked System Feature Matrix

P25 PH1 TRUNKED SYSTEM FEATURE MATRIX chw
Last Updated: June 14, 2010/ Version 13.0

P25 PH1 TRUNKED FEATURE NAME MOTOROL TIA STANDARDS
A OFFERS DOCUMENTS
in Release
7.8
P25 PH1 CAI TRUNKING – PHASE ONE COMMON AIR INTERFACE
VOICE CALLS
Group Voice Call Yes TSB102-A/ TIA-102.AABD/
TIA-102.AABC-B /
TIA-102.AABF-A
Individual Voice Call Yes TSB102-A/ TIA-102.AABD/
TIA-102.AABC-B /
TIA-102.AABF-A
Availability Check on Called Party Yes TIA-102.AABD
Broadcast Voice Call Yes TSB102-A/ TIA-102.AABD
Announcement Group Call Yes TIA-102.AABD
Emergency Group Voice Call Yes TIA-102.AABD
MOBILITY MANAGEMENT
Roaming Yes TSB102-A / TIA-102.AABD/
TIA-102.AABC-B
Intra-System Roaming (Automatic) Yes TSB102-A / TIA-102.AABD/
TIA-102.AABC-B
Inter-System Roaming (Manual) Yes TSB102-A / TIA-102.AABD/
TIA-102.AABC-B
Registration Yes TSB102-A / TIA-102.AABD /
TIA-102.AABC-B
Restricting service access only to valid Yes TIA-102.AABD
SU

RFP# 101216
December 16, 2010

De-registration Yes TIA-102.AABD / TIA-

102.AABC-B
Group Affiliation Yes TSB102-A / TIA-102.AABD /
TIA-102.AABC-B
Call Restriction Yes1 TSB102-A / TIA-102.AABC-B
Call Routing Yes TSB102-A
Wide Area Call Yes TIA-102.AABD
Location Registration Yes TIA-102.AABD
WUID Validity Timer Yes TIA-102.AABD
KEY MANAGEMENT
KFD Based Key Management
Manual Rekeying Features Yes TIA-102.AACD
Key Load Yes TIA-102.AACD
Key Erase Yes TIA-102.AACD
Erase all Keys Yes TIA-102.AACD
View Key Info Yes TIA-102.AACD
KMF Based Key Management
Unique Key Yes TIA-102.AACD, TIA-
Encryption Key 102.AACA
(UKEK)
Individual Radio Set Yes TIA-102.AACD, TIA-
Identifier (Ind RSI) 102.AACA
Key Management Yes TIA-102.AACD, TIA-
Facility Radio Set 102.AACA
Identifier (KMF RSI)
Message Number Yes TIA-102.AACD, TIA-
Period (MNP) 102.AACA
Key Load Yes TIA-102.AACD, TIA-
102.AACA
View Individual RSI Yes TIA-102.AACD, TIA-
102.AACA
Load Individual RSI Yes TIA-102.AACD, TIA-
102.AACA
View KMF RSI Yes TIA-102.AACD, TIA-
102.AACA
Load KMF RSI Yes TIA-102.AACD, TIA-
102.AACA
View MNP Yes TIA-102.AACD, TIA-
102.AACA
Load MNP Yes TIA-102.AACD, TIA-
102.AACA
View Keyset Info Yes TIA-102.AACD, TIA-
102.AACA
Activate Keyset Yes TIA-102.AACD, TIA-
102.AACA
SECURITY SERVICES
Confidentiality
Encryption Transformation
Traffic Encryption Yes2 TIA-102.AAAB-A, TIA-
102.AAAD/

RFP# 101216
December 16, 2010

TIA-102.AAAA-A/ TIA-
102.AAAC/
TIA-102.AAAD
Integrity
Chronological Integrity Yes3 TIA-102.AAAB-A
Message Integrity Yes4 TIA-102.AAAB-A
Authentication (Link Layer Authentication) Future TIA-102.AACE
SU Authentication (Authentication of SU by Future TIA-102.AACE
FNE)
Key Management Yes TIA-102.AAAB-A/ TIA-
102.AACA
Physical Key Distribution Yes TIA-102.AAAB-A/ TIA-
102.AACA
Over-the-Air Key Distribution Yes TIA-102.AAAB-A/ TIA-
102.AACA
Key Download Yes TIA-102.AAAB-A/ TIA-
Procedures 102.AACA
Key Activation Yes TIA-102.AAAB-A/ TIA-
Procedures 102.AACA
Destruction of Keys Yes TIA-102.AAAB-A/ TIA-
102.AACA
Rekey Request Yes TIA-102.AAAB-A/ TIA-
102.AACA
Provisioning of the Yes TIA-102.AAAB-A/TIA-
MR 102.AACA
Key Compromise Yes5 TIA-102.AAAB-A/ TIA-
102.AACA
ENCRYPTION
Encryption Yes TSB102-A / TIA-102.AAAB-A
/
TIA-102.AAAD / TIA-
102.AACD /
TIA-102.AACA / TIA-
102.AACB
DES-OFB Encryption of Voice Yes TSB102-A / TIA-102.AAAD
AES Encryption of Voice Yes TIA-102.AAAD
AES Encryption of Packet Data Yes TIA-102.AAAD
Multiple Encryption Algorithms Yes TIA-102.AACA
Multiple Encryption Keys Yes TIA-102.AAAD
SUPPLEMENTARY SERVICES
Priority Call Yes TSB102-A / TIA-102.AABD
Preemptive Priority Call Yes6 TSB102-A / TIA-102.AABD-A
/ TIA-102.BACA / TIA-
102.BACE
Dispatcher Audio Takeover Yes TSB102-BAGA
Emergency Alarm Yes TSB102-A / TIA-102.AABD /
TIA-102.AABC-B
Silent Emergency Yes TSB102-A
Radio Unit Monitoring Future7 TSB102-A / TIA-102.AABD /
TIA-102.AABC-B

RFP# 101216
December 16, 2010

Talking Party Identification Yes TSB102-A

Call Alerting Yes TSB102-A / TIA-102.AABD /
TIA-102.AABC-B
Radio Check Yes TIA-102.AABD / TIA-
102.AABC-B
Radio Inhibit Yes TIA-102.AABD / TIA-
102.AABC-B
Radio Uninhibit Yes TIA-102.AABD / TIA-
102.AABC-B
Alert Tones Yes TIA-102.AABD
Emergency Call Yes TIA-102.AABD
Pre-Programmed Emergency Group Call Yes TIA-102.AABD
Group Emergency Behavior during an In- Yes TIA-102.AABD
Progress Emergency Call
SU Status Update Yes TIA-102.AABC-B / TIA-
102.AABD-A / TIA-102.AABG
/ TIA-102.BACD
SYSTEM SERVICES
Network Status Broadcast Message Yes TIA-102.AABD
System Status Broadcast Message Yes TIA-102.AABD
Channel Identifier Update Broadcast Yes TIA-102.AABD
Message
Adjacent Status Broadcast Message Yes TIA-102.AABD
Secondary Control Channel Broadcast Yes8 TIA-102.AABD
Backup Control Channel Broadcast Message Yes TIA-102.AABD
MISCELLANEOUS
Electronic Serial Number Yes TSB102-A
Queuing Yes TIA-102.AABD
Message Trunking Yes TIA-102.AABD
Transmission Trunking Yes TIA-102.AABD
Network Access Code Yes TIA-102.AABD
Extended hunt sequence Yes TIA-102.AABD
PHYSICAL LAYER
CAI Yes TSB102-A / TIA-102.BAAA-A
9
Enhanced Full Rate Vocoder Yes TSB102-A / TIA-102.BABA
12.5 KHz Channel Bandwidth Yes TIA-102.CAAA-B /
TIA-102.CAAB-B
Frequency Division Multiple Access (FDMA) Yes TSB102-A / TIA-102.BAAA-A
9.6 kbps Gross Bit Rate Yes TSB102-A / TIA-102.BAAA-A
C4FM and CQPSK Modulation Yes TSB102-A / TIA-102.BAAA-A
/ TIA-102.CAAA-C / TIA-
102.CAAB-B
DATA SERVICES
Packet Switched Confirmed Delivery Data Yes TSB102-A / TIA-102.BAEB-A
Packet Switched Unconfirmed Delivery Data Yes TSB102-A / TIA-102.BAEB-A
Packet Switched Data Network Access Yes TSB102-A / TIA-102.BAEB-A
Data Configuration - Radio to FNE Yes TIA-102.BAEA-A / TIA-
102.BAEB-A / TIA-102.BAEE-

RFP# 101216
December 16, 2010

A
Packet Data Registration Yes TIA-102.BAAD-1. / TIA-
102.BAEB-A
SU Registration Yes TIA-102.BAAD-1. / TIA-
102.BAEB-A
SU Deregistration Yes TIA-102.BAAD-1. / TIA-
102.BAEB-A
SU Location Tracking Yes TIA-102.BAAD-1. / TIA-
102.BAEB-A
Mobile Data Interface (A) Yes TSB102-A / TIA-102.BAEB-A
Link Layer and Physical Layer Protocols Yes TIA-102.BAEA-A / TIA-
102.BAEB-A
SNDCP (Sub network Dependent Yes TIA-102.BAEB-A
Convergence Protocol)
Fixed Host Data Interface (Ed) Yes TSB102-A / TIA-102.BAEB-A
Ethernet (802.3) Yes TIA-102.BAEB-A
Internet Protocol Suite Yes TIA-102.BAEB-A
P25 ISSI/CSSI - INTER RF SUB-SYSTEM INTERFACE/ CONSOLE SUB-SYSTEM INTERFACE
VOICE SERVICES
Group Voice Service
Unconfirmed Group Voice Service Yes, ISSI.1 TIA-102.BACA
Emergency Call Yes, ISSI.1
MOBILITY MANAGEMENT FUNCTIONS
Group Affiliation Yes, ISSI.1 TIA-102.BACA
Group Tracking Yes, ISSI.1 TIA-102.BACA
RFSS Service Capability Polling Yes, ISSI.1 TIA-102.BACA-2
P25 TELEPHONE INTERCONNECT
Telephone Interconnect Yes10 TIA-102.BADA / TIA-
102.AABD
Notes:
1
Motorola Network Management provides the capability to provision the services available to both
subscriber radios and talkgroups.
2
Traffic Encryption is made up of two parts; Voice Traffic Encryption and Encrypted Integrated Data.
Voice Traffic Encryption is defined by the P25 standard and Motorola offers. Today there is no
published P25 standard for Encrypted Integrated Data however Motorola started offering this feature
in the 7.8 release
3
Today the Project 25 standard defines Chronological Integrity for OTAR, which Motorola offers
4
Today the Project 25 standard defines Message Integrity for OTAR, which Motorola offers. The
Project 25 standard will also support Message Integrity in the future Packet Data Security standard.
Currently, Motorola supports Message Integrity for Encrypted Integrated Data.
5
Zerorize and No Service procedures can be used in Key Compromise situation
6
Motorola understands this feature to mean Emergency Priority will Pre-empt a Non-Emergency
Call

RFP# 101216
December 16, 2010

7
In a future release Motorola will support remote unit monitor for talkgroup calls however it will not
support the U2U version of remote unit monitor.
8
Motorola's ASTRO 25 trunked system meets this need by advertising back up control channel
frequencies
9
The APX subscriber uses the P25 enhanced vocoder. The XTS/XTL subscriber product portfolio
uses the P25 baseline vocoder with added background noise reduction capability.
10
Motorola’s Telephone Interconnect solution complies with all the mandatory P25 requirements
however it does not support Landline to Talkgroup which is an optional feature.
Overall Comment – This matrix comments on Motorola ASTRO 25 System Release 7.8 System
Infrastructure Capabilities, this matrix does not comment on Motorola Subscriber Capabilities.
Motorola offers a diverse portfolio of P25 solutions to address a wide variety of customer needs.
Customers should work with Motorola representatives to ensure that their specific requirements are
addressed.
5.5 Subscriber Radios

Motorola has the widest portfolio of user radios in the industry today and offers a
wide range of mobile and portable radio configurations for use on Motorola’s
ASTRO 25 Digital Voice system. Our subscriber portfolio includes radios that meet
the requirements of RFP as well as other models offered by Motorola.
Below are the models that meet the requirements of the RFP:
♦ APX 6000 M3: High Tier Portable
♦ APX 6000 M2: Mid Tier Portable
♦ XTS 2500 M2: Low Tier Portable
♦ APX 7500: High Tier Mobile
♦ APX 6500: Mid Tier Mobile and Control Station
♦ XTL 2500 Control Station
♦ XTL 1500: Low Tier Mobile and Control Station
♦ Minitor V Pagers
5.5.1 End User Radios Proposed

Motorola remains the industry innovator in mission critical two-way
communications. Through this leadership, we are able to offer Floyd County the
widest portfolio of user radios in the industry (Figure 5-25).

RFP# 101216
December 16, 2010

Figure 5-25: Because our portfolio includes a wide range of options within the same
model families, we can deliver the functionality options you require with the low
operational costs provided by shared programming, accessories, support, and training
5.5.2 Features of All Proposed Motorola Radios

All radios that Motorola offers to the public safety market have specific features that
our customers have indicated are critical for first responders and other public safety
field personnel.
Trunking Support
All Motorola high-performance mobile and portable radios are compatible with the
Project 25 Type II standards for analog and digital trunking. They all support
conventional analog and digital operation, as well as trunked digital operation in the
same radio. In addition, they support Project 25 features for interoperability with
systems from both Motorola and other manufacturers. They are ideally suited to
situations where personnel need instant interoperability on different systems.
Backwards and Forwards Compatibility

Motorola’s current P25 radio portfolio is designed with both backwards and forwards
compatibility. The radios in our portfolio have been designed to operate on analog
conventional, Project 25 conventional, and Project 25 trunking systems, and can also
operate on systems using Motorola Project 16 analog trunking, SMARTNET, and
SmartZone technology.
Easy Radio Programming

All proposed Motorola radios can be easily programmed using Customer
Programming Software (CPS). This easy to use, Windows-based customer
programming software enables programmers to use the drag and drop, clone wizard,
and programming over IP capabilities. This increases your users’ speed and
efficiency in updating their radio’s programming. As your system changes or expands
and your field users’ needs change, you can easily add new software or future
enhancements.

RFP# 101216
December 16, 2010

Superior Audio Quality
Motorola radios incorporate Noise Reduction Software (NRS) to improve voice
intelligibility by eliminating background noise picked up by the radio microphone in
the transmitted signal, and accurately filter the caller’s voice from background noise
(Figure 5-26). This improves user safety by ensuring that transmissions are not only
heard, but clearly understood.
Without Noise Reduction With Noise Reduction
Figure 5-26: The APX significantly improves voice intelligibility using Motorola’s Noise
Reduction Software
Rugged, Robust Design—Standard with Every Radio

Motorola public safety radios meet applicable Military Specifications 810, C, D, E,
and F. Using MacroBlend housing material, they are designed to survive severe
shock and vibration, and exposure to damaging environments such as salt fog, UV
radiation, dust, and electrostatic discharge.
Motorola radios are tested and exposed to extreme conditions to simulate years of
abuse. Typical environmental tests performed on our radios include temperature
shock, temperature cycling, drop, display impact, vibration, blowing rain, dust, salt
fog, UV exposure and Electro-Static discharge (ESD). We also perform functional
and parametric testing to verify that the radios still work after they are exposed to the
environment. Our testing standards used include:
♦ Military Specification 810 C, D, E, F
♦ European “IP” specs
♦ Motorola Internal 12M spec
Motorola’s Internal 12M specifications are more stringent than industry-standard

testing. For example, Military Specifications for a drop test calls for the unit to be
dropped onto a plywood surface. Motorola’s drop tests utilize a steel landing surface,
which increases the severity of the test. It is Motorola procedure that each test unit
should be subjected to every environmental test, rather than using a different unit for
each test. This ensures that our radios perform to specification regardless of the
amount and type of abuse they receive.
POP25 Over the Air Programming (OTAP) (optional, not included)

All proposed radios are capable of providing Floyd with the functional and cost
benefits of Motorola’s Programming-Over Project 25 (POP25) over-the-air
programming (OTAP) technology. POP25 functionality reduces the time, effort, and
costs needed to update radio functionality by allowing radios’ configuration to be

RFP# 101216
December 16, 2010

accessed and updated over the air. Your personnel will be able to continue working in
the field while their radios are updated to the most current configuration.
5.5.3 APX Portable and Mobile Radios
Figure 5-27: The APX line of radios is the first P25 multi-band radios in the public safety market.
Motorola’s APX P25 multi-band radios deliver exceptional performance by

combining advanced voice and data technology driven by the challenges of mission
critical users. They enable Floyd County to achieve instant multi-agency
interoperability for mission critical first responders, in a form factor that has been
designed specifically for Public Safety and Law Enforcement agencies.
The APX radio interfaces with our ASTRO 25 infrastructure technology to provide
seamless, high-quality communications that meet and exceed P25 standards for all of
Floyd’s mission critical communications needs.
5.5.3.1 Features of All APX Radios

Motorola’s IP-enabled APX radios offer a full array of sophisticated features and
progressive technology, and are the most sophisticated interoperable and rugged
radios that Motorola manufactures for public safety professionals.
APX mobile and portable radios are capable of offer the following features.
Interoperability in 700/800 MHz and VHF or UHF Frequencies

The APX multi-band radio can operate on both 700/800 MHz and VHF or UHF
frequencies to enable instant interoperable communications for improved

RFP# 101216
December 16, 2010

coordination, response, and first responder safety. This meets Floyd’s need for
seamless multi-agency collaboration.
In mission critical situations, agencies from different jurisdictions often operate on
different frequency bands – requiring personnel to carry two radios in order to
communicate with one another. With the APX portable and mobile radios, Floyd’s
agencies can purchase one radio for instant communication over multiple frequency
bands. This eliminates the need for field users to carry multiple radios, and reduces
the amount of equipment that must be maintained and installed.
Project 25 Phase 1 FDMA and Phase 2 TDMA Operation

The proposed APX mobile and portable radios can operate in both Project 25 Phase 1
FDMA and Project 25 Phase 2 TDMA trunking modes. Floyd County can purchase it
with FDMA trunking operation for the initial deployment, and upgrade in the future
with software for TDMA trunking operation. Once the Project 25 Phase 2 standards
have been finalized, Motorola will submit the APX series radio for approval through
the official standards approval process—and then make a software upgrade available
to Floyd for full compliance with Project 25 Phase 2 TDMA standards.
Using Motorola’s unique Dynamic Dual Mode (DDM) capability, APX radios can
dynamically switch between FDMA and TDMA without the user having to change
channels. This provides interoperability on demand with existing and future
networks.
Integrated GPS Capability (optional, not included)

The APX portable and mobile radios can offer Floyd the advantage of being able to
locate and track each field unit from a central location. The integrated GPS receiver
in the APX transmits the outdoor location of an individual or vehicle to map-based
location software.
Figure 5-28: Enhanced user interface provides intelligent lighting to significantly improve
legibility (APX 7000 example)

RFP# 101216
December 16, 2010

Intelligent Lighting
The APX portables offer a high resolution display that uses color and lighting to
indicate radio mode, potential emergencies, or specific events. Intelligent lighting
enables users to see critical information at a glance, regardless of the amount of
ambient lighting.
Radio Profiles
Radio profiles enable users to customize their radios’ interface to their environments
and activities, including the radio’s default audio level, lighting and tone alerts. For
example, a user in bright sunlight or high-noise environments can increase the
lighting or audio level—or if the user is conducting ongoing, covert surveillance, they
can create a profile that provides lower lighting with subdued alert tones and audio.
Text Messaging (optional, not included)

Text messaging offers freeform and canned messaging between field users and
dispatch operators. This enables selected field users to not only communicate with
one another and with dispatch operators via voice transmission, but also through
efficient and discreet texts.
Security
The APX radios meet Federal Information Processing Standard Publication (FIPS)
encryption standards FIPS 140-3 and FIPS 197. The radios support multi-algorithm
Project 25 and legacy encryption capabilities, including AES / DES / DES-XL / DES-
OFB / DVP-XL for increased interoperability with other systems. AES has been
included in accordance with the RFP.
They are also capable of Motorola’s proprietary Advanced Digital Privacy (ADP),
which provides a low cost digital encryption option. ADP is a 40-bit encryption key
security, is based on the RC4 algorithm, providing secure communications with no
degradation in voice quality or coverage.
To increase the effectiveness of this encryption, Over the Air Rekeying is available to
update encryption keys while radios and their users can stay in the field. This
infrastructure and tactical over-the-air rekeying can offer the Parish the benefit of
real-time, ongoing security.
Expandable for Future Applications

One of the prime limiters of radio expansion is memory: future applications are
expected to use significantly more memory than current applications. To
accommodate this future need, each APX radio is equipped with 64 MB of industrial
grade internal memory.

RFP# 101216
December 16, 2010

Advanced Audio Quality
APX radios represent a significant advancement in digital audio quality. Using an
enhanced vocoder that enables both Phase 1 enhanced full rate and Phase 2 enhanced
half rate modes of operation, the APX includes noise reduction software and
advanced audio adjustment technology to ensure that your personnel can both hear
and be heard.
5.5.3.2 Features of the APX 6000 Portable Radio
Figure 5-29: The APX Portable is the most advanced portable in our portfolio.

RFP# 101216
December 16, 2010

The APX 6000 P25 Portable Radio delivers exceptional performance combining
advanced voice and data technology driven by the challenges of mission critical
users. Motorola’s 4th generation P25 subscriber communicates with current and
future networks (FDMA and TDMA), and has integrated GPS (optional).
Designed specifically for first responders, the dual-sided mission critical design has
both an audio and data side providing optimal functionality and loud and clear audio
in a compact rugged form factor. Its top-of-the-line audio, user interface, and
ruggedization features will enable Floyd’s personnel to focus on their mission, not
communication.
Built for Ease of Use

The APX portable radio is 15 percent smaller than our previous portable models,
making it easier to carry. Its unique T-Grip form factor provides secure and easy
handling. The radio’s ergonomics are optimized for both gloved and bare hand
operation, preventing the accidental actuation of buttons and switches. The radio’s
software enables users to easily navigate to the functions that they need in the fastest
and easiest way possible; for example, it consolidates all call lists underneath one
unified list, providing quick and easy access to all information associated with
contacts.
Superior Audio Provides Reliable Communications in the Worst

Environments
The APX portable radio equips first responders with the loudest, clearest audio of any
Motorola portable on the market – 50% louder than the Motorola XTS 5000. Unlike
most other radios, the APX has dual speakers that emit extremely loud, bi-directional
audio. These speakers accurately reproduce speech dynamics for superior
intelligibility.
Uncompromising Durability
APX portable radios are hardened to the Internal Protection (IP) 67 standard. This
means that they are completely protected against the ingress of dust and grit, and that
they have complete protection against water. In fact, the APX portable can be
immersed in two meters of water for up to two hours with no harmful effects. This
means that the Parish’s first responders can use the radios without losing
communications even in extreme environments.
Advanced Emergency Functionality

Numerous advanced emergency call/alert features are standard in the APX. These
features keep your personnel safe and communicating, even in dire circumstances:
♦ When an emergency call is initiated in digital mode, other users in a talkgroup
will hear an alert and see the alert ID in their display.

RFP# 101216
December 16, 2010

♦ “All Emergency Keep Alive” ensures that your emergency call is not dropped
even if the radio power switch is turned OFF
♦ “Emergency with Voice to Follow” will allow you to communicate without
having to press the PTT button.
♦ An Emergency Beacon provides a tone when the radio is in emergency mode,
enabling the radio to be found by emergency personnel, even if the user is
incapacitated.
The APX Customer Programming Software includes all of the standard features of
Motorola public safety radio CPS, such as drag and drop, cloning, and programming
over IP capabilities. In addition, the APX CPS provides extended functionality, so
that it is even easier for the Parish’s users to update their radio’s programming. The
APX CPS enables users to see only the codeplug fields they are interested in,
provides Undo/Redo functionality, and improved help functionality that stays in
synch with the user’s selections.
Ergonomic and Functional Benefits of the APX

The APX 6000 provides specific ergonomic and functional features and benefits to
Floyd’s First Responders. Please see Table 5-19 for descriptions of these features and
benefits.

RFP# 101216
December 16, 2010

Table 5-19: The APX 6000 M3
Channel Capacity:
-870 standard
Universal Push-to-Talk
T-Grip
Dual Battery Latch
Orange emergency button
16 position rotary knob
2 position concentric switch
3 position toggle switch
3 programmable side buttons
Transmit LED indicator
Backlit Keypad:
-Home and Data buttons
-3 soft keys
-4 direction navigation key
-4 x 3 keypad
Full Bitmap Display:

-2 lines of icons
-4 lines x 14 characters of text
-Status icons
Models Available for the APX

There are three APX 6000 models: the Top Display model (Model 1), the Dual
Display Model (Model 2), and the Dual Display model with full keypad (Model 3) as
shown in Table 5-20. Each model is designed to provide users with the most
information at a glance. The Top Display Model features a monochrome display at
the top of the radio, with two rows: one for alphanumeric characters, one for icons;
up to 96 channels; three programmable side buttons; and a large angled volume
on/off knob and large channel selector knob for easy gloved operation. The Dual
Display Model possesses all of the features of the Top Display model, and adds a
four-row color front display, with two rows for alphanumeric characters and 2 rows
for icons; up to 870 channels. The Dual Display with keypad additionally offers the
full DTMF keypad.

RFP# 101216
December 16, 2010

Table 5-20: The APX 6000 comes in three models
5.5.3.3 Features of the APX 7500 Mobile Radio

With the APX 7500, Floyd County can purchase one radio for instant multi-band
communication, reducing the expense of maintaining, installing, and operating
multiple mobile radios. The APX 7500 offers Floyd all of the communications
features and benefits of our APX line of radios in an easy to install design.
Figure 5-30: The APX has hard gold contacts molded into plastic to eliminate loose wires and
parts

RFP# 101216
December 16, 2010

Reliable Construction
The APX 7500 mobile platform dramatically improves reliability by reducing the
number of discreet parts and connectors. Side connectors with hard gold contacts
molded into plastic eliminate loose wires and parts, and radial silicone seals protect
the internal components. The radio housing is ultrasonically welded to distribute
impacts over the entire area of the radio and additional adhesive layers and gaskets
prevent water intrusion.
Easy Vehicular Installation and Serviceability

There are two models of the APX 7500: the APX 7500 Mid Power and APX 7500
High Power. The Mid Power version is designed to maintain the same mounting
footprint as the XTL mobile radio. This makes them easy to install and allows reuse
of mounting holes and cables. The High Power version’s trunion was completely
redesigned to include installation guides and rails, better engagement into the tray,
and enhanced handle grip. This enables the radio to be removed and installed easily
and quickly, without removing the cables.
All APX 7500 mobile radios are equipped with 12 character RFID tags, which
provide a fast, accurate way of obtaining valuable asset tracking information without
having to uninstall the radio.
Multiple Control Heads

Each APX 7500 mobile radio can be controlled by multiple control heads, with four
different wired locations. There are two control heads available: the O3 and the O5
(Table 5-21): the O3 is available in dash mount, remote mount, and motorcycle
configurations, and is therefore flexible for many different applications in the
Parish’s fleet. The O5 is available in dash mount configuration only, and has a screen
and keypad for detailed data inputs.

RFP# 101216
December 16, 2010

Table 5-21: APX 7500 Control Heads
O5 Control Head O3 Control Head

Available in dash mount, remote mount, and Available in dash mount configuration
motorcycle configurations
4-line/14 character/1 icon customizable, tri-color 4-line/14 character/2 icons character alphanumeric
LCD display. display.
Can be ordered with a 3 x 6 keypad microphone Integrated 3 x 6 keypad with up to 24
accessory with 3 programmable soft keys. programmable soft keys.
5 programmable soft key buttons and, 5 scroll- Cellular style user interface and color display.
through menus with up to 24 programmable soft
keys.
Multiple control head configuration to fully control a Easy Access Emergency Button.
single radio with up to 4 different wired locations.
Motorcycle configuration also available. Meets Military Specs 810 (C, D, E, & F).
Recessed Orange Emergency Button.
Meets Military Specs 810 (C, D, E, & F).
5.5.3.4 APX 6500 Mobile Radios

The APX™ 6500 is the Mid–tier mobile offering that provides Floyd with an
affordable radio option that meets the requirements while providing many of the
high-tier features of the APX™ 7500.
The APX 6500 is capable of seamlessly scanning multiple protocols and technologies
(FDMA/TDMA). The following features are available with the Mid-Tier APX 6500
subscribers.
System Compatibility & Supported Operation Modes

The mobiles support the following systems, operation modes and capabilities:

RFP# 101216
December 16, 2010

♦ Clear or encrypted APCO Project 16
♦ APCO Project 25 Phase 1 and Phase 2 Upgradeable
♦ 9600 and 3600 baud Control Channel capable
♦ 12.5/20/25 kHz bandwidth receiver – analog capable
♦ 12.5 kHz bandwidth receiver – digital capable
♦ 6.25e TDMA capable
Enhanced Encryption Capabilities

The APX™ 6500 can support Motorola’s software based and FIPS approved UCM
based Encryption Algorithms.
♦ ADP/AES/DES/DES-XL/DES-OFB/DVP-XL
♦ Single Algorithm/Multi-Key Support
♦ Over the Air Encryption Key Management (OTAR) capable/optional
♦ Supports a minimum of 48 Encryption Keys/Radio
♦ FIPS Approved Encryption Module Design
Data Capabilities
The APX™ 6500 also supports multiple IV&D Data applications.
♦ Over- the-Air Programming (POP25) available/optional
♦ Integrated GPS for personnel location available/optional
♦ Text Messaging available/optional
5.5.4 XTS/XTL Portable and Mobile Radios
Figure 5-31: The XTS 2500 (M1.5 Shown) and XTL 1500 are a budget-conscious alternative for
personnel from public works and utilities.
The XTS2500/XTL 1500 are Motorola’s economically priced public safety portable
and mobile radios. Motorola provides this product to the St. Tammany Parish as a
budget-conscious alternative to provide reliable communications to the Parish’s non-
mission critical users.

RFP# 101216
December 16, 2010

5.5.4.1 Features of XTS/XTL Radios
The XTS /XTL portable and mobile radios support Project 25 Phase 1 operation for
interoperability with Project 25 systems, both from Motorola and from other
manufacturers. They assure seamless, high quality communication in a robust design
that stands up to the most demanding environments. The XTS/XTL radios work with
ASTRO® analog or digital trunking with mutual aid or ASTRO 25 digital trunking
with mutual aid systems, and are available in 700 MHz, 800 MHz, VHF, UHF R1
and UHF R2 bands.
5.5.4.2 Features of the XTS 2500 Portable Radio
Figure 5-32: The XTS 2500 portable radio is the cost-effective choice
When trying to restore service or respond to an emergency situation reliable

communication is imperative. Motorola's XTS 2500 digital portable radio helps
mobile workers to communicate, coordinate and interoperate together as one.
Advanced Emergency Functionality

Numerous advanced emergency call/alert features are standard in the XTS 2500.
These features keep your personnel safe and communicating, even in the most dire of
circumstances:
♦ When an emergency call is initiated in digital mode, other users in a talkgroup
will hear an alert and see the alert ID in their display
♦ “All Emergency Keep Alive” ensures that your emergency call is not dropped
even if the radio power switch is turned OFF
♦ “Emergency with Voice to Follow” will allow you to communicate without
having to press the PTT button.

RFP# 101216
December 16, 2010

Built-In Durability and Optional Ruggedization
XTS 2500 radios are hardened to the Internal Protection (IP) 67 standard. This means
that they are completely protected against the ingress of dust and grit, and that they
have complete protection against water. In fact, the XTS 2500 can be immersed in a
meter of water for up to 30 minutes without fear of losing communications even in
extreme environments. This means that Floyd’s first responders can use the radios
without fear of losing communications even in extreme environments.
For personnel needing more protection than the standard XTS 2500 offers, the radio
can be ruggedized. The ruggedized version (XTS 2500R) can be immersed in water
for up to two hours and has been tested in temperatures in excess of 27°C.
Ergonomic and Functional Benefits of the XTS 2500

The XTS 2500 provides specific ergonomic and functional features as shown in the
diagram below.
Table 5-22: Benefits of XTS 2500
1 16 – position easily selectable rotary knob
2 Power On / Off volume control
3 Ergonomically recessed PTT
4 Three programmable side buttons for quick

access to pre-programmed functions E. Home
button
5 Indentions for grip assistance
6 Three software programmable menu buttons
7 Six line twelve character full bitmap high

resolution display. Two lines of icons including:
RSSI, battery gauge, user time clock
8 Top mounted speaker so not to muffle the audio
integrity of the radio in holster
9 Emergency top button - easy to locate by

following antenna

RFP# 101216
December 16, 2010

Models Available for the XTS 2500
There are three models of the XTS 2500, ranging from no display/keypad to a full
bitmap display and full keypad with navigational keys.
Table 5-23: Models Available for the XTS 2500
Model 1 Model 1.5 Model 2 Model 3

The XTS 2500 Model 1 The XTS 2500 Model 1.5 The XTS 2500 Model 2 The XTS 2500 Model 3
has the following has the same features has the same features has the same features
features as the Model 1, plus the as Models 1 and 2, plus as Models 1, 1.5, and 2,
following features the following features plus the following
features
48 channels 96 channels, display 870 channels, display and 870 channels, display and
navigation buttons full keypad
Available in the 700/800 Up to 96 talkgroups or Backlit Keypad (3 soft Backlit Keypad (3 soft
MHz, VHF, UHF R1 and channels keys and 3 navigation keys, 3 navigation keys,
R2 bands keys) and 4 x 3 alphanumeric
keypad)
Convenience features Bitmap Display (2 lines of Bitmap Display (2 lines of
including Time/Date and icons and 2 lines of text icons and 4 lines of text
Digital Caller ID with 12 characters per with 12 characters per
line) line)
Noise Reduction Software Status icons including Programmable soft keys
and Audio Gain Control battery and received for easy access to radio
signal strength indicator menu
Enhanced encryption 16-position top mounted Up to 512 talkgroups or
capability (Optional) rotary knob channels
Supports USB and RS- Programmable orange Dial from pre-stored lists
232 communications emergency button
Meets Applicable Mil 3-position concentric
Specs 810C, D, E, and F switch
Programmable monitor
button
2 programmable side
buttons
Transmit LED indicator

RFP# 101216
December 16, 2010

5.5.4.3 Features of the XTL 1500 Mobile Radio
Figure 5-33: The XTL 1500 offers the Parish’s agencies an affordable P25 solution
For individuals who do not need all the full featured robustness of our high and mid
tier radios, Motorola is pleased to offer our XTL 1500 mobile radio. The XTL 1500 is
designed to meet the public service communication needs of the Parish’s personnel.
The XTL 2500 acts as an affordable migration solution and is a powerful choice for
P25 interoperability. With its simple user interface, the XTL 1500 was designed to be
user friendly. This durable Project 25 compliant mobile assures radio users crisp,
continuous and high quality communication. It supports encryption, is data capable,
and available in mid and high power models. The XTL 2500 mobile radio is capable
of operating in analog, digital, trunked, and conventional modes.
XTL 1500 Key Features

All XTL 1500 mobile radios are available with the following hardware features:
♦ 10 Foot Negative Ground Power Cable (3 meters) for Dash Mount
♦ Ignition Sense Cable
♦ Palm Microphone
♦ Internal Speaker (Standard)
♦ Mounting Hardware
♦ FLASHport, which allows for feature and system upgrades.
♦ 48 Channels/modes (Standard)
♦ Optional Software Enhancement provides 255 channels/modes
♦ Operation mode (ASTRO Digital and Analog) 9600 or 3600 Baud capable
♦ Project 25 capability on Conventional and Trunking systems Type II Trunking
Only
♦ Project 25 compliance interoperable voice signaling features
♦ Bandwidth Receiver
♦ 12.5/25/30 kHz (analog) – 136-174 MHz
♦ 12.5/25 kHz (analog) – 380-470 MHz and 450-520 MHz

RFP# 101216
December 16, 2010

♦ 12.5/20/25 kHz (analog) – 764-870 MHz
♦ 12.5 kHz bandwidth receiver (digital)
♦ 4 Programmable buttons
♦ 14 digit character display
♦ Tri-color Backlit LCD display
♦ Emergency button
♦ Dash mount
♦ Meets Military Specs 810 (C,D, E and F)
♦ Built in FLASHport™ support
♦ Optional Keypad microphone
♦ Internal Speaker
♦ Frequency Band: 764-870 MHz
♦ talk group or channel capacity
♦ 10-35 Watt variable power
♦ 5 programmable buttons with 14 character tri-color backlit LCD display
♦ P25 compliant interoperable voice signaling
♦ Multiple modes of operation (ASTRO digital clear and encrypted, and analog)
♦ Bandwidth analog receiver: 12.5 kHz, 20 kHz, 25 kHz
♦ Bandwidth digital receiver: 12.5 kHz
♦ Integrated voice and data capable
♦ Meets Mil Specs 810 (C, D, E and F)
♦ Dash and Remote Mount configurations
♦ Siren/PA and/or Dual Control Head operation (optional)
♦ Encryption capability (optional)
5.5.5 Control Stations
Figure 5-34: APX 6500 Control Station
Motorola’s APX 6500 and XTL 2500/1500 based Control Stations provide the
features of the APX 6500 and XTL 2500/1500 mobiles in a housing with built in
power supply. They are ideal for local law enforcement, utility, and transportation
users who need a low cost desktop-based control station or wireless dispatch solution.

RFP# 101216
December 16, 2010

These control stations can also be used as emergency backup stations, a low-cost
dispatch center for local agencies, and as a fire station alerting system. They are
offered in both local and digital remote control configurations.
5.5.6 Minitor V Pagers

The Motorola MINITOR V™ Pager is a new generation Voice Pager for a more
secure community. It's ideal for fire departments as well as businesses and other
organizations that must react quickly in times of emergency. Motorola has proposed
the single channel, non-stored voice VHF Minitor V with standard charger.
The Minitor V is a major upgrade in pager performance and options:
♦ Wide and narrow-band programmable
♦ Improved paging sensitivity
♦ Expanded alert tones
♦ Tremendous stored voice capacity (optional, not included)
♦ Rugged design and excellent durability
Figure 5-35: Minitor V Pager
5.5.6.1 Features and Functions

♦ Single and Dual Channel models (single channel included)
♦ Wide and Narrow-Band Options: Programmable for both UHF and VHF (VHF
included)
♦ Paging Sensitivity: Helps consistently receive messages, even in fringe or weak
signal areas
♦ Speaker/Earphone Jack.
♦ 12 Alert Tones Per channel: Supports 8 two-tone pairs and 4 long-tone alerts
♦ Programmable Music Alerts: Supports 10 different musical alerts
♦ Meets MIL-STD 810E, Procedures 1 for Driving Rain
♦ Tone, Vibrate or Vibrate then Tone Alerting Options
♦ Field Programmable Frequencies and Tones
♦ Certified Intrinsically Safe
♦ Function Mode Announcement (Stored voice option): Announces operating
programmed mode (optional, not included)
♦ Expanded Stored Voice Capacity: Records up to 8 minutes of voice messages for
playback (optional, not included)
♦ Silent Scan (Dual frequency model): Scans both channels silently, alerts on either
channel (optional, not included)
♦ Priority Scan (Dual frequency model). Plays all traffic on Channel 2, alerts on
Channel 1 (optional, not included)

RFP# 101216
December 16, 2010

5.5.7 Customer Programming Software (CPS)
The customer programming software is used to configure the subscriber radios. It
runs on a PC and is used to create or modify a radio’s operating parameters.
Required Components
♦ PC to run the CPS software.
♦ Programming cable to connect PC with the subscriber unit.
Improved Features of CPS Tool

♦ The CPS tool starts common tasks quickly and it is customizable with color
themes and screen layouts. The log file allows the user to keep track of changes
and simple log feature helps to track current changes.
♦ Takes less time to configure, set up and maintain the subscriber radios.
♦ Can easily diagnose and troubleshoot the problems.
♦ Can share information between radios.
♦ User can easily compare 2 different code plugs and generate reports.
♦ CPS shows only the fields relevant to the user by graying out the fields which are
not relevant.
♦ The users are notified in case of error by keeping it in the error log.
Figure 5-36: APX CPS.

RFP# 101216
December 16, 2010


RFP# 101216
December 16, 2010

Regional Customer Reference
Customer Name: Hamilton County, Ohio

Hamilton County Communications Center
2377 Civic Center Drive
Cincinnati, OH 45231
Synopsis
This existing system is comprised of a single zone with two simulcast
cells (one for the County and one for City), distributed Centracom Gold
Elite Embassy subsystem, 37 Elite operator positions, and MOSCAD
monitoring. The CADI data stream and Elite API are used by Premier
CAD systems (one for the County and one for City). PDMC’s en-
hanced service residing on CDM/ADM server creates a second copy
of CADI data stream (outbound only) for City of Cincinnati’s CAD sys-
tem. The ATIA data stream is used for NICE digital recording. IV&D
is used by Premier MDC for Fire departments data application within
the County and City.

• 15 Sites
• Circuit Based Simulcast
• Release A6.8 Project 25
• CAD Vendor: PCAD
• Dispatch Integration: Voice, PCAD, IV&D and PMDC
Completion Date: 2002
Customer Contact:
Greg Wenz
Operations Director
Phone: 513-595-8445
Fax: 513-595-8457 B
m
Greg.Wenz@hamilton-co.org
5.1 Diagrams
System diagrams are provided on the following pages.

RFP# 101216
December 16, 2010
Diagrams 5.1-1

December 16, 2010
5.1-2 Diagrams
8 7 6 5 4 3 2 1
Primary/Back-up Site Router Links
J J
T1 Connections
Ethernet Links to either of the following:

7 - site simulcast cell / 1 ASR Site
OR
HP 2610-24 HP 2610-24 8 - site simulcast cell
AND
Gig-T Ports
Gig-T Ports
SFP Ports
SFP Ports
Fan Out Switch Fan Out Switch EOC Back-up Dispatch
Packet Data
Gateway ISSI.1 Gateway to TVRS/NWGA
(IV & D)
DL360 Server
I I
S6000 Router S6000 Router
Core Router #1 Core Router #2
H Zone Level
H
Ethernet
HP 2610-24 HP 2610-24
Gig-T Ports
Gig-T Ports
Ethernet Links to Co-located MCC7500
SFP Ports
SFP Ports
ZC1, ATR, & ZDS Server Core LAN Switch Core LAN Switch Ethernet LAN Switches
G G
ST6000 Router
Ethernet
ZC2 & NM Server
Gateway Router #1
ST6000 Router
F GPS Network Timing Source
F
MOSCAD Gateway Router #2
Ethernet
Graphics Master (1)
Customer Enterprise Network (CEN)
DL360 Server
ST6000 Router
Presence Notifier Server HP 2610-24

SDM3000 GGSN Router
E E
Gig-T Ports
SFP Ports
CEN Switch
MOSCAD SNT
ST6000 Router
CEN Border Router

NM Workstation
D T1 Connections D
DL360 Server
Common Platform /
Domain Controller #1
ST6000 Router
C C
Out of Band Management – 48 ports ST6000 PN Router
(Terminal Seraver)
S2500 Router HP 2610-24
NETWORKS & ENTERPRISE
Gig-T Ports
R
LAN WAN SERIAL SuperStac k II SUPER

(CSU/DSU) NETBuilder STACK
L1 L2 B1 B2
L1 L2 A B
100m b Line A B
Link Lin k Ru n Au x
Ac t Cons o l e
Link
Systems Engineering
Co n n e c t Ac t i v e Res et Load
SFP Ports
Ac ti v e Sta tu s
Line Fa u l t Te s t
Fa u l t Fa u l t Fwd Po we r
Erro r /Fa u l t
SYSTEM
ZC1, ZC2, LAN routers, LAN Network Monitoring Router DMZ Switch
Switches, etc... Lawrenceville, GA 30043
B (Connections to devices not shown)
Juniper SSG140
PROJECT:
Floyd County E911 Center, Rome, Georgia B
Firewall
ASTRO 25 800 MHz Radio System
TITLE
C
ASTRO 25 Zone Core Block Diagram
Link to System Support B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
Center
A
Gary Brady A
A O 12/10/10 GJB Proposal Final Version
PROGRAM DRAWN
Gary Brady
CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
11/05/10
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-1
8 7 6 5 4 3 2 1
J J
7.5' Rack 7.5' Rack
16 T1 Protector
Backhaul LAN Switch #2

I Backhaul LAN Switch #1
GPS Network Timing
I
DMZ Switch
LAN Switch #2
LAN Switch #1
Border Router
PN Router
H IDSS
Firewall
H
Terminal Server
Gateway Router #2
Gateway Router #1
Core Rtr 2
Core Rtr 1
G G
Panel monitor & KVM Panel monitor & KVM
Slide Out Slide Out
ZC #2
NM Printer NM/ZC #1
F ISSI LAN Switch
F
Common Platform Hrdwr
ISSI Firewall
PDG
ISSI Gateway
GPRS Gateway Service Router
Ethernet
AVL AVL Network ISSI
MUPS Presence Timing Application
Server Notifier Server Server
E E
D D
Rack 1 Rack 2
Supervisor Supervisor
MOSCAD NM Workstation
NFM Workstation
C C
Networks & Enterprise

Systems Engineering
Lawrenceville, GA 30043
B PROJECT:
Floyd County E911 Center B
TITLE
C
Zone Core Site Racking Layout
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A
½” = 1' A
A O 12/10/10 GJB ORIGINAL RELEASE – with ISSI and NTP
PROGRAM DRAWN CHECKED SHEET REV
O A
8 7 6
Motorola Confidential, Proprietary and Trade Secret
5 4 3 2 5.1-2
1
8 7 6 5 4 3 2 1
7.5' Rack 7.5' Rack
J (2) Outdoor 800MHz Antennas

Co-Located MCC7500 Site J
(6) Desk-
I CS Combiner 1 CS Combiner 2
mounted Control I
Stations
Logging
Control Station 5 Co-located Master Site
Ethernet Links to Core LAN
Logging
Control Station 4
H Logging Logging
H
Control Station 3 Control Station 11
Logging Logging
Control Station 2 Control Station 10
Backup EOC Dispatch Site Logging Logging HP 2610-24 HP 2610-24
G Control Station 1 Control Station 9 G

Ethernet link to Floyd Logging
911 via Microwave Control Station 8
Logging
Control Station 7
F (1) Outdoor
Logging
Control Station 6
F
GenWatch Detrunk Logger
800MHz Antenna (3) MCC7500 Ops (3) MCC7500 Ops
GGM8000 Gateway
LAN WAN
(CSU/DSU)
S ERIAL SuperStac k II
NETBui l der
SUPER
STACK
R
(3) Voice Processor Modules (3) Voice Processor Modules
L1 L2
(VPMs)
B1 B2
L1 L2 A B
(VPMs)
10 0m b Li ne A B
Li n k Li n k Ru n
Ac t Co ns o l e Au x
Li nk Res et
Con ne c t Ac ti v e Lo ad
Ac ti v e S ta t u s
L i ne F au l t Te s t F wd P o we r
Fa ul t F au l t
Erro r / Fa u l t
SYSTEM
E E
CS Combiner 1
R
LAN WA N SERIA L SuperStack II SUPER SuperStack II SUPER

R
SuperStack II SUPER
R
LAN WA N SERIA L LAN WA N SERIA L

(CSU/DSU) NETBuil der STACK NETBuil der NETBuil der
L1 L2 B1 B2 L1 L2
(CSU/DSU) STACK L1 L2
(CSU/DSU) STACK
L1 L2 B1 B2 B1 B2
A B L1 L2 A B L1 L2 A B
1 00 m b L i ne A B 1 00 m b L i ne 1 00 m b L i ne
L i nk L in k Ru n L i nk A B L i nk A B
Ac t Cons ol e Aux Ac t L in k Ru n Aux L in k Ru n Aux
L i nk L i nk Cons ol e L i nk
Ac t Co ns ol e
Co nn ec t Ac t iv e Res et Lo ad Res et Res et
Status Co nn ec t Ac t iv e Lo ad Co nn ec t Ac t iv e Lo ad
Ac t i v e Ac t i v e Status Ac t i v e Status
L in e Fa u l t Te s t F wd P o we r L in e Fa u l t Te s t L in e Fa u l t Te s t
F au l t F aul t F au l t F aul t F wd P o we r F au l t F aul t F wd P o we r
Error / Fa u l t Error Error
/ Fa u l t / Fa u l t
SYSTEM SYSTEM SYSTEM
HP 2610-24
CCGW #1 (4 Conv Channels) CCGW #2 (4 Conv Channels) CCGW #3 (4 Conv Channels)
1. Fire Paging / Alerting (VHF) 1. Fire Station Alerting (B/U) 1. Cutover Conventional
2. FUTURE 2. FUTURE 2. Cutover Conventional
D 3.
4.
EMS Station Alerting (800)
FUTURE
3.
4.
MOTOBRIDGE RGU
FUTURE
3.
4.
Cutover Conventional
Cutover Conventional
D
(5) Desk-
mounted Control
Stations
(5) MCC7500 Ops

C MCC7500 Aux I/O C
MCC7500 Aux I/O
(5) Voice Processor Modules
(VPMs)
L1
LAN
L2
L1 L2
1 00 m b
L i nk
WA N
(CSU/DSU)
L i ne
Ac t
B1 B2
L i nk A
SERIA L
B
A B
L in k
Res et
SuperStack II
NETBuil der
Co ns ol e
Ru n
SUPER
STACK
Aux
R
L1
LAN
L2
L1 L2
10 0m b
WAN
(CSU/DSU)
Li ne
Ac t
B1 B2
Li n k A
S ERIAL
B
A B
Li n k
SuperStac k II
NETBui l der
Co ns o l e Ru n
SUPER
STACK
Au x
R
Systems Engineering
Co nn ec t Ac t iv e Lo ad Li nk
Ac t i v e Status Con ne c t Ac ti v e Res et Lo ad
L in e Te s t F wd Ac ti v e S ta t u s
F aul t Fa u l t P o we r
F au l t Error L i ne F au l t Te s t
/ Fa u l t Fa ul t F au l t F wd P o we r
SYSTEM Erro r / Fa u l t
SYSTEM
CCGW #1 (4 Conv Channels)

B CCGW #2 (4 Conv Channels) PROJECT:
Floyd County, Georgia B
1. FUTURE 1. Fire Paging / Alerting (VHF) ASTRO 25 800 MHz Radio System
2. EMS Station Alerting 2. FUTURE TITLE
3. FUTURE 3. FUTURE C
Main & Back-up Dispatch Centers – Floyd 911 & EOC
4. FUTURE 4. FUTURE
A Gary Brady TBD A
A O 11/17/2010 RLB Proposal Drawing
PROGRAM DRAWN
G. Brady
CHECKED SHEET REV
O A
REV DATE ENGNR DESCRIPTION 11/17/2010
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J 7' 5" Rack J

GGM8000 Gtwy #1
HP2610 Switch #1
CCGW #1
CCGW #2
I SDM3000 Aux I/O

Backup I
CS Combiner 1
H H
7' 5" Rack 7' 5" Rack
HP2610 Switch #1
HP2610 Switch #2
G CCGW #1
CCGW #2
(5) Desk-mount
Control stations
G
CCGW #3
SDM3000 Aux I/O Main
CS Combiner 1 CS Combiner 2
F F
Logging
Control Station 5
Logging
Control Station 4
Logging
E Logging Control Station 11
Rack 1 E
Control Station 3 (5) MCC7500 OPs
Logging (6) Desk-mount
Logging Control Station 10 Control stations
Control Station 2
Logging
Logging Control Station 9
Control Station 1
D Logging
D
Control Station 8
Logging
Control Station 7
Logging
C GenWatch Detrunk Logger
Control Station 6 C
Rack 1 Rack 2 Networks & Enterprise
(6) MCC7500 OPs
Systems Engineering
B PROJECT:
Floyd MCC7500 Console System B
TITLE
C
Main & Backup Rack Layouts
A Gary Brady A
A O 11/19/10 RLB ORIGINAL RELEASE
PROGRAM DRAWN
Gary Brady
CHECKED SHEET REV
O A
REV DATE ENGNR DESCRIPTION 11/19/10
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
Ethernet Microwave RX-A
1+1 Link to Floyd 911
I I
GGM8000 Site Gateway Primary GGM8000 Site Gateway Alt
R
SuperStac k II SUPER
R

LAN WAN SERIAL NETBui lder
NETBui lder STACK L1 L2
(CSU/DSU) STACK
L1 L2 (CSU/DSU) B1 B2
B1 B2 L1 L2 A B
L1 L2 A B 10 0m b Line A B
100 mb Line A B Link Link Ru n Au x
L in k Link Ru n Au x Ac t Cons o le
Link
TO Floyd 911
Ac t Con s ol e Res e t
Link Co n n e c t Ac t i v e Lo ad
Co n n e c t Ac t i v e Re s et Load St a tu s
Ac ti v e
TO Floyd 911
Ac t i v e St a tu s
Line Fa u l t Te s t
Line Fa u lt Te s t Fa u l t Fa u l t F wd Po we r
Fa u l t Fa u l t F wd Po we r Erro r
Erro r /Fa u lt
/F a u l t SYSTEM
SYSTEM
MASTER SITE MASTER SITE (2)HP Procurve 2610

Primary Site Alternate Site
Link Link TTA
H S6000 Prime-Master Site Routers H
Unused until TDMA TTA

RMC TX TX
OUTPUTS
MOSCAD RTU Prime Simulcast 7' Schroff

7' Schroff
7' 6" Rack
RMC ITAC
Site LAN SW Junction Panel Junction Panel
G
G 48 DI (2)HP Procurve 2610 PSEL
B
16 DO Site RMC/LNA “A” Site RMC/LNA “A”
For environmental PSEL PSEL
800MHZ Tx
A TX Filter TX Filter Combiner #2
A
alarms (6 channel)
1 GIG Cable
Tx Combiner Tx Combiner
GTR8000
ITAC4
GTR8000
F ITAC3 VHF TX/RX F
GCP8000 GTR8000
PA5
PA1
PA2
PA3
PA4
PA5
PA1
PA2
PA3
PA4
Simulcast ITAC2
GCP8000 GTR8000
(2) GCM8000 Prime #2 (3) GCM8000
Simulcast ITAC1
S6000 Primary Subsite Access Router Prime #1
Comparators
1&5,3&7,
Comparators
2&8,4&10,6&9
GTR8000
RMC/LNA “B” RMC/LNA “B”
ICALL
GTR8000
EMS ALERTiNG
XCVR4
XCVR5
XCVR1
XCVR2
XCVR3
XCVR1
XCVR2
XCVR3
XCVR4
XCVR5
SCA
SCB
SCA
SCB
E E
[1] 1PPS
S6000 Alternate Subsite Access Router
[2] 1PPS
P P P P P P P P P P MTR2000
TRAK 9100 S S S S S S S S S S VHF Fire Paging
Ethernet Microwave to Remote Sub-sites Frequncy Standard

Serves Prime &
Rack
RF Site [2 or 7] Composite 5MPPS/
Primary & Alt Fanout Switches - HP Procurve 2610 Equipment 1PPS
D Output from Phasing D

Harness and two 6-port
Combiners
Ethernet Microwave to Remote Sub-sites
C C
Systems Engineering
H
G PROJECT:
F Floyd County, GA - ASTRO 25
B E 10 Channel Simulcast Site w/ ITAC and VHF Paging B
TITLE
D
C
SYSTEM DIAGRAM – Prime and Co-Located Remote
Gary J Brady Jr NONE B
A
A O 12/10/2010 G. Brady Mt Alto Prime/Co-located 10 Channel RF Site w/ITAC
PROGRAM DRAWN
G. Brady
CHECKED SHEET
1 of 1
REV
O A
REV DATE ENGNR DESCRIPTION 11/08/2010 PRJ-xxx
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
RX-A
Ethernet Microwave to
I Prime Site I
GGM8000 Site Gateway Primary GGM8000 Site Gateway Alt
R
SuperStac k II SUPER
R

LAN WAN SERIAL NETBui lder
NETBui lder STACK L1 L2
(CSU/DSU) STACK
L1 L2 (CSU/DSU) B1 B2
B1 B2 L1 L2 A B
L1 L2 A B 10 0m b Line A B
100 mb Line A B Link Link Ru n Au x
L in k Link Ru n Au x Ac t Cons o le
Ac t Con s ol e Link
Link Co n n e c t Ac t i v e Res e t Lo ad
Co n n e c t Ac t i v e Re s et Load St a tu s
St a tu s Ac ti v e
Ac t i v e Line Te s t
Line Te s t Fa u l t Fa u l t F wd Po we r
Fa u lt F wd Po we r Fa u l t
Fa u l t Fa u l t Erro r /Fa u lt
Erro r /F a u l t SYSTEM
SYSTEM
(2)HP Procurve 2610
TTA
H H
MOSCAD RTU
RMC TX
7' Schroff
7' Schroff
Junction Panel
G 48 DI
Junction Panel
PSEL
G
B
16 DO Site RMC/LNA “A” Site RMC/LNA “A”
For environmental PSEL PSEL
A TX Filter TX Filter
A
alarms
Tx Combiner Tx Combiner
F F
PA5
PA1
PA2
PA3
PA4
PA5
PA1
PA2
PA3
PA4
RMC/LNA “B”
2 - 5MPPS RMC/LNA “B”
2 - 1PPS
XCVR4
XCVR5
XCVR1
XCVR2
XCVR3
XCVR1
XCVR2
XCVR3
XCVR4
XCVR5
SCA
SCB
SCA
SCB
E E
P P P P P P P P P P
TRAK 9100 S S S S S S S S S S
Frequncy Standard
D Output from Phasing D

Harness and two 6-port
Combiners
C C
Systems Engineering
H
G PROJECT:
B E 10 Channel Simulcast Sub-Site B
TITLE
D
C
SYSTEM DIAGRAM – Simulcast Remote RF
A
A O 12/10/2010 G. Brady Remote RF Sub-site - 10 Channel
PROGRAM DRAWN
G. Brady
CHECKED SHEET
1 of 1
REV
O A
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
45 45
5 5
800MHZ Tx Combiner #2
GGM Site Gateway GGM Site Gateway
I S2500 S2500
(6 channel) I
HP 2610-24
40 40
10 10 Primary RMC
H TX Rflct Power Monitor GTR8000 ITAC4 Microwave H
15 15
35 35
Radio(s) and
GTR8000 ITAC3
Controllers
G Expansion TX Primary TX GTR8000 ITAC2 G
30 30
20
Combiner 20
Combiner
Exterior Wall
GTR8000 ITAC1
F 25
GTR8000 ICALL
25
F
25 25 FUTURE RF FUTURE ESS
GTR8000
EMS ALERTiNG
20 20
Ch 1
E 30 30 Interop
Control Station 1
E
MTR2000
VHF Fire Paging
1
1
0
15 15 Interop
Control Station 2
35 35
D D
Interop
3
Control Station 3
10 10
40 40
Interop
Control Station 4
C C
5 5
45 45
Systems Engineering
B PROJECT:
ESS Odd Chnls ESS Even Chnls ASTRO25 Project
TITLE
C
Mount Alto Prime/RF Site – Rack Layout Row 1
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Mt Alto with CS
O A
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
45 45 45
TRAK - GPS
Master Site Router GCP Controller
I I
40 40 40
Hot Spare S6000
CWR Routers
H H
GCP Controller
35 35 35
DC GCM Ch 1 & 6
Rectifier CWR Panel
G 30
& Battery
30 30
G
HP 2610-24
Distribution GCM Ch 2 & 7
Exterior Wall
System
25 25 25
F FUTURE RF GCM Ch 3 & 8 F

SDM3000
20 20 20
GCM Ch 4 & 9
E E
15 15 15
GCM Ch 5 & 10
D D
10 10 10
C 5 5 5
C

Systems Engineering
B PROJECT:
ASTRO25 Project
TITLE
C
Mount Alto Prime/RF Site – Rack Layout Row 2
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Mt Alto with CS
O A
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
5 5
GGM Site Gateway S2500
I I
HP 2610-24
10 10 Primary RMC
TX Rflct Power Monitor
H H
15 15
G Expansion TX Primary TX G
20
Combiner 20
Combiner
Exterior Wall
F 25 25 F
30 30
E E
1
6
1
0
35 35
D D
3
40 40 8
C C
45 45
Systems Engineering
B PROJECT:
ESS Odd Chnls ESS Even Chnls ASTRO25 Project
TITLE
C
Remote Simulcast RF Site – Rack Layout Row 1
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Final Design w/ CS
O A
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
45 45
TRAK - GPS
SDM3000
I I
40 40
H H
35 35
DC
Rectifier
& Battery Microwave
G 30 30
G
Distribution Radio(s) and
System Controllers
Exterior Wall 25 25
F FUTURE ESS F
20 20
E E
15 15
Interop
Control Station 1
D D
Interop
10 10 Control Station 2
Interop
Control Station 3
(Some sites have more than
C 5 5
2 Control Stations) C

Systems Engineering
B PROJECT:
ASTRO25 Project
TITLE
C
Remote Simulcast RF Site – Rack Layout Row 2
A
A
A O 12/13/2010 G.Brady Changed to match Final Design w/ CS
O A
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
J J
RX-A
Ethernet Microwave to
I Prime Site I
GGM8000 Site Gateway
R

(CSU/DSU) NETBui lder STACK
L1 L2 B1 B2
L1 L2 A B
100 mb Line A B
L in k Link Ru n Au x
Ac t Con s ol e
Link
Co n n e c t Ac t i v e Re s et Load
Ac t i v e St a tu s
Line Fa u lt Te s t
Fa u l t Fa u l t F wd Po we r
Erro r /F a u l t
SYSTEM
(1)HP Procurve 2610
TTA
H H
MOSCAD RTU
RMC TX
7' Schroff
Junction Panel
G 48 DI G
16 DO Site RMC/LNA “A”
For environmental PSEL

A TX Filter
alarms
Tx Combiner
F F
PA5
PA1
PA2
PA3
PA4
RMC/LNA “B”
XCVR4
XCVR5
XCVR1
XCVR2
XCVR3
SCA
SCB
E E
P P P P P
S S S S S
D D
C C
Systems Engineering
H
G PROJECT:
B E 5 Channel ASTRO25 Site Repeater B
TITLE
D
C
SYSTEM DIAGRAM – RF Site Repeater
A
A O 12/10/2010 G. Brady RF ASTRO 25 Site Repeater Option - 5 Channel
PROGRAM DRAWN
G. Brady
CHECKED SHEET
1 of 1
REV
O A
8 7 6 5 4 3 2 1
Motorola Confidential and Restricted 5.1-11
This page intentionally left blank.


8 7 6 5 4 3 2 1
J J
45
5
I I
Microwave
40 SDM3000
Radio(s) and 10
Controllers
TX Rflct Power Monitor
H H
35
15
G 30 Expansion TX G
Interop
Control Station 1
20
Combiner
Exterior Wall
25 Interop
Control Station 2
F 25 F
Interop
Control Station 3
20
30
E E
5
15
35
DC
D Rectifier 2 D
4
10
& Battery
Distribution
40
C System C
5
45
Systems Engineering
B PROJECT:
ESS Even Chnls ASTRO25 Project
TITLE
C
Rocky Mtn ASTRO 25 Repeater RF Site – Rack Layout
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Final Design
O A
8 7 6 5 4 3 2 1
Taylors
1+1 Spur Link Ridge
1+1 Loop Link
s
bp
M
49
Blossom Shannon
Hill
Rocky
Mtn
ps
s
bp
185Mb
8 5M
1
18
5
185Mbps
Mb
Fouche 185Mbps
ps
Gap
Floyd
911
Mt
8 5M bps
Alto 1
18 5
Mb
ps EOC
bps
B/U 911
Hillin
185M
dale
s
bp
5M
18
185Mbps
Cave
Leonard
Springs
8 7 6 5 4 3 2 1
H H
G G
F F
VHF Conventional
800 MHz
Repeater
Conventional
Repeater
Discriminated Audio
Discriminated Audio XTL2500 CDM1250
E E
D Digital Output Digital Output D

PA PA
C C
B B
Systems Engineering
PROJECT:

Fire and EMS Station Alerting System
TITLE:
Block Diagram
A CONTRACT:
Access via Repeaters on Mt Alto
ENGINEER: PM: SCALE: SIZE:
A
G. Brady NONE XXX
PROGRAM: DRAWN: CHECKED: SHEET: REV:
MS VISIO 2003 1 OF 1 XXX
FILE NAME: DATE: CODE IDENT: DRAWING NO:
12/10/2010 XXX
8 7 6 5 4 3 ORIGINAL DOCUMENT SIZE IS 11X17, CORRECT SCALE
Motorola Confidential, Proprietary and Trade Secret IS NOT GUARANTEED IF REDUCED OR ENLARGED 5.1-16
8 7 6 5 4 3 2 1
J J
800MHz P25
I JAIL Rptr I
On roof outside Central New wiring New wiring
MC1000 MC1000 MC1000 MC1000 MC1000 MC1000 MC1000
Control Room MC1000 MC1000
Junction Box
MC1000
New wiring New wiring New Wiring
MC1000 MC1000
H MC1000
MC1000 MC1000 MC1000
MC1000 H
P25 Jail Rptr

access via MC1000 MC1000 MC1000
Consolette MC1000 MC1000 New wiring New wiring
MC1000 MC1000
G Junction Box G
MIP5000 IP Console System @ Central Control

Junction Box
Digital Gateway New wiring New wiring
MIP5000 Console PC MC1000 MC1000
MC1000 MC1000
State Band access

F Ethernet Switch F
via Leased Line
Digital Gateway
Court talkgroup
access via
Consolette
Digital Gateway Digital Gateway Digital Gateway Digital Gateway
New Wiring
MC1000 MC1000 MC1000
MC1000
E E
FCPD & RPD Warrants talkgroup RFD & FCPW SO TAC talkgroup
talkgroup scan via access via talkgroup scan via access via
Consolette Consolette Consolette Consolette
Junction Box
D D
SO TAC talkgroup Court talkgroup
MC1000 MC1000 MC1000 MC1000
access via access via
Consolette Consolette
Junction Box
C C
NETWORKS & ENTERPRISE

Systems Engineering
PROJECT:
B Floyd County Jail & Courthouse, Rome, Georgia B
800 MHz P25 Repeater System
TITLE
Control Stations and Desktop Consoles

C
B
CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
Gary Brady A
A
A PROGRAM DRAWN CHECKED SHEET REV A

O 12/10/10 GJB Adapted Addendum #2 – To reflect Proposed Implementation Floyd Co – RFP #101216 O

10/29/10
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
H H
G G
800MHz P25
PRISON Repeater
F F
P25 Trunking
P25 Prison Rptr talkgroup access
access via via Control
E Control Station Station E
Junction Box
Junction Box
MC1000 MC1000
MC1000 MC1000
D MC1000 @ Work MC1000 @ Work D
@ Main Ctrl @ Main Ctrl
@ Admin Release @ Admin Release
Room Room
Ctrl Room Ctrl Room
C C

B Systems Engineering B
PROJECT
: Floyd County Prison, Rome Georgia
TITLE:
800 MHz P25 Repeater System
Control Stations and Desktop Consoles
SIZE
A CONTRACT: ENGINEER
G. Brady
:
PM: SCALE:
NONE : A
PROGRAM DRAWN: CHECKED: SHEET: REV:
:
1 OF 1
DATE: CODE IDENT: DRAWING NO:
Motorola Confidential, Proprietary and Trade Secret 12/10/2010 5.1-18

8 7 6 5 4 3
Section 6. Functional Acceptance Test Procedures
In-Field Draft

RFP# 101216
December 16, 2010
Functional Acceptance Test Procedures 1

Step 2. Verify that the change has
6.1 Wide Area Trunking - FDMA completed by checking the status
Only Sites of the job that was created in the
schedule Manager in the UNC.
Wide Area Trunking - FDMA Only Sites The status should be
"Completed".
Site Access Control/"Talkgroup Only" Site Step 3. Set SITE 2 to be a valid site for
Access Denial (7.8) RADIO-2 through the UCM. Set
SITE 2 to be a non-valid site for
TALKGROUP 1 through the UCM
1. DESCRIPTION and distribute the update to the
system.
The Unified Network Configurator (UNCW) can be
used to limit radio or talkgroup access to selected valid Step 4. Attempt to force RADIO-2 to scan to
sites. Control can be exercised to restrict radio users SITE 2. Verify that RADIO-2
or talkgroups to certain sites, or to steer radio activity cannot affiliate to SITE 2 since
away from smaller sites in an effort to avoid busies. TALKGROUP 1 is a non-valid
User Configuration Manager (UCM) flags establish talkgroup for SITE 2.
which sites are valid for each individual radio user,
talkgroup and multigroup. An overall Site Access Step 5. Set SITE 2 to be a valid site for
Denial flag for the system governs how these radio TALKGROUP 1 through the UCM.
and talkgroup settings affect the affiliation or rejection Set SITE 2 to be a non-valid site
of radios to individual sites. Four possible values for for RADIO-2 through the UCM
the Site Access Denial flag exist: Individual Only, and distribute the update to the
Talkgroup Only, Either, or Both. system. (The change must
complete before the next step is
"Talkgroup (TG) Only" Site Access Denial dictates that done.)
a radio will not be allowed to affiliate to a particular site
if its affiliated talkgroup does not have access to that Step 6. Cycle power to RADIO-2 then
site. In this case, the individual radio user setting for attempt to force RADIO-2 to scan
valid sites is not used in the determination of actual to SITE 2. Verify that RADIO-2 is
site affiliation permissions. now allowed to affiliate to SITE 2
since the talkgroup record
NOTE: Site Denial flags are not cleared from the determines site access.
subscriber until the power is cycled or the talkgroup is
changed. Step 7. Initiate a call from RADIO-2. Verify
SETUP that RADIO-2 is allowed to make
RADIO-1 - TALKGROUP 1 the call from SITE 2 since
RADIO-1 - SITE - SITE 1 TALKGROUP 1 is valid at SITE 2.
RADIO-2 - TALKGROUP 1 Also verify that RADIO-1 hears
RADIO-2 - SITE - SITE 1 the audio.
VERSION #1.010
Step 8. Set Site2 to be a valid site for
RADIO-2. Return the Site Access
Denial Flag to "Both" and
2. TEST distribute the update to the
system. (The change should
Step 1. Set the Site Access Denial Flag to Talkgroup complete before the next test is
Only via the Unified Network Configurator done.)
(UNCW).
Pass____ Fail____
RFP# 101216
December 16, 2010
2 Functional Acceptance Test Procedures

Wide Area Trunking - FDMA Only Sites 2. TEST
Step 1. Verify ATG 1 is set for the Wait

Multigroup Call in Wait Mode (Single Site) mode in the UCM database.
Step 2. Using RADIO-1, initiate a call on

1. DESCRIPTION TALKGROUP 1.
Step 3. While RADIO-1 is keyed, attempt to

This trunking feature allows an equipped radio user to initiate a multigroup call using
transmit an announcement to several different RADIO-4 on ATG 1. Verify
talkgroups simultaneously. The multigroup (ATG) call RADIO-4 receives a busy tone
can be flagged for Wait Mode in the User because one of the talkgroups
Configuration Manager (UCM) database forcing all attached to ATG 1 is involved in a
attached talkgroups to finish calls in progress before Talkgroup Call.
the trunked system will process the multigroup call.
The system does not permit inactive, attached Step 4. Key RADIO-2 and verify that a busy
talkgroups to initiate Talkgroup Calls during the "wait" tone is received because the ATG
timeframe. As with other types of calls, multigroup 1 call is in queue.
calls can take place from anywhere in the system.
Step 5. Dekey RADIO-1 and verify RADIO-4
receives a callback.
SETUP
Step 6. Key RADIO-4 and verify both
RADIO-1 and RADIO-2 hear the
RADIO-1 - TALKGROUP 1 multigroup call while RADIO-3
RADIO-2 - TALKGROUP 2 does not unmute.
RADIO-3 - RANDOM
RADIO-4 - ATG 1
* TALKGROUP 1 and TALKGROUP 2 are members of

ATG 1.
* RANDOM is any talkgroup not a member of ATG 1.
* Multigroups are set up through both the UCM and the

Subscriber Programming software.
Pass____ Fail____
VERSION #1.050

RFP# 101216
December 16, 2010

2. TEST
Wide Area Trunking - FDMA Only Sites
Step 1. Verify ATG 1 is set for the Wait
mode in the UCM database.
Multigroup Call in Wait Mode
TALKGROUP 1.
1. DESCRIPTION
Step 3. While RADIO-1 is keyed, attempt to
initiate a multigroup call using
This trunking feature allows an equipped radio user to RADIO-4 on ATG 1. Verify
transmit an announcement to several different RADIO-4 receives a busy tone
talkgroups simultaneously. The multigroup (ATG) call because one of the talkgroups
can be flagged for Wait Mode in the User attached to ATG 1 is involved in a
Configuration Manager (UCM) database forcing all Talkgroup Call.
attached talkgroups to finish calls in progress before
the trunked system will process the multigroup call. Step 4. Key RADIO-2 and verify that a busy
The system does not permit inactive, attached tone is received because the ATG
talkgroups to initiate Talkgroup Calls during the "wait" 1 call is in queue.
timeframe. As with other types of calls, multigroup
calls can take place from anywhere in the system. Step 5. Dekey RADIO-1 and verify RADIO-4
SETUP Step 6. Key RADIO-4 and verify both

RADIO-1 and RADIO-2 hear the
multigroup call while RADIO-3
RADIO-1 - TALKGROUP 1 does not unmute.
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 2
RADIO-3 - RANDOM (Not part of MG)
RADIO-4 - ATG 1

ATG 1.

Pass____ Fail____

VERSION #1.240

RFP# 101216
December 16, 2010

Step 1. Verify/Set the Site Access Denial

Site Access Control/"Both" Site Access Flag to Both via the Unified
Denial Network Configurator Wizard
(UNCW).
1. DESCRIPTION Step 2. Cycle power to RADIO-1 and

RADIO-2 to force them to affiliate,
this will clear any site denials they
The Unified Network Configurator (UNCW) can be may hold in memory.
used to limit radio or talkgroup access to selected valid
sites. Control can be exercised to restrict radio users Step 3. Initiate a TALKGROUP 1 call from
or talkgroups to certain sites, or to steer radio activity RADIO-2. Verify that RADIO-2 is
away from smaller sites in an effort to avoid busies. allowed to make the
The User Configuration Manager (UCM) flags TALKGROUP 1 call.
establish which sites are valid for each individual radio
user, talkgroup and multigroup. An overall Site Access Step 4. Set SITE 2 to be a non-valid site for
Denial flag for the system governs how these radio RADIO-2 through the UCM.
and talkgroup settings affect the affiliation or rejection
of radios to individual sites. Once a subscriber unit has Step 5. Initiate a TALKGROUP 1 call from
been denied at a site, it will not attempt to access that RADIO-2. Verify that RADIO-2 is
site unless power is cycled or the user changes allowed to make the
talkgroups. Four possible values for the Site Access TALKGROUP 1 call.
Denial flag exist: Individual Only, Talkgroup Only,
Either, or Both. Step 6. Set SITE 2 to be a non-valid site for
"Both" Site Access Denial indicates that a radio will not TALKGROUP 1 through the UCM
be allowed to affiliate to a site only if both the radio and distribute the update to the
user and affiliated talkgroup do not have access to the system.
site.
Step 7. Verify the updates complete using
NOTE: Site Denial flags are not cleared from the the Schedule Manager.
changed. Step 8. Initiate a TALKGROUP 1 call from
RADIO-2. Verify that RADIO-2
receives a reject, and roams to a
SETUP valid site. RADIO-2 is not allowed
to make the TALKGROUP 1 call
from SITE 2 since TALKGROUP 1
RADIO-1 - TALKGROUP 1 nor RADIO-2 is valid at SITE 2.
RADIO-2 - TALKGROUP 1 Step 9. Reset all Talkgroup and Radio User
RADIO-2 - SITE - SITE 2 flags in the UCM. Verify the
updates complete using the
Schedule Manager.
VERSION #1.030
Step 10. Recycle power to the radios
to clear the affiliation flags.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Change the emergency type for
TALKGROUP 1's template using
Emergency Alarm and Call with Ruthless the User Configuration Manager
Preemption (UCM) as Ruthless Preemption.
Step 2. Simulate a busy system by disabling
all channels at SITE 1 with the
1. DESCRIPTION exception of the control channel
and one voice channel.
Step 3. Press the PTT on RADIO-4 to
Users in life threatening situations can use the initiate a call on TALKGROUP 2
Emergency button on the radio to immediately send a and hold the PTT switch until
signal to the dispatcher and be assigned the next instructed to release. Verify
available voice channel. An Emergency Call can be RADIO-3 receives the call.
set to either Top of Queue or Ruthless Preemption Step 4. Key RADIO-1 and verify the radio
operation. To demonstrate this, an Emergency Alarm receives a busy tone. Release the
and Call will be initiated from a portable which will be PTT switch on RADIO-1.
received by a portable, on the same talkgroup, Step 5. Using RADIO-1 send an Emergency
affiliated at any site of any zone in the system. Call by depressing the emergency
switch and then the PTT switch.
NOTE : If the subscriber does not have the Display Step 6. Observe that RADIO-1 is granted
option, the Emergency ID will not be displayed. This the channel immediately and the
test is not recommended for single site systems as RF Talkgroup Call is dropped for
contention will occur. RADIO-3. Verify an Emergency
Alarm is displayed at CONSOLE-1
on TALKGROUP 1. Dekey
SETUP RADIO-4.
Step 7. Key RADIO-3 and verify the radio
receives a busy tone. Release the
RADIO-1 - TALKGROUP 1 PTT switch on RADIO-3.
RADIO-1 - SITE - SITE 1 Step 8. End the Emergency Call by holding
RADIO-2 - TALKGROUP 1 down the Emergency button on
RADIO-2 - SITE - SITE 2 RADIO-1 until an alert tone
RADIO-3 - TALKGROUP 2 sounds. Verify RADIO-1 returns to
RADIO-3 - SITE - SITE 1 normal operation and that RADIO-
RADIO-4 - TALKGROUP 2 3 receives a callback after the
RADIO-4 - SITE - SITE 2 emergency hang time expires.
CONSOLE-1 - TALKGROUP 1 Step 9. Return the emergency type for
TALKGROUP 1's template back
to Top of Queue.
VERSION #1.140 Step 10. Enable the disabled
channels at SITE 1 to return the
system to normal operation.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1 send an Emergency

Emergency Alarm and Call with Hot Mic Alarm by pressing the emergency
(Single Site) button.
Step 2. Observe the display on RADIO-2

1. DESCRIPTION and RADIO-3 denotes an
emergency and the unit ID or alias
of RADIO-1.
Users in life threatening situations can use the
Emergency button on the radio to immediately send a Step 3. Observe that RADIO-2 and RADIO-
signal to the dispatcher and be assigned the next 3 can hear any audio from
available voice channel. An Emergency Call can be RADIO-1 even though RADIO-1
set to either Top of Queue or Ruthless Preemption does not have its PTT switch
operation. During an emergency call the Emergency pressed.
ID will appear on the display of the subscribers. To
demonstrate this, an Emergency Alarm and Call will be Step 4. Observe that RADIO-1 PTT times
initiated from a portable which will be received by a out and the radio dekeys.
portable, on the same talkgroup, affiliated at any site of
any zone in the system. Step 5. End the Emergency Call by holding
This test demonstrates when the Hot Mic option is down the Emergency button.
chosen, the subscriber will send an emergency and
after a voice channel is assigned, the subscriber will
automatically transmit for a programmable period of
time.
Emergency Alarm with Voice to Follow (Hot Mic) is an
option in the portable and must be enabled via
software. This test case works for all portable radios.
For mobile radios, specific mobile microphone models
are required.
NOTE : If the subscriber does not have a display, the
Emergency ID will not be displayed.
SETUP Pass____ Fail____
VERSION #1.080

RFP# 101216
December 16, 2010

Audio Interrupt/Interrupt Never Mode Step 1. Verify TALKGROUP 1's template is

set up as Audio Interrupt Never
through the User Configuration
1. DESCRIPTION Manager (UCM).

A radio PTT request may be received for a group TALKGROUP 1.
already active and currently being sourced by another
radio unit. The talkgroup can be flagged in the User Step 3. Verify both RADIO-2 and RADIO-3
Configuration Manager (UCM) to either allow or monitor the audio.
disallow the new PTT. If allowed, the latest PTT
request will be granted and become the source of the Step 4. Using RADIO-3, initiate a call on
call. If both Radios are at the same site, RF contention TALKGROUP 1.
may prevent either call from working.
Step 5. Verify that RADIO-3 receives a
reject and that RADIO-2 continues
SETUP to listen to RADIO-1.
Step 6. Dekey both Radios.

VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify TALKGROUP 1's template is

Audio Interrupt/Interrupt Never Mode (Single set up as Audio Interrupt Never
Site) through the User Configuration
Manager (UCM).
1. DESCRIPTION Step 2. Using RADIO-1, initiate a call on

TALKGROUP 1.
A radio PTT request may be received for a group Step 3. Verify both RADIO-2 and RADIO-3
already active and currently being sourced by another monitor the audio.
radio unit. The talkgroup can be flagged in the User
Configuration Manager (UCM) to either allow or Step 4. Using RADIO-3, initiate a call on
disallow the new PTT. If allowed, the latest PTT TALKGROUP 1.
request will be granted and become the source of the
call. If both Radios are at the same site, RF contention Step 5. Verify that RADIO-3 receives a
may prevent either call from working. reject and that RADIO-2 continues
to listen to RADIO-1.
SETUP Step 6. Dekey both Radios.
VERSION #1.090
Pass____ Fail____

RFP# 101216
December 16, 2010


Emergency Alarm and Call with Hot Mic Alarm by pressing the emergency
button.
1. DESCRIPTION Step 2. Observe the display on RADIO-2

and RADIO-3 denotes an
Users in life threatening situations can use the emergency and the unit ID or alias
Emergency button on the radio to immediately send a of RADIO-1.
signal to the dispatcher and be assigned the next
available voice channel. An Emergency Call can be Step 3. Observe that RADIO-2 and RADIO-
set to either Top of Queue or Ruthless Preemption 3 can hear any audio from
operation. During an emergency call the Emergency RADIO-1 even though RADIO-1
ID will appear on the display of the subscribers. To does not have its PTT switch
demonstrate this, an Emergency Alarm and Call will be pressed.
initiated from a portable which will be received by a
portable, on the same talkgroup, affiliated at any site of Step 4. Observe that RADIO-1 PTT times
any zone in the system. out and the radio dekeys.
This test demonstrates when the Hot Mic option is
chosen, the subscriber will send an emergency and Step 5. End the Emergency Call by holding
after a voice channel is assigned, the subscriber will down the Emergency button.
automatically transmit for a programmable period of
time.
Emergency Alarm with Voice to Follow (Hot Mic) is an
option in the portable and must be enabled via
software. This test case works for all portable radios.
For mobile radios, specific mobile microphone models
are required.
NOTE: If the subscriber does not have a display, the
Emergency ID will not be displayed.
SETUP
RADIO-2 - TALKGROUP 1 Pass____ Fail____
VERSION #1.150

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, press the Private

Private Call Call (Call) button.
Step 2. Enter the unit ID of RADIO-2 with

1. DESCRIPTION the keypad, or scroll to the
location where this ID is stored.
Private Call is a selective calling feature that allows a Step 3. Press the PTT to initiate the Private
radio user to carry on one-to-one conversation that is Call.
only heard by the 2 parties involved. Subscriber units
receiving a private call will sound an alert tone. As with Step 4. Verify that RADIO-2 hears tones
other types of calls, Private Calls can take place from and the display indicates that a
anywhere in the system. Private Call has been received,
but RADIO-3 receives no
indications.
SETUP
Step 5. Answer the call at RADIO-2 by
pressing the Private Call (Call)
RADIO-1 - TALKGROUP 1 button. If RADIO-2 has a display,
RADIO-2 - TALKGROUP 1 verify it shows the ID number or
RADIO-3 - TALKGROUP 1 Alias of the calling unit.
Step 6. Press the PTT switch on RADIO-2

VERSION #1.080 and respond to the Private Call.
Note that if you do not press the
Private Call button before
pressing PTT, your audio will be
heard by all members of the
talkgroup, and not just by the
radio initiating the Private Call.
Step 7. Verify that RADIO-2 can

communicate with RADIO-1.
Step 8. Verify that RADIO-3 does not

monitor the Private Call.
Step 9. End the Private Call by pressing the

"home" key and return to normal
talkgroup operation.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Set the Site Access Denial Flag to
Either via the Unified Network
Site Access Control/"Either" Site Access Configurator Wizard (UNCW). (If a
change is made the updates will need
Denial (7.8 Single Site)
to be approved in the Schedule
Manager.)
1. DESCRIPTION Step 2. Verify that the job(s) that was/were
created due to the change has
The Unified Network Configurator (UNCW) can be completed through the schedule
used to limit radio or talkgroup access to selected valid Manager.
sites. Control can be exercised to restrict radio users
or talkgroups to certain sites, or to steer radio activity Step 3. Set SITE 1 to be a non-valid site for
away from smaller sites in an effort to avoid busies. RADIO-2 through the User
The User Configuration Manager (UCM) flags Configuration Manager (UCM). Set
establish which sites are valid for each individual radio SITE 1 to be a valid site for
user, talkgroup and multigroup. An overall Site Access TALKGROUP 1 through the UCM and
distribute the update to the system.
Denial flag for the system governs how these radio
Step 4. Key-up and verify that RADIO-2 cannot
of radios to individual sites. Once a subscriber unit has affiliate to SITE 1 since SITE 1 is a
been denied at a site, it will not attempt to access that non-valid site for RADIO-2. RADIO-2
site unless power is cycled or the user changes will display "Out of Range."
talkgroups. Four possible values for the Site Access
Denial flag exist: Individual Only, Talkgroup Only, Step 5. Set SITE 1 to be a non-valid site for
Either, or Both. TALKGROUP 1 through the UCM. Set
SITE 1 to be a valid site for RADIO-2
"Either" Site Access Denial indicates that a radio will through the UCM and distribute the
not be allowed to affiliate to a site if either the radio update to the system.
user or affiliated talkgroup does not have access to
Step 6. Force RADIO-2 to scan to SITE 1. Verify
that site.
that RADIO-2 is still not permitted to
affiliate to SITE 1 since now the
NOTE: Site Denial flags are not cleared from the selected talkgroup is non-valid at
subscriber until the power is cycled or the talkgroup is SITE 1.
changed.
Step 7. Set SITE 1 to be a valid site for
TALKGROUP 1 through the UCM and
SETUP distribute the update to the system.
Step 8. Verify that after some time, RADIO-2

can now affiliate to SITE 1. Note that
RADIO-1 - TALKGROUP 1 power may need to be recycled on
RADIO-1 - SITE - SITE 1 RADIO-2 before it can again affiliate
RADIO-2 - TALKGROUP 1 to SITE 1.
Step 9. Initiate a call from RADIO-2 on
TALKGROUP 1. Verify that RADIO-2
VERSION #1.020 is allowed to make the call from SITE
1 since both TALKGROUP 1 and
RADIO-2 are valid at SITE 1.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the test telephone line, dial the

Landline to Subscriber Telephone telephone number of a phone line
Interconnect connected to the PBX.
Step 2. Verify that an automated voice is

1. DESCRIPTION heard in the telephone prompting
the landline caller to enter the
eight-digit unit ID of the target
This test will show the capability to make or receive radio.
phone calls on a radio. Two types of interconnect calls
can be initiated: subscriber-to-landline and landline-to- Step 3. Enter the fully qualified radio ID of
subscriber. RADIO-1.
The landline-to-subscriber call feature enables a land
telephone user to dial a radio user directly. Step 4. Verify that ringing is heard on
Some radios feature phone list capability with RADIO-1 only and that the display
programmable alias names which may be assigned. indicates a phone call is being
Radios with keypad operation may also be received.
programmed for unlimited dialing capability.
Since the telephone interconnect functionality depends Step 5. Press the Telephone Interconnect
upon the Private Branch Exchange (PBX) unit, sites button on RADIO-1 to answer the
must be Wide Area Trunking in order to support this landline-to-subscriber interconnect
telephone interconnect function. In addition, radios call.
cannot be site-locked to a specific site before initiating
a telephone interconnect call. Step 6. Verify that the landline-to-subscriber
call can be completed, and the
Note: A radio can be setup to use either the Private radio and landline users can
Branch Exchange (PBX) in the zone it is affiliated with communicate.
or a PBX in a default zone.
Step 7. Verify that RADIO-2 does not listen
to the call.
SETUP
Step 8. Hang up the interconnect call.
VERSION #1.070
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that RADIO-1 is set to

Priority Monitor/Priority Scan TALKGROUP 1 and in the scan
mode of operation and
programmed to scan
1. DESCRIPTION TALKGROUP 1 and
TALKGROUP 2 with
TALKGROUP 1 as its Priority
This test will show that a subscriber unit can scan a Monitor Talkgroup.
pre-programmed list (in the radio) to find any Priority
and Non-priority Talkgroups with assigned voice Step 2. Verify that in the User Configuration
channels at that site. To demonstrate this, a call will be Manager (UCM) under Talkgroup
initiated from a portable at a remote site on a talkgroup Configuration, Priority Monitor and
monitored by a portable at the same site as the the Valid Site setting is set to yes
scanning radio. The scanning radio will scan from its for SITE 2.
selected talkgroup to the active talkgroup. The test will
be repeated with an additional radio transmitting on Step 3. Initiate a Talkgroup Call with
the Priority Talkgroup while the scanning radio is RADIO-4 to RADIO-5 and observe
scanning. This third radio will be on a remote site with that RADIO-1 scans to the
a fourth radio on the Priority Talkgroup at the same talkgroup and receives the call.
site as the scanning radio. Note that the radio will scan Keep the call in progress until the
for talkgroups only at the site to which it is affiliated. completion of the following step.
Note: Subscribers must be capable of supporting the
Talkgroup scan. Step 4. Initiate a Talkgroup Call with
RADIO-3 and observe that
RADIO-1 reverts to the
SETUP TALKGROUP 1 and receives the
call.
RADIO-1 - TALKGROUP 1 (SCANNING)

* RADIO-1 needs to be set to a dial position configured

to scan.
Pass____ Fail____
VERSION #1.170

RFP# 101216
December 16, 2010

Step 1. Verify RADIO-6's template for

Receive Only Radio "dispatch enabled" is set to no in
the Radio User Capabilities
Profile. This allows the radio to
1. DESCRIPTION receive, but not initiate group
calls.
This test verifies that a subscriber can be set up for Step 2. Verify RADIO-6's Radio User record
receive operation only. is set to no for the "Voice enabled"
flag. This allows the user to
Setting a portable for "dispatch enabled" equal to no in receive dispatch calls, but not
the Radio User Capabilities record allows the radio to originate or receive Unit-to-Unit or
receive, but not initiate group calls. call alerts.
Setting a portable for "Voice enabled" equal to no in Step 3. Verify that the Site Access denial
the Radio User profile allows the user to receive flag is set to either "Both" or "TG
dispatch calls, but not originate or receive Unit-to-Unit Only".
or call alerts.
Step 4. Make a call from CONSOLE-1 on
SETUP TALKGROUP 1. Verify RADIO-6
and RADIO-2 can hear the audio.
Step 5. Make a call from RADIO-2 and

RADIO-6 - TALKGROUP 1 verify that both RADIO-6 and
RADIO-2 - TALKGROUP 1 CONSOLE-1 hear the call.
CONSOLE-1 - TALKGROUP 1
Step 6. Verify that RADIO-6 is not granted a
channel when it is keyed up.
VERSION #1.120
Step 7. Verify that CONSOLE-1 can not
make a Private Call to RADIO-6
but can Private Call RADIO-2.
Step 8. Verify that RADIO-2 cannot make a

Private Call to RADIO-6 but can
Private Call CONSOLE-1.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a call on TALKGROUP 1

Emergency Alarm and Call with Talkgroup from RADIO-1 and verify RADIO-2
Revert can hear the audio. Verify RADIO-
3 does not hear the audio.
1. DESCRIPTION Step 2. Dekey RADIO-1.
Step 3. Using RADIO-1, send an

Users in life threatening situations can use the Emergency Call by depressing the
Emergency button on the radio to immediately send a emergency switch and then the
signal to the dispatcher and be assigned the next PTT switch.
available voice channel. An Emergency Call can be
set to either Top of Queue or Ruthless Preemption Step 4. Observe the display on RADIO-3
operation. During an emergency call the Emergency denotes an emergency and the
ID will appear on the display of the subscribers. To unit ID or alias of the unit sending
demonstrate this, an Emergency Alarm and Call will be the emergency and that RADIO-3
initiated from a portable which will be received by a can hear RADIO-1's audio.
portable affiliated at any site of any zone in the
system. Step 5. In addition observe that RADIO-2
This test will show a portable has the ability to revert to cannot hear RADIO-1's audio.
a specific talkgroup when an emergency is initiated.
This is useful when the users have a designated Step 6. Release the PTT switch on RADIO-
talkgroup for handling emergencies. 1 and end the Emergency Call by
The revert talkgroup must be set in the portable via holding down the Emergency
software. button.
NOTE: If the subscriber does not have the Display

option, the Emergency ID will not be displayed.
SETUP
RADIO-3 - EMERGENCY TG
Pass____ Fail____
* EMERGENCY TG is the talkgroup programmed for
emergency reverts.
VERSION #1.070

RFP# 101216
December 16, 2010

Step 1. Verify that TALKGROUP 1's

Fast Start Talkgroup with Critical Site template is set up as Fast Start
Manager (UCM) and specify SITE
1. DESCRIPTION 1 as a Critical Site.

Talkgroups can be set up as either All Start or Fast all channels at SITE 1 with the
Start. exception of the control channel
"FastStart" is the Talkgroup Call setup approach that
allows a group call setup whether or not all affiliated Step 3. Key RADIO-3 and busy out the only
Talkgroup members are available. This "Automatic voice channel available at SITE 1.
Busy Override by Talkgroup" call setup method still
requires the participation of all affiliated consoles, Step 4. Initiate a Talkgroup Call from
LOMIs (i.e. logging recorders) and critical sites before RADIO-1 and observe the call is
the call can begin. As channels at the affiliated busied as no voice channel is
talkgroup members' sites become available, they are available at SITE 1 for RADIO-2.
added to the call in progress.
Step 5. Dekey RADIO-3. Verify that the call
NOTE: This feature test only works on a multi-site from RADIO-1 is now granted and
system. RADIO-2 can hear the audio.
Step 6. Return the system to the original

SETUP settings.
VERSION #1.140
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a secure wide area call with

Secure Operation (Single Site) RADIO-1 on TALKGROUP 1.
Keep this call in progress until
instructed to end the call.
1. DESCRIPTION
Step 2. Observe that RADIO-2 will be able
to monitor the call.
Digital encryption is used to scramble a transmission
so only properly equipped and configured radios can Step 3. Observe that RADIO-3 does not
monitor the conversation. A "Key" is used to encrypt receive the call.
the transmit audio. Only radios with the same "Key"
can decrypt the audio and listen to it. Step 4. Observe that RADIO-4 will also
receive the call even with the
secure switch set to the non-
SETUP secure mode of operation.
Step 5. End the call from RADIO-1.

RADIO-1 - TALKGROUP 1 (Secure TX Mode)
RADIO-2 - TALKGROUP 1 (Secure TX Mode) Step 6. Respond to the RADIO-1 call with
RADIO-3 - TALKGROUP 1 (Secure TX Mode & no, or RADIO-2. Verify that RADIO-1
incorrect Key ) and RADIO-4 hear the reponse
RADIO-4 - TALKGROUP 1 (Clear TX Mode) but that RADIO-3 does not hear
the response.
Note: The identical secure mode must be programmed
into RADIO-1, RADIO-2, RADIO-4 and that RADIO-3
has no secure code loaded or has a unique secure
code from the other testing radios.
VERSION #1.070
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Make a Talkgroup Call from RADIO-

Emergency Alarm and Call with Talkgroup 1 and verify only RADIO-2 can
Revert (Single Site) hear the audio.
Step 2. Dekey RADIO-1.

1. DESCRIPTION
Call by depressing the emergency
Users in life threatening situations can use the switch and then the PTT switch.
Emergency button on the radio to immediately send a
signal to the dispatcher and be assigned the next Step 4. Observe the display on RADIO-3
available voice channel. An Emergency Call can be denotes an emergency and the
set to either Top of Queue or Ruthless Preemption unit ID or alias of the unit sending
operation. . During an emergency call the Emergency the emergency and that RADIO-3
ID will appear on the display of the subscribers. To can hear RADIO-1's audio.
demonstrate this, an Emergency Alarm and Call will be
initiated from a portable which will be received by a Step 5. In addition observe that RADIO-2
portable affiliated at any site of any zone in the can not hear RADIO-1's audio.
system.
This test will show a portable has the ability to revert to Step 6. Release the PTT switch on RADIO-
a specific talkgroup when an emergency is initiated. 1 and end the Emergency Call by
This is useful when the users have a designated holding down the Emergency
talkgroup for handling emergencies. button.
The revert talkgroup must be set in the portable via
software.
NOTE : If the subscriber does not have the Display

SETUP
Pass____ Fail____
RADIO-3 - EMERGENCY TG
* EMERGENCY TG is the talkgroup programmed for

emergency revert.
VERSION #1.050

RFP# 101216
December 16, 2010

Step 1. Verify the emergency type for

Emergency Alarm and Call with Top of Queue TALKGROUP 1's template is set
up as Top of Queue.
1. DESCRIPTION Step 2. Simulate a busy system by disabling

exception of the control channel
Users in life threatening situations can use the and one voice channel.
Emergency button on the radio to immediately send a
signal to the dispatcher and be assigned the next Step 3. Press the PTT to initiate a call with
available voice channel. An Emergency Call can be RADIO-3 and hold the PTT switch
set to either Top of Queue or Ruthless Preemption until instructed to release.
operation. During an emergency call the Emergency
ID will appear on the display of the subscribers. To Step 4. Key RADIO-4 and verify the radio
demonstrate this, an Emergency Alarm and Call will be receives a busy tone. Release
initiated from a portable which will be received by a the PTT switch on RADIO-4.
portable, on the same talkgroup, affiliated at any site of
any zone in the system. Step 5. Using RADIO-1 send an Emergency
Call by depressing the emergency
NOTE : If the subscriber does not have the Display switch and then the PTT switch.
Step 6. Observe that RADIO-1 cannot
transmit due to the voice channel
SETUP being busy.
Step 7. Release the PTT switch on RADIO-

RADIO-1 - TALKGROUP 1 3.
RADIO-2 - TALKGROUP 1 Step 8. Observe that RADIO-1 receives the
RADIO-2 - SITE - SITE 2 call back before RADIO-4 and is
RADIO-3 - TALKGROUP 2 able to proceed with the call. Also
RADIO-3 - SITE - SITE 1 observe that the display on
RADIO-4 - TALKGROUP 3 RADIO-2 denotes an emergency
RADIO-4 - SITE - SITE 1 and the unit ID or alias of RADIO-
1.
All radios and talkgroups should start with default
priorities. Default is 10. Step 9. Dekey RADIO-1 and end the
Emergency Call by holding down
the Emergency button on RADIO-
VERSION #1.180 1 until an alert tone sounds.
Verify RADIO-1 returns to normal
operation and that RADIO-4
Step 10. Return the system to normal

operation by enabling all the
channels at SITE 1.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, initiate a telephone

Subscriber To Landline Telephone call to phone number of a pager
Interconnect - Overdial Mode with overdial prompt.
Step 2. Enter the pager number of the party

1. DESCRIPTION to be paged when asked.
Step 3. Enter a telephone number when

This test verifies the capability to make or receive asked.
can be initiated: subscriber-to-landline and landline-to- Step 4. Hang up the interconnect call on
subscriber. RADIO-1.
The subscriber-to-landline call feature enables a radio
user to dial a land telephone user directly. If calling a Step 5. Verify the page goes through.
automated voice system or a paging system, the user
can enter more dial keys.
Some radios feature phone list capability with
programmable alias names which may be assigned.
Radios with keypad operation may also be
Since the telephone interconnect functionality depends
upon the Private Branch Exchange (PBX) unit, sites
must be Wide Area Trunking in order to support this
telephone interconnect function. In addition, radios
a telephone interconnect call.
Note : A radio can be setup to use either the Private
Branch Exchange (PBX) in the zone it is affiliated with Pass____ Fail____
SETUP
VERSION #1.070

RFP# 101216
December 16, 2010


Site Access Control/"Individual Only" Site Individual Only via the Unified
Access Denial (7.8 Single Site) Network Configurator (UNCW). Verify
that the change has completed by
checking the status of the job(s) that
1. DESCRIPTION was\were created in the schedule
Manager in the UNC. The status
should be "Completed".
used to limit radio or talkgroup access to selected valid
sites. Control can be exercised to restrict radio users TALKGROUP 1. Verify that RADIO-2
or talkgroups to certain sites, or to steer radio activity is allowed to make the call.
away from smaller sites in an effort to avoid busies. Step 3. Set SITE 1 to be a non-valid site for
The User Configuration Manager (UCM) flags TALKGROUP 1 through the UCM and
establish which sites are valid for each individual radio distribute the update to the system.
user, talkgroup and multigroup. An overall Site Access (The change must complete before
Denial flag for the system governs how these radio the next step is done.)
and talkgroup settings affect the affiliation or rejection Step 4. Verify that RADIO-2 is still affiliated to
of radios to individual sites. Four possible values for SITE 1 since the individual Radio user
record determines site access.
the Site Access Denial flag exist: Individual Only,
Talkgroup Only, Either, or Both.
TALKGROUP 1. Verify that RADIO-2
is not allowed to make the call from
"Individual Only" Site Access Denial dictates that a SITE 1 since TALKGROUP 1 is no
radio will not be allowed to affiliate to a particular site if longer valid at SITE 1.
the radio user does not have access to that site. If the Step 6. Change RADIO-2 to TALKGROUP 2
Site Access Denial flag is set to "Individual Only", the and attempt to make a call at SITE 1.
talkgroup record for valid sites is not used in the Verify that the Talkgroup Call occurs
determination of actual site affiliation permissions. because TALKGROUP 2 is valid at
SITE 1.
NOTE: Site Denial flags are not cleared from the Step 7. Initiate a Private Call from RADIO-2 to
RADIO-1. Verify that the Private Call
occurs since RADIO-2 is valid at SITE
changed.
1.
Step 8. Set SITE 1 to be a valid site for
SETUP TALKGROUP 1 through the UCM. Set
SITE 1 to be a non-valid site for
RADIO-1 - TALKGROUP 1 RADIO-2 through the UCM and
RADIO-1 - SITE - SITE 1 distribute the update to the system.
RADIO-2 - TALKGROUP 1 (The change must complete before
RADIO-2 - SITE - SITE 1 the next step is done.)
Step 9. Verify that RADIO-2 can no longer
affiliate to SITE 1 and that RADIO-2
VERSION #1.010 will display "Out of Range."
Step 10. Return all settings to the original state
and distribute the update to the
system. Power cycle RADIO-1 and
RADIO-2 to clear the affiliation flags.
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Access Control/"Individual Only" Site Individual Only via the Unified
Access Denial (7.8) Network Configurator (UNCW).
Step 2. Verify that the change(s) has/have

1. DESCRIPTION completed by checking the status of
the job(s) that was/were created in the
schedule Manager in the UNC. The
status should be "Completed".
used to limit radio or talkgroup access to selected valid Step 3. Cycle power to RADIO-1 and RADIO-2
sites. Control can be exercised to restrict radio users to force them to affiliate, this will clear
or talkgroups to certain sites, or to steer radio activity any site denials they may hold in
away from smaller sites in an effort to avoid busies. memory.
The User Configuration Manager (UCM) flags
establish which sites are valid for each individual radio Step 4. Initiate a Private Call from RADIO-2 to
user, talkgroup and multigroup. An overall Site Access RADIO-1. Verify that the Private Call
occurs since RADIO-2 is valid at SITE
Denial flag for the system governs how these radio
2. End the Private Call.
of radios to individual sites. Once a subscriber unit has Step 5. Set SITE 2 to be a non-valid site for
been denied at a site it will not attempt to access that RADIO-2 through the User
site unless power is cycled or the user changes Configuration Manager (UCM) and
talkgroups. Four possible values for the Site Access distribute the update to the system.
Denial flag exist: Individual Only, Talkgroup Only, (The change must complete before
Either, or Both. the next step is done.)
"Individual Only" Site Access Denial dictates that a Step 6. Initiate a Private Call from RADIO-2 to
radio will not be allowed to affiliate to a particular site if RADIO-1. Verify that RADIO-2
receives a reject, (Note: this may
the radio user does not have access to that site. If the
happen quickly and not be noticeable
Site Access Denial flag is set to "Individual Only", the
if the radio is not site locked. If site
talkgroup record for valid sites is not used in the locked, the radio will not roam until
determination of actual site affiliation permissions. the site lock is removed.) and roams
to a valid site. RADIO-2 is not allowed
NOTE: Site Denial flags are not cleared from the to make the Private Call from SITE 2
subscriber until the power is cycled or the talkgroup is since it is no longer valid at SITE 2.
changed.
Step 7. Set SITE 2 to be a valid site for RADIO-
2 through the UCM and distribute the
SETUP
update to the system. (The change
must complete before the next step is
RADIO-1 - TALKGROUP 1 done.)
RADIO-2 - TALKGROUP 1 Step 8. Cycle power to RADIO-1 and RADIO-2
RADIO-2 - SITE - SITE 2 to force them to affiliate, this will clear
any site denials they may hold in
memory.
VERSION #1.010
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that TALKGROUP 1 is set up

Sub-band Restricted Operation in the User Configuration Manager
(UCM) to be a sub-band restricted
talkgroup.
1. DESCRIPTION
Step 2. Verify TALKGROUP 2 is set up in
the UCM to be a non-sub-band
This feature will allow radios limited to one sub-band to restricted talkgroup.
operate at sites set up with resources to handle both
sub-band and full band range radios. Step 3. Using RADIO-1, initiate a call on
TALKGROUP 1.
SETUP Step 4. Verify that a sub-band restricted

channel is granted at both sites
and that only RADIO-3 is able to
RADIO-1 - TALKGROUP 1 monitor and respond to the call.
RADIO-2 - TALKGROUP 2 Step 5. Dekey RADIO-1.
RADIO-3 - TALKGROUP 1 Step 6. Using RADIO-2, initiate a call on
RADIO-3 - SITE - SITE 2 TALKGROUP 2.
RADIO-4 - SITE - SITE 2 Step 7. Verify that a non-sub-band restricted
* SITE 1 and SITE 2 should support sub-band and that only RADIO-4 is able to
channels. monitor and respond to the call.
VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010


Busy Queuing and Callback with Ten all channels at SITE 1 with the
Talkgroup Priority Levels (Single Site) exception of the control channel
1. DESCRIPTION Step 2. Verify the priority level for

TALKGROUP 4's template is set
up through the User Configuration
If no voice channel resources are available, radios Manager (UCM) as "9".
requesting channels for new conversations are placed
in a queue. Users of the same priority will move Step 3. Verify priority level for TALKGROUP
through the queue in a FIFO (first in, first out) 1 and TALKGROUP 3 templates
sequence; however, users of higher priority will be are set up through the (UCM) as
inserted ahead of lower priority users in queue. "10".
When a voice channel becomes available, the radio at
the top of the busy queue gets a channel assignment Step 4. Initiate a Talkgroup Call with
and generates a callback tone. The callback tone RADIO-1. Keep this call in
alerts the user that a channel assignment was made progress until instructed to end
and transmitting is now possible on the selected the call.
talkgroup.
Step 5. Key RADIO-3 and observe that the
Note: An Emergency Call has the highest priority at radio receives a busy. Key
level 1. The highest assignable priority is 2 and 10 is RADIO-2 and observe that the
the lowest. radio receives a busy.
NOTE: All radios and talkgroups should start with
default priorities. Default is 10. Step 6. End the Talkgroup Call established
in Step 3.
SETUP Step 7. Observe RADIO-2 receives the first

callback and can now make a call
to RADIO-4 upon receipt of the
RADIO-1 - TALKGROUP 1 callback indication.
RADIO-3 - TALKGROUP 3 Step 8. End the call between RADIO-2 and
RADIO-4 - TALKGROUP 4 RADIO-4.
Step 9. Observe RADIO-3 now receives a

VERSION #1.010 callback and can make a call upon
receipt of the callback indication.
Step 10. Return the system to the

original settings.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, initiate a telephone

Subscriber To Landline Telephone call to a test telephone phone
Interconnect number.
Step 2. Verify the telephone rings.

1. DESCRIPTION
Step 3. Pickup the phone and verify that
RADIO-1 and the landline user
This test will show the capability to make or receive can communicate.
can be initiated: subscriber-to-landline and landline-to- Step 4. Verify that the landline user hears a
subscriber. tone after each radio transmission
The subscriber-to-landline call feature enables a radio signifying the half-duplex nature of
user to dial a land telephone user directly. the interconnect call.
Some radios feature phone list capability with
programmable alias names which may be assigned. Step 5. Verify that RADIO-2 does not listen
Radios with keypad operation may also be to the call.
Since the telephone interconnect functionality depends Step 6. Hang up the interconnect call.
upon the Private Branch Exchange (PBX) unit, sites
must be Wide Area Trunking in order to support this
telephone interconnect function. In addition, radios
a telephone interconnect call.
Note: A radio can be setup to use either the Private

Branch Exchange (PBX) in the zone it is affiliated with
SETUP Pass____ Fail____
VERSION #1.080

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, press the page

Call Alert button.

location where this ID is stored
Call Alert is a tone page that allows a user to Step 3. Press the PTT to initiate the call
selectively alert another radio unit. The initiating radio alert (Page). Verify that the
will receive notification from the trunked system as to RADIO-1 user receives audible
whether or not the page was received by the target indication that the Call Alert
radio. Units receiving a Call Alert will sound an alert (Page) was sent.
tone. As with other types of calls, Call Alerts can take
place from anywhere in the system. Step 4. Verify that RADIO-2 user receives
an audible indication of an
incoming Call Alert (Page) was
SETUP sent but RADIO-3 does not.
Step 5. Verify RADIO-1 gets an audible

RADIO-1 - TALKGROUP 1 indication that the Call Alert
RADIO-2 - TALKGROUP 2 (Page) was successfully received
RADIO-3 - TALKGROUP 3 at the target radio.
Step 6. Turn off RADIO-2. Send a Call Alert

VERSION #1.120 (Page) from RADIO-1 to RADIO-
2.
Step 7. Verify that the RADIO-1 user

receives audible indication that
the Call Alert (Page) was sent.
Step 8. Verify RADIO-1 receives a "No

Acknowledgement" indication that
the Call Alert (Page) was not
successfully received at the target
radio.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. In the Unified Network Configurator

In Call User Alert (Enabled) - Unified Network Wizard (UNCW), verify that In-Call
Configurator Wizard (UNCW) Parameters User Alert is enabled. Verify that
RADIO-1 and RADIO-2 have
Talkgroup Muting (VMUT)
1. DESCRIPTION disabled in the radios.
Step 2. Enable Talkgroup Muting (VMUT)

In-Call User Alert enhances the Call Alert feature to on RADIO-1.
allow Call Alerts to be received by radios that are
currently involved in voice and data services. As part Step 3. Verify that there is a visual
of this feature, the radio supports Talkgroup Muting indication on RADIO-1 that
where the radio user can mute all talkgroup voice Talkgroup Muting is enabled.
received by the radio. The Console Dispatcher or
another radio user can unmute the radio by sending Step 4. Initiate a talkgroup call on
the radio a Call Alert. TALKGROUP 1 from CONSOLE-
1.
Note: Talkgroup Muting is a programmable option in
the radio. There are also sub-options which will affect Step 5. Verify that no audio is heard by
the time and operation of the Talkgroup muting. RADIO-1 and that RADIO-1
displays the ID of CONSOLE-1.
SETUP Step 6. Send a Call Alert to RADIO-1 from

receives a Call Alert and that
RADIO-1 - TALKGROUP 1 RADIO-2 indicates success of Call
RADIO-2 - TALKGROUP 2 Alert. Verify that CONSOLE-1
CONSOLE-1 - TALKGROUP 1 audio is now heard by RADIO-1
Step 7. End Console talkgroup call.

VERSION #1.070
Step 8. Acknowledge Call Alert by hitting
home key on RADIO-1.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a wide area call with RADIO-

Talkgroup Call (Single Site) 1 in TALKGROUP 1.
Step 2. Observe that only RADIO-2 will be

1. DESCRIPTION able to monitor and respond to the
call.
The Talkgroup is the primary level of organization for Step 3. Initiate a wide area call with RADIO-
communications on a trunked radio system. Radios 3 in TALKGROUP 2.
with Talkgroup Call capability will be able to
communicate with other members of the same Step 4. Observe that only RADIO-4 will be
Talkgroup. This provides the effect of a private able to monitor and respond to the
channel down to the Talkgroup level. This test will call.
demonstrate that a Talkgroup transmission initiated by
a radio user will only be heard by system users who
have the same Talkgroup selected. As with other types
of calls, Talkgroup Calls can take place from anywhere
in the system.
SETUP
Pass____ Fail____
VERSION #1.150

RFP# 101216
December 16, 2010

"Either" via the Unified Network
Site Access Control/"Either" Site Access Configurator Wizard (UNCW). (If a
Denial (7.8) change is made the updates will
need to be approved in the
Schedule Manager.)
1. DESCRIPTION Step 2. Verify that the approved updates
have completed by using the
Schedule Manager.
The Unified Network Configurator Wizard (UNCW) can Step 3. Cycle power to the radios to force
be used to limit radio or talkgroup access to selected them to affiliate, this will clear any
valid sites. Control can be exercised to restrict radio site denials they may hold in
users or talkgroups to certain sites, or to steer radio memory.
activity away from smaller sites in an effort to avoid Step 4. Initiate a TALKGROUP 1 call from
busies. UCM flags establish which sites are valid for RADIO-2. Verify that RADIO-2 is
each individual radio user, talkgroup and multigroup. allowed to make the
An overall Site Access Denial flag for the system TALKGROUP 1 call.
governs how these radio and talkgroup settings affect Step 5. Set SITE 2 to be a non-valid site for
the affiliation or rejection of radios to individual sites. RADIO-2 through the UCM and
Once a subscriber unit has been denied at a site, it will distribute the update to the
not attempt to access that site unless power is cycled system.
or the user changes talkgroups. Four possible values
for the Site Access Denial flag exist: Individual Only, Step 6. Initiate a TALKGROUP 1 call from
Talkgroup Only, Either, or Both. RADIO-2. Verify that RADIO-2
"Either" Site Access Denial indicates that a radio will valid site. RADIO-2 is not allowed
not be allowed to affiliate to a site if either the radio to make the TALKGROUP 1 call
user or affiliated talkgroup does not have access to from SITE 2 since RADIO-2 is no
that site. longer valid at SITE 2.
NOTE: Site Denial flags are not cleared from the Step 7. Switch RADIO-1 to TALKGROUP 2
subscriber until the power is cycled or the talkgroup is and initiate a TALKGROUP 2 call
changed. from RADIO-3. Verify that RADIO-
3 is allowed to make the
SETUP TALKGROUP 2 call.
RADIO-1 - TALKGROUP 1 Step 8. Set SITE 2 to be a non-valid site for

RADIO-1 - SITE - SITE 1 TALKGROUP 2 and distribute the
RADIO-2 - TALKGROUP 1 update to the system.
RADIO-3 - TALKGROUP 2 Step 9. Initiate a TALKGROUP 2 call from
RADIO-3 - SITE - SITE 2 RADIO-3. Verify that RADIO-3
VERSION #1.010 valid site. RADIO-3 is not allowed
to make the TALKGROUP 2 call
from SITE 2 since TALKGROUP 2
is no longer valid at SITE 2.
Step 10. Return all settings to the
original state and distribute the
update to the system.
Pass____ Fail____
RFP# 101216
December 16, 2010

Step 1. Turn OFF RADIO-1.

Continuous Assignment Updating
Step 2. Initiate a Talkgroup Call using
RADIO-2 and verify RADIO-3
1. DESCRIPTION hears the audio.
Step 3. While the Talkgroup Call is in

When a talkgroup is assigned a voice channel, the site progress, turn ON RADIO-1.
controller continues to transmit the channel
assignment on the control channel for the duration of Step 4. Observe that the radio, which was
the talkgroup call. Radios coming into use on the just brought back into service,
system are automatically sent to voice channels with joins the Talkgroup Call already in
conversations in progress involving their selected progress.
talkgroups.
Step 5. End the talkgroup call.
SETUP Step 6. Switch RADIO-1 to another

talkgroup.
RADIO-1 - TALKGROUP 1 Step 7. Initiate a Talkgroup Call from

RADIO-2 - TALKGROUP 1 RADIO-2 to RADIO-3.
Step 8. While the Talkgroup Call is in
progress, set RADIO-1 back to the
VERSION #1.070 original talkgroup.
Step 9. Observe that RADIO-1 joins the

Talkgroup Call already in
progress.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. In the Unified Network Configurator

In Call User Alert (Disabled) Unified Network Wizard (UNCW), verify that In-Call
Configurator Wizard (UNCW) Parameters User Alert is disabled. Verify that
RADIO-1 and RADIO-2 have
Talkgroup Muting (VMUT)
1. DESCRIPTION disabled (Off) in the radios.
Step 2. Enable Talkgroup Muting (VMUT)

In-Call User Alert enhances the Call Alert feature to (Turn on) on RADIO-1.
allow Call Alerts to be received by radios that are
currently involved in voice and data services. As part Step 3. Verify that there is a visual
of this feature, the radio supports Talkgroup Muting indication on RADIO-1 that
where the radio user can mute all talkgroup voice Talkgroup Muting is enabled.
received by the radio. The Console Dispatcher or
another radio user can unmute the radio by sending Step 4. Initiate a talkgroup call on
the radio a Call Alert. TALKGROUP 1 from CONSOLE-
1.
Note: Talkgroup Muting is a programmable option in
the radio. There are also sub-options which will affect Step 5. Verify that no audio is heard by
the time and operation of the Talkgroup muting. RADIO-1 and that RADIO-1
SETUP Step 6. Send a Call Alert to RADIO-1 from

does not receive a Call Alert and
RADIO-1 - TALKGROUP 1 that RADIO-2 indicates failure of
RADIO-2 - TALKGROUP 2 Call Alert. End Console talkgroup
CONSOLE-1 - TALKGROUP 1 call.
Step 7. Send a Call Alert to RADIO-1 from

VERSION #1.050 CONSOLE-1. Accept the Call
Alert at RADIO-1 by pressing the
Home key.
Step 8. Initiate a talkgroup call on

TALKGROUP 1 from CONSOLE-
1.
Step 9. Verify that audio is now heard by

RADIO-1 and that RADIO-1
Step 10. End Console talkgroup call.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify/Set the Site Access Denial

Site Access Control/"Both" Site Access Flag to Both via the Unified
Denial (Single Site) Network Configurator Wizard
(UNCW).
1. DESCRIPTION Step 2. Cycle power to RADIO-1 and

RADIO-2 to force them to affiliate,
this will clear any site denials they
The Unified Network Configurator Wizard (UNCW)can may hold in memory.
be used to limit radio or talkgroup access to selected
valid sites. Control can be exercised to restrict radio Step 3. Verify/Set SITE 1 to be a valid site
users or talkgroups to certain sites, or to steer radio for RADIO-2 through the UCM.
activity away from smaller sites in an effort to avoid Set SITE 1 to be a non-valid site
busies. UNCW flags establish which sites are valid for for TALKGROUP 1 through the
each individual radio user, talkgroup and multigroup. UCM.
An overall Site Access Denial flag for the system
governs how these radio and talkgroup settings affect Step 4. Verify that RADIO-2 can affiliate to
the affiliation or rejection of radios to individual sites. SITE 1 since both TALKGROUP 1
Four possible values for the Site Access Denial flag and RADIO-2 records are not set
exist: Individual Only, Talkgroup Only, Either, or Both. as "non-valid" for SITE 1.
"Both" Site Access Denial indicates that a radio will not Step 5. Initiate a call from RADIO-2 on
be allowed to affiliate to a site only if both the radio TALKGROUP 1. Verify that
user and affiliated talkgroup do not have access to the RADIO-2 is not allowed to make
site. the call from SITE 1 since
TALKGROUP 1 is non-valid at
NOTE: Site Denial flags are not cleared from the SITE 1.
changed. Step 6. Set SITE 1 to be a non-valid site for
RADIO-2 through the UCM.
SETUP Step 7. Verify the updates complete using

the Schedule Manager.
RADIO-1 - TALKGROUP 1 Step 8. Verify that RADIO-2 cannot affiliate

RADIO-2 - TALKGROUP 1 to SITE 1 since both
TALKGROUP 1 and RADIO-2
records are set as "non-valid" for
VERSION #1.020 SITE 1. RADIO-2 will be "Out of
Range." (For Radios with the
display option this tet can be
displayed.)
Step 9. Reset all Talkgroup and Radio User

flags in the UNCW and the UCM,
approve the changes.
Step 10. Verify the updates complete

using the Schedule Manager.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Set up TALKGROUP 1's template to

Audio Interrupt/Interrupt Always Mode be Audio Interrupt Always through
the User Configuration Manager
(UCM).
1. DESCRIPTION
TALKGROUP 1.
A radio PTT request may be received for a group
already active and currently being sourced by another Step 3. Verify both RADIO-2 and 3 monitor
radio unit. The talkgroup can be flagged in the User the audio.
Configuration Manager (UCM) to either allow or
disallow the new PTT. If allowed, the latest PTT Step 4. Using RADIO-3, initiate a call on
request will be granted and become the source of the TALKGROUP 1.
call. If both Radios are at the same site, RF contention
may prevent either call from working. Step 5. Verify that RADIO-2 now listens to
RADIO-3.
Note: This test is not recommended for single site
systems as RF contention will occur. Step 6. Dekey both Radios.
SETUP
RADIO-3 - SITE - SITE 3 (SITE 2 if only 2 Sites)
Pass____ Fail____
VERSION #1.090

RFP# 101216
December 16, 2010


Site Access Control/"Talkgroup Only" Site Talkgroup Only via the Unified
Access Denial (Single Site) Network Configurator (UNCW).
1. DESCRIPTION Step 2. Verify that the change has

completed by checking the status
of the job that was created in the
The Unified Network Configurator (UNCW) can be Schedule Manager in the UNC.
used to limit radio or talkgroup access to selected valid The status should be
sites. Control can be exercised to restrict radio users "Completed".
or talkgroups to certain sites, or to steer radio activity
away from smaller sites in an effort to avoid busies. Step 3. Set SITE 1 to be a valid site for
User Configuration Manager (UCM) flags establish RADIO-2 through the UCM. Set
which sites are valid for each individual radio user, SITE 1 to be a non-valid site for
talkgroup and multigroup. An overall Site Access TALKGROUP 1 through the UCM
Denial flag for the system governs how these radio and distribute the update to the
and talkgroup settings affect the affiliation or rejection system.
of radios to individual sites. Four possible values for
the Site Access Denial flag exist: Individual Only, Step 4. Verify that RADIO-2 cannot affiliate
Talkgroup Only, Either, or Both. to SITE 1 since TALKGROUP 1 is
a non-valid talkgroup for SITE 2.
"Talkgroup (TG) Only" Site Access Denial dictates that RADIO-2 will display "Out of
a radio will not be allowed to affiliate to a particular site Range."
if its affiliated talkgroup does not have access to that
site. In this case, the individual radio user setting for Step 5. Set SITE 1 to be a valid site for
valid sites is not used in the determination of actual TALKGROUP 1 through the UCM.
site affiliation permissions. Set SITE 1 to be a non-valid site
for RADIO-2 through the UCM
NOTE: Site Denial flags are not cleared from the and distribute the update to the
subscriber until the power is cycled or the talkgroup is system. (The change must
changed. complete before the next step is
done.)
SETUP Step 6. Verify that RADIO-2 is now allowed

to affiliate to SITE 1 since the
talkgroup record determines site
access.
Step 7. Initiate a call from RADIO-2. Verify
that RADIO-2 is allowed to make
the call from SITE 1 since
TALKGROUP 1 is valid at SITE 1.
VERSION #1.010 Step 8. Return the Site Access Denial Flag
to "Both" and set SITE 1 to be a
valid site for RADIO-2. Distribute
the update to the system. (The
change should complete before
the next test is done.)
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that RADIO-1 is set to

Priority Monitor/Non-Priority Scan TALKGROUP 1 and in the scan
mode of operation and
programmed to scan
1. DESCRIPTION TALKGROUP 1, TALKGROUP 2,
and TALKGROUP 3.
This test will show that a subscriber unit can scan a Step 2. Initiate a Talkgroup Call with
pre-programmed list (in the radio) to find any Priority RADIO-4 and observe that
and Non-priority Talkgroups with assigned voice RADIO-1 scans to the talkgroup
channels at that site. To demonstrate this, a call will be and receives the call. Keep the
initiated from a portable at a remote site on a talkgroup call in progress until completion of
monitored by a portable at the same site as the the following step.
scanning radio. The scanning radio will scan from its
selected talkgroup to the active talkgroup. The test will Step 3. Initiate a Talkgroup Call with
be repeated with an additional radio transmitting on RADIO-2 and observe that
the Priority Talkgroup while the scanning radio is RADIO-1 does not receive the call
scanning. This third radio will be on a remote site with since RADIO-1 is listening to
a fourth radio on the Priority Talkgroup at the same TALKGROUP 3.
site as the scanning radio. Note: Subscribers must be
capable of supporting the Talkgroup scan.
SETUP
RADIO-1 - TALKGROUP 1 (SCANNING)

* RADIO-1 needs to be set to a dial position configured

to scan. Pass____ Fail____
VERSION #1.250

RFP# 101216
December 16, 2010

Step 1. Verify that MOBILE-1, MOBILE-2 &

Private Call using Mobile Subscribers MOBILE-3 are on the same
talkgroup by initiating a group call
between the 3 units.
1. DESCRIPTION
Step 2. Initiate a private call from MOBILE-1
to MOBILE-2. The display shows
Private Call is a selective calling feature that allows a that the subscriber is in the private
dispatcher or radio user to carry on one-to-one mode and the last ID called is
conversation that is only heard by the 2 parties displayed.
involved. Subscriber units receiving a private call will
sound an alert tone. As with other types of calls, Step 3. Verify MOBILE-1 is engaged in a
Private Calls can take place from anywhere in the private call with MOBILE-2. Verify
system. MOBILE-3 does not hear any
This test will show Private Call functionality using a audio.
Mobile Unit.
Step 4. Terminate the private call.
SETUP Step 5. The private call is terminated after

the hang timer expires.
MOBILE-1 - TALKGROUP 1
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a Wide Area Call with

Talkgroup Call RADIO-1 in TALKGROUP 1.

call.
The Talkgroup is the primary level of organization for Step 3. Initiate a Wide Area Call with
communications on a trunked radio system. Radios RADIO-3 in TALKGROUP 2.
with Talkgroup call capability will be able to
communicate with other members of the same Step 4. Observe that only RADIO-4 will be
Talkgroup. This provides the effect of a private able to monitor and respond the
channel down to the Talkgroup level. This test will call.
demonstrate that a Talkgroup transmission initiated by
a radio user will only be heard by system users, which
have, the same Talkgroup selected. As with other
types of calls, Talkgroup calls can take place from
anywhere in the system.
SETUP
Pass____ Fail____
VERSION #1.140

RFP# 101216
December 16, 2010

Step 1. Verify ATG 1 is set for the Interrupt

Multigroup Call in Interrupt Mode mode in the UCM database.

1. DESCRIPTION TALKGROUP 1.
Step 3. While RADIO-1 is keyed, initiate a

This trunking feature allows an equipped radio user to multigroup call using RADIO-4 on
transmit an announcement to several different ATG 1. Verify RADIO-2 receives
talkgroups simultaneously. The multigroup (MG) call the call but RADIO-3 does not
can be flagged for Interrupt Mode in the User unmute.
Configuration Manager (UCM) database, this means
that the trunked system does not wait for attached Step 4. Dekey RADIO-1 and verify RADIO-1
talkgroups to finish calls in progress. Upon dekeying, unmutes and joins the multigroup
the interrupted radios will join the multigroup call in call in progress.
progress. As with other types of calls, multigroup calls
can take place from anywhere in the system.
NOTE: A receiver interference failure may appear if

RADIO-1 is not immediately dekeyed. This test is not
recommended for single site systems as RF
contention will occur.
SETUP
RADIO-2 - SITE - SITE 1 Pass____ Fail____
RADIO-3 - RANDOM (Not part of MG)
RADIO-4 - ATG 1

ATG 1.

VERSION #1.160

RFP# 101216
December 16, 2010

Step 1. Initiate a secure wide area call with

Secure Operation RADIO-1 on TALKGROUP 1.
Keep this call in progress until
instructed to end the call.
1. DESCRIPTION
Step 2. Observe that RADIO-2 will be able
to monitor the call.
Digital encryption is used to scramble a transmission
so only properly equipped and configured radios can Step 3. Observe that RADIO-3 does not
monitor the conversation. A "Key" is used to encrypt receive the call.
the transmit audio. Only radios with the same "Key"
can decrypt the audio and listen to it. Step 4. Observe that RADIO-4 will also
receive the call even with the
secure switch set to the non-
SETUP secure mode of operation.
Step 5. End the call from RADIO-1.

RADIO-1 - TALKGROUP 1 (SECURE TX MODE)
RADIO-2 - TALKGROUP 1 (SECURE TX MODE) Step 6. Respond with RADIO-2 and verify
RADIO-3 - TALKGROUP 1 (SECURE MODE and no, that RADIO-1 receives the
or incorrect key) response audio but RADIO-3
RADIO-4 - TALKGROUP 1 (Clear TX Mode) cannot.
Note: The identical secure mode must be programmed

into RADIO-1, RADIO-2, RADIO-4 and that RADIO-3
has no secure code loaded or has a unique secure
code from the other testing radios.
VERSION #1.130
Pass____ Fail____

RFP# 101216
December 16, 2010


Busy Queuing and Callback with Ten all channels at SITE 1 with the
Talkgroup Priority Levels exception of the control channel
1. DESCRIPTION Step 2. Verify the priority level for

TALKGROUP 4's template is set
up through the User Configuration
If no voice channel resources are available, radios Manager (UCM) as "9".
requesting channels for new conversations are placed
in a queue. Users of the same priority will move Step 3. Verify that the priority level for
through the queue in a FIFO (first in, first out) TALKGROUP 1, and
sequence; however, users of higher priority will be TALKGROUP 3 are set up in the
inserted ahead of lower priority users in queue. UCM as "10".
the top of the busy queue gets a channel assignment Step 4. Initiate a Talkgroup Call with
and generates a callback tone. The callback tone RADIO-1. Keep this call in
alerts the user that a channel assignment was made progress until instructed to end
and transmitting is now possible on the selected the call.
talkgroup.
Step 5. Key RADIO-3 and observe that the
Note: An Emergency Call has the highest priority at radio receives a busy. Then key
level 1. The highest assignable priority is 2 and 10 is RADIO-2 and observe that the
the lowest. radio receives a busy.
Step 6. End the Talkgroup Call established

SETUP in Step 3.
Step 7. Observe RADIO-2 receives the first

RADIO-1 - TALKGROUP 1 callback and can now make a call
RADIO-1 - SITE - SITE 1 to RADIO-4 upon receipt of the
RADIO-2 - TALKGROUP 4 callback indication.
RADIO-3 - TALKGROUP 3 Step 8. End the call between RADIO-2 and
RADIO-3 - SITE - SITE 1 RADIO-4.
RADIO-4 - SITE - SITE 2 Step 9. Observe RADIO-3 now receives a
callback and can make a call upon
receipt of the callback indication.
VERSION #1.010
original settings.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, press the page

Call Alert (Single Site) button.

location where this ID is stored
Call Alert is a tone page that allows a user to Step 3. Press the PTT to initiate the call
selectively alert another radio unit. The initiating radio alert (Page). Verify that the
will receive notification from the trunked system as to RADIO-1 user receives audible
whether or not the page was received by the target indication that the Call Alert
radio. Units receiving a Call Alert will sound an alert (Page) was sent.
tone. As with other types of calls, Call Alerts can take
place from anywhere in the system. Step 4. Verify that RADIO-2 user receives
an audible indication of an
incoming Call Alert (Page) was
SETUP sent but RADIO-3 does not.
Step 5. Verify RADIO-1 gets an audible

RADIO-1 - TALKGROUP 1 indication that the Call Alert
RADIO-2 - TALKGROUP 2 (Page) was successfully received
RADIO-3 - TALKGROUP 2 at the target radio.
Step 6. Turn off RADIO-2. Send a Call Alert

VERSION #1.060 (Page) from RADIO-1 to RADIO-
2.
Step 7. Verify that the RADIO-1 user

receives audible indication that
the Call Alert (Page) was sent.
Step 8. Verify RADIO-1 receives an

indication that the Call Alert
(Page) was not successfully
received at the target radio.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Ensure that the priority level for all

Recent User Priority talkgroups is the same. Simulate a
busy system by disabling all
channels at SITE 1 with the
1. DESCRIPTION exception of the control channel
This test verifies that a recent user of the channel has Step 2. Press and hold the PTT switch of
priority over other users of equal priority of being RADIO-1.
assigned a channel when a busy queue exists. The
maximum number of consecutive times that a user Step 3. Press the PTT switch on RADIO-2.
may be elevated to recent user priority is two. Verify that the radio receives a
busy tone.
Note: Timing is critical for this test, it is recommended
that the test be read through and understood before Step 4. Press the PTT switch on RADIO-3.
attempting to complete. Verify that the radio receives a
busy tone.
SETUP Step 5. Release the PTT switch on RADIO-

1.
RADIO-1 - TALKGROUP 1 Step 6. As soon as RADIO-2 receives its

RADIO-1 - SITE - SITE 1 callback tone, press and hold its
RADIO-2 - TALKGROUP 2 PTT switch.
RADIO-3 - TALKGROUP 3 Step 7. Within 2 seconds of callback, re-key
RADIO-3 - SITE - SITE 1 RADIO-1. Verify that RADIO-1
receives a busy tone. Release the
PTT switch on RADIO-1.
VERSION #1.230
Step 8. Release the PTT switch on RADIO-
2. Verify that RADIO-1 receives a
callback tone before RADIO-3.
Step 9. Repeat Steps 2-8. Verify that the

priority of RADIO-1 is once more
elevated in the busy queue.
Step 10. Repeat Steps 2-8 once

more. Verify that in Step 9 that
RADIO-3 receives the callback
tone since RADIO-1 cannot be
elevated in the busy queue more
than two consecutive times.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, press the Private

Private Call (Single Site) Call (Call) button.

location where this ID is stored.
Private Call is a selective calling feature that allows a Step 3. Press the PTT to initiate the Private
dispatcher or radio user to carry on one-to-one Call (Call).
conversation that is only heard by the 2 parties
involved. Subscriber units receiving a private call will Step 4. Verify that RADIO-2 hears tones
sound an alert tone. As with other types of calls, and the display indicates that a
Private Calls can take place from anywhere in the Private Call (Call) has been
system. received, but RADIO-3 receives
no indications.
SETUP Step 5. Answer the Private Call (Call) at

RADIO-2 by pressing the Private
Call (Call) button. If RADIO-2 has
RADIO-1 - TALKGROUP 1 a display, verify it shows the ID
RADIO-2 - TALKGROUP 2 number or alias of RADIO-1.
Step 6. Press the PTT switch on RADIO-2
and respond to the Private Call
VERSION #1.090 (Call). Note that if you do not
press the Private Call (Call) button
before pressing PTT, your audio
will be heard by all members of
the talkgroup, and not just by the
radio initiating the Private Call
(Call).
Step 7. Verify that RADIO-2 can

communicate with RADIO-1.

monitor the Private Call.
Step 9. End the Private Call (Call) by

pressing the Private Call (Call)
button or the Home button to
return to normal talkgroup
operation.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that TALKGROUP 1 is set up

Sub-band Restricted Operation (Single Site) in the User Configuration Manager
(UCM) to be a sub-band restricted
talkgroup.
1. DESCRIPTION
Step 2. Verify TALKGROUP 2 is set up in
the UCM to be a non-sub-band
This feature will allow radios limited to one sub-band to restricted talkgroup.
operate at sites set up with resources to handle both
sub-band and full band range radios. Step 3. Using RADIO-1, initiate a call on
TALKGROUP 1.
SETUP Step 4. Verify that a sub-band restricted

and that only RADIO-3 is able to
RADIO-1 - TALKGROUP 1 monitor and respond to the call.
RADIO-2 - TALKGROUP 2 Step 5. Dekey RADIO-1.
RADIO-3 - TALKGROUP 1 Step 6. Using RADIO-2, initiate a call on
RADIO-4 - SITE - SITE 1 Step 7. Verify that a non-sub-band restricted
* SITE 1 should support sub-band channels. and that only RADIO-4 is able to
monitor and respond to the call.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. The emergency type for

Emergency Alarm and Call with Top of Queue TALKGROUP 1's template must
(Single Site) be set up through the User
Configuration Manager (UCM) as
Top of Queue.
1. DESCRIPTION
Users in life threatening situations can use the exception of the control channel
Emergency button on the radio to immediately send a and one voice channel.
signal to the dispatcher and be assigned the next
available voice channel. An Emergency Call can be Step 3. Press the PTT to initiate a call with
set to either Top of Queue or Ruthless Preemption RADIO-3 and hold the PTT switch
operation. During an emergency call the Emergency until instructed to release.
ID will appear on the display of the subscribers. To
demonstrate this, an Emergency Alarm and Call will be Step 4. Key RADIO-4 and verify the radio
initiated from a portable which will be received by a receives a busy tone. Release
portable, on the same talkgroup, affiliated at the same the PTT switch on RADIO-4.
site of any zone in the system.
NOTE : If the subscriber does not have the Display Call by depressing the emergency
option, the Emergency ID will not be displayed. switch and then the PTT switch.
NOTE: All radios and talkgroups should start with Step 6. Observe that RADIO-1 cannot
default priorities. Default is 10. transmit due to the voice channel
being busy.
SETUP Step 7. Release the PTT switch on RADIO-

3.
RADIO-1 - TALKGROUP 1 Step 8. Observe that RADIO-1 receives the

RADIO-2 - TALKGROUP 1 call back before RADIO-4 and is
RADIO-3 - TALKGROUP 2 able to proceed with the call.
RADIO-4 - TALKGROUP 3 Observe that the display on
RADIO-2 denotes an emergency
and the unit ID or alias of RADIO-
VERSION #1.170 1.
Step 9. Dekey RADIO-1 and end the

Emergency Call by holding down
the Emergency button on RADIO-
1 until an alert tone sounds.
Verify RADIO-1 returns to normal
operation and that RADIO-4

original settings.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify TALKGROUP 1's template is

All Start Talkgroups setup as an All Start Talkgroup in
the User Configuration Manager
(UCM).
1. DESCRIPTION
Talkgroups can be set up as either All Start or Fast exception of the control channel
Start. and one voice channel.
"AllStart" is the default Talkgroup Call setup approach
that requires that all sites with affiliated talkgroup Step 3. Key RADIO-3 and busy out the only
members and other required resources be available voice channel available at SITE 1
before the call begins. Otherwise, the system returns where RADIO-2 and RADIO-3 are
a busy response to the subscriber who initiated the affiliated.
Talkgroup Call. Once the required resources become
available, the call is granted. Step 4. Initiate a Talkgroup Call from
RADIO-1 and observe a busy
NOTE: This feature test only works on a multi-site indication is received due to no
system. available voice channel at SITE 1
where RADIO-2 is affiliated.
SETUP Step 5. Dekey RADIO-3. Verify that the call

from RADIO-1 is now granted and
RADIO-2 can hear the audio.
RADIO-1 - SITE - SITE 2 Step 6. Return the system to the original
RADIO-2 - TALKGROUP 1 settings.
VERSION #1.140
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that TALKGROUP 1's

Fast Start Talkgroup without Critical Site template is set up as Fast Start
Manager (UCM) with no critical
1. DESCRIPTION sites specified.

Talkgroups can be set up as either All Start or Fast all channels at SITE 1 with the
Start. exception of the control channel
"FastStart" is the Talkgroup Call setup approach that
allows a group call setup whether or not all affiliated Step 3. Key RADIO-3 and busy out the only
Talkgroup members are available. This "Automatic voice channel available at SITE 1.
Busy Override by Talkgroup" call setup method still
requires the participation of all affiliated consoles, Step 4. Initiate a Talkgroup Call from
LOMIs (i.e. logging recorders) and critical sites before RADIO-1 and observe the call is
the call can begin. As channels at the affiliated granted even with no voice
talkgroup members' sites become available, they are channel available at SITE 2 for
added to the call in progress. RADIO-2.
NOTE: This feature test only works on a multi-site Step 5. Dekey RADIO-3. Verify that RADIO-
system. 2 can now hear RADIO-1.
Step 6. Return the system to the original

SETUP settings.
VERSION #1.120
Pass____ Fail____

RFP# 101216
December 16, 2010

6.1 MCC 7500 Features

RFP# 101216
December 16, 2010

MCC 7500 Features VERSION #1.030
2. TEST
Individual Tone Pages (Mixed Resources -
Sequential) Step 1. Verify communications on
TALKGROUP 1 and
TALKGROUP 2 by setting up
1. DESCRIPTION voice calls between the Radio and
Console on each TG separately.
A Tone Page is an audio alert typically sent to alert the Step 2. Create a list of tone pages through
user. Tone page is also sent to a device to issue a the standard paging interface on
control message. A tone page can be sent to Trunked CONSOLE-3 Elite interface. Keep
Group or Analog Conventional resource. the order of the pages to be
The user interface allows for issuing an individual page TALKGROUP 1TonePage1,
and a group of individual pages. TALKGROUP 2TonePage1,
The sequential mode refers to the configured paging TALKGROUP 2 TonePage2.
mechanism where console sends pages sequentially
on different resources. Pages on a same resource are Step 3. Press "Send" and Verify that the first
sent as sequential pages in the order in which the page on each resource in the
pages appear in the paging queue. queue is sent on TALKGROUP 1
A pre-configured group page representing a set of and then the second page is sent
individual pages is invoked via the console user on TALKGROUP 2.
interface to issue a simultaneous tone pages.
Tone Page can be sent over both a trunking talkgroup Step 4. Verify that RADIO-1 and RADIO-2
and a conventional channel. For the purpose of received tone pages on
testing at CCSi, testing will be done over a trunking TALKGROUP 1 and
talkgroup only since a conventional resource is not TALKGROUP 2 respectively.
available.
SETUP
RADIO-3 - CCH1
RADIO-4 - CCH2
CONSOLE-1 - TALKGROUP 1, CCH1
CONSOLE-2 - TALKGROUP 2, CCH2
CONSOLE-3 - TALKGROUP 1, TALKGROUP
2,TALKGROUP 3, CCH2
Note: The Console should be setup for sequential
paging mode through the network management. The Pass____ Fail____
individual tone pages on TALKGROUP 1 with
TALKGROUP 1TonePage1 alias, Quick Call I Paging
Format, TALKGROUP 2 with TALKGROUP
2TonePage1 alias, Quick Call I Paging Format,
TALKGROUP 1 with TALKGROUP 2TonePage2 alias,
Quick Call II Paging Format.

RFP# 101216
December 16, 2010

MCC 7500 Features 2. TEST
Step 1. Send an Alert tone from CONSOLE-

Tone Generation Trunking Resource (MCC 1
7500 Consoles)
Step 2. Verify that RADIO-1 hears Alert tone
from CONSOLE-1
1. DESCRIPTION
Step 3. Key up general transmit by using
Console-1's mike or foot switch
This test will demonstrate that the dispatch console is
able to transmit Alt-Tone on a trunking resource during Step 4. Verify that RADIO-1 hears audio
the tone generation period. from CONSOLE-1 during the Alert
Tone Talk Extend period.
SETUP
SITE-1 - ZONE 1
CONSOLE-1 -TALKGROUP 1
CONSOLE-1 - SITE - CSITE 1
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate an analog conventional

Transmission on IP-based Analog transmission from CONSOLE-1
Conventional Voice Channel - Relay Keying on frequency F1 on CONVCH1.
Step 2. Observe that RADIO-1, RADIO-2

1. DESCRIPTION and CONSOLE-2 hear
CONSOLE-1.
The IP-based analog conventional feature provides Step 3. Observe that CONSOLE-2 indicates
radio users /dispatchers capability to communicate the presence of transmission on
with other radio users /dispatchers listening to the the channel (transmit busy
channel. This test will demonstrate the MCC 7500 indication).
dispatcher can communicate to other radios and MCC
7500 dispatchers who are listening to the channel.
SETUP
An operational CCGW with an analog conventional

channel (CONVCH1) configured (via NM) to use relay
(M-Lead) to key up the station. Note that the attached
repeater/BS must be appropriately configured to work
with an M-Lead. The BS is tuned to F1
transmit/receive pair.
RADIO-1 - CONVCH1
RADIO-2 - CONVCH1
CONSOLE-1 - CONVCH1 Pass____ Fail____

CONSOLE-2 - CONVCH1
VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. At CONSOLE-1 select one of the

Multi-Select/APB Multi-Select tabs in the
Patch/Multi-Select window.
1. DESCRIPTION Step 2. Click the button on the Multi-Select

that allows an operator to setup
and edit a multiselect (note: MSEL
Multi-Select (MSEL) allows a dispatcher to merge window turns green).
several talkgroups together on one voice channel to
participate in a single conversation. This can be used Step 3. Add TALKGROUP 1, TALKGROUP
for announcements to two or more channels or 2, TALKGROUP 3 and
talkgroups for general broadcast purposes. TALKGROUP 4 to the Multi-Select
by selecting each resource tile.
Using the Multi-Select feature, the console operator
can talk and listen to all of the selected talkgroups Step 4. Once the talkgroups are added click
grouped; however, the members of the individual the Multi-Select Setup button
talkgroups cannot talk or listen to members of other again to complete the Multi-Select
talkgroups. Multi-selected talkgroups still only setup.
communicate with the console dispatcher and other
members in the same talkgroup. A predefined multi- Step 5. Initiate a call from CONSOLE-1
select configuration can be saved by the console using the APB Transmit and
operator as an All Points Bulletin (APB) for quick observe that all radios are able to
broadcast-type transmissions by the dispatcher. receive the call. Also via
ZoneWatch (if available) verify
NOTE : If "secure" and "clear" resources are multi- that only one RF resource is
selected, one repeater for each mode may be assigned at any site where
assigned per site. multiple radios are affiliated. (See
note)
SETUP Step 6. Remove all talkgroups from the

Multi-Select.
CONSOLE-1 - TALKGROUP 1, TALKGROUP 2,
TALKGROUP 3 and TALKGROUP 4
Pass____ Fail____
VERSION #1.090

RFP# 101216
December 16, 2010

Step 1. Select the "PRIVATE-CALL" tile and

Console Initiates / Receives Secure Private set to the secure mode at
Call CONSOLE-1.
Step 2. Click the button on the tile that

1. DESCRIPTION provides the Private Call function.
Step 3. Select the numeric keypad and

Private Conversation is a selective calling feature that using the displayed keypad enter
allows a dispatcher or radio user to carry on one-to- the unit ID for RADIO-1.
one conversation that is heard only by the two parties
involved. The test validates the ability to Step 4. Click the Send button.
initiate/receive secure private calls by the
Console/Radio. Step 5. Answer the Private Call using the
menu "CALL" selection or the
programmed button for Private
SETUP Call and respond to CONSOLE-1.
Step 6. Verify that audio can be heard on

RADIO-1 - TALKGROUP 1 both ends.
CONSOLE-1 (w/Private Call) Step 7. After completing the Private Call,
return to the normal talkgroup
mode.
VERSION #1.090
Step 8. PTT RADIO-1 to initiate Private
Calling (PC) ring sequence to
CONSOLE-1 in secure transmit
mode. Answer PC ring on
CONSOLE-1 and establish audio
conversation between RADIO-1
and CONSOLE-1.
Step 9. Verify that audio can be heard on

both ends.
Step 10. Exit Private Call on RADIO-

1 and CONSOLE-1.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate PTT from RADIO-1 on

Radio Transmission on IP-based Analog CCH1.
Conventional Voice Channel - COR
Step 2. Observe that RADIO-2, CONSOLE-
1 and CONSOLE-2 hear RADIO-
1. DESCRIPTION 1.
Step 3. Observe that CONSOLE-1 and

The IP-based analog conventional feature provides CONSOLE-2 indicate the inbound
radio users/dispatchers capability to communicate audio on the channel.
with other radio users/dispatchers listening to the
analog conventional voice channel. This test will Step 4. Release RADIO-1 PTT.
demonstrate the radio user can use the known
frequency of the channel to communicate to other Step 5. Verify RADIO-2, CONSOLE-1 and
radios and dispatchers listening to the channel. CONSOLE-2 no longer hear
RADIO-1. CONSOLE-1 and
CONSOLE-2 no longer indicate
SETUP inbound transmission on the
channel.

channel (CCH1) configured (via NM) to use relay (E-
Lead/COR) mode to receive communication from the
BS. Note that the attached repeater/BS must be
appropriately configured in COR mode of operation in
order to communicate with the CCGW. The BS is
tuned to F1 transmit/receive pair.
Two radios (RADIO-1, RADIO-2) tuned to the transmit

frequency of the conventional voice channel (CCH1),
and two MCC 7500 console sites with CONSOLE-1
and CONSOLE-2 respectively are affiliated to CCH1.
Pass____ Fail____
VERSION #1.020

RFP# 101216
December 16, 2010

Step 1. Initiate PTT from RADIO-1 on

Radio Transmission on IP-based Analog CCH1.
Conventional Voice Channel - VOX
Step 2. Observe that RADIO-2, CONSOLE-
1 and CONSOLE-2 hear RADIO-
1. DESCRIPTION 1.
Step 3. Observe the CONSOLE-1 and

The IP-based analog conventional feature provides CONSOLE-2 indicate the inbound
radio users/dispatchers capability to communicate audio on the channel.
with other radio users/dispatchers listening to the
analog conventional voice channel. This test will Step 4. Release RADIO-1 PTT.
demonstrate the radio user can use the known
frequency of the channel to communicate to other Step 5. Verify RADIO-2, CONSOLE-1 and
radios and dispatchers listening to the channel. CONSOLE-2 no longer hear
RADIO-1. CONSOLE-1 and
CONSOLE-2 no longer indicate
SETUP inbound transmission on the
channel

channel (CCH1) configured (via NM) to use VOX
mode to receive communication from the BS. The BS
is tuned to F1 transmit/receive pair.
Two radios (RADIO-1, RADIO-2) tuned to the transmit

frequency of the conventional voice channel (CCH1),
and two MCC 7500 console sites with CONSOLE-1
and CONSOLE-2 respectively are affiliated to CCH1.
VERSION #1.020
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select the "PRIVATE-CALL" tile at

MCC 7500 Console Initiated Private Call to a CONSOLE-1.
MCC 7500 Console
provides the Private Call function.
1. DESCRIPTION
Step 3. Select the numeric keypad.
Private Conversation is a selective calling feature that Step 4. Using the displayed keypad enter
allows a dispatcher or radio user to carry on one-to- the unit ID to be Private Called
one conversation that is heard only by the two parties (CONSOLE-2) or select
involved. Subscriber units receiving a private call will CONSOLE-2 from the drop down
sound an alert tone. As with other call types, Private list (if listed).
Calls operate across sites as well as within the same
site. MCC 7500 Console can use the feature to Step 5. Click the Send button.
communicate with another MCC 7500 Console in the
same or another Console Site. Step 6. At CONSOLE-2, answer the Private
Private call between the two Consoles is supported for Call from CONSOLE-1 and verify
MCC 7500 Consoles only. that CONSOLE-2 is able to hear
the CONSOLE-1 audio. Also
verify that the CONSOLE-1 can
SETUP hear the CONSOLE-2 audio.
Step 7. Verify that RADIO-1 and

RADIO-1 - TALKGROUP 1 CONSOLE-3 do not hear the
RADIO-1 - SITE - SITE 1 audio for the Private Call.
CONSOLE-1 - CSITE - CSITE 1
CONSOLE-2 - CSITE - CSITE 2 Step 8. Verify using ZoneWatch (if
CONSOLE-3 - CSITE - CSITE 2 available) that no site resources
are used as this is an IP based
call from Console user to Console
VERSION #1.060 user.
Step 9. After completing the Private Call,

return to the normal talkgroup
mode.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Put RADIO-1 into Remote Monitor

Remote Monitor via the Remote Monitor tile on the
CONSOLE-1.
1. DESCRIPTION Step 2. Verify that RADIO-1 keys up without

any transmit indication.
Remote Monitor from Console is a call type in which Step 3. Verify any audio is heard by RADIO-
the console operator can select and remotely key a 2 and CONSOLE-1.
subscriber unit. This allows the dispatcher to monitor
the transmit audio remotely and without detection. This Step 4. Wait 30 seconds and verify that
feature is useful in situations where the subscriber unit RADIO-1 dekeys.
has been stolen, or there is a need to determine if the
radio user is incapacitated and cannot activate a PTT
(i.e. an officer has been injured or is under duress).
The radio being monitored will not show any sign of
being keyed up. This test can be run in secure or clear
mode on a trunked 9600 or 3600 site.
SETUP
Pass____ Fail____
VERSION #1.070

RFP# 101216
December 16, 2010

Step 1. Verify communications between the

Cross Mute - Mute Dispatcher Audio on a CONSOLE-1 and the RADIO-1 on
Channel (MCC 7500 Consoles Only) CCH1 and CONSOLE-2 and
RADIO-2 on CCH2 separately.
1. DESCRIPTION Step 2. Initiate instant transmission from

CONSOLE-1 on CCH1.
The inbound audio on a conventional channel is muted Step 3. Verify that RADIO-1 hears the
at a dispatch position that is receiving audio on a CONSOLE-1.
transmitting channel with overlapping RF coverage as
the muted channel. This is to prevent potential audio Step 4. Verify that CONSOLE-2 receives
distortion/echoing due to duplicated audio. the inbound transmission
indication on a CCH2 of a radio
transmission due to CONSOLE-1
SETUP transmission on CCH1.
Step 5. Verify that CONSOLE-2 does not

Set two analog conventional channels, CCH1 and receive audio of the inbound
CCH2 to the frequency F1. transmission on CCH2.
RADIO-1- CCH1
RADIO-2 - CCH2
CONSOLE-1 CCH1
CONSOLE-2 CCH2
Note: The channels CCH1 on F1 and CCH2 on F1 are

configured (via Network Management) to be RF Cross
Mute coupled.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From CONSOLE-1 create a paging

Tone Paging - Conventional queue containing paging tones.
Step 2. From CONSOLE-1 start the pages

1. DESCRIPTION on - CONVCH 1
Step 3. Verify that the tones are transmitted

This test verifies that an MCC7500 console using a and received in on CONVCH1.
Conventional channel is able to transmit tone pages
without using an external paging tone generator. This
test can be run using Digital Conventional, Mixed
Mode or MDC1200 Channels.
SETUP
RADIO-1 - SITE 1 - CONVCH 1
CONSOLE-1 - CONVCH 1
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify communications between the

Channel Marker - Trunked Channels (MCC Consoles and the Radios on
7500 Consoles Only) TALKGROUP 1
Step 2. Initiate a Channel Marker tone on

1. DESCRIPTION TALKGROUP 1 from CONSOLE-
1.
A Channel Marker is a distinct, short duration, audible Step 3. Verify that RADIO-1 and RADIO-2
tone over radio and Console speakers. The tone is can monitor the Channel Marker
initiated and cancelled by a console operator. tone at TALKGROUP 1 preset
period.
The tone can be initiated only for the talkgroups or
analog conventional channels. On initiation, it is Step 4. Verify that CONSOLE-1 and
generated periodically when there is no voice activity. CONSOLE-2 can also monitor the
Channel Marker tone at
The tone can be used for various purposes. The TALKGROUP 1 preset period.
primary purpose of the tone is to inform radio users
that the conventional channel or the trunked talkgroup Step 5. Initiate a call from RADIO-1 and
is currently involved in a high priority situation and they continue to key longer than the
should stay off the channel unless they are involved in preset Channel Marker tone
the high priority situation. The tone also informs the period for TALKGROUP 1
users that a console operator is actively monitoring the
talkgroup. Step 6. Verify that while RADIO-1 is keyed,
the Channel Marker tone is
Note that the Channel Marker tone will only start when suppressed.
there is no voice activity for the selected
Talkgroup/Analog conventional channel. Step 7. Verify that after RADIO-1 de-keys,
the periodic Channel Marker tone
The channel Marker tone is sent in a current continues to be transmitted on
transmission mode of the Console user. TALKGROUP 1
Step 8. Cancel the Channel Marker on

SETUP TALKGROUP 1 from CONSOLE-
1.
RADIO-1 TALKGROUP 1
RADIO-2 TALKGROUP 1 Step 9. Verify the Channel Marker is no
longer monitored on
CONSOLE-1 - TALKGROUP 1 TALKGROUP 1
Note: Verify that TALKGROUP 1 has Channel Marker

capability
Pass____ Fail____
VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. Initiate a wide area call from

Talkgroup Selection and Call CONSOLE-1 on TALKGROUP 1.
Step 2. Observe that RADIO-1 and RADIO-

1. DESCRIPTION 3 will be able to monitor the call.
Dekey the console and have
either radio respond to the call.
The Talkgroup Call is the primary level of organization
for communications on a trunked radio system. Step 3. Observe that all Consoles with
Dispatchers with Talkgroup Call capability will be able TALKGROUP 1 can monitor both
to communicate with other members of the same sides of the conversation.
talkgroup. This provides the effect of an assigned
channel down to the talkgroup level. When a Step 4. Initiate a wide area call from
Talkgroup Call is initiated from a subscriber unit, the CONSOLE-2 on TALKGROUP 2.
call is indicated on each dispatch operator position that
has a channel control resource associated with the Step 5. Observe that RADIO-2 and RADIO-
unit's channel/talkgroup. 4 will be able to monitor the call.
Dekey the console and have
either radio respond to the call.
SETUP
Step 6. Observe that all Consoles with
TALKGROUP 2 can monitor both
RADIO-1 - TALKGROUP 1 sides of the conversation.
VERSION #1.100 Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Place an outbound analog mode call

Inbound and Outbound Calls - Conventional on CONSOLE-1 using CONVCH 1
Mixed Mode resource.
Step 2. Verify voice is audible on RADIO-1

1. DESCRIPTION and that no ID or alias is provided.
Step 3. Place an inbound analog mode call

This test verifies the capability to make and receive using RADIO-1 on CONVCH 1
calls on a radio using a Conventional Mixed Mode
channel. Use the console’s transmit mode select to Step 4. Verify that voice is audible at
switch between analog and digital modes. CONSOLE-1 and that no ID or
alias is provided (the console
displays “Unknown”).
SETUP
Step 5. Place an outbound digital mode call
on CONSOLE-1 using CONVCH 1
RADIO-1 – CONVCH 1 resource.
CONVCH 1 - MIXED MODE Step 6. Verify voice is audible on RADIO-1

and that the ID or alias is
CONSOLE-1 - CONVCH 1 provided.
Step 7. Place an inbound digital mode call

VERSION #1.000 using RADIO-1 on CONVCH 1
Step 8. Verify that voice is audible at

CONSOLE-1 and that the ID or
alias is provided.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a analog conventional Call

Link Failure between CCGW and Zone with RADIO-1 on CCH1.
Controller (MCC 7500 System only)
Step 2. Observe that only CONSOLE-1 and
CONSOLE-2 will be able to
1. DESCRIPTION monitor and respond to the call.
Step 3. Initiate an analog conventional call

This test verifies that the two communication paths with RADIO-2 on CCH2.
between the CCGW and Zone Controller (ZC) are
redundant and the system will continue uninterrupted if Step 4. Observe that only CONSOLE-1and
the main path fails. To accomplish this, a NIC CONSOLE-2 will be able to
connection is removed at the ZC. monitor and respond to the call.
Step 5. Remove one ENET cable to Link1

SETUP from the NIC on the ZC, this will
simulate a Zone Controller to
Console Site Link failure.
RADIO-1 - CCH1
RADIO-2 - CCH2 Step 6. Observe that the calls on CCH1 and
This test requires an operational system with a CCGW CCH2 continue.
with CCH1 and CCH2 and MCC 7500 Console Site
with CONSOLE-1 and CONSOLE-2. CONSOLE-1 and Step 7. Repeat steps 1-6 for the other Zone
CONSOLE-2 are affiliated to CCH1 and CCH2. Controller.
Step 8. Connect the ENET cables to

VERSION #1.020 normalize the system.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using a shorting wire, simulate a

Alarm Input / Outputs (Aux I/O Option) relay closure on an input via the
punch block.
1. DESCRIPTION Step 2. Verify that CONSOLE-1 momentary

input displays the icon designated
for an ON_STATE.
The alarm inputs of the Aux I/O can be connected to
almost any device that requires or can detect a relay Step 3. Remove the shorting wire and verify
closure. These signals can be simulated and that CONSOLE-1 displays the
monitored in the factory. icon designated for an
OFF_STATE.
SETUP Step 4. Connect the meter to the pins to

monitor a relay output.
Connect a multi-meter capable of monitoring closures Step 5. Verify that the meter reads an open
to the proper pins of the punch block cabled to the Aux circuit.
I/O. One momentatry input and one momentary output
should be configured on at least one MCC 7500 Step 6. Depress the momentary input button
console. on the console to initiate a relay
CONSOLE-1 - TALKGROUP 1 closure.
CONSOLE-1 - SITE - CONSITE 1
Aux I/O punch block pinout: Step 7. Verify that the meter displays a
closed circuit.
Aux I/O 1 - pins 26,1
VERSION #1.010
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate an analog conventional

Transmission on IP-based Analog transmission from CONSOLE-1
Conventional Voice Channel - Tone Remote on frequency F2 on CCH1.
Control (TRC)
Step 2. Observe that RADIO-1, RADIO-2
and CONSOLE-2 hear
1. DESCRIPTION CONSOLE-1.
Step 3. Verify that CONSOLE-2 indicates

The IP-based analog conventional feature provides the presence of transmission on
radio users /dispatchers capability to communicate the channel (transmit busy
with other radio users /dispatchers listening to the indication).
channel. This test will demonstrate the MCC 7500
dispatcher can communicate to other radios and MCC
7500 dispatchers who are listening to the channel.
SETUP

channel (CCH1) configured (via NM) to use TRC to
key up the station. Note that the attached repeater/BS
must be appropriately configured to work with TRC.
The BS is tuned to F1 transmit/receive pair.
This test requires two radios (RADIO-1, RADIO-2)
tuned to the transmit frequency of the conventional
voice channel (CCH1). Two MCC 7500 Consoles
CONSOLE-1 and CONSOLE-2, respectively. The
CONSOLE-1 and CONSOLE-2 are both affiliated to Pass____ Fail____
the CCH1.
VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. Initiate a Talkgroup call from

Console Priority RADIO-1 on TALKGROUP 1.
Keep this call in progress until the
test has completed.
1. DESCRIPTION
Step 2. Observe that RADIO-2 receives the
call.
Console Operator Positions have ultimate control of
transmitted audio on an assigned voice channel Step 3. While the call is in progress, key up
resource. The Console Position has the capability to CONSOLE-1 on TALKGROUP 1.
take control of an assigned voice channel for a
talkgroup call so that the operator's audio overrides Step 4. Observe that RADIO-2 is now
any subscriber audio. Console priority is a feature that receiving audio from CONSOLE-1
enables dispatchers to gain immediate access to an on TALKGROUP 1.
assigned voice channel so that a central point of audio
control exists. Step 5. De-key CONSOLE-1.
Step 6. Verify RADIO-2 now receives

SETUP RADIO-1 audio.
Step 7. End the TALKGROUP 1 call from

RADIO-1 - TALKGROUP 1 RADIO-1.
VERSION #1.110
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select the ATG 1 resource, which

Multigroup Call/ATG corresponds to TALKGROUP 1,
TALKGROUP 2, and
TALKGROUP 3.
1. DESCRIPTION
Step 2. Initiate the Multigroup Call from the
operator position.
This trunking feature allows an equipped console
operator position to transmit an announcement to Step 3. Observe that RADIO-1, RADIO-2
several different talkgroups simultaneously. As with and RADIO-3 receive the
Talkgroup Calls, multigroup calls operate across sites Multigroup Call.
as well as within the same site.
* Multigroups are set up through both the UCM and the receive the Multigroup Call
Subscriber Programming software. because it is not a member of
ATG 1.
SETUP Step 5. Answer the Multigroup Call using

RADIO-1 and observe the
console(s) receive the response.
RADIO-1 - SITE - SITE 1 Step 6. Verify that if the call is answered
RADIO-2 - TALKGROUP 2 within the repeater hang time, the
RADIO-2 - SITE - SITE 2 console will receive the call on the
RADIO-3 - TALKGROUP 3 ATG 1 resource tile, otherwise the
RADIO-3 - SITE - SITE 3 (SITE 1 if only 2 Sites) console will receive the call on the
RADIO-4 - RANDOM TALKGROUP 1 tile.
RADIO-4 - SITE - SITE 4 (SITE 2 if only 2 Sites)
Step 7. Verify that if the call is answered
* TALKGROUP 1, TALKGROUP 2, & TALKGROUP 3 within the repeater hang time,
are members of ATG 1. RADIO-2 and RADIO-3 will
monitor that call.
VERSION #1.000
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select an MCC 7500 operator

Emergency Alarm (Ack'd by MCC 7500 position in the zone where
Console) and Call Display Description RADIO-1 is affiliated for the test.
Step 2. Initiate an Emergency Alarm from

1. DESCRIPTION RADIO-1.
Step 3. Observe the Emergency from

Users in life threatening situations can use the RADIO-1 is received at the MCC
emergency button on the radio to send an audible 7500 operator position for
alarm and a visual alarm signal to a console operator TALKGROUP 1.
in order to request immediate system access to a
voice channel for an emergency call. Step 4. Acknowledge the Emergency at the
An emergency alarm begins after the radio user MCC 7500 operator position.
presses the radio's emergency button. Pressing the Verify that another operator
emergency button places the radio in "emergency position affiliated to TALKGROUP
mode". To begin an emergency call, the radio user 1 receives notification that the call
must press the radio's PTT button while in "emergency has been acknowledged.
mode." The assigned voice channel will be dedicated
to the emergency caller's talkgroup for an extended Step 5. Key RADIO-1 to initiate an
period of time, equal to the Message Hang Time plus Emergency call to the MCC 7500
the Emergency Hang Time. As with other call types, operator position and reply to the
emergency calls can operate across sites as well as radio from the operator position.
within the same site. Observe that the call takes place.
Step 6. Clear the Emergency from the MCC

SETUP 7500 console on TALKGROUP 1.
Step 7. Reset RADIO-1 by holding the

RADIO-1 - TALKGROUP 1 Emergency button on the radio.
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a call from CONSOLE-1 on

Conventional Radio Resource on the MCC CONVCH1.
7500 Console (Coded)
Step 2. Verify CONSOLE-1 outbound audio
can be monitored by RADIO-1
1. DESCRIPTION because it has the necessary keys
to decrypt the coded call, but
RADIO-2 is not able to monitor the
Subscribers can communicate to each other through a call because it does not have the
repeater that is selected via the channel selector on correct keys.
the individual radio.
Step 3. Respond to CONSOLE-1's
The signals that are received from the subscriber radio outbound transmission from
are repeated so that other radios on that channel will RADIO-1. Verify that the radio
be able to hear and participate in the conversation. audio can be monitored at the
console.
SETUP Step 4. Repeat steps 1-3 for a sample of the

remaining repeaters as needed.
RADIO-1 - CONVCH1 (with proper keys loaded for Step 5. Repeat steps 1-3 for a sample of the
coded call) remaining OPs as needed.
RADIO-1 - SITE - CONVSITE 1
RADIO-2- CONVCH1 (without keys loaded for coded
call)
CONSOLE-1 - CONVCH1
VERSION #1.010
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a Secure Talkgroup call on

Console Operator Secure / Clear Cross-Mode RADIO-1 by hitting the PTT.
Indication
Step 2. Verify that CONSOLE-1 is able to
receive audio from RADIO-1.
1. DESCRIPTION
Step 3. Place RADIO-1 in clear TX mode.
This test validates the ability of the console to show a Step 4. Initiate a Talkgroup call on RADIO-1
visual indication of a Secure and Clear mode by hitting the PTT.
mismatch during the following conditions:
1. Talkgroup on the Console is in secure transmit Step 5. Verify that CONSOLE-1 is able to
mode but receiving clear audio. receive audio from RADIO-1 and
2. Talkgroup on the Console is in clear transmit mode displays a secure mode mismatch
but receiving secure audio. indication.
Step 6. Place RADIO-1 in secure transmit

SETUP mode and place CONSOLE-1 in
clear transmit mode.
RADIO-1 TALKGROUP 1 (Secure TX mode) Step 7. Initiate a Secure Talkgroup call on

RADIO-1 - SITE - SITE 1 RADIO-1 by hitting the PTT.
CONSOLE-1 TALKGROUP 1 (Secure TX mode) Step 8. Verify that CONSOLE-1 is able to

receive audio from RADIO-1 and
displays a secure Cross-Mode
VERSION #1.030 Indication.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. CONSOLE-1 initiates a Talkgroup

Redundant Console Site Link Failure (MCC call on TALKGROUP 1.
7500 Console Site only)
Step 2. Observe that RADIO-1 is able to
receive and respond to the call.
1. DESCRIPTION
Step 3. Remove the WAN link from the
active router (Primary Site Router)
Communication between the Master Site and a at the Remote Console Site.
Remote Console Site can take place over dedicated
redundant links. The two links between the Master Site Step 4. Initiate a Talkgroup Call with
and the Remote Console Site operate in a redundant RADIO-1 in TALKGROUP 1.
mode. The system will switch to the backup link if the
main LAN or WAN link fails. Step 5. Observe that CONSOLE-1 is able to
receive and respond to the call.
Note: The Primary Site Router, if functional, will always
be the active router. The Secondary Site Router will Step 6. Replace the WAN link connection
only take over when the Primary Site Router is that was removed in step 4.
malfunctioning.
SETUP
A radio and a Console are required to perform this test
(RADIO-1 and CONSOLE-1). Select a Console site
with redundant links to the Master Site.
Pass____ Fail____
VERSION #1.010

RFP# 101216
December 16, 2010

Step 1. Assign an instance of global

Alarm Input / Outputs - Global (Aux I/O AUXIO_1 to CONSOLE-1 to a talk
Option) resource tile on TALKGROUP 1
Step 2. Assign instance of global AUXIO_1

1. DESCRIPTION to CONSOLE-2 to a talk resource
tile on TALKGROUP 1.
A dispatch console user can simultaneously view the Step 3. Change the status of AUXIO_1 on
status of all Aux I/O instances pertaining to the AUX CONSOLE-1.
I/O object. Change to one AUX I/O instance is
simultaneously viewable by all other instances. Step 4. Verify the standalone tile as well as
the talk resource instance on
CONSOLE-1 and CONSOLE-2
SETUP change and display the same
state for AUXIO_1.
CONSOLE-1 - TALKGROUP 1 Step 5. Change the status of AUXIO_1 on

CONSOLE-1 - SITE - CONSITE-1 CONSOLE-2.
CONSOLE-2 - SITE - CONSITE-1 Step 6. Verify the standalone tile as well as
For this test- the talk resource instance on
Global instance of AUXIO_1 has been created and is CONSOLE-1 and CONSOLE-2
assigned as a standalone tile on CONSOLE-1 and change and display the same
CONSOLE-2. state for AUXIO_1.
VERSION #1.020
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select the resource for

PTT Unit ID/Alias Display for MCC 7500 TALKGROUP 1 on CONSOLE-1.
Consoles
Step 2. Initiate a call on TALKGROUP 1
from RADIO-2 and observe that
1. DESCRIPTION the alias is seen at both
CONSOLE-1 and CONSOLE-2 in
the resource window as well as in
Console operator positions contain various resources the Activity Log window.
such as talkgroup, multigroup, Private Call which
enables the dispatcher to communicate with the Step 3. Initiate a call from RADIO-1 and
subscriber units. If activity occurs on one of these observe that the alias of RADIO-1
operator position resources, the unit ID or associated is seen at both CONSOLE-1 and
alias of the initiating radio appears at the console CONSOLE-2 in the resource
resource. window as well as in the Activity
Log window.
SETUP Step 4. Update the UCM with a new

RADIO-2 alias. Make sure to give
enough time for the alias change
RADIO-1 - TALKGROUP 1 to propagate to the Zone
RADIO-1 - SITE - SITE 1 Controller.
RADIO-2 - SITE - SITE 2 Step 5. Initiate a call from RADIO-2 and
RADIO-1 and RADIO-2 have to have aliases in the observe that now the new alias of
UCM. RADIO-2 is seen at both consoles
CONSOLE-1 - TALKGROUP 1 in the list in the resource window
CONSOLE-2 - TALKGROUP 1 as well as in the Activity Log
window
VERSION #1.020
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a wide area coded call from

Console ASTRO Secure Talkgroup Call (MCC CONSOLE-1 on TALKGROUP 1.
7500 only)
Step 2. Verify RADIO-1 and RADIO-3 can
monitor and respond to the secure
1. DESCRIPTION call.

Digital encryption is used so only properly equipped CONSOLE-2 on TALKGROUP 2.
radios can monitor the conversation. A "Key" is used
to encrypt the transmit audio. Only radios and Step 4. Verify that RADIO-2 can monitor
Consoles with the same "Key" can decrypt the audio and respond to the secure call.
and listen to it. Unlike CENTRACOM Gold Elite Note that RADIO-4 cannot monitor
Console which uses the MGEG, secure functionality the call because it does not have
resides within the MCC 7500 Console and is keyed via the "Key" that corresponds to
the KVL. CKR2.
Note: The MCC 7500 Console(s) need to be equipped Step 5. Change RADIO-2 and RADIO-4 to
with Crypto Cards and the radios with Crypto Modules TALKGROUP 1.
in order to participate in secure calls.
CONSOLE-1 on TALKGROUP 1.
SETUP
Step 7. Verify that RADIO-1, RADIO-2,
RADIO-3 and RADIO-4 can
RADIO-1 - TALKGROUP 1 monitor and respond to the secure
RADIO-1 - SITE - SITE 1 call because they all have the
RADIO-2 - TALKGROUP 2 "Key" that corresponds to CKR1.
RADIO-2 - SITE - SITE 1 If the radios are equipped with
RADIO-3 - TALKGROUP 1 dual algorithm encryption
RADIO-3 - SITE - SITE 2 modules, select talkgroups using
RADIO-4 - TALKGROUP 2 the second algorithm and repeat
RADIO-4 - SITE - SITE 2 steps 1-6.
TALKGROUP 1 needs to be bound to "CKR1" and
TALKGROUP 2 needs to be bound to "CKR2" in both
the UCM and the radio programming. CONSOLE-1,
CONSOLE-2, RADIO-1, RADIO-2 and RADIO-3
should be loaded with the "Keys" that correspond to
CKR1 and CKR2. RADIO-4 should only have the
"Key" that corresponds to CKR1. All radios should be Pass____ Fail____
set for the secure mode.
VERSION #1.050

RFP# 101216
December 16, 2010

Step 1. Select the CONVCH1 resource on

Acoustic Crossmute Feature for Conventional CONSOLE-1 and CONSOLE-2.
Resource on the MCC 7500
Step 2. Without an Acoustic Crossmute
configured, and the select
1. DESCRIPTION speakers of each operator
position turned to maximum
volume, transmit on CONSOLE-1.
Acoustic crossmuting means that selected operator
positions will not hear outbound transmissions from Step 3. Confirm feedback is heard on the
operator positions they are cross-muted with. operator positions and the
portable hears feedback on the
This feature is used when operator positions are channel.
located in the same room.
Step 4. With an Acoustic Crossmute
configured, and the select
SETUP speakers of each operator
position turned to maximum
volume, transmit on CONSOLE-1.
RADIO-1 - CONVCH1
RADIO-1 - SITE - CONVSITE 1 Step 5. Verify no feedback is heard at either
CONSOLE-1 - CONVCH1 operator position and that the
CONSOLE-1 - SITE - CONSITE 1 portable does not hear feedback
CONSOLE-2 - CONVCH1 on the channel.
VERSION #1.020
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Choose a conventional Radio

Channel Control Gateway (CCGW) Resource at the console.
Step 2. Connect a transmission test set to

1. DESCRIPTION the output of the Channel Control
Gateway (CCGW) port
corresponding to the selected
A conventional station can be integrated into a Radio Resource in the Elite
trunking system by placing a conventional resource on operator position.
the Elite consoles. This allows the user to dispatch
and patch the conventional station with the desired Step 3. Key up the console Radio Resource
talkgroups. and verify Transmit audio for the
conventional resource is heard
through the transmission test set.
SETUP
Step 4. Inject a test tone into the input of the
Radio Resource selected.
Connect a transmission test set to the CCGW port that
corresponds to a conventional channel in the Elite Op Step 5. Verify the Radio Resource receives
Position. Each RJ45 receptacle on the CCGW , pins 1 the tone in the appropriate
and 2 are for RX audio, and pins 4 and 5 are for TX speaker.
audio.
Step 6. Repeat Steps 1-5 for a random
sample of the remaining channels
VERSION #1.030 as needed.
Pass____ Fail____

RFP# 101216
December 16, 2010

MCC 7500 Features VERSION #1.040
Talk Extend (MCC 7500 Consoles Only) 2. TEST

1. DESCRIPTION
Step 1. Verify communications on TALKGROUP
A Tone Page is an audio alert typically sent to alert the
1, TALKGROUP 2, CCH1 and CCH2
user. Tone page is also sent to a device to issue a by setting up voice calls between the
control message. A tone page can be sent to Trunked Radio and Console on each TG and
Group or Analog Conventional resource. CCH separately.
The user interface allows for issuing an individual page Step 2. Create a list of tone pages through the
and a group of individual pages. standard paging interface on
The simultaneous mode refers to the configured CONSOLE-3 Elite interface. Keep the
paging mechanism where console sends pages all-at- order of the pages to be
once on different resources. Pages on a same TALKGROUP 1TonePage1,
resource are sent as sequential pages in the order in TALKGROUP 2TonePage1,
TALKGROUP 2TonePage2,
which the pages appear in the paging queue.
CCH1TonePage1 and
A pre-configured group page representing a set of
CCH2TonePage1.
individual pages is invoked via the console user Step 3. Press "Send" and Verify that the first
interface to issue a simultaneous tone pages. page on each resource in the queue
The dispatcher can initiate a voice conversation after is sent simultaneously.
the tone page is sent out within a given time period Step 4. Verify that Radio-1, Radio-2, Radio-3
without the system having to re-allocate resources for and Radio-4 received tone pages on
voice transmission. This is referred to as talk extend TALKGROUP 1, TALKGROUP 2,
and is available to the dispatcher in a simultaneous CCH1 and CCH2 respectively.
mode of operation. Step 5. Verify that the CONSOLE-1 and 2
received tone pages on TALKGROUP
SETUP
1, CCH1 and TALKGROUP 2, CCH2
respectively.
RADIO-2 - TALKGROUP 2 Step 6. Verify that the second page on
RADIO-3 - CCH1 TALKGROUP 2 is sent once the tone
RADIO-4 - CCH2 is completed for the first page.
CONSOLE-1 - TALKGROUP 1, CCH1 Step 7. Verify that the RADIO-2 and CONSOLE-
CONSOLE-2 - TALKGROUP 2, CCH2 2 received tone pages on
CONSOLE-3 - TALKGROUP 1, TALKGROUP TALKGROUP 2 and CCH2.
2,TALKGROUP 3, CCH2 Step 8. Verify that while the second page
Note: Console should be setup for simultaneous TALKGROUP 2TonePage2 is sent on
paging mode through the network management. The TALKGROUP 2, transmission on
other resources remain active even
individual tone pages on TALKGROUP 1 with
after the tone is sent. The next step
TALKGROUP 1TonePage1 alias, Quick Call I Paging
must be executed within 1.2 seconds
Format, TALKGROUP 2 with TALKGROUP to be successful.
2TonePage1 alias, Quick Call I Paging Format, Step 9. Press general transmit button and Verify
TALKGROUP 2 with TALKGROUP 2TonePage2 alias, that RADIO-1, Radio2, CONSOLE-1
Quick Call II Paging Format, CCH1 with and CONSOLE-2 receive PTT grant
CCH1TonePage1 alias, Quick Call I Paging Format, on resources associated with the
CCH2 with CCH2TonePage1 alias, Quick Call I paging event. Note that although the
Paging Format via network management. Configure TALKGROUP 3 is a single select
the Talk Extend tier >0 via network management. resource the general transmit invokes
transmission on res
Pass____ Fail____

RFP# 101216
December 16, 2010


Tone Generation Trunking Resource in 1
Secure Mode (MCC 7500 Consoles)
from CONSOLE-1
1. DESCRIPTION
Step 3. Key up general transmit by using
CONSOLE-1's mike or foot switch
This test will demonstrate that the dispatch console
(which is in secure mode) is able to transmit Alt-Tone Step 4. Verify that RADIO-1 hears audio
on a trunking resource during the tone generation from CONSOLE-1 during the Alert
period. Tone Talk Extend period..
SETUP
TG-1 - Crypto Key - CKR1
SITE-1 - ZONE 1
CONSOLE-1 -TALKGROUP 1

RFP# 101216
December 16, 2010

Step 1. Select an operator position for

Talkgroup Patch testing which contains
TALKGROUP 1 and
TALKGROUP 2.
1. DESCRIPTION
Step 2. At the desired operator position
select one of the Patch tabs in the
Talkgroup Patch allows a dispatcher to merge several Patch/Multi-Select window.
talkgroups together on one voice channel to participate
in a single conversation. This can be used for Step 3. Click the button on the patch that
situations involving two or more channels or talkgroups allows an operator to setup and
that need to communicate with each other. edit a patch (note that the patch
window turns blue).
Using the Patch feature, the console operator can talk
and listen to all of the selected talkgroups grouped; in Step 4. Add TALKGROUP 1 and
addition, the members of the individual talkgroups can TALKGROUP 2 to the patch by
also talk or listen to members of other talkgroups. selecting each resource tile.
Patched talkgroups can communicate with the console
dispatcher and other members of different talkgroups Step 5. Once the talkgroups are added,
because of the "supergroup" nature of the Patch click the patch setup button again
feature. to complete the patch setup.
NOTE : If "secure" and "clear" resources are patched Step 6. Initiate several Talkgroup Calls
together, one repeater for each mode may be between radios.
assigned per site.
Step 7. Observe that all radios are able to
communicate with one another.
SETUP Also via ZoneWatch (if available)
observe that only one station is
assigned at each of the two sites.
RADIO-1 - SITE - SITE 1 Step 8. Initiate a call from the operator
RADIO-2 - TALKGROUP 2 position using the Patch Transmit
RADIO-2 - SITE - SITE 1 and observe that all radios are
RADIO-3 - TALKGROUP 1 able to receive the call and only
RADIO-3 - SITE - SITE 2 one station is assigned at each of
RADIO-4 - TALKGROUP 2 the two sites.
Step 9. Remove TALKGROUP 1 and
* All 4 Radios must have the same home zone. All 4 TALKGROUP 2 from the patch.
Radios should be in the clear mode.
VERSION #1.090
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Send a Alert-Tone to PATCH-1

Sending Alert Tone to Patch Member (MCC
7500 Consoles) Step 2. Verify that RADIO-1 and RADIO-2
hear the Alert-Tone
1. DESCRIPTION
This test will demonstrate that the console will send

Alert-Tone to all the members in a patch.
SETUP
SITE-1 - ZONE 1
CONSOLE-1 - SITE - CSITE-1
PATCH-1-TG-1-TALKGROUP 2

RADIO-1- SITE- SITE-1
RADIO-2 - SITE- SITE-1
VERSION #1.040

RFP# 101216
December 16, 2010

Step 1. Using CONSOLE-1, select the call

Call Alert Page alert button in the "Private Call"
resource window.
1. DESCRIPTION Step 2. Enter the ID of RADIO-1.
Step 3. Send the call alert to RADIO-1 by

Call Alert Page allows a subscriber/dispatcher to depressing the send button.
selectively alert another radio unit. The initiating
radio/console will receive notification as to whether or Step 4. Verify that RADIO-1 receives the
not the call alert was received. Units receiving a Call alert and that the ID of the console
Alert will sound an alert tone and show a visual alert is shown.
indication. The display will also show the individual ID
of the initiating radio/console unit. After receiving the Step 5. Turn off RADIO-1.
Call Alert, the radio can respond with either a Private
Call or normal talkgroup call. Step 6. Send the call alert to RADIO-1
again.
This feature is fully supported on all display portables
and mobiles. Step 7. Verify that after trying to page
RADIO-1, the console displays
"Can not send call alert - target
SETUP not found" in the summary list.
VERSION #1.070
Pass____ Fail____

RFP# 101216
December 16, 2010

2. TEST
MCC 7500 Features
Step 1. Select the CONVCH1 Radio
Resource by moving the cursor
Conventional Radio Resource on the MCC over the Radio Resource's name
7500 Console (Clear) and selecting.
Step 2. Begin an outbound console

1. DESCRIPTION transmission using the PTT Button
on the newly selected Radio
Resource, in clear mode.
A Radio Resource is selected on the MCC 7500
consoles by placing the cursor over the Radio Step 3. Verify that console's outbound audio
Resource (Channel Control Window), choosing an can be monitored by RADIO-1.
area and selecting. The Radio Resource choice area
is the region where the name of the Radio Resource is Step 4. Respond to the console outbound
located (Top alphanumeric line of the Radio transmission from RADIO-1.
Resource). When selected, the background of the Verify that RADIO-1 audio can be
Radio Resource will turn white and the border will turn monitored at the console Select
green. Choosing the PTT button will send keying speaker.
commands to the station.
Step 5. Depress any of the other available
Radio Resources to "deselect" the
SETUP present Radio Resource.
Step 6. Respond to the console outbound

RADIO-1 - CONVCH1 transmission from RADIO-1.
RADIO-1 - SITE - CONVSITE 1 Verify that RADIO-1's audio can
CONSOLE-1 - CONVCH1 be monitored at the unselect
CONSOLE-1 - SITE - CONSITE 1 speaker.
Step 7. Repeat steps 1-6 for a sample of the

VERSION #1.010 remaining channels as needed.
Step 8. Repeat steps 1-7 for a sample of the

remaining OPs as needed.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify communications on

Individual Tone Pages (Mixed Resources - TALKGROUP 1, TALKGROUP 2,
Simultaneous) CCH1 and CCH2 by setting up
voice calls between the Radio and
Console on each TG and CCH
1. DESCRIPTION separately.
Tone Page is an audio alert typically sent to alert the Step 2. Create a list of tone pages through
user. Tone page is also sent to a device to issue a the standard paging interface on
control message. A tone page can be sent to Trunked CONSOLE-3 Elite interface. Keep
Group or Analog Conventional resource. the order of the pages to be
The user interface allows for issuing an individual page TALKGROUP 1TonePage1,
and a group of individual pages. TALKGROUP 2TonePage1,
The simultaneous mode refers to the configured TALKGROUP 2TonePage2,
paging mechanism where console sends pages all-at- CCH1TonePage1 and
once on different resources. Pages on a same CCH2TonePage1.
resource are sent as sequential pages in the order in
which the pages appear in the paging queue. Step 3. Press "Send" and Verify that the first
A pre-configured group page representing a set of page on each resource in the
individual pages is invoked via the console user queue is sent simultaneously.
interface to issue a simultaneous tone pages.
Step 4. Verify that RADIO-1, RADIO-2,
RADIO-3 and RADIO-4 received
SETUP tone pages on TALKGROUP 1,
TALKGROUP 2, CCH1 and CCH2
RADIO-1 - TALKGROUP 1 respectively.
RADIO-3 - CCH1 Step 5. Verify that the CONSOLE-1 and
RADIO-4 - CCH2 CONSOLE-2 received tone pages
CONSOLE-1 - TALKGROUP 1, CCH1 on TALKGROUP 1, CCH1 and
CONSOLE-2 - TALKGROUP 2, CCH2 TALKGROUP 2, CCH2
CONSOLE-3 - TALKGROUP 1, TALKGROUP respectively.
2,TALKGROUP 3, CCH2
Note: The Console should be setup for simultaneous Step 6. Verify that the second page
paging mode through the network management. The TALKGROUP 2TonePage2 on
individual tone pages on TALKGROUP 1 with TALKGROUP 2 is sent once the
TALKGROUP 1TonePage1 alias, Quick Call I Paging tone is completed for the first
Format, TALKGROUP 2 with TALKGROUP page.
2TonePage1 alias, Quick Call I Paging Format,
TALKGROUP 1 with TALKGROUP 2TonePage2 alias, Step 7. Verify that the RADIO-2 and
Quick Call II Paging Format, CCH1 with CONSOLE-2 received tone pages
CCH1TonePage1 alias, Quick Call I Paging on TALKGROUP 2 and CCH2.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010


Tone Generation on Conventional Resource 1
(MCC 7500 Consoles)
from CONSOLE-1
1. DESCRIPTION
Step 3. Verify that RADIO-1 hears audio
from CONSOLE-1 during the Alert
This test will demonstrate that the dispatch console is Tone Talk Extend period.
able to transmit on a conventional resource during the
tone generation period
SETUP
RADIO-1 - CONVCH1
CCGW-1 - CONVCH1
CCGW-1 - SITE 1
CONSOLE-1 - CONVCH1
(Note: Use General Transmit by keying up CH1 via

console microphone or footswitch)
Pass____ Fail____
VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. Initiate a voice transmission from

Station Control on IP-Based Analog CONSOLE-1 on selected
Conventional Channel - Frequency Select Test frequency on CCH1.
Step 2. Verify that CONSOLE-2, RADIO-1

1. DESCRIPTION and RADIO-2 can hear
CONSOLE-1, but CONSOLE-3
does not hear CONSOLE-1.
This feature enables the MCC 7500 Console to modify
operational parameter(s) on an IP-Based analog Step 3. End the voice transmission by
conventional channel. The operational commands releasing PTT at CONSOLE-1.
include changing frequency, PL Code of the station, Wait for a few seconds to clear
turning on/off monitor to enable / disable PL Code, etc. the call.
The execution of the commands requires the
application of the TRC tones. Step 4. Select frequency F2 from
CONSOLE-1 on CCH1.
SETUP Step 5. Observe that the selected frequency

is displayed at CONSOLE-1 and
CONSOLE-2 has changed to F2.
This test requires an operational CCGW with an
analog conventional channel (CCH1) and the attached Step 6. Tune RADIO-1 to frequency F2.
BS which is tuned to F1 transmit/receive pair.
RADIO-1 Tuned to TX Freq (F1) of CCH1 Step 7. Initiate a voice transmission from
RADIO-2 Tuned to TX Freq (F1) of CCH1 CONSOLE-1 on selected
CONSOLE-1 - CCH1 frequency on CCH1.
CONSOLE-2 - CCH1
CONSOLE-3 - Not affiliated to CCH1 Step 8. Observe that CONSOLE-1 voice
transmission is heard by RADIO-1
and CONSOLE-2. RADIO-2 and
VERSION #1.030 CONSOLE-3 do not hear
CONSOLE-1.
Pass____ Fail____

RFP# 101216
December 16, 2010


Console ASTRO Secure Talkgroup Call CONSOLE-1 on TALKGROUP 1.
Step 2. Verify RADIO-1 and RADIO-4 can

1. DESCRIPTION monitor and respond to the secure
call.
Digital encryption is used so only properly equipped Step 3. Initiate a wide area coded call from
and configured subscribers can monitor the CONSOLE-2 on TALKGROUP 2.
conversation. A "Key" is used to encrypt the transmit
audio. Only radios, Consoles and MGEGs with the Step 4. Verify that RADIO-2 can monitor
same "Key" can decrypt the audio and listen to it. The and respond to the secure call.
talkgroup to Common Key Reference (CKR) binding is Note that RADIO-3 cannot monitor
kept in the MGEG or MCC 7500 Console and is the call because it does not have
configured in the User Configuration Manager (UCM). the correct "Key" that corresponds
The bindings are propagated to the MGEGs, which to CKR2.
enable the Elite Consoles to participate in encrypted
calls. The "Key" that corresponds to the CKRs must be Step 5. Change RADIO-2 and RADIO-3 to
loaded into all MGEG Crypto Cards and/or MCC 7500 TALKGROUP 1.
Console Crypto Cards in the Zone.
Note: The MGEG/MCC 7500 Console(s) need to be CONSOLE-1 on TALKGROUP 1.
equipped with Crypto Cards and the radios with Crypto
Modules in order to participate in secure calls. Step 7. Verify that RADIO-1, RADIO-2,
RADIO-3 and RADIO-4 can
monitor and respond to the secure
SETUP call because they all have the
"Key" that corresponds to CKR1.
RADIO-1 - TALKGROUP 1 (Secure TX Mode) Step 8. If the radios are equipped with dual
RADIO-1 - SITE - SITE 1 algorithm encryption modules,
RADIO-2 - TALKGROUP 2 (Secure TX Mode) select talkgroups using the
RADIO-2 - SITE - SITE 1 second algorithm and repeat
RADIO-3 - TALKGROUP 2 (Secure TX Mode & No steps 1-7.
Key for CKR2)
RADIO-4 - TALKGROUP 1 (Secure TX Mode)
TALKGROUP 1 Loaded with CKR1 Keys Pass____ Fail____
TALKGROUP 2 Loaded with CKR2 Keys
VERSION #1.100

RFP# 101216
December 16, 2010

Step 1. On the MCC 7500 select the "Show

Activity Log" button on the tool bar
Activity Log to open the Activity Log Window.
1. DESCRIPTION Step 2. Place several calls on various radios

& talkgroups to log call information
and insure calls are displayed in
activity log window.
MCC 7500 Console activity log will show all traffic for
the resource assigned to that console to include the
Step 3. Select a logged call in the Activity
time, radio alias, TG, PTT ID and Emergency Call.
Log Window and verify that the
CCW at the top of the Activity log
The dispatcher has the capability of selecting a logged
window changes to the
call within in the "Activity Log Window" for instant
corresponding resource. Verify
transmit on the corresponding logged resource.
the dispatcher is capable of
responding via the instant transmit
This activity log can be logged to a text file for archival
button.
purposes.
Step 4. Open the "Activity Text Document
File" and verify call traffic has
SETUP been archived to the document file
.
Ensure that "Log to File" option is enabled in the Elite

Admin Preferences Activity Log tab.
Set up various radios to various talkgroups monitored

by the Elite Dispatch being tested.
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a Talkgroup Call with

Link Failure between MCC 7500 site and Zone RADIO-1 in TALKGROUP 1.
Controller
Step 2. Observe that only RADIO-2,
CONSOLE-1 and CONSOLE-2
1. DESCRIPTION are able to monitor and respond to
the call
This test verifies that the two communication paths Step 3. Initiate a Talkgroup call with RADIO-
between the MCC 7500 Console Site and Zone 3 in TALKGROUP 2.
Controller are redundant and the system will continue
uninterrupted if the main path fails. To accomplish this Step 4. Observe that only RADIO-4,
test one of the two NIC connections is removed at the CONSOLE-1 and CONSOLE-2
ZC. are able to monitor and respond to
the call.
SETUP Step 5. Remove the ENET cable to Link 1

from the NIC on the ZC, this will
simulate a Zone Controller to
RADIO-1 - TALKGROUP 1 Console Site Link failure.
RADIO-2 - TALKGROUP 1 Step 6. Observe that the calls on
RADIO-2 - SITE - SITE 1 TALKGROUP 1 and
RADIO-3 - TALKGROUP 2 TALKGROUP 2 can continue.
RADIO-4 - TALKGROUP 2 Step 7. Repeat steps 1-6 for the other Zone
RADIO-4 - SITE - SITE 2 Controller.
CONSOLE-1 and CONSOLE-2 at the MCC 7500
Console site are affiliated to the TALKGROUP 1 and Step 8. Connect the ENET cables to
TALKGROUP 2 talkgroups. normalize the system.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select an operator position for

Console Initiated Private Call testing.
Step 2. Select the "PRIVATE-CALL" tile.

1. DESCRIPTION
provides the Private Call function.
Private Conversation is a selective calling feature
which allows a dispatcher or radio user to carry on Step 4. Select the unit to be Private Called,
one-to-one conversation that is heard only by the two in this case RADIO-1. (or select
parties involved. Subscriber units receiving a private the numeric keypad and enter the
call will sound an alert tone. As with other call types, Unit ID to be Private Called.)
Private Calls operate across sites as well as within the
same site. Step 5. Click the Send button.
Step 6. Answer the Private Call with

RADIO-1 and respond to the
SETUP console.
Step 7. Verify RADIO-2 does not hear the

RADIO-1 - TALKGROUP 1 private conversation.
RADIO-2 - TALKGROUP 1 Step 8. After completing the Private Call,
RADIO-2 - SITE - SITE 2 return to the normal talkgroup
mode.
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Depress the Instant Transmit button

Console Instant Transmit on the TALKGROUP 1 (Select)
radio resource.
1. DESCRIPTION Step 2. Verify that the Transmit indicator is

lit.
The instant transmit switch provides immediate Step 3. Verify that outbound audio is heard
operator access to a channel, independent of its select on TALKGROUP 1 using RADIO-
status (selected or unselected). It provides priority 1.
over other dispatcher transmit bars or optional
footswitches. Step 4. On RADIO-1 change the selector to
TALKGROUP 2.
SETUP Step 5. Depress the Instant Transmit button

on the TALKGROUP 2 radio
resource (Unselected).
RADIO-1 - SITE - SITE 1 Step 6. Verify that outbound audio is heard
on TALKGROUP 2 using RADIO-
CONSOLE-1 – TALKGROUP 1 (Selected), 1.
TALKGROUP 2 (Unselect mode)
VERSION #1.080
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using CONSOLE-1, select the ATG

Multigroup Call 1 resource, which corresponds to
TALKGROUP 1, TALKGROUP 2,
and TALKGROUP 3.
1. DESCRIPTION
Step 2. Initiate the Multigroup Call from
CONSOLE-1.
This trunking feature allows an equipped console
operator position to transmit an announcement to Step 3. Observe that RADIO-1, RADIO-2
several different talkgroups simultaneously. As with and RADIO-3 receive the
Talkgroup Calls, multigroup calls operate across sites Multigroup Call.
as well as within the same site.
receive the Multigroup Call
SETUP because it is not a member of
ATG 1.
RADIO-1 - TALKGROUP 1 Step 5. Answer the Multigroup Call using

RADIO-1 - SITE - SITE 1 RADIO-1 and observe
RADIO-2 - TALKGROUP 2 CONSOLE-1 receives the
RADIO-2 - SITE - SITE 2 response.
RADIO-3 - SITE - SITE 3 (SITE 1 if only 2 Sites) Step 6. Verify that if the call is answered
RADIO-4 - RANDOM within the repeater hang time, the
RADIO-4 - SITE - SITE 4 (SITE 2 if only 2 Sites) console will receive the call on the
CONSOLE-1 - ATG ATG 1 resource tile, otherwise the
console will receive the call on the
* TALKGROUP 1, TALKGROUP 2, & TALKGROUP 3 TALKGROUP 1 tile.
are members of ATG 1.
Step 7. Verify that if the call is answered
* RANDOM is any talkgroup not a member of ATG 1. within the repeater hang time,
RADIO-2 and RADIO-3 will
* Multigroups are set up through both the UCM and the monitor that call.
VERSION #1.120
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using CONSOLE-1, select one of

Secure Talkgroup Patch the Patch tabs in the Patch/Multi-
Select window.
1. DESCRIPTION Step 2. Click the button on the patch that

allows the operator to setup and
edit a patch (Note: The patch
A Patch is created to allow users of dissimilar window turns blue).
resources (different
frequencies, different infrastructure) to communicate Step 3. Add TALKGROUP 1 and
with each other. Telephones and radio resources can TALKGROUP 2 talkgroups to the
be patched together. A patch is a way of connecting patch by selecting each resource
resources so that when a call is received on one tile.
resource the audio is passed along to another
resource. Step 4. Once all talkgroups are added, click
This test validates the ability of the console/radio to the patch setup button again to
transmit and to receive secure calls on Patch and complete the patch setup.
patch secure audio from one resource to another.
Step 5. Initiate a talkgroup call on
TALKGROUP 1 from RADIO-2 in
SETUP a secure transmit mode.
Step 6. Observe that all radios are able to

RADIO-1 - TALKGROUP 1 hear RADIO-2 except RADIO-3 as
RADIO-1 - SITE - SITE 1 it is a clear only radio.
RADIO-2 - SITE - SITE 1 Step 7. Dissolve the patch.
RADIO-3 - TALKGROUP 2 (No secure keys loaded)
CONSOLE-1 - TALKGROUP 1, TALKGROUP 2
RADIO-3 is a clear only radio. The TALKGROUP 1
and TALKGROUP 2 are non-regroupable and transmit
mode set to secure.
Pass____ Fail____
VERSION #1.060

RFP# 101216
December 16, 2010

Step 1. While the CONVCH1 resource is in

Console Conventional Instant Transmit an "Unselect" mode press the
Instant Transmit button on the
CONVCH1 resource window.
1. DESCRIPTION
Step 2. Verify that the Transmit indicator is
lit (lightening bolt).
The instant transmit switch provides immediate
operator access to a channel, independent of its select Step 3. Verify that RADIO-1 can monitor
status (selected or unselected). and respond to the call on
CONVCH1.
SETUP Step 4. Make the CONVCH1 resource

"Select" by clicking the mouse
anywhere in the CONVCH1
RADIO-1 - CONVCH1 resource window.
RADIO-1 - CONVSITE 1
Step 5. Press the Instant Transmit button on
the CONVCH1 resource window.
VERSION #1.010
Step 6. Verify that RADIO-1 can monitor
and respond to the call on
CONVCH1.
Pass____ Fail____

RFP# 101216
December 16, 2010

6.2 System Management Tests

RFP# 101216
December 16, 2010

System Management Tests 2. TEST
Step 1. Initiate a TALKGROUP 1 call from

Configuration Management - General Timeout RADIO-1. Verify that the Radio
Parameters System permits the RADIO-1 call
request.
1. DESCRIPTION Step 2. In the manager, configure the

"Maximum Private Call Duration"
to 1 minute and apply.
System and call timeout parameters such as Private
Call Ring, Group Call Service Timeout, Private Call Step 3. Initiate a Private Call from RADIO-1
Hang Time, Emergency Call Hang time, Maximum to RADIO-2. Continue to converse
Group Call Duration and Maximum Private Call back and forth using RADIO-1 and
Duration can also be manipulated from the UNC RADIO-2,
Wizard (7.8) or UCM (7.7 and earlier).
Step 4. Verify that after one minute elapses,
For this test the Private Call Duration will be limited to the system will transmission trunk
one minute. The call will change to transmission the Private Call because the
trunked after the one minute timer expires at which maximum call duration has been
time the hang timers will come into play. Once the exceeded. Once the hang time
users have discontinued using the system for the timer has expired the call will be
Private Call long enough for the hang timers to expire terminated.
the system will end the call.
Step 5. Reset the Private Call Maximum
Call Duration setting to be 10
SETUP minutes (default).
VERSION #1.090
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. The first view is the Active Alarms.

UEM - Views In the navigation pane expand
Fault Management and select
Alarms.
1. DESCRIPTION
Step 2. Customize the Active Alarms display
by selecting the Edit option from
The Unified Event Manager (UEM) provides three the menu bar, then select Search.
different views. The purpose of this test is to validate
the views available from the UEM. Step 3. Perform a Managed Resource
search for channels, site
controllers and routers by entering
SETUP "Starts with" and ch, sc, and z00
respectively in the search fields to
perform the three separate
NMclient01 - UEM session up and running. searches.
Step 4. For each of the three searches a

VERSION #1.080 filtered alarm view is displayed
that contains alarms for the
appropriate device in the search.
Step 5. The second view is the Physical

Summary view. In the navigation
pane, expand Zone Maps and
select Physical Summary. The
Physical Summary View provides
an aggregated alarm severity
status of the devices located at all
subnets in the Zone.
Step 6. The third view is the Service

Summary. In the navigation pane,
under Zone Maps select Service
Summary. The Service Summary
View provides a quick summary of
the service status of sites in a
Zone.
Step 7. In the main UEM window is an

Alarm Summary View pane. In the
Alarm Summary View, select the
format for the desired view, pie,
tabular or bar.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the service laptop attempt to

VPN Via CEN Firewall - Authentication ping nm client on Motorola radio
network. Verify no connection can
occur. Open Remote desktop
1. DESCRIPTION connection and attempt to connect
to NM client on Motorola radio
network. Confirm no connection.
The Juniper VPN firewalls provide remote access for
service and maintenance technicians (Customer or Step 2. Right click on vpn program
Motorola) through a VPN Client. Once the VPN client (Netscreen Remote) in system
is connected, the VPN firewall allows a service tray.
technician to run a remote desktop on an NM Client.
The service technician can then work on the entire Step 3. Select "Connect" ->My
Master Site by using standard ASTRO® 25 NM tools connections\NM_Client-Auth
and any pre-installed service tools.
Step 4. Login prompt appears. Enter proper
SecurID userid and password.
SETUP Dialogue box appears
"Successfully connected to My
Connections\NM_Client-Auth."
A configured service laptop with the appropriate VPN
software is required. Step 5. Open Remote desktop connection
on service laptop. Validate
connection to NM client.
VERSION #1.010
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Add RADIO-1,RADIO-2,RADIO-3,

Affiliation Display (Single Site) and RADIO-4 to the Affiliation
Display.
1. DESCRIPTION Step 2. Verify that RADIO-1 and RADIO-2

show they are affiliated to SITE 1
Affiliation Display is a Private Radio Network and TALKGROUP 1.
Management (PRNM)application that monitors the
mobility of radios for a particular zone. Mobility Step 3. Verify that RADIO-3 and RADIO-4
describes how radio users travel between different show they are affiliated to SITE 1
sites in a zone and how they communicate with other and TALKGROUP 2.
members of their assigned talkgroup or even with
members outside of their talkgroup. A radio can be Step 4. Change the talkgroup of RADIO-1
viewed in more than one zone. As a radio roams from and RADIO-2 to TALKGROUP 2.
one site to another or changes talkgroups, Affiliation
Display updates and displays the affiliation and de- Step 5. Verify that RADIO-1 and RADIO-2's
affiliation information for a monitored radio. This affiliated talkgroup changes to
information can be useful for the troubleshooting and TALKGROUP 2 on the Affiliation
tracking of radios in the system and for monitoring the Display.
movement of traffic within a zone.
The Affiliation Display is divided into three sections:
Site Viewer, Talkgroup Viewer, and Radio Viewer.
- The Site Viewer displays the number of talkgroups
and number of radios affiliated to that site.
- The Talkgroup Viewer displays how many radios are
affiliated to that talkgroup and the number of sites at
which the talkgroup has radios affiliated.
- The Radio Viewer window displays affiliation
information for a custom list of radios.
SETUP
Pass____ Fail____
VERSION #1.040

RFP# 101216
December 16, 2010

Step 1. Delete the database record for
RADIO-1 in both the Radio and
Configuration Management - Access Radio User Configuration
Permissions Windows so that the system does
not have any knowledge of
RADIO-1.
1. DESCRIPTION Step 2. Verify the "Individual Default Access
Permission" flag is set to "NO"
using the correct management
Prior to the ASTRO 7.8 release the Radio System application. If changes are made,
Infrastructure Configuration Management section of approve the job in Voyence, then
the Zone Configuration Manager (ZCM) application set Publish Infrastructure Data from
the parameters for each of the system devices in the the UNCW. (Prior to 7.8 release
SmartZone system. In ASTRO releases 7.8 and later the application will be the ZCM,
the Radio System Infrastructure management is done 7.8 and later releases will use the
in the Unified Network Configurator (UNC) application. Unified Network Configurator
The Unified Network Configurator Wizard (UNCW) Wizard.)
also helps to configure the system by having a User Step 3. Initiate a call from RADIO-1 on
interface into the system configuration. TALKGROUP 1. Verify that the
Radio System rejects the RADIO-
Configuration parameters such as Individual and 1 call request because RADIO-1
Talkgroup Default Access Permission, and Site has not been defined in the Radio
Access Denial Type can be manipulated from these User database.
applications. Step 4. Change the Individual Default
Access Permission flag to YES.
After approving the job in
SETUP Voyence, Publish Infrastructure
Data from the UNCW.
RADIO-1 - TALKGROUP 1 that the system permits the
RADIO-1 - SITE - SITE 1 RADIO-1 call request because the
RADIO-2 - TALKGROUP 1 system grants radio access using
RADIO-2 - SITE - SITE 1 default settings.
Step 6. Configure the RADIO-1 records that
were automatically created in the
VERSION #1.120 Radio and Radio User
Configuration Windows as a result
of the radio's PTT.
Step 7. Reset the "Individual Default Access
Permission" flag to NO. After
approving the job in Voyence,
Publish Infrastructure Data from
the UNCW.
that the Radio System permits the
RADIO-1 call request because
RADIO-1 is now a valid user.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a Call Alert (PAGE) from

Configuration Management - Subscriber RADIO-1 to RADIO-2. Verify that
Capabilities RADIO-2 receives the Call Alert
(PAGE).
1. DESCRIPTION Step 2. Change the Call Alert Enabled flag

to NO for RADIO-1 via the UCM.
The User Configuration Manager (UCM) controls the Step 3. Initiate a Call Alert (PAGE) from
parameters for all radio users and dispatchers on the RADIO-2 to RADIO-1. Verify that
system. Within the Subscriber section, the Radio User RADIO-2 receives a reject when
Configuration Window enables the network manager attempting to Call Alert (PAGE)
to tailor SmartZone subscribers' capabilities. RADIO-1.
Multigroup, Secure, Call Alert, Private Call, and
Telephone Interconnect are some of the features that Step 4. Change the Call Alert Enabled flag
can be enabled or disabled. The features that could be back to YES for RADIO-1 via the
unique to the particular user are configured directly in UCM.
the Radio User Configuration Window. The features
that could be configured the same for a group of users Step 5. Initiate a Call Alert (PAGE) from
are placed into records called profiles. The network RADIO-2 to RADIO-1. Verify that
manager references the profile which contains the RADIO-1 now receives the Call
desired setup for these features from the Radio User Alert (PAGE).
Configuration Window.
Step 6. Initiate a Private Call (CALL) from
Note - A profile must already exist to be referenced RADIO-1 to RADIO-2. Verify that
through the Radio Configuration Window but can be RADIO-2 receives the Private Call
modified later if needed. (CALL).
Step 7. Change the Private Call Enabled

SETUP flag to NO for RADIO-1 via the
UCM.
RADIO-1 - TALKGROUP 1 Step 8. Initiate a Private Call (CALL) from

RADIO-1 - SITE - SITE 1 RADIO-2 to RADIO-1. Verify that
RADIO-2 - TALKGROUP 1 RADIO-2 receives a reject when
RADIO-2 - SITE - SITE 2 attempting to Private Call (CALL)
RADIO-1.
* Flag both radios to be capable of Call Alert, Private
Call, and Dispatch Calls. Step 9. Change the Private Call Enabled
flag back to YES for RADIO-1 via
* Set the "User Enabled" flag to YES for both RADIO-1 the UCM.
and RADIO-2.
Step 10. Initiate a Private Call
(CALL) from RADIO-2 to RADIO-
VERSION #1.050 1. Verify that RADIO-1 now
receives the Private Call (CALL).
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify "Emergency Acknowledge" is

Configuration Management - Console set to YES in the Console
Talkgroup (MCC 7500 Systems only) Talkgroup Capability Profile for
TALKGROUP 1.
1. DESCRIPTION Step 2. Using RADIO-1, initiate an

Emergency on TALKGROUP 1.
Verify that CONSOLE-1 is able to
The User Configuration Manager (UCM) controls the "Ack" the Emergency.
parameters for all radio users and MCC 7500
dispatchers on the system. Within the Subscriber Step 3. End the Emergency on RADIO-1.
section, the Console Talkgroup Capability profile
enables the network manager to tailor a Console's Step 4. Change the "End Emergency" flag
Talkgroup capabilities. to NO in the console talkgroup
capability profile for TALKGROUP
1.
SETUP
Step 5. Verify that an indication is provided
via the console's Elite GUI status
RADIO-1 - TALKGROUP 1 bar on CONSOLE-1 indicating to
RADIO-1 - SITE - SITE 1 the dispatcher that new
CONSOLE-1 - TALKGROUP 1 configuration information is
available.
VERSION #1.070 Step 6. Using RADIO-1, initiate an

Emergency on TALKGROUP 1.
Step 7. Verify that after the database update

indication is received, the
CONSOLE-1 user is not able to
"Ack" an Emergency.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. On a UEM client session, click on

UEM - Manual Synchronization - Core Router the Network Database node tree
in the navigation window.
1. DESCRIPTION Step 2. Right click on a Core Router, select

SNMP-Node, and then select
Synchronize.
The purpose of this test is to manually synchronize
state with agents within the system using the Unified Step 3. The Synchronization Job Status
Event Manager (UEM). window appears with the Job
Status ID.
Manual synchronization provides a fallback to obtain
object status after a network interruption. Step 4. Click on the View Job Status button.
Step 5. The Job Status View window opens

SETUP providing the Job ID, Status,
Owner, Type, Target, Submit
Time, End Time, and Additional
NMclient01 - UEM session up and running. Info for all the jobs.
Step 6. Locate the Synchronization job

VERSION #1.090 initiated in step 2 and click on the
job. Verify the Synchronization job
is listed with a status of Success.
Step 7. Click on the View Log button. A

summary of the Synchronization
job details is provided in the job
log.
Step 8. Locate the Core Router in the

Network Database View. The
correct Severity property of the
device is displayed.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using the UNC Wizard , select an

Unified Network Configurator (UNC) Device RF Repeater site or Simulcast
Management - Site Parameter Subsite to update. (Note:
Changing an entire Simulcast Cell
may take a considerable amount
1. DESCRIPTION of time.)
Step 2. Change the Site Alias parameter to

The Unified Network Configurator (UNC) allows users a new value and click the Submit
to perform various functions to managed devices on button.
the system. This test will cover the modification of a
parameter at a site. Step 3. From the tools menu of the UNC
client session, open the Schedule
For this test, the Site Alias parameter will be modified Manager. Configuration remedy
on all radio system devices at the site. jobs are immediately added to the
Schedule Manager with a status
of Pending for all affected target
SETUP devices.
Step 4. Highlight the pending Remedy jobs

If the UNC is not open, double-click the UNC shortcut and approve them in the Schedule
(UNC) on the desktop, and a VoyenceControl client Manager. The remedy jobs are
session will launch. When prompted, use the Login approved and indicate a status of
dialog box to login to the UNC using the appropriate running in the Schedule Manager.
username and password.
If the UNC Wizard is not open, double-click the UNC Step 5. Refresh the Schedule Manager view
Wizard (UNCW) shortcut on the desktop, and a UNC until the jobs are completed.
Wizard client session will launch. When prompted, use
the Login dialog box to login to the UNC Wizard using Step 6. Once the jobs are performed
the appropriate username and password. successfully, use the Configlet
editor in the Network View and
perform a pull on all site devices
VERSION #1.060
Step 7. View the current configuration
information for the devices at the
site, and verify that the Site Alias
has been updated in the devices
current configuration
Step 8. Return the site alias to the correct

value.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the service laptop attempt to

VPN Via CEN Firewall - No Authentication ping nm client on Motorola radio
network. Verify no connection can
occur. Open Remote desktop
1. DESCRIPTION connection and attempt to connect
to NM client on Motorola radio
network. Confirm no connection.
The Juniper VPN firewalls provide remote access for
service and maintenance technicians (Customer or Step 2. Right click on vpn program
Motorola) through a VPN Client. Once the VPN client (Netscreen Remote) in system
is connected, the VPN firewall allows a service tray.
technician to run a remote desktop on an NM Client.
The service technician can then work on the entire Step 3. Select "Connect" -> My
Master Site by using standard ASTRO® 25 NM tools connections\NM_Client-No_Auth
and any pre-installed service tools. Dialogue box appears
"Successfully connected to My
Connections\NM_Client-No-Auth."
SETUP
Step 4. Attempt to ping nm client again.
Verify visibility to nm client.
A configured service laptop with the appropriate VPN
software is required. Step 5. Open Remote desktop connection
(program) on service laptop.
Validate connection to NM client.
VERSION #1.000
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Configure an alarm using the UEM

UEM - Email Alert Test client. On the UEM select Fault
Management and then Alarms.
Select Edit from toolbar at top of
1. DESCRIPTION window. Next select configure
and then Alarm Filter. Enter your
configuration parameters and
The Unified Event Manager (UEM) has the capability alarm filtering information.
to send email alerts. This email is sent using SMTP
protocol. The purpose of this test is to verify that an Step 2. Physically cause the alarm
email is sent from the UEM to an email server on the associated with the previously
customer network. created filter.
Step 3. Verify the alarm is displayed in

SETUP UEM.
Step 4. At the Email server verify an email

Email server connected to CEN. Logged into the has been received.
email application.
Step 5. Clear the alarm. Verify the alarm
*This test requires an optional Email Server.* has cleared in UEM.
VERSION #1.000
Pass____ Fail____

RFP# 101216
December 16, 2010


Configuration Management - Talkgroup TALKGROUP 1. Verify that
Capabilities RADIO-2 hears the RADIO-1
audio.
1. DESCRIPTION Step 2. Change the Talkgroup Enabled flag

to NO for TALKGROUP 1 via the
UCM.
The User Configuration Manager (UCM) controls the
parameters for all radio users and dispatchers on the Step 3. Initiate a call from RADIO-1 or
system. RADIO-2 on TALKGROUP 1.
Verify that neither radio can
Within the Subscriber section, the Talkgroup initiate a call because of the
Configuration Window enables the network manager change in status of the Group
to tailor SmartZone Talkgroup Capabilities. Enabled Flag of TALKGROUP 1.
Emergency, Secure and Priority Monitor are some of
the features that can be enabled or disabled. The Step 4. Initiate an Emergency call from
features that could be unique to the particular user are RADIO-1. Verify that both the
configured directly in the Talkgroup Configuration console (if present) and RADIO-2
Window. The features that could be configured the can hear the transmission.
same for a group of users are placed into records
called profiles. The network manager references the Step 5. Dekey RADIO-1.
profile which contains the desired setup for these
features from the Talkgroup Configuration Window. Step 6. Change the Talkgroup Enabled flag
back to YES for TALKGROUP 1
NOTE: A profile must already exist to be referenced via the UCM.
through the Talkgroup Configuration Window but can
be modified later if needed. Step 7. Initiate a call from RADIO-1 on
TALKGROUP 1. Verify that both
the console (if present) and
SETUP RADIO-2 hear RADIO-1.
* Set the "Talkgroup Enabled" flag to YES for

TALKGROUP 1 in the UCM. Pass____ Fail____
VERSION #1.060

RFP# 101216
December 16, 2010

Step 1. From the UEM, right click on an

UEM - Diagnostics - RF Site ASTRO Repeater Site managed
resource and select the Command
option.
1. DESCRIPTION Step 2. The command window opens for the
ASTRO repeater Site managed
resource with the following
The purpose of this test is to confirm diagnostic commands available: Site
commands are sent to an RF site and the proper Trunking, Site Off, Wide Trunking,
status is reported at the Unified Event Manager and Site Failsoft.
(UEM). Step 3. Select Site Trunking and click the
Apply button.
All commands are initiated from the UEM. Step 4. The command execution status is
displayed in the command
Standalone and MultiSite configurations are tested. window. After the command is
executed, the site enters site
trunking mode. The event is
SETUP displayed in the Network Events
Browser. An alarm is displayed in
the Alarms Browser.
NMclient01 - UEM session up and running in the Step 5. Select Site Off and click the Apply
Network Database view. button.
Step 6. The command execution status is
VERSION #1.070 window. After the command is
executed, the site enters site off
mode. The event is displayed in
the Network Events Browser. An
alarm is displayed in the Alarms
Browser.
Step 7. Select Wide Trunking and click the
Apply button.
window. After the command is
executed, the site enters wide
trunking mode. The event is
displayed in the Network Events
Browser.
Step 9. For a MultiSite Site, repeat step 1
except right click on a MultiSite
Site managed resource.
Step 10. Repeat steps 2-8. Verify the same
results occur.
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Wide Area Trunking to Site Trunking RADIO-1 in TALKGROUP 1.
State using the Unified Event Manager (UEM) Verify RADIO-2 will be able to
1. DESCRIPTION Step 2. Select SITE 1 in the Network

Devices tab. Right click and select
SNMP Node then Issue
Through the Unified Event Manager (UEM), the Command. Select "Site Trunking"
system user can run diagnostics that change the and apply to put the site in Site
"Trunking State" of a site. The effect of the diagnostic Trunking mode.
is displayed on the UEM.
Step 3. Observe that the UEM alarms view
shows that the site is now in Site
SETUP Trunking and is User Requested.
Step 4. Verify ZoneWatch (if available) no

RADIO-1 - TALKGROUP 1 longer shows the SITE 1 trunking
RADIO-1 - SITE - SITE 1 (Site Locked) activity. Also verify that RADIO-1
RADIO-2 - TALKGROUP 1 can no longer communicate with
RADIO-2 - SITE - SITE 2 RADIO-2
NMclient01 - UEM session up and running in the
alarms view. Step 5. Place the site back into Wide Area
Trunking using the "Issue
command" feature from UEM.
VERSION #1.100 Verify that the site returns to Wide
Area mode using the UEM.
Step 6. Verify communications between

RADIO-1 and RADIO-2
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Launch UNC/Voyence, if not already
opened. From the Network View,
Unified Network Configurator (UNC)/ Voyence select a Site Controller to modify.
Step 2. Change the SITE ID for the Site
Device Compliance Testing on Site ID
Controller to a different value. Perform
an audit on the configuration change
by selecting the audit button from the
1. DESCRIPTION bottom of the configuration window.
When the audit dialogue box opens,
select the modified Site Controller and
The Unified Network Configurator (UNC)-Voyence select the "Audit" button.
allows users to perform various functions on managed Step 3. When the Audit Window opens, using
devices on the system. The purpose of this test is to the Select Item dialogue boxes for the
validate system parameter compliance testing by the system, select the correct Zone, Site
UNC/Voyence. and Site item where the audited
device resides.
Step 4. Verify that the Audit Results indicate the
The UNC has the capability to detect errors in
device is non compliant.
configuration data before the change is sent to
Step 5. In the Compliance Audit Results window
device(s), immediately after a change has been sent to select the "List" button to expand the
a device, or on a configuration poll. audit results. Select the non-compliant
item from the list. View the "Remedy"
For this test, the error in the configuration data will be to correct the item compliance. A
detected before the change is sent to the device. The remedy will display that needs to be
configuration error can be detected by performing an run in order to put the device back
audit check in either the channel configuration screen, into compliance.
or through the approval process. This test covers Step 6. Exit from the Compliance Results
detecting the configuration error from the channel window by selecting "OK". Return the
configuration for the Site Controller
configuration screen.
back to the original configuration.
(Change the Site ID back to the
original ID.)
SETUP Step 7. Perform an audit on the configuration of
the device in test by selecting the
audit button from the bottom of the
No prior setup is required. configuration window. When the audit
dialogue box opens, select the site
controller under test and select audit.
Step 8. When the Audit Window opens, using
VERSION #1.080 the Select Item dialogue boxes for the
system, select the correct Zone, Site
and Site item where the audited
device resides.
Step 9. Verify that the Audit Results indicate the
device is compliant.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the Voyence Control Network

Unified Network Configurator (UNC) Device View, select a Channel that is
Compliance Testing on Channel currently Control Channel
Capable to update.
Step 2. Double click the channel to open the
1. DESCRIPTION Configuration window. Edit the
configuration to change "Dynamic
Frequency Blocking Capability =
The Unified Network Configurator (UNC) allows users Disable" to "Dynamic Frequency
to perform various functions on managed devices on Blocking Capability = Enable".
the system. The purpose of this test is to validate Step 3. Select the Schedule button, and in
system parameter compliance testing by the UNC. the Schedule Dialogue Box select
schedule. When the Schedule Job
The UNC has the capability to detect errors in Dialogue box opens, give the job
configuration data before the change is sent to a name and select Approve and
device(s), immediately after a change has been sent to Submit.
a device, or on a configuration poll. Step 4. From the Schedule Manager, verify
that the configuration change job
For this test, the error in the configuration data will be is listed with a status of Running.
detected by the UNC after a change has been sent to Press the refresh button to verify
a device. that the job is running, and to
obtain the current status. The job
is done when the status indicates
SETUP complete.
Step 5. Once the job is successfully
completed, the UNC will
If the UNC is not currently open, double-click the UNC automatically pull and validate the
shortcut (UNC) on the desktop, and a VoyenceControl configuration data from the
client session will launch. When prompted, use the device that was modifed. The
Login dialog box to login to the UNC using the UNC will detect the error, and
appropriate username and password. indicate the device is non
compliant. In the Network View,
If the UNC Wizard is not currently open, double-click press the refresh
the UNC Wizard (UNCW) shortcut on the desktop, and Step 6. The UNC will generate a remedy
a UNC Wizard client session will launch. When that indicates which parameter(s)
prompted, use the Login dialog box to login to the need to be changed for the device
UNC Wizard using the appropriate username and to be compliant.
password. Step 7. Approve the remedy from the
Schedule Manager to return the
channel to compliance.
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Login onto the Zone Controller

Zone Controller Database Backup (SFTP) admin menu via the NM Client.
Step 2. Perform a database backup using

1. DESCRIPTION the migrate database option.
Step 3. Log into the NM_ZC backup server

This is a feature that allows the infrastructure database and schedule a one time backup
to be stored onto a CD for backup. The database can for the ZC.
be backed up or restored without affecting system
operation. Step 4. The backup process will take
around 20 minutes.
SETUP Step 5. Log into the NM_ZC backup server

and select the reports section and
verify that the backup is created
No prior setup required. under the ZC.
Step 6. Select Manage Backups from the

VERSION #1.020 menu and create an offline
backup of the ZC database.
Step 7. PSFTP into the NM_ZC server and

log in with FTP_USER login.
Step 8. Enter ls to list all the files on the

server.
Step 9. Verify the ZC file is in the list and

copy this file to the NM Client
using the GET <IP> command.
(10.x.233.11 for the IBS and
10.x.233.12 NM/ZC Backup)
Step 10. Verify the file exists on the

NM Client under the
USER/Administrator folder and
has an ISO extension.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that the Conventional

Affiliation Display for Analog Conventional Channel View shows CONVCH1
(MCC 7500 Systems only) to be affiliated with CONSOLE-1
and CONVCH2 to be affiliated
with CONSOLE-2.
1. DESCRIPTION
Step 2. Verify that the Console Site
Conventional View shows that
The Affiliation Display for Analog Conventional is CONSITE-1 has CONVCH1 and
divided into two sections: Conventional Channel CONSITE-2 has CONVCH2
Viewer and Console Site Conventional Viewer.. affiliated.
-The Conventional Channel Viewer displays the Step 3. Logoff CONSOLE-1 and
consoles affiliated to a given conventional channel and CONSOLE-2.
the console sites with consoles affiliated to the
conventional channel. Step 4. Log into CONSOLE-1 and affiliate to
CONVCH2. Log into CONSOLE-2
-The Console Site Conventional Viewer displays the and affiliate to CONVCH1.
conventional channels affiliated to this console site
and the consoles at this console site affiliated to the Step 5. Verify that the Conventional
selected channel. Channel View shows CONVCH1
to be affiliated with CONSOLE-2
and CONVCH2 to be affiliated
SETUP with CONSOLE-1. Also for
CONVCH1 CONSITE-2 and for
CONVCH2 CONSITE-1 shall
CONSOLE-1 CONVCH1 show up in the viewer.
CONSOLE-1 - SITE - CONSITE-1
CONSOLE-2 CONVCH2 Step 6. Verify that the Console Site
CONSOLE-2 - SITE - CONSITE-2 Conventional View shows that
Two consoles, each capable of performing calls on two CONSITE-1 has CONVCH2 and
unique conventional channels, are required to perform CONSITE-2 has CONVCH2
this test. affiliated.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. In the Unified Event Manager (UEM)
Physical Sites screen, verify the
Current Status and Diagnostics for MCC 7500 Console Site is green (No alarms).
Console (UEM)
Step 2. Through the UEM, open the devices
under the site container by right
1. DESCRIPTION clicking and selecting "View
Devices".
This test verifies that the Unified Event Manager Step 3. Choose the Console position to
(UEM) can change the state of sites and the status disable by highlighting the correct
shows up in the UEM. To accomplish this, the current device, right clicking and selecting
state of a Console site will be displayed and using the "Issue Command".
UEM - "Issue Command" feature, it will be changed.
Step 4. Disable the Application Platform or
VPM-Dispatch Application
SETUP (depending on the console type)
for the Console from the window
and select "Apply".
Select the Physical Sites object in the UEM tree for the
site to be tested. Step 5. Observe that the UEM shows that
the Application Platform or VPM-
Dispatch Application is now
VERSION #1.010 Disabled and is User Requested.
Verify that the Console Site
container shows WARNING.
Step 6. Choose the Console position and

enable by highlighting the correct
device, right clicking and selecting
"Issue Command".
Step 7. Enable the Application Platform or

VPM-Dispatch Application for the
Console from the window and
select "Apply".
Step 8. Observe that the UEM shows that

the Application Platform or VPM-
Dispatch Application is now
Enabled and is User Requested.
Verify that the Console Site
container returns to a green
status.
Step 9. Close the open windows.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Add RADIO-1,RADIO-2,RADIO-3,

Affiliation Display and RADIO-4 to the Affiliation
Display.
1. DESCRIPTION Step 2. Verify that RADIO-1 and RADIO-2

show they are affiliated to SITE 1
and TALKGROUP 1.
Affiliation Display is a Private Radio Network
Management (PRNM)application that monitors the Step 3. Verify that RADIO-3 and RADIO-4
mobility of radios for a particular zone. Mobility show they are affiliated to SITE 2
describes how radio users travel between different and TALKGROUP 2.
sites in a zone and how they communicate with other
members of their assigned talkgroup or even with Step 4. Change the talkgroup of RADIO-1
members outside of their talkgroup. A radio can be and RADIO-2 to TALKGROUP 2.
viewed in more than one zone. As a radio roams from
one site to another or changes talkgroups, Affiliation Step 5. Verify that RADIO-1 and RADIO-2's
Display updates and displays the affiliation and de- affiliated talkgroup changes to
affiliation information for a monitored radio. This TALKGROUP 2 on the Affiliation
information can be useful for the troubleshooting and Display.
tracking of radios in the system and for monitoring the
movement of traffic within a zone. Step 6. Change the site of RADIO-3 and
The Affiliation Display is divided into three sections: RADIO-4 to SITE 1.
Site Viewer, Talkgroup Viewer, and Radio Viewer.
- The Site Viewer displays the number of talkgroups Step 7. Verify that RADIO-3 and RADIO-4's
and number of radios affiliated to that site. affiliated site changes to SITE 1
- The Talkgroup Viewer displays how many radios are on the Affiliation Display.
affiliated to that talkgroup and the number of sites at
which the talkgroup has radios affiliated.
- The Radio Viewer window displays affiliation
information for a custom list of radios.
SETUP
Pass____ Fail____
VERSION #1.040

RFP# 101216
December 16, 2010

Step 1. On a UEM client session, select

UEM - UEM User actions are logged Tools from the menu bar and then
System Administration. The
Administration Menu window
1. DESCRIPTION opens up.
Step 2. In the System Administration

This test validates that Unified Event Manager (UEM) window, click on Audit Trails.
user actions are logged by the system.
Step 3. Verify the Authentication Audit Log
is displayed. The following
SETUP information is displayed for each
entry: User Name, Operation,
Audit Time, Severity, Category,
NMclient 01 - UEM client session active. and Audited Object. User actions
recorded include: Login, Logout,
(Note: If the Authentication Audit Log has been cleared Discovery, Synchronization,
there will only be the event to clear the log.) Device Deletion, Diagnostics,
Telnet, and Manage/Unmanage.
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the UEM, right click on a CCGW
managed resource and select SNMP-
Unified Event Manager (UEM) - Diagnostics - Node then the Issue Command
option.
CCGW
Step 2. The command window opens for the
CCGW managed resource with the
1. DESCRIPTION following commands available:
Disable and Enable.
The purpose of this test is to confirm diagnostic Step 3. Verify the conventional channel is
commands are sent to a Conventional Channel operational using the two radios
GateWay (CCGW) and the proper status is reported at programmed to the channel.
the Unified Event Manager (UEM).
Step 4. Select Disable and click the Apply
All commands are initiated from the UEM. button.

displayed in the command window.
SETUP After the command is executed, the
CCGW is disabled. The event is
displayed in the Network Event
RADIO-1 CCH1 Browser. An alarm is displayed in the
RADIO-2 CCH1 Alarm Browser.
CONSOLE-1 CCH1
Step 6. Attempt to place a conventional call
using the two radios. The call audio
NMclient01 - UEM session up and running in the
will not be heard at the console. The
Network View. resource at Console-1 will show that
the resource is unavailable.
VERSION #1.070 Step 7. Select Enabled and click the Apply

button.

displayed in the command window.
After the command is executed, the
CCGW is enabled. The event is
displayed in the Network Event
Browser.
Step 9. Attempt to place a conventional call

using RADIO-1. The call should now
be heard by CONSOLE-1 as well as
RADIO-2.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that the console is able to initiate

Configuration Management - External Paging paging Tones on the Selected
channel.
Capabilities (MCC 7500 Systems only)
Step 2. Change the "External Paging Capability
Enabled" flag to NO in this Console
1. DESCRIPTION User's Capability Profile via the User
Configuration Manager.
The User Configuration Manager (UCM) controls the Step 3. Verify that an indication is provided via
parameters for all radio users and dispatchers on the the console's Elite GUI status bar
system. Within the Subscriber section, the Console indicating to the dispatcher that new
Talkgroup Capability profile enables the network configuration information is available.
manager to tailor a Console's Talkgroup capabilities.
Note: The parameter changes affect the console user Step 4. Verify that even after the above
indication the console dispatcher is
profile only after the logged-in dispatchers log out and
still able to initiate paging tones.
then back in to the dispatch application.
Step 5. Verify that after the console dispatcher
logs out of the Elite GUI application
SETUP and then logs back in that the console
dispatcher is no longer able to initiate
paging Tones on the Selected
Console User1 is logged on and has the "External channel.
Paging Capability Enabled" set to YES in the
Step 6. Change the "External Paging Capability
appropriate Console User Capability Profile. The
Enabled" flag back to YES in this
console has affiliated to analog conventional voice Console User's Capability Profile via
channel CCHl1 and this channel is Selected. the User Configuration Manager.
Step 7. Verify that an indication is provided via

VERSION #1.050 the console's Elite GUI status bar
indicating to the dispatcher that new
configuration information is available.
Step 8. Verify that even after the above

indication the console dispatcher is
still unable to initiate paging tones.
Step 9. Verify that after the console dispatcher

logs out of the Elite GUI application
and then logs back in that the console
dispatcher is now able once again to
initiate paging Tones on the Selected
channel.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Double-click the Unified Network
Configurator (UNC) shortcut on the
Unified Network Configurator (UNC) Device desktop, and a VoyenceControl client
session will launch. Login to the UNC
Management - Channel Parameter
using the appropriate username and
password.
1. DESCRIPTION Step 2. Double-click the UNC Wizard (UNCW)
shortcut on the desktop, and a UNC
Wizard client session will launch. Log
The Unified Network Configurator (UNC) allows users into the UNC Wizard using the
to perform various functions on the system. This test appropriate username and password.
will cover the modification of a parameter on a device.
Step 3. Using the UNC Wizard, select a channel
For this test, the control channel capability for a from a Repeater Site to update. (Note:
channel will be modified. It is recommended to use a repeater
site because the change will
propagate much quicker because
It is important to note that ASTRO releases prior to 7.8
there are less devices being updated
this change will impact the control channel capability than a Simulcast Site.)
for the site only when it is operating in Site Trunking. In
order to modify the operation for Wide Area, the Step 4. From the wizard, change the Home /
change will need to be made in the Zone Configuration Control Channel Capable parameter
Manager (ZCM). It is recommended that the change for the channel, and submit the
be made in both the Zone Configuration Manager change.
(ZCM) and UNC for live systems. For the ASTRO 7.8
release the ZCM is eliminated and the changes can be Step 5. Start a UNC client session and open the
made using the Unified Network Configurator Wizard. Schedule Manager. Configuration
remedy jobs are immediately added to
the Schedule Manager with a status
of Pending for all affected target
SETUP devices.
Step 6. Highlight the pending jobs related to this

No prior setup is required. update, and approve the remedy jobs
in the Schedule Manager. The
remedy jobs are approved and
indicate a status of running in the
VERSION #1.070 Schedule Manager. Refresh the
Schedule Manager view until the jobs
are completed.
Step 7. View the configuration data for the

device and verify that the Home /
Control Channel Capability has been
updated in the devices current
configuration.
Step 8. Change the Home / Control Channel

Capability parameter for the channel
back to the initial value.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. On a UEM client session, click on

UEM - Manual Synchronization - Site the Network Database node tree
Controller in the navigation window.
Step 2. Right click on an Site Controller,

1. DESCRIPTION select SNMP-Node, and then
select Synchronize.
The purpose of this test is to manually synchronize Step 3. The Synchronization Job Status
state with agents within the system using the Unified window appears with the Job
Event Manager (UEM). Status ID.
Manual synchronization provides a fallback to obtain Step 4. Click on the View Job Status button.
object status after a network interruption.
Step 5. The Job Status View window opens
providing the Job ID, Status,
SETUP Owner, Type, Target, Submit
Time, End Time, and Additional
Information for all the jobs.
NMclient01 - UEM session up and running.
Step 6. Locate the Synchronization job
initiated in step 2 and click on the
VERSION #1.110 job. Verify the Synchronization job
is listed with a status of Success.
Step 7. Click on the View Log button. A

summary of the Synchronization
job details is provided in the job
log.
Step 8. Locate the Site Controller in the

Network Database View. The
correct Severity property of the
device is displayed.
Pass____ Fail____

RFP# 101216
December 16, 2010

6.3 Radio Control Manager
(RCM) Features

RFP# 101216
December 16, 2010

Radio Control Manager (RCM) Features 2. TEST
Step 1. Select the Command menu and

Radio Check then select the Radio Check item
to open the Radio Check window.
1. DESCRIPTION Step 2. Enter the ID or alias of RADIO-2 into

the entry box and click the Apply
button.
Radio Check is a RCM command used to verify that a
radio is active in the trunking system. The Radio Step 3. Observe the radio is polled and the
Check command causes the Zone Controller to poll for current radio information is
the radio requesting that the radio re-affiliate. When displayed on the RCM.
the radio re-affiliates, the RCM then has the
knowledge that the radio is powered on and within Step 4. Turn off RADIO-1.
system range. If the radio is involved in a
conversation, whether group or interconnect, the RCM Step 5. Enter the ID or alias of the RADIO-1
application displays a message to that effect. into the entry box and click the
Apply button.
The information displayed by the RCM in response to
the Radio Check command is: current talkgroup Step 6. Observe that the RCM displays
affiliation, the multigroup that the talkgroup is attached "Radio Not Found."
to (assuming the talkgroup belongs to a multigroup),
and the site where the radio is affiliated. If the radio Step 7. Depress and hold the PTT button of
does not respond to the Radio Check command, a RADIO-2 until instructed to
message to that effect displays. release.
Step 8. Enter the ID or alias of RADIO-2 into

SETUP the entry box and click the Apply
button. Observe that a busy for
the radio is displayed on the RCM.
RADIO-1 - SITE - SITE 1 Step 9. Release the PTT button on RADIO-
Step 10. Observe the radio is polled
and the current radio information
VERSION #1.100 is displayed on the RCM.
Pass____ Fail____

RFP# 101216
December 16, 2010

Radio Control Manager (RCM) Features
2. TEST
Dynamic Regrouping (Single Site) Step 1. With the RCM open from the
Commands menu item select the
Radio Commands item to open
1. DESCRIPTION the command window. Choose
Dynamic Regrouping allows the RCM to assign Regroup.
individual radios operating in different talkgroups to a
temporary talkgroup via the Regroup command. Step 2. Enter TALKGROUP 3 in the target
Network managers or supervisors can override field.
individual radio talkgroup selections by steering
regrouped subscribers to a new talkgroup containing Step 3. Enter the IDs or aliases of RADIO-1,
users which need to communicate on a temporary RADIO-2, RADIO-3 and RADIO-4.
basis. After receiving a Regroup command, a radio will
ignore the current setting of the talkgroup selector and Step 4. Once all desired radio information is
move to the target talkgroup specified in the Regroup entered and appears in the
command. Unless the supervisor issues a LOCK command window click the
command, the radio user can deselect the target Regroup button to initiate the
talkgroup by selecting another talkgroup using the command.
radio selector. A unique location on the radio selector
is reserved for the target talkgroup following a Step 5. Observe all radios are regrouped
Regroup command. and are able to communicate on
TALKGROUP 3.
Dynamic Regrouping assignments can be initiated
rapidly, but not instantaneously. Regrouping is best Step 6. Switch the Subscriber to the
suited for planned activities or occasional changes Dynamic Regroup channel to
from normal routines. It is not intended for immediate acknowledge the group request.
responses such as highspeed chases or for a rapid
deployment on a per incident basis. Step 7. Observe that the radios are able to
select different talkgroups and are
Regrouped radios receiving a second Regroup not locked onto the regrouped
command will move to the new target talkgroup mode. Note- The Talkgroup
specified in the second command. When a regrouped selector knob has to be set to the
radio receives a Regroup command, all information dynamic regroup position before
pertaining to the previous Regroup command is lost. A switching to any other talkgroup.
Cancel Regroup command or a Revert returns an
individual radio to its normal operation. Step 8. Observe that the Regroup task
Note - RCM user must be attached to primary and appears in the Command Monitor
target talkgroup. window.
SETUP Step 9. Issue a Selector Lock command all

RADIO-1 - TALKGROUP 1 four radios and verify their
RADIO-1 - SITE - SITE 1 selectors have been locked.
RADIO-2 - TALKGROUP 1 Step 10. Revert both commands and
RADIO-2 - SITE - SITE 1 verify the radios have returned to
RADIO-3 - TALKGROUP 2 normal operation.
VERSION #1.040

RFP# 101216
December 16, 2010

Step 1. From the Radio Control Manager

Selective Radio Inhibit select the Commands menu and
then select the Radio Commands
item in the menu to open the
1. DESCRIPTION Command Window.
Step 2. Enter the IDs or aliases of RADIO-1.

The INHIBIT command issued by the Radio Control
Manager (RCM) disables a radio, preventing it from Step 3. Select "Selective Inhibit" from the
transmitting or receiving any audio. All of the radio's command pull down menu.
functionality ceases while a radio is inhibited by the
RCM. Once inhibited, the radio cannot be used to Step 4. Once all desired radio information is
monitor voice channels or for any other radio user entered and appears in the
initiated activity. Note that an inhibited radio still command window click the submit
monitors the control channel so that it can be re- button to initiate the command.
enabled with the Cancel Inhibit command. Upon
receiving the Cancel Inhibit command from the RCM, Step 5. Observe RADIO-1 is inhibited and
the radio returns to its normal operation. appears to be dead.
Step 6. Observe that the Inhibit task

SETUP appears in the Command Monitor
window.
RADIO-1 - TALKGROUP 1 Step 7. Cancel the Inhibit by selecting the

RADIO-1 - SITE - SITE 1 task in the Command Monitor
window and clicking the Revert
button to submit the task.
VERSION #1.060
Step 8. Observe that the Cancel Inhibit task
appears in the Command Monitor
window and that RADIO-1 is
returned to normal operation.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Open the Radio Control Manager

Emergency Alarm Display (RCM) windows and verify that the
Emergency Alarm window is
visible. If it is not, go to the View
1. DESCRIPTION menu and select it bringing it into
the RCM viewable area.
The emergency call information that is displayed on Step 2. Initiate an Emergency Alarm from
the Radio Control Manager (RCM) includes the radio RADIO-1.
alias of the radio that initiated the Emergency Alarm,
the talkgroup that the radio was affiliated to at the time Step 3. Observe that the RCM receives the
the alarm was sent, and the time the alarm was Emergency Alarm.
received.
Step 4. Acknowledge the Emergency by
selecting the Emergency in the
SETUP window and clicking on the
Respond button.
RADIO-1 - TALKGROUP 1 Step 5. Verify the window displays the radio

RADIO-1 - SITE - SITE 1 alias, the talkgroup, and the time
RADIO-2 - TALKGROUP 1 the alarm was received.
Step 6. Again, select the displayed
One RCM is required which has TALKGROUP 1 Emergency and click the Delete
attached to it. button to clear the emergency.
Step 7. Reset the radio by holding the

VERSION #1.100 Emergency button until the radio
clears.
Step 8. Repeat Steps 1-7 using RADIO-2.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Submit a Dynamic Regroup

Radio Snapshot command for RADIO-1 and
RADIO-3 to be regrouped to
TALKGROUP 3.
1. DESCRIPTION
Step 2. At the RCM, initiate the Snapshot
command for RADIO-1.
Snapshot is a RCM command used to retrieve
information about an individual radio. Information Step 3. Verify that the RCM shows RADIO-1
provided by the RCM application in response to the affiliated to SITE 1 and that its
Snapshot command includes: the serial number of the current Regroup state is
radio, current talkgroup/multigroup and site affiliations; "Regroup."
the Regroup, Inhibit, and Selector Lock state of the
radio. Snapshot information is taken from the system Step 4. At the RCM, revert the dynamic
databases. The Snapshot command does not initiate regrouping on RADIO-1 and
any communication with the target radio. RADIO-3.
Note - Radios are not required to be locked to a Step 5. Initiate the Snapshot command for
specific site for this test. RADIO-1.
Step 6. Verify RADIO-1 shows an affiliation

SETUP to SITE 1 and that its current
Regroup state is "Cancel
Regroup."
RADIO-1 - SITE - SITE 1 Step 7. At the RCM, inhibit RADIO-2 and
RADIO-2 - TALKGROUP 1 then initiate the Snapshot
RADIO-2 - SITE - SITE 2 command for RADIO-2.
RADIO-3 - SITE - SITE 3 Step 8. Verify RADIO-2 shows an affiliation
to SITE 2 and that its current
* RADIO-1 and RADIO-3 must be programmed with Inhibit state is "Selective Inhibit."
Dynamic Regrouping capability.
Step 9. At the RCM, revert RADIO-2 and
*Make sure Radio Users are configured with a "Radio then initiate the Snapshot
Primary Talkgroup Assignment" in the UCM. command for RADIO-2.
Step 10. Verify RADIO-2 shows an

VERSION #1.050 affiliation to SITE 2 and that its
current Inhibit state is "Cancel
Inhibit."
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. With the RCM open from the

Storm Plans (Single Site) Commands menu item select the
Storm Plan item to open the
Storm Plan Window.
1. DESCRIPTION
Step 2. Select the Storm Plan.
Storm Plans represent any number of preprogrammed Step 3. Click on OK or Apply to invoke the
Dynamic Regrouping combinations constructed in Storm Plan.
advance to anticipate a unique need, such as a
disaster, or to make a needed adjustment for an Step 4. Observe that the Storm Plan
infrequent yet repeated event, like a parade or appears in the Command Monitor
election. When implemented, a Storm Plan will window.
automatically assign individual radios operating in
different talkgroups to a temporary talkgroup, Step 5. Observe RADIO-1 and RADIO-2 are
containing the radios specified by the stored Dynamic regrouped.
Regrouping command. Storm Plans are deactivated
by selecting the revert option in the Command window. Step 6. Initiate a call from RADIO-1.
Note - Radios are not required to be locked to a Step 7. Observe that RADIO-2. RADIO-3
specific site for this test. and RADIO-4 are able to listen to
the call.
SETUP Step 8. Observe that RADIO-1, RADIO-2,

RADIO-3 and RADIO-4 are able
to initiate and receive calls on
RADIO-1 - TALKGROUP 1 TALKGROUP 2.
RADIO-2 - TALKGROUP 1 Step 9. Un-regroup the radios by selecting
RADIO-2 - SITE - SITE 1 the task in the Command Monitor
RADIO-3 - TALKGROUP 2 window and clicking on the Revert
RADIO-3 - SITE - SITE 1 button to submit the task.
RADIO-4 - SITE - SITE 1 Step 10. Observe that the regrouping
of the radios is now dissolved.
Create a storm plan in the UCM that regroups RADIO-
1 and RADIO-2 to TALKGROUP 2.
Pass____ Fail____
VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. Open the Radio Control Manager

Emergency Alarm Display (Single Site) (RCM) windows and verify that the
Emergency Alarm window is
visible. If it is not, go to the View
1. DESCRIPTION menu and select it bringing it into
the RCM viewable area.
The emergency call information that is displayed on Step 2. Initiate an Emergency Alarm from
the Radio Control Manager (RCM) includes the radio RADIO-1.
alias of the radio that initiated the Emergency Alarm,
the talkgroup that the radio was affiliated to at the time Step 3. Observe that the RCM receives the
the alarm was sent, and the time the alarm was Emergency Alarm.
received.
Step 4. Acknowledge the Emergency by
selecting the Emergency in the
SETUP window and clicking on the
Respond button.
RADIO-1 - TALKGROUP 1 Step 5. Verify the window displays the radio

RADIO-1 - SITE - SITE 1 alias, the talkgroup, and the time
RADIO-2 - TALKGROUP 1 the alarm was received.
Step 6. Again, select the displayed
One RCM is required which has TALKGROUP 1 Emergency and click the Delete
attached to it. button to clear the emergency.
Step 7. Reset the radio by holding the

VERSION #1.060 Emergency button until the radio
clears.
Step 8. Repeat Steps 1-7 using RADIO-2.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select the Command menu and

Radio Check (Single Site) then select the Radio Check item
to open the Radio Check window.
1. DESCRIPTION Step 2. Enter the ID or alias of RADIO-2 into

the entry box and click the Apply
button.
Radio Check is a RCM command used to verify that a
radio is active in the trunking system. The Radio Step 3. Observe the radio is polled and the
Check command causes the Zone Controller to poll for current radio information is
the radio requesting that the radio re-affiliate. When displayed on the RCM.
the radio re-affiliates, the RCM then has the
knowledge that the radio is powered on and within Step 4. Turn off RADIO-1.
system range. If the radio is involved in a
conversation, whether group or interconnect, the RCM Step 5. Enter the ID or alias of the RADIO-1
application displays a message to that effect. into the entry box and click the
Apply button.
The information displayed by the RCM in response to
the Radio Check command is: current talkgroup Step 6. Observe that the RCM displays
affiliation, the multigroup that the talkgroup is attached "Radio Not Found."
to (assuming the talkgroup belongs to a multigroup),
and the site where the radio is affiliated. If the radio Step 7. Depress and hold the PTT button of
does not respond to the Radio Check command, a RADIO-2 until instructed to
message to that effect displays. release.
Step 8. Enter the ID or alias of RADIO-2 into

SETUP the entry box and click the Apply
button. Observe that a busy for
the radio is displayed on the RCM.
RADIO-1 - SITE - SITE 1 Step 9. Release the PTT button on RADIO-
Step 10. Observe the radio is polled
and the current radio information
VERSION #1.020 is displayed on the RCM.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. With the RCM open from the

Storm Plans Commands menu item select the
Storm Plan item to open the
Storm Plan Window.
1. DESCRIPTION
Step 2. Select the Storm Plan.
Storm Plans represent any number of preprogrammed Step 3. Click on OK or Apply to invoke the
Dynamic Regrouping combinations constructed in Storm Plan.
advance to anticipate a unique need, such as a
disaster, or to make a needed adjustment for an Step 4. Observe that the Storm Plan
infrequent yet repeated event, like a parade or appears in the Command Monitor
election. When implemented, a Storm Plan will window.
automatically assign individual radios operating in
different talkgroups to a temporary talkgroup, Step 5. Observe RADIO-1 and RADIO-2 are
containing the radios specified by the stored Dynamic regrouped.
Regrouping command. Storm Plans are deactivated
by selecting the revert option in the Command window. Step 6. Initiate a call from RADIO-1.
Note - Radios are not required to be locked to a Step 7. Observe that RADIO-2. RADIO-3
specific site for this test. and RADIO-4 are able to
communicate with one another.
SETUP Step 8. Un-regroup the radios by selecting

the task in the Command Monitor
window and clicking on the Revert
RADIO-1 - TALKGROUP 1 button to submit the task.
RADIO-2 - TALKGROUP 1 Step 9. Observe that the regrouping of the
RADIO-2 - SITE - SITE 2 radios is now dissolved.
Pass____ Fail____
Create a storm plan in the UCM that regroups RADIO-
1 and RADIO-2 to TALKGROUP 2.
VERSION #1.060

RFP# 101216
December 16, 2010

Radio Control Manager (RCM) Features
2. TEST
Dynamic Regrouping Step 1. With the RCM open from the

Commands menu item select the
Radio Commands item to open
1. DESCRIPTION the command window. Choose
Regroup.
Dynamic Regrouping allows the RCM to assign
individual radios operating in different talkgroups to a Step 2. Enter TALKGROUP 3 in the target
temporary talkgroup via the Regroup command. field.
Network managers or supervisors can override
individual radio talkgroup selections by steering Step 3. Enter the IDs or aliases of RADIO-1,
regrouped subscribers to a new talkgroup containing RADIO-2, RADIO-3 and RADIO-4.
users which need to communicate on a temporary
basis. After receiving a Regroup command, a radio will Step 4. Once all desired radio information is
ignore the current setting of the talkgroup selector and entered and appears in the
move to the target talkgroup specified in the Regroup command window click the
command. Unless the supervisor issues a LOCK Regroup button to initiate the
command, the radio user can deselect the target command.
talkgroup by selecting another talkgroup using the
radio selector. A unique location on the radio selector Step 5. Observe all radios are regrouped
is reserved for the target talkgroup following a and are able to communicate on
Regroup command. TALKGROUP 3.
Dynamic Regrouping assignments can be initiated Step 6. Switch the Subscriber to the
rapidly, but not instantaneously. Regrouping is best Dynamic Regroup channel to
suited for planned activities or occasional changes acknowledge the group request.
from normal routines. It is not intended for immediate
responses such as highspeed chases or for a rapid Step 7. Observe that the radios are able to
deployment on a per incident basis. select different talkgroups and are
not locked onto the regrouped
Regrouped radios receiving a second Regroup mode. Note- The Talkgroup
command will move to the new target talkgroup selector knob has to be set to the
specified in the second command. When a regrouped dynamic regroup position before
radio receives a Regroup command, all information switching to any other talkgroup.
pertaining to the previous Regroup command is lost. A
Cancel Regroup command or a Revert returns an Step 8. Observe that the Regroup task
individual radio to its normal operation. appears in the Command Monitor
window.
Note - RCM user must be attached to primary and
target talkgroup. Step 9. Issue a Selector Lock command all
SETUP four radios and verify their
RADIO-1 - TALKGROUP 1 selectors have been locked.
RADIO-1 - SITE - SITE 1 Step 10. Revert both commands and
RADIO-2 - TALKGROUP 1 verify the radios have returned to
RADIO-2 - SITE - SITE 2 normal operation.
RADIO-3 - SITE - SITE 3 Pass____ Fail____
VERSION #1.060

RFP# 101216
December 16, 2010

Step 1. Initiate a Status transmission from

Radio Status RADIO-1.
Step 2. Verify the RCM displays the proper

1. DESCRIPTION Status text.
This optional feature allows the Radio Console

Manager to view status information sent in by
subscribers. Statuses are used to indicate the Radio
operator's operational state (e.g. off duty). The
information that will be displayed includes the radio
alias, talkgroup alias, hour and minute time stamp,
status number or message number, and the customer
entered translation for the specific status. Status input
is displayed in chronological order, independent of the
type of status number.
SETUP
Pass____ Fail____
* Configure RADIO-1 in the manager to use a
particular status set.
* Configure the assigned status set (via the status set

manager configuration objects) to include text
translations for a few different statuses.
* The RCM user needs to be assigned the dispatch

attachment group that matches the radio user's
assigned dispatch attachment group.
VERSION #1.020

RFP# 101216
December 16, 2010

6.4 Report Generation Tests

RFP# 101216
December 16, 2010

Report Generation Tests 2. TEST
Step 1. From the PC Application Launcher,

User Configuration Manager (UCM) Reports select User Configuration
Manager.
1. DESCRIPTION Step 2. Click on the appropriate folder to list

its contents if it is not already
open.
The User Configuration Manager report window allows
the user to generate data summaries to view Step 3. Select the object for which a report
information from the database in a Web browser or to is to be generated.
export the information as a file. The User Configuration
Manager report window shows the users all of the Step 4. Under the toolbar FILE pulldown
fields that can be included in the report. By selecting menu, select Reports.
which fields are wanted in the report and entering
selection criteria for each field, the user can restrict the Step 5. Observe a window opens allowing a
data that is retrieved. user to create a report.
Step 6. Enter all sorting data for the report

SETUP and click Generate Report.
Step 7. Observe a window appears showing

No prior setup is required for this test. the requested report.
Step 8. Close the report window.

VERSION #1.070
Step 9. Reports available to an operator
under the UCM User
Configuration Reports section are
arranged in three categories:
Subscribers, Security and System
Configuration. Run the following
reports : Under Subscribers folder,
select Radio User; Under
Security, select User; Under
System Configuration , select
System.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the PC Application Launcher,

Historical Reports select a zone.
Step 2. From that zone's menu, choose

1. DESCRIPTION Zone Historical Reports.
Step 3. From the Historical Reports Player

Performance reports can be created automatically for window that opens, select a
dynamic statistical information about the air traffic report.
activity on the system. These reports provide
assistance with system management, resource Step 4. Using the left mouse button, click on
planning, usage allocation, and monitoring. All reports the view button.
are preformatted and summarize air traffic activity for a
configured time span. Step 5. Observe a window opens allowing a
user to enter report parameters.
Note: Depending on the time span selected smaller
time intervals may not be available. Step 6. Enter all desired data for the report
and Generate Report.
SETUP Step 7. Observe a window appears showing

the requested report.
No prior setup is required for this test. Step 8. Close the report window.
Step 9. Run the following reports during

VERSION #1.110 testing: Talkgroup at Zone
Summary; User at Zone
Summary; Site Summary.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the UNC launch page menu bar
select the Tools menu and choose
Unified Network Configurator (UNC) Reports - Report Advisor. (If needed log in with
appropriate user name and
Device Inventory Report
password.)
Step 2. From the Report Advisor screen, select

1. DESCRIPTION the "Inventory Reports" header to
expand the drop down menu.
The Unified Network Configurator (UNC) reports allow Step 3. Select the desired report to run, in this
the user to generate data summaries to view case select "Devices by Model" and
information from the UNC database. Once the report is choose "Run Report".
run, the results can be viewed, printed, and exported.
This test will run a report that provides the data for a Step 4. Navigate through the available devices
specific device. until the desired device is located,
select the devices, in this case HP
Procurve Switch, to generate a report
specific to the device.
SETUP
Step 5. Drill down further by selecting the model
of the device. This should list each of
If the UNC is not open, double-click the UNC shortcut the appropriate model devices found
(UNC) on the desktop, and a VoyenceControl client in the UNC.
session will launch. When prompted, use the Login
Step 6. Select the "Disk" icon to save the report
dialog box to login to the UNC using the appropriate to the server. Select the file format for
username and password. saving the report. (Not all formats will
be viewable on the client. The
Note: The output format for the report will default to appropraite application would be
PDF. If a different output format for the report is needed to view the saved file.)
desired it will need to be selected.
Step 7. Select "Downloads" on the left side of
the screen to expand the selection.
Verify the report that was saved in the
VERSION #1.030 previous step is listed. If it was saved
as a PDF it should be available to
view on the NM client.
Step 8. View the generated report. (In some

cases the user may need to
temporarily allow pop ups on the
browser) The report can be saved to
the client by selecting "Save As" and
applying the appropriate information
for filename and location.
Step 9. Verify the generated report has

appropriate information on the
selected devices and that it can be
saved to the client.
Pass____ Fail____

RFP# 101216
December 16, 2010

6.5 System Reliability Features

RFP# 101216
December 16, 2010

System Reliability Features 2. TEST
Step 1. Verify the state of the current Zone

Redundant Zone Controller Switching – Controllers is Active or Standby in
Manual Switchover the Unified Network Configurator
(UNC). (There will be 2 Zone
Controllers in single Zone or 4 in
1. DESCRIPTION the case of DSR configured
zones.)
In a non-Dynamic System Resilience (DSR) Step 2. Using the Unified Network

configuration the Zone Controller subsystem uses two Configurator, switch the Standby
Zone Controllers in a redundant configuration. The Zone Controller to the Active
standby Zone Controller is made active either upon the state.
loss of the active Zone Controller or upon a user
command from the Unified Network Configurator. In a Step 3. Verify using UNC, UEM and
DSR configuration there are 4 Zone Controllers in a ZoneWatch (if available) that the
redundant configuration. Any one of the 4 could be standby Zone Controller becomes
active to keep the Zone Sites in Wide Area Trunking. If active and brings all sites back
using DSR configuration the Unified Event Manager wide. Wait for the Radios to settle
(UEM) will report the Zone Controller switchover in out the site affiliations.
both UEMs.
Step 4. Key RADIO 1 and verify that RADIO
2 and RADIO 3 hear the audio.
SETUP
Step 5. End the call from RADIO 1.
RADIO 1 - TG 1 Step 6. Verify that Zone Controller that was

RADIO 1 - SITE - SITE 1 previously “Active” comes back up
RADIO 2 - TG 1 to an “Enabled” and “Standby”
RADIO 2 - SITE - SITE 2 state.
RADIO 3 - TG 1
RADIO 3 - SITE - SITE 3 (In another Zone if available,
otherwise set to a random site in the same Zone.)
VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010

System Reliability Features
VERSION #1.000
Verify Continued Operation Upon Loss of 2. TEST

Prime Site Switch
Step 1. Verify that the Site is in wide area
trunking.
1. DESCRIPTION
Step 2. Fail switch 2 and verify that the Site
remains in wide area trunking.
The Simulcast Prime Site High Availability feature
enhances current operation by increasing the number Step 3. Verify that the UEM reports the
of channels available following a LAN switch failure. failure of switch 2.
These sites are configured with four LAN switches
rather than the standard two LAN switch configuration. Step 4. Verify in Zone Watch (if available)
When the same site resources are spread across four that channels on switches 1, 3
LAN switches, the failure of a single switch removes and 4 are available.
fewer resources hence improving the general
availability of resources as well as improving the Step 5. Key-up RADIO-1 on a channel
likelihood of preserving redundancy. connected to switch 1 and verify
that RADIO-2 and RADIO-3
Per current operation, these sites are expected to receive RADIO-1 audio. Repeat
preserve wide area operation upon failure of any of the this step for channels connected
switches (assumes redundant WAN links are utilized to switch 3 and 4 also.
between the master site and prime site). This test
case verifies continued wide area operation upon a
single switch failure. It also demonstrates increased
channel availability over the standard 2 LAN switch
configuration.
SETUP
Three radios are required. All three are set to the

same talkgroup.
• RADIO-1 TALKGROUP 1
• RADIO-2 TALKGROUP 1 Pass____ Fail____
Channel 2 (on switch 2) is set as the preferred control

channel. Channel 4 is the next preferred. Redundant
WAN links are configured between the master site and
prime site.
Ensure Zone Watch (if available) is setup to monitor

the sites and the Unified Event Manager (UEM) is
available for viewing faults.
Note: Switch failures may be simulated by pulling

power on the switch.

RFP# 101216
December 16, 2010

Step 1. Verify the state of the current Zone

Redundant Zone Controller Controllers is Active or Standby in
Switching/Automatic Switchover the Unified Network Configurator
(UNC). (There will be 2 Zone
Controllers in single Zone or 4 in
1. DESCRIPTION the case of DSR zones.)
Step 2. Reset the active Zone Controller via

In a non-DSR configuration the Zone Controller the Unified Event Manager (UEM)
subsystem uses two Zone Controllers in a redundant diagnostic.
configuration. The backup Zone Controller is made
active either upon the loss of the active ZC or upon a Step 3. Verify using UNC, UEM and
user command from the Unified Network Configurator ZoneWatch (if available) that the
(UNC). In a DSR configuration there are 4 Zone standby Zone Controller becomes
Controllers in a redundant configuration. Any one of active and brings all sites back
the 4 could be active to keep the Zone Sites in Wide wide. Wait for the Radios to settle
Area Trunking. If using the Dynamic Resilience Zone out the site affiliations.
configuration the Unified Event Manager will report the
Zone Controller switchover in both Unified Event Step 4. Key RADIO 1 and verify that RADIO
Managers (UEM). 2 and RADIO 3 hear the audio.
Step 5. End the call from RADIO 1.

SETUP
Step 6. Verify that Zone Controller that was
reset comes back up to an
RADIO 1 - TG 1 “Enabled” and “Standby” state.
RADIO 1 - SITE - SITE 1
RADIO 2 - TG 1
RADIO 2 - SITE - SITE 2
RADIO 3 - TG 1
RADIO 3 - SITE - Site 3 (Site 3 should be in another
Zone if applicable.)
* The Zone Controllers should be sucessfully

synchronized before performing this procedure.
Pass____ Fail____
VERSION #1.050

RFP# 101216
December 16, 2010


Multiple Control Channels RADIO-1 on TALKGROUP 1.

call.
A maximum of four channels are eligible for Step 3. Initiate a Talkgroup Call with
assignment as control channel at each site. In the RADIO-3 on TALKGROUP 2.
event that the assigned control channel fails at any
remote site, the Zone controller automatically selects Step 4. Observe that only RADIO-4 will be
one of the other control capable channels as the active able to monitor and respond to the
control channel for that site. A Control Channel call.
Preference Level can be used to rank the control
capable channels where 1 is the highest ranking and 4 Step 5. Power off the control channel at
is the lowest. SITE 1 where RADIO-1 and
RADIO-3 are affiliated.
SETUP Step 6. Observe that the control channel

rotates to the next available
channel capable of acting as a
RADIO-1 - TALKGROUP 1 control channel.
RADIO-3 - TALKGROUP 2 Step 7. Initiate a Talkgroup Call with
RADIO-4 - TALKGROUP 2 RADIO-1 on TALKGROUP 1.

VERSION #1.090 able to monitor and respond to the
call.

RADIO-3 on TALKGROUP 2.
Step 10. Observe that only RADIO-4

will be able to monitor and
respond to the call. Power up the
channel previously powered off to
return the system to normal
operation.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using CSS read the Site Controller

Simulcast Essential Subsite Operation and bring up the Site Controller
(GCP's) Status Panel service screen.
Step 2. Power down one of the control

1. DESCRIPTION channel capable stations at the
non-essential site and note that
the CSS shows the channel is
This test verifies the essential site operation within a malfunctioned and will not be
simulcast system. An essential simulcast remote site used.
is one that must have at least one control channel and
one traffic channel for the simulcast subsystem to Step 3. Repeat Step 1 for each of the other
remain trunking mode. If all control channels or all control channel capable stations
traffic channels have experienced faults at an essential or until 50% or more of the
simulcast remote site, then the entire simulcast stations have been malfunctioned.
subsystem is put into failsoft mode to ensure
communication can continue in the area covered by Step 4. Verify that the CSS shows that the
the essential simulcast remote site. When all of the disabled channels have been
wide area failsoft channels at an essential simulcast enabled at all other sites in the
remote site have experienced faults, the essential simulcast subsystem and that
simulcast remote site is malfunctioned. RADIO-1 can communicate with
RADIO-3.
SETUP Step 5. Re-power all of the control channel

capable stations at the non-
essential site.
RADIO-1 - SITE - (SIMULCAST SITE) Step 6. Power down all of the control
RADIO-2 - TALKGROUP 1 channel capable stations at the
RADIO-2 - SITE - (SIMULCAST SITE) essential site.
RADIO-3 - SITE - SITE 1 Step 7. Verify that the simulcast subsystem
is now in the failsoft mode.
* At least one of the remote simulcast sites must be
designated an essential site (availability number is set Step 8. Re-power all of the control channel
to 100%) and one must be designated a non-essential capable stations at the essential
site. site and verify the simulcast
* CSS (Configuration Service Software) must be subsystem is back in wide-area
running on a laptop computer (provided by CCSI) and trunking.
plugged into the Simulcast Site Controller.
* This test assumes that the availability number for the
non-essential site is set to the default of 50%.
VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010


Redundant Site Link Failure RADIO-1 on TALKGROUP 1.
Step 2. Observe that RADIO-2 is able to

1. DESCRIPTION monitor and respond to the call.
Step 3. Remove the WAN link from the

Communication between the Master Site and the active router at the Remote Site.
Remote Site can take place over dedicated redundant
links. The two links between the Master Site and the Step 4. Initiate a Talkgroup Call with
Remote Site operate in a hot/standby mode. The RADIO-1 on TALKGROUP 1.
system will switch to the backup link if the main LAN or
WAN link fails. Step 5. Observe that RADIO-2 is able to
Note that the Primary Site Router, if functional, will
always be the active router. The Secondary Site Step 6. Replace the WAN link connection
Router will only take over when the Primary Site that was removed in Step 3.
Router is malfunctioning.
SETUP
* The site being tested should have redundant links to

the Master Site.
Pass____ Fail____
VERSION #1.050

RFP# 101216
December 16, 2010

Step 1. Select a channel to disconnect the

Transmitter Power Failure Shutdown transmit antenna connection to
the trunked repeater. (This will
cause a high VSWR condition)
1. DESCRIPTION
Step 2. Key RADIO-1 so that the selected
channel is assigned, and verify
The repeaters can detect a loss or decrease in that the channel disables due to
transmitter output power of all trunked repeaters an alarm condition. Verify that this
connected to it. Each trunked repeater contains an alarm is reported at the Unified
internal wattmeter element. Once the forward power Event Manager (UEM).
has decreased past the threshold set, the repeater
instructs the Zone Controller to take the channel out of Step 3. Wait 30 seconds after the failure
service. If reflected power increases past the then restore the transmit antenna
threshold set, the repeater will also instruct the Zone connection to the trunked
Controller to take the channel out of service. repeater.
Once the station threshold has been exceeded and the
station taken out of service a 5 minute timer will start. Step 4. Using the station LEDs, verify that
At the timer expiration a transmitter test will start to the time it takes from the
perform a self check on the station. This self check corrected connection to the station
lasts for 20 seconds. If the station passes the self being placed back in service is
check it will be placed back into service. within 5 minutes.
Note: This test should be done on a site with more Step 5. Verify the Unified Event Manager
than 2 channels. Failsoft will occur if the test is done (UEM) also reports the station
on a 2 channel site. being back in service.
SETUP
VERSION #1.110
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using a service monitor, transmit a 1

Receiver Interference Shutdown kHz tone at the receive frequency of
any repeater.
1. DESCRIPTION Step 2. Continue to transmit the 1 kHz tone until

the controller removes the channel
from service. (The Carrier Malfunction
Time parameter timer is configurable,
Receiver interference occurs when a repeater receives
default is 50 seconds).
an unauthorized signal. In order to prevent a
disruption of communications, the affected channel will Step 3. Initiate a Talkgroup Call with RADIO-1
be disabled and removed from the system's pool of on TALKGROUP 1.
available channel resources when the undesired
carrier is detected for longer than the time-out period. Step 4. Dekey (allow the channel to end the
Once the interfering carrier disappears, the channel is call) and initiate another Talkgroup
returned to service within approximately 5 minutes. Call with RADIO-1. Verify the affected
The channel is then enabled. channel is removed from the
selection/assignment process by
repeating talkgroup calls until the
Note: The default Carrier Malfunction Timeout is 50
available channels have all been
seconds. If the default value is to be modified, the
used.
change will need to be made in the Unified Network
Configurator (UNC) for the channel(s) to be modified. Step 5. From the Unified Event Manager (UEM),
verify channel malfunction due to
interfering carrier is indicated.
SETUP
Step 6. Remove the interfering signal. Verify the
test Channel is returned to service
within five minutes and that UEM
A Service Monitor is needed to transmit a signal at the
indicates that the channel is now
receive frequency of a chosen channel. enabled.
Step 7. Initiate a Talkgroup Call with RADIO-1

VERSION #1.100 on TALKGROUP 1. Dekey (allow the
channel to end the call) and initiate
another Talkgroup Call with RADIO-1.
Repeat the calls until the test channel
has been used.
Step 8. Verify that RADIO-2 can monitor and

respond to the TALKGROUP 1 call on
the channel that has returned to
service.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Power down a voice repeater for

Station Failure any voice channel at one remote
site.
1. DESCRIPTION Step 2. Press PTT on a radio several times

to step through all available voice
channels.
When a base station repeater at one site fails due to
hardware problems, the pending call is lost and the Step 3. Verify that the disabled channel is
trunking controller removes the channel from service not used.
system wide. This failure can be created by powering
down one base station repeater.
SETUP
No set up required.
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Choose one site to test for Base

Base Station Identification Station Identification (BSI).
Step 2. Setup the service monitor to receive

1. DESCRIPTION the frequency of the BSI channel
for the particular site.
This test verifies that the repeater(s) programmed for Step 3. Monitor the service monitor until the
Base Station Identification (BSI) operation at every site Base Station Identification is
broadcasts the FCC BSI at predefined intervals broadcast.
(usually 30 minutes). To accomplish this, a service
monitor will be set up to monitor the BSI channel of a
random site and note that the Base Station
Identification is heard.
SETUP
A service monitor will be required to perform this test.
VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Using RADIO-1, key-up on a

Verify Continued Operation Upon Loss of GPS channel residing on the primary
ESS. While RADIO-1 is keyed,
fail GPS_1.
1. DESCRIPTION
Step 2. Verify RADIO-1 operation on Zone
Watch (if available). RADIO-1
Dual LAN subsites utilize two Global Positioning stays on the same channel and
System (GPS) receivers as timing reference sources the Site remains in wide area
rather than TRAK. In addition, two new modules trunking.
(“GPB 8000 Reference Distribution Modules (RDM)”)
are added to the primary GTR8000 Expandable Site Step 3. Verify that RADIO-2 and RADIO-3
Subsystem (ESS) to facilitate the switching and time receive RADIO-1 audio without
reference distribution functions at the remote sites. interruption.
The GPB 8000 Reference Distribution Modules train to
the GPS receivers and generate the output time Step 4. Verify that the UEM reports the
reference which is utilized by the Multisite Base failure of GPS_1.
Radios (MsBRs). In the event of a GPS failure, the
RDMs are capable of making a transparent transition Step 5. Dekey RADIO-1, key-up RADIO-3
from one time reference source to another without on a channel residing on the
disturbing any channels that are in service at the site. primary ESS. While RADIO-3 is
The MsBRs choose the most accurate reference being keyed, restore GPS_1.
output by each RDM.
Step 6. Verify RADIO-3 operation on Zone
This test case verifies continued wide area operation Watch (if available). RADIO-3
upon a single point of failure associated with a GPS stays on the same channel and
receiver. the Site remains in wide area
trunking.
SETUP Step 7. Verify that RADIO-1 and RADIO-2

receive RADIO-3 audio without
interruption.
Three radios are required. All three are set to the
same talkgroup. Step 8. Verify that the UEM reports the
• RADIO-1 TALKGROUP 1 recovery of GPS_1.
Ensure Zone Watch (if available) is setup to monitor

the sites and the Unified Event Manager (UEM) is
available for viewing faults.
Pass____ Fail____
Note: A GPS failure can be simulated by pulling the
GPS cable at the junction panel.
VERSION #1.000

RFP# 101216
December 16, 2010

6.6 Fault Management
Features

RFP# 101216
December 16, 2010

Fault Management Features 2. TEST
Step 1. From the Unified Network

VPM “No Console IP Address” Fault Reports Configurator (UNC), prepare the
to the Unified Event Manager (UEM) configuration file for the VPM.
Step 2. Push the configuration to the VPM.

1. DESCRIPTION
Step 3. From Unified Event Manager
(UEM), observe that the Console
This test verifies that the VPM reports the condition PC reports the link to the VPM as
when it does not have an IP address for the Console Down.
PC configured. This event is viewable in the Unified
Event Manager (UEM). Step 4. From UEM, observe that the VPM
reports a CRITICAL alarm
“Console IP address is not
SETUP configured.”
Step 5. From the UNC, prepare and push a

Voice Processing Module (VPM) configured without a new configuration which includes
valid Console IP address. the valid IP address of the
Console PC.
VERSION #1.010 Step 6. From UEM, observe that the

Console PC reports the link to the
VPM as Up, and that the
CRITICAL alarm reported by the
VPM is cleared.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that the Core Router to be

Core Router Failure Reports to the Unified tested shows up without failures
Event Manager (UEM) (normal) on UEM. The core router
is contained in the specific subnet
that it is physically collocated with
1. DESCRIPTION in the network.
Step 2. Power down the Core Router.

This test verifies that the Unified Event Manager
(UEM) alarms view is able to capture information Step 3. Observe that an alarm indicating a
about various failures at the system and zone level. Core Router failure appears on
the UEM alarms view.
A Core Router will be turned off to simulate a failure.
The system health will be monitored on UEM. Step 4. Restore power to the Core Router.
Step 5. Observe the changes to the alarm in

SETUP UEM, indicating the Core Router
is Enabling.
NMclient01 - UEM session up and running. Step 6. Observe that alarm view updates in
the UEM, indicating the Core
Router is Enabled.
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a call from RADIO-1 to

Console PC - VPM Link Failure Reports to the CONSOLE-1 to verify
Unified Event Manager (UEM) communication.
Step 2. Remove the Ethernet cable from the

1. DESCRIPTION VPM to the Console Site Ethernet
Switch.
This test verifies that the Unified Event Manager Step 3. Observe the UEM reports
(UEM) alarms view is able to capture information CommFailure alarms for the VPM
about various failures at the system and zone level.
Step 4. In addition, observe that CONSOLE-
This test simulates a Console PC to Voice Processing 1 reports the link to the VPM as
Module (VPM) link failure. Down.
Step 5. Reconnect the VPM to the Console

SETUP Site Ethernet Switch.
Step 6. Observe that UEM regains

RADIO-1 - TALKGROUP 1 communication with the VPM and
CONSOLE-1 - TALKGROUP 1 (VPM Based console) the Console PC to VPM link
recovers.
VERSION #1.030 Step 7. Initiate a call from RADIO-1 to

CONSOLE-1 to verify
communication.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that the power amp of the

Station Power Amp Failure Reports to the station to be tested has no active
Unified Event Manager (UEM) alarms against it.
Step 2. Disconnect the dummy

1. DESCRIPTION load/antenna from the station.
Step 3. Make several talkgroup calls using

This test verifies that the Unified Event Manager Radio-1 until the test station has
(UEM) alarms view is able to capture information been keyed.
about various failures at the system and zone level.
Step 4. Observe that an alarm indicating a
A station will be keyed while the output is unloaded to Power Amp failure appears on the
simulate a power amp failure. The failures will be UEM alarms view.
monitored on the UEM.
Step 5. Reconnect the dummy load/antenna
Note: For safety, either power down the station or TX disconnected in Step 3.
Inhibit it before disconnecting or re-connecting the
dummy load to prevent accidental keying of the Step 6. In approximately 5 minutes, observe
station. the changes to the alarm on the
UEM, indicating the module is
Note: This test should be done on a site with more restored to service.
than 2 channels. Failsoft will occur if the test is done
on a 2 channel site.
SETUP
Pass____ Fail____
* All Radios should be "Site Locked"
VERSION #1.070

RFP# 101216
December 16, 2010

Step 1. Remove the T1 cable(s) to the SITE

Site Path Failure Reports to the Unified Event 1 router(s) (If Simulcast, this
Manager (UEM) refers to the Prime Site router(s))
at the site where RADIO-1 is
affiliated. Be certain to remove the
1. DESCRIPTION T1 cable from both routers if
redundant site links are being
utilized.
This test verifies that the Unified Event Manager
(UEM) alarms view is able to capture information Step 2. Observe the UEM reports
about various failures at the system and zone level. CommFailure alarms for the
devices at the affected site.
This test simulates a microwave failure by removing a
customer selected site data link and monitoring the Step 3. In addition, observe that the site is
alerts. now in the Site Trunking mode.
Note: If using a Simulcast site, this test refers to the Step 4. Reconnect the T1 cable(s)
Prime Site links. While failures would be seen at the disconnected in Step 1.
subsite level if a Subsite link were failed, the site would
not drop into Site Trunking. Step 5. Observe the site returns to the Wide
Area Trunking mode.
SETUP Step 6. Observe the topology and alarms

that appear on the UEM indicating
the site has recovered.
* RADIO-1 should be "Site Locked"
VERSION #1.110
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a Talkgroup call on

MCC 7500 Console Site Control Path Failure TALKGROUP 1 by hitting the PTT
Monitored by Unified Event Manager on RADIO-1 and verify
communication with CONSOLE-1.
1. DESCRIPTION Step 2. Remove the T1 or E1 cable(s) to the

Console Site router(s) at
CONSITE 1. Be certain to remove
This test verifies that the Unified Event Manager the T1 or E1 cable from both
(UEM) is able to capture information about various routers if redundant site links are
failures at the system and zone level. being utilized.
This test simulates a failure by removing the Console Step 3. Observe the alert appears in the
Site link(s). The alerts will be monitored at the Unified UEM indicating the Console Site
Event Manager. Link has failed.
Step 4. Observe the color for the console

SETUP site container turns from green
(normal) to Black for loss of
communications.
RADIO-1 TALKGROUP 1
RADIO-1 - SITE - SITE 1 Step 5. Observe that CONSOLE-1 is no
CONSOLE-1 TALKGROUP 1 longer able to contact RADIO-1 on
CONSOLE-1 - SITE - CONSITE 1 TALKGROUP 1.
Step 6. Connect the T1 or E1 cable(s)

VERSION #1.020 previously disconnected in step 2.
Step 7. Observe that the Console is now

able to contact RADIO-1.
Step 8. Observe that the color for the site

changes to Green (normal) at the
UEM.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Observe that the CCGW1 container

Analog Conventional Voice Channel Failure is GREEN in the Unified Event
(MCC 7500 Systems only) Manager (UEM).
Step 2. Disable CONVCH1 on CCGW1.

1. DESCRIPTION
Step 3. Observe the appropriate alert
appears on the UEM Event
This test verifies that the User Event Manager (UEM) Browser and that the CCGW1
event browser is able to capture information about container changes color.
various failures at the system and zone level. An
analog conventional voice channel will be disabled and Step 4. Observe that CONSOLE-1 is no
the alerts will be monitored. longer able to contact RADIO-1.
Step 5. Disable the rest of the Analog

SETUP Conventional Channels on
CCGW1. Observe the appropriate
alerts appear in the UEM.
RADIO-1 - CONVCH1
Conventional Channel Gateway (CCGW) 1 is in Step 6. Bring each of the Channels on
service and all four of its channels are operational. CCGW1 back into service.
CONSOLE-1 - CONVCH1
Step 7. Observe the color for the CCGW1
container turns to GREEN
VERSION #1.060 (normal) in the UEM.
Step 8. Observe that CONSOLE-1 is now

able to contact RADIO-1 on
CONVCH1.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. On both routers at each end of the

Ethernet Site Link Round Trip Delay Fault Ethernet Site/Interzone Link(ie
Reports to the Unified Event Manager (UEM) Core & Site Router for a site link),
configure the IPTD(delay)
threshold for the minimum value
1. DESCRIPTION of 10ms. (Follow step 2
procedure)
When the average round trip IPTD(delay) statistic Step 2. In UNC, right-click on each router
exceeds the IPTD Fault Threshold for an Ethernet and select Set IPTD Stats
Site/Interzone Link, an event is sent to the Unified Threshold from the Saved
Event Manager (UEM). Commands. NOTE: After
selecting the Saved Commands
NOTE: This test is only valid if it is executed on a real option, the tester will have to
Ethernet Site/Interzone Link that has 10ms or more of navigate to the location of the
round trip delay. 10ms is the minimum configurable saved commands using the Up
value. button and double clicking on
folders within the folder list to get
to the following location Library
SETUP Manager>System > Motorola >
MNR
No prior setup is necessary. Step 3. After the end of next full

measurement
Note: This test will not be practical to run in staging interval(approximately 30 minutes)
because the link delays would not exceed the check for the event reporting. In
threshold in most cases even at the minimum settings. UEM, select Fault Management >
This test, if used, should be reserved for execution in Events.
the field under real conditions.
Step 4. Verify Unified Event Manager
displays an event for the
VERSION #1.020 configured routers indicating that
the IPTD Fault Threshold has
been exceeded, including the
IPTD(delay) value.
Step 5. Using the procedure in Step #1, set

the trap threshold to the
appropriate value for the Ethernet
Site/Interzone link. This value is
determined during system
planning and provisioning of the
customer backhaul network. The
default value is 40ms.
Pass____ Fail____

RFP# 101216
December 16, 2010

6.7 Integrated Voice and Data
(IV & D)

RFP# 101216
December 16, 2010

Integrated Voice and Data (IV & D) 2. TEST
Step 1. From a Host computer on the

Outbound Data Transfer Customer Enterprise Network
(CEN), generate an outbound
message to MDT-1, using the ping
1. DESCRIPTION command from the MS-DOS
prompt: ping -w 4000 <destination
IP address>
This test will demonstrate the transfer of a short
message from the host computer on the Customer Step 2. Verify that the Host computer
Enterprise Network (CEN) to a mobile user terminal. receives a response from MDT-1.
SETUP
Host computer - Connected
MDT-1 - Connected
Note: RADIO-1 must be affiliated to the system and
have a mobile data terminal (MDT) connected.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Open the Radio User record for

Context Reject - Radio Not Enabled for Data RADIO-1. Verify that the radio
Service record indicates that it is not
enabled for data service.
1. DESCRIPTION Step 2. Verify that the "PPP Link

Establishment icon" and the
"Packet Data IP icon" on the
If a Radio is not enabled for data service in the Radio are not displayed. This
SmartZone Manager, a Context Activation request indicates that the RADIO is not
from that Radio will be rejected. This test will currently context activated with
demonstrate that a Radio that is not enabled for data the system.
service will not be allowed to register with the data
system. Step 3. Verify that the Digital Link Manager
(DLM) Icon on the PC is red on
the System Status area of the
SETUP Taskbar. This indicates that a
PPP link between the PC and the
Radio is not present.
RADIO-1 - SITE - SITE 1 Step 4. Initiate a Context Activation Request
from the Radio by starting the
PPP (Point to Point Protocol) link
VERSION #1.040 assigned to the data service
network connection from the PC.
Step 5. Verify that the context request for

the Radio is unsuccessful.
Step 6. Verify that the "PPP Link

Establishment icon" is visible and
the "Packet Data IP icon" is not
visible on RADIO-1's display.
Step 7. Verify that the DLM Icon on the PC

is yellow in the System Status
area of the Taskbar.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the application server on the

Outbound Data Messaging LAN, specify the IP address of
UNIT-1.
1. DESCRIPTION Step 2. Type "Hello" in the text field.
Step 3. Press the send button.

The application server has the ability to send outbound
messages to the MDT. The application server is Step 4. Verify "Hello" is displayed on UNIT-
connected to the IV&D network via an Ethernet 1.
connection. A data message is sent out through the
data-capable base station that is connected to the
RNC.
NOTE: This test assumes the availability of an

application capable of sending text messages to a
target IP.
SETUP
No prior setup is required.

RFP# 101216
December 16, 2010

Step 1. Disable all sites on the comparator

Outbound Data Messaging via Comparator except SITE 1.
Step 2. Specify the IP address of UNIT-1 on

1. DESCRIPTION the application server.
Step 3. Type "Hello" in the text field and

The application server has the ability to send outbound press the send button.
messages to the MDT. The application server is
connected to the IV&D network via an Ethernet Step 4. Verify "Hello" is displayed at the
connection. A data message is sent out through the UNIT-1.
data-capable base station that is connected to the
RNC. Step 5. If needed, manually change RADIO-
1 to the next site on the
A comparator will vote all receive capable sites and comparator.
transmit on specified transmit capable sites. Because
a comparator will construct a signal from multiple sites, Step 6. Disable SITE 1 and enable the next
it is necessary to test each site individually. site on the comparator.
NOTE: This test assumes the availability of an Step 7. Repeat Steps 2-5 on the newly
application capable of sending text messages to a enabled site.
target IP.
Step 8. Repeat Steps 2-7 until all sites on
the comparator have been verified
SETUP individually.
Step 9. Enable all sites on the comparator.

UNIT-1/RADIO-1 - SITE 1 Repeat Steps 2-5 for a sample of
the sites.
VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that the "PPP Link

Context Deactivation - Initiated from the Establishment icon" and the
Network Manager "Packet Data IP icon" on RADIO-1
are visible. This indicates that
RADIO-1 is currently context
1. DESCRIPTION activated with the system.
Step 2. Verify that the Data Link Manager

Context deactivation covers the process used to (DLM) icon on MDT-1 is green
cancel a currently active context. Context deactivation displayed in the System Status
can be initiated either at the Radio or at the network area of the Taskbar. This
manager. For this test, the context will be deactivated indicates that a PPP (Point to
from the Network Manager. Once context deactivated, Point Protocol) link between MDT-
the Radio will be unable to use the packet data 1 and RADIO-1 is present.
service. This test will be performed from a fixed
location. Step 3. From the Network Manager, open
the Radio User record for RADIO-
1 and change the "Data Enabled"
SETUP parameter for the Radio to "No".
Step 4. Verify that RADIO-1 is context

RADIO-1 - TALKGROUP 1 deactivated.
(Mobile Data Terminal) MDT-1 - Connected Step 5. Verify that the "PPP Link
Note: RADIO-1 must be affiliated to the system and be Establishment icon" is visible and
context activated. SITE 1 must be operating in wide the "Packet Data IP icon" on the
area trunking, capable of supporting data service. Radio display is turned off.
Step 6. Verify that the DLM Icon on MDT-1

VERSION #1.050 is now yellow in the System
Status area of the Taskbar.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From a Host computer on the

Outbound Confirmed Data Transfer Customer Enterprise Network
(CEN), generate an outbound
message to MDT-1, using the ping
IP address>
message from the host computer on the Customer Step 2. Verify that the Host computer
Enterprise Network (CEN) to a mobile data terminal. receives a response from MDT-1.
SETUP
MDT-1 - Connected
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From UNIT-1, specify the IP

Inbound Data Messaging address of the application server
on the LAN.
1. DESCRIPTION Step 2. Type "Hello" in the text field.
Step 3. Press the send button.

In an IV&D system, mobile data terminals (MDT) are
connected to data-capable subscribers via a RS232 Step 4. Verify "Hello" is displayed at the
data cable. This gives the MDT the ability to send application server.
inbound data messages to a data server, which is
connected to the IV&D network via a LAN.

application capable of sending text messages to a
target IP.
SETUP
VERSION #1.060
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Power-on RADIO-1.

Context Activation
Step 2. Observer radio context activation
and can be identified by the icon
1. DESCRIPTION in the upper right-hand corner of
the radio if equipped with a
display.
Context Activation covers the process a Radio uses to
register for packet data service on the trunked system.
For this test, the Radio is configured to initiate a
context request with the system upon power-on.
SETUP
RADIO-1 - TALKGROUP 1 (Powered-off)
Note: RADIO-1 must be a XTS 5000 and must have

data capabilities enabled in the network manager.
VERSION #1.080
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From a data terminal attached to

Inbound Data Transfer RADIO-1, generate an inbound
message to a Host computer on
the network, using the ping
IP address>
message from the mobile user terminal to a host Step 2. Verify that MDT-1 receives a
computer on the CEN. For the purposes of this test, a response from the Host computer.
short message is defined as between 50 to 200 bytes.
SETUP
MDT-1 - Connected
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Disable all sites on the comparator

Inbound Data Messaging via Comparator except SITE 1.
Step 2. Specify the IP address of the

1. DESCRIPTION application server on UNIT-1.
Step 3. Type "Hello" in the text field and

In an IV&D system, mobile data terminals (MDT) are press the send button.
connected to data-capable subscribers via an RS232
data cable. This gives the MDT the ability to send Step 4. Verify "Hello" is displayed at the
inbound data messages to the data server, which is application server
connected to the IV&D network via a LAN.
Step 5. If needed, manually change RADIO-
A comparator will vote all receive capable sites and 1 to the next site on the
transmit on specified transmit capable sites. Because comparator.
a comparator will construct a signal from multiple sites,
it is necessary to test each site individually. Step 6. Disable SITE 1 and enable the next
site on the comparator.
application capable of sending text messages to a Step 7. Repeat Steps 2-5 on the newly
target IP. enabled site.
Step 8. Repeat Steps 2-7 until all sites on

SETUP the comparator have been verified
individually.
UNIT-1/RADIO-1 - SITE 1 Step 9. Enable all sites on the comparator.

Repeat Steps 2-5 for a sample of
the sites.
VERSION #1.070
Pass____ Fail____

RFP# 101216
December 16, 2010

6.8 MOSCAD Fault
Management System

RFP# 101216
December 16, 2010

MOSCAD Fault Management System 2. TEST
Step 1. Create an alarm condition by
simulating an alarm on a device in
Alarm Processing - Acknowledged Alarm the system or shorting/opening a
status input to any MOSCAD
status input module in the system.
1. DESCRIPTION Navigate to the lowest level
screen that depicts the highest
degree of alarm detail.
This segment of the test verifies that the bi-state site
alarms are processed and communicated to the Step 2. Verify that the colored status bullet
MOSCAD server. The alarms can originate from a for the associated alarm on the
device with "hard wired" physical dry contact server is blinking red and that the
interfacing or from a device connected to the "state" text is red and is displayed
MOSCAD CPU by means of an RS232 interface. for the correct alarm point and
site.
SETUP Step 3. If speakers are present, verify that

an audible indication is heard at
the server.
Step 4. Verify that the alarm displays in red

VERSION #1.030 text on the Alarm Summary
window.
Step 5. Click with the mouse on the

"acknowledge" button. Verify that
the audible indication is silenced.
Step 6. Verify that the text on the alarm

summary window of the server
changes from red to black.
Step 7. Verify that the colored status bullet

for the associated alarm on the
server remains red but stops
blinking.
Step 8. Return the alarm point to the normal

condition. Verify that the colored
status bullet for the associated
alarm returns to green.
Step 9. Verify that the text is removed from

the alarm summary window.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Choose the site to perform test.

GCP 8000 MultiSite Controller - Ethernet
Communications Failure Detection Step 2. Verify that there are no current
alarms for the chosen primary or
redundant GCP 8000.
1. DESCRIPTION
Step 3. Disconnect one of the GCP 8000s
from the Ethernet network.
The MOSCAD system will interface to the GCP 8000
via the network hub or switch. Select alarm messages Step 4. Verify that the graphic user interface
are then converted to native MOSCAD data format for indicates that the primary GCP
transmission to the MOSCAD alarm Server. has failed SNMP communications.
Note that this failure detection can
take up to 10 minutes to be
SETUP displayed.
Step 5. Acknowledge the alarm on a

No prior setup is required. MOSCAD server or client.
Step 6. Re-connect the Ethernet cable

VERSION #1.000 previously removed.
Step 7. Verify the communications alarm

clears.
Pass____ Fail____

RFP# 101216
December 16, 2010


GCP 8000 MultiSite Controller - Site Failsoft
Step 2. Verify that there are no current
alarms for the chosen GCP 8000
1. DESCRIPTION on the MOSCAD server and
client(s).
The MOSCAD system will interface to the GCP 8000 Step 3. From the UEM select the Simulcast
via the network switch. Select alarm messages are site to be tested, right click the site
then converted to native MOSCAD data format for select View Devices, then select
transmission to the MOSCAD alarm Server. "Issue Command, set the Site to
"Site Failsoft"
SETUP Step 4. Verify that a site failsoft alarm is

received at the MOSCAD server
and clients.
Step 5. Acknowledge the alarm on either
the MOSCAD server or client.
VERSION #1.030
Step 6. Return the site from failsoft.
Step 7. Verify that the site controller returns

to normal.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Choose the site to perform the test.

TRAK Communication Status Fault (UEM)
Step 2. Verify there are no current alarms
for the chosen TRAK GPS on the
1. DESCRIPTION InTouch and in the Unified Event
Manager (UEM)
The MOSCAD system connects to a TRAK 9100 GPS Step 3. Disconnect the RJ45
Standard via the RS-232 port 9 pin D connector. This communication cable (which
interface requires a dedicated MOSCAD SDM3000 ultimately connects to the TRAK
RS-232 port. The MOSCAD will periodically solicit the 9100 RS232 port) from the rear of
TRAK for its status and response messages are sent the GPS..
back to the MOSCAD SDM3000. New alarm
messages, with respect to the last received status held Step 4. Verify that the TRAK 9100
in the SDM3000, are then converted to native communication alarm is received
MOSCAD data format for transmission to the at the MOSCAD server and at the
MOSCAD alarm Server. Alarm messages are also UEM alarm manager. (This may
sent as SNMP traps from the SDM3000's IP Interface take up to 5 minutes)
to the Unified Event Manager (UEM).
the MOSCAD server or client.
SETUP
Step 6. Reconnect the communication cable
to the TRAK 9100 GPS..
No Setup Required.
Step 7. Verify that the GPS communication
status returns to normal on the
VERSION #1.010 alarm managers.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Choose the channel and site to

RSBR(Repeater Site Base Radio) / perform test.
MSBR(Multisite Base Radio) GTR8000
Diagnostics-Ext. Ref. Status Step 2. Verify that there are no current
alarms for the chosen GTR8000
on the MOSCAD Server.
1. DESCRIPTION
Step 3. Disconnect the external standard
frequency reference cable found
The MOSCAD system will connect to each repeater in the rear of the chosen station.
site base radio (RSBR) or a multisite base radio
(MSBR) using the site's Ethernet switch(es). The Step 4. Verify that the alarm is received at
MOSCAD will receive SNMP traps from the base radio the MOSCAD server and clients.
(BR) as well as solicit the BR for status. The
MOSCAD will continuously poll for any alarm Step 5. Acknowledge the alarm on
messages present in the BR. New alarm messages, MOSCAD server or clients.
with respect to the last received status held in the
SDM3000, are then converted to native MOSCAD data Step 6. Reconnect the cable at the station.
format for transmission to the MOSCAD alarm Server.
Note - this test only applies for Base Radios that use Step 7. Verify that the station returns to
an external frequency reference normal.
SETUP

RFP# 101216
December 16, 2010

Step 1. Login and Password Screen - This is the

Screen Navigation first screen displayed after a system
startup. It allows a user with the
proper login and password to access
1. DESCRIPTION the MOSCAD alarm system. Login to
MOSCAD using the appropriate user
name and password.
MOSCAD alarming tests shall be conducted from the
Step 2. System Overview Screen - The "System
MOSCAD server and clients if applicable. The alarms Overview" screen contains site names
demonstrated are to be made on the actual equipment adjacent to color status pushpins.
or punch block interface, with an exception made for Details of a particular site can be
cases where it is not practical to create an actual viewed by selecting the site name
alarm. The following will provide a brief introduction pushpin of interest. Depending on
and description of the main display screens alarm status, the color bullet will flash
encountered when navigating the MOSCAD GUI
(Graphic User Interface). Step 3. Alarm Summary Screen - Proceed to
the "Alarm Summary" screen from the
"System Overview" screen. The
"Alarm Summary" screen provides a
SETUP text display of all alarms currently in
the system. On this screen, you can
choose between alarm summary and
No prior setup is required. alarm history by selecting the "Alarm
Summary / Alarm History" button.
Also, the display can be filtered to
show alarms based on site name or
VERSION #1.080
acknowledgement status.
Step 4. Comm Screen - From the "Alarm

Summary" screen access the "Site
Comm" screen. The "Site Comm"
screen displays a combined
communication status for each site.
To view all the SDM3000s within a
site, select the icon next to the site
comm. Should the communications
path between the IP Gateway and any
SDM3000 in the system be
interrupted, it will be indicated by an
alarm present on this screen.
Step 5. Device Monitoring From the "System

Overview" screen, navigate to each
site monitored by MOSCAD in the
system. Once a particular site pushpin
has been selected, a site overview
screen will appear that indicates the
types and quantities of devices
monitored by MOSCAD at that site.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Create an alarm condition by simulating

InTouch Alarm Processing - Acknowledged an alarm on a device in the system or
Alarm shorting/opening a status input to any
MOSCAD status input module in the
system. Navigate to the lowest level
1. DESCRIPTION screen that depicts the highest degree
of alarm detail.
Step 2. Verify that the colored status bullet for

This segment of the test verifies that the bi-state site the associated alarm on the server is
alarms are processed and communicated to the blinking red and for RS232 interfaces,
MOSCAD Server. The alarms can originate from a that the "state" text is red and is
device with "hard wired" physical dry contact displayed for the correct alarm point
interfacing or from a device connected to the and site.
MOSCAD SDM3000 by means of an RS232 or
Ethernet protocol interface. Step 3. If speakers are present, verify that an
audible indication is heard at the
client.
This test will also show the equal display and
acknowledging capabilities of both MOSCAD Server
Step 4. Verify that the alarm displays in red text
and Client(s). on the pop-up Alarm Summary
window.
SETUP Step 5. Click with the mouse on the

"acknowledge" button. Verify that the
audible indication is silenced.
Step 6. Verify that the text on the alarm
changes from red (unacknowledged
VERSION #1.080 alarm) to black (acknowledged alarm).
Step 7. Verify that the colored status bullet for

the associated alarm on the server
remains red but stops blinking.
Step 8. Return the alarm point to the normal

condition. Verify that the colored
status bullet for the associated alarm
returns to green.
Step 9. Verify that the text is removed from the

alarm summary window.
Step 10. These steps should be performed once

again to verify the functionality of the
MOSCAD client(s).
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Navigate through the UEM

UEM MOSCAD Management application to view a site with the
MOSCAD SDM3000.
1. DESCRIPTION Step 2. Verify all MOSCAD devices for the

specific site have been discovered
and indicative of any failures that
MOSCAD SDM3000s report alarms to the Unified they have in the active alarms
Event Manager (UEM) via SNMP traps. The purpose view.
of this test is to verify that all MOSCAD site objects are
being managed effectively from UEM.
SETUP
NMClient01 - UEM client session running
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010


Physical Inputs/Outputs - Analog Inputs
Step 2. At the MOSCAD server or client,
select the Analog Input icon from
1. DESCRIPTION the testing site overview screen.
Step 3. Using a MOSCAD test board,

The purpose of this section is to verify that the physical manipulate the analog input
inputs and outputs that interface to the MOSCAD I/O voltage by moving the
modules are properly processed by the MOSCAD potentiometer to ¼, ½, or ¾ of the
system. Analog inputs can be tested by comparing full range.
GUI needle deflection on-screen (full scale, half scale,
2/3 scale, etc) Step 4. Verify that the needle deflection of
the MOSCAD alarm manager
Analog values can only been seen on the MOSCAD matches, with reasonable
alarm server and clients. accuracy, to that of the
potentiometer.
SETUP
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010


PSC - Station Link
alarms on the base radios for the
1. DESCRIPTION chosen PSC.
Step 3. Remove the Ethernet cable from

The MOSCAD system will interface to the PSC via the one of the base stations.
network hub or switch. Select alarm messages are
then converted to native MOSCAD data format for Step 4. Verify that an alarm is received on
transmission to the MOSCAD alarm Server. the MOSCAD server and/or
clients from the site controller.
SETUP Step 5. Acknowledge the alarm on either a

MOSCAD server or clients.
No prior setup is required. Step 6. Restore the station's link to the

network.
VERSION #1.050 Step 7. Verify that an alarm returns to

normal on the MOSCAD server
and clients.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Minimize the Wonderware Intouch

Report Generator software and select the Report
Generator icon from the Windows
desktop.
1. DESCRIPTION
Step 2. Select the "Show Report" button
shown in the application.
The Report Generator is used as a stand-alone or a
networked application to log and report alarms that are Step 3. Verify that the present date is
generated within the Wonderware Intouch database. displayed as well as any past
Alarms and Acknowledgements can be logged and alarms for which the Report
stored according to the time, site, or equipment at Generator is configured.
which the alarm originated, and the detailed summary
of filtered events can then be forwarded to a printer. Step 4. Create several alarm conditions
Report Generator is capable of Auto Archiving on a (typically 2 or 3) by simulating
monthly basis or at every 150,000 events, whichever alarms on devices in the system
occurs first, and it includes utilities to both compact or by shorting/opening a status
and repair the alarm database. input to any MOSCAD status input
module in the system.
SETUP Step 5. Verify that the alarms are displayed

on the Wonderware Intouch alarm
summary screen.
Step 6. Verify that the alarms are displayed
on the Report Generator alarm
VERSION #1.040 history report.
Pass____ Fail____

RFP# 101216
December 16, 2010


PSC - Site Failsoft
alarms for the chosen PSC.
1. DESCRIPTION
Step 3. Power off all but 2 radio channels at
the site under consideration.
The MOSCAD system will interface to the PSC via the
network hub or switch. Select alarm messages are Step 4. Verify that a site failsoft alarm is
then converted to native MOSCAD data format for received at the MOSCAD server
transmission to the MOSCAD alarm Server. and clients.

SETUP the MOSCAD server or clients.
Step 6. Return the site from failsoft.

Step 7. Verify that the station returns to
normal.
VERSION #1.020
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select a site to perform the test.

Physical Inputs/Outputs - Digital Outputs
(SDM3000) Step 2. Trigger a latched state of the output
point by selecting the "On" button
from the appropriate site's digital
1. DESCRIPTION output screen, confirming that the
screen indication changes from
"Off" to "On" for that point.
The purpose of this section is to verify that the physical
inputs and outputs that interface to the MOSCAD I/O Step 3. Verify a change of state by
modules are properly processed by the MOSCAD observing the LED on the
system. Proper processing can be verified in two MOSCAD DO module and by
ways. First, a witness can observe the I/O module observing the control back
LED indications for DO's by changes on the SDM3000 indication on the InTouch client or
panel. Second, a witness can observe the DO back server.
indication on the InTouch "Digital Output" screen.
Step 4. Return the output to its "Off"
Note that digital outputs cannot be initiated from the condition. Verify that the "On"
Unified Event Manager Client. indication on the InTouch server
returns to "Off" in addition to
DO - Digital Outputs confirming a change of state of
the MOSCAD LED.
SETUP
VERSION #1.010
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Select a site at to perform the test.

Physical Inputs/Outputs - Digital Inputs
Step 2. Short/Open the input point and
verify that an alarm indication is
1. DESCRIPTION received at the InTouch Server
and/or client(s).
The purpose of this section is to verify that the physical Step 3. Verify the active alarm is displayed
inputs and outputs that interface to the MOSCAD I/O in the UEM. (Make sure the show
module(s) are properly processed by the MOSCAD all button has been selected.)
system. All alarms demonstrated are to be made on
the punch block. Proper processing can be verified by Step 4. Return the input to its normal
observing I/O module LED indications for DI's. condition. Verify that the alarm
indication changes in the UEM
DI - Digital Inputs active alarms view.
UEM - Unified Event Manager
SETUP
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010


TRAK GPS - Power Supply Fault
1. DESCRIPTION InTouch and UEM active alarms
view.
The MOSCAD system connects to a TRAK 9100 GPS Step 3. Disconnect one of the power supply
Standard via the RS-232 port 9 pin D connector. This cables from the rear of the TRAK
interface requires a dedicated MOSCAD SDM3000 GPS
RS-232 port. The MOSCAD will periodically solicit the
TRAK for its status and response messages are sent Step 4. Verify that the alarm is received on
back to the MOSCAD SDM3000. New alarm the alarm managers.
messages, with respect to the last received status held
in the SDM3000, are then converted to native Step 5. Acknowledge the alarm on the
MOSCAD data format for transmission to the MOSCAD server or client.
MOSCAD alarm Server. Alarm messages are also
sent as SNMP traps from the SDM3000's IP Interface Step 6. Reconnect the power supply cable
to the Unified Event Manager (UEM) application. to the rear of the TRAK GPS.
Step 7. Verify that the TRAK GPS power

SETUP status returns to normal.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010


TRAK GPS - GPS Fault
1. DESCRIPTION MOSCAD server and UEM active
alarms view.
The MOSCAD system connects to a TRAK 9100 GPS Step 3. Disconnect the antenna cable from
Standard via the RS-232 port 9 pin D connector. This the TRAK GPS.
interface requires a dedicated MOSCAD RS-232 port.
The MOSCAD will periodically solicit the TRAK for its Step 4. Verify that the alarm is received at
status and response messages are sent back to the the MOSCAD server and/or client.
MOSCAD SDM3000. New alarm messages, with
respect to the last received status held in the Step 5. Acknowledge the alarm on either
SDM3000, are then converted to native MOSCAD data the MOSCAD server or client.
format for transmission to the MOSCAD Server. Alarm
messages are also sent as SNMP traps from the Step 6. Reconnect the antenna cable to the
SDM3000's IP Interface to the Unified Event Manager TRAK GPS standard.
(UEM) application.
Step 7. Verify that the TRAK GPS status
returns to normal.
SETUP
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Create an alarm condition by

InTouch Alarm Processing - Unacknowledged simulating an alarm on a device in
Alarm the system or shorting/opening a
status input to any MOSCAD
status input module in the system.
1. DESCRIPTION Navigate to the lowest level
screen that depicts the highest
degree of alarm detail.
This segment of the test verifies that the bi-state site
alarms are processed and communicated to the Step 2. Verify that the colored status bullet
MOSCAD Server. The alarms can originate from a for the associated alarm on the
device with "hard wired" physical dry contact server is blinking red and for
interfacing or from a device connected to the RS232 interfaces, that the "state"
MOSCAD SDM3000 by means of an RS232 or text is red and is displayed for the
Ethernet protocol interface. correct alarm point and site.
This test will also show the equal display and Step 3. If speakers are present, verify that
acknowledging capabilities of both MOSCAD Server an audible indication is heard at
and Client(s). the Server.
Step 4. Without acknowledging the alarm,

SETUP return the alarm point to its normal
condition.
No prior setup is required. Step 5. Verify the text on the alarm

has changed from red to blue
VERSION #1.060 indicating the alarm that has
returned to normal but remains
unacknowledged.
Step 6. Verify that the associated alarm

bullet is blinking green and yellow,
indicating an unacknowledged
alarm that has returned to normal.
An audible alert will persist until
the alarm is acknowledged.
Step 7. These steps should be performed

once again to verify the
functionality of the MOSCAD
client(s).
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the MOSCAD client, choose

RSBR(Repeater Site Base Radio) / the channel and site to perform
MSBR(Multisite Base Radio) Diagnostics - the test.
Reset Station
alarms for the chosen base radio
1. DESCRIPTION on the MOSCAD server and/or
client(s).
The MOSCAD system will connect to each repeater Step 3. Select "Station Reset".
site base radio (RSBR) or a multisite base radio
(MSBR) using the site's Ethernet switch(es). The Step 4. Verify that the station is reset by
MOSCAD will receive SNMP traps from the base radio observing the LED's on the face of
(BR) as well as solicit the BR for status. The the respective base radio.
MOSCAD will continuously poll for any alarm
messages present in the BR. New alarm messages, Step 5. Verify that the applicable alarms
with respect to the last received status held in the report to MOSCAD for the station
SDM3000, are then converted to native MOSCAD data reset.
format for transmission to the MOSCAD alarm Server.
SETUP
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

6.9 Site Trunking –
FDMA Only Sites

RFP# 101216
December 16, 2010

Site Trunking - FDMA Only Sites 2. TEST
Step 1. Place SITE 1 into the Site Trunking

Site Trunking Talkgroup Call (Single Site) mode via the Unified Event
Manager (UEM).
1. DESCRIPTION Step 2. Initiate a Talkgroup Call with

RADIO-1 on TALKGROUP 1 at
SITE 1.
When a Site goes into Site Trunking, radios with
Talkgroup Call capability will be able to communicate Step 3. Observe that only RADIO-2 will be
with other members of the same talkgroup at that able to monitor and respond to the
same site. (Members of the same talkgroup at other call. Note that RADIO-3 AND
sites will not be able to monitor those conversations.) RADIO-4 are not able to monitor
the call since they are on another
Talkgroup.
SETUP
RADIO-1 - TALKGROUP 1 SITE 1.
RADIO-2 - TALKGROUP 1 Step 5. Observe that only RADIO-4 will be
RADIO-2 - SITE - SITE 1 able to monitor and respond to the
RADIO-3 - TALKGROUP 2 call.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Trunking Call Alert mode via the Unified Event
Manager (UEM).
1. DESCRIPTION Step 2. Using RADIO-1, press the page

button.
Call Alert is a tone page that allows a user to Step 3. Enter the Unit ID of RADIO-2 with
selectively alert another radio unit. When a site is in the keypad, or scroll to the
Site Trunking, Radios at the site will only be able to location where this ID is stored.
Call Alert other radios at the same site. The initiating
radio will receive notification from the trunked system Step 4. Press the PTT to initiate the Call
as to whether or not the page was received by the Alert.
target radio.
Step 5. Verify that RADIO-2 received the
Call Alert.
SETUP
Step 6. Exit the Call Alert mode and return
to normal talkgroup mode.
VERSION #1.040
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Trunking Emergency Call and Alarm mode via the Unified Event
Manager (UEM).
1. DESCRIPTION Step 2. Simulate a busy system by disabling

This test verifies that Emergency Alarms and Calls can and one voice channel.
be initiated by subscribers when the registered site is
in Site Trunking. With all portables registered on a Site Step 3. Press the PTT on RADIO-3 and
Trunking site, a portable will initiate an Emergency hold the PTT switch until
Alarm by pressing the Emergency button. By pressing instructed to release.
the PTT, an Emergency Call will be issued and the ID
of the initiator will be displayed with an Emergency Step 4. Key RADIO-4 and observe that the
indication by the other subscribers on the same radio receives a busy.
talkgroup. Note that for site trunking, Emergency Call
operation is always Top of Queue. Step 5. Using RADIO-1, initiate an
emergency alarm followed by an
emergency call.
SETUP
Step 6. Observe that RADIO-1 cannot
transmit due to the voice channel
RADIO-1 - TALKGROUP 1 being busy.
RADIO-2 - TALKGROUP 1 Step 7. Release the PTT switch on RADIO-
RADIO-2 - SITE - SITE 1 3.
RADIO-3 - SITE - SITE 1 Step 8. Observe that RADIO-1 can now
RADIO-4 - TALKGROUP 3 proceed with the call and RADIO-
RADIO-4 - SITE - SITE 1 2 receives the call. Also observe
that the display on RADIO-2
* All Radios should be "Site Locked" denotes an emergency and the ID
of the unit sending the
emergency.
VERSION #1.040
Step 9. End the emergency call and verify
that RADIO-4 gets a callback.
Step 10. Restore all channels to

service.
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Trunking Continuous Assignment mode via the Unified Event
Updating Manager (UEM).
Step 2. Turn OFF RADIO-1.

1. DESCRIPTION
Step 3. Initiate a Talkgroup Call using
RADIO-2.
When a talkgroup is assigned a voice channel, the site
controller continues to transmit the channel Step 4. While the Talkgroup Call is in
assignment on the control channel for the duration of progress, turn on RADIO-1.
the Talkgroup Call. Radios coming into use on the
system are automatically sent to voice channels with Step 5. Observe that RADIO-1, which was
conversations in progress involving their selected just brought back into service,
talkgroups. This is demonstrated for a site in Site joins the Talkgroup Call already in
Trunking. progress.
Step 6. Release the PTT of RADIO-2.

SETUP
Step 7. Switch RADIO-1 to TALKGROUP 2.
RADIO-1 - TALKGROUP 1 Step 8. Initiate a Talkgroup Call using

RADIO-1 - SITE - SITE 1 RADIO-2.
RADIO-2 - SITE - SITE 1 Step 9. While the Talkgroup Call is in
RADIO-3 - TALKGROUP 1 progress, turn RADIO-1 back to
* All Radios should be "Site Locked" Step 10. Observe that RADIO-1,
which was just set back to
TALKGROUP 1, joins the
VERSION #1.030 Talkgroup Call already in
progress.
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. From the UEM set the status of

Site Trunking Wide Area Recovery SITE 1 to Wide Area and clear
any system errors that may have
placed SITE 1 into Site Trunking.
1. DESCRIPTION
Step 2. Verify that the status of SITE 1 in
ZoneWatch (if available) and UEM
A site in Site Trunking will transition to Wide Area reflect that SITE 1 has
Trunking when all failures have been cleared and transitioned into Wide Area
when the Unified Event Manager (UEM) has set the Trunking.
sites status to Wide Area.
Step 3. Verify that RADIO-1 and RADIO-2
All subscribers should transition from Site Trunking to no longer display Site Trunking.
Wide Area Trunking and continue to process calls.
Step 4. Verify communications between
RADIO-1 and RADIO-2.
SETUP
Step 5. Verify that ZoneWatch (if available)
can now monitor the status of
Site needs to be placed in Site Trunking via the UEM

VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Set the Failure Random Holdoff

Site Trunking Roaming to Wide Area Sites Time (FRHOT) setting for SITE 1
to 1 minute. (This can be found in
the Zone Configuration Manager
1. DESCRIPTION for releases prior to 7.8 and in the
Unified Network Configurator
Wizard in ASTRO 7.8 and later
Radios at a site that goes into Site Trunking will releases.)
attempt to roam to a site in Wide Area Trunking so it is
not stranded at a site with limited system resources Step 2. Initiate a Talkgroup Call between
available. The parameter adjusted in the test is the RADIO-1 and RADIO-2.
Failure Random Holdoff Time setting. This timer is
used by the subscribers to set a random timer, which Step 3. Note the site that the radios are
delays subscribers from flooding an adjacent site with affiliated to on the ZoneWatch (if
registration requests. available) screen.
NOTE: This feature only works on a multi-site system. Step 4. Place the site the radios are
affiliated to into Site Trunking.
SETUP Step 5. After 1 minute, initiate a Talkgroup

Call between RADIO-1 and
RADIO-2.
RADIO-1 - SITE - SITE 1 Step 6. Observe that RADIO-1 and RADIO-
RADIO-2 - TALKGROUP 1 2 have roamed to a wide area site
RADIO-2 - SITE - SITE 1 on the ZoneWatch (if available)
screen.
*Start up a ZoneWatch (if available) session for the
site the radios are affiliated in. Step 7. Reset the FRHOT setting of SITE 1
back to the default.
*All sites should be in Wide Area at the start of this
test. Step 8. Return SITE 1 back to Wide Area.
*All radios should NOT be "Site Locked"
*The radios should have alternate site control channel

frequencies setup in the portable's control channel list.
*The portables should not be configured for "Always Pass____ Fail____

Preferred" for this site which would prevent the radios
from roaming under site trunking conditions.
VERSION #1.120

RFP# 101216
December 16, 2010


Site Trunking Talkgroup Call mode via the Unified Event
Manager (UEM).
1. DESCRIPTION Step 2. Initiate a Talkgroup Call with

SITE 1.
When a Site goes into Site Trunking, radios with
Talkgroup Call capability will be able to communicate Step 3. Observe that only RADIO-2 will be
with other members of the same talkgroup at that able to monitor and respond to the
same site. Members of the same talkgroup at other call. Note that RADIO-3 and
sites will not be able to monitor those conversations. RADIO-4 are not able this monitor
the call since the site is not in
wide area operation.
SETUP
RADIO-2 - TALKGROUP 1 Step 5. Observe that only RADIO-4 will be
RADIO-2 - SITE - SITE 1 able to monitor and respond to the
RADIO-3 - TALKGROUP 1 call.
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Trunking Private Call mode via the Unified Event
Manager (UEM).
1. DESCRIPTION Step 2. Using RADIO-1, press the Private

Call button.
Private Calls is a selective calling feature that allows a Step 3. Enter the Unit ID of RADIO-2 with
dispatcher or radio user to carry on one-to-one the keypad, or scroll to the
conversation that is only heard by the 2 parties location where this ID is stored.
involved. When a site is in Site Trunking, Radios at
the site will only be able to Private Call other radios at Step 4. Press the PTT to initiate the call.
the same site.
Step 5. Verify that at RADIO-2 only tones
are heard and the display
SETUP indicates that a call has been
received.
RADIO-1 - TALKGROUP 1 Step 6. Answer the call at RADIO-2 by

RADIO-1 - SITE - SITE 1 pressing the Private Call button.
RADIO-2 - TALKGROUP 1 Verify its display shows the ID
RADIO-2 - SITE - SITE 1 number or alias of the calling unit.
RADIO-3 - SITE - SITE 1 Step 7. Press the PTT switch on RADIO-2
and respond to the call. Note that
* All Radios should be "Site Locked" if you do not press the Private Call
button before pressing PTT, your
audio will be heard by all
VERSION #1.040 members of the talkgroup, and not
by the radio initiating the Private
Call.
Step 8. Verify only RADIO-1 hears the audio

from RADIO-2.
Step 9. End the Private Call and return to

normal talkgroup operation.
Pass____ Fail____

RFP# 101216
December 16, 2010


Site Trunking Busy Queuing and Callback all channels at SITE 1 with the
1. DESCRIPTION
RADIO-1 and observe that
If no voice channel resources are available, radios RADIO-4 receives the call. Keep
requesting channels for new conversations are placed this call in progress until instructed
in the busy queue. Users of the same priority will to end the call.
move through the queue in a FIFO (first in, first out)
sequence; however, users of higher priority will be Step 3. Key RADIO-2 and observe that the
inserted ahead of lower priority users in the queue. radio receives a busy.
the top of the busy queue gets a channel assignment Step 4. Key RADIO-3 and observe that the
and generates a callback tone. The callback alerts the radio receives a busy.
user that a channel assignment was made and
transmitting is now possible on the selected talkgroup. Step 5. End the Talkgroup Call established
in Step 2.
SETUP Step 6. Observe that RADIO-2 receives a

callback prior to RADIO-3
receiving a callback.
All radios are "Site Locked."

Pass____ Fail____
VERSION #1.090

RFP# 101216
December 16, 2010

6.10 Analog Conventional Tests

RFP# 101216
December 16, 2010

Analog Conventional Tests 2. TEST
Step 1. Power down both CCGW-1 and

Zone Controller Assigns Active Conventional CCGW-2
Channel
Step 2. Power up CCGW-1 first and then
power up CCGW-2.
1. DESCRIPTION
Step 3. Verify that CONSOLE-1 displays
CCGW-1 with a status of Main
This test will demonstrates that the Zone Controller active.
assigns the first received main / alt conventional
channel to be "in service" as active channel. Step 4. Verify from ZoneWatch (if available)
that CONVCH1 is available.
SETUP Step 5. Power down both CCGW-1 and

CCGW-2
CONSOLE-1 - CONVCH1 - CONSITE 1 Step 6. Power up CCGW-2 first and then

power up CCGW-1.
CONVSITE 1 - ZONE 1
Step 7. Verify that CONSOLE-1 displays
CCGW-1 - CONVCH1 CCGW-2 with a status of Alternate
CCGW-1 - CONVSITE 1 active.
CCGW-2 - CONVCH2
CCGW-2 - CONVSITE 1 Step 8. Verify from ZoneWatch (if available)
that CONVCH2 is available.
MAIN - CONVCH1
ALTERNATE - CONVCH2
VERSION #1.030
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Initiate a call with RADIO-1 on

Active Conventional Call During Transition to CONVCH1. Continue to transmit
Site Conventional Mode this call until the completion of the
test.
1. DESCRIPTION Step 2. Verify that CONSOLE-1 and

CONSOLE-2 hear RADIO-1
audio.
The Conventional Site Controller is an optional device
that is installed at a console site. The CSC provides Step 3. Put CONVSITE 1 into site
fallback capability for the console site and conventional mode by
conventional channels colocated with this site when disconnecting the site link.
the link between a console site and the zone controller
is lost. Such way of operating is called Site Step 4. CONVSITE 1 transitions to site
Conventional mode. conventional mode. For a short
This test will demonstrate that the active conventional period of time CONSOLE-1 and
calls are transferred to the Conventional Site CONSOLE-2 stop hearing
Controller (CSC) during Wide area to site conventional RADIO-1 audio. Verify that
transition. CONSOLE-1 and CONSOLE-2
join the call again and continue to
hear audio from RADIO-1.
SETUP
Step 5. End the CONVCH1 call on RADIO-
1.
RADIO-1 - CONVCH1
CONSOLE-1 - CONVCH1
CONSOLE-2 - CONVCH1
CSC - SITE CONVSITE 1
CCGW-1 - CONVCH1
CCGW-1 - SITE - CONVSITE 1
Note: Configure the method to detect inbound radio Pass____ Fail____

transmission to VOX
VERSION #1.050

RFP# 101216
December 16, 2010

Step 1. Key-up CONSOLE-2 on CONVCH1.

Main / Alt Failure while Console Voice Call
Step 2. Verify that CONSOLE-1 hears
CONSOLE-2 on CONVCH1.
1. DESCRIPTION
Step 3. While the call is ongoing, power
down CCGW-1
The Main/Alternate feature provides a back-up station
interface for a conventional channel. The console Step 4. Verify that CONSOLE-2 continues
provides a single channel control window for the to hear CONSOLE-1. NOTE: After
Main/Alternate channel pair. It also provides an powering down CCGW-1 there
interface indicating which interface is currently active may be a brief interruption in the
(Main/Alternate), and allows the user to request that audio.
the active interface be changed to the other interface.
The system will automatically switch to the inactive Step 5. Power CCGW-1 back up to return to
interface if the active interface fails (and the inactive service.
has not failed). The channels comprising the
Main/Alternate pair may be located at the same or
different RF sites, but must be members of the same
zone. The Main/Alternate conventional channel
interfaces may be located on the same CCGW or on
different CCGWs. This test will demonstrate that the
Console monitors call activity and receive audio from a
conventional call from console while in Site
Conventional mode.
SETUP
Pass____ Fail____
SITE-1 - ZONE 1
CCGW-1 - SITE 1
CCGW-2 - SITE 1
CCGW-1 - CONVCH1
CCGW-2 - CONVCH2
MAIN - CONVCH1
ALTERNATE - CONVCH2
CONSOLE-1 - CONVCH1 - CONSITE 1

VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. From a Network Management client,

Configuration Reports for the Conventional attempt to generate a
Site Controller configuration report for the
Conventional Site Controller and
print the report (if applicable).
1. DESCRIPTION
Step 2. Verify that the Network
Management client can generate
This test will demonstrate the Network Management and print (if applicable) the report.
user can create configuration reports for Conventional
Site Controller (CSC). Step 3. From the Network Management
client, modify the Conventional
Site Controller's NTP settings
SETUP
Step 4. Generate a configuration report for
the Conventional Site Controller
RADIO-1 - CONVCH1 and print (if applicable) the report.
Step 5. Verify that the Network
CONSOLE-1 - CONVCH1 Management client can generate
CONSOLE-1 - SITE - CONSITE 1 and print (if applicable) the report
for updated configurations.
CSC-1 - SITE - CONVSITE 1
CCGW-1 - CONVCH1
CCGW-1 - SITE - CONVSITE 1
VERSION #1.050
Pass____ Fail____

RFP# 101216
December 16, 2010

Step 1. Verify that CONSOLE-1 shows the

Main / Alt Change Request channel available with status of
Main active
1. DESCRIPTION Step 2. Send Main / Alt switch from

CONSOLE-1.
The Main/Alternate feature provides a back-up station Step 3. Verify that the CONSOLE-1 shows
interface for a conventional channel. The console the channel available with status
provides a single channel control window for the of Alt active
Main/Alternate channel pair. It also provides an
interface indicating which interface is currently active Step 4. Verify the Main / Alt switch from
(Main/Alternate), and allows the user to request that ZoneWatch (if available) and ATIA
the active interface be changed to the other interface. logs
The system will automatically switch to the inactive
interface if the active interface fails (and the inactive Step 5. Send Main / Alt switch from
has not failed). The channels comprising the CONSOLE-1 (to set the Main
Main/Alternate pair may be located at the same or active)
different RF sites, but must be members of the same
zone. The Main/Alternate conventional channel
interfaces may be located on the same or on different
CCGWs.
This test will demonstrate that the Main/ Alt change
can be requested by Dispatch Console.
SETUP
SITE-1 - ZONE 1
CCGW-1 - CONVCH1 Pass____ Fail____

CCGW-1 - CONVSITE 1
CCGW-2 - CONVSITE 1
CCGW-2 - CONVCH2
MAIN - CONVCH1
ALTERNATE - CONVCH2
CONSOLE-1 - CONVCH1 - CONVSITE 1
VERSION #1.020

RFP# 101216
December 16, 2010

Step 1. Power down CCGW-2

Main Channel is in Service / Alt Channel is not
in Service Step 2. Verify that CONSOLE-1 shows
status that CCGW-1 as active
1. DESCRIPTION Step 3. Power down CCGW-1
Step 4. Power up CCGW-2

The Main/Alternate feature provides a back-up station
interface for a conventional channel. The console Step 5. Verify that CONSOLE-1 shows
provides a single channel control window for the status that CCGW-2 (alternate) as
Main/Alternate channel pair. It also provides an active
interface indicating which interface is currently active
(Main/Alternate), and allows the user to request that Step 6. Power up CCGW-1.
the active interface be changed to the other interface.
The system will automatically switch to the inactive
interface if the active interface fails (and the inactive
has not failed). This test will demonstrate that the
dispatch console will indicate the status of the main/alt
conventional channel pair.
SETUP

Pass____ Fail____
CONVSITE 1 - ZONE 1
CCGW-1 - CONVCH1
CCGW-1 - CONVSITE 1
CCGW-2 - CONVCH2
CCGW-2 - CONVSITE 1
MAIN-ACTIVE - CONVCH1
ALTERNATE-INACTIVE - CONVCH2
VERSION #1.030

RFP# 101216
December 16, 2010

Step 1. Disconnect the CONSITE 1 link and

Active Call During Transition to Wide Area verify that CONSOLE-1 provides
Conventional Mode an indication that the CONVSITE-
1 has entered into site
conventional mode.
1. DESCRIPTION
Step 2. Initiate a conventional call on
CONVCH1 with RADIO-1.
The Conventional Site Controller (CSC) is an optional
device that is installed at a console site. The CSC Step 3. Verify that CONSOLE-1 hears
provides fallback capability for the console site and RADIO-1. Continue to transmit the
conventional channels colocated with this site when call through the duration of the
the link between a console site and the zone controller test.
is lost. Such way of operating is called Site
Conventional mode. Step 4. Put CONVSITE 1 into wide area
This test demonstrates the ability for an active site conventional mode by connecting
conventional call to transition to wide conventional with the CONSITE 1 link.
minimal interruption. The active call will be interrupted
for a short period. Step 5. Verify that the RADIO-1 call
continues with a brief interruption
Note: Configure the method to detect inbound radio while the CONVSITE 1 transitions
transmission to VOX. into wide area conventional mode.
(Note: CONSOLE-1 will briefly
stop hearing RADIO-1, but then
SETUP the call will resume once back into
wide area conventional mode).
RADIO-1 - CONVCH1 Step 6. Verify that CONSOLE-1 continues

RADIO-1 - SITE - CONVSITE-1 to hear RADIO-1 after
transitioning to wide area
CONSOLE-1 - CONVCH1 conventional mode.
CONSOLE-1 - SITE - CONVSITE-1
Step 7. End the CONVCH1 call.
CONSOLE-2 - CONVCH1
CONSOLE-2 - SITE - CONSITE-1
CSC - SITE - CONVSITE-1
CCGW-1 - CONVCH1
CCGW-1 - SITE - CONVSITE-1

RFP# 101216
December 16, 2010

6.11 ISSI.1 Network Gateway

RFP# 101216
December 16, 2010

ISSI.1 Network Gateway 2. TEST

Serving System Initiated Talkgroup Call RADIO-4 on TALKGROUP 4.
Step 2. Observe that CONSOLE-1, RADIO-

1. DESCRIPTION 1 and RADIO-2 will be able to
monitor and respond to the call on
TALKGROUP 2, while RADIO-5
The Talkgroup is the primary level of organization for will be able to monitor and
communications on a trunked radio system. Radios respond to the call on T43.
with Talkgroup call capability will be able to
communicate with other member of the same
Talkgroup. With ISSI.1 Interconnectivity, Radios will
also be able to communicate with users in a different
system that interconnect via the Talkgroup This test
will demonstrate that a Talkgroup transmission
initiated by a radio user in the Serving System will be
heard by Home system users, which have, the
Talkgroup that maps to the initiated Talkgroup.
SETUP
In this test TALKGROUP 1 and TALKGROUP 2 are

Talkgroups defined in SYSTEM 1. TALKGROUP 3 and
TALKGROUP 4 are defined in System 2.
TALKGROUP 1 (Serving TG) is mapped to
TALKGROUP 3 (Home TG). TALKGROUP 2 (Home
TG) is mapped to TALKGROUP 4 (Serving TG). Pass____ Fail____
SYSTEM 1
RADIO-1 - TALKGROUP 2 @ SITE 1
SYSTEM 2
VERSION #1.010

RFP# 101216
December 16, 2010

Step 1. Switch the selected Talkgroup on

Manual Roaming Between Systems RADIO-1 from SYSTEM 1
TALKGROUP 1 to SYSTEM 2
TALKGROUP 3.
1. DESCRIPTION
RADIO-1 in SYSTEM 2 on
ISSI.1 provides the ability to manually roam from one TALKGROUP 3.
system to another and maintain communication. This
test will demonstrate that a radio can register on a Step 3. Observe that RADIO-2 will be able
peer system and initiate and receive on a Talkgroup to monitor and respond to the call
that will communicate with the roamed from system. on SYSTEM 1 TALKGROUP 1
and RADIO-4 and RADIO-5 will
be able to monitor and respond to
SETUP the call on SYSTEM 2 on
TALKGROUP 3.

TG) is mapped to TALKGROUP 4 (Serving TG). The
switch from TALKGROUP 1 to TALKGROUP 3 will
switch the radio from SYSTEM 1 to SYSTEM 2.
SYSTEM 1
SYSTEM 2
RADIO-5 - TALKGROUP 3 @ SITE 2 Pass____ Fail____
VERSION #1.010

RFP# 101216
December 16, 2010

Step 1. Initiate a Wide Area Emergency Call

Emergency Call with RADIO-1 on TALKGROUP 1.

1. DESCRIPTION RADIO-2 will be able to monitor,
display the Emergency PTT ID
The Talkgroup is the primary level of organization for TALKGROUP 1 and RADIO-4 and
communications on a trunked radio system. This test RADIO-5 will be able to monitor,
will demonstrate that an Emergency Talkgroup display the Emergency PTT ID
transmission initiated by a radio user will be heard and and are able to respond to the call
displayed as an Emergency Talkgroup transmission in on TALKGROUP 3.
the peer system.
Step 3. Initiate a Wide Area Emergency Call
with RADIO-3 in SYSTEM 1 on
SETUP TALKGROUP 2.

SYSTEM 1 RADIO-6 will be able to monitor,
RADIO-1 - TALKGROUP 1 display the Emergency PTT ID
RADIO-2 - TALKGROUP 1 and are able to respond to the call
RADIO-3 - TALKGROUP 2 on TALKGROUP 4.
CONSOLE-1 TALKGROUP 1
SYSTEM 2

TALKGROUP 1 is mapped to TALKGROUP 3.
TALKGROUP 2 is mapped to TALKGROUP 4

RFP# 101216
December 16, 2010

Step 1. Initiate a Wide Area Secure Call

Secure Call with RADIO-1.

1. DESCRIPTION RADIO-2 will be able to monitor
TALKGROUP 1 and RADIO-4 and
The Talkgroup is the primary level of organization for RADIO-5 will be able to monitor
communications on a trunked radio system. This test and respond to the call on
will demonstrate that a secure Talkgroup transmission TALKGROUP 3.
initiated by a radio user will be heard by peer system
users, which have, the Talkgroup that maps to the Step 3. Initiate a Wide Area Secure Call
initiated Talkgroup. with RADIO-3.

SETUP RADIO-6 will be able to monitor
TALKGROUP 4.
TG) is mapped to TALKGROUP 4 (Serving TG).
Ensure the proper keys have been loaded in the
consoles and radios.
SYSTEM 1
SYSTEM 2 Pass____ Fail____

VERSION #1.010

RFP# 101216
December 16, 2010


Home System Initiated Talkgroup Call RADIO-1 in SYSTEM 1 on
TALKGROUP 2.
1. DESCRIPTION Step 2. Observe that CONSOLE-1 and

RADIO-2 will be able to monitor
The Talkgroup is the primary level of organization for TALKGROUP 2, while RADIO-4
communications on a trunked radio system. Radios and RADIO-5 will be able to
with Talkgroup call capability will be able to monitor and respond to the call on
communicate with other members of the same TALKGROUP 4.
Talkgroup. With ISSI.1 Interconnectivity, Radios will
also be able to communicate with users in a different
system that interconnect via the Talkgroup This test
will demonstrate that a Talkgroup transmission
initiated by a radio user in the Home System will be
heard by Serving system users, which have, the
Talkgroup that maps to the initiated Talkgroup.
SETUP
SYSTEM 1
SYSTEM 2

TG) is mapped to TALKGROUP 4 (Serving TG).
VERSION #2.000

RFP# 101216
December 16, 2010

6.12 Wide Area Trunking
Features

RFP# 101216
December 16, 2010

Wide Area Trunking Features 2. TEST
Step 1. Affiliate all radios to TALKGROUP 1

Audio Interrupt On Priority
Step 2. Key RADIO-1, RADIO-2 and
RADIO-3 hear RADIO-1 audio
1. DESCRIPTION
Step 3. Key RADIO-2, RADIO-3 hears
RADIO-2 audio
This test demonstrates that a radio with higher
individual priority will interrupt another radio with lower Step 4. DeKey RADIO-2, RADIO-2 and
individual priority RADIO-3 hear RADIO-1 audio.
SETUP
RADIO-1 – TALKGROUP 1
Note:
RADIO-2 has higher priority than RADIO-1 or RADIO-
3.
TALKGROUP 1 has been configured to
Audio_Interrupt= On_Priority
Pass____ Fail____
VERSION #1.010

RFP# 101216
December 16, 2010

Wide Area Trunking Features 2. TEST
Step 1. Key radio 1, hear audio from radio

Agencygroup interrupt mode 1 in radio 2. Keep radio 1 keyed.
Step 2. Key radio 3, hear audio from radio 3

1. DESCRIPTION in radio 2. Radio 1 call is dropped
as soon as radio 3 keys up.
This test verifies the basic functionality of Step 3. Dekey radio 3, hear no audio
Agencygroups. An active member [Talkgroup /
Multigroup] call will be interrupted by an Agencygroup
call, when the Agencygroup is configured for interrupt
mode.
SETUP
RADIO-1 – MG 1
RADIO-3 – AG1
Note:
TALKGROUP 1 is configured in wait mode
Pass____ Fail____
TALKGROUP 1 is assigned to multigroup MG1
MG1 is configured in wait mode.
MG1 is assigned to the Agencygroup AG1
AG1 is configured in interrupt mode
AG1 is configured as the highest priority TG
VERSION #1.030

RFP# 101216
December 16, 2010

6.13 Signoff Certificate
By their signatures below, the following witnesses certify they have observed the In-Field System
Acceptance Test Procedures.
Signatures
WITNESS: ___________________________________Date: _______
Please Print Name: ________________________________________ ________

Initials:
Please Print Title: ________________________________________
Motorola Field Engineer WITNESS: ___________________________________Date: _______

Initials:
Motorola Project Manager WITNESS: ___________________________________Date: _______

Initials:

RFP# 101216
December 16, 2010

Section 7. Coverage Acceptance Test Plan
7.1 Overview
This Coverage Acceptance Test Plan (CATP) is designed to verify that the voice
radio system implemented by Motorola meets or exceeds the required coverage
reliability within the City and County service area as defined by the RFP. The CATP
defines the coverage testing method and procedure, the coverage acceptance
criterion, the test documentation, and the responsibilities of both Motorola and the
County.
Coverage Acceptance Testing is based upon a coverage prediction that accurately
represents the implemented infrastructure and parameters consistent with the contract
agreements. If the implemented system varies from the design parameters, a revised
coverage map will be prepared. New test maps will reflect the measured losses and
gains associated with the implemented infrastructure and subscribers. These will be
used to define the test configuration and potential areas from which test locations
may be included in the evaluation process.
There are three defined service areas as outlined in this CATP; 1) Floyd County
service area, 2) City of Rome service area, 3) and the Central Business District
service area.
To verify that the radio service area reliability is met as presented, the Floyd County
service area will be divided into approximately 1600 equally sized test tiles at
minimum. The Floyd County service area is defined by the Floyd County boundary
shape files provided in Addendum 3. The County service area excludes the City of
Rome service area and the Central Business District service area. These test tiles are
approximately 3337 feet by 3020 feet and thus meet the maximum tile size for the
countywide test of no greater than 4000 feet.
To verify that the radio service area reliability is met as presented, the City of Rome
service area will be divided into grids – with an approximated minimum of 1500
equally sized test tiles for the testing the City of Rome area. The City of Rome
service area is defined by The City of Rome boundary shape files provided in
Addendum 3 and excludes the Central Business District service area. The test tiles for
the City service area are approximately 739 feet by792 feet and thus meet the
maximum tile size for the urban services area of no greater than 2000 feet.
The City of Rome’s central business district and government areas will require
smaller test tiles as defined within the RFP. To verify that the radio service area

subject to the restrictions on the title page RFP# 101216
December 16, 2010
Coverage Acceptance Test Plan 7-1

reliability is met as presented, the central business district service area (which is
defined in Addendum 1) will be divided into equally sized test tiles. The maximum
size of 400 feet will be observed, although Motorola’s recommendations include at
least a 600-foot tile to be practical and obtaining sufficient samples while driving in
the test tile. With a 400-foot tile, there will be approximately 6700 equally sized test
tiles. With a 600-foot tile, there will be approximately 2900 equally sized test tiles.
The quantity of test tiles is determined by the Estimate of Proportions formula to
achieve a statistically valid test.
Table 7-1 details the service area reliabilities for each of the different configurations.
The service area reliability is the percentage of test tiles that will pass within the
service area with a specified CPC or DAQ.
Table 7-1: Predicted System Coverage
Equipment Configuration % Service Area % Service Area % Service Area

Reliability of Reliability of Reliability of
Floyd County City of Rome Central
Business
District
Mobile w/unity gain ant. ≥95% ≥95% ≥95%
Portable (SMA) Outside ≥95% ≥95% ≥95%
Portable (SMA) 4 dB loss ≥95% ≥95% ≥95%
Motorola has defined the countywide in-building/in-residence loss factor to be 4 dB.
The following coverage maps are included for the configurations listed in Table 7-1:
8-site Simulcast System (Talk-out and Talk-In)
♦ Mobile with unity gain antenna.
♦ Portable (½ wave in Swivel Case) outside.
♦ Portable (½ wave in Swivel Case) 4 dB loss.
7-site Simulcast System with 1 ASTRO 25 Repeater Sites (Talk-out and

Talk-In)
♦ Mobile with unity gain antenna.
♦ Portable (½ wave in Swivel Case) outside.
♦ Portable (½ wave in Swivel Case) 4 dB loss.
Motorola is additionally including several other coverage maps for various building
losses for informational purposes and to ensure all coverage criteria in the RFP is
appropriately addressed.

December 16, 2010
7-2 Coverage Acceptance Test Plan

7.1.1 CATP Definitions
Several definitions are needed to accurately describe the coverage test method.
7.1.1.1 Coverage Area

The coverage area is the geographical region in which communications will be
provided that meets or exceeds the specified CPC at the specified reliability for the
specified equipment configurations.
7.1.1.2 Reliability
Reliability is the percentage of locations within the coverage area that meet or exceed
the specified CPC. Motorola’s coverage maps indicate the area within which this
system is predicted to provide at least 95% reliability of meeting or exceeding the
CPC.
7.1.1.3 Channel Performance Criterion

CPC is the specified minimum design performance level in a faded channel. For this
system, the CPC is DAQ-3.4 for portables and DAQ-4.0 for mobiles. The DAQ
definitions are provided in Table 7-2: Delivered Audio Quality Definitions
Table 7-2: Delivered Audio Quality Definitions
DAQ Faded Subjective Performance Description

1 Unusable, speech present but unreadable.
2 Understandable with considerable effort. Frequent repetition due to
noise/distortion.
3 Speech understandable with slight effort. Occasional repetition
required due to noise/distortion.
3.4 Speech understandable with repetition only rarely required. Some
noise/distortion.
4 Speech easily understood. Occasional noise/distortion.
4.5 Speech easily understood. Infrequent noise/distortion.
5 Speech easily understood.
7.1.1.4 Service Area Reliability

The service area reliability is the percentage of test tiles that will pass within the
service area with a specified CPC or DAQ. These service areas are as noted in header
of Table 7-1 and meet the requirements of the RFP.
There are three defined service areas as outlined in this CATP: 1) Floyd County
service area, 2) City of Rome service area, 3) Central Business District service area.
The outline of these service areas are depicted on each coverage map. Motorola has
indicated the CPC Service Area Reliability of these areas in Table 7-1 of this

December 16, 2010

document for the losses detailed in the RFP. Although the coverage maps do not
guarantee coverage within a specific location, they do indicate the ability of the
system to overcome the expected losses of these buildings.
7.1.1.5 Equipment Configurations

There are two configurations for the field unit equipment or subscriber upon which
coverage acceptance is based. Motorola’s coverage maps for this system indicate the
coverage area for the following equipment configurations:
♦ 3-watt Portable.
♦ Remote Speaker Microphone and ½ wave flex-whip antenna.
♦ In swivel case at hip level (3 feet) for Transmit and Receive.
♦ 15-watt mobile with unity gain antenna center roof mounted.
The 8-site Simulcast proposed design and the 7-site simulcast with 1 ASTRO 25
Repeater sites proposed design support this configuration.
♦ The Seven (7) or eight (8)-site System Transmitting Simulcast and Receiver
Voting sites utilize P25 compliant ASTRO 25 Linear Simulcast Modulation
(LSM).
♦ The One (1) ASTRO 25 Repeater Sites utilize P25 C4FM modulation.
In-Building Coverage
Motorola’s coverage maps for portable in-building equipment configurations are
predictions of coverage inside 4 dB, 6 dB, 15 dB, 20 dB, and 25 dB loss buildings.
Since building loss varies significantly depending on the construction of buildings,
Motorola’s coverage maps do not predict coverage within any specific building.
Rather, the in-building coverage maps indicate the area within which this system is
predicted to provide the percentage reliability of meeting or exceeding the CPC of
DAQ-3.4. The named buildings in Attachment C of the RFP will be tested per the
requirements of the RFP. Motorola will provide 95% reliability coverage within these
buildings as required.
7.1.2 CATP Method

The method used to test coverage is statistical sampling of the predicted coverage
area to verify that the CPC is met or exceeded at the required reliability for the
defined equipment configuration. It is impossible to verify every point within a
coverage area, because there are infinite points; therefore, coverage reliability will be
verified by sampling a statistically significant number of randomly selected locations,
quasi-uniformly distributed throughout the predicted coverage area.
This CATP provides an objective, quantitative method of measurement using
Motorola’s Voyager software in conjunction with an APX 6000 portable radio for
location reference, signal strength measurements, and recording.

December 16, 2010

The CATP also provides a subjective audio quality test by using actual equipment
configured as it will be used in the system.
If a coverage test, or a portion thereof, is suspected by Motorola to have failed due to
external interference, those tiles suspected of being affected by an interferer may be
retested. If the tiles (or test points) retested are confirmed to have failed due to
interference, those tiles (or test points) will be excluded from all acceptance
calculations and Motorola will work with the County to identify potential solutions to
the interference issues.
If a coverage test, or a portion thereof, is suspected by Motorola to have failed due to
the system malfunctioning and being in need of repair, those tiles (or test points)
suspected of being affected by this may be retested. The coverage testing will be
stopped until the repairs are made. After the repairs are made, Motorola will retest
only the tiles (or test points) that failed due to the system malfunctioning and being in
need of repair.
Determine the Required Number of Test Tiles in the Coverage Area
The predicted coverage area shown on Motorola’s coverage maps and service area
will be divided into a tile pattern to produce at least the number of uniformly sized
test locations (or tiles) required by the Estimate of Proportions formula {TSB-88B,
sub clause 8.2.1, equation 64}. The minimum number of test tiles required varies for
different systems, from a hundred to many thousands, depending on the size of the
service area, desired confidence in results, type of coverage test, and the predicted
versus required reliability. Motorola’s Hydra coverage modeling tool calculates the
required test tiles as described.
Constraints on Test Tile Sizes
The minimum tile size is 100 by 100 wavelengths; however, the minimum practical
test tile size is typically about 400 by 400 meters (about 0.25 by 0.25 miles). The
minimum practical tile size for any system is determined by the distance traveled at
the speed of the test vehicle while sampling, GPS error margin, and availability of
road access within very small test tiles. A related consideration is the time, resources,
and cost involved in testing very large numbers of very small tiles. The maximum test
tile size is 2 by 2 km (1.25 by 1.25 miles). In some wide-area systems, this constraint
on maximum tile size may dictate a greater number of test tiles than the minimum
number required by the Estimate of Proportions formula. Motorola has complied with
the maximum tile sizes as recommended by the RFP.
Accessibility to Test Tiles
Prior to testing (if possible) or during the test, Motorola and the County will
determine whether any test tiles are inaccessible for the coverage test (due to lack of
roads, restricted land, etc.). Inaccessible tiles will be counted as a pass for the
acceptance test calculation.

December 16, 2010

Randomly Select a Test Location Within Each Tile
Using Voyager, the actual test location within each test tile will be randomly selected
by the test vehicle crossing into the tile at an arbitrary point, with an arbitrary speed
and direction. This will be the queue for the objective sampling test to begin.
Perform Measurements in Each Tile
In each test tile, a series of 200 or more sequential SSI measurements (sub-samples)
will be made. This test location measurement, containing a number of sub-samples,
constitutes the test sample for this location. The test sample will establish the local
mean and median SSI within the test tile. With this measurement, the required target
SSI can be extrapolated for each configuration and loss required. The distance over
which the sub-samples are measured will be 40 wavelengths. A mean or median of
multiple SSI sub-samples is used rather than a single measurement to ensure that the
measurement is not biased by taking a single sample that might be at a peak or null
point on the radio wave.
7.1.2.1 Determine If Each Test Tile Passes or Fails the CPC

Requirement
For each test tile, the pass/fail criterion is the objective target signal strength test that
indicates the specified DAQ-3.4 (DAQ-4.0 for mobile). To simulate losses of
buildings, the loss is simply extrapolated from the measured faded SSI. The target
faded SSI is the actual signal level as measured by the test radio at the input
connector.
Table 7-3: Net Target Signal Strength Indication – Mobile
Objective Mobile Faded Measured Faded Adjustments for Mobile

Test Sensitivity Target SSI Antenna Loss/Gain & Delta for
(dBm) DAQ-4.0 (dBm) talk-in/talk-out (dB)
DAQ-4.0
Outside -105.5 -105.5 0
Table 7-4: Net Target Signal Strength Indication – Portable in Swivel Case at Hip
Objective Test Portable Portable Faded Adjustments for Mobile

Faded Target SSI Antenna Loss/Gain, Portable
Sensitivity (dBm) Antenna & Building Loss (dB)
(dBm) DAQ- DAQ-3.4
3.4
Outside -108.5 -103.6 -4.9 (-7.7+2.8)
4 dB bldg -108.5 -99.6 -8.9 (-7.7-4.0+2.8)
6 dB bldg -108.5 -97.6 -10.9 (-7.7-6.0+2.8)
15 dB bldg -108.5 -88.6 -19.9 (-7.7-15.0+2.8)
20 dB bldg -108.5 -83.6 -24.9 (-7.7-20.0+2.8)
25 dB bldg -108.5 -78.6 -29.9 (-7.7-25.0+2.8)

December 16, 2010

* The -7.7 dB is the antenna loss figure for the ½ wave flex-whip antenna on an APX
6000 portable in a swivel case with remote speaker microphone and standard battery.
** The +2.8 dB is the mobile antenna and transmission line that a portable does not
have and thus must be added back to get the signal at the input to the test radio.
7.1.2.2 Determine the Coverage Area Reliability for Acceptance

After all accessible tiles in the coverage area have been tested; the coverage area
reliability (percentage) will be determined by dividing the number of tiles that pass
by the total number of tiles tested. The total number of tiles is defined as the
summation of the tiles tested in the Floyd County, City of Rome, and central business
district service areas. The coverage test acceptance criterion for each equipment
configuration is that the tested coverage area reliability must be equal to or greater
than the required reliability as shown in Table 7-1.
7.1.2.3 Responsibilities and Preparation

This information will help set the expectations of Floyd County and Motorola
regarding requirements for equipment, personnel, and time during the coverage test.
The County will provide the following for the duration of the coverage test:
♦ One marked Public Safety vehicle as an escort for each test team.
♦ At least one City/County representative, and one Tusa Consulting Services
representative for each test vehicle to be the customer representatives for each of
the field test teams.
♦ At least one City/County representative, one Tusa Consulting Services
representative for the fixed location (likely the dispatch center) to be the customer
representatives for the fixed end.
Motorola will provide the following for the duration of the coverage test:
♦ Rental off road type vehicles for the duration of the test
♦ At least one Motorola representative to operate Voyager for each team (this
would assume that the customer representative would drive the vehicle).
♦ At least one calibrated Motorola Voyager coverage testing package per team
♦ Test radios for each field team (will use calibrated subscribers)
Coverage acceptance testing will be performed within the borders of the County.
Motorola has determined the minimum number of test tiles required, as described in
Section 7.1 of this CATP. Motorola and the County will plan the route for the test
vehicles through the coverage test area, to ensure that at least the minimum required
number of tiles is tested. If possible, any tiles not accessible to the test vehicles will
be identified while planning the route.

December 16, 2010

Motorola will calibrate the test radios (standard APX 6000 portables) used with the
Voyager coverage testing package. This can be done at an independent testing lab or
facility using their calibrated signal generating equipment. Depending on the system,
either Motorola or the County may provide the test radios.
Motorola will conduct this test only once. If any portion of the test is determined to
be unreliable because of proven equipment malfunctions or failures, Motorola will
repeat the portion of the test affected by the equipment malfunction or failure. The
County will have the option to accept the coverage at any time prior to completion of
the coverage test.
Before starting the test, the County and Motorola will agree upon the time frame for
Motorola’s submission of a report containing the coverage test results.
7.1.2.4 CATP Procedures

Objective Signal Strength Testing Measurements
The Motorola Voyager coverage test setup consists of the following:
♦ A calibrated digital voice test radio, connected to an antenna installed in a
representative location on the test vehicle. The test radio will monitor sequential
transmissions within each grid from the fixed network radio site(s).
♦ A laptop computer with Voyager software and a mapping database, which
includes highways and local streets, political boundaries, rivers, and railroads.
♦ A Global Positioning System (GPS) receiver, which will provide the computer
with the location and speed of the test vehicle.
Subjective Voice Quality Testing
A subjective listening test will be performed for coverage acceptance testing to verify
talk-out and talk-in DAQ performance of the system. Since the DAQ-3.4 portable
threshold is more stringent than the DAQ-4.0 mobile threshold, the test will be
conducted using the DAQ-3.4 portable.
The procedure for the subjective DAQ coverage test will be as follows:
♦ To perform a statistically valid subjective DAQ test, a large group of people is
required to ensure high confidence in the results. However, obtaining a large
group of people for a subjective listening test is usually impractical; therefore,
several (3 to 4) people in a car or van must be used for the test. Since a group this
small cannot provide statistically significant results, it is very important that the
personnel participating in the subjective test be familiar with the sound of radio
conversations. Before subjectively testing, all personnel who will evaluate audio
quality must be “calibrated” by listening to examples of static and faded audio of
various CPC levels from the type of system being tested.
♦ A fixed control point location will be established. Prior to testing, the County and
Motorola will agree upon a procedure to allow each audio transmission to be
evaluated for approximately five seconds.

December 16, 2010

♦ The test participants will be divided into teams, each consisting of personnel from
the County, Tusa Consulting Services, and Motorola. Each team will have
members that operate a portable unit inside the test vehicle and members that are
stationed at the fixed control point location. An odd number of team members is
required to avoid ties for the pass/fail consensus.
♦ As the field test team(s) drive through the coverage area, test locations within
each tile will be selected randomly by Voyager that will be conducting the
objective SSI testing. The voice subjective test may begin after the sampling is
complete. This is to prevent any degradation to the receiver sampling the SSI.
♦ The field test unit will make a call, identify the test tile by the current x-y tile
location, and repeat one of the ten phonetically balanced phrases (approximately
5 seconds in length). The fixed location unit (console or control station) test team
will then determine if the voice passes or fails the DAQ criteria as defined by the
Table 7-2: Delivered Audio Quality Definitions in this document. The fixed
location will then read one of the ten phonetically balanced phrases
(approximately 5 seconds in length) and the field team will in turn determine if
the voice passes or fails the DAQ criteria shown in Table 7-2: Delivered Audio
Quality Definitions
♦ The tile pass/fail evaluations will be used to determine the coverage area
reliability of the defined coverage areas in Table 7-1. If any test point should fail,
the test team will move three feet and perform another test in the same manner.
Either passed test will render that test point a PASS. No more than 15% of the test
points within a given service area may be deemed to have passed due to a
successful retry. If the portable transmission is still a considered a FAIL, a DAQ-
4.0 test will be conducted using a mobile radio for purposes of evaluating mobile
coverage.
♦ Coverage acceptance will be based on demonstrating that the percentage of the
tile locations, as described in Table 7-1 for each equipment configuration will
provide an audio quality of DAQ-3.4 or better (DAQ-4.0 for mobiles). The
system coverage acceptance criterion will be the successful passing of each of the
equipment configurations.
♦ Motorola reserves the right to review any test tiles that fail the subjective DAQ
tests.
Objective SSI Testing and Subjective Voice Quality Testing
Both the subjective and objective testing as described will be performed at the same
time but will be evaluated independently of each other. A failed tile for the objective
test does not constitute a failure for the subjective testing. The reason for this is that
the points are taken at different times (thus at different locations). The modeling does
not predict the probability of one location against the other but predicts area
reliability of all test points for each test.

December 16, 2010

Critical Buildings Subjective Voice Quality Testing
An independent subjective listening test will be performed for each of the 176 critical
buildings identified in Attachment C of the RFP. Testing will verify talk-out and talk-
in DAQ performance of the system.
The procedure for the critical building subjective DAQ coverage test will be as
follows:
♦ To perform a statistically valid subjective DAQ test, a large group of people is
required to ensure high confidence in the results. However, obtaining a large
group of people for a subjective listening test is usually impractical; therefore,
several (3 to 7) people must be used for the test. Since a group this small cannot
provide statistically significant results, it is very important that the personnel
participating in the subjective test be familiar with the sound of radio
conversations. Before subjectively testing, all personnel who will evaluate audio
quality must be “calibrated” by listening to examples of static and faded audio of
various CPC levels from the type of system being tested.
♦ A fixed control point location will be established. Prior to testing, the County and
Motorola will agree upon a procedure to allow each audio transmission to be
evaluated for approximately five seconds.
♦ The test participants will be divided into teams, each consisting of personnel from
the County, Tusa Consulting Services, and Motorola. Each team will have
members that operate a portable unit inside the building and members that are
stationed at the fixed control point location. An odd number of team members is
required for the pass/fail consensus.
♦ Each critical building must be divided into test points:
♦ 40,000 square feet per floor or less - The building’s lowest floor that is
completely above ground level will be tested. This lowest floor test will
include 20 test points, evenly distributed throughout the floor. The 20 test
points will include at least one test point at each of the furthermost accessible
locations in the northern, southern, western, eastern, and one in the center of
the floor, as well as one point in each stairwell entrance. All test locations will
be above ground level. If no more than 5% of the test points on this floor have
been shown to have failed, then this particular building is considered to have
passed. If more than 5% of the test points on this floor have been shown to
have failed, then a full building test will need to be performed. If necessary,
the full building CATP will include 20 points, evenly distributed throughout
each of the remaining upper floors. The 20 points will include at least one test
point at each of the furthermost accessible locations in the northern, southern,
western, eastern, and one in the center of the floor, as well as one point in
each stairwell entrance on each floor. All test locations will be above ground
level. There will be a minimum of 100 test points per building. Should the full
building not pass the required 95% threshold, the building will be retested
using a vehicular repeater purchased by Floyd County as part of this project to
supplement in-building coverage. The vehicular repeater will be placed within

December 16, 2010

200 feet and in line of sight of each individual building being tested. The
building will be retested using the procedure outlined in this CATP.
♦ Greater than 40,000 square feet per floor - The building’s lowest floor that is
completely above ground level will be tested. All test points will be evenly
distributed throughout the floor. The total number of test points required to
achieve a maximum of 50-foot sample spacing will be employed. The total
the floor, as well as one point in each stairwell entrance. All test locations will
be above ground level. If no more than 5% of the test points on this floor have
been shown to have failed, then this particular building is considered to have
passed. If more than 5% of the test points on this floor have been shown to
have failed, then a full building test will need to be performed. If necessary,
the full building CATP will include evenly distributed points throughout each
of the remaining upper floors. The total number of test points required to
achieve a maximum of 50-foot sample spacing will be employed. The total
the floor as well as one point in each stairwell entrance on each floor. All test
locations will be above ground level. There will be a minimum of 20 test
points per floor and a minimum of 100 test points per building. Should the full
building not pass the required 95% threshold, the building will be retested
using a vehicular repeater purchased by Floyd County as part of this project to
supplement in-building coverage. The vehicular repeater will be placed within
200 feet and in line of sight of each individual building being tested. The
building will be retested using the procedure outlined in this CATP.
♦ Specialty Buildings – Any critical buildings which are constructed with metal
roofs, bay doors, or stairwells, will be tested with the exterior doors open, this
includes bay doors at fire/EMS stations, manufacturing/shipping facilities,
and airport hangars, or exterior stairwell access doors for multiple story
buildings.
♦ Campuses – Campuses are defined as any building listed in Attachment C of
the RFP that consist of more than one (1) building. All buildings within a
campus will provide equally weighted test points which will contribute to the
coverage criteria of 95% reliability. Therefore, the total number of test points
will be the summation of all the test point from all the buildings within a
campus.
♦ In order to make the testing as easy and time efficient as possible, the talkout and
talkback field tests for all test points will initially be performed utilizing a
portable in hand without the use a remote speaker microphone. The field test unit
will make a call, identify the test number and the building, and repeat one of the
ten phonetically balanced phrases (approximately 5 seconds in length).
♦ The fixed location unit (console or control station) test team will then determine if
the voice passes or fails the DAQ criteria as defined by Table 7-2 of this
document. The fixed location will then repeat one of the ten phonetically

December 16, 2010

balanced phrases (approximately 5 seconds in length) and the field team will in
turn determine if the voice passes or fails the DAQ criteria.
♦ If any test point should fail, the test team will move three feet and perform
another test in the same manner. Either passed test will render that test point a
PASS. No more than 15% of the test points within a given building may be
deemed to have passed due to a successful retry. If a test point also fails the retry
then measurements will be made from that test point to determine if in-building
loss exceeds 25db for that specific test point. If penetration loss exceeds 25db,
that specific test point will be omitted from reliability calculations.
♦ Each critical buildings coverage acceptance will be based on demonstrating that
95 percent of the test point locations provide an audio quality of DAQ-3.4 or
better. Motorola reserves the right to review any test tiles that fail the subjective
DAQ tests. Each critical building will be evaluated independently of each other.
A failed test for one critical building does not constitute a failure of another
building.
♦ If a building is determined to have failed after the entire critical building testing
procedure is completed as described in this CATP then the system may be
modified to achieve the required reliability within the failed building. If it is
determined that a BDA system is required then a BDA system may be installed as
described in the SOW of this proposal.
7.1.2.5 CATP Documentation and Coverage Acceptance

During the coverage acceptance test, Voyager generates computer files that include
the mean and median SSI for each test tile. It also generates a raw file that has the
multiple samples for each test point taken. A copy of this raw data will be provided to
the County or Tusa Consulting Services at any time per the RFP requirements.
Motorola will process this data to determine whether the coverage test was passed for
the equipment configurations and to produce a map that graphically displays the
statistical coverage test results along with the analyzed numbers of the passes and
failures.
Motorola will submit to the County a report detailing the coverage test results. This
report will include a document, which is to be signed by both the County and
Motorola, indicating the test was performed in accordance with this CATP and the
results of the test indicate the acceptance or non-acceptance of the coverage portion
of the system. The County will have the option to accept the coverage at any time
prior to completion of the coverage test or documentation process.

December 16, 2010

Section 8. Coverage Description
8.1 Coverage Description and Modeling
8.1.1 Coverage Maps
Per the RFP, two system designs are proposed. The core design is an eight site
Simulcast only system and an alternate design of a seven site Simulcast system with
one ASTRO25 Site Repeater (ASR at Rocky Mountain).
Motorola has included the following coverage maps for the configurations used for
the coverage guarantee:
8-site Simulcast System (Talk-out and Talk-In)
♦ Mobile w/unity gain antenna
♦ Portable (½ wave in Swivel Case) Outside
♦ Portable (½ wave in Swivel Case) 4 dB loss
7-site Simulcast System with 1 ASTRO25 Repeater Sites (Talk-out and
Talk-In)
♦ Mobile w/unity gain antenna
♦ Portable (½ wave in Swivel Case) Outside
♦ Portable (½ wave in Swivel Case) 4 dB loss
Per the RFP several other coverage maps for various building losses have also been
included for information purposes.
8.1.2 Hydra Overview

HydraSM is an innovative software tool developed by Motorola to accurately predict
coverage, model traffic (voice and data), analyze interference, plan channel re-use,
and perform other design tasks for Motorola’s diverse portfolio of radio networks.
This description concentrates on Hydra’s coverage planning aspects.
Motorola has presented in this proposal, Hydra coverage analysis for Floyd County,
GA (“County”).

December 16, 2010
Coverage Description 8-1

8.1.2.1 Hydra Development
Hydra’s coverage prediction tool was developed to provide accurate coverage
simulations by applying proven models to detailed system and environmental data
across large geographical areas.
To accurately create a picture of the predicted radio coverage, many elements must
be considered. Some of these elements, called system factors, are related to the
system design parameters. System factors affecting coverage performance include the
following: frequency, distance, transmitter power, receiver sensitivity, antenna
height, and antenna gain. Other factors, called environmental factors, vary according
to the path taken by the radio signal and the environment surrounding the receiver.
Environmental factors include the following: terrain variations, obstructions,
vegetation, buildings, ambient noise, and interference.
All coverage prediction methods try to account for both types of factors and
incorporate them into a computational model. In general, the currently accepted
models, such as Okumura, Longley-Rice, and TIA provide excellent portrayals of
radio coverage when used within their respective ranges of applicability.
In the past, this level of analysis was adequate for the type of basic systems that were
available. However, today’s complex technologies, such as digital voice radios,
packet data systems, or simulcast, require a much more in-depth analysis of the
expected coverage performance to create a cost-effective design. This makes it
necessary to select the appropriate coverage model, provide accurate representation
of the environmental factors throughout the service area, and apply the coverage
analysis method to every location within the service area.
Recognizing these facts, Motorola has developed Hydra, a multi-purpose network
design tool that includes a coverage analysis program. Taking advantage of the
knowledge gained from Motorola’s many years of practical experience and coverage
testing, Hydra provides a superior means for analyzing system coverage. This
program, unique to Motorola, employs a technique of computing coverage on every
tile in a service area rather than along a finite number of radials. Hydra computes
“layers” of these tiles, with each layer containing the values of propagation model
losses, coverage simulation results, or datasets. Layers can be displayed separately or
in any combination as maps of the service area.
8.1.2.2 Hydra Detailed Description
8.1.2.2.1 Inputs and Outputs

Inputs to Hydra’s simulations include system architecture, equipment characteristics,
service area boundaries, areas of various building losses, subscriber unit distribution
density for Traffic analysis, etc.
Hydra’s coverage map outputs are created and displayed using ESRI’s shapefiles, an
industry-standard GIS file format. Shapefiles from many sources (GIS vendors, the

December 16, 2010
8-2 Coverage Description

Internet, your own GIS department, etc.) can be loaded, displayed, and used in Hydra
to enhance mapping, and to define service area polygons. Hydra’s coverage analyses
can be limited to specified service area polygons (e.g., a county, a city, or a dispatch
territory), so coverage reliability can be analyzed exclusively within the boundaries
of your operating area.
In addition to showing coverage reliability, Hydra maps can display terrain, land
cover, roads and boundaries, signal strength and field strength, interference
predictions, etc.
Hydra provides closed-loop integration between predicting coverage and verifying
coverage using Motorola’s VoyagerSM coverage acceptance testing tools. Field
survey measurements for signal strength can be loaded into Hydra for analysis,
display, and printing.
8.1.2.2.2 Tile Method

Hydra uniformly divides the entire geographical area to be analyzed into small,
distinct areas called tiles. The resolution (size) of the tiles can be as fine as one arc-
second (approximately 100 feet at U.S. latitudes). At each tile, Hydra models
propagation from each site in the system.
The tile method is of particular importance in the calculation of simulcast coverage
and interference analysis. Radial methods determine performance only at the
locations where radials from all sites cross, leaving many areas where coverage
performance is not calculated. With the tile method, the information from every site
and all datasets is available in every tile; this provides the most accurate results for
multi-site analyses (simulcast, voting, interference, best server, etc.).
8.1.2.2.3 Datasets
For propagation prediction, Hydra uses two types of geophysical datasets:
♦ Hypsographic (terrain elevations) - to determine shadow loss and elevation
♦ Morphological (land use) - for environmental clutter loss
With the proper datasets, Hydra produces accurate results. Because propagation
prediction accuracy is directly dependent on the quality of the digitized datasets,
Motorola uses high-quality datasets for its analyses. These datasets generally
originate from official government agencies such as the U.S. Geological Survey in
the United States, and equivalent governmental organizations worldwide. When
datasets are not available from these sources, Motorola can work with commercial
GIS vendors to produce Hydra-compatible datasets.
Even the best datasets contain a certain amount of errors, caused by a number of
factors that are difficult to completely overcome due to the massive amount of data
involved. Some examples follow:

December 16, 2010

♦ Source Information – Older hypsographic and morphologic datasets were
derived from existing map information, so any errors in the existing maps were
carried over to the datasets. Newer datasets such as the U.S. National Land Cover
Dataset (NLCD) are derived from satellite imagery, and are affected by
digitization error.
♦ Dataset Development Process – Potential error sources include limitations in the
digitizing algorithms, computer hardware problems, and judgment calls by the
dataset developer.
♦ Dataset Currency – Since the physical world is constantly changing, datasets
can never be completely up-to-date. Over time, forests and shrub land are turned
into farmland, hills are leveled, roads are built, communities are developed, and
large buildings are constructed. Natural phenomena such as earthquakes,
volcanoes, fires, storms, etc., change both the topography and environmental
factors.
Hydra, like all terrain-based propagation tools, provides coverage predictions that are
only as accurate as the available datasets permit. In the U.S., Motorola uses high-
quality terrain and land cover data derived from USGS 30-meter DEM and NLCD
sources.
Other datasets that Hydra can use include the following:
♦ Planimetric (mapping) – roads, water features, political boundaries, feature
names, etc.
♦ U.S. Radio Site Locations – coordinates of existing radio sites, including FCC
Wireless Licenses, FCC Antenna Site Registry, and some commercial site
providers.
♦ U.S. Frequencies – potentially available channels in geographic areas, per FCC
Wireless Licenses.
8.1.2.2.4 Propagation Model

For each tile, Hydra predicts signal strength using an improved algorithm based on
the industry-accepted Okumura model.1
8.1.2.2.5 Coverage Reliability

Hydra coverage maps indicate the probability (usually referred to as reliability) of the
radio system providing a minimum acceptable criterion, such as a voice Delivered
Audio Quality (DAQ) or a data Message Success Rate (MSR). Since system coverage
can never be one-hundred percent reliable, there will always be particular times and
1
Okumura, Yoshihisa et al, “Field Strength and Its Variability in VHF and UHF Land-Mobile Radio Service”,
Review of the Electrical Communication Laboratory, 16(9-10), Sept-Oct 1968, pp 825 873.

December 16, 2010

locations where the signal strength does not meet that needed to reach the
performance criterion. These locations of unsatisfactory performance are often
predictable in a coverage study. However, there are also areas of unsatisfactory
coverage that cannot be predicted due to unknown circumstances such as unusual
structures, tree density, ambient noise, atmospheric conditions, dataset errors, and
interference from co-channel or adjacent channel units operating outside their normal
service area.
Because these conditions exist and signals fade due to these
environmental and terrain factors, coverage must be described
statistically in terms of a percentage of locations that exhibit the
minimum acceptable criterion.
Hydra predicts Area reliability, defined as the probability of achieving a specified

performance criterion within a geographical area of interest. The area of interest is
the entire Service Area.
To provide radio systems with acceptably few communications failures throughout
the Covered Area, Motorola designs coverage at high Area reliabilities. The voice
performance criterion is going to be DAQ. It is also important to note that locations
outside of a Hydra map coverage area may still provide useable communications,
even though such locations do not achieve the minimum acceptable performance.
8.1.2.3 Hydra Capabilities

Hydra provides detailed performance simulation of the following Motorola wireless
network architectures:
♦ Voice coverage and traffic (Analog FM, ASTRO®, etc.).
♦ ASTRO 25 Integrated Voice & Data (IV&D) coverage and traffic.
If co-channel and/or adjacent-channel sites are known to exist, Hydra can model both
Interfered & non-Interfered coverage.
Hydra’s Frequency Re-Use Planning analysis takes into account both co-channel and
adjacent channel frequencies.
8.1.2.3.1 Voice Systems

Hydra’s coverage models use proven Okumura-based prediction methods and Monte
Carlo simulation techniques to provide coverage reliability maps. Voice coverage
models (Voice, ASTRO 25) provide system-wide coverage maps, as well as
subsystem maps (when applicable, e.g., for Simulcast cells and Receiver Voting), and
individual site maps.

December 16, 2010

8.1.2.3.2 Simulcast Coverage Performance
For a simulcast system, merely providing coverage maps of individual sites
(separately or on the same map) does not accurately represent the total system
performance, which depends upon differential delays and aggregate signal levels.
Therefore, Motorola has developed Hydra’s simulcast model, which uses the delay
spread methodology to simulate aggregate signal strength and audio phase angle
(delay) throughout the entire predicted coverage area. All locations within the
predicted coverage area are analyzed for the combined effect of signal strengths and
differential delays from the simulcast transmitters in the system. Hydra’s simulcast
coverage maps will show any areas predicted to have coverage problems caused by
out-of-phase signals and/or inadequate signal strengths. Hydra allows modeling with
varied transmitter launch delays to predict optimized simulcast coverage within the
area being evaluated.
8.1.2.3.3 Data Systems (ASTRO 25 IV&D)

Wireless data network performance is highly dependent on RF coverage reliability,
network protocol, and network traffic load. Hydra accurately predicts the coverage
and traffic performance of Motorola data systems by modeling the automatic protocol
retry mechanisms of data protocols. Hydra integrates RF coverage prediction,
network protocol modeling, and traffic engineering into a single simulation, and
utilizes Monte Carlo simulations as well as discrete event simulation techniques to
provide a tool that accurately predicts wireless network system performance.
Hydra uses the Okumura model for terrain-based propagation prediction, and adds
the modeling of the protocol behavior (try-based coverage) via a detailed protocol
simulation. Hydra models the relevant layers of the OSI protocol stack, from the
physical layer of the air interface to the application layer of the host and subscriber
entities.
Using this modeling approach, Hydra can account for all the elements that impede
network performance, from packet loss on the wireless link due to co-channel
interference, to packet latencies in the fixed end equipment introduced by protocol
behavior. Hydra’s modeling architecture allows true end-to-end system modeling.
8.1.2.3.4 Data Coverage

Hydra’s data coverage model, through multiple iterations, displays the area that meets
the MSR performance criterion requested by the user. The system-wide maps show
the composite coverage from multiple sites, at the specified area reliability criterion
and for the specified number of protocol tries.
8.1.2.3.5 Data Traffic

Hydra integrates coverage prediction into the traffic simulation, so the terrain and
subscriber distribution effects on packet collisions and interference are modeled in

December 16, 2010

the simulation. Traffic simulation results provide performance statistics for the RF
Station, Radio Channel, Controller, and Application(s). Hydra allows predicting the
performance of the actual network topology as designed by the engineer.
8.2 Summary
Hydra is continually updated for the latest technologies by Motorola’s Resource
Development Engineering team, to create the most accurate and up-to-date coverage
and traffic prediction tool. It is used extensively in the design and testing phases of
Motorola’s radio networks. Hydra provides accurate, easy-to-read maps of the
predicted coverage for your radio system.

December 16, 2010


December 16, 2010

8.1 Coverage Maps
The coverage maps listed in Table 1 below are provided on the following pages.
Talk-in and Talk-out coverage maps are provided for each subscriber configuration in
both the 8-Site Simulcast and the 7-Site Simulcast with Rocky Mountain ASR
designs. Each subscriber configuration is listed below.
Table 1: Coverage Maps
Coverage Maps
APX6500 Mobile Maps
APX6000 Portable with Halfwave Antenna On-street
APX6000 Portable with Halfwave Antenna In 4dB Residence
APX6000 Portable with Halfwave Antenna In 6dB Building
Talk-in and Talk-out coverage maps are provided for each individual RF site.
Additionally, Talk-in and Talk-out ITAC coverage maps are provided for mobiles
and portables (on-street) with portable and infrastructure sensitivity at -106dBm.
Site specific data is shown in Table 2 and Table 3 below:
Table 2: RF Site Transmission Line and Antenna Data
RF Site Transmission Line and Antenna Data

Site GTR8000 Transmit Antenna Antenna Antenna Type Effective
Power Line Gain (dB) Height Radiated
(dBm) Losses Power
(dB) (dBm)
Mt. Alto 50 -5.478 9 180 Sinclair SC479-HF1LDF(D04-E5608) 53.5
Shannon AT&T 50 -5.3828 9 300 Sinclair SC479-HF1LDF(D04-E5608) 53.6
Leonard Rd. 50 -6.6588 9 400 Sinclair SC479-HF1LDF(D04-E5608) 52.3
Hillindale 50 -5.3828 9 300 Sinclair SC479-HF1LDF(D04-E5608) 53.6
Fouche Gap 50 -4.658 5.5 180 RFI CC807-06 50.8
Cave Spring 50 -5.6848 9 350 Sinclair SC479-HF1LDF(D04-E5608) 53.3
Blossom Hill 50 -4.21 5.5 60 RFI CC807-06 51.3
Rocky Mountain 50 -4.658 9 120 Sinclair SC479-HF1LDF(D04-E5608) 54.3

December 16, 2010
Coverage Maps 8.1-1

Table 3: Radio Sensitivity and Power Data
Radio Sensitivity and Power Data

GTR8000 -109.44 dB, -112.9 dBm N/A N/A
APX / XTL Mobile -105.07 dBm -108.53 dBm N/A N/A
APX / XTS Portable N/A -108.53 dBm -100.83 dBm 26.3 dBm

December 16, 2010
8.1-2 Coverage Maps

Floyd County
Mobile
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6500 OUTBOUND OVERLAY (BEST OF)
Talk Out To APX6500 Mobile Operator C00145

0 4.11 8.21 mi Center Point 34:18:56.48 N 85:14:23.22 W
1 inch = 4.11 miles @ 1/260193
Monday, December 13 2010 3.40 Build 3671 Job Id : 1232714444.8.000.1.26
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential Restricted 8.1-1
Floyd County
Mobile
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6500 INBOUND OVERLAY (BEST OF)
Talk In From APX6500 Mobile Operator C00145

1 inch = 4.11 miles @ 1/260193
Motorola Confidential Restricted 8.1-1b
Floyd County
Mobile
7-Site Simulcast + Rocky Mtn ASR
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
Talk Out To APX6500 Mobile Operator C00145

1 inch = 4.11 miles @ 1/260193
Scale 1/260193
Motorola Confidential Restricted 8.1-1c
Floyd County
Mobile
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6500 INBOUND OVERLAY (BEST OF)
Talk In From APX6500 Mobile Operator C00145

1 inch = 4.11 miles @ 1/260193
Scale 1/260193
Motorola Confidential Restricted 8.1-1d
Floyd County
Portable On-Street
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6000 W HALFWAVE ANTENNA IN SWIVELCASE OUTBOUND OVERLAY (BEST OF)
Talk Out To APX6000 Portable Halfwave Operator C00145

0 4.11 8.21 mi Antenna in Swivelcase On-Street Center Point 34:18:56.48 N 85:14:23.22 W
1 inch = 4.11 miles @ 1/260193
Motorola Confidential Restricted 8.1-2a
Floyd County
Portable On-Street
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6000 W HALFWAVE ANTENNA IN SWIVELCASE INBOUND OVERLAY (BEST OF)
Talk In From APX6000 Portable Halfwave Operator C00145

1 inch = 4.11 miles @ 1/260193
Motorola Confidential Restricted 8.1-2b
Floyd County
Portable On-Street
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6000 PORTABLE HALFWAVE ANTENNA IN SWIVELCASE OUTBOUND OVERLAY (BEST OF)
Talk Out to APX6000 Portable Halfwave Antenna Operator C00145

0 4.11 8.21 mi in Swivelcase On-Street Center Point 34:18:56.48 N 85:14:23.22 W
1 inch = 4.11 miles @ 1/260193
Scale 1/260193
Motorola Confidential Restricted 8.1-2c
Floyd County
Portable On-Street
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6000 PORTABLE HALFWAVE ANTENNA IN SWIVELCASE INBOUND OVERLAY (BEST OF)
Talk In from APX6000 Portable Halfwave Operator C00145

1 inch = 4.11 miles @ 1/260193
Scale 1/260193
Motorola Confidential Restricted 8.1-2d
Floyd County
Portable in Residential Building
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring

0 4.11 8.21 mi Antenna in Swivelcase with 4 dB Building Loss Center Point 34:18:56.48 N 85:14:23.22 W
1 inch = 4.11 miles @ 1/260193
Motorola Confidential Restricted 8.1-3a
Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring

1 inch = 4.11 miles @ 1/260193
Tuesday, December 14 2010 3.40 Build 3671 Job Id : 1232714444.8.000.1.26
Motorola Confidential and Restricted 8.1-3b
Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6000 Portable Halfwave Antenna In Swivelcase Outbound Overlay (BEST OF)

0 4.11 8.21 mi in Swivelcase with 4 dB Building Loss Center Point 34:18:56.48 N 85:14:23.22 W
1 inch = 4.11 miles @ 1/260193
Scale 1/260193
Motorola Confidential and Restricted 8.1-3c
Floyd County
Portable In Residential Building
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

1 inch = 4.11 miles @ 1/260193
Scale 1/260193
Motorola Confidential and Restricted 8.1-3d
Floyd County
Portable in 6 dB Building
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring

1 inch = 4.11 miles @ 1/260193 (For Information Only)

Motorola Confidential and Restricted 8.1-4a
Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring


Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
Portable In 6 dB Building
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring


Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring


Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring


Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring


Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring

0 4.11 8.21 mi Antenna in Swivelcase with 25dB Building Loss Center Point 34:18:56.48 N 85:14:23.22 W

Floyd County
8-Site Simulcast
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring


Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
95% AREA MSE APX6000 PORTABLE HALFWAVE ANTENNA IN SWIVELCASE OUTBOUND OVERLAY (BEST OF)

Scale 1/260193
Tuesday, December 14 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Floyd County
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring

Scale 1/260193
Floyd County
Portable On-Street
Blossom Hill
Blossom Hill
95% AREA BLOSSOM HILL OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Blossom Hill
Blossom Hill
95% AREA BLOSSOM HILL INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Portable On-Street
Cave Spring
Cave Spring
95% AREA CAVE SPRING OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Cave Spring
Cave Spring
95% AREA CAVE SPRING INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Portable On-Street
Fouche Gap
Fouche Gap
95% AREA FOUCHE GAP OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Fouche Gap
Fouche Gap
95% AREA FOUCHE GAP INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Portable On-Street
Hillindale
Hillindale
95% AREA HILLINDALE OUTRELIABILITY APX6000 PORTABLE HALFWAVE SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Hillindale
Hillindale
95% AREA HILLINDALE INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Portable On-Street
Leonard Rd.
Leonard Rd
95% AREA LEONARD RD OUTRELIABILITY APX6000 PORTABLE HALFWAVE SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Leonard Rd.
Leonard Rd
95% AREA LEONARD RD INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Portable On-Street
Mt. Alto
Mt Alto
95% AREA MT ALTO OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Mt. Alto
Mt Alto
95% AREA MT ALTO INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Portable On-Street
Rocky Mountain
Rocky Mountain
95% AREA ROCKY MOUNTAIN OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6

Motorola Confidential and Proprietary 8.1-14a
Floyd County
Portable On-Street
Rocky Mtn.
Rocky Mountain
95% AREA ROCKY MOUNTAIN INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6

0 4.11 8.21 mi Antenna in Swivelcase On-street Center Point 34:18:56.48 N 85:14:23.22 W

Floyd County
Portable On-Street
Shannon AT+T
Shannon AT&T
95% AREA SHANNON AT&T OUTRELIABILITY APX6000 PORTABLE HALFWAVE SWIVELCASE WALKING CH 6

Floyd County
Portable On-Street
Shannon AT+T
Shannon AT&T
95% AREA SHANNON AT&T INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6


Floyd County
Mobile
800 MHz Mutual Aid System
5 Channels
ITAC
100 Watt GTR8000 Talk out to APX6500 with Projection World_Mercator

0 4.11 8.21 mi -106 dBm Faded Sensitivity Center Point 34:18:56.48 N 85:14:23.22 W
Operator C00145
Floyd County
Mobile
5 Channels
ITAC
95% AREA MSE APX6500 15W INBOUND OVERLAY (BEST OF)
15 Watt APX6500 Talk in to GTR8000 with Projection World_Mercator

Operator C00145
Floyd County
Portable
5 Channels
ITAC
95% AREA MSE APX6000 HALFWAVE HIP OUTSIDE 3W OUTBOUND OVERLAY (BEST OF)
100 Watt GTR8000 Talk out to APX6000 Projection World_Mercator

Operator C00145
Floyd County
Portable
5 Channels
ITAC
95% AREA MSE APX6000 HALFWAVE HIP OUTSIDE 3W INBOUND OVERLAY (BEST OF)
3 Watt APX6000 Talk in to GTR8000 with Projection World_Mercator

Operator C00145
8.1 Coverage Maps
The coverage maps listed in Table 1 below are provided on the following pages.
Talk-in and Talk-out coverage maps are provided for each subscriber configuration in
both the 8-Site Simulcast and the 7-Site Simulcast with Rocky Mountain ASR
designs. Each subscriber configuration is listed below.
Table 1: Coverage Maps
Coverage Maps
APX6500 Mobile Maps
APX6000 Portable with Halfwave Antenna On-street
APX6000 Portable with Halfwave Antenna In 4dB Residence
Talk-in and Talk-out coverage maps are provided for each individual RF site.
Additionally, Talk-in and Talk-out ITAC coverage maps are provided for mobiles
and portables (on-street) with portable and infrastructure sensitivity at -106dBm.
Site specific data is shown in Table 2 and Table 3 below:
Table 2: RF Site Transmission Line and Antenna Data
RF Site Transmission Line and Antenna Data

Site GTR8000 Transmit Antenna Antenna Antenna Type Effective
Power Line Gain (dB) Height Radiated
(dBm) Losses Power
(dB) (dBm)
Mt. Alto 50 -5.478 9 180 Sinclair SC479-HF1LDF(D04-E5608) 53.5
Shannon AT&T 50 -5.3828 9 300 Sinclair SC479-HF1LDF(D04-E5608) 53.6
Leonard Rd. 50 -6.6588 9 400 Sinclair SC479-HF1LDF(D04-E5608) 52.3
Hillindale 50 -5.3828 9 300 Sinclair SC479-HF1LDF(D04-E5608) 53.6
Fouche Gap 50 -4.658 5.5 180 RFI CC807-06 50.8
Cave Spring 50 -5.6848 9 350 Sinclair SC479-HF1LDF(D04-E5608) 53.3
Blossom Hill 50 -4.21 5.5 60 RFI CC807-06 51.3
Rocky Mountain 50 -4.658 9 120 Sinclair SC479-HF1LDF(D04-E5608) 54.3

December 16, 2010
Coverage Maps 8.1-1

Table 3: Radio Sensitivity and Power Data
Radio Sensitivity and Power Data

GTR8000 -109.44 dB, -112.9 dBm N/A N/A
APX / XTL Mobile -105.07 dBm -108.53 dBm N/A N/A
APX / XTS Portable N/A -108.53 dBm -100.83 dBm 26.3 dBm

December 16, 2010
8.1-2 Coverage Maps

9.1 Systems Integration Statement of Work
9.1.1 Systems Integration Overview

Motorola’s Systems Integration has established processes for systems implementation
that follow Motorola’s pioneering Six Sigma quality and adhere to best practices
frameworks such as ISO9001, TL9000, and ITIL. These processes effectively
address the requirements of Floyd County and focus on multi-agency/multi-
jurisdictional interoperability in multiple technology environments; complex system
solutions requiring a high degree of technical coordination and attention to the
smallest details.
This Systems Integration Statement of Work (SOW) describes the deliverables to be
furnished to Floyd County and the tasks to be performed by Motorola, its
subcontractors, and by the County in order to implement the proposed solution. It
contains information that describes the most current understanding of the work
required by both parties to provide a successful implementation.
It is understood that this SOW may be revised during contract negotiations or during
the Contract Design Review (CDR) and through any other Change Orders that may
occur during the execution of the project. If there are changes to the Scope of Work,
these changes must be reflected in this SOW before becoming binding on either
party. This SOW will be an Exhibit to the Contract negotiated between Motorola and
Floyd County. After contract execution, changes to the SOW will be made through
the formal contract Change Order process as set forth in the Contract.
9.1.2 Project Management

Project management is the application of knowledge, skills, tools, and techniques to
address our customer’s contractual requirements. To this end, there are nine
interrelated practices that are key to project management with each as important as
the others. These nine key practices are identified and further described below as:
1) Scope management
2) Schedule and Time management
3) Cost management
4) Quality management
5) Risk management
6) Subcontracts and Procurement management
7) Resources management
8) Communications management
9) Integration management (System Implementation Work Plan)

December 16, 2010
Systems Integration Statement of Work 9.1-1

9.1.2.1 Scope Management
Scope management is the process of maintaining control of the project in terms of the
aims, goals, and objectives of Floyd County. During the planning process, Motorola
strives to ensure that the project scope includes all the work required and only that
work required to satisfy the contractual requirements of the project. Motorola’s
understanding of the Scope of Work is defined in this SOW and in the System
Description.
9.1.2.2 Schedule and Time Management

The project schedule identifies Motorola and the County’s projected timeline for
completing the required tasks to successfully implement the County’s new digital
ASTRO25 radio and dispatch communications system. Upon contract award,
Motorola’s Project Manager will provide an updated project schedule with specific
sub-activities to display accurately the start and completion dates of the project. This
schedule will be updated regularly during the implementation of the project and
updates will be provided to the County’s Project Manager.
Motorola will work with Floyd County to identify all project responsibilities for the
successful completion of the project. Upon mutual agreement of the final project
schedule, the schedule will be incorporated as part of the final contract. Motorola will
closely coordinate the schedule with Floyd County to adjust, compensate for, and
take corrective actions as required by any schedule changes. Schedule delays that
occur through no fault of Motorola shall result in a modification of the schedule
and/or cost of the project and will be amended to the Contract as required.
The preliminary project schedule included in this response is directed toward
achieving an operational system, based on an estimated contract execution date of
May 31st, 2011. In order to assure timely completion, both Motorola and the County
must work towards compliance with all interim milestones.
9.1.2.3 Cost Management

During the execution of a project of this scope, contract change requirements may
arise from time to time to accommodate changes in scope. Either party may request
changes within the general scope of the contract. If a requested change causes an
increase or decrease in the cost or time required to perform the contract, Motorola
and Floyd County will agree upon an equitable adjustment of the Contract Price,
Performance Schedule, or both and document it as a part of the Change Order
process.

December 16, 2010
9.1-2 System Integration Statement of Work

9.1.2.4 Quality Management
It is Motorola’s policy to produce and provide products and services of the highest
quality which are responsive to the needs of our customers. Motorola has a well-
established reputation for designing and developing high quality products and
systems, on schedule, and within budget. Motorola adheres to the International
Standards Organizations (ISO) quality standards.
All work will be performed consistent with high quality commercial practice and in
accordance with Motorola’s Quality Standards for Fixed Equipment Installations and
all applicable manufacturer installation and maintenance manuals.
9.1.2.5 Risk Management

One of the major tasks of project management is to mitigate risk to our customers, to
Motorola, our subcontractors, the environment and the public. No project is entirely
without risk, but purchasing from Motorola reduces the risk by bringing the benefit of
our experience in implementing radio systems. Potential problems, which have been
resolved in the past, can be planned for and avoided. Motorola has worked closely
with Coosa Valley Communications to identify current County systems and
operations to better tailor our proposal. Motorola’s thorough review of customer
requirements and cost analysis allows us to address these issues and develop a system
implementation plan that is workable both from a time and cost standpoint while
minimizing the risk to all parties.
9.1.2.6 Subcontracts and Procurement Management

Motorola has extensive experience in managing programs with many large
subcontracted efforts. Motorola routinely employs teams of subcontractors as integral
members of our system integration teams and we have established policies and
procedures to manage these efforts. Early in the proposal phase, Motorola establishes
the groundwork that enables a rapid execution of subcontracts with each of our team
members. Motorola’s subcontracts define the tasks to be performed by and the
Project Schedule which is required from our subcontractors in accordance with our
prime contract.
9.1.2.7 Resource Management

Motorola believes that the success of any project depends upon obtaining and
applying the best resources to every aspect of the project through organizational
planning, staff acquisition, and team development. Our staffing approach brings
together a team of specialists, subcontractors, engineers, and project management
personnel under the direction of a Project Manager. This philosophy also pervades
our selection of suppliers, facilities, tools, and staff. By integrating our

December 16, 2010

subcontractor’s management and staff with the Motorola team, we are able to utilize
the best-qualified personnel for every task, regardless of company affiliation. The
team selections are based upon individual skill, prior experience, and qualifications.
Motorola’s key team members are described below:
Project Manager (PM) – Mark Hollomon

Motorola’s Project Manager’s primary responsibility is the successful implementation
of the County’s project. Successful implementation takes place when the project is
completed on schedule in accordance with the requirements and meets both
Motorola’s and the County’s financial objectives. The PM will have direct lines of
communication with the County’s Program Manager, Motorola Product Groups,
Systems Technologists, Engineering, Financial and Contractual departments. Mark
leads a team of five Georgia-based project managers and he resides in Douglas
County, GA.
Key responsibilities assigned to the PM are as follows:
♦ Act as Motorola’s single point of contact for all issues related to the contract.
♦ Provide the leadership and vision for the team to thrive in an environment
conducive to project success.
♦ Maintain overall responsibility for Motorola project resources including
additional project managers that will be assigned to implement major subsystems.
♦ Provide and update the detailed project schedule representing major events,
planned activities, and progress.
♦ Oversee the management of all field installation and implementation teams
ensuring all integration and optimization tasks are performed within contract
requirements.
♦ Ensure quality workmanship by all Motorola subcontractors.
♦ Oversee the product ordering process and assure manufacturing schedules meet
the requirements of the project schedule.
♦ Ensure all deliverables are met while achieving Motorola’s quality standards.
♦ Manage the project to ensure Total Customer Satisfaction.
♦ Manage contractual requirements including change orders and schedule
adherence.
♦ Prepare and conduct regular progress meetings and provide progress reports as
required.
♦ Ensure a successful transition to the warranty and maintenance phase of the
project.

December 16, 2010

Lead System Engineer – Gary Brady
Motorola’s Lead System Engineer's primary responsibility is to ensure technical
integrity of the system design. He is responsible for adherence to the documented
system design and implementation of that design through system optimization,
programming, and acceptance testing. Gary resides in Roswell, GA.
Motorola’s System Engineer has the responsibility for system design and
performance. The System Engineer is responsible for coverage analysis and
intermodulation studies, Acceptance Test Plan (ATP) development, path and
frequency coordination preparation, and development of site design system
programming parameters. Additionally, the System Engineer will participate in the
system staging process and will be available to assist the County in fleetmapping and
determining the subscriber unit configurations.
Key responsibilities assigned to the lead system engineer are as follows:
♦ Ensure all contractual requirements are met through the system design and
performance.
♦ Perform coverage design, analysis, and intermodulation studies
♦ Manage all Motorola engineers assigned to the County’s project
♦ Create, review, and validate of the path and frequency plan
♦ System documentation development and revision control
♦ Develop all acceptance test plans and procedures
♦ Participate in product staging and testing at Motorola’s Customer Center for
Solutions Integration (CCSi)
♦ Assist the County in fleetmap development and subscriber unit configuration for
the following:
• Subscriber unit ID plan
• Talkgroup plan
• Talkgroup layout and accessibility within each subscriber unit
• Interoperability plan for mutual aid talkgroups and conventional channels
• Console programming template
Lead System Technologist

The Lead System Technologist (ST) is responsible for assuring that the system is
tested and optimized to perform as designed. The Lead ST oversees the team of
technologists responsible for all sub-systems and the integration of those sub-systems
into the final system. The Lead ST is responsible to oversee installation quality,
programming, optimization and testing of the integrated system to ensure it operates
according to the specifications and system design. Motorola has a team of 16 Atlanta-
based ST’s available for project support.

December 16, 2010

Key responsibilities assigned to the Lead System Technologist are as follows:
♦ Participate in the staging and testing of the system at Motorola’s Customer Center
for Solutions Integration (CCSi).
♦ Perform site link verification testing to validate connectivity and adequate
performance at the County’s sites.
♦ Oversee the integration and optimization of all system hardware and software.
♦ Participate in all equipment programming and configuration development
♦ Perform optimization of RF equipment.
♦ Perform optimization of the dispatch consoles.
♦ Participate in the Acceptance Test Plan.
♦ Assist in the development of the system cut-over plan.
♦ Provide customer technical support.
Local Motorola Service Shop (MSS) – Coosa Valley Communications

Motorola will partner with Coosa Valley Communications located in Rome, Georgia
for field installation, subscriber unit programming and installation, and assistance
with system optimization and testing. In addition to Coosa Valley, Motorola has
extensive technical resources to utilize for this project in the north metropolitan
Atlanta area. Currently there are four MSS’s with more than 15 technicians with P25
system experience. Also supporting Coosa Valley is Motorola’s team of 16 Atlanta-
based System Technologists, who are our most advanced field technical resources.
Coosa Valley has been fully engaged with Motorola’s system engineering and
Systems Integration team in developing the system design in response to the County’s
RFP and ensuring that Motorola’s proposed scope is accurate.
Coosa Valley will be fully involved in the system implementation, integration, and
cutover assuring that their Service personnel are fully trained on and understand the
ASTRO25 radio system in order to provide effective system maintenance after
acceptance of the system during warranty support.
Sub-System Subcontractors
Motorola’s PM will coordinate the activities of our subcontractors to assure cost-
effective performance and resolution of technical interface issues during design as
opposed to during integration activities.
The PM will be the single authority for subcontract actions and reporting and will
have the full responsibility for quality performance, schedules, and cost control.
Motorola will use a straightforward procedure for managing and controlling work
assignments to subcontractors.
Subcontractors have been selected for this project based on their experience and
many have worked for Motorola on numerous projects. Each subcontractor will
assign a lead manager who will be responsible for their company’s performance.

December 16, 2010

These managers will report directly to Motorola’s Project Manager on contractual
issues and to the System Engineer on specific technical assignments. All
subcontractors will submit as-needed progress reports to Motorola describing
progress, level of effort, and anticipated problems which will be integrated into the
project’s tracking system. The subcontractors’ reports will serve as Motorola’s
primary mechanism for ensuring that they remain on track to deliver their promised
results.
The current proposed subcontractors for the Floyd County project are as follows:
Coosa Valley Communications
Coosa Valley Communications provides telecommunications installation and support
services in the local Rome, Floyd County area. Coosa Valley will be the primary
provider of installation services for the radio network infrastructure in this proposal.
Ceragon Networks, Ltd.
Ceragon will provide design, path optimization, FCC licensing, staging, installation,
cutover and field acceptance testing for the microwave system. Since 1996, Ceragon
Networks Ltd. (NASDAQ: CRNT) is a leading provider of high-capacity TDM and
Ethernet wireless backhaul solutions.
United Tower Company
United Tower will provide construction and installation services for tower site
components including installation of lines, antennas, and associated materials; light
changes, painting towers to FCC specifications, tower erections, and installation of
foundations. United Tower is a family-owned business for 42 years and is located in
Monroe, Georgia.
MACTEC
MACTEC will provide site design services including environmental site assessment,
NEPA/FCC compliance services, geotechnical investigation, foundation design,
construction testing, structural evaluation of existing towers, construction drawings,
and construction materials testing. MACTEC is headquartered in Alpharetta,
Georgia.
9.1.2.8 Communications Management
Status Meeting and Reports
Motorola’s PM, or designee, will attend all project status meetings with Floyd County
as determined during the Contract Design Review meeting. Motorola will record the
meeting minutes as related to the system proposed herein and supply this information
to Floyd County’s Project Manager within five business days. The general agenda
will include the following:

December 16, 2010

♦ Updated Project Schedule
♦ Overall project status compared to the Project Schedule
♦ Product or service-related issues that may impact the Project Schedule
♦ Current status of action items and responsibilities in accordance to the Project
Schedule
♦ Tasks completed over the last 30 days
♦ Tasks to be completed over the next 30 days
♦ Customer satisfaction issues
Any additional concerns of either Floyd County or Motorola will be added to the
general agenda.
Progress Milestone Submittal

During the course of the project, Motorola will submit milestone completion
documentation to Floyd County. This documentation will be submitted in accordance
with the milestone schedule as agreed upon during the Contract Design Review. The
County’s approval of each milestone will signify confirmation that the work
associated with the scheduled task has been completed.
Correspondence and Approvals

Floyd County shall respond to all Motorola submittals, correspondence, and written
requests within five calendar days of receipt. Any responses rejecting submittals,
requests or correspondence will contain a detailed explanation in support of such
rejection referencing the contract section or item number affected.
9.1.3 Integration Management - System Implementation Work

Plan
An effective work plan ensures not only a timely and orderly implementation, but
also the optimization of system effectiveness. This section outlines the Systems
Integration processes that Motorola will incorporate throughout system
implementation to ensure Floyd County’s users a smooth and efficient transition to
their new communications system.
Motorola has developed the implementation plan contained herein for most efficient
utilization of resources and earliest possible completion of the project.
Motorola’s process for the integration of the proposed communications system will
ensure that the implementation adheres to the highest quality and process standards.
Several of the steps of this Systems Integration process parallel and complement
Motorola’s Project Management Team activities previously discussed. The major
phases of the Motorola Systems Integration process are:
♦ Contract Initiation

December 16, 2010

♦ Contract Design Review (CDR)
♦ System Fleetmap/Template Definition
♦ Ordering and Manufacturing
♦ Site Construction and Development
♦ Systems Factory Staging
♦ Delivery to the Field and Inventory
♦ Fixed Equipment Installation
♦ System Training
♦ System Programming and Optimization
♦ Functional Acceptance Testing
♦ Coverage Acceptance Testing
♦ System Cutover
♦ System Acceptance
♦ Project Finalization
The steps listed above are described in detail in the following subsections below. By
following these steps and applying the previously described Project Management
Team arrangement, Motorola can monitor and control all aspects of the
implementation to ensure successful on-time completion, Six Sigma quality, and
Total Customer Satisfaction to Floyd County.
9.1.3.1 Contract Initiation

After the contract is signed, the implementation process will begin with the project
kickoff meeting. The date, time, and location of the meeting will be mutually agreed
upon between Motorola and the County. The objectives of this meeting include:
♦ Introduction of all project participants
♦ Review of the roles of the project participants to identify communication flows
and decision-making authority between project participants
♦ Review of the overall project scope and objectives
♦ Review of the resource and scheduling requirements
♦ Review of the project schedule to address any upcoming milestones or events
♦ Review of the team interaction, meetings, reports, milestone acceptance, and the
County’s participation in particular phases
9.1.3.2 Contract Design Review

The goal of the Contract Design Review process is to verify and finalize agreement
on the overall design and deliverables. During the Contract Design Review,
Motorola will provide the following documents to the County for its review:
♦ Project Schedule
♦ Preliminary Site Layout Drawings
♦ System Block Diagrams

December 16, 2010

♦ Sample Antenna Network Diagrams
♦ Site Connectivity Diagram
♦ Acceptance Test Procedures
Frequency Licensing
As required by the RFP, Motorola will provide services and costs required to properly
coordinate and license all the needed channels for the proposed system. However, as
mandated by the FCC, the County, as the licensee, has the ultimate responsibility for
the frequencies and licenses over the life of the system.
Motorola’s subcontractor will research and complete all necessary FCC Licensing
Forms 601 for the following frequencies. Motorola’s subcontractor will also assist
with answering any questions that the frequency coordinator and/or the FCC have
regarding the licensing of the County’s radio system and track the following
applications through to FCC grant. Motorola’s cost includes the filing of the FCC
construction notification.
Dependent upon the final system configuration, the following applications will be
filed on behalf of Floyd County:
8-Site Simulcast Design
♦ 800MHz NPSPAC
“New” 10 frequencies at 8 sites
♦ 800MHz 8TAC Mutual Aid
“New” 5 frequencies at 1 site
♦ VHF Conventional (Fire Paging and Alerting)
“Modified” 1 frequency at 1 site
♦ 800MHz Conventional (EMS Alerting)
“New” 1 frequency at 1 site
7-Site Simulcast, 1-Site ASR Design

♦ 800MHz NPSPAC
“New” 5 frequencies at Rocky Mountain
♦ 800MHz NPSPAC
“New” 10 frequencies at 7 sites
♦ 800MHz 8TAC Mutual Aid
“New” 5 frequencies at 1 site
♦ VHF Conventional (Fire Paging and Alerting)
“Modified” 1 frequency at 1 site
♦ 800MHz Conventional (EMS Alerting)
“New” 1 frequency at 1 site
Option: Transportable Trunked Repeater

♦ 700/800MHz NPSPAC
“New” 6 frequencies per repeater

December 16, 2010

Option: Mobile Repeater
♦ 700MHz NPSPAC
“New” 1 frequency per repeater
9.1.3.3 System Fleetmapping and Template Definition

Fleetmapping is the process of configuring a system’s features and programming
parameters to function according to the unique operational requirements of each
participating agency. Programming decisions for system infrastructure, dispatch
consoles, and subscriber units are critical to tailoring system performance. Motorola
will provide assistance to the County in making informed equipment programming
choices based on their unique operational expectations.
Fleetmap requirements (subscriber configuration for end users) must be determined
prior to subscriber unit programming and installation, but ideally, prior to system
staging. This is a major undertaking and will require a joint effort on the part of the
County and Motorola to make decisions according to the Project Schedule. Because
the high level management of the new digital ASTRO25 system is so critical,
Motorola recommends that the County set up a fleetmap committee consisting of
members of the various user agencies that will utilize the system. The fleetmapping
committee will be the primary point of contact with Motorola during the
fleetmapping process and will provide all customer inputs and approve all final
programming decisions. The fleetmapping committee is also responsible for
reviewing current radio standard operational policies, and then determining what
modifications, if any, will be required to accommodate operational changes needed to
fully utilize the new digital ASTRO25 system. It is recommended, as a best practice,
that the County’s committee create a “Console Dispatch and Subscriber Unit
Programming Policy” to discuss and determine how each group of subscribers will
operate on the system and which purchased subscriber features should be activated.
This committee should be responsible for setting standardized system management
and operational policies (SOP) that will apply to all end users. Examples of elements
to be included in the SOP are:
♦ Which users can access the system

♦ Who will have rights to modify the radio database
♦ What neighboring jurisdictions have rights to utilize the system
♦ What subscriber features are available to which users
♦ What are the procedures if a subscriber unit is lost or stolen
Motorola will work with the County after contract award to develop the fleetmap for
the system and participating agencies. Motorola will provide a System Engineer to
work with the County’s fleetmapping committee representing the user groups.

December 16, 2010

Motorola’s Engineer will provide detailed consultative advice on the features and
functionality of the mobiles, portables, and consoles purchased by the County. This
step requires careful planning between Motorola and the County’s committee
representing the end users. Motorola will conduct meetings with this committee to
define the fleetmapping process, discuss effective organization of talkgroups and
detail how to set up the system/radio parameters. It is important to stress that
console/subscriber unit programming decisions are the responsibility of the County’s
fleetmapping committee in its entirety.
Based on the final system fleetmap, the configurations for the consoles (talkgroups by
operator position, conventional and auxiliary interfaces) and logging talkgroups will
be developed by Motorola for programming into the fixed equipment. All
infrastructure equipment, mobiles, portables, terminals, and any other radio fixed
network equipment in the system will be programmed based on County-approved and
signed fleetmap and programming templates.
Motorola will create and enter all database record entries into the system based on the
County’s final approval. Final radio codeplug quantities and fleetmapping services
will be determined based on the subscriber unit configurations purchased by the
County.
9.1.3.4 Ordering and Manufacturing

After the kickoff meeting, Motorola will process the orders for equipment and begin
equipment manufacturing. The manufacturing facilities will test each subsystem from
its base kit or module level up to the complete subsystem. In addition to the
individual tests applied to all units shipped, Motorola’s Product Quality Engineering
Department will perform additional tests on periodic samples.
9.1.3.5 Site Construction and Development

During the manufacturing and staging process, the field site preparation will be
underway so that the sites will be ready for installation when the equipment is
shipped from Motorola’s staging facility. Motorola’s Project Installation Supervisor
will review each site, make assessments for the scheduling of required work, and
ensure that the sites are ready for installation according to the project schedule.
Motorola will be responsible for obtaining the required local building permits for
work provided in this proposal. Motorola requests Floyd County’s assistance in
securing permits. Permits required for work other than provided in Motorola’s
proposal and/or work being performed at sites by Floyd County will be the County’s
responsibility.

December 16, 2010

Floyd County will be responsible for all zoning issues, including but not limited to,
permits, variances, waivers, easements, right of way clearances, FAA clearances,
EPA/DEP requirements, or any other requirements of local, State, or Federal
regulations with regard to the permission to develop these sites.
Motorola will begin work with mutual agreement by Floyd County and Motorola that
the sites are deemed ready and released by Floyd County according to the Project
Schedule. At a minimum, Site Ready will consist of adequate room in an existing
building or shelter to accommodate the equipment to be installed with electrical
service and internal distribution in place.
For all proposed site locations, Floyd County will be responsible for paying all usage
costs of power, generator fueling, telephone lines, and microwave both during the
construction/installation effort and on an ongoing basis. Motorola will fill the new LP
tanks one time as part of the installation.
Please refer to Section 9.2 (Site Development SOW) for a detailed description of the
site development work that Motorola has included in this proposal to meet the
County’s specifications.
Site Access
Floyd County shall provide free and open access to all Floyd County-owned or leased
sites for work as defined in this proposal. Access must be available 24-hours a day
during the course of this project. This includes, but is not limited to, the following:
♦ Provide escort at no charge if escorts are required at any particular site. The
availability of such escorts shall not be unreasonably withheld.
♦ Arrange site permission and provide keys to all the locks at sites.
♦ Issue temporary identification cards to Motorola personnel and its subcontractors,
if required, for access to Floyd County facilities.
9.1.3.6 Systems Factory Staging

Motorola is one of the world leaders in developing and implementing large-scale
communications systems. As part of our commitment to quality, we propose the
staging of equipment before shipment. Motorola achieves its high levels of customer
satisfaction by assembling and testing every communications system sold to stringent
quality and functional performance tests prior to the system shipping.
Motorola will provide factory staging at Motorola’s Customer Center for Solutions
integration (CCSi) for ASTRO25 trunking and console equipment and a
representative sampling of subscriber units, if purchased, included in this proposal.
This staging is the same activity that Floyd County representatives attended in
December of 2008 for the Tennessee Valley / Northwest Georgia Regional System.

December 16, 2010

Motorola will assemble the system hardware at our factory staging facilities. Physical
set up and location of hardware will comply with the County’s approved equipment
layout plans. All cables will be cut and labeled with to/from information to clarify
interconnection for field installation. Cables will be cut to fit the room layout plan
specifications. All provided equipment cables will be connectorized and tested.
After assembling the equipment, Motorola’s staging technicians will power up the
equipment, load software, set levels, and optimize the equipment. System parameters
will be set according to inputs from the field team. System software and system
features will be tested and validated. All system levels will be set according to
specifications to verify proper end-to-end connectivity. These settings will be
recorded and documented to provide baseline information to the field integration
team. Once the system or subsystem has been assembled, optimized, and integrated
as a complete working unit, the system will be tested according to the staging
acceptance test procedures.
Motorola will coordinate with the County for a visit to Motorola’s CCSi in
Schaumburg, Illinois to witness the system testing. This visit will provide the County
with the opportunity to see the equipment assembled and working as an integrated
system. Most functionality and features of the communication system that are capable
of operation in a factory environment will be tested and verified for the County. The
passing of acceptance testing will be the determination that the equipment is ready to
be shipped to the field.
Factory staging allows systems to go through an exercising period before leaving the
staging area. This allows testing of components or boards for proper operation as a
complete system before shipping to their final destination. At completion of system
staging Factory Acceptance Test Procedures (FATP), Motorola will inventory the
equipment and update the inventory database with this information to assist in
tracking upon delivery to the field.
The County will be responsible for all travel, lodging, meals, and incidental costs for
County personnel and representatives to witness the Factory Acceptance Testing
during system staging.
9.1.3.7 Delivery to the Field and Inventory

All equipment will be delivered to Motorola subcontractor locations for inventory
and storage, as needed, and then to County sites for field installation. Access to
County sites by Motorola and its subcontractor personnel will be arranged by the
County prior to the delivery dates.
The County shall, upon notification of equipment delivery by Motorola, provide
personnel to catalog all received goods and attach property tags (if required).

December 16, 2010

9.1.3.8 Fixed Equipment Installation
Motorola will be responsible for the installation of all fixed equipment contained in
the equipment list and as outlined in the System Description based upon the agreed-to
floor plans at the sites where the physical facility improvement is complete and the
site is ready for installation. All equipment will be installed in a neat and professional
manner, employing a standard of workmanship consistent with Motorola’s own R-56
installation standards and in compliance with applicable National Electrical Code
(NEC), EIA, Federal Aviation Administration (FAA), and FCC standards and
regulations.
For installation of the fixed equipment at the various sites, Motorola will furnish all
cables for power, audio, control, and radio transmission to connect the Motorola-
supplied equipment to the power panels or receptacles and the audio/control line
connection point. All cabling will be properly connected and terminated based upon
Motorola’s installation quality standards and clearly labeled at both ends. All
associated punch block connections will also be properly labeled. All cabling and
punch block connections will be recorded into the final system as-built
documentation. All cabling associated with computer equipment will be shielded and
grounded based upon the manufacturer’s specifications. Cables for computer
terminals will provide a minimum of five feet of slack to allow for slight adjustments
in positioning of the equipment (if requested). All additional cabling will be neatly
coiled and secured with cable ties.
All Motorola-provided equipment will be properly grounded to the site’s grounding
system. All cabinets, racks, enclosures, telephone circuit surge protectors, and
transmission line surge protectors provided by Motorola will be connected to the
single point ground plate. Ground connections will be connected using approved split
bolt or clamp connections. All painted surfaces where ground connections will be
made will be scraped and dissimilar metal connections treated with an anti-oxidant
compound.
To minimize interference, all cabling will be grouped by category and run separately.
Cable categories will consist of control cabling (power, data), RF, and ground. All
cables will be run and secured neatly in cable tray, under elevated flooring, conduit,
or by other appropriate means. Any cuts in computer flooring will be dressed with a
protective grommet to avoid sharp edges. All sawdust and metal shavings will be
vacuumed from beneath the computer flooring. Entry holes placed in cabinets will
have grommets installed to protect the cables from damage. Any wiring connections
terminating at punch blocks will utilize appropriate bridging clips for cross
connections.
Motorola will follow R-56 installation practices in the assembly and installation of all
antenna systems. Motorola will utilize appropriate connectors and assemble the
cables according to the manufacturer’s specifications. All transmission lines will be
run and installed without exceeding the manufacturer’s specified bending radius.

December 16, 2010

Transmission lines will be properly secured and/or fastened to the cable tray or ladder
attached to the tower using the manufacturer’s recommended devices.
During field installation of the equipment, any required changes to the installation
will be noted and assembled with the final ‘as-built’ documentation of the system.
The as-built documents will be provided at the end of the project along with the
maintenance and operator manuals. Upon completion of installation, Motorola will
perform final site quality audits to verify proper physical installation and operational
configurations of each individual site.
The following sections describe the major system components to be installed at each
County location:
ASTRO25 FNE Equipment Installation

Motorola will install the following equipment at the Floyd County 911 Zone Core:
♦ Zone controllers and servers
♦ Telephone Interconnect
♦ GPS-sourced Network Timing Protocol unit
♦ MOSCAD SNT, server, RTU, punchblock, and associated equipment
♦ Microwave equipment and DC power plants
♦ Associated switches and routers
♦ ISSI Gateways and firewall
♦ IV&D Packet Data Gateway (PDG)
♦ Firewall and server
♦ AVL application server
♦ Optional: Dual Prime site equipment
Motorola will install the following equipment at the Mount Alto Prime Site:
♦ Prime site controllers
♦ Comparators
♦ GPS Trak unit
♦ MOSCAD NFM RTU
♦ (5) 800MHz Quantar base stations for ICALL
♦ 800MHz Quantar base station for EMS Alerting
♦ existing VHF MTR2000 repeater from the current Mount Alto site to the new
Prime Site
♦ Combiner and multi-coupler

December 16, 2010

Motorola will install the following equipment at seven simulcast remote sites (Mount
Alto, Shannon AT&T, Hillindale, Leonard Road, Cave Springs, Blossom Hill, and
Fouche Gap):
♦ (2) ESS cabinets with five GTR8000 base stations each
♦ MOSCAD NFM RTU
♦ GPS Trak unit
♦ TTA control unit
♦ (3) XTL5000 control stations
♦ Microwave and DC power plants
Motorola will install the following equipment at Rocky Mountain that will be either
simulcast or ASTRO25 Site Repeater (ASR) sites depending on the final
configuration determined by the County:
Simulcast Site Option:

♦ (2) ESS cabinets with five GTR8000 base stations each
♦ MOSCAD NFM RTU
♦ GPS Trak unit
♦ (2) control stations
ASR Site Option:

♦ ESS cabinets with five GTR8000 base stations
♦ MOSCAD NFM RTU
♦ control stations
♦ Associated network equipment
Console and Control Station Installation

Floyd County E911 Center:
Motorola will install the following console equipment into space and furniture
provided by the County at the Floyd County E911 Center.
♦ (6) MCC7500 console operator positions and ancillary equipment

December 16, 2010

♦ (6) XTL2500 800 MHz control stations (one per operator position) for backup
dispatch
♦ Back-room equipment:
• (11) XTL2500 control stations for logging

• (1) GenWatch3 de-trunked logging server
• (1) VHF high-band control station for Fire Paging
• Antenna systems and combiners for the control stations provided
Floyd County EOC Backup Center:
Motorola will install the following console equipment into space and furniture
provided by the County at the Floyd County Backup EOC and connect the console
site via microwave to the Zone Core at Floyd County E911. Motorola will oversee
the expansion of the County’s existing CAD system to add the five new positions,
however, Motorola recommends that Floyd County contract directly with Intrado to
supply and implement their software.
♦ (5) MCC7500 console operator positions and ancillary equipment
♦ (5) XTL2500 800 MHz control stations (one per operator position) for backup
dispatch
• (1) existing VHF high-band control station for Fire Paging

(relocated from Floyd County E911)
• Antenna systems and combiners for the control stations provided
Floyd County Jail:

Motorola will install the following equipment:
♦ MIP5000 console operator position and ancillary equipment
• (6) XTL5000 800 MHz consolettes with ceiling-mounted antenna

system
• (1) CDM1250 VHF control station with ceiling-mounted antenna
• (7) Radio Gateways
• (32) MC1000 tone-remote desksets and ancillary equipment
• (1) 800MHz P25 repeater with removal of the old repeater to a
County-identified location

December 16, 2010

Floyd County Sheriff’s Office / Courthouse:

system
Floyd County Prison:


system
• (1) 800MHz P25 repeater
Control Station Installations:

Motorola will install antennas and RF cabling (up to 50 feet of coax per antenna) for
the control stations, consolettes, and desksets.
The cabling will be properly connectorized, grounded, and will be run via the least
obtrusive way to the outdoor or ceiling antenna location. A lightning surge protector
will be provided and installed to protect the cabling. Cable entry into each
building/shelter will be through existing feed-through and sealed with silicone, unless
the County provides an entry plate and boot.
Motorola will perform the following tasks for the control stations installations:
♦ Create the installation plan.
♦ At each site, assist Floyd County in determining the locations of control stations
and desk sets.
♦ Install RF local control stations.
♦ Install line (not greater than 50 feet in length) and antenna system (connectors,
coax grounding kit, antenna, and surge protection).
♦ Connect to Floyd County’s supplied ground point within six cable feet of the unit.
♦ All control stations will be programmed once prior to delivery from a template
that will be approved by Floyd County.

December 16, 2010

Console Equipment Optimization
Motorola will perform the console-programming task based on the console templates
designed and approved during the fleetmapping process. The County shall supply the
required radio ID and alias information so that the Alias database can be setup for
interfacing to the console. The County will define all logging recorder information
including which talkgroups will be logged. This information should be provided prior
to the console installations. Based on County-supplied information, Motorola will
setup the consoles to perform the dispatching operation on the new radio system.
For any existing repeaters or control stations that are to be interfaced with the new
console system, Motorola assumes that the remote control capability of these devices
is via “Tone Remote” signaling. Motorola has included four sets of adapters for DC
remote control capability.
Microwave Network Installation

Motorola will install a new microwave network that will provide connectivity
between the new radio tower sites and allow for future growth, as required by the
County. Motorola will furnish and install FibeAir IP-10 radios, DC power, and
antenna systems to support this major conversion. The microwave install will be done
in phases and assumes that the roof of the Floyd County E911 Center will support the
antennas outlined below and that the Back-up EOC roof will provide the elevation
required to complete the hop.
Motorola will provide and install a wireless Ethernet loop with monitored hot stand-
by protection for each link, plus loop protection for the core simulcast sites shown
below:
♦ Floyd County E911 Center (loop)
♦ Mount Alto (loop)
♦ Fouche Gap (loop)
♦ Cave Springs (loop)
♦ Leonard Road (loop)
♦ Shannon AT&T (loop)
♦ Hillindale (loop)
Motorola will provide and install a wireless Ethernet hop from the loop to the
following sites with monitored hot stand-by protection:
♦ Floyd County Backup EOC (spur)
♦ Rocky Mountain (spur)
♦ Blossom Hill (spur)
♦ Taylor’s Ridge (NWGA) (spur) (for ISSI connectivity to TVRS)

December 16, 2010

Motorola has performed preliminary paper path studies to determine the initial
microwave design. To verify the suitability of the proposed microwave paths,
Motorola will conduct, with its microwave subcontractor, a path survey analysis and
will generate a Microwave Path Survey Report including path calculations and
profiles. The path survey will confirm the exact geographical location of sites, the
heights of the towers, and the waveguide length requirements as well as the actual
antenna height requirements by identifying obstructions and reflections.
Motorola will present the path survey report to Floyd County for approval, and will
assist the County with frequency coordination, FCC licensing, and FAA applications.
Should the actual field path survey reveal an obstruction to a clear path for the
microwave signal, Motorola will provide documentation detailing the obstructions
and work with the County on a design modification. It will be the County’s
responsibility to coordinate/negotiate with adjacent property owner(s), state and local
agency(s), or any other entity for the removal of the obstruction.
The microwave installation will be completed on a site-by-site and hop-by-hop basis.
The new ASTRO25 radio and console sites will be connected to the network at the
completion of the microwave acceptance testing. The microwave manufacturer will
conduct factory testing, but no formal staging will be held for the microwave sub-
system.
Leased Telephone Lines and Circuits

During implementation, Motorola will give Floyd County notices or readiness of sites
to receive the communications links. Motorola will work closely with the County’s
Project Manager to ensure the appropriate timing for the procurement of these
communications links.
The County shall supply four analog telephone lines for the telephone interconnect
feature at the Floyd County E911 Center as well as the 911 trunk lines for the EOC
Backup Center.
All transport media shall have demarcation points within ten feet of Motorola-
provided equipment and should be properly labeled and shall be supplied with
adequate protective devices as required for equipment operation. Motorola will
provide testing to assure that the supplier installs the media to Motorola’s technical
specifications.
Bi-Directional Amplifiers (BDAs) Installation

Should it be determined, as outlined in the Coverage Acceptance Test Procedure, that
BDA systems are required to meet the coverage requirement in any of the buildings,
successful implementation of those BDA systems will require that certain
responsibilities be managed by Motorola, its subcontractors and Floyd County.
These responsibilities are outlined as follows:

December 16, 2010

♦ A description of the responsibilities for Motorola, its subcontractors, and the
County.
♦ The assumptions taken into consideration during the development of this
proposal.
Motorola will perform the following tasks:
♦ During the Coverage Testing phase, determine the need for BDA systems within
the buildings specified by the County as requiring in-building coverage.
♦ Develop specific designs of BDA systems for each building, as required, by
analysis of building plans and drawings and performing full site surveys.
♦ Provide all of the equipment necessary for the BDA system installations inside
any identified buildings.
♦ Provide detailed system designs for each building, outlining internal and external
antenna installation points and cable distribution network.
♦ Work with the County’s assigned Project Manager to ensure that all necessary
facility preparation work is defined and completed prior to start of the
implementation.
♦ Install the 800MHz BDA system as defined in the system description. This
includes installation of the following items:
External antenna system
In-building antenna system and splitter distribution network
800MHZ Bi-directional amplifier unit
Floor to floor coaxial or fiber cable runs
Inter-building cable installations
♦ Terminate and connect coaxial or fiber cables.
♦ Optimize system for optimum performance.
♦ Conduct post-installation testing.
♦ Provide final As Built System Documentation
♦ Provide notification of site access requirements, as well as any changes in those
requirements, to the County throughout each phase of the project.
The County will be responsible for the following tasks:
♦ Obtain the written agreement of each building owner to install a BDA system.
This will include the installation of external antennas, BDAs, internal distributed
antennas and any of the cabling required to connect them within the premises.
♦ Obtain architectural plans or drawings for each building in which a BDA system
will need to be installed.
♦ Assist Motorola with making arrangements with each building owner for site
access during each phase of the project. This will include, but may not be limited

December 16, 2010

to, initial coverage testing and site surveys, installation, optimization and
post-installation testing.
♦ Work with each building owner to insure that adequate space has been provided
for the installation of the BDA equipment.
♦ Work with each building owner to insure that the necessary 120 VAC electrical
outlet(s) will be available at each of the BDA locations. If possible, electrical
outlets should be UPS/Generator backed.
♦ Work with each building owner to determine any special requirements they may
have for the installation of the BDA equipment and make arrangements to have
any necessary building modifications that result from these requirements prior to
the beginning of the installations. “Special requirements” refers to any conditions
for installation the building owner may require that are not required by local
building codes.
♦ Work with each building owner to insure access for cable transfers between any
buildings with shared BDAs.
♦ Assign a single point of contact (Project Manager) to address the following:
• Initiate notice to proceed after initial project kickoff meeting.
• Arrange for site access as needed during system design, installation,
optimization, and testing.
• Work with Motorola’s Project Manager to plan and facilitate system
installation.
• Facilitate installation team during hours of implementation.
• Approve equipment installation plan
• Ensure that any necessary facility improvements or modifications are
completed in a timely fashion.
• Participate in post-installation system testing
♦ Provide documentation of each BDA system installation to the respective building
owners. This documentation should become part of the facilities and maintenance
plans of the buildings to ensure the integrity of the installations during any future
building modifications or installations.
♦ Arrange to have each BDA system tested on a regular basis. Such testing can be
as simple as making radio calls from within the buildings to verify that the
required coverage is still being provided within the buildings.
♦ Arrange with each building owner for ongoing site access during the warranty and
service phase of the project. Provide Motorola with the contact information
necessary to gain access to each building in the event that an on-site service
response becomes necessary.

December 16, 2010

Assumptions:
♦ Motorola assumes that the County will be able to successfully obtain access to
each building for coverage testing and that the County will be able to obtain
permission from each building owner to install a BDA system, if deemed
necessary by the testing. Motorola is not responsible for meeting the in-building
coverage requirement in any building where access for coverage testing is not
provided or where the installation of a BDA system is not permitted.
♦ Motorola assumes that the County will be able to obtain architectural plans or
drawings for each building in which a BDA system will be installed. Motorola is
not responsible for meeting the in-building coverage requirement in any building
for which plans are not available. Motorola is also not responsible for any project
schedule delays resulting from the inability of the County to obtain building plans
or drawings and provide them to Motorola in a timely fashion. Any additional
project costs resulting from such delays can be quoted by Motorola through the
change order process.
♦ Motorola assumes that the County will be able to arrange timely site access to
each building for the design, installation, optimization and testing phases of any
BDA systems needed. Motorola is not responsible for any project schedule
delays resulting from the inability of the County to obtain site access when
required. Any additional project costs resulting from site access delays can be
quoted by Motorola through the change order process.
♦ Motorola assumes that adequate installation space and power will be available in
the areas of each building where the BDAs will need to be installed. Any
building modifications or electric power circuit installations/extensions are the
responsibility of the County.
♦ Motorola assumes that there are not any special installation requirements in any
of the buildings. “Special requirements” refers to any conditions for installation
the building owner may require that are not required by local building codes.
Motorola can quote these installation services on an as-needed per building basis,
through the change order process.
♦ In the event that cable installations are required between floors in a building or
between buildings, Motorola assumes that cores, penetrations or conduits are
already in place and have adequate space available for any required cabling.
Should any of these be needed to effect installation of cabling, Motorola can
quote these services through the change order process.
♦ Motorola assumes that the building owners will be supplied with the
documentation developed for any BDA installations. Motorola is not responsible
for any damage to the BDAs, external antennas or distributed antenna systems
caused by any future building modifications or installations.
♦ Motorola assumes that the BDA systems will be tested by the County on a regular
basis. Motorola is not responsible for in-building coverage in any building not
tested on a regular basis.

December 16, 2010

♦ Motorola assumes that ongoing site access arrangements will be made during the
service and warranty phase of the project, that valid contact information will be
provided to Motorola initially and that any changes to contact information or site
access procedures will be communicated to Motorola in a timely fashion.
Motorola is not responsible for any delays in incident response time or equipment
repair resulting from the inability of Motorola to gain site access as needed.
Subscriber Programming
Motorola will program the quantities of subscriber units as agreed upon in the
Contract. Subscribers will be programmed one-time only based upon programming
templates that have been approved by Floyd County prior to beginning any
programming tasks. Programming of all subscribers will be defined as loading a
County-provided radio codeplug (personality file) into each device. The codeplug
files will be owned and maintained by the County. Motorola’s System Engineer will
assist the County with initial codeplug development during the fleetmapping process.
Additional re-programming of the subscribers will be handled through the Change
Order process due to the significant amount of labor required to re-program the units.
To identify errors in the templates, Motorola’s System Engineer will program test
radios and activate them on the system. The County’s Project Manager shall be
responsible for testing and verifying each feature selected as well as providing
acceptance sign-off of the final templates for all subscriber units. Sign-off of the
final template must be received within 10 business days of submission to the
County’s Project Manager for approval.
Once the determined quantities of subscribers have been programmed by Motorola,
the radios will be delivered to Floyd County for distribution to its users. Upon
delivery, Motorola will obtain an authorized signature acknowledging receipt of all
subscribers and accessories and proper operation of a sampling of subscribers.
Motorola will document all inventory adjustments as these units are distributed and
verify the information with the County’s Project Manager.
Mobile Radio and Mobile Repeater Installation

Motorola will program all mobile radio and repeater units agreed upon in the
Contract based on the pre-approved templates and test each mobile unit for proper
performance. Power, frequency, and deviation within specification will be verified. If
it is determined that any mobile unit creates or receives interference from other
electronic equipment in the vehicle, Motorola will coordinate with the County for a
satisfactory resolution.
Motorola will coordinate the installation of mobiles into the identified vehicles with
the County’s Project Manager. It is the intention of Motorola to minimize the impact
upon and the involvement of the individual vehicle operators in the selection and
approval of each installation. The mounting locations of like-type vehicles will be

December 16, 2010

prototyped and approved by the County’s Project Manager before performing
installations en masse. Motorola will work with the County to develop and approve
prototypes of each type of mobile installation.
These prototype installations will be designed to avoid interference with any
functional devices, or adversely affect the safe operation of the vehicles. Motorola
will develop an installation diagram depicting the equipment placement and cable
routing and for each approved vehicle prototype. This diagram will be provided to
each of the authorized installation subcontractors to be used as the basis of all
installations. Dependent upon vehicle configurations, certain installations will require
variations from the approved plan. For those vehicle types, Motorola will obtain
approval by the County’s Project Manager before proceeding with the installation.
This will limit confusion and control the requests of unauthorized individuals.
All mobile radio installations will take place during normal workings hours, 8:00 a.m.
to 5:00 p.m., Monday through Friday, excluding holidays. The mobile radio and
repeater installations will be performed at a mutually agreeable location and time.
Scheduling and management of this operation will be performed under the guidance
of Motorola’s Project Manager. All mobile radio and repeater installation pricing is
based on a ‘standard installation.’ This proposal pricing does not include the
following:
♦ Customized installation(s).
♦ Separate visit for the removal or relocation of existing equipment in the vehicles
after the installation of new mobile unit.
♦ Any installation of vehicular accessories (i.e. light bars, shotgun release, PA
speakers, disguise consoles, etc.).
♦ Relocation of existing equipment (mobiles, sirens, flashlights, scanners, etc.).
♦ Any mounting hardware other than the hardware that is provided as a part of the
standard Motorola mounting kit.
Upon delivery of the mobile subscriber equipment, Motorola will obtain authorized
signature acknowledging receipt of all mobiles and accessories.
Specialized use vehicles such as command vehicles, fire/rescue trucks, SWAT vans
and the like may require design and fabrication of special mounting brackets and/or
cables to insure an ergonomically correct installation. The design, fabrication and
installation costs for the specialized brackets, power, antenna, or control cables
cannot be defined by Motorola at time of proposal submittal, therefore the costs for
these will be identified by Motorola and agreed upon by the County prior to
installation. The installation supervisor will inspect each specialized vehicle to
determine if any customized hardware will be necessary to complete the installation.
A list of custom hardware with estimated pricing will be submitted to the Customer
for approval before installation commences. Installation will commence only when

December 16, 2010

the County has approved any additional costs and all custom hardware becomes
available to the installation supervisor.
Power converters and/or battery splitters are assumed not to be in use. Motorola’s
installation quotation assumes constant power will be supplied at all times to the
radio to maintain user programming. Mobile equipment is quoted with a standard 12-
volt negative-ground vehicle battery system.
The County will perform the following tasks for mobile radio installations:
♦ Provide the required amount of vehicles at the start of each business day.
♦ If a vehicle cannot be released to Motorola’s installation facility, then the County
will provide a mutually agreeable location suitable for mobile installations that
has adequate working space with HVAC, lights, electric, and shelter from the
outside elements.
♦ Designate a single point of contact within the County’s project organization that
will be responsible for scheduling vehicles as required for installation.
♦ Have a representative on site during the installations to approve and accept the
installations daily.
♦ Inspect each vehicle prior to delivery to the installation facility to ensure that the
vehicle is free from trash, weapons, and contraband.
♦ Arrange for all equipment removed from the vehicles to be picked up from the
installation facility on a weekly basis.
♦ Inventory all equipment prior to removal from the installation facility; any
discrepancies shall be resolved at that time.
The County’s Project Manager will need to arrange a continuous flow of vehicles to
support the installation schedule in order to avoid any scheduling delays. It will be
the responsibility of the County or the user groups to assign a staff member to act as
the distribution coordinator of user staff and radios. As users arrive at the facility to
pick up a new mobile subscriber, the County’s staff member will review the
subscriber database and issue the correct mobile to that individual. Distribution of
mobiles not assigned at the time the programming center closes at a given location
becomes the responsibility of the user group. If the County is unable to provide the
vehicles according to the agreed upon schedule, the Motorola and the County Project
Managers will identify any additional cost or impact to the project schedule.
Fire Station Alerting (FSA) Installation

Motorola will install Fire Station Alerting Radios at 19 Fire and EMS locations. As
part of this installation, Motorola will install an antenna and RF cabling. The cabling
will be properly connectorized, grounded and will be run via the least obtrusive way
to the outdoor antenna location. Motorola assumes that the routing of this coax cable
will not require the coring of any concrete or brick wall and will not require the

December 16, 2010

penetration of any exterior roof where the installation of any weather head will be
required. A bulkhead lightning surge protector will protect the cabling. Cable entry
into the building will be through County-provided wall feed-through and sealed with
silicone. Motorola has included a basic installation plan for each Fire and EMS
location consisting of the following tasks. During the Contract Design Review,
specific inputs and outputs as well as unique installation and antenna mounting
requirements can be addressed and any deviations from the basic installation will be
handled via the Change Order process as required.
Motorola will perform the following tasks:

♦ Create the installation plan.
♦ Install the following at each Fire location (11 locations):
• Install one CDM1250 control station. Each station will have up to 100’ of
½” transmission line with a directional antenna.
• Provide and install one audio Public Address amplifier (PA).
• Connect to the County-supplied ground point within six cable feet of unit.
• Terminate the following outputs:
Two-wire analog audio output from PA to County-provided speaker
system.
Two-wire digital output to County-provided light and/or audible
alarms relay.
♦ Install the following at each EMS location (eight locations):
• Install one XTL2500 control station. Each station will have up to 100’ of
½” transmission line with a directional antenna.
• Provide and install one audio Public Address amplifier (PA).
• Connect to the County-supplied ground point within six cable feet of unit.
• Terminate the following outputs:
Two-wire analog audio output from PA to EMS-provided speaker
system.
Two-wire digital output to County-provided light and/or audible
alarms relay.
The County shall provide the following:
♦ Provide space as necessary for installation of the FSA equipment described
above.
♦ Supply space for installation of the Motorola control station antenna with no more
than a 100-foot cable run.
♦ Provide working speakers at each Fire and EMS location.

December 16, 2010

Assumptions:
♦ At each FSA installation location, there is a dedicated 115 VAC grounded
electrical outlet rated at 15 AMPS to power the FSA equipment with an outlet
provided within six feet of the units.
♦ Each FSA installation location has a ground point of 10 ohms or less located in
the immediate vicinity (six feet) of the finalized location of the antenna for the
control station.
♦ Each FSA installation location has adequate space and facilities for mounting the
control station antenna including means of feed-line routing and support within
150 feet of the control station.
Existing Equipment
Motorola will re-use the following existing County equipment:
♦ Leased telephone lines at the Jail which access the State-band radio.
Motorola will re-use and relocate the following existing County equipment:
♦ Fire Paging and Police Department MTR2000 repeaters from the existing Mount
Alto site to the new ASTRO25 Mount Alto site.
♦ On-site VHF / UHF control stations used by the current County console system
from their existing location to a new cabinet.
Motorola will remove the following existing County equipment to a County-owned

location as agreed upon during the Contract Design Review and as identified and
directed by the County’s representative:
♦ Existing Floyd County 911 radio console positions and back-room equipment.
♦ (10) VHF / UHF antenna systems and (8) radios from Mount Alto.
♦ Repeater, (5) control stations, and (24) desksets from the Jail.
♦ Control station and (4) desksets from the Sheriff’s Office / Courthouse.
♦ Control stations from the Prison.
♦ Un-used control stations from the existing console system.
Interfaces
Motorola has included the Application Programming Interface (API) for the new
proposed ASTRO25 system which provides Floyd County’s selected CAD vendor the
ability to program its interface to communicate with the Radio System. Additional
CAD interfaces are also available to control the MCC7500 console or Fire Station
Alerting system.
Motorola has also included an email notification interface. The County must provide
email account and LAN access to the County’s email server at the Floyd County
E911 Center.

December 16, 2010

Motorola will provide, install, and program two ISSI.1 Gateways which will be the
interface to the Floyd P25 system. Motorola is the only vendor who can provide a
turnkey ISSI solution between the proposed Floyd County ASTRO25 system and the
Tennessee Valley Regional ASTRO25 system, by providing one gateway for the
proposed Floyd system and one gateway for the ASTRO25 Tennessee Valley system.
As an option, Motorola is also proposing connecting and configuring the proposed
Floyd ASTRO25 system as an additional zone on the Tennessee Valley ASTRO25
system. This option preserves features inherent to the ASTRO25 system and
provides additional features above the capabilities of ISSI. Please refer to the system
description for further details.
Motorola has not quoted interfaces to any other existing equipment as part of this
proposal. Motorola will work with Floyd County’s contractors in providing them the
support necessary to interface their equipment to Motorola’s new equipment.
Optional: Site-on-Wheels Installation

Motorola is proposing a deployable Pepro trailer configured to operate as an RF
repeater site. The system will be voice-only and does not include options for
Integrated Voice and Data (IV&D), console connectivity, or a customer network
interface (CNI) although the ASTRO Express site is capable of supporting these
options. The proposed deployable trailer will be used to improve local RF coverage
when deployed.
As the proposed system is a deployable system, no specific coverage guarantee can
be made regarding the performance of the system. Motorola will demonstrate to the
County that the system is able to provide the required functionality via limited PTT
key-up testing, however no specific coverage performance can be guaranteed.
The following equipment will be mounted in the equipment racks:
♦ ESS cabinet with (3) GTR8000 800MHz base stations
♦ ESS cabinet with (3) GTR8000 700MHz base stations
♦ Site controllers to provide redundancy
♦ (2) 6-port transmit combiners
♦ 700/800MHz omni-directional antennas for transmit and receive will be mounted
on the 60-foot antenna mast.
The County will be responsible for providing an adequate tow vehicle for the Pepro
trailer. Motorola estimates that a GVWR (tow rating) of 18,400 pounds will be
necessary.
The Pepro trailer included in this proposal was designed to specifically hold the
system equipment as described in this Statement of Work. If the County adds any
additional equipment, the overall weight capacity of the trailer must be maintained so
as not to exceed limitations.

December 16, 2010

Motorola will deliver the finished Pepro trailer to a County-owned and identified
location as agreed upon during the CDR.
9.1.4 System Training

Floyd County’s total satisfaction is directly related to the technical and operational
efficiency of the new digital ASTRO25 radio and dispatch communications system.
These efficiencies are only realized when each discipline within the County is fully
trained to properly operate the system. Motorola’s Learning Services (MLS) group
will be responsible for the technical training for the County’s personnel. Motorola
will provide training programs that are specifically designed to meet the particular
needs of the County and its system. Courses will cover end user, dispatch operations,
and technical and system manager training.
Motorola will conduct training classes on-site in Floyd County unless a more
appropriate and mutually agreed upon location is determined. In order for training to
be most effective, Motorola will utilize the actual equipment supplied for the new
system for hands-on activities, whenever possible. This allows students to learn on
the actual programs and equipment they will use after training is completed.
Motorola recommends that there be one subscriber unit available per student present
in the Subscriber training sessions. In the case of console end-user training, Motorola
recommends that there be at least one console position for every two dispatch
operators being trained. Floyd County will be responsible for identifying and
scheduling personnel that will participate in the training classes described in the
training plan.
Please refer to Section 10.0 (Training) of this response for a full description of the
training courses Motorola has identified to meet the training goals of the County.
9.1.5 System Programming and Optimization

Upon completion of the installation process, the ASTRO25 system equipment will be
powered up and then optimized by Motorola’s System Technologist under the
direction of the Project Manager and System Engineer. Motorola and its
subcontractors will optimize each subsystem individually. Audio and data levels will
be checked to verify factory settings. Radio equipment will have forward and
reflected power checked after connection to the antenna systems to verify that they
meet the FCC requirements and are within tolerances. Communication interfaces
between devices will be verified for proper operation. Features and functionality will
be tested to ensure that they are functioning according to the manufacturer’s
specifications and based upon the final configuration established during system
staging. Optimization levels and settings will be documented and included with the
as-built documentation.

December 16, 2010

9.1.6 Functional Acceptance Testing
Upon completion of the fixed-end equipment optimization, Functional Acceptance
Testing of the fixed equipment will begin based upon the Acceptance Test Plan
(ATP) agreed upon during the Contract Design Review. Motorola has included
preliminary ATPs in this proposal response for the County’s review. The ATP
specifies the standards and tests to which Motorola and its authorized subcontractors
will adhere. Motorola will conduct a Functional Acceptance Test to verify the
operational functionality and features of both the individual subsystems and of the
system as a whole. In the event that any task fails in the initial test, that particular task
will be retested when Motorola determines that corrective action has been taken. All
issues that arise during the acceptance test are to be fully documented and resolved
before the subsystem is considered ready for integration into the system. Motorola
will document the results of this acceptance test and these results will be available for
review by Floyd County.
Acceptance tests of the individual components will be conducted as part of the
system installation and optimization, and as such, have not been scheduled separately.
County representatives are welcome to be present during the testing period to witness
each of the tests. These tests include individual equipment specifications such as
receiver sensitivity and RF transmitter power and will be performed as agreed upon.
Documentation of component tests will be made available for the County as part of
the final documentation package.
9.1.6.1 Interference
Motorola will work with Floyd County to identify any mutual radio interference
between the new ASTRO25 radio system and any other existing radio systems.
Motorola is not responsible for issues outside of its immediate control. Such issues
include, but are not restricted to, improper frequency coordination by others and non-
compliant operation of other radios.
Motorola is not responsible for co-channel interference due to errors in frequency
coordination by APCO or any other unlisted frequencies or the improper design,
installation, or operation of systems installed or operated by others. Motorola is not
responsible for the costs associated with site changes and/or delays; including, but not
limited to, re-engineering, frequency re-licensing, site zoning, site permitting,
schedule delays, site abnormalities, re-mobilization, etc. due to a site being unusable
for any frequency issues outside of Motorola’s control.

December 16, 2010

9.1.7 Coverage Acceptance Testing
The Coverage Acceptance Test Plan (CATP) will determine acceptance of system
coverage. The Coverage Acceptance Test will require the participation of Floyd
County personnel in the testing process. Please refer to Section 7.0 (CATP) and 8.0
(Coverage Description) of this response for details and a description of each of the
service areas to be tested.
Motorola will perform objective Signal Strength Indicator (SSI) and subjective
Delivered Audio Quality (DAQ) Coverage Testing for each of the required areas
identified by Floyd County in order to meet County’s coverage requirements.
The County shall provide the following for the duration of the coverage testing:
♦ Permissions and access for Motorola and County teams to enter all pre-
determined buildings for the purpose of performing coverage testing prior to
Motorola representatives being on-site according to the Project Schedule. This
includes any required identification or visitor badges.
♦ At least four County representatives (one per vehicle and one at dispatch) to be
witness in each test vehicle and to be the control point witness for each test team.
County personnel shall be available a minimum of eight hours each day.
♦ Suitably equipped and marked public safety escort vehicles, as required, by the
County.
Motorola will provide the following for the duration of the coverage test:
♦ At least three Motorola representatives (one per vehicle) to navigate and to
operate the Coverage Test Equipment.
♦ At least three full-sized (off-road capable) test vehicles with a driver.
♦ One Motorola representative to manage, administer and collect the coverage test
data on each day of coverage test.
♦ At least three calibrated Motorola Coverage Testing Packages (one per vehicle).
♦ At least three subscriber radios with antenna configurations as defined in the
CATP.
Motorola will conduct this test only once per configuration as outlined in the CATP.
If any portion of the test is determined to be unreliable because of proven equipment
malfunctions or failures, Motorola will repeat the portion of the test affected by the
equipment malfunction or failure. Floyd County will have the option to accept the
coverage at any time prior to completion of the coverage test.
Before starting the coverage test, Floyd County and Motorola will agree upon the
time frame for both Motorola’s submission of a report containing the coverage test
results and the County’s review and acceptance of the results.

December 16, 2010

9.1.7.1 System Acceptance
System Acceptance will occur upon the installation, optimization, and successful
completion of the Functional Acceptance Tests, which apply to the specific system,
or upon “Beneficial Use”, whichever occurs first. “Beneficial Use” means use of the
system or subsystem for operational purposes, other than for training or testing. If
Floyd County commences Beneficial Use of the system prior to system acceptance,
final acceptance for said system or subsystem will have occurred. The warranty
period shall commence upon the date of System Acceptance or Beneficial Use,
whichever occurs first.
9.1.7.2 Project Finalization

The Project Finalization Phase ensures that all criteria for Final Project Acceptance
have been met. Motorola will provide the County with a System Manual, software
licenses, and any equipment manuals supplied with purchased equipment.
This phase is considered complete when Motorola and the County sign the Final
Project Acceptance portion of the System Acceptance Certificate.
Motorola will perform a System and Project Readiness Review to obtain concurrence
from all Motorola functional groups and the County as follows:
♦ All actions relating to system components, installation, testing, and training, have
been addressed and successfully completed.
♦ The system is ready for Cutover.
♦ The project is evaluated and assessed to identify any issues that may affect the
satisfaction of the end-users of the system.
9.1.7.2.1 System Cutover
A detailed cutover plan will be developed with the assistance of the County’s Project
Manager and designated County agency representatives to ensure that an effective
and efficient transition occurs from the existing radio system to the new digital P25
radio and dispatch communications system. The cutover plan will detail which
departments move to the new system and in which order they migrate. Motorola has
developed a preliminary System Cutover / Migration Plan included in Section 9.3 of
this response.
It is critical that the County understands that all users on the current County system
must be prepared to move to the new digital radio system during the scheduled
cutover period and have subscriber radios capable and programmed to operate on the
new system.
After the successful completion of the cutover, the County will begin to use the
system for its day-to-day operation. At this point, Motorola will transition the
operations of the County’s new system to our Life Cycle Services Organization for
providing ongoing system management, maintenance, and support.

December 16, 2010

9.1.7.2.2 As-Built Documentation
Motorola will provide as-built site manuals, system manuals, and maintenance
manuals for each of the remote sites as well as the Prime and Master sites to the
County within 45 days after system testing has been successfully concluded. The
documentation provided will be appropriate to the scope and complexity of the
County’s system. Manuals in CD or other electronic format will be provided
whenever possible.
The documentation will consist of:

♦ Standard equipment manuals; the content of these manuals is standardized and
may not be specific to the County’s system.
♦ Inventory of all equipment and software including spares
♦ Manufacturer’s warranty for all equipment and software
♦ Licenses and permits for all software
♦ Manuals / specifications sheet for all software
♦ Software installation and configuration parameters
♦ Equipment installation and configuration including unique wiring and circuit
modifications not part of the standard equipment documentation.
♦ Acceptance Test Plan and test results
♦ Operators’ manuals
♦ Operation and Maintenance manuals
♦ As-built System drawings in both hard and soft copy
♦ As-built and design drawings for new towers and equipment shelters
♦ Training materials
9.1.7.2.3 Punch-Lists
During acceptance testing, a punch-list will be generated noting any corrections that
may be required to be made prior to Final Project Acceptance. A resolution to each
punch-list item will be mutually agreed to and a time frame for satisfactory
completion will be listed. When punch-list items have been resolved and the final
documentation delivered, the County and Motorola will execute Final Project
Acceptance.
9.1.7.2.4 Final Project Acceptance

After successful completion of system testing and acceptance of the system, Motorola
will conduct meetings to verify with the County that all contract deliverables have
been satisfied and review the Managed Services Support Plan. These meetings will
allow the County an opportunity to discuss any final issues or address any questions
associated with the closeout of the System Implementation Phase. Reviewing the
Managed Services Plan will provide the opportunity for the County to review the
level of support being supplied, the procedures that need to be followed, and who to
call when questions or concerns arise.

December 16, 2010

The County will grant Final Project Acceptance to Motorola all contractual
commitments of Motorola have been completed.
9.1.8 Summary
Motorola will apply its exceptional qualifications, proven processes, and experienced
team to ensure Floyd County a successful system implementation. Motorola is
excited to have the opportunity to serve the needs of the County. Using proven
techniques and processes conducted by highly skilled professionals, Motorola will
prove our continued commitment to Floyd County.
9.1.9 Change Order Plan

Either Party may request changes within the general scope of this Agreement. If a
requested change causes an increase or decrease in the cost or time required to
perform this Agreement, the Parties will agree to an equitable adjustment of the
Contract Price, Performance Schedule, or both, and will reflect the adjustment in a
change order. Neither Party is obligated to perform requested changes unless both
Parties execute a written change order.
9.1.10 Preliminary Project Schedule

Motorola has provided a preliminary project schedule in Section 9.6 (Project
Schedule) that reflects our ability to complete the County’s Project within seventeen
months.

December 16, 2010

9.2 Site Development Statement of Work
9.2.1 Civil Work
9.2.1.1 Site Development at Mount Alto Site

Mt Alto is a raw land site that will be developed across the driveway from Floyd
County's existing radio site. This site will receive a new equipment shelter and tower
in accordance with Floyd County RFP #101216.
Site Scope Summary

♦ Engineering services for site drawings and regulatory approvals – Included.
♦ Site acquisition services – Not included.
♦ Zoning Services – Not included.
♦ New fenced compound/expansion size – 50-foot x 50-foot.
♦ Clearing type – Heavy.
♦ New power run – 50 feet, Electrical service type – Underground, 200-amp -
120/240-volt, single-phase.
♦ New shelter size – 12-foot x 20-foot.
♦ New fuel tank size – 1200 gallons- , Type – Propane above-ground.
♦ New generator size – 50 kW, Type – Outdoor.
♦ New tower to be used for antennas – 180-foot self-supported tower.
♦ New tower foundation size – 48 cubic yard, Type – Drilled Pier.
Motorola Will:
Site Engineering
♦ Prepare site construction drawings showing the layout of various new and
existing site components.
♦ Conduct site walks to collect pertinent information from the sites (e.g., location of
Telco, power, existing facilities, etc.).
♦ Perform a boundary and topographic survey for the property on which the
communication site is located or will be located.
♦ Prepare a lease exhibit sketch of the site to communicate to the property owner
the proposed lease space and planned development at the particular site location.
♦ Prepare record drawings of the site showing the as-built information.
♦ Perform construction staking around the site to establish reference points for
proposed construction.
♦ Perform NEPA Threshold Screening, including limited literature and records
search and brief reporting, as necessary to identify sensitive natural and cultural
features referenced in 47 CFR Chapter 1, subsection 1.1307 that may potentially
December 16, 2010
Site Development Statement of Work 9.2-1

be impacted by the proposed construction activity. This does not include the
additional field investigations to document site conditions if it is determined that
the proposed communication facility “may have a significant environmental
impact” and thus require additional documentation, submittals, or work. Regional
Environmental Review (RER) report submittals if required by FEMA have not
been included.
♦ Perform a cultural resource study, as needed to identify sensitive historical and
archaeological monuments that might be impacted by proposed construction.
♦ Conduct up to 40-foot deep soil boring test at tower location and prepare
geotechnical report of soil conditions at locations of the tower foundation.
Grouting of boring holes or access by Automatic Traction Vehicle (ATV) -
mounted rig is not included.
♦ Conduct construction inspection of foundation steel prior to pour to ensure quality
construction.
♦ Check tower erection for plumbness, linearity and alignment after installation.
♦ Perform inspection of the site and the work performed by the Contractor to
document that the site is built in accordance with the “Site Plans” and document
any deviations or violations.
♦ Research permit requirements (building, utility, construction and FAA permits)
for the construction of the proposed site, and determine if the permits are
required. If a permit is required, Motorola shall obtain the necessary permit forms
and complete the necessary information on behalf of the Customer.
♦ Submit the completed application forms to the local jurisdiction and apply for
applicable permits.
Site Preparation
♦ Obtain the permits such as electrical, building, and construction permits, and any
inspections that may need to be coordinated with the local authorities to complete
site development work.
♦ Provide one-time mobilization costs for the construction crews. Any
remobilization due to interruptions/delays that are out of Motorola's control will
result in additional costs.
♦ Perform tree clearing, grubbing and disposal of vegetation in the site compound
area and a 20-foot path around it (not to exceed 8100 square feet).
♦ Grade the site compound and 10-foot path around it to provide a level, solid,
undisturbed surface for installation of site components (not to exceed 4900 square
feet).
♦ Provide earth fill to raise surface level in the site compound (not to exceed 200
cubic yards).
♦ Supply and install gravel surfacing to a depth of 6 inches, underlain with
geotextile fabric within the fenced in site compound area, and a 3-foot path
around it (not to exceed 3136 square feet).
♦ Provide silt fence around the compound to control soil erosion (not to exceed 200
linear feet).
December 16, 2010
9.2-2 Site Development Statement of Work

♦ Supply and install 8-foot high chain-link fencing with a ten-foot wide gate around
the shelter compound (not to exceed 200 linear feet).
♦ Perform site touchup (fertilize, seed and straw) disturbed areas not covered with
gravel after completion of construction work. Landscaping, decorative fencing or
any other aesthetic improvement that may be required by local jurisdictions has
not been included and will be handled through a negotiated contract change
notice.
Site Components Installation

♦ Construct 1 reinforced concrete foundation necessary for a 12-foot x 20-foot
shelter.
♦ Construct 1 concrete slab for a 1200 gallon above-ground Liquid Propane (LP)
fuel tank at 3000 psi with reinforcing steel necessary for foundations.
♦ Construct 1 foundation for the 50 kW generator with reinforcing steel necessary
for foundations.
♦ Supply and install 1 prefabricated concrete shelter 12-foot x 20-foot.
♦ Supply and install 1ea 1200-gallon Liquid Propane (LP) fuel tank(s), fill it with
fuel and connect it to the generator.
♦ Supply and install fuel tank monitors on the tanks to monitor low fuel in tanks
and run alarm wiring to the building located within 50 feet of the tank.
♦ Supply and install 1 standby power generator (50 kW) located within 20 feet of
the ATS, including interconnection wiring between the generator, transfer switch,
and site electrical service mains.
♦ Supply and install 1 120/240-volt, 200-amp, single-phase meter pedestal and
hookup for electrical service by the local utility.
♦ Provide all trenching, conduit, and cabling necessary for underground hookup of
power to the shelter from nearby utility termination located within 50 cable feet
of the shelter.
♦ Supply and install a grounding system around the shelter tied to the fence and
other new metal structures within the compound to meet Motorola’s R56
standards.
♦ Conduct 1 three-point ground resistance test of the site. Should any improvements
to grounding system be necessary after ground testing, the cost of such
improvements shall be the responsibility of Floyd County, GA.
♦ Supply and install 1 freestanding 24-inch-wide cable/ice bridge from the tower to
the shelter (up to 15 linear feet).
♦ Pressure testing of FM-200 system in the field.
Tower Work
♦ Construct drilled pier type tower foundations including excavation, rebar and
concrete (not to exceed 48 cubic yards).
♦ Erect new 180-foot self-supported tower.

December 16, 2010

Antenna and Transmission Line Installation
♦ Install 4 antenna(s) for the RF system.
♦ Install 1 tower top amplifier(s).
♦ Install up to 210 linear feet of 1/2-inch transmission line.
♦ Install up to 630 linear feet of 1-1/4-inch transmission line.
♦ Perform sweep tests on transmission lines.
♦ Supply and install 1 ground buss bar at the bottom of the antenna support
structure for grounding RF cables before they make horizontal transition.
♦ Remove decommissioned antennas and lines
Miscellaneous Work
♦ Application of regionally specific soil sterilant
♦ Provide, install and connectorize alarm contacts for compound gates per
specifications
♦ Dewatering process as required
♦ Disposal of spoils
Completion Criteria
♦ Site development completed and approved by Floyd County, GA
9.2.2 Site Development at Leonard Road Site

The Leonard site will be developed on the back side of the Floyd County Water
System tank facility. This site will receive a new equipment shelter and tower in
accordance with Floyd County RFP #101216.
Site Scope Summary

♦ Clearing type – Light.
♦ New shelter size – 12-foot x 20-foot .
♦ New tower to be used for antennas – 400-foot guyed tower-field assembled.
♦ New tower foundation size – 62 cubic yard, Type – Base + 6 anchors.

December 16, 2010

Motorola Will:
Site Engineering
been included.
geotechnical report of soil conditions at locations of guyed tower base and each
guy anchor point. Grouting of boring holes or access by Automatic Traction
Vehicle (ATV) - mounted rig is not included.
construction.
applicable permits.

December 16, 2010

Site Preparation
♦ Perform clear light brush, grub roots and dispose vegetation and shrub growth in
the site compound area and a 20-foot path around it (not to exceed 8100 square
feet).
feet).
cubic yards).
♦ Provide minimal grading in a 15-foot x 30-foot compound around each of 6 guy
anchors to allow anchor installation.
♦ Supply and install gravel surfacing to a depth of 6 inches around each of 6 guy
anchors underlain with geotextile fabric.
linear feet).
♦ Supply and install 8-foot high chain-link fencing with a four-foot wide gate
around a 15-foot x 30-foot compound for each of 6 guy anchors.
notice.

shelter.
for foundations.
♦ Supply and install 1 prefabricated concrete shelter 12-foot x 20-foot .
December 16, 2010

of the shelter.
♦ Supply and install a grounding system around the shelter and tower tied to the
fence and other new metal structures within the compound to meet Motorola’s
R56 standards.
Tower Work
♦ Construct tower foundations for a guyed tower (base and six anchors) including
excavation, rebar and concrete (not to exceed 62 cubic yards).Rock coring and
hazardous material removal have not been included and will be considered extra.
♦ Erect new 400-foot guyed tower with strobe lighting.
♦ Ground each of the 6 guy anchors using galvanized steel ground rods.

Miscellaneous Work
specifications

December 16, 2010

9.2.3 Site Development at Fouche Gap Site
The Fouche Gap site on Lavender Mountain is a raw land site to be developed near
the west end of Lavender Trail. This site will receive a new equipment shelter and
tower in accordance with Floyd County RFP #101216. Access to this site is via a
steep, narrow road with an abundance of sharp curves which may necessitate special
equipment.
Site Scope Summary

♦ Clearing type – Heavy.
♦ New tower to be used for antennas – 180-foot self-supported tower.
♦ New tower foundation size – 45 cubic yard, Type – Drilled Pier.
Motorola Will:
Site Engineering

December 16, 2010

been included.
geotechnical report of soil conditions at locations of the tower foundation.
Grouting of boring holes or access by Automatic Traction Vehicle (ATV) -
mounted rig is not included.
construction.
applicable permits.
Site Preparation
♦ Perform tree clearing, grubbing and disposal of vegetation in the site compound
area and a 20-foot path around it (not to exceed 8100 square feet).
feet).
cubic yards).
linear feet).

December 16, 2010

notice.

shelter.
for foundations.
of the shelter.
♦ Supply and install a grounding system around the shelter tied to the fence and
other new metal structures within the compound to meet Motorola’s R56
standards.
Tower Work
♦ Construct drilled pier type tower foundations including excavation, rebar and
concrete (not to exceed 45 cubic yards).
♦ Erect new 180-foot self-supported tower.


December 16, 2010

Miscellaneous Work
specifications
9.2.4 Site Development at Cave Spring Site

The Cave Spring site currently has a small guyed tower that will require
disassembling and a small CMU shelter that will require demolition in order for the
site development and integration to commence. This site will receive a new
equipment shelter and tower in accordance with Floyd County RFP #101216.
Site Scope Summary

Motorola Will:
Site Engineering

December 16, 2010

been included.
construction.
applicable permits.
Site Preparation
December 16, 2010

feet).
feet).
cubic yards).
linear feet).
notice.

shelter.
for foundations.

December 16, 2010

of the shelter.
R56 standards.
Tower Work
♦ Construct tower foundations for a guyed tower (base and three anchors) including
♦ Dismantle and remove the existing 160 ft. guyed tower structure.

Miscellaneous Work
♦ Cut, load and haul existing CMU shelter to a certified disposal facility.
specifications

December 16, 2010

9.2.5 Site Development at Hillindale Site
The Hillindale site will be developed on the front side of the Floyd County Water
System tank facility. This site will receive a new equipment shelter and tower in
accordance with Floyd County RFP #101216. Access to this site is via a steep road
which may necessitate special equipment.
Site Scope Summary

Motorola Will:
Site Engineering
been included.

December 16, 2010

construction.
applicable permits.
Site Preparation
feet).
feet).
cubic yards).
linear feet).

December 16, 2010

notice.

shelter.
for foundations.
♦ Supply and install 1 prefabricated concrete shelter 12-foot x 20-foot .
of the shelter.
R56 standards.

December 16, 2010

Tower Work

Miscellaneous Work
specifications
The following Customer Responsibilities and Assumptions Apply to: the

Mt Alto, Fouche Gap, Leonard Rd, Cave Spring, Hillindale.
Customer Will:
♦ If required, prepare and submit EME plans for the site (as a licensee) to
demonstrate compliance with FCC RF Exposure guidelines.
♦ Assist Motorola with permitting for sites as owner/lessee.
♦ As applicable, coordinate, prepare, submit, and pay for all required permits and
inspections for the work that is the Customer’s responsibility.
♦ Pay for all utility connection, pole or line extensions, and any easement or usage
fees.
♦ Review and approve site design drawings within 7 calendar days of submission
by Motorola or its subcontractor(s). Should a re-submission be required, the
Customer shall review and approve the re-submitted plans within 7 calendar days
from the date of submittal.
♦ Pay for the usage costs of power, leased lines and generator fueling both during
the construction/installation effort and on an ongoing basis.

December 16, 2010

♦ Pay for application fees, taxes and recurring payments for lease/ownership of the
property.
♦ Provide personnel to observe construction progress and testing of site equipment
according to the schedule provided by Motorola.
♦ Secure clear and unencumbered title, MOU, or Lease Agreement with the
property owner.
♦ Provide approved, standardized lease language and negotiation guidelines to
assist Motorola in site acquisition.
♦ Provide property deed or lease agreement, and boundary survey, along with
existing as-built drawings of the site and site components to Motorola for
conducting site engineering.
♦ Provide a right of entry letter from the site owner for Motorola to conduct field
investigations.
♦ Provide clear and stable access road to the site for heavy-duty construction
vehicles, cement trucks and cranes. Sufficient space must be available at the site
for these vehicles to maneuver under their own power, without assistance from
other equipment.
♦ Conduct all the testing and documentation (balloon tests, photo simulations,
zoning application, expert testimony, zoning drawings etc.) required for the
zoning the proposed new tower sites.
♦ Secure power connection to the site, associated permitting and installation of a
meter and disconnect within 50 feet of the proposed shelter location.
♦ Provide additional temporary space for the staging the construction equipment
during the construction of new site facilities (tower, shelter, generator, fuel tank
etc.).
Assumptions:
♦ No prevailing wage, certified payroll, mandatory union workers or mandatory
minority workers are required for this work
♦ All work is assumed to be done during normal business hours as dictated by time
zone (Monday thru Friday, 7:30 a.m. to 5:00 p.m.).
♦ Temporary site trailers (tower, housing, COWS, and generator) have not been
included for cutovers. Cutover logistics will be determined on a case-by-case
basis; any additional costs will be negotiated prior to the execution of cutover
tasks.
♦ All recurring and non-recurring utility costs [including, but not limited to,
generator fuel (except first fill), electrical, Telco] will be borne by the Customer
or site owner.
♦ All utility installations shall be coordinated and paid for by the site owner and
located at jointly agreed to location within or around the new communications
shelter or equipment room.
♦ Site has adequate electrical service for the new shelter and tower. Utility
transformer, transformer upgrades, line, or pole extensions have not been
included.

December 16, 2010

♦ Pricing has been based on National codes such IBC or BOCA. Local codes or
jurisdictional requirements have not been considered in this proposal.
♦ Site is being constructed at a location where hazardous materials are not present.
Testing and removal of hazardous materials encountered during site
investigations or construction will be the responsibility of the Customer.
♦ A maximum of 30 days will be required for obtaining approved building permits
from time of submission, and a maximum of 60 days will be required for zoning
approvals from time of submittal.
♦ No improvements are required for concrete trucks, drill rigs, shelter delivery, and
crane access.
♦ If extremely harsh or difficult weather conditions delay the site work for more
than a week, Motorola will seek excusable delays rather than risk job site safety.
♦ In absence of geotechnical reports, foundations and subsurface conditions for
tower design are based on Presumptive Clay soil parameters, as defined by EIA-
222-G. Also, rock coring, piling, permanent casings or hazardous material
removal has not been included.
♦ For zoning approvals, a maximum of 60 days will be required from time of
submittal with attendance at maximum of two (2) required planning meetings.
♦ The new tower location will pass the FAA hazard study, zoning, FCC and
environmental permitting.
♦ The restoration of the site surroundings by fertilizing, seeding and strawing the
disturbed areas will be adequate. Additional landscaping or aesthetic
improvements (decorative fencing, tree plantings, stealth towers etc.) will not be
required.
♦ Tower and foundation sizing is based on the tower loading requirements as a
result of the RF Antenna System design and the Microwave Antenna System
design (i.e. - dish sizes and locations obtained from paper path studies). If after
physical path studies, the dish sizes and locations change, then Motorola will then
review the impact to tower structure and foundations and revise applicable costs.
♦ If as a result of NEPA studies, any jurisdictional authority should determine that a
proposed communications facility "may have a significant environmental
impact", the environmental impact studies or field testing and evaluation related
to such determination have not been included.
♦ For new towers greater than 200 feet in overall height, medium intensity strobe
lighting has been included. Painting or dual lighting of any new towers has not
been included.
♦ The site location can be finalized and lease agreement can be reached with the
property owner within 60 calendar days after the start of the site acquisition
effort.
♦ A waiver to zoning requirements like setbacks, tower height limitations, etc. can
be obtained.
♦ The soil resistivity at the site is sufficient to achieve resistance of ten (10) ohms
or less. Communications site grounding will be designed and installed per
Motorola's Standards and Guidelines for Communications Sites (R56).

December 16, 2010

♦ Underground utilities are not present in the construction area, and as such no
relocation will be required.
♦ Foundations for the shelter, generator and fuel tank are based "normal soil"
conditions as defined by TIA/EIA 222-F. Footings deeper than 30 inches, raised
piers, rock coring, dewatering, or hazardous material removal have not been
included.
♦ In the case of the Mt Alto site, It is assumed that the existing Mt Alto tower is
structurally safe for climbing and poses no safety hazard as it relates to the
removal of the antennas and lines to be decommissioned in accordance with the
RFP.
Completion Criteria
9.2.6 Site Development at Shannon Site

The Shannon site is the location of a pre-existing ATT shelter and tower. The shelter
will be used to house the new equipment and generator. A 12 X 20 equipment room
will be built in the left rear corner of the shelter. Electric, grounding and HVAC
upgrades will be a part of the integration at this location.
Site Scope Summary

♦ New generator size – 50 kW, Type – Indoor.
Motorola Will:
Site Engineering

December 16, 2010

been included.
♦ Conduct construction inspection of foundation steel prior to pour, materials
testing of concrete and field density tests of backfill to ensure quality
construction.
applicable permits.
Site Preparation
feet).
December 16, 2010

feet).
linear feet).
notice.

of the shelter.
R56 standards.
Tower Work
excavation, rebar and concrete (not to exceed 33 cubic yards).Rock coring,

December 16, 2010

extensive dewatering of foundations or hazardous material removal have not been
included and will be considered extra.
Note: Please see MACTEC tower structural report located at the end
of this document.

Existing Facility Improvement Work

♦ Construct a new room of drywall construction (not to exceed 240 square feet) for
installing the communications equipment.
♦ Supply and install 1 100-amp breaker panel with capacity for 20 circuits.
♦ Supply and install 10 20-amp breakers in the distribution panel and wire to outlets
located on an average within 35 cable feet.
♦ Install 1 Type 2 surge protector on electrical service side of the ATS.
♦ Install 1 primary Type 1 surge protector on the room electrical feed to protect the
equipment from surges.
♦ Install HVAC Compressor, Air Handler Thermostat and condensate drain system
in new equipment room
♦ Install 1 automatic transfer switch and connect it to generator and electric main.
♦ Supply and install 12-inch-wide cable runway (up to 40 linear feet) inside the
existing room.
♦ Supply and install 1 cable entry panel with 12 ports.
♦ Ground all metallic objects in the interior of the existing room, to meet
Motorola’s Standards and Guidelines for Communications Sites (R56)
requirements and terminate near equipment locations.
♦ Supply and install 2 copper ground buss bar(s).
♦ Supply and install 8 fluorescent lighting fixtures inside the existing room.
♦ Supply and install 1 telco board (48 inch x 96 inch).
♦ Supply and install 1 wall-mounted 10-pound CO2 fire extinguisher and 1 wall-
mounted 20-pound ABC fire extinguisher.
♦ Supply and install "No smoking" EME signage at the site.

December 16, 2010

♦ Supply and install 1 eye wash station and 1 first aid kit.
♦ Supply and install sensors for alarming (Fire, Smoke, Hi/Lo temp, door
intrusion), punch block and wiring of contact closures to alarm block
Miscellaneous Work
specifications
♦ General Repairs for Generator Room
♦ Wall boring for utility penetration
9.2.7 Site Development at Blossom Hill Site

The Blossom Hill site is the location of a pre-existing radio equipment room and
water tower. The room will be used to house the new equipment with a generator and
fuel tank to be installed at the base below the room. Electric, grounding and HVAC
upgrades will be a part of the integration at this location.
Site Scope Summary

♦ New power run – 100 feet, Electrical service type – Overhead, 200-amp -
♦ Existing tower to be used for antennas – 60 ' Water Tank.
Motorola Will:
Site Engineering
♦ Prepare site construction drawings, showing the layout of various new and
♦ Perform National Environmental Policy Act (NEPA) Threshold Screening,
including limited literature and records search and brief reporting, as necessary to
identify sensitive natural and cultural features referenced in 47 Code of Federal
Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted

December 16, 2010

by the proposed construction activity. This does not include the additional field
investigations to document site conditions if it is determined that the proposed
communication facility “may have a significant environmental impact” and thus
require additional documentation, submittals, or work.
♦ Provide a structural engineering analysis for antenna support structure, if
necessary, to support the proposed the proposed equipment loads.
♦ Design multi antenna support platform to support proposed antennas and dishes.
♦ Research permit requirements (building, utility, and construction permits) for the
construction of the proposed site, and determine if the permits are required. If a
permit is required, Motorola shall obtain the necessary permit forms and complete
the necessary information on behalf of the Customer.
applicable permits.
Site Preparation

♦ Construct concrete slab for 1200 gallon above-ground Liquid Propane (LP) fuel
tank at 3000 psi with reinforcing steel necessary for foundations.
for foundations.
♦ Supply and install one 1200-gallon Liquid Propane (LP) fuel tank(s), fill it with
♦ Overhead power hookup of power to the site from nearby utility termination
located within 100 cable feet.
♦ Coordinate 120/240-volt, 200-amp, single-phase overhead electrical service
including installation of weatherhead and connection to utility pole within 50 feet
of the shelter.
the equipment room.

December 16, 2010

♦ Capacitative stud welding to attach the antennas and lines to the water tank.

♦ Install 1 primary Type 1 surge protector on the room electrical feed to protect the
equipment from surges.
♦ Install 1 automatic transfer switch and connect it to generator and electric main.
existing room.
♦ Supply and install 1 cable entry panel with 12 ports.
♦ Supply and install 2 copper ground buss bar(s).
♦ Supply and install 8 fluorescent lighting fixtures inside the existing room.
♦ Supply and install 1 telco board (48 inch x 96 inch).
♦ Supply and install 1 wall-mounted 10-pound CO2 fire extinguisher and 1 wall-
mounted 20-pound ABC fire extinguisher.
♦ Supply and install "No smoking" EME signage at the site.
♦ Supply and install 1 eye wash station and 1 first aid kit.
♦ Supply and install sensors for alarming (Fire, Smoke, Hi/Lo temp, door
intrusion), punch block and wiring of contact closures to alarm block
Miscellaneous Work
♦ DC Connectivity
♦ Install HVAC Compressor, Air Handler Thermostat and condensate drain system
in new equipment room

December 16, 2010

♦ Fabricate and install antenna mounting grid and microwave mounts to be located
on water tank. If actual cost for fabrication and installation of grid exceeds quoted
estimate a change order will be submitted for approval before proceeding.
Mounting grid to be epoxied to surface.
♦ Additional labor and material to install transmission line and hangers on wall of
water tank from above equipment room to top of tank. Wall hangers to be epoxied
to tank.
♦ Rigging of water tank and provide man basket to hoist men and equipment on
tower.
Customer Will:
fees.
property.
property owner.
investigations.
other equipment.
♦ Conduct all the testing and documentation (balloon tests, photo simulations,
zoning application, expert testimony, zoning drawings etc.) required for the
zoning the proposed new tower sites.
December 16, 2010

meter and disconnect within 50 feet of the proposed shelter location.
♦ Provide additional temporary space for the staging the construction equipment
during the construction of new site facilities (tower, generator, fuel tank etc.).
♦ If required, remove or relocate any existing facilities, equipment, and utilities to
create space for new site facilities and equipment.
♦ Repair penetrations in existing corrugated metal roof of facility.
♦ Provide and/or secure doors in order to maintain a waterproof, secure, structurally
resilient shelter.
Assumptions:
tasks.
generator fuel (except first fill), electrical, Telco] will be borne by the Customer
or site owner.
♦ Site has adequate electrical service for the new tower. Utility transformer,
transformer upgrades, line, or pole extensions have not been included.
♦ Site is being constructed at a location where hazardous materials are not present.
Testing and removal of hazardous materials encountered during site
investigations or construction will be the responsibility of the Customer.
♦ No improvements are required for concrete trucks, drill rigs or crane access.
♦ In absence of geotechnical reports, foundations and subsurface conditions for
tower design are based on presumptive sand soil parameters, as defined by EIA-
222-G. Also, rock coring, piling, extensive dewatering of foundations, permanent
casings or hazardous material removal has not been included.
♦ For zoning approvals, a maximum of 60 days will be required from time of
submittal with attendance at maximum of two (2) required planning meetings.

December 16, 2010

♦ The new tower location will pass the FAA hazard study, zoning, FCC and
environmental permitting.
♦ The restoration of the site surroundings by fertilizing, seeding and strawing the
disturbed areas will be adequate. Additional landscaping or aesthetic
improvements (decorative fencing, tree plantings, stealth towers etc.) will not be
required.
♦ Tower and foundation sizing is based on the tower loading requirements as a
result of the RF Antenna System design and the Microwave Antenna System
design (i.e. - dish sizes and locations obtained from paper path studies). If after
physical path studies, the dish sizes and locations change, then Motorola will then
review the impact to tower structure and foundations and revise applicable costs.
♦ If as a result of NEPA studies, any jurisdictional authority should determine that a
proposed communications facility "may have a significant environmental
impact", the environmental impact studies or field testing and evaluation related
to such determination have not been included.
♦ For new towers greater than 200 feet in overall height, medium intensity strobe
lighting has been included. Painting or dual lighting of any new towers has not
been included.
♦ The site location can be finalized and lease agreement can be reached with the
property owner within 60 calendar days after the start of the site acquisition
effort.
♦ A waiver to zoning requirements like setbacks, tower height limitations, etc. can
be obtained.
♦ The soil resistivity at the site is sufficient to achieve resistance of ten (10) ohms
or less. Communications site grounding will be designed and installed per
Motorola's Standards and Guidelines for Communications Sites (R56).
♦ Underground utilities are not present in the construction area, and as such no
relocation will be required.
♦ Foundations for the shelter, generator and fuel tank are based "normal soil"
conditions as defined by TIA/EIA 222-F. Footings deeper than 30 inches, raised
piers, rock coring, dewatering, or hazardous material removal have not been
included.
♦ Alarming at existing sites will be limited to new component installations and will
have to be discussed and agreed to on a site-by-site basis.
♦ The existing utility service and backup power facilities (UPS, generators) have
sufficient extra capacity to support the proposed new equipment load.
♦ A clear obstruction-free access exists from the antenna location to the equipment
room.
♦ The floor can support the proposed new loading. Physical or structural
improvements to the existing room will not be required.
Completion Criteria

December 16, 2010

9.2.8 Site Development at Rocky Mountain Site
Rocky Mountain is an existing shelter and tower site on the Oglethorpe Power
property near the Chattooga/Floyd County lines. The existing backup power system
(generator) will be utilized for the new equipment.
Site Scope Summary

♦ Existing tower to be used for antennas – 151 ' self supported Tower.
Motorola Will:
Site Engineering
♦ Prepare site construction drawings, showing the layout of various new and
necessary, to support the proposed antenna system. The structural analysis does
not include mapping, structural measurement survey, materials testing,
geotechnical investigation, and/or other field investigation to acquire the data. If
the tower structure fails the analysis, the cost of any site relocation or
modifications to the tower required to support the antenna system will be the
responsibility of Floyd County, GA.
♦ Research permit requirements (building, utility, and construction) for the
construction of the proposed site, and determine if the permits are required. If a
permit is required, Motorola shall obtain the necessary permit forms and complete
the necessary information on behalf of the Customer.

December 16, 2010

applicable permits.
Site Preparation


9.2.9 Site Development at Taylor’s Ridge (NWGA) Site

Site Scope Summary
♦ Engineering services for site drawings and regulatory approvals – Not included.
♦ Existing tower to be used for antennas – 180 ' Self supported Tower.
Motorola Will:
Site Engineering

December 16, 2010

necessary, to support the proposed antenna system. The structural analysis does
not include mapping, structural measurement survey, materials testing,
geotechnical investigation, and/or other field investigation to acquire the data. If
the tower structure fails the analysis, the cost of any site relocation or
modifications to the tower required to support the antenna system will be the
responsibility of Floyd County, GA.
♦ Provide tower climbing and tower mapping services for towers up to 350 feet to
collect information about structural members and existing equipment.
Site Preparation
The following Customer Responsibilities and Assumptions Apply to: the

Rocky Mountain and Taylor’s Ridge sites.
Customer Will:
fees.
property.
property owner.

December 16, 2010

investigations.
other equipment.
♦ Arrange for space on the structure for installation of new antennas at the proposed
heights on designated existing antenna-mounting structures.
♦ Provide as-built structural and foundation drawings of the structure and site
location(s) along with geotechnical report(s) for Motorola to conduct a structural
analysis.
♦ Provide support facilities for the antenna cables (cable ladder, entry ports,
waveguide bridge) from the antenna to the equipment room.
♦ Pay for any upgrade of the antenna support structure necessary to accommodate
the new antennas.
meter, and disconnect within 50 feet of the proposed equipment room location.
♦ Provide space, HVAC, backup power (generator), outlets unless otherwise
indicated, grounding, surge suppression, lighting, fire suppression and cabling
facilities for the equipment room per Motorola's R56 specifications. Ceiling and
cable tray heights in the equipment rooms should be such as to accommodate 7-
1/2-foot equipment racks, and the ceiling should be 9 feet or greater.
♦ Confirm that there is adequate utility service to support the new equipment and
ancillary equipment.
♦ Confirm that the existing generator is sufficient to support the new equipment and
ancillary equipment loads.
♦ If required, provide any physical improvements (walls, roofing, flooring, painting,
etc.) necessary to house the equipment in the existing room.
♦ Supply a grounding tie point within ten (10) feet of the-Motorola-supplied
equipment.
♦ Supply required standby generator power to support the additional proposed
equipment. This power source shall be adequate to back up all radio equipment,
future equipment growth, and ancillary equipment such as, but not limited to,
interior lighting, tower lighting and HVAC.
♦ Provide support and entry facilities for the cables (cable ladder/chaseway, entry
ports, etc.) between the proposed equipment locations.

December 16, 2010

Assumptions:
tasks.
generator fuel, electrical, Telco] will be borne by the Customer or site owner.
♦ The existing ground system and soil resistivity at the site is sufficient to achieve
resistance of 10 ohms or less. Communication site grounding will be designed
and installed per Motorola’s R56 standards.
♦ AM detuning or electromagnetic emission studies will not be required.
♦ Protective grating over microwave dishes or the communications shelter has not
been included in this proposal.
♦ Structural and foundation drawings of the antenna support structure will be made
available to preclude the need for ultrasonic testing or mapping of existing tower
structural members.
♦ Lead paint testing of existing painted towers has not been included.
♦ On the existing tower, the antenna locations for the proposed antenna system
design will be available at the time of installation.
♦ The site has adequate utility service to support the proposed equipment loading.
Utility transformer upgrades or step-up or down transformers will not be required.
♦ The existing antenna support structure is structurally capable of supporting the
new antenna, cables, and ancillary equipment proposed and will not need to be
removed or rebuilt at the existing site. The tower or supporting structure meets all
applicable EIA/TIA-222 structural, foundation, ice, wind, and twist and sway
requirements. Motorola has not included any cost for structural or foundation
upgrades to the antenna support structure.
♦ The existing cable support facilities from the antenna to the cable entry port can
be used for supporting the new antenna cables.
♦ Structural analyses for towers or other structures that have not been performed by
Motorola will relinquish Motorola from any responsibility for the analysis report
contents and/or recommendation therein.

December 16, 2010

♦ The site will have adequate room for installation of proposed equipment, based on
applicable codes and Motorola’s R56 standards.
♦ The existing utility service and backup power facilities (generator) have sufficient
extra capacity to support the proposed new equipment load.
room.
♦ The Customer does not desire upgrade of the existing site to meet Motorola’s R56
standards.
Completion Criteria
9.2.10 Site Development at Floyd County 911 Site

Floyd County 911 is located in Rome, GA. The equipment room and dispatch facility
are on the second floor. As the systems will need to run in parallel prior to cutover,
this site will receive a UPS for the new console system and master site.
Site Scope Summary

♦ Engineering services for site drawings and regulatory approvals – Not included.
♦ Existing tower to be used for antennas – 50 ' Rooftop.
Motorola Will:
Site Engineering
necessary, to support the proposed the proposed equipment loads.

December 16, 2010

♦ Perform an x-ray of the structure (up to 15 location of three square feet each) to
determine the location of structural components and rebar sizing.
Site Preparation

♦ Install 2 8-outlet distribution-bar(s) and wire each outlet to individual breaker.
♦ Install 1 new single-phase UPS equipment and wire output to UPS distribution
panel.
existing room.
Customer Will:
fees.
the installation effort and on an ongoing basis.
property.
♦ Provide personnel to observe progress and testing of site equipment according to
the schedule provided by Motorola.
investigations.

December 16, 2010

♦ Arrange for space on the roof for installation of new antennas at the proposed
locations.
♦ Provide as-built structural and foundation drawings of the structure and site
location(s) along with geotechnical report(s) for Motorola to conduct a structural
analysis.
♦ Provide support facilities for the antenna cables (cable ladder, entry ports,
waveguide bridge) from the antenna to the equipment room.
♦ Pay for any upgrade of the antenna support structure necessary to accommodate
the new antennas.
♦ Provide space, HVAC, backup power (generator), outlets, grounding, surge
suppression, lighting, fire suppression and cabling facilities for the equipment
room per Motorola's R56 specifications. Ceiling and cable tray heights in the
equipment rooms should be such as to accommodate 7-1/2-foot equipment racks,
and the ceiling should be 9 feet or greater.
♦ Confirm that there is adequate utility service to support the new equipment and
ancillary equipment.
♦ Confirm that the existing generator is sufficient to support the new equipment and
ancillary equipment loads.
♦ If required, provide any physical improvements (walls, roofing, flooring, painting,
etc.) necessary to house the equipment in the existing room.
♦ Supply required standby generator power to support the additional proposed
equipment. This power source shall be adequate to back up all radio equipment,
future equipment growth, and ancillary equipment such as, but not limited to,
interior lighting, tower lighting and HVAC.
Assumptions:
tasks.
generator fuel, electrical, Telco] will be borne by the Customer or site owner.
♦ No improvements are required for crane access.

December 16, 2010

♦ Existing facility has an adequate ground system with a ground resistance of 10
ohms or less.
♦ Existing antenna support structure is structurally capable of supporting the new
antenna, cables and ancillary equipment proposed and will not need to be
removed or rebuilt at the existing site. The supporting structure meets all
applicable EIA/TIA-222 requirements. Motorola has not included any cost for
structural or foundation upgrades to the antenna support structure.
♦ Existing cable support facilities from the antenna to the cable entry port can be
used for supporting the new antenna cables
♦ The site will have adequate room for installation of proposed equipment, based on
applicable codes and Motorola’s R56 standards.
♦ The existing utility service and backup power facilities (generator) have sufficient
extra capacity to support the proposed new equipment load.
room.
♦ The Customer does not desire upgrade of the existing site to meet Motorola’s R56
standards.
Completion Criteria

December 16, 2010

December 7, 2010
Mr. Mark Hollomon

Motorola, Inc.
1700 Belle Meade Court
Subject: Report of Limited Tower Evaluation

Site Name: Floyd County-Shannon
Site Location: Fire Tower Road, Rome, GA
MACTEC Project No. 6143-10-0383
Dear Mr. Hollomo n:
MACTEC was asked to perform a structural evaluation of an existing tower located on Fire
Tower Road in Rome, Floyd County Georgia. The tower is an existing AT&T tower and was
initially scheduled to be 100 feet tall. MACTEC was asked to structurally evaluate the tower to
determine feasibility of a 200 foot extension i.e. a modification that would make the final tower
300 feet tall.
The current IBC building code references the TIA/EIA structural code for steel towers which
requires that the tower be designed to support a 70 mph fastest mile wind speed for Floyd
County Georgia. The 2009 IBC which is expected to be adopted by the state in 2012 would
require that the tower be designed for a 90 mph 3-second gust wind speed.
The code additionally requires that public safety towers be designed with an additional
importance factor of 1.5, i.e. it recommends that the suggested wind speeds be increased by 15%.
Motorola has requested that the tower be checked for a 120 mph sustained wind speed which
converts to a 140 mph 3-second gust wind speed.
It should be mentioned that the design forces on a tower due to the wind are directly proportional
to the square of the wind velocity or speed. Therefore, an additional factor of safety of 2.42
which compounds the aforementioned 15% increase, is ensued when evaluating for a 140 mph
wind speed (support calculation: (1402/902) x 100 = 242%).
MACTEC was tasked with mapping the tower to determine the tower dimensions and member
sizes. A copy of the tower mapping report is included in this document. The tower mapping
report indicates that the existing structure is 75 feet tall rather than the anticipated 100 feet. For
the analysis MACTEC assumed that the tower legs were 50ksi steel and other tower members
were A36 steel. MACTEC used RISA Tower (Version 5.4.2.0), a commercially available software
MACTEC Engineering and Consulting, Inc.
3200 Town Point Drive NW, Suite 100 • Kennesaw, GA 30144 • Phone: 770-421-3400 • Fax: 770-421-3486
Motorola – Floyd County December 7, 2010
MACTEC Project 6143-10-0383 Page 2
program, to evaluate the tower. MACTEC modeled the existing 75 foot tower with an additional
200 foot extension.
Using the software referenced above, MACTEC tried to evaluate the capacity of the tower to
support a 70 mph fastest mile wind speed, a 90 mph 3-second gust wind speed and a 140 mph 3-
second gust wind speed.
To rationalize the results realized, MACTEC will briefly explain the software’s iterative p-delta
analysis process. The first pass of the analysis applies the wind force to the tower and calculates
the deflection along its height. The weight of the tower and other vertical superimposed loads are
then applied to the structure in its deflected state. This is done to account for the additional
stresses caused by the gravity loads being non-concentric to the tower axis i.e. the so called p-
delta stresses. The structural program repeats this process to account for additional stresses until
the deflection between the predecessor and successor analyses runs are within 1% of each other.
At that point, the analysis is said to be complete.
The tower with the 200 foot extension was first evaluated using the 70 mph fastest mile wind
speed. No additional loads were placed on the tower. This run indicated that for a 70 mph fastest
mile wind speed the tower rating would be 127.20% of its design capacity i.e. the structure
would be 27.20% overstressed. Another attempt was made to analyze the tower under a 90 mph
and a 140 mph 3-second gust wind speed. When the tower was subjected to both of the
aforementioned wind speeds, the tower continued deflection without convergence. This
behavior indicates that the tower mast is not capable of carrying these wind forces. A copy of
the tower mapping and computer analysis for the 70 mph wind speed is included in the report.
Tower Loading:
The tower was evaluated in an unloaded state i.e. the analysis model attached does not account for the
existence of any existing or proposed antennae, microwave dishes, coax, mounting equipment and the
like.
Tower Summary:
The results obtained from RISA Tower (Version 5.4.2.0), and our review of those results indicates that
the existing tower structure CANNOT be adequately retrofitted to support a tower height extension
of 200ft under a 70 mph wind speed.
Foundation Summary:
No foundation information was available for the existing. However due to the fact that the tower
superstructure is not capable for being retrofitted to carry the recommended design wind load, MACTEC
concludes that the foundation would also be inadequate.
Motorola – Floyd County December 7, 2010
MACTEC Project 6143-10-0383 Page 2
We appreciate the opportunity to work with Motorola and look forward to contributing to the success of
this project. If we can be of further assistance, please do not hesitate to contact us.
Sincerely,
MACTEC ENGINEERING AND CONSULTING, INC.
Attachments: Structural Analysis and Tower Mapping

9.3 System Migration and Cutover Plan
9.3.1 Overview
In order to transition from the County’s and City’s existing analog conventional
channels to the proposed ASTRO 25 digital Trunking system, the County and
Motorola will need to develop a system migration and cutover plan. This plan, when
executed precisely, will allow the County and City users to transition as smoothly as
possible and without interruption onto the new system.
It is not the purpose of this document to present a final plan, but rather to identify the
key components that will be transitioned; to highlight the challenges associated with
those transitions, and to present recommended directions and solutions for each.
The final detailed plan will be developed as a joint collaboration between Motorola,
Floyd County’s technical team, and the individual system users or their
representatives.
9.3.2 Subscribers
Most of Floyd County’s existing subscribers are not upgradeable to the new P25
standard. In order to operate on the new ASTRO25 system, new subscribers will be
required. Therefore, the subscriber transition to the new Trunking system will
require significant coordination between Floyd County, Motorola, and Coosa Valley
Communications. When considering how to transition the County’s subscribers from
the current system to the proposed system, three issues are of primary importance:
♦ Developing a system Fleetmap for the subscriber radios
♦ Programming and distributing portables or installing mobile radios
♦ Maintaining seamless operations for the County and City public safety personnel
while user groups are transitioned to the ASTRO25 system.
9.3.3 Designing an Effective Fleetmap and Flexible Talkgroup

Structure
The development of a Fleetmap requires involvement of all potential users groups
and therefore takes a significant amount of time. Please review the Statement of
Work which outlines the steps required to complete Fleetmap planning. A good
Fleetmap will allow the flexibility of user groups to communicate during the system
transition. The transition from a conventional system to a Trunking system with a
well planned Fleetmap can be quite simple.

RFP# 101216
December 16, 2010
System Migration and Cutover Plan 9.3-1

9.3.4 Programming and Distributing Radios
The best approach for cutover is to provide an entire shift of a particular user group
new radios and have them all start their shift using the new radio system. While
portable radios can be programmed ahead of time and distributed quickly at the start
of a shift, mobile radios require install and must be completed ahead of time.
9.3.5 Maintaining Operations During Cutover

Once all user groups have been identified, it will be necessary for the project team to
choose the group migration order, set a transition schedule, and create the detailed
procedure for each group transition. Motorola will do the bulk of the work for this
process but will require regular meetings with County technical authorities to refine
and approve each step.
The largest challenge will be to maintain communications across multiple agencies
during this time. The simplest option is to keep the old radios on-hand until the
cutover is complete.
9.3.6 Dispatch
It is proposed that the new MCC7500 dispatch consoles will be installed in parallel
with the existing operator positions. The MCC7500s will have the ability to control
any existing VHF/UHF radios via 4-wire tone remote control. The MCC7500
consoles will all have direct access to the ASTRO 25 trunking talkgroups; therefore,
they will follow the transition of the subscriber units.
Since the consoles will operate side by side during the transition, all information will
be available—but during the transition the operators will need to use both the existing
consoles and the new MCC7500 consoles to access all information coming from both
systems.
Because operating two consoles in parallel is awkward, at best, the County and
Motorola will collaborate on a plan to minimize the time doing so by any individual
operator. This will require a detailed understanding of each operator’s responsibilities
and how those responsibilities are affected by the transitioning of the various
subscriber groups. If existing console control stations are capable of tone remote
control, the control stations can be moved to the new consoles to allow dispatch to
utilize the new console to dispatch on both P25 and existing analog channels.
9.3.7 Trunking Infrastructure

Motorola’s response calls for a completely parallel implementation of the system.
This will include buildings being installed at new sites, a new equipment room to be
constructed at Shannon AT&T, and new equipment at Rocky Mtn, as well as Floyd
911 and the Floyd Back-up EOC.

RFP# 101216
December 16, 2010
9.3-2 System Migration and Cutover Plan

During the creation of this proposal it was necessary to make some assumptions
concerning the following items. These assumptions will have to be addressed as part
of the overall transition plan:
♦ Frequencies – Ten (10) frequencies must be licensed at the proposed sites, with
the proposed antennas, and at the proposed antenna heights.
9.3.8 Fire & EMS Station Alerting Conventional Infrastructure

The existing VHF Fire Paging system will be relocated from the existing Mt. Alto
tower to the proposed Mt. Alto tower after an MTR2000 repeater is decommissioned
at the old Mt Alto tower. This transition would be made possible by consolidating
and/or removing the existing users on another MTR2000 channel and relocating and
reprogramming the repeater to operate at the new Mt. Alto location. The existing
dispatch consoles will be used to alert the Fire stations until the dispatch center
console cutover is completed.
The EMS alerting system will utilize a new 800MHz analog repeater which shares
the Mt. Alto 8TAC mutual aid transmitter antenna network. This repeater can be
installed prior to cutover and EMS stations can start to be alerted via the 800MHz
repeater as soon as the radio is installed at the EMS stations. During the station
cutover the existing station wiring will need to be reused and the dispatcher will be
required to alert EMS on both the existing repeater and the new repeater, using the
console’s multi-select feature.
Existing console radio control station resources are not capable of being connected in
parallel to the existing consoles and the new MCC7500 consoles. The Fire
Paging/Alerting control station will be transitioned to the MCC7500 console during
the dispatch center cutover.
9.3.9 Floyd County Jail

Motorola’s response calls for a highly coordinated cutover and implementation of the
repeater and control station system currently in use at the Floyd County Jail. Based
on Motorola’s understanding of the Officers and employees daily operation and
interpreting the RFP and site drawing provided in the addendum, Motorola feels that
an efficient cutover can be conducted to minimize user impact. Prior to any
installation, the new 800MHz repeater will be programmed and tested for operation
with the control stations and desk-sets provided for the new Jail communications
solution. The new MIP5000 console will be staged with the system at CCSi and will
be programmed in the field, based on results of the fleetmap process.

System Migration and Cutover Plan 9.3-3

The MIP5000 console will be installed and tested with its new P25 trunking resources
prior to the cutover. After the P25 Jail repeater is installed and tested, at the start of
each shift, P25 subscribers will be distributed to the users. As the Sheriff’s Office
users are cutover to their new associated Talkgroups, the associated desk-sets and
control stations will be switched to the same P25 Talkgroups. The entire Jail cutover
should take approximately 24 to 48 hours, however the Jail cutover is dependant on
the requirements of the Sheriff’s Office cutover to the P25 Trunking system. After
users and control stations are cutover, the MIP5000 console will be the primary Jail
dispatch console and the Command Start Lite will be decommissioned at a later date
once system cutover is complete.
9.3.10 Conclusion
As shown above, a smooth (if somewhat intricate) transition from the existing to the
new system can be achieved. The details of the repurposed equipment during the
transition will pose the greatest challenge to the transition team. Motorola has the
experience necessary to overcome these and any other challenges required to be met
during this transition.

RFP# 101216
December 16, 2010
9.3-4 System Migration and Cutover Plan

9.4 Motorola Project Team Resumes
Name Gary Brady

POSITION TITLE Sr. Systems Engineer
OFFICE ADDRESS 1700 Belle Meade Court, Lawrenceville, Georgia 30043
BUSINESS TELEPHONE 770-338-3868
YEARS OF RELEVANT 12
INDUSTRY EXPERIENCE
CERTIFICATIONS Bachelors in Computer Engineering from Georgia Tech
RELATED PROJECT Supporting Cobb County’s console upgrade to new
EXPERIENCE APCO25 compliant digital (ASTRO25) system.
Led the Motorola Engineering team during the relocation
of Forsyth County’s Dispatch center.
Engineered DeKalb County (implementation phase) and
Cobb County (vendor selection phase) console upgrades.
NAME Gary Minard

POSITION TITLE Senior Customer Service Analyst
OFFICE ADDRESS 1700 Belle Meade Court, Lawrenceville, GA 30043
YEARS OF RELEVANT 38
INDUSTRY EXPERIENCE
RELATED PROJECT Electronics Technician Third Class Petty Officer, US
EXPERIENCE Navy 1972-1977, Bench Technician- Commercial Radio,
Norfolk, VA 1977-1979, Field Technical Representative,
Motorola-1979-1981, District Manager, Field Technical
Representatives, Motorola 1981-1990, Area Field
Technical Representative Manager 1990-1995, Division
System Technologist Manager, 1995-2000, Technical
Operations Manager 2000-2003, Senior Customer Service
Analyst 2003- present
CERTIFICATIONS FCC General Class Radiotelephone License, NABER
Certification, Certified Master Technical Trainer,
Certified Customer Support Manager
SIMILAR PROJECTS / Houston County, GA P25 Smartzone Simulcast system,
CAPACITY Atlanta Olympics 1996, Hall County, GA P25 Smartzone
Simulcast system, Carroll County, GA / Western Area
Regional Radio System (WARRS) P25 Smartzone
Simulcast system, Catoosa County, GA / Northwest
Georgia Interoperability Committee (NWGIC) P25
Smartzone Simulcast - System Manager and System
Service Support Manager

RFP# 101216
December 16, 2010
Motorola Project Team Resumes 9.4-1

Name Mark Holloman
POSITION TITLE Project Manager
OFFICE ADDRESS 1700 Belle Meade Court
YEARS OF RELEVANT 21 Years
SERVICE
DESCRIPTION OF Motorola 2006 to Present
RELEVANT INDUSTRY Location: Kennesaw, GA
EXPERIENCE
Title: GA PM Team Lead
Business Unit
Managed the UASI Fayette County site expansion, COPS
GSU console upgrade, and the Carroll County / WARRS
P25 seven site simulcast implementation.
Motorola 2000- 2006
Location: Atlanta GA
Area Operations Manger
Nextel/Sprint
Managed the Motorola team responsible for installation
and upgrades for the Southeast portion of Nextel’s
territory. This included 9 switch office complexes.
Motorola 1994-2000
Location: Atlanta GA
Lead Project Manger/Lead Engineer
Nextel/Sprint
Responsible for overseeing the equipment installation and
optimization of the first 100 Nextel RF sites in the Atlanta.
Also included overseeing installation and commissioning
of Nextel switch offices. Installed, commissioned and
upgrade new switch office equipment.
Motorola 1989-1994
Location: Atlanta, GA
Project Manger
LMPS
Responsibilities included the installation and optimization
of RF equipment, site development and system cutovers.
Projects include SMR sites in the FL, GA, AL, LA and TN
area, Tampa Electric Simulcast, and City of Oak Ridge
Simulcast.
EDUCATIONS, BSS Electrical Engineering
CERTIFICATIONS AND Georgia Institute of Technology
MEMBERSHIPS
RFP# 101216
December 16, 2010
9.4-2 Motorola Project Team Resumes

Name Mark Holloman
Atlanta, GA
Sept. 1984- March 1989
Federal Communications Commission
First Class Radiotelephone License with Radar
Endorsement
Naber Certified Technician.
32 years of on going product, service, and technology
training through Motorola local and out of state training
facilities and seminars.
System Technologist Mike Yearout

POSITION TITLE System Technologist
OFFICE ADDRESS Motorola Solutions
495 Circle 85, Suite D
Atlanta, GA 30349
YEARS OF RELEVANT 33 Years (1997)
SERVICE
DESCRIPTION OF Provides system implementation services for mission critical
RELEVANT INDUSTRY public safety systems. Leads team of technicians in planning,
EXPERIENCE installing, configuring, testing and cutover of leading edge
wireless voice and data communications systems. Provides
diagnostic and troubleshooting expertise for operational
systems to root cause performance variations.
Simulcast & Zone Radio System Implementation Duties:

♦ Performed simulcast optimization to meet audio quality
specifications.
♦ Set up routers and switches to configure proper routing

of IP packets.
♦ Conducted functional tests on major system elements

to verify compliance with requirements.
♦ Performed system cutover from legacy network to new

P25 radio system.
The above technical services were applied to the

implementation of radio systems throughout the
Southeast Region and beyond, including the following
customers:
♦ Palmetto 800, SC ASTRO 4.1 Trunked Radio System
♦ Charlotte, NC ASTRO 4.1 & 7.5 Trunked Radio

System

RFP# 101216
December 16, 2010
Motorola Project Team Resumes 9.4-3

System Technologist Mike Yearout
♦ City of Tallahassee, FL 7.7 Trunked Radio System
♦ Wake County, NC Smartnet Trunked Radio System
♦ State of Delaware ASTRO 3.0 Trunked Radio System
♦ Fulton County, GA ASTRO 3.0/4.x Trunked Radio

System
♦ Orange County, FL Smartnet Trunked Radio System
♦ City of Atlanta, GA 7.x Digital Trunked Radio System
TRAINING, ♦ ASTRO P25 Advanced Systems Mobility Operations

CERTIFICATIONS (TTS141 )
AND AWARDS.
♦ ASTRO 6.7 / 7.0 Overview (FIL - 70764)
♦ MCC 7500 Consoles (FIL - 70763)
♦ ASTRO 6.x Site Optimization & Implementation (FIL -

70762)
♦ Radio Frequency (RF) Safety ( EHS0302 )
♦ MotoBridge Implementation (FIL - 70765)
♦ Motorola's Approach to Quality ( CIC2006 )
♦ Next Generation of Remote Access ( ITS2742 )
♦ Introduction to Product Security ( SCC1360 )
♦ ASTRO 25 7.XX INTERMEDIATE (FIL - 84644)
♦ Microwave Principles ( TTS133 )
♦ SmartX Migration ( TTS147 )
♦ Rebanding Techniques for System Technologists
♦ Antenna System Analysis ( TTS130 )
** The final assignment of the System Technologist will come at the time of contract
and will be determined by project availability. The person assigned will be 100%
dedicated this project.

RFP# 101216
December 16, 2010
9.4-4 Motorola Project Team Resumes

9.5 Subcontractor Profiles
9.5.1 Coosa Valley Communications
Motorola’s Service Partner, Coosa Valley Communications has been in business
since the 1950's. The current owner has been involved since June of 1976. Coosa
Valley Communications is the largest and most experienced two-way
communications service provider in Floyd County. They specialize in the sale,
installation and maintenance of radio communication networks, wireless broadband,
and 9-1-1 systems for Public Safety, Commercial, and Industrial users in the area.
As the authorized Motorola service facility in the Floyd County area for over 34
years, Coosa Valley Communications is a certified Motorola Service Partner with
two ETA certified technicians supervised by an ETA certified Journeyman
Technician who is currently completing Motorola's P25 training. Two full-time
installers perform mobile and fixed equipment installations, along with tower,
antenna, and transmission line installations.
Coosa Valley Communications headquarters includes a two-service bay drive-in
facility with a Technical Repair Center and Administrative Offices located at 10 Bale
Street in Rome, GA. This office is within one quarter mile of the Floyd County
Dispatch Center. Installing and servicing Floyd County and the associated
jurisdictions for many years, it is the preferred "radio shop" for the Floyd County
area.
Nearly all of the local governments in the area of Rome and Floyd County, which are
not self-maintained, rely upon Coosa Valley Communications for twenty-four
support and service. Other customers who depend upon Coosa Valley for service
include most of the industrial plants in Floyd County, Berry College and the local
Hospital.
9.5.2 Ceragon Networks

Who is Ceragon Networks?
Since 1996 Ceragon Networks Ltd. (NASDAQ: CRNT) is a leading provider of high-
capacity TDM and Ethernet wireless backhaul solutions.
We provide a broad portfolio of innovative, field-proven, high capacity wireless
backhaul solutions for the utility, public safety, right-of-way, carrier and federal
markets. These solutions are designed to deliver voice and premium data services,
eliminate the backhaul capacity bottleneck, improve throughput and, significantly
reduce backhaul costs and transition for TDM and next generation IP-based
networks.

RFP# 101216
December 16, 2010
Subcontractor Profiles 9.5-1

Ceragon's focus on backhaul is a significant advantage as it serves all types of access
technologies, and any type of network. The main driver of Ceragon's business is its
modular FibeAir® product family, a cutting-edge, high-capacity solution for Carrier
Class backhaul transport of broadband services over IP, TDM and SONET networks.
Worldwide Sales
With a customer base of over 150 service providers and hundreds of private networks
Ceragon's solutions are deployed in nearly 100 countries across the globe. Operating
an extensive sales network, Ceragon has numerous sales offices located throughout
North and South America, EMEA and Asia, handling direct sales. Our headquarters
for our North American operations is located in Paramus, New Jersey and handles
sales, engineering, program management, system integration, training and customer
service.
Ongoing Leadership
As a long-time leader, Ceragon has achieved numerous industry "firsts", including
the first solution for wireless transmission of 155 Mbps at 38 GHz, the first native IP
wireless transmission offering, the first to achieve Metro Ethernet Forum (MEF)
certification for microwave Ethernet and other breakthroughs. The Ceragon's
innovative approach has been proven to provide a rapid, highly reliable, cost effective
and scalable wireless answer for all types of access networks, a true competitive
advantage that provides a sturdy foundation for the Ceragon's current success and
ongoing growth prospects. We at Ceragon believe in a culture of innovation which
allows for our customers to enjoy the most feature rich radios with the highest
reliability and lowest costs on the market.
Comprehensive Support
Ceragon provides customers with complete Engineering, Furnish and Installation
services. Our design team will work with Nelson County from inception, path
optimization, FCC licensing, Staging, Installation, Cutover and Field Acceptance test
immediate professional technical assistance through its North American Service and
Support Center. During standard business hours, customers may contact the Help
Desk by phone, email or web form, and will be assisted by professional specialists
who have a thorough understanding of Ceragon products. After hours, Ceragon staffs
a round-the-clock Emergency Support Hotline, ensuring that network availability is
never compromised.
Additional information
Additional information regarding including financial statements, our leadership team,
global presence and such can be found at http://www.ceragon.com.

RFP# 101216
December 16, 2010
9.5-2 Subcontractor Profiles

9.5.3 United Tower Co., LLC
740 Adamson Drive
P.O. Box 1229
Monroe, GA 30655
P: 770-267-0335
F: 770-267-0751
Email: utcllc@windstream.net
Company Information
United Tower Company has been in business for over 42 years. We are a family run
business with three generations working together in the communications industry.
William W. Singleton was the original owner of the business, but has since retired.
Tracy Singleton is the President of the company and Project Director. Tracy's son
Jason Singleton serves as Vice President and is also one of the crew leaders. Tracy's
son-in-law Danny L. Tillery serves as the Office Manager for the company.
United Tower Company provides a variety of services, including installation of lines,
antennas, and associated materials; light changes, painting towers to FCC
specifications, tower erections, and installation of foundations.
We guarantee customer satisfaction and offer several major companies as references:
Southern Company - Laverne Vickery @ 386-938-1118
Motorola - Jay Nix @ 678-772-2651
Midland Communications - Henry Hodgkins @ 706-629-1730
United Tower Company provides WSB, WXIA, and many area counties with quality
service and dependable workmanship.
We have worked in Maryland, Tennessee, Alabama, Florida, Georgia, North
Carolina, South Carolina, Arkansas, Alaska, Montana, Texas, and Haiti.
All employees have completed the Fall Protection and Competent Tower Climber
certification by SALA. All have been trained in First Aid and CPR. United Tower
Company serves as a qualified vendor for Motorola and Southern Company.

December 16, 2010

9.5.4 MACTEC
“MACTEC has the resources to perform virtually any scope of work, regardless of
location, size, or complexity.”
Contact MACTEC today for more information, or visit us online at
mactec.com/geotech.
Towering Mapping and Structural Analysis

Following nine acquisitions, MACTEC has become a leader in the engineering,
environmental, and remedial construction industries. Operating with 70 U.S.
locations and over 2,700 employees—including specialists in approximately 50
scientific and engineering disciplines—MACTEC has the resources to perform
virtually any scope of work, regardless of location, size, or complexity.
MACTEC Then
In 1975, MACTEC began serving the electric utility and nuclear power plant
construction industries and in the 1980s expanded into nuclear site remediation. In
1997, MACTEC began to acquire companies that provided design/build and
environmental services. With the 2000 merger of Harding Lawson Associates Group,
Inc. and Environmental Science & Engineering, Inc., MACTEC expanded into the oil
and gas, mining, manufacturing, consumer products, chemical and pharmaceutical,
aerospace, transportation, telecommunications, and waste management industries.
Pacific Environmental Services, Inc. (PES) brought major U.S. Department of
Defense (DoD) contracts and nationally recognized value engineering, occupational
health and safety, water/wastewater management, and pollution prevention expertise.
MACTEC Now
With broader geographic coverage, deeper resources, and expanded technical
capabilities, MACTEC is now a $440 million firm providing a full range of
engineering, environmental, and construction services to approximately 5,000 clients
worldwide. Uniting the strengths of the former Harding ESE, LAW, and PES,
MACTEC provides a wide variety of services, including site development, planning
and engineering design, construction phase services, environmental, and facilities
operation and maintenance (O&M). With world-class expertise in various disciplines,
including environmental, facilities, civil, structural, and geotechnical engineering,
MACTEC provides innovative, efficient solutions tailored to our clients’ needs. With
the recent merger of MACTEC Engineering and Consulting, Inc. with MACTEC
Federal Programs, MACTEC also addresses the unique needs of U.S. government
agencies, including DoD, the Department of Energy (DOE), USEPA, NASA, and
NPS.

RFP# 101216
December 16, 2010

Site Design Support Services
♦ Zoning support
♦ Environmental site assessment
♦ NEPA/FCC compliance services
♦ Geotechnical investigation
♦ Foundation design
♦ Resistivity testing
♦ Construction testing
♦ Site acquisition
♦ Surveying
♦ Structural evaluation of existing towers
♦ Construction drawings
Construction Management
♦ Review civil design drawings
♦ Prepare construction bid packages
♦ Prepare construction closeout binders
Construction Materials Testing

♦ Concrete testing
♦ Steel testing and inspection
♦ Foundation inspection
Site Audits
♦ Field audits
♦ Report preparation MACTEC can provide these services for raw land, co-locate
and facility sites (rooftops, water tanks, billboards, etc.)
Project Experience
MACTEC has provided tower-related services for over 40 years, including more than
5,000 telecommunication sites. Major carriers, build-to-suit companies, and program
managers include:
♦ Berliner Communications, Inc.
♦ Nextel
♦ Chase
♦ American Tower
♦ Nextel Partners
♦ Centerpointe
♦ Lucent Technologies
♦ Metro PCS
♦ Crown Castle

December 16, 2010

♦ Verizon Wireless
♦ Signal One
♦ Faulk and Foster
♦ Sprint_Com
♦ Powertel
♦ Cellular One
♦ Omnipoint US Cellular
♦ OnSite
♦ Metricom
♦ Cricket Communications
♦ SSI Communications
♦ Motorola, Inc.
♦ BroadLink
♦ CLS Group
♦ Bell South
♦ Tritel
♦ SpectraSite
♦ AT&T
♦ SBA
♦ VoiceStream
♦ General Dynamics
♦ Alpha Omega
♦ Cingular Wireless
♦ Qwest
♦ Spring PCS
♦ Nortel

RFP# 101216
December 16, 2010

9.5.5 Motorola Service Partners
Motorola Service Partners Supporting P25 systems within 100 Miles of Floyd County,
Georgia
Company Servicer Certified Years in Street City, State, ASTRO P25 Systems
Level Technicians Service Address Zip - Installed and/or
Maintained
Atlanta Motorola 7 49 1510 Huber Atlanta, City of Atlanta, Urban
Communications Service Street GA 30318 Area Security Initiative
Partner (Metro Atlanta)
Communications Motorola 2 23 105 West Dalton, NW Georgia
and Engineering Service Ezzard Ave GA 30721 Interoperable
Partner Communications
Communications Motorola 1 30 2310 Belle Chattanooga, NW Georgia

and Engineering Service Arbor Ave TN 37406 Interoperable
Partner Communications
Diversified Premier 4 22 1290 Field Marietta, Cobb County,GA -

Communications Service Parkway GA 30066 Urban Area Security
Partner Initiative (Metro
Atlanta) - NW Georgia
Interoperable
Communications
Diversified Premier 3 12 309C Forest Park, Cobb County,GA -
Communications Service Agnew GA 30298 Urban Area Security
Partner Drive Initiative (Metro
Atlanta)
East Georgia Motorola 2 16 1375 Covington, Walton County, GA
Communications Service Access GA 30014
Partner Road
Metropolitan Motorola 6 36 103 Carrollton, Western Area

Communications Service Commercial GA 30117 Regional Radio
Partner Avenue System (WARRS)
including Carroll,
Heard and Haralson
Counties in GA
Mobile Premier 3 10 1479 A Cumming, Forsyth County, GA
Communications Service Ventura GA 30040
Partner Drive
Mobile Premier 4 55 526 Oak Gainesville, Hall County, GA

Communications Service Street GA 30501
Partner
Mobile Premier 4 20 885 Cripple Lawrenceville, Gwinnett County, GA -

Communications Service Creek Drive GA 30043 Greene County, GA
Partner
Mobile Premier 3 12 2241 Tucker Tucker, DeKalb County, GA

Communications Service Industrial GA 30084
Partner Road

December 16, 2010

C&E 175 Field Support Technicians
On the Ground Every Day
Coosa Valley
Mobile Comm
Diversified East Ga
Atlanta Comm
Augusta Comm
Motorola SRC
Metropolitan Comm
Transcomm
Savannah Comm
Columbus Comm
Macon Comm
Albany Comm Hasty’s East
Thomasville Comm Hasty’s Comm
Figure 9.5-1: Motorola Service Partners

RFP# 101216
December 16, 2010

9.6a Project Schedule Summary

December 16, 2010
Project Schedule Summary 9.6a-1


December 16, 2010
9.6a-2 Project Schedule Summary

Floyd County, Georgia - Preliminary Project Gantt Summary
FLOYD CNTY DGT TRK GA-10Q123A Duration Task Start Task Finish 2011 2012
As of Date > 12/10/2010 Days May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct
Summary ImpProj-0 Preliminary Implementation Project Schedule - Floyd County 375 5/31/2011 11/5/2012
Phase Cont-0 Contract 31 5/31/2011 7/12/2011
Phase IDR-0 Contract Design Review 15 7/13/2011 8/2/2011
Phase SitAcqCust-9 Site Acquisition Completed 0 5/31/2011 5/31/2011
Phase Ord-0 Order Processing 10 8/3/2011 8/16/2011
Phase Mnfg-0 Equipment Manufacturing 165 8/17/2011 4/3/2012
Phase FltMap-0 Fleetmapping 138 9/14/2011 3/23/2012
Phase Stage-0 Staging 77 10/20/2011 2/6/2012
Phase CIV-1-11 Site Development Mount Alto 220 6/3/2011 4/5/2012
Phase CIV-4 Site Development Leonard Road 220 6/3/2011 4/5/2012
Phase CIV-7 Site Development Fouche Gap 220 6/3/2011 4/5/2012
Phase CIV-3 Site Development Hillindale 220 6/3/2011 4/5/2012
Phase CIV-5 Site Development Cave Springs 220 6/3/2011 4/5/2012
Phase CIV-8-8 Site Development Blossom Hill 128 6/3/2011 11/29/2011
Phase CIV-6-6 Site Development Rocky Mountain 134 6/3/2011 12/7/2011
Phase CIV-2-2 Site Development Shannon AT&T 233 6/3/2011 4/24/2012
Phase CIV-9 Site Development Floyd 911 233 6/3/2011 4/24/2012
Phase Inst-0 FNE Installation 34 2/21/2012 4/6/2012
Phase Cnsl-0 Console and Control Station Installation 141 10/4/2011 4/17/2012
Activity Cnsl-1 Console Installation - Floyd 911 87 12/2/2011 4/2/2012
Activity Cnsl-2 Console Installation - Backup EOC 133 10/4/2011 4/5/2012
Activity Cnsl-3 Console Installation - Jail 6 4/3/2012 4/10/2012
Activity Cnsl-4 Installation - Sheriffs Office / Courthouse 2 4/11/2012 4/12/2012
Activity Cnsl-5 Installation - Prison 3 4/13/2012 4/17/2012
Phase MW-0 Microwave Studies and Installation 168 8/26/2011 4/17/2012
Phase SysOpt-0 System Optimization 181 12/7/2011 8/15/2012
Task SysLnkVer-0 Link Verification 9 2/27/2012 3/8/2012
Task SysOptFNE-0 Optimize System FNE 35 4/18/2012 6/5/2012
Activity Trng Training 181 12/7/2011 8/15/2012
Phase ATP-0 Audit and Acceptance Testing 141 2/1/2012 8/15/2012
Phase Subb Subscriber Installation 60 4/4/2012 6/26/2012
Phase Fnl-0-0-0 Project Finalization 209 1/18/2012 11/5/2012
Activity Cutover Cut-Over 164 1/18/2012 9/3/2012
Activity 03.05-5 System Testing & Cutover Milestones 2 9/4/2012 9/5/2012
Task FnlInspCust-0 Final Inspection w/Customer 10 9/4/2012 9/17/2012
Task FnlPunRes-0 Punchlist Resolution 15 9/18/2012 10/8/2012
Task FnlDoc-0 Finalize Documentation ** 45 8/16/2012 10/17/2012
Task FnlSerTran-0 Transition Service/PTC 3 10/18/2012 10/22/2012
Milestone FnlAccpt-0 Final Acceptance 0 10/22/2012 10/22/2012
Task TrngSupp-0 Supplemental SystemTraining ** 10 10/23/2012 11/5/2012
12/10/10 1/1
9.6b Project Schedule

December 16, 2010
Project Schedule Summary 9.6b-1


December 16, 2010
9.6b-2 Project Schedule Summary

Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A FLOYD CNTY DGT TRK GA-10Q123A Duration Task Start Task Finish 2011 2012
Summary ImpProj-0 Preliminary Implementation Project Schedule - Floyd County 375 5/31/2011 11/5/2012
Phase Cont-0 Contract 31 5/31/2011 7/12/2011
Milestone ContAdmAward-0 Contract Award 0 5/31/2011 5/31/2011
Task ContAdm-0 Contract Administration 20 5/31/2011 6/27/2011
Task ContK0-0 Project Kick - Off 11 6/28/2011 7/12/2011
Phase IDR-0 Contract Design Review 15 7/13/2011 8/2/2011
Task CDR-0 Review Contract Design 15 7/13/2011 8/2/2011
Milestone IDDRApp-0 Design Review Approval 0 8/2/2011 8/2/2011
Phase SitAcqCust-9 Site Acquisition and Development 0 5/31/2011 5/31/2011
Milestone SitAcqCust-1 Site Acquisition Mt Alto (Customer Responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-2 Site Acquisition Shannon AT&T (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-3 Site Acquisition Hillindale (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-4 Site Acquisition Leonard Road (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-5 Site Acquisition Cave Springs (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-6 Site Acquisition Rocky Mtn (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-7 Site Acquisition Fouche Gap (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-8 Site Acquisition Blossom Hill (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqCust-MS Site Acquisition Floyd 911 Zone Core (Customer responsibility) Com 0 5/31/2011 5/31/2011
Milestone SitAcqCust-MS-0 Site Acquisition Backup EOC (Customer responsibility) Complete 0 5/31/2011 5/31/2011
Milestone SitAcqComp-0 Site Acquisition Complete - Notice to Proceed 0 5/31/2011 5/31/2011
Phase Ord-0 Order Processing 10 8/3/2011 8/16/2011
Task OrdProc-0 Process Equipment list 10 8/3/2011 8/16/2011
Milestone OrdBrdg-0 Order Bridged 0 8/16/2011 8/16/2011
Phase Mnfg-0 Equipment Manufacturing 165 8/17/2011 4/3/2012
Task MnfgTow-0 Manufacture Towers 25 11/14/2011 12/16/2011
Task MnfgBldg-0 Manufacture Buildings 40 12/7/2011 1/31/2012
Task MnfgMW-0 Manufacture Microwave Equipment 46 10/28/2011 12/30/2011
Task MnfgMFNE-0 Manufacture FNE 47 8/17/2011 10/20/2011
Task MnfgDS-0 Manufacture Non-Staged Equipment 46 8/17/2011 10/19/2011
Task MnfgSub Manufacture Subscribers ( as contracted for) 45 2/1/2012 4/3/2012
Phase FltMap-0 Fleetmapping 138 9/14/2011 3/23/2012
Task FltMapTrn-0 Customer Training for Fleetmapping 20 9/14/2011 10/11/2011
Task FltMapDev-0 Develop Initial Fleetmap Configurations 46 10/12/2011 12/14/2011
Task FltMapDevFnl-0 Develop Final Fleetmap Configuration 32 12/15/2011 1/27/2012
Milestone FltMapApp-0 Customer Approval of Fleetmap 0 1/27/2012 1/27/2012
Task FltMapProg-0 Develop Programming Templates 40 1/30/2012 3/23/2012
Milestone FltMapCpt-0 Fleetmapping Complete 0 3/23/2012 3/23/2012
Phase Stage-0 Staging 77 10/20/2011 2/6/2012
Milestone MnfgStgShip-0 Ship to Staging 0 10/20/2011 10/20/2011
Task StgRxInv-0 Receive and Inventory Equipment 10 10/21/2011 11/3/2011
Task StgSys-0 Stage System 31 12/15/2011 1/26/2012
Task StgATP-0 Perform Staging ATP 7 1/27/2012 2/6/2012
Milestone CCSIShip-0 CCSi Acceptance 0 2/6/2012 2/6/2012
Milestone StgShip-0 Ship Equipment to Field 0 2/6/2012 2/6/2012
Phase CIV-1-11 Site Development Mt Alto 220 6/3/2011 4/5/2012
Activity Civ-1 A&E - Mt Alto 130 6/3/2011 12/1/2011
Task CivSur-1-1 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-1-2 Prepare, Review and Approve Site Sketch 7 6/8/2011 6/16/2011
Task CivSur-1 Site Survey and Mapping 7 6/22/2011 6/30/2011
Task CivArch-1-11 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task CivArch-1-12 New Tower Zoning App and Approval 70 7/15/2011 10/20/2011
Task CivNEPA-1 NEPA/SHPO Studies and Approvals 70 6/21/2011 9/26/2011
Task CivGEO-1 GeoTech Testing and Report 8 7/5/2011 7/14/2011
Task MWPathSur-1 MW Path Studies 3 7/15/2011 7/19/2011
Task BldDes-1 Design Tower and Building 6 7/22/2011 7/29/2011
12/10/10 1/13
Task CivArch-1 Final Approval of Site Drawings by County 12 10/21/2011 11/7/2011
Task CivSitPerm-1-3 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-1-2 Land Disturbance Permit App and Approval 5 11/11/2011 11/17/2011
Task CivSitPerm-1 Electrical Permit App and Approval 10 11/11/2011 11/24/2011
Milestone CivComp-1 A&E Complete - Mt Alto 0 11/24/2011 11/24/2011
Activity CivSitPrep-1-19 Site Preparation - Mt Alto 23 12/6/2011 1/5/2012
Task CivSitPrep-1-18 Mobilization 1 12/6/2011 12/6/2011
Task CivSitPrep-1-17 Locate Utilities 1 12/9/2011 12/9/2011
Task CivSitPrep-1-16 Construction Staking 2 12/12/2011 12/13/2011
Task CivSitPrep-1-15 Heavy Clearing and Grubbing 14 12/7/2011 12/26/2011
Task CivSitPrep-1-14 Compound Grading and Silt Fencing 3 12/23/2011 12/27/2011
Task CivSitPrep-1-13 Pickup Meter and Install Meterboard 2 12/28/2011 12/29/2011
Task CivSitPrep-1 Utility Hookup to the Site by Electric Co 5 12/30/2011 1/5/2012
Activity TowConst-1 Tower Construction - Mt Alto 31 12/14/2011 1/25/2012
Task TowCnstShip-1 Ship Anchor Bolts and Base Plate to Site 4 12/14/2011 12/19/2011
Task TowCnstFndn-1 Drill, Rebar, and Pour Drilled Pier Foundation 5 12/28/2011 1/3/2012
Task TowCnstFndn-1-1 Foundation Inspection / Concrete Testing 1 1/2/2012 1/2/2012
Task TowCnstGrd-1 Tower Grounding 1 1/2/2012 1/2/2012
Task TowCnstShip-1-2 Ship Forms, Backfill, and Compaction 1 1/9/2012 1/9/2012
Task TowCnstShip-1-1 Ship Tower to Site 4 1/9/2012 1/12/2012
Task TowCnstFAA-1 Notify FAA of Impending Tower Construction 1 1/10/2012 1/10/2012
Task TowAssem-1-2 Tower Assembly and Stacking - Mt Alto 4 1/16/2012 1/19/2012
Task TowAssem-1-1-1 Tower Plumbness Testing 1 1/20/2012 1/20/2012
Task TowCnstFAA-1-1 Notify FAA of Tower Completion 1 1/20/2012 1/20/2012
Task AntRxInv 1-1 Ship Antennas, Lines, and Accessories to the Site 5 1/10/2012 1/16/2012
Task AntRxInv 1 Install Antennas and Lines 4 1/20/2012 1/25/2012
Milestone TowComp-1-1 Tower Complete - Mt Alto 0 1/25/2012 1/25/2012
Activity Bldg-1-1 Site Components Installation - Mt Alto 63 1/10/2012 4/5/2012
Task BldUtilHU-1 Trench and Install Underground Power Conduits 5 1/10/2012 1/16/2012
Task BldGrnd-1-3 Trench and Install Grounding 2 1/17/2012 1/18/2012
Task BldGrnd-1-2 Grounding Inspection 1 1/19/2012 1/19/2012
Task BldUtilHU-1-1 Conduit Inspection and Backfill 1 1/17/2012 1/17/2012
Task BldFndCnst-1 Excavate, Form, and Rebar Shelter Foundations 3 1/19/2012 1/23/2012
Task BldFndCnst-1-2 Excavate, Form, and Rebar Fuel Tank Foundation 1 1/19/2012 1/19/2012
Task BldFndCnst-1-1 Excavate, Form, and Rebar Generator Foundation 1 1/20/2012 1/20/2012
Task BldFndInsp-1 Foundation Inspection, Concrete Pour and Testing 1 1/24/2012 1/24/2012
Task BldConDel-1 Ship Shelter to the Site 2 2/1/2012 2/2/2012
Task BldConDel-1-4 Offload and Install Equipment Shelter 2 2/3/2012 2/6/2012
Task BldConDel-1-3 Offload and Install Generator 2 2/3/2012 2/6/2012
Task BldConDel-1-2 Install Fuel Tank and Piping 2 2/9/2012 2/10/2012
Task BldConDel-1-1 Piping Inspection, Leakage Test, and Backfill 3 2/13/2012 2/15/2012
Task BldExtCon-1 Cabling and Hookup Power System to Shelter 3 2/16/2012 2/20/2012
Task BldElecInsp-1 Building/Electrical Inspection 1 2/21/2012 2/21/2012
Task BldGrnd-1-1 Install Icebridge from Shelter to Tower 2 2/16/2012 2/17/2012
Task BldCln-1-1 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldFnc-1 Fencing of Tower Compound 3 3/6/2012 3/8/2012
Task BldGrnd-1 Complete Grounding Connections 1 3/9/2012 3/9/2012
Task BldCln-1 Site Touchup and Restoration 2 3/12/2012 3/13/2012
Task BldWrkCom-1 Line Termination and Sweep Test 1 2/22/2012 2/22/2012
Task BldWrkCom-1-4 Generator Startup / Test Power System 1 2/27/2012 2/27/2012
Task BldWrkCom-1-3 Grounding Test of the Site 1 3/12/2012 3/12/2012
Task BldWrkCom-1-2 Startup / Test Shelter Power System 1 3/1/2012 3/1/2012
Task BldWrkCom-1-1 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/2/2012 3/2/2012
Task BldPunRes-1-1-1 Punch List with Floyd County 1 3/14/2012 3/14/2012
Task BldPunRes-1-2 Punch List completion - Mt Alto 9 3/15/2012 3/27/2012
12/10/10 2/13
Task BldDoc-1-1 Finalize As-Built drawings from A&E - Mt Alto 7 3/28/2012 4/5/2012
Milestone SitDevComp-1-1 Site Development Complete - Mt Alto 0 4/5/2012 4/5/2012
Phase CIV-4 Site Development Leonard Road 220 6/3/2011 4/5/2012
Activity Civ-4-4 A&E - Leonard Road 130 6/3/2011 12/1/2011
Task CivSur-4 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-4-5 Site Survey and Mapping 7 6/22/2011 6/30/2011
Task CivArch-4 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task CivArch-4-5 Final Approval of Site Drawings by County 12 10/21/2011 11/7/2011
Task CivSitPerm-4 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-4-5 Electrical Permit App and Approval 10 11/11/2011 11/24/2011
Milestone CivComp-4 A&E Complete - Leonard Road 0 11/24/2011 11/24/2011
Activity CivSitPrep-4 Site Preparation - Leonard Road 23 12/6/2011 1/5/2012
Task CivSitPrep-4-10 Utility Hookup to the Site by Electric Co 5 12/30/2011 1/5/2012
Activity TowConst-4 Tower Construction - Leonard Road 31 12/14/2011 1/25/2012
Task TowAssem-4 Tower Assembly and Stacking 4 1/16/2012 1/19/2012
Task TowAssem-4-4 Tower Plumbness Testing 1 1/20/2012 1/20/2012
Task AntRxInv 4 Ship Antennas, Lines, and Accessories to the Site 5 1/10/2012 1/16/2012
Task AntRxInv 4-4 Install Antennas and Lines 4 1/20/2012 1/25/2012
Milestone TowComp-4 Tower Complete - Leonard Road 0 1/25/2012 1/25/2012
Activity Bldg-4 Site Components Installation - Leonard Road 63 1/10/2012 4/5/2012
Task BldGrnd-4 Trench and Install Grounding 2 1/17/2012 1/18/2012
12/10/10 3/13
Task BldCln-4 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldGrnd-4-6 Complete Grounding Connections 1 3/9/2012 3/9/2012
Task BldCln-4-4 Site Touchup and Restoration 2 3/12/2012 3/13/2012
Task BldPunRes-4 Punch List with Floyd County 1 3/14/2012 3/14/2012
Task BldPunRes-4-4 Punch List completion - Leonard Road 9 3/15/2012 3/27/2012
Task BldDoc-4 Finalize As-Built drawings from A&E - Leonard Road 7 3/28/2012 4/5/2012
Milestone SitDevComp-4 Site Development Complete - Leonard Road 0 4/5/2012 4/5/2012
Phase CIV-7 Site Development Fouche Gap 220 6/3/2011 4/5/2012
Activity Civ-7-7 A&E - Fouche Gap 130 6/3/2011 12/1/2011
Milestone CivComp-7 A&E Complete - Fouche Gap 0 11/24/2011 11/24/2011
Activity CivSitPrep-7 Site Preparation - Fouche Gap 23 12/6/2011 1/5/2012
Activity TowConst-7 Tower Construction - Fouche Gap 31 12/14/2011 1/25/2012
Milestone TowComp-7 Tower Complete - Fouche Gap 0 1/25/2012 1/25/2012
Activity Bldg-7 Site Components Installation - Fouche Gap 63 1/10/2012 4/5/2012
12/10/10 4/13
FFloyd County, Georgia -Preliminary Project Gantt
Task BldGrnd-7 Trench and Install Grounding 2 1/17/2012 1/18/2012
Task BldCln-7 Finish Grade and Gravel Compund 3 2/28/2012 3/1/2012
Task BldPunRes-7-7 Punch List completion - Fouche Gap 9 3/15/2012 3/27/2012
Task BldDoc-7 Finalize As-Built drawings from A&E - Fouche Gap 7 3/28/2012 4/5/2012
Milestone SitDevComp-7 Site Development Complete - Fouche Gap 0 4/5/2012 4/5/2012
Phase CIV-3 Site Development Hillindale 220 6/3/2011 4/5/2012
Activity Civ-3-3 A&E - Hillindale 130 6/3/2011 12/1/2011
Milestone CivComp-3 A&E Complete - Hillindale 0 11/24/2011 11/24/2011
Activity CivSitPrep-3 Site Preparation -Hillindale 10 12/6/2011 12/19/2011
Task CivSitPrep-3-6 Light Clearing and Grubbing 1 12/7/2011 12/7/2011
Activity TowConst-3 Tower Construction - Hillindale 31 11/25/2011 1/6/2012
12/10/10 5/13
Milestone TowComp-3 Tower Complete - Hillindale 0 1/6/2012 1/6/2012
Activity Bldg-3 Site Components Installation - Hillindale 76 12/22/2011 4/5/2012
Task BldCln-3 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldPunRes-3-3 Punch List completion - Hillindale 9 3/15/2012 3/27/2012
Task BldDoc-3 Finalize As-Built drawings from A&E - Hillindale 7 3/28/2012 4/5/2012
Milestone SitDevComp-3 Site Development Complete - Hillindale 0 4/5/2012 4/5/2012
Phase CIV-5 Site Development Cave Springs 220 6/3/2011 4/5/2012
Activity Civ-5-5 A&E - Cave Springs 130 6/3/2011 12/1/2011
12/10/10 6/13
Milestone CivComp-5 A&E Complete - Cave Springs 0 11/24/2011 11/24/2011
Activity CivSitPrep-5 Site Preparation - Cave Springs 10 12/6/2011 12/19/2011
Activity TowConst-5 Tower Construction - Cave Springs 31 11/25/2011 1/6/2012
Milestone TowComp-5 Tower Complete - Cave Springs 0 1/6/2012 1/6/2012
Activity Bldg-5 Site Components Installation - Cave Springs 76 12/22/2011 4/5/2012
Task BldCln-5-5 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldWrkCom-5-8 Line Termination and Sweep Test 1 2/22/2012 2/22/2012
Task BldWrkCom-5 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/2/2012 3/2/2012
Task BldPunRes-5-5 Punch List with Floyd County 1 3/14/2012 3/14/2012
Task BldPunRes-5 Punch List completion - Cave Springs 9 3/15/2012 3/27/2012
Task BldDoc-5 Finalize As-Built drawings from A&E - Cave Springs 7 3/28/2012 4/5/2012
Milestone SitDevComp-5 Site Development Complete - Cave Springs 0 4/5/2012 4/5/2012
Phase CIV-8-8 Site Development Blossom Hill 128 6/3/2011 11/29/2011
12/10/10 7/13
Activity Civ-8 A&E - Blossom Hill 71 6/3/2011 9/9/2011
Task CivSur-8-9 Structural Analysis of Existing Tower 6 6/6/2011 6/13/2011
Task CivArch-8-8 Existing Tower Zoning App and Approval 20 7/7/2011 8/3/2011
Milestone CivComp-8 A&E Complete - Blossom Hill 0 9/9/2011 9/9/2011
Activity CivSitPrep-8-12 Site Preparation - Blossom Hill 14 9/14/2011 10/3/2011
Task CivSitPrep-8-10 Locate Existing Utilities 1 9/15/2011 9/15/2011
Task CivSitPrep-8-9 Pickup and Install Meterboard 3 9/16/2011 9/20/2011
Task CivSitPrep-8-8 Utility Hookup by Electric Co. 3 9/16/2011 9/20/2011
Task CivSitPrep-8 Tower Grounding 3 9/21/2011 9/23/2011
Milestone TowComp-8 Site Prep Complete - Blossom Hill 0 10/3/2011 10/3/2011
Activity Bldg-8 Site Components Installation - Blossom Hill 54 9/15/2011 11/29/2011
Task BldGrnd-8-15 Trench and Install Underground Power Conduits 3 9/21/2011 9/23/2011
Task BldCln-8 Conduit Inspection and Backfill 1 10/6/2011 10/6/2011
Task BldFndCnst-8 Excavate, Form, and Rebar Generator Foundation 1 10/10/2011 10/10/2011
Task BldConDel-8 Piping Inspection, Leakage Test, and Backfill 3 10/24/2011 10/26/2011
Task BldGrnd-8-11 Electrical Distribution within the Equipment Room 5 9/15/2011 9/21/2011
Task BldGrnd-8-10 Install Cable Trays 2 9/22/2011 9/23/2011
Task BldGrnd-8-9 Install Cable Entry Ports 2 9/26/2011 9/27/2011
Task BldGrnd-8-8 Install Internal Grounding 3 9/28/2011 9/30/2011
Task BldPunRes-8 Punch List completion - Blossom Hill 10 11/7/2011 11/18/2011
Task BldDoc-8 Finalize As-Built drawings from A&E - Blossom Hill 7 11/21/2011 11/29/2011
Milestone SitDevComp-8 Site Development Complete - Blossom Hill 0 11/29/2011 11/29/2011
Phase CIV-6-6 Site Development Rocky Mountain 134 6/3/2011 12/7/2011
Activity Civ-6 A&E - Rocky Mountain 89 6/3/2011 10/5/2011
Task CivArch-6 Existing Tower Zoning App and Approval 20 7/7/2011 8/3/2011
Milestone CivComp-6 A&E Complete - Rocky Mountain 0 10/5/2011 10/5/2011
Activity CivSitPrep-6-7 Site Preparation - Rocky Mountain 16 10/10/2011 10/31/2011
12/10/10 8/13
Task CivSitPrep-6 Compound Grading and Silt Fencing 3 10/11/2011 10/13/2011
Task AntRxInv6 Ship Antennas, Lines, and Accessories to the Site 5 10/14/2011 10/20/2011
Milestone TowComp-6 Site Prep - Rocky Mountain 0 10/31/2011 10/31/2011
Activity Bldg-6 Site Components Installation - Rocky Mountain 36 10/19/2011 12/7/2011
Task BldCln-6-6 Finish Grade and Gravel Compund 2 10/31/2011 11/1/2011
Task BldPunRes-6 Punch List completion - Rocky Mountain 10 11/15/2011 11/28/2011
Task BldDoc-6 Finalize As-Built drawings from A&E - Rocky Mountain 7 11/29/2011 12/7/2011
Milestone SitDevComp-6 Site Development Complete - Rocky Mountain 0 12/7/2011 12/7/2011
Phase CIV-2-2 Site Development Shannon AT&T 233 6/3/2011 4/24/2012
Activity Civ-2 A&E - Shannon AT&T 130 6/3/2011 12/1/2011
Task CivArch-2-3 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task BldDes-2 Design Tower 6 7/22/2011 7/29/2011
Task CivSitPerm-2-3 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-2 Electrical Permit App and Approval 10 11/11/2011 11/24/2011
Milestone CivComp-2 A&E Complete - Shannon AT&T 0 11/24/2011 11/24/2011
Activity CivSitPrep-2-6 Site Preparation - Shannon AT&T 6 12/6/2011 12/13/2011
Task CivSitPrep-2 Compound Grading and Silt Fencing 6 12/6/2011 12/13/2011
Activity TowConst-2 Tower Construction - Shannon AT&T 32 12/7/2011 1/19/2012
Task TowCnstShip-2-3 Ship Anchor Bolts and Base Plate to Site 4 12/7/2011 12/12/2011
Task TowCnstFndn-2-2 Drill, Rebar, and Pour Drilled Pier Foundation 7 12/16/2011 12/26/2011
Task TowCnstFndn-2 Foundation Inspection / Concrete Testing 1 12/23/2011 12/23/2011
Task TowCnstShip-2 Ship Tower to Site 4 12/30/2011 1/4/2012
Task TowCnstFAA-2-2 Notify FAA of Impending Tower Construction 1 1/2/2012 1/2/2012
Task TowAssem-2-2 Tower Assembly and Stacking 6 1/6/2012 1/13/2012
Task TowAssem-2 Tower Plumbness Testing 1 1/16/2012 1/16/2012
Task TowCnstFAA-2 Notify FAA of Tower Completion 1 1/16/2012 1/16/2012
Milestone TowComp-2 Tower Complete - Shannon AT&T 0 1/19/2012 1/19/2012
Activity Bldg-2 Site Components Installation - Shannon AT&T 82 1/2/2012 4/24/2012
Task BldUtilHU-2-2 Trench and Install Underground Power Conduits 5 1/2/2012 1/6/2012
12/10/10 9/13
Task BldUtilHU-2 Conduit Inspection and Backfill 1 1/9/2012 1/9/2012
Task BldConDel-2-8 Power Hookup 2 1/19/2012 1/20/2012
Task BldConDel-2-7 Framing and Drywall Construction of the Equipment Room 15 1/30/2012 2/17/2012
Task BldConDel-2-6 Electrical Distribution within the Equipment Room 10 2/20/2012 3/2/2012
Task BldConDel-2-5 Install Cable Trays 3 3/5/2012 3/7/2012
Task BldConDel-2-4 Install HVAC 4 3/8/2012 3/13/2012
Task BldConDel-2-3 Install Fire Suppression System 4 3/14/2012 3/19/2012
Task BldConDel-2-2 Install Cable Entry Port 2 3/20/2012 3/21/2012
Task BldConDel-2 Install Internal Grounding 3 3/22/2012 3/26/2012
Task BldCln-2-2 Finish Grade and Gravel Compund 2 2/27/2012 2/28/2012
Task BldWrkCom-2-5 Line Termination and Sweep Test 1 1/20/2012 1/20/2012
Task BldWrkCom-2 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/20/2012 3/20/2012
Task BldPunRes-2 Punch List completion - Shannon AT&T 10 4/2/2012 4/13/2012
Task BldDoc-2 Finalize As-Built drawings from A&E - Shannon AT&T 7 4/16/2012 4/24/2012
Milestone SitDevComp-2 Site Development Complete - Shannon AT&T 0 4/24/2012 4/24/2012
Phase CIV-9 Site Development Floyd 911 233 6/3/2011 4/24/2012
Activity Civ-9-9 A&E Floyd 911 60 6/3/2011 8/25/2011
Task CivArch-9 Existing Tower Zoning App and Approval 20 6/14/2011 7/11/2011
Milestone CivComp-9 A&E Complete - Floyd 911 0 8/22/2011 8/22/2011
Activity CivSitPrep-9 Site Preparation - Floyd 911 12 8/26/2011 9/12/2011
Task AntRxInv PS-9 Ship Antennas, Lines, and Accessories to the Site 5 8/26/2011 9/1/2011
Task AntRxInv PS-9-9 Install Antennas and Lines 4 9/7/2011 9/12/2011
Milestone TowComp-9 Site Prep - Floyd 911 0 9/12/2011 9/12/2011
Activity Bldg-9 Site Components Installation - Floyd 911 33 9/9/2011 10/25/2011
Task BldGrnd-9 Electrical Disribution within the Equipment Room 12 9/9/2011 9/26/2011
Task BldGrnd-9-9 Install Internal Grounding 3 9/27/2011 9/29/2011
Task BldPunRes-9-9 Punch List completion - Floyd 911 10 10/3/2011 10/14/2011
Task BldDoc-9 Finalize As-Built drawings from A&E - Floyd 911 7 10/17/2011 10/25/2011
Milestone SitDevComp-9 Site Development Complete - Floyd 911 0 10/25/2011 10/25/2011
Activity Civ-10 A&E - Backup EOC (MW Only) 36 8/3/2011 9/21/2011
Task CivNEPA-10 NEPA - Backup EOC (MW Only) 31 8/3/2011 9/14/2011
Task CivArch-10 Tower (or Rooftop) Structural and Mapping - Backup EOC (MW Onl 5 9/15/2011 9/21/2011
Milestone CivComp-10 A&E Complete - Backup EOC (MW Only) 0 9/21/2011 9/21/2011
Activity Civ-11 A&E - Dug Gap (MW Only for ISSI Connectivity) 190 8/3/2011 4/24/2012
Task CivNEPA-11 NEPA - Dug Gap (MW Only) 31 8/3/2011 9/14/2011
Task CivArch-11 Tower Structural and Mapping - Dug Gap (MW Only) 5 9/15/2011 9/21/2011
Milestone CivComp-11 A&E Complete - Dug Gap (MW Only) 0 9/21/2011 9/21/2011
Milestone CivComp-0 Architecture & Engineering Work Complete 0 11/24/2011 11/24/2011
12/10/10 10/13
Milestone SitDevCompAll-0 All Site Development Complete 0 4/24/2012 4/24/2012
Phase Inst-0 FNE Installation 34 2/21/2012 4/6/2012
Task FNERxInv-0 Receive and inventory FNE 15 2/21/2012 3/12/2012
Task InstFNE-MS Install Floyd County 911 Zone Core Site 15 3/13/2012 4/2/2012
Task InstFNE1 Install FNE Remote Mt Alto 3 3/15/2012 3/19/2012
Task InstFNE2 Install FNE Remote Shannon AT&T 5 4/2/2012 4/6/2012
Task InstFNE-3 Install FNE Remote Hillindale 3 3/15/2012 3/19/2012
Task InstFNE-4 Install FNE Remote Leonard Road 3 3/15/2012 3/19/2012
Task InstFNE-5 Install FNE Remote Cave Springs 3 3/15/2012 3/19/2012
Task InstFNE-6 Install FNE Remote Rocky Mtn 5 3/13/2012 3/19/2012
Task InstFNE-7 Install FNE Remote Fouche Gap 3 3/15/2012 3/19/2012
Task InstFNE-8 Install FNE Remote Blossom Hill 3 3/13/2012 3/15/2012
Task InstFNE-9 Install EMS FSA Alerting Locations (8) 4 2/23/2012 2/28/2012
Task InstFNE-10 Install Fire FSA Alerting Locations (11) 6 2/29/2012 3/7/2012
Milestone FNECpt-0 FNE Install Complete 0 4/6/2012 4/6/2012
Phase Cnsl-0 Console and Control Station Installation 231 5/31/2011 4/17/2012
Activity Cnsl-1 Console Installation - Floyd 911 87 12/2/2011 4/2/2012
Task CnslCon-1 Test Connectivity - Floyd 911 1 12/2/2011 12/2/2011
Task CnslInst-1 Install MCC7500 Consoles (qty 6) - Floyd 911 10 3/13/2012 3/26/2012
Task CnslInst-1-1 Install GenWatch3 De-trunked Logger - Floyd 911 2 3/27/2012 3/28/2012
Task CnslInst-1-2 Install Control Stations - Floyd 911 2 3/29/2012 3/30/2012
Task CnslInst-1-3 Install Fire Paging Control Station - Floyd 911 1 4/2/2012 4/2/2012
Milestone CnslComp-1 Console Complete - Floyd 911 0 4/2/2012 4/2/2012
Activity Cnsl-2 Console Installation - Backup EOC 223 5/31/2011 4/5/2012
Task CnslCon-2-2 Notice to Proceed - Backup EOC 1 10/4/2011 10/4/2011
Task CnslCon-2 Test Connectivity - Backup EOC 1 10/5/2011 10/5/2011
Task CnslInst-2-1 Install MCC7500 Consoles (qty 5) - Backup EOC 5 3/27/2012 4/2/2012
Task CnslInst-2-1-1 Coordination of CAD / 911 Installation - Backup EOC 5 5/31/2011 6/6/2011
Task CnslInst-2-2 Install Control Stations - Backup EOC 2 4/3/2012 4/4/2012
Task CnslInst-2-3 Install Fire Paging Control Station - Backup EOC 1 4/5/2012 4/5/2012
Milestone CnslComp-2 Console Complete - Backup EOC 0 4/5/2012 4/5/2012
Activity Cnsl-3 Console Installation - Jail 6 4/3/2012 4/10/2012
Task CnslCon-3 Test Connectivity - Jail 1 4/3/2012 4/3/2012
Task CnslInst-3-1 Install MIP5000 Console (qty 1) - Jail 1 4/4/2012 4/4/2012
Task CnslInst-3-2 Install Control Stations - Jail 1 4/5/2012 4/5/2012
Task CnslInst-3-3 Install 800MHz P25 Repeater - Jail 1 4/6/2012 4/6/2012
Task CnslInst-3-4 Remove Existing Repeater - Jail 1 4/9/2012 4/9/2012
Task CnslInst-3-5 Install Digital Desksets - Jail 2 4/9/2012 4/10/2012
Milestone CnslComp-3 Console Complete - Jail 0 4/10/2012 4/10/2012
Activity Cnsl-4 Installation - Sheriffs Office / Courthouse 2 4/11/2012 4/12/2012
Task CnslInst-4 Install Consolettes and Desksets - Sheriffs Office / Courthouse 2 4/11/2012 4/12/2012
Milestone CnslComp-4 Install Complete - Sheriffs Office / Courthouse 0 4/12/2012 4/12/2012
Activity Cnsl-5 Installation - Prison 3 4/13/2012 4/17/2012
Task CnslInst-5-5 Install Consolettes and Desksets - Prison 2 4/13/2012 4/16/2012
Task CnslInst-5 Install 800MHz P25 Repeater - Prison 1 4/17/2012 4/17/2012
Milestone CnslComp-5 Install Complete - Prison 0 4/17/2012 4/17/2012
Milestone CnslInstComp-0 Console Installations Complete 0 4/17/2012 4/17/2012
Phase MW-0 Microwave Installation 168 8/26/2011 4/17/2012
Task MWFrq-0 MW Frequency Coordination 45 8/26/2011 10/27/2011
Task MWInst-1 Install MW - Mt Alto - Loop 5 1/26/2012 2/1/2012
Task MWInst-2 Install MW - Shannon AT&T - Loop 5 1/20/2012 1/26/2012
Task MWInst-3 Install MW - Hillindale - Loop 5 1/9/2012 1/13/2012
Task MWInst-4 Install MW - Leonard - Loop 5 1/26/2012 2/1/2012
Task MWInst-5 Install MW - Cave Springs - Loop 5 1/9/2012 1/13/2012
Task MWInst-6 Install MW - Rocky Mtn - Spur 5 1/2/2012 1/6/2012
12/10/10 11/13
Task MWInst-7 Install MW - Fouche Gap - Loop 5 1/26/2012 2/1/2012
Task MWInst-8 Install MW - Blossom Hill - Spur 5 2/2/2012 2/8/2012
Task MWInst-9 Install MW - Floyd 911 - Loop 5 1/9/2012 1/13/2012
Task MWInst-10 Install MW - Backup EOC - Spur 5 1/2/2012 1/6/2012
Task MWInst-11 Install MW - Dug Gap - Spur (for ISSI connectivity) 5 1/2/2012 1/6/2012
Task MWPathOpt-0 Microwave Path Alignment / optimization 7 2/9/2012 2/17/2012
Task ATPMW-0 Microwave ATP 5 2/20/2012 2/24/2012
Milestone MWInstComp-0 Microwave Installation Complete 0 2/24/2012 2/24/2012
Milestone InstAccpt-0 System FNE installation complete (FNE A&L and MW) 0 4/17/2012 4/17/2012
Phase SysOpt-0 System Optimization 181 12/7/2011 8/15/2012
Task SysLnkVer-0 Link Verification 9 2/27/2012 3/8/2012
Task SysOptFNE-0 Optimize System FNE 35 4/18/2012 6/5/2012
Activity Trng Training 181 12/7/2011 8/15/2012
Task TrngDev Finalize Training Plan 62 12/7/2011 3/1/2012
Task TrngMatDev Develop Training Material 55 3/2/2012 5/17/2012
Task TrngSched Schedule Training 5 3/2/2012 3/8/2012
Task TrngSystem Console Supervisor Training 1 8/8/2012 8/8/2012
Task TrngSystem-3 Console Operator Training 2 8/9/2012 8/10/2012
Task TrngSystem-2 Jail DispatchTraining 1 8/13/2012 8/13/2012
Task TrngSystem-1 Police Subscriber Training 16 6/27/2012 7/18/2012
Task TrngSystem-0 Fire Subscriber Training 3 7/19/2012 7/23/2012
Task TrngSystem-0-0 EMS Subscriber Training 3 7/24/2012 7/26/2012
Task TrngSystem-0-0-0 Non-Public Safety Subscriber Training 14 7/27/2012 8/15/2012
Milestone SysOptComp-0 Optimization and Training Complete 0 8/15/2012 8/15/2012
Phase ATP-0 Audit and Acceptance Testing 141 2/1/2012 8/15/2012
Task ATPR56Cnt-0 R-56 Control Sites 3 4/25/2012 4/27/2012
Task ATPR56RF-0 R-56 RF Sites 15 4/9/2012 4/27/2012
Task ATPR56PL-0 R-56 Punchlist Resolution 10 4/30/2012 5/11/2012
Task ATPEqp-0 Perform Equipment and Functional System Testing 10 6/6/2012 6/19/2012
Task ATPCovEqp Secure and Configure Test Sets 15 5/23/2012 6/12/2012
Task ATPCovProc Generate CATP procedures 30 2/1/2012 3/13/2012
Task ATPCovMps Generate Grid Maps 60 3/14/2012 6/5/2012
Task ATPCovATP Perform In-Building Test CATP ** 12 6/20/2012 7/5/2012
Task AntRxInv PS-0!-8 BDA Analysis, Installation, and Testing 25 6/27/2012 7/31/2012
Task ATPCovATP-0 Perform Drive Test CATP ** 7 7/6/2012 7/16/2012
Task ATPCovDoc Document CATP Results 10 8/1/2012 8/14/2012
Milestone ATPCovAcc CATP Acceptance 0 8/14/2012 8/14/2012
Milestone ATPAcc-0 SATP Acceptance 0 8/15/2012 8/15/2012
Phase Subb Subscriber Installation 60 4/4/2012 6/26/2012
Task SubMobb Mobile Install and Program 60 4/4/2012 6/26/2012
Task SubPortb Portable Program and Distribute 60 4/4/2012 6/26/2012
Milestone SubAccb Subscriber Acceptance 0 6/26/2012 6/26/2012
Phase Fnl-0-0-0 Project Finalization 209 1/18/2012 11/5/2012
Activity Cutover Cut-Over 164 1/18/2012 9/3/2012
Task CutOverPln Cutover Plan Development 60 1/18/2012 4/10/2012
Task CutOverCust Customer Agreement on Cutover 45 4/11/2012 6/12/2012
Task FnlCutOver-0 Cutover FNE 3 8/23/2012 8/27/2012
Task FnlCutOver-0-1 Cutover Dispatch 2 8/28/2012 8/29/2012
Task FnlCutOver-0-0 Cutover Police Subscribers 1 8/30/2012 8/30/2012
Task FnlCutOver-0-0-2 Cutover Fire Subscribers 1 8/31/2012 8/31/2012
Task FnlCutOver-0-0-1 Cutover EMS Subscribers 1 9/3/2012 9/3/2012
Task FnlCutOver-0-0-0 Cutover Non-Public Safety Subscribers 1 8/16/2012 8/16/2012
Milestone CutoverComp-0 Cutover Complete 0 9/3/2012 9/3/2012
Activity 03.05-5 System Testing & Cutover Milestones 2 9/4/2012 9/5/2012
Task FnlCutOver-0-!-0 Move Police MTR2000 Repeater to Mt Alto 1 9/4/2012 9/4/2012
12/10/10 12/13
Task FnlCutOver-0-!-1 Decommission Old Fire Paging Repeater 1 9/5/2012 9/5/2012
Task FnlInspCust-0 Final Inspection w/Customer 10 9/4/2012 9/17/2012
Task FnlPunRes-0 Punchlist Resolution 15 9/18/2012 10/8/2012
Task FnlDoc-0 Finalize Documentation ** 45 8/16/2012 10/17/2012
Task FnlSerTran-0 Transition Service/PTC 3 10/18/2012 10/22/2012
Milestone FnlAccpt-0 Final Acceptance 0 10/22/2012 10/22/2012
Task TrngSupp-0 Supplemental SystemTraining ** 10 10/23/2012 11/5/2012
12/10/10 13/13
Section 10. Training
10.1 Overview
Motorola has proposed a training plan for Floyd County’s consideration that addresses
the requirements identified in the RFP. The courses, which are listed below, will
prepare the County’s personnel to manage and operate the system and provide various
levels of maintenance directly, should that be the desired direction for Floyd County
after System Warranty.
Motorola's Worldwide Learning Services (WLS) organization dedicates itself to
offering a comprehensive training plan to enable Floyd County personnel to realize
the full potential of the County’s new ASTRO 25 radio system. From sophisticated
training needs analysis to ongoing training throughout the life cycle of your system,
WLS can help ensure that the County’s investment in training today is an investment
for its future.
WLS' training methodology includes knowledgeable instructors, well-designed
courseware, lab activities, and system hardware and software integrated with detailed
system documentation. This methodology is based upon several key criteria:
♦ Course design is driven by an analysis of learner needs and focuses on how-to
rather than theory.
♦ Learning objectives are based upon what learners need to accomplish on the job
and focus on specific applications.
♦ Hands-on lab opportunities using customer-specific job aids are incorporated into
training to maximize the transfer of skills to the job and the retention/reuse of
information.
Motorola offers both train-the-trainer and end-user training. Students can attend
training at one of WLS’ training centers or instructors can come to your site. In
conjunction with or in addition to instructor-led training, WLS can provide self-
study/e-learning programs in which students follow a computer-based training module
on CD-ROM or other media.
10.2 Courses Proposed

In the process of assessing your training needs, Motorola has identified the following
course(s) that are necessary to achieve your training goals. Inserted within the matrix
are course description files for your review or printing.

RFP# 101216
December 16, 2010
Training 10-1
While the standard courses are encouraged, the class outline may be tailored for your
quotation. Thus, the outline(s) below may not exactly match your quoted class length
and content.
10.2.1 System Administrator
System Administrator
Course Target Audience No. of Duration Location Date No. of
Sessions (days) Attendees
Bridging the Knowledge System NA 6-12 Online Prior to 6
Gap for ASTRO 25-System Managers Hours Rome, GA Overview
Administrator Course Part 1
(Self-Paced Online)
Course Synopsis:
This five-module course is designed to bring Administrators from different technical backgrounds and experience levels to a common
starting point for the ASTRO 25 curriculum. This course provides seven modules from the basic concepts of radio communication
systems and computer networking features, through the evolution that led to the ASTRO 25 trunking system’s architecture.
ASTRO 25 IV&D System System 1 5 Rome, GA Post 6

Networking Managers and Installation
IT Technicians and Prior
(Instructor Led)
to
Managing
Course Synopsis:
This course provides the technician with the necessary networking information required for understanding the Network Transport
subsystem components installed in an ASTRO 25 Release 6.x/7.x communications system. The course includes familiarization with
basic networking concepts and the networking components deployed throughout the system.
ASTRO 25 IV&D Trunking System NA 6-12 Online Prior to 6

with M Core System Managers and Hours Rome, GA Part 2
Overview Technicians
Part 1 of 3
(Self-Paced Online)
Course Synopsis:
The ASTRO 25 Integrated Voice and Data System Overview course is intended to provide an overview of the ASTRO 25 System in
order to familiarize the various audiences with the overall system capabilities, components, features, and benefits.

RFP# 101216
December 16, 2010
10-2 Training
ASTRO 25 IV&D System NA 6-12 Online Prior to 6

Introduction to Radio Managers and Hours Rome, GA Part 3
System Administrator Technicians
Workshop
Part 2 of 3
(Self-Paced Online
Course Synopsis:
This course provides an introduction to the Motorola Radio System Management Applications. This course is a Prerequisite to Radio
System Administrator.
ASTRO 25 IV&D Radio System 1 5 Rome, GA Post 6

System Administrator Managers Installation
Workshop and Prior
Part 3 of 3 to
(Instructor Led) Managing
Course Synopsis:
This workshop covers management functions for an ASTRO 25 Integrated Voice and Data (IV&D) System. Learning activities in this
document-based training course focus on how to use the different ASTRO 25 IV&D System Management applications. Participants will
be provided with an opportunity to discuss how to structure their organization and personnel for optimal ASTRO 25 IV&D system use..
ASTRO 25 IV&D System NA 4 hours Rome, GA Post 6

Telephone Interconnect Managers and Installation
Technicians and Prior
(Self-Paced Online) to
Managing
Course Synopsis:
This workshop describes the functionality of – and the hardware and software associated with – the Telephone Interconnect feature in
the ASTRO 25 Integrated Voice & Data (IV&D) System.
ASTRO 25 IV&D ISSI.1 System NA 2-4 hours Rome, GA Post 6
Network Gateway Managers and Installation
Overview Technicians and Prior
(Self-Paced Online) to
Managing
Course Synopsis:
The ASTRO 25 IV&D ISSI.1 Network Gateway Overview is a self study course intended to provide information related to the operation
and functionality of, including the hardware and software associated with, the ISSI.1 Network Gateway. This course covers the ISSI.1
Network Gateway operation in detail, including tasks, operation, theory, and troubleshooting; while providing an overview of the
installation and configuration of the ISSI Network Gateway components.
Point to Point / Point to System NA 4-6 Hours On-line TBD 6
Multi Point Overview Managers and Rome, GA
(On-line; Self-paced) Technicians
Course #: WEE1604
Course Synopsis:
The Wireless Network Solutions Overview course teaches basic concepts, skills, and terminology surrounding Motorola Point-to-Point
products. The course focuses on radio frequency basics, PTP technology, differentiators, licensed band applications, and case studies.

RFP# 101216
December 16, 2010
Training 10-3
Tailored System 1 2 days Rome, GA 90 days Up to 12

Managers after
System Administrator System
Refresher Acceptance
(Instructor Led)
Course Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce System
Administrator training.
10.2.2 Technical Maintenance Training
Technician Maintenance Training

ASTRO 25 IV&D M Core Master Site 1 5 Rome, GA Prior to Up to 6

Workshop Technicians Maintaining
(Instructor-led)
Course Synopsis:
This workshop teaches advanced troubleshooting skills and best practices for the ASTRO 25 Integrated Voice and Data System Release
7.x. The workshop focuses on gathering and analyzing system information to implement the appropriate actions that return a system to
full operational status.
ASTRO 25 IV&D Simulcast 1 3 Rome, GA Prior to Up to 6

IP Based Digital Simulcast Technicians Maintaining
Workshop
(Instructor-led)
Course Synopsis:
This workshop describes the components in the ASTRO 25 Integrated Voice and Data System Digital Simulcast subsystem. This course
presents how the Simulcast subsystem operates and explains the tools and methods available for troubleshooting components within the
Simulcast subsystem.
ASTRO 25 IV&D Remote Site 1 3 Rome, GA Prior to Up to 6

GTR 8000 Repeater Site Technicians Maintaining
Workshop
(Instructor-led)
Course Synopsis:
This workshop describes the components in the ASTRO 25 Integrated Voice and Data System GTR 8000 site subsystem. This course
presents how the GTR 8000 site subsystem operates and explains the tools and methods available for troubleshooting components
within the repeater site subsystem.
MCC7500 Dispatch Console 1 4 Rome, GA Prior to Up to 6
Console Technicians Maintaining
(Instructor-led)
Course Synopsis:
This course familiarizes technicians in troubleshooting/repair functions, operating procedures, and hardware/software applications for the
MCC 7500 console. The focus is on a detailed discussion of console hardware and hands-on activities with the installation and
configuration of the MCC 7500 console.

RFP# 101216
December 16, 2010
10-4 Training
Technician Maintenance Training
MOSCAD Maintenance Technical 1 5 Rome, GA Prior to Up to 6

and Programming System Maintaining
(Instructor Led) Managers
Course Synopsis:
This course provides System Designers, Technicians and System Managers general programming and development skills of MOSCAD
(Network Fault Management) systems. This class will be provided using Motorola Lab SDM3000 and NFM-XC RTUs. A Training manual
is provided and will be supplied to each participant.
APX CPS Radio Radio 1 2 Rome, GA Prior to Up to 6

Programming and Programmers / Subscriber
Template Building System Program-
(Instructor Led) Managers ming
Course Synopsis:
This course may be modified and tailored to the customer’s features. It will introduce the student to CPS installation, assembling
hardware, CPS menu structure, Software configuration, and normal features used in Analog Conventional and Trunked systems.
Tutorials will guide the student through the CPS menus and screens. Adequate time will be available for hands-on practice using a
variety of scenarios. It will also demonstrate how to create templates used to program subscribers in a system.
APX Technical Subscriber Radio 1 5 Rome, GA Prior to Up to 6

Academy Programmers / Maintaining
(Note: APX CPS is System
Prerequisite) Managers
(Instructor Led)
Course Synopsis:
This five-day course focuses on the knowledge required for a 2-way Radio Technician working in a communication environment or using
the family of APX radios in the field. The course is specifically designed to provide significant amounts of hands-on, scenario based labs
around configuration and troubleshooting. Key Loading and Management, Encryption, Over-The Air Programming and Mobile Radio
Installation are some of the topics that will be covered in detail for both mobile and portable radios
It is recommended that the students bring their lap top computers for all System
Manager and Technician classes. One set of hard copy manuals will be provided for
the class. Students will receive their manuals in CD-ROM format and hard copy
participant guides.

RFP# 101216
December 16, 2010
Training 10-5
10.2.3 Console End User Training
Console End User Training
Course Target Audience No. of Duration Location Date No. of Attendees
Sessions (days)
MCC7500 Console System 1 1 Rome, GA Prior to 6

Supervisors Administrators Cut-over
(Instructor-led) and Dispatch (8 hr (6 per session)
6 training consoles (2x1 Ratio) Supervisors session)
Course Synopsis:
This course provides participants with the knowledge and skills to manage and utilize the MCC 7500 console administrator functions.
Through facilitation and hands-on activities, the participant learns how to customize the console screens. This session also includes the
Operator course below.
MCC7500 Console Console 4 2 Rome, GA Prior to Up to 30

Operators Operators Cut-over (6-7 per session)
(Instructor-led) (4 hr
6 training consoles (2x1 Ratio) sessions)
Course Synopsis:
This course provides participants with an introduction to the dispatch console, its basic operation and tailored job aids which will be
available for assistance in operation. Through facilitation and hands-on activities, the user learns how to perform common tasks associated
with the console operation.
MIP5000 Console Operator Jail 2 1 Rome, GA Prior to Up to 4

(Instructor-led) Dispatchers Cut-over
1 training console (2x1 Ratio) (4 hr (2 per)
sessions)
Operator Course Synopsis:

This course will provide a dispatcher with the necessary skills to quickly access and activate the dispatch features of the MIP 5000 console.
The classroom experience is a mix of instructor-led facilitation and hands-on activities.
MCC7500 Console Console 4 1 Rome, GA 90 days Up to 30

Operator Refresher Operators after (7-8 per session)
(Instructor-led) (2 hr System
sessions) Accep-
6 training consoles (2x1 Ratio)
tance
Course Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce console training.

RFP# 101216
December 16, 2010
10-6 Training
Optional – Console Cutover Support
Sessions (days)
MCC7500 Console Cutover Console 1 Trainer 3 Rome, GA During NA

Support On the Job Training Operators / (2 hours st
(1 3 days
(OTJT) Supervisors before and Go-Live
of “Go
after each Live”)
One (1) Trainer shift
(4 hours per shift) change)
Course Synopsis:
This service will provide 1 CENTRACOM Trainer at the COM Center for 3 days the first three days of go-live. The trainer will offer guidance
during system cutover, providing assistance for approximately 12 hours in each 24-hour period (4 hours at each shift change).
10.2.4 Radio End User Training
Radio End User Training

Sessions (days)
APX Mobile and Portable Police Users 32 16 Rome, GA Prior to Up to 490

User Training (4 hr (15-16 per)
Cut-over
(Instructor-led) sessions)
APX Mobile and Portable Fire Users 6 3 Rome, GA Prior to Up to 90

Cut-over
APX Mobile and Portable EMS Users 5 2.5 Rome, GA Prior to Up to 70

Cut-over
Course Synopsis:
This course provides APX mobile and portable radio users with an introduction to their new ASTRO Trunked System, the radios, basic
operation and tailored job aids available for assistance in operation. The learning experience is a mix of facilitation and hands-on activities
to help users perform common tasks associated with their radio operation. Segmentation between user groups (i.e. Police, Fire/EMS,
Public Service) is encouraged to help focus instruction on the specific operational issues of the individual user group.
XTL/XTS Mobile and Non-Public 28 14 Rome, GA Prior to Up to 430

Portable User Training Safety Users (4 hr (15-16 per)
Cut-over
Course Synopsis:
This course provides the XTL/XTS mobile and portable radio users with an introduction to their new ASTRO Trunked System, the radios,
basic operation and tailored job aids available for assistance in operation. The learning experience is a mix of facilitation and hands-on
activities to help users perform common tasks associated with their radio operation. Segmentation between user groups (i.e. Police,
Fire/EMS, Public Service) is encouraged to help focus instruction on the specific operational issues of the individual user group.
APX Mobile and Portable Police, Fire and 4 2 Rome, GA 90 days 60

User Refresher EMS Trainers after
(4 hr (15 per)
System
Accep-
tance
Course Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce APX training

RFP# 101216
December 16, 2010
Training 10-7
XTL/XTS Mobile and Non-Public 2 1 Rome, GA 90 days 30
Portable User Refresher Safety Trainers after
(4 hr (15 per)
System
Accep-
tance
Course Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce APX training
Optional - Radio Train-the-Trainers Training

Sessions (days)
APX Mobile and Portable Police Trainers 1 1 Rome, GA Prior to Up to 15

Train-the-Trainers (8 hr Cut-over
(Instructor-led) session)
APX Mobile and Portable Fire Trainers 1 1 Rome, GA Prior to Up to 15

APX Mobile and Portable EMS Trainers 1 1 Rome, GA Prior to Up to 15

Course Synopsis:
These courses are designed to teach the customer how to operate the APX radios with the features programmed. In addition, the
customer will be taught how to use Motorola Interactive End User Toolkits (iEUTK) to customize their end user training presentations for
individual agencies. Segmentation between user groups (i.e. Police, Fire/EMS, Public Service) is encouraged to help focus instruction on
the specific operational issues of the individual user group.
XTL/XTS Mobile and Non-Public 1 1 Rome, GA Prior to Up to 15
Portable Train-the-Trainers Safety Trainers (8 hr Cut-over
Course Synopsis:
These courses are designed to teach the customer how to operate the XTL/XTS radios with the features programmed. In addition, the
customer will be taught how to use Motorola Interactive End User Toolkits (iEUTK) to customize their end user training presentations for
individual agencies. Segmentation between user groups (i.e. Police, Fire/EMS, Public Service) is encouraged to help focus instruction on
the specific operational issues of the individual user group.

RFP# 101216
December 16, 2010
10-8 Training
The Interactive End User
Tool Kit (iEUTK) is a
revolutionary knowledge
transfer tool designed to
accelerate learning. Using
the iEUTK allows trainers
to customize operator
training to match unique
button, feature
programming, and displays
provided in the system.
Each iEUTK is user
friendly and menu driven.
The home page in every
iEUTK provides excellent
navigation to the multiple
areas of interest for the
specific communication
device. Operators select
“Getting Started” to view a
highly informative video
overview that helps build
solid foundational
knowledge and quickly
brings users up to speed on We use our iEUTK to produce PowerPoint™ presentations so that
the operational theory of students can have self-paced training on any PC with Microsoft
Office™ .
their specific device. The
tailored materials are
developed on-site using tool kits that allow users to modify training materials when
radio or console features change. Personnel are taught how to maneuver through and
tailor the iEUTK screens. The tailored selections are saved to an electronic file that
the Motorola training team sends to the printer to develop the training materials. The
trainers use the iEUTK to generate their instructor guides, incorporating standard
operating procedures, notes, and reminders. This dynamic tool allows the customer to
generate training materials on an as-needed basis depicting current features and
functionality.

RFP# 101216
December 16, 2010
Training 10-9
10.3 Course Descriptions
10.3.1 Bridging the Knowledge Gap for ASTRO 25-System
Administrator Course
Duration
6-12 hours
Delivery Method
Online Self Paced
Course Synopsis:
This five-module course is designed to bring Administrators from different technical
backgrounds and experience levels to a common starting point for the ASTRO 25
curriculum. This course provides seven modules from the basic concepts of radio
communication systems and computer networking features, through the evolution that
led to the ASTRO 25 trunking system’s architecture.
Audience
This is targeted for System Administrators and other ASTRO 25 system users who are
new to trunked radio systems. Also those with experience in non-IP-based radio
systems like SmartNet and SmartZone
Course Objectives
Course material is designed to enable you to:
♦ Identify different communication concepts using representative block diagrams of
the respective systems
♦ Compare radio system communication concepts using representative block
diagrams of the respective systems
♦ Compare how voice and data, information flows though different radio
communication systems types and how the signaling information controls that
flow of information
♦ Describe the features of each radio communication system in terms of advantages
and disadvantages
♦ Explain the Trunked Radio System Concepts
Prerequisites
None
Course Outline
♦ Trunked Radio System
♦ Wide Area Trunked System
♦ Packet Switched Systems-ASTRO 25 Trunking
♦ Data
♦ Radio Call Features

RFP# 101216
December 16, 2010
10-10 Training
10.3.2 ASTRO 25 IV&D System Networking (w/labs)
Duration
5 Days
Delivery Method
Instructor-led
Target Audience
Technical system managers, technicians, engineers
Course Synopsis
This course provides the technician with the necessary networking information
required for understanding the Network Transport subsystem components installed in
an ASTRO 25 IV&D communications system. The course includes familiarization
with basic networking concepts and the networking components deployed throughout
the system.
Required Pre-Work
None
Required Lab Equipment
Items required for a single lab position with two participants:
♦ One Motorola router (model number GGM8000, S2500, S6000 or S4000)
♦ One Hewlett Packard Procurve switch (model number 2610-24, 2626 or 2524)
♦ Two RJ-45 network cables
♦ One DB9 to DB9 null modem cable (connects PC to console connector on switch
and router)
♦ One DB9 to RJ-45 null modem cable (only applies to the 2610 switches)
♦ A sufficient number of power cords and power strips
♦ One PC or laptop with a login account that has the authority to change the IP
address, add a TFTP file transfer program (3CDaemon) and execute a TFTP file
transfer.
NOTE: the total equipment required is dependant on the number of participants; i.e.
twelve participants would require six sets of equipment.
Recommended Prerequisites
None
Course Objectives
Upon Completion, the Participant Will Be Able To:
♦ Understand basic networking concepts

RFP# 101216
December 16, 2010
Training 10-11
♦ Describe the various Transport network subsystem components
♦ Define the LAN topologies for each system
♦ Define the WAN topologies for each system
♦ Identify the expanse of Network Management across each system
♦ Discuss HP Switch, and Motorola Series Router configurations
♦ Describe and Perform the backup/restore procedures for the HP Switch and
Motorola Series Routers in the ASTRO 25 system
Course Outline
I. Basic Networking Concepts
A. Terminology and Acronyms
B. LANS and WANS
C. Basic Protocols
D. Network troubleshooting commands
II. ASTRO 25 Network Transport Subsystem
A. Call Processing
1. Block diagram description of how a call travels through the system
2. Identification and isolation of the network components
B. Network Components
1. HP Switches—description and location in the network
a) Menu-Driven Configuration
b) Web-Based Configuration
2. Cooperative WAN Routing—description and location in the network
3. Motorola Series Routers—description and location in the network
a) Command Line Interface Configuration
b) Menu-Driven Configuration
c) Web-Based Configuration
4. Router Manager -- location and application identification
C. Network Concepts
1. Identify the LAN portion(s) of the network
2. Identify the LAN Protocols and describe where they are present in the
network
3. Identify the WAN portion(s) of the network
4. Identify the WAN Protocols and describe where they are present in the
network
D. Hands-On Practice
1. Backup and Restore HP Switch Configurations
2. Backup and Restore Motorola Series Router Configurations
3. Create router boot configuration file
4. Flash routers with new operating system

RFP# 101216
December 16, 2010
10-12 Training
10.3.3 ASTRO 25 IV&D Trunked System Overview (M Core still
in development)
Duration
12 hours
Delivery Method
Online/Self-Paced
Target Audience
System Managers, Technical System Managers, System Technicians, and other
Application Users
Course Synopsis
The ASTRO 25 Integrated Voice and Data System Overview course is intended to
provide an overview of the ASTRO 25 System in order to familiarize the various
audiences with the overall system capabilities, components, features, and benefits.
Prerequisites
Completion of the following courses or equivalent experience:
♦ Bridging the Knowledge Gap for ASTRO 25
OR
♦ Bridging the Knowledge Gap for ASTRO 25: System Administrators
♦ Networking Essential in Communication Equipment
♦ Advanced Networking in Motorola Communications Equipment or the 5-Day field
version
Course Objectives
After completing this course, the student will be able to do the following:
♦ Explain the purpose of the ASTRO 25 IV&D System.
♦ List and describe the ASTRO 25 system features and capabilities.
♦ Describe the ASTRO 25 system subsystems and their respective functions.
♦ List the system and software tools.
♦ Identify ASTRO 25 system compatible end-user devices.
Course Outline
I. Multiple Zone Trunking Systems

A. Definitions
B. Site Statuses
C. Information Types
D. A25 Repeater Site
E. A25 Repeater Expandable Site Subsystem

RFP# 101216
December 16, 2010
Training 10-13
F. High Performance Data
G. Simulcast Site
H. Master Site
II. Voice Processing
A. Turning on the radio
B. Making a call
C. Information paths
III. Data Processing
A. 9600 BPS
B. High Performance Data
IV. Mobility Management
A. Affiliation Registration Details
B. Roaming
C. Out of Range
D. Scan in Multiple Zone Trunking Systems
V. Servers and Databases
A. Servers
B. Databases
C. Backups
10.3.4 ASTRO 25 IV&D Introduction to Radio System

Administration
Duration
12 hours
Delivery Method
Online; Recorded
Course Synopsis:
This virtual, interactive course provides a high-level preview of the Motorola Radio
System Management applications. This course is a prerequisite to the Radio System
Administration workshop.
Audience
System Managers, Technical System Managers, System Technicians, and other
Application Users
Course Objectives
♦ Become familiar with the following ASTRO 25 IV&D Radio System Management
applications:
System Profile
Zone Profile
ZoneWatch
ATIA Log Viewer
Unified Event Manager (UEM)

RFP# 101216
December 16, 2010
10-14 Training
Affiliation Display
Radio Control Manager (RCM)
RCM Reports
Historical Reports
Dynamic Reports
User Configuration Manager (UCM)
Zone Configuration Manager (ZCM)
Unified Network Configurator (UNC)
Configuration/Service Software (CSS)
♦ Acquire base knowledge of the overall System Management functions, their
purposes, and an introduction to basic navigation and use of the Radio System
Management applications
♦ Ability to see and ask questions about the common operations allowed by the
Radio System Management applications
Prerequisites
♦ Completion of ASTRO 25 IV&D Trunked System Overview with a passing score
on the post test
®
♦ Completion of Bridging the Knowledge Gap for ASTRO 25 OR Bridging the
Knowledge Gap for ASTRO 25: System Administrators
Computer Requirements
♦ Windows compatible workstation with XP or later operating system
Course Outline
I. Getting Ready
A. WebEx Interface Familiarization
B. Presentation of Objectives
II. Introduction
A. List of Applications
III. Demonstration of Management Applications
A. System Profile
B. Zone Profile
C. ZoneWatch
D. ATIA Log Viewer
E. Unified Event Manager (UEM)
F. Affiliation Display
G. Radio Control Manager (RCM)
H. Reports
a. RCM and Historical Reports
b. Dynamic Reports
c. UCM, ZCM, and UNC Reports

RFP# 101216
December 16, 2010
Training 10-15
I. User Configuration Manager (UCM)
J. Zone Configuration Manager (ZCM)
K. Unified Network Configurator (UNC)
L. Configuration/Service Software (CSS)
10.3.5 ASTRO 25 IV&D Radio System Administration Workshop

Duration:
5 Days
Delivery Method
Instructor-led
Course Overview
This workshop covers administrator functions for an ASTRO 25 Integrated Voice and
Data (IV&D) System. Learning activities in this document-based training course focus
on how to use the different ASTRO 25 IV&D System Management applications.
Participants will be provided with an opportunity to discuss how to structure their
organization and personnel for optimal ASTRO 25 IV&D system use.
Audience
System Administrators, Technical System Administrators, System Technicians, and
other Application Users
Objectives
♦ Describe the relationship between radio programming, console administration and
system management, and the impact of this relationship on system planning
♦ List the network management tools applicable at each phase of the system life
cycle
♦ Use the report and real-time data to monitor performance and make adjustments
necessary to maintain acceptable system performance levels
♦ Identify the advantages and disadvantages of options available for the
configuration of system infrastructure and user parameters
Prerequisites
♦ Completion of ASTRO 25 IV&D Trunked System Overview (ACS78200-E) with
a passing score on the post test
♦ Completion of ASTRO 25 IV&D Introduction to Radio System Administration
(ACS78201-V)
♦ Completion of the following courses or equivalent experience:
Bridging the Knowledge Gap for ASTRO 25 – System Administrators
(ACT101-E)
Networking Essential in Communication Equipment (NST762)
Advanced Networking in Motorola Communications Equipment (NWT003) or 5
day field course

RFP# 101216
December 16, 2010
10-16 Training
N/A
Course Outline
I. Course Introduction
II. Basic Concepts of Radio System Administration
A. Why Did They Do it That Way?
B. Radio Programming vs. System Management
C. List of Management Applications
III. Operation and Optimization
A. License Sharing
B. Live Monitoring of the System
C. Report Generation
D. Network Maintenance Tools
IV. Configuration
A. Configuration Process and Tools
B. Adding Radios and Talkgroups to the System
C. Editing Existing Records in UCM
D. Setting System-Level Parameters
E. Creating Managers and Controlling Access
F. Managing Configurations with UNC
G. Configuring Sites and Channels with ZCM**
V. Communications Planning
A. Factors That Impact Communications System Planning
B. Fleetmapping
10.3.6 ASTRO 25 IV&D Telephone Interconnect

Duration
4 Hours
Delivery Method
Online/Self-Paced
Target Audience
System Technicians, System Managers
Course Synopsis
This workshop describes the hardware and software functionality associated with the
Telephone Interconnect feature in the ASTRO 25 Integrated Voice & Data (IV&D)
System.
Prerequisites
Completion of the following courses or equivalent experience:

RFP# 101216
December 16, 2010
Training 10-17
♦ Bridging the Knowledge Gap for ASTRO 25 Systems
♦ ASTRO 25 Integrated Voice and Data System Networking
♦ Completion of ASTRO Integrated Voice and Data System Overview with a
passing score on the post-test.
Course Objectives
♦ Describe the function and major components for the Telephone Interconnect
feature.
♦ Describe the operation of the Telephone Interconnect feature within the system.
♦ Install and configure the Telephone Interconnect equipment.
♦ Maintain and troubleshoot the Telephone Interconnect equipment.
Course Outline
I. Overview
II. Operation
III. Installation, Configuration and Optimization
IV. Maintenance and Troubleshooting
10.3.7 ASTRO® 25 IV&D ISSI.1 Network Gateway Overview

Duration
2-4 hours
Delivery Method
On-line, self paced
Audience
System Technicians, System Managers, Field Technicians
Course Synopsis
The ASTRO® 25 IV&D ISSI.1 Network Gateway Overview is a self study course intended to
provide information related to the operation and functionality of, including the hardware and
software associated with, the ISSI.1 Network Gateway. This course covers the ISSI.1 Network
Gateway operation in detail, including tasks, operation, theory, and troubleshooting; while
providing an overview of the installation and configuration of the ISSI Network Gateway
components.
Objectives:
♦ Describe how the ISSI.1 Networking Gateway fits into the system
♦ Describe how the ISSI.1 Network Gateway performs its interface functions
♦ Describe how the ISSI.1 Network Gateway works in its various configurations
Prerequisites
ACS78200-E ASTRO® 25 IV&D System Overview

RFP# 101216
December 16, 2010
10-18 Training
♦ Windows IE 6.x or higher
♦ Adobe Flash Player 9.x or higher
♦ Adobe Acrobat Reader 8.x or higher
♦ Minimum Screen resolution Set 1024 x 768
♦ Sound Card with speakers and headphones
Course Outline
♦ ISSI.1 Gateway Description
♦ Theory of Operations
♦ ISSI.1 Network Gateway Installation
♦ ISSI.1 Network Gateway Operation
♦ Troubleshooting
10.3.8 Point-to-Point Overview

Duration
4-6 hours
Delivery Method
Online; Self-paced
Course Overview
The Wireless Network Solutions Overview course teaches basic concepts, skills, and
terminology surrounding Motorola Point-to-Point products. The course focuses on
radio frequency basics, PTP technology, differentiators, licensed band applications,
and case studies.
Audience
Field Engineers
Objectives
♦ Identify radio basics and zone characteristics
♦ Recognize the characteristics of signal path
♦ Describe adaptive modulation
♦ Identify Point-to-Point architectures
♦ Define ISM and U-NII bands
♦ Compare the use and application of various licensed bands for PTP products
Prerequisites
None
Course Outline
I. RF Basics
A. Making the Link

RFP# 101216
December 16, 2010
Training 10-19
B. Clear Path
C. System Gain
D. Fade Margin
E. Adaptive Modulation
F. Duplexing Options
G. Adaptive Modulation
H. Duplexing Options
II. PTP Technology and Differentiators
A. Network Types
B. Key Network Challenges
C. MIMO
D. The IP Header
III. Licensed Band Applications
A. 4.9 GHz Connectivity for Public Safety
B. Pairing with ASTRO networks
C. PTP 49600 Value Proposition
D. 6 GHz Underbuild
E. Payload and Space Diversity
IV. Case Studies
A. Overwater Application
B. Non-Line-of-Sight
C. 6 GHz Underbuild Example
D. Long Distance Application
E. Security and Surveillance
F. Rapid Deployment
10.3.9 ASTRO 25 IV&D with M Core Workshop

Duration
5 days
Delivery Method
Instructor-led
Course Overview
The ASTRO 25 IV&D with M Core course teaches advanced troubleshooting skills
and best practices for the Trunked Large Systems. The course also focuses on
gathering and analyzing system information to implement appropriate action(s) that
return a system to full operational status.

RFP# 101216
December 16, 2010
10-20 Training
Audience
Master Site Technicians
Objectives
♦ Describe the ASTRO 25 System architecture
♦ Identify the functional and radio subsystems that comprise the ASTRO 25 System
♦ Explain and discuss call flow and data flow through Large System Core devices
and their subsystems
♦ Perform recommended routine maintenance procedures for the ASTRO 25 Large
System Core
♦ Utilize the troubleshooting tools to diagnose a fault and restore the Large System
Core to the level of the Motorola-supported service strategy
Prerequisites
♦ Completion of ASTRO 25 IV&D System Overview with a passing score on the
post-test
♦ ASTRO 25 IV&D Introduction to Radio System Administration
Networking Essentials in Communication Equipment
Advanced Networking in Motorola Communications Equipment (or equivalent
Field course)
Bridging the Knowledge Gap for ASTRO 25 - Technicians
Course Outline
I. Review of ASTRO® 25 System
A. System Review
B. Functional View – Call Processing (Control) Path
C. Functional View – Audio Path
D. Functional View – Network Management Path
E. Functional View – Data Path
F. Information Assurance High-Level Overview
II. System Troubleshooting Tools
A. Recommended Test Equipment
B. Troubleshooting Tools Overview
C. Detection Tools
D. Diagnostic Tools
E. Performance Management Tools
III. Network Transport Subsystem
A. Network Transport Review
B. Ethernet LAN Switch
C. Routers
D. Cooperative WAN Routing (CWR)
E. Transport Network Performance Server (TNPS)
IV. Call Processing Subsystem
A. Call Processing Subsystem Overview
B. Generic Application Server (GAS)
C. Zone Controller

RFP# 101216
December 16, 2010
Training 10-21
D. Zone Controller Configuration
V. Network Management Subsystem
A. Network Management Overview
B. Network Management Servers
C. Network Management Databases
D. Network Management Clients
E. Network Management Applications
VI. Data Subsystem and Customer Enterprise Network (CEN) Interface
A. Integrated Voice and Data Description
B. Packet Data Gateway (PDG)
C. “Global Packet Radio Service” Gateway Support Node (GGSN) Router
D. Customer Enterprise Network (CEN) Interface
E. Data Configuration
VII. Routine Maintenance and System Troubleshooting
A. Recommended Routine Maintenance
B. Database Backups
C. Network Device Configuration Backup
D. Appendix A: Routine Maintenance Schedules
E. Troubleshooting Hard Failures
F. Troubleshooting Intermittent Failures
G. System-Level Reliability
H. Intrazone Reliability
I. Configuration Troubleshooting
VIII. MGEG & AEB – Dispatch
A. Circuit-Based Dispatch
B. Motorola Gold Elite Gateway (MGEG)
C. Ambassador Electronics Bank (AEB)
10.3.10 ASTRO 25 IV&D IP Based Digital Simulcast

Duration
3 days
Delivery Method
Instructor-led
Course Synopsis:
The ASTRO 25 IV&D IP Based Digital Simulcast workshop provides an
understanding of the components that comprise the ASTRO 25 IV&D IP Simulcast
subsystem, and how they operate in conjunction with each other. The workshop also
explains the tools and methods available for troubleshooting components within the IP
Based Simulcast subsystem.
Audience
Simulcast Site Technicians

RFP# 101216
December 16, 2010
10-22 Training
Course Objectives
♦ Recognize the flow of message and control data within an ASTRO 25 IV&D IP
Digital Simulcast subsystem
♦ Identify the major components and connections within an ASTRO 25 IV&D IP
Digital Simulcast subsystem prime and remote sites
♦ Recognize how calls are processed within an ASTRO 25 IV&D IP Digital
Simulcast subsystem
♦ Perform maintenance and troubleshooting of select components in an ASTRO 25
IV&D IP Digital Simulcast subsystem
Prerequisites
♦ Completion of ASTRO 25 IV&D Trunked System Overview with a passing score
on the post test
♦ Introduction to Radio System Management Applications
Bridging the Knowledge Gap for ASTRO 25
OR
Bridging the Knowledge Gap for ASTRO 25: System Administrators
Networking Essential in Communication Equipment
Advanced Networking in Motorola Communications Equipment or the 5-Day
field version
Course Outline
I. IP Simulcast with GTR 8000 Subsystem Overview
A. Simulcast Review
B. IP Simulcast with GTR 8000 Subsystem Overview
C. Site Configurations
D. IP Simulcast – Integrated Voice and Data
II. GCP 8000 Simulcast Site Controller
A. GCP 8000 Overview
B. GCP 8000 Physical Description
C. GCP 8000 Configuration
D. GCP 8000 Diagnostics and Troubleshooting
III. Prime Site Ethernet LAN Switch
A. Prime Site Switch Overview
B. Prime Site Switch Physical Description
C. Prime Site Switch Configuration
D. Prime Site Switch Diagnostics and Troubleshooting
IV. GCM 8000 Comparator
A. GCM 8000 Overview
B. GCM 8000 Physical Description
C. GCM 8000 Configuration

RFP# 101216
December 16, 2010
Training 10-23
D. GCM 8000 Diagnostics and Troubleshooting
V. Prime Site - Routers
A. Prime Site Routers – Overview
B. Prime Site Routers – Physical Description
C. Prime Site Routers – Configuration
D. Prime Site Routers – Diagnostics and Troubleshooting
VI. TRAK 9100 Site Reference
A. TRAK 9100 Site Reference Overview
B. TRAK 9100 Site Reference Physical Description
C. TRAK 9100 Site Reference Installation and Configuration
D. TRAK 9100 Site Reference Diagnostics and Troubleshooting
VII. GTR 8000 Base Radio Subsystem
A. GTR 8000 Base Radio Subsystem Overview
B. GTR 8000 Base Radio Subsystem Physical Description
C. GTR 8000 Base Radio Subsystem Configuration
D. GTR 8000 Base Radio Subsystem Diagnostics and Troubleshooting
VIII. Remote Site Ethernet LAN Switch
A. Overview
B. Connection and Interface Requirements
IX. Remote Site Router
A. Remote Site Router Overview
B. Remote Site Router Physical Description
C. Remote Site Router Configuration
D. Remote Site Router Diagnostics and Troubleshooting
X. IP Simulcast Subsystem Maintenance and Troubleshooting
A. Maintenance and Troubleshooting Overview
B. Troubleshooting Tools
C. Device Fault Management
D. Troubleshooting Process
E. Troubleshooting Site Links
F. Motorola Support Centers
10.3.11 ASTRO 25 IV&D –GTR 8000 Repeater Site Workshop

Duration
3 Days
Delivery Method
Instructor-led

RFP# 101216
December 16, 2010
10-24 Training
Course Synopsis:
This workshop describes the components in the ASTRO 25 Integrated Voice and Data
System Repeater Site with GTR 8000 expandable site subsystem. This course also
presents how the GTR 8000 expandable site subsystem operates and explains the tools
and methods available for troubleshooting components within the subsystem.
Audience
GTR 8000 Site Technicians
Course Objectives
♦ Identify the major components and configurations of the ASTRO 25 Repeater Site
with GTR 8000 expandable site subsystem.
♦ Describe the functionality of the subsystem components and perform the required
maintenance.
♦ Configure the hardware and software for efficient operation.
♦ Describe the flow of message and control data in the various configurations.
♦ Describe call processing in a site.
♦ Troubleshoot the site, its hardware, and its configuration.
Prerequisites
♦ Completion of ASTRO 25 IV&D Trunked System Overview and passing score on

post-test
Bridging the Knowledge Gap for ASTRO 25
OR
Bridging the Knowledge Gap for ASTRO 25: System Administrators
Networking Essential in Communication Equipment
Advanced Networking in Motorola Communications Equipment or the 5-Day
field version
Course Outline
I. Course Introduction
II. GTR 8000 Repeater Site
A. GTR 8000 Repeater Site Overview
B. Operational Modes
C. Site Configurations
D. Site Components
E. Time Synchronization and Frequency Reference
III. GCP 8000 Site Controller
A. GCP 8000 Overview
B. GCP 8000 Physical Description

RFP# 101216
December 16, 2010
Training 10-25
C. GCP 8000 Configuration
D. GCP 8000 Diagnostics and Troubleshooting
IV. GTR 8000 Expandable Site Subsystem
A. GTR 8000 Expandable Site Subsystem Overview
B. GTR 8000 Expandable Site Subsystem Physical Description
C. GTR 8000 Expandable Site Subsystem Configuration
D. GTR8000 Expandable Site Subsystem Diagnostics and Troubleshooting
V. Radio Frequency Distribution System (RFDS)
A. RFDS Overview
B. RFDS Physical Description
C. RFDS Configuration
D. RFDS Diagnostics and Troubleshooting
VI. Network Transport Subsystem
A. Network Transport Subsystem Overview
B. Ethernet Switch Diagnostics and Troubleshooting
C. Site Routers
D. Router Diagnostics and Troubleshooting
VII. GTR 8000 Site Maintenance and Troubleshooting
A. Troubleshooting Tools
B. Troubleshooting Methodology
C. Troubleshooting Repeater Site Link
D. Motorola Support Centers
10.3.12 MCC7500 Dispatch Console

Duration
4 days
Delivery Method
Instructor-led
Target Audience
System Managers, Dispatch Supervisors, Console Technicians

RFP# 101216
December 16, 2010
10-26 Training
Course Synopsis
This course familiarizes technicians in troubleshooting/repair functions, operating
procedures, and hardware/software applications for the MCC 7500 console. The focus
is on a detailed discussion of console hardware and hands-on activities with the
installation and configuration of the MCC 7500 console.
Lab Requirements
♦ AIS
♦ AUX I/O servers
♦ Network Management Terminals at a ratio of 1 for every 4 students to insure
proper hands-on
Prerequisites
♦ Bridging the Knowledge Gap
♦ ASTRO 25 IV&D System Overview
♦ ASTRO 25 IV&D Introduction to System Management Applications
♦ ASTRO 25 IV&D System Networking
Course Objectives
♦ Install and configure the hardware and software components of the MCC 7500
Dispatch Console Subsystem.
♦ Perform system administrator functions using the MCC 7500 Administrator
software.
♦ Perform maintenance and troubleshooting for the MCC 7500 Dispatch Console.
Course Outline
I. MCC 7500 Dispatch Console Overview

A. Features and Benefits
B. System Views
C. Interoperability – CENTRACOM/MCC 7500
II. Hardware Install and Specifications
A. Dispatch Console PC
B. Aux I/O
C. Logging System
D. Site Router and LAN Switch
E. Analog Conventional Operation
III. Configuration
A. Configuring the Console Operator Position
B. Configuring System Resources
C. Configuring Zone-Level Entities and Third-Party Devices
IV. Administrator Functions
A. Installation and Configuration
B. Folders and Resource Setup
C. Setting up Aux I/Os
D. Configuring the Toolbar

RFP# 101216
December 16, 2010
Training 10-27
E. Editing Preferences
F. Auto Starting the MCC 7500 Dispatch Console
V. Troubleshooting
A. Troubleshooting with FullVision INM
B. Troubleshooting MCC 7500 Components
10.3.13 MOSCAD NFM Programming, Maintenance and Operator

Duration
5 days
Delivery Method
Instructor-led
Course Synopsis:
♦ The MOSCAD Network Fault Management course covers the programming,
maintenance, and operation of the:
NFM/NFM XC RTU
SDM3000 RTU
IP Gateway
SDM3000 Network Translator (SNT)
Graphic Master Computer (GMC)
♦ The course focuses on a detailed discussion of the different types of Network Fault
Management systems, RTU hardware, hands-on activities with programming the
RTU’s, running Mixed MASB and MASB sessions, navigating with the web
browser features and the Graphic Master Computer.
Audience
System Managers, Service Technicians, Motorola Service Center, End Users
Course Objectives
♦ Install NFM software on students laptops
♦ Configure alarm points using site builder and SDM3000 builder
♦ Perform a Mixed MASB and MASB session to import alarm tags
♦ Navigating and acknowledging alarms at the Graphic Master Computer
♦ Utilize the web browser features to view and configure the system
♦ Create a custom data base using .CSV files for I/O integers and I/O discretes
♦ Create custom tabs
♦ Create custom maps
Prerequisites
♦ A basic understanding of Windows navigation
♦ Laptop computer with Windows XP
♦ Windows program files must be on the “C” directory

RFP# 101216
December 16, 2010
10-28 Training
Course Outline
I. Network Fault Management Overview (NFM)
A. Introduction to MOSCAD NFM
B. Types of NFM systems
C. Serial infrastructure systems (NFM/NFM XC)
D. Ethernet infrastructure systems (NFM XC/ SDM3000)
II. MOSCAD NFM Hardware Overview
A. NFM RTU
B. NFM XC RTU
C. IP Interface
D. IP Gateway
E. RS 232 Mux/R-Mux
F. SDM3000 Advance Model
G. SDM3000 Basic Model
H. SDM3000 Expansion Models
I. SDM3000 Network Translator
III. Configuring MOSCAD NFM Software
A. IP Gateway Programming Tool Box
B. MOSCAD Programming Tool Box
C. Site Builder
D. SDM3000 Builder
E. Mixed MASB
F. MASB
G. Configuring and Navigating the GMC
H. Create Custom .CSV files
I. Create Custom Tabs
J. Create Custom Maps
IV. Utilizing NFM Software for Diagnostics and Browsing
A. Perform Hardware and Communications test using the Tool Boxes
B. Implement the Web Browser features for both the NFM XC and SDM3000
V. Introduction to optional MOSCAD NFM Software
A. Report Generator
B. SCADA Alarm
10.3.14 APX CPS Programming and Template Building

Duration:
Tailored for 2 days Instructor Led
Delivery Method
Instructor-led
Course Synopsis
The APX CPS Programming and Template Building course provides communications
management personnel and technicians with the knowledge and training necessary to build
templates and program APX 7000/7500 subscriber radio’s in the most efficient way possible.

RFP# 101216
December 16, 2010
Training 10-29
The content, parameters and exercises demonstrated in the APX CPS Programming and
Template Building class apply to the APX 7000 Portable and APX 7500 Mobile.
Target Audience
♦ Radio Technicians, System Managers and anyone who has the responsibility of
programming APX subscriber radios.
Prerequisites
♦ Knowledge of the basic features and options of two-way radios, and the basic
concepts of conventional and trunking systems.
Course Objectives
After completing this course, the student will be able to:
♦ Build APX 7000/7500 templates using the APX Customer Programming Software
(CPS)
♦ Program the specific parameters related to various radio system configurations:
Conventional, Single Site Trunking, Simulcast, SmartZone, ASTRO 25 and
ASTRO 25 X2
♦ Demonstrate detailed knowledge of APX CPS navigation, tools, options and
features that make efficient programming of the radio possible
♦ Demonstrate a complete understanding of APX CPS efficiency tools, such as
Cloning, Drag and Drop, Codeplug Comparison, Radio Flashing, Advance System
Key Administration and others
Course Outline
♦ Introduction to APX 7000 Radio
♦ Introduction to APX CPS
♦ APX CPS Install, Setup and Configuration
♦ Navigating APX CPS
♦ APX CPS Data Transfer
♦ Understanding and Interpreting Radio Information
♦ Detailed Review of Codeplug Contents
♦ APX Conventional Codeplug Build
♦ APX Type II Trunking Codeplug Build
♦ APX ASTRO 25 Trunking Codeplug Build
♦ Building Scan List
♦ Additional/Advanced CPS Functionality

RFP# 101216
December 16, 2010
10-30 Training
10.3.15 APX Technical Subscriber Academy
Duration
5 days
Delivery Method
Classroom Instruction
Course Synopsis:
This course focuses on the knowledge required for a 2-way Radio Technician working
in a communication environment or using the family of APX radios in the field. The
course is specifically designed to provide significant amounts of hands-on, scenario
based labs around configuration and troubleshooting. Key Loading and Management,
Encryption, Over-The Air Programming and Mobile Radio Installation are some of the
topics that will be covered in detail for both mobile and portable radios.
Audience
Radio technicians
Objectives
After completing this course, the student will be able to:
♦ Distinguish between the features and specifications of the APX 7000 and the APX
7500 radio
♦ Verify the correct operations of the APX 7000 and the APX 7500 radio
♦ Maintain and troubleshoot an APX 7000 and APX 7500 radio
♦ Disassemble and reassemble the radio using the documented procedures
♦ Verify the housing integrity of an APX 7000 portable radio
♦ Flash upgrade an APX 7000 and APX 7500 radio
Prerequisites
Completion of the following courses:
♦ CPS Programming and Template Building Overview (ADT001-V or Test out
ADT001-T)
♦ Completion of the following courses or equivalent experience in Radio
Communications:
♦ Communication Systems Concepts (NST021)
♦ Radio Systems Overview (RCS002-E or Test out RCS002-T)
♦ Theory of Radio Operations (RCS003-E or TEST out RCS003-T)
Course Outline
♦ APX Radio Introduction
♦ APX Radio Performance Checks
♦ APX Radio Alignment

RFP# 101216
December 16, 2010
Training 10-31
♦ APX Radio Theory Of Operation
♦ Radio Disassembly / Reassembly
♦ Vacuum Testing For Submergibility
♦ Mobile Radio Installation & Configuration
♦ Advanced Customer Programming Software
♦ Radio Troubleshooting
10.3.16 MCC7500 Supervisor

Duration
4 hours Operator, plus
4 hours Supervisor
Delivery Method
Instructor-led
Target Audience
Dispatch Supervisors, System Administrators
Course Synopsis
This course provides participants with the knowledge and skills to manage and utilize
the MCC 7500 console administrator functions. Through facilitation and hands-on
activities, the participant learns how to customize the console screens.
Course Objectives
♦ Understand the menu items and tool bar icons
♦ Edit folders, multiselect/patch groups, auxiliary input output groups, windows and
toolbars
♦ Add/delete folders
None
Key Topics
♦ Introduction
♦ Configurations
♦ Folders and Resource Setup
♦ Customizing Folders
♦ Auto Starting the MCC 7500 Dispatch Console
♦ Editing Preferences
♦ Configuring the Toolbar
♦ Setting Up Aux IOs
♦ Resource Groups

RFP# 101216
December 16, 2010
10-32 Training
10.3.17 MCC7500 Operator
Duration
4 hours
Delivery Method
Instructor-led
Target Audience
Dispatch Console Operators, Supervisors, System Administrators, and Support
Personnel
Course Synopsis
This course provides participants with an introduction to the dispatch console, its basic
operation and tailored job aids which will be available for assistance in operation.
Through facilitation and hands-on activities, the user learns how to perform common
tasks associated with the console operation.
Course Objectives
♦ Perform basic operational tasks of the dispatch console
♦ Utilize the provided job aids to perform specific tasks associated with the console
♦ Understand a high level view of the system configuration
♦ High-level overview of the customer system configuration
♦ General console operation
♦ Proper operating procedures for specific customer features
None
Key Topics
♦ Overview
♦ Communicating with Radios
♦ Advanced Signaling Features
♦ Resource Groups
♦ Working with Configurations
♦ Working with Aux IOs
♦ Troubleshooting

RFP# 101216
December 16, 2010
Training 10-33
10.3.18 MIP5000 Console Operator
Duration
4 hours
Delivery Method
Instructor-led
Target Audience
Dispatch Console Operators, Supervisors and Support Personnel
Course Synopsis
This course will provide a dispatcher with the necessary skills to quickly access and
activate the dispatch features of the MIP 5000 console. The classroom experience is a
mix of instructor-led facilitation and hands-on activities.
Required Pre-Work
None
♦ Proficiency in IBM-compatible computers
®
♦ Proficiency in the Microsoft Windows™ operating system interface
Course Objectives
♦ Access and activate radio features basic to two-way communications
♦ Transmit and receive a variety of voice communications using all of the console’s
features
♦ Control repeater access
♦ Work with multiple selections of radio channels
♦ Control sets of radio channels as patches
♦ Send a page in two different ways, and program the page list
♦ Send or receive a stat-alert signaling message or request
Course Outline
A. Module 1: Overview
1) Start the Program
2) Log In
3) Log Out
4) Exit the Program
B. Module 2: Basic Radio Operations

1) Select a Radio
2) Unselect a Selected Radio
3) Select a Radio Channel
4) Unit ID or Alias

RFP# 101216
December 16, 2010
Training 10-35
5) Receive a Radio Channel
6) Adjust Volume
7) Mute/Unmute Radio Channel Audio
8) Mute/Unmute All Unselected Channel Audio
9) Activity Log Window
10) Respond to Emergency Call
11) Send an Alert Over Selected Radio Channels
12) Transmit on a Radio Channel
13) Transmit on a Multiple Selection
14) Transmit an APB
15) Transmit to the Base Station Intercom
16) Transmit Queue
17) Private-Line/Tone-Coded Squelch Control
a. Enable/Disable the Coded Squelch
b. Change the Coded Squelch
18) Voice Secure
19) Marker Tone
a. Send
b. Stop
20) Site Select
21) Repeater Access
a. Disable
b. Enable
C. Module 3: Multiple Selection of Radio Channels
1) Create a Multiple Selection
2) Delete a Multiple Selection
3) Activate a Multiple Selection
4) Deactivate a Multiple Selection
D. Module 4: Patching
1) Create a Patch
2) Modify a Patch
a. Add a Radio Channel Control
b. Remove a Radio Channel Control
3) Clear a Patch
4) Activate a Patch
5) Transmit on a Patch
E. Module 5: Paging
1) Send a Manual Page
2) Program the Page List
a. Add a Tab
b. Delete a Tab
c. Edit a Tab
d. Add a new Entry
e. Delete an Entry
f. Edit an Entry
3) Send a Programmed Page
4) Page History Dialog Box
F. Module 6: Stat-Alert Signaling

RFP# 101216
December 16, 2010
10-36 Training
1) Incoming Signaling
2) Outgoing Signaling
3) Send a Stat-Alert Signal
G. Module 7: Supervisory Features
1) Takeover
2) Supervisory Button
10.3.19 APX7000 Portable and APX7500 Mobile Train-the-Trainers

Duration
Up to 8 hours
Delivery Method
Instructor-led
Target Audience
APX Trainers, Supervisors and Support Personnel.
Course Synopsis
This course provides APX radio trainers with an introduction to their radio, its basic
operation and tailored job aids available for assistance in operation. The learning
experience is a mix of facilitation and hands-on activities to help users perform
common tasks associated with their radio operation. Segmentation between user groups
(i.e. Police, Fire/EMS, Public Service) is encouraged to help focus instruction on the
specific operational issues of the individual user group. This course is geared for
customers who have an experienced dedicated training staff in their organization. It
provides the customer’s identified training personnel with the knowledge and practice
applying training techniques that will enable them to successfully train their students.
Trainers will use audio visual (Interactive End User Toolkits – iEUTK), facilitation
and hands-on activities to facilitate learning events supported by tailored or customized
training materials and job aides. They will become proficient in discussing common
tasks associated with the operation of the customer’s radios.
Required Pre-Work
None
Recommended Pre-requisites
Previous two-way radio and training experience
Course Objectives
♦ High-level overview of the customer system configuration
♦ General radio operation
♦ Proper operating procedures for specific customer features
♦ Perform basic operational tasks of the radio
♦ Utilize the provided job aids to perform specific tasks associated with the radio

RFP# 101216
December 16, 2010
Training 10-37
Course Outline
A. Basics
1. Controls
a. Top and Side Buttons
b. Switches
1. 3 Position toggle
2. 2 Position Concentric
c. Home key
d. Data Key
2. Display
a. Front Display
b. Top Display
c. Display light
d. Intelligent Lighting
3. Push To Talk or Accessory PTT found on the microphone
4. Hub, hang up box (Mobile)
5. Menu
a. Menu Screen Anatomy
b. Navigating Menu Screen
6. Recent Call List (Model 3.5)
7. Unified Call List - Contacts (Model 3.5)
8. Dual Sided Radio (Model 3.5)
a. Dual Mics
b. Dual Speakers
9. Accessory Connector
B. Specific Features
1. Changing Talkgroups/Channels
2. Changing Zones
3. Mute tones of keypad
4. Talkgroup Call
5. Private Call
a. Accessing Private Call Feature
b. Initiating Private Call
c. Call List Programming
6. Announcement/All Call (Calls involving Multiple Talkgroups)
a. Initiating Announcement/All Call
7. Direct/Talkaround
8. Failsoft
9. Radio Profiles
a. Accessing and changing Radio Profile
C. Optional Features
1. Scan
a. Scan program
b. Priority Scan
c. Dynamic Priority
2. Telephone Interconnect

RFP# 101216
December 16, 2010
10-38 Training
a. Accessing Telephone Interconnect Feature
b. Initiating a Phone Call
c. Phone List Programming
3. Data Services
a. Text Messaging
1. Accessing the Text Messaging Feature
2. Creating a Free Form Text Message
3. Sending a “Canned Text Message
b. GPS
c. OTAP
4. Encryption
10.3.20 ASTRO 25 Mobile and Portable Train-the-Trainers

Duration
1 day (up to 6 hours of content)
Delivery Method
Instructor-led
Target Audience
This one-day course is geared for customers who have an experienced dedicated
training staff in their organization. This course concentrates on specific product
features and how it relates to the training process.
Course Synopsis
These courses are designed to teach the customer how to operate the ASTRO 25 radios
with the features programmed. In addition, the customer will be taught how to use
Motorola Interactive End User Toolkits (iEUTK) to customize their end user training
presentations for individual agencies. Segmentation between user groups (i.e. Police,
Fire/EMS, Public Service) is encouraged to help focus instruction on the specific
operational issues of the individual user group.
Note: This course is presented as customer specific and will cover pertinent to
customer equipment.
Prerequisites
Previous training experience and radio system knowledge is a must.
Course Objectives
The participant will be able to employ the toolkit resource needed to facilitate learning
events supported by the Interactive Toolkit. Train-the-Trainer sessions for radio
user/operations will typically consist of a training event following the basic outline:
1. Discuss high-level overview of the customer’s system configuration.

2. Present a Trunking Overview if applicable.

RFP# 101216
December 16, 2010
Training 10-39
3. Cover the Instructor Guide provided for group and product being covered.
4. Present Interactive End User Toolkit (iEUTK) training philosophy/methodology.
5. Review Interactive End User Toolkit (iEUTK) controls.
6. Demonstrate techniques for training using the Interactive End User Toolkit (iEUTK)
materials.
7. Discuss the difference between ASTRO and Analog audio quality if applicable to the
customer’s system.
8. Discuss proper radio techniques.
9. Conduct practice sessions with trainers. (depends on size and protocol of audience.)
10. Basics
♦ Volume / on - off
♦ Zone up and down keys
♦ Home key
♦ Display with all its icons
♦ Push to talk or PTT found on the microphone
♦ Hub, hang up box
11. Features
♦ Mute tone of keypad
♦ Changing Talkgroups
♦ Changing zones or personalities
♦ Differences of Talkgroups call and Private call
Call list program
♦ Phone Interconnect
Phone list program
♦ Scan
Scan program
♦ Direct
♦ Display light
♦ Failsoft definition

RFP# 101216
December 16, 2010
10-40 Training
10.3.21 CCSA IP-10/IP-10G class curriculum
Agenda:
Day 1: 9:00 to 4:30
Module 1 Welcome and introductions

♦ Introduction to Ceragon Networks
♦ Short overview on the Company
♦ Support structure
Module 2 Going from links to a complete solution

♦ Network topologies and infrastructure
♦ Challenges in todays technologies for microwave and beyond
♦ Flexing the Network with ACM and lowering cost
♦ Benefits of Carrier Ethernet deployment
Module 3 Electromagnetic Radiation

♦ RF 101 review
♦ Radio waves physics
♦ Power measurements, antennas, signals
Module 4 TDM & IP What does it all mean? (introduction)

♦ TDM signal structures (T1)
♦ Ethernet signal structure (IP)
Module 5 FiberAir Family of Products IP-10/IP-10G

♦ FiberAir IP-10 Products Description and Specifications
♦ Technical specifications and features
♦ Configurations and Protection Schemes
♦ IDU Features and Specifications
♦ RFU Features and Specifications
Including:
Modulation scheme details
Adaptive code modulation details, switching criteria
Relationship : System capacity – modulation – channel spacing – RF bands –
Tx power – Rx threshold – system gain
Relationship: Throughput – air link speed – efficiency – packet length – latency
SW licensing and set up
MEF brief and compliance
Ethernet capabilities overview e.g. RSTP, VLAN, type of interface, SFP,
throughput, port setting options, Ethernet OAM and statistics

RFP# 101216
December 16, 2010
Training 10-41
Transmission features: ATPC,
System features: sychronization, timing distribution, protection (1+0, 1+1),
reliability, auxiliary channels, Tx mute override, security
Module 6 Management and General Set up
♦ Management and configuration

♦ Polyview Network managment
♦ Hyper terminal (getting access to radio via CLI)
♦ Web base management
♦ Radio Provisioning
Including:
♦ Inband and out of band management set up
Lab 1
♦ CLI set up configuration
Lab 2
♦ Management set up using Web interface
Lab 3
♦ Radio set up
Lab 4
♦ Radio Parameters
Lab 5 & 6
♦ Manage Switch, Metro and Single pipe
Day 2: 8:30 to 2:00

Module 7 ACM and QoS Demonstration
♦ Demonstration of IP-10IP-10G ACM hitless and errorless mechanisms using QoS
features
Module 8 Diagnostics and Maintenance
♦ Diagnostics (LED indications)
♦ Loopbacks
♦ Performance analysis
♦ Troubleshooting

RFP# 101216
December 16, 2010
10-42 Training
Lab 7
♦ Troubleshooting the radio
Module 9 Software upgrade and download Parameters

♦ Software upgrade procedures
♦ Configuration management
♦ Software management
♦ Suggestions on various FTP servers and installations
Module 10 Hardware Installation and Set up

♦ Installation requirments
♦ Hardware set up and provisioning
♦ Antenna alignment and measurements
♦ Front panel indications
♦ Acceptance and commissioning
CCSA certification exam

♦ Multiple choice questions
NOTE:
Students are required to have Laptops, Cat-5 and RS-232 cables to get access to the
radios via SNMP and Hyper terminal.
If students have Layer 2 Test equipment, it is helpful if brought to class, but not
mandatory.

RFP# 101216
December 16, 2010
Training 10-43
10.3.22 Ceragon Training Agenda
Product:
♦ NMS
Course:
♦ NMS Operation and Maintenance
Duration:
♦ 1 days (Theory + Practice)
DAY ONE
Topology Configuration:
♦ Adding Elements
♦ AutoDiscovery
♦ Adding Maps
Administration
Log Analysis and Filtering
System Configuration
♦ Dynamic Poling
♦ Static Poling
♦ Configuration Broadcast
♦ Configuration File Download
♦ Software Download
♦ FTP
♦ Mail Server
♦ Northbound
End to End Trap Configuration

Exam / Course Summary

RFP# 101216
December 16, 2010
10-44 Training
Section 11. Warranty and Customer Support
11.1 System Warranty
Motorola provides an integrated total support plan for service, support and repair of
your wireless communications network. Our comprehensive support services can
help reduce your total cost of ownership and ensure service availability, while
helping you cost-effectively deliver new network capabilities.
Motorola is committed to earn your confidence with regard to the post contract
warranty and future maintenance requirements of the proposed Astro P25 network.
The City of Rome and Floyd County can be assured that Motorola as the provider of
all services will be responsible for your system’s performance during warranty and
beyond. Our local Georgia team has vast experience in maintaining Digital P25
systems. Having deployed the first Digital 800 Mhz Simulcast P25 system in 2002 in
Houston County; this Motorola team maintains more than 100 sites covering over 20
Counties in Georgia. Our proposed warranty support plan for the City of Rome and
Floyd County will utilize our significant customer support resources that include:
♦ Local Field System Technologists
♦ Motorola System Support Center
♦ Local MSS Coosa Valley Communications
In order to support our public safety customers in Georgia and to ensure our
commitment to Floyd County, Motorola has a vast team of technical resources to
draw from that include our Atlanta based, sixteen member Field System
Technologists team, as well as over twenty Motorola Authorized Service Centers
with more than one hundred technical support personnel on the ground every day.
Motorola will also provide a technical resource with significant ASTRO P25 “hands
on" experience to the Floyd County project. This individual will work with the local
Motorola Service Partner to ensure that all shop technical responsibilities are
implemented correctly and expediently. Motorola will work closely with Coosa
Valley Communications during the implementation period to ensure that they expand
their staff and technical expertise to guarantee a high level of service support.
Motorola and Coosa Valley Communications have collectively committed to invest
what is necessary to support the service support requirements for the City of Rome
and Floyd County. Coosa Valley Communications has already begun the certification
process required by Motorola to provide P25 support services. Their commitment
coupled with Motorola’s corporate commitment and vast experience will ensure that

RFP# 101216
December 16, 2010
Warranty and Customer Support 11-1

the City of Rome and Floyd County receive an impressive level of local support
during system implementation and post system acceptance.
Motorola is pleased to propose a warranty plan that provides all the support services
required by the County’s RFP and also includes services that exceed the RFP
requirements. These additional services are part of our standard warranty offering and
are included at no additional cost to the County. Specifically Motorola is providing
the following services during warranty that exceed the RFP requirements:
♦ Network Monitoring – 24x7 fault monitoring and diagnostics
♦ Security Monitoring – 24x7 protection against security breaches
♦ Security Update Service – pre-tested anti-virus and security updates
♦ Dispatch Service – 24x7 call tracking and escalation
11.2 Warranty Services

Motorola’s proposed warranty program consists of a one-year parts and labor
warranty from the date of system acceptance or beneficial use of the new equipment
included in this proposal. During the warranty year, these services provide complete
support of your communications network and ensure optimal efficiency, security and
reliability of your investment:
♦ Network Monitoring Service
♦ Security Monitoring Service
♦ Security Update Service
♦ Dispatch Service
♦ OnSite Infrastructure Response
♦ Network Preventative Maintenance
♦ Technical Support
♦ Infrastructure Repair with Advanced Replacement
♦ Software Maintenance Agreement (SMA)
♦ Subscriber Support
11.2.1 Network Monitoring Service
Exceeds RFP Specification

Motorola’s Network Monitoring Service provides real-time remote fault monitoring
and diagnostics on a consistent and continuous (24 x 7 x 365) basis. The Network
Monitoring Service enables highly trained technologists located in Motorola’s
System Support Center (SSC) to routinely observe network performance and to
intervene as necessary, often before a potential problem becomes apparent even to
users. The SSC uses sets of hardware and software tools for remote monitoring,
characterization, restoration and maintenance support for the management of a
complex communications network, as well as their component parts (including base
stations, computers and internetworking components).

RFP# 101216
December 16, 2010
11-2 Warranty and Customer Support

When the SSC detects an event, Motorola
trained technologists acknowledge and assess
that situation, then conduct remote diagnostic
routines, and initiate an effective response. Such
responses could include, but are not limited to,
continuing to monitor the event for further
developments, attempting remote restoration, or
transferring the event information via a case for
the dispatch of a local service technician. The
technician will respond to the customer location
based on pre-determined severity levels and response times. The SSC maintains
contact with the onsite technician until your system is restored and the case closed.
The SSC will continuously track and manage case activity from open to close through
an automated case-tracking process, enabling Motorola to issue timely activity and
performance reports.
11.2.2 Security Monitoring Service

Motorola’s Security Monitoring Service is designed specifically for ASTRO® 25
public safety radio communications networks and identifies viruses worms, and other
potential security threats that will result in a security incident and impact system
availability and performance. While these threats could come from outside, they
could unintentionally come from your own employees or third party vendors who
work on your network.
Expert technologists at our Security Operations Center,

currently monitoring over 50 customer networks, as well
as 100,000 Motorola nodes. They look at the data,
identify events outside the norm, and then initiate incident
response and escalation processes. The technologists also
have direct access to Motorola’s engineers who know the
network inside and out and get involved to resolve the
more critical, higher level issues.
Your network security elements are monitored 24x7x365 (includes antivirus, firewall,
IDS, centralized logging services, etc.) for proactive detection, collection, and
analysis of security events. Our Remote Incident Team provides SLA-driven
notifications and remediation assistance with security case management, escalation as
needed, and security incident reports. Proven processes and procedures ensure
automated deployment of pre-tested antivirus and IDS updates with 24-hour
turnaround for urgent anti-virus updates.

December 16, 2010

11.2.3 Security Update Service

The Security Update Service (SUS) provides the latest releases of software security
updates. Commercial security software updates are often designed without RF
systems in mind and could cause inadvertent harm to your radio network, disrupting
mission-critical communications and putting your first responders and citizens at risk.
SUS assures that commercial anti-virus definitions, operating system software
patches, and Intrusion Detection Sensor signature files are compatible with your
ASTRO 25 network and do not interfere with network functionality.
After these patches have been pre-tested and certified by Motorola, an email
notification is sent to customers upon availability of new updates with access to a
Motorola secure extranet website that will enables customers to download the pre-
tested, certified security updates when convenient. Deploying these pre-tested
updates and patches as they become available assures preparedness against network
performance interruptions due to security vulnerability, and electronic attack.
Customers may also purchase the ability to have these pre-tested patches
automatically deployed on their system.
11.2.4 Dispatch Service

Motorola’s System Support Center (SSC) is the single point of contact for all service
issues. With Dispatch Service, one phone call to the SSC and the system response
and restoration process begins immediately. Dispatch ensures that local, trained and
qualified technicians will arrive on location within hours to diagnose and restore the
communications network. Once the issue has been addressed the SSC verifies
resolution and, with customer approval, closes the case. Activity records are also
available to provide comprehensive history of site performance, issues, and
resolutions.

RFP# 101216
December 16, 2010

11.2.5 OnSite Infrastructure Response
OnSite Infrastructure Response provides local, trained and qualified technicians who
arrive on location to diagnose and restore the communications network. Motorola
Dispatch contacts the local authorized service center in your area and dispatches a
qualified technician to the site. An automated escalation and case management
process ensures that the technician arrives and system restoration begins within the
contracted response times.

December 16, 2010

The field technician performs first level trouble-shooting, provides information
regarding the system condition, removes any failed components for repair, and
reinstalls new or reconditioned components. If the technician is unable to resolve the
issue, the case is escalated to the SSC or product engineering teams as needed.
As the authorized Motorola service partner in Floyd County, Coosa Valley
Communications will provide 7x24 local onsite support of the proposed system.
Coosa Valley Communications is the largest and most experienced two-way
communications service provider in Floyd County. Coosa Valley has specialized in
the sale, installation and maintenance of radio communication networks, wireless
broadband, and 9-1-1 systems for Public Safety, Commercial, and Industrial users in
the area. Motorola is working closely with Coosa Valley Communications to ensure
their staff and level of technical training is enhanced to support the proposed P25
technology. The Motorola Georgia service team is uniquely positioned to dedicate
additional resources as necessary to ensure complete customer satisfaction.
Motorola’s extensive network of service partners located with 100 miles of Floyd
County is listed in Subsection 9.4. These additional service partners are available for
support of your system as needed.
11.2.6 Network Preventative Maintenance

Motorola’s Network Preventative Maintenance minimizes premature repairs by
providing operational test and alignment on the infrastructure or fixed network
equipment to ensure all components are operating consistent to manufacturers’
specifications.
This service proactively detects those potential issues that may result if the equipment
does not meet original manufacturer’s specifications. This helps prevent a system
malfunction and minimize costly repairs, thus better managing your maintenance
budget.
11.2.7 Technical Support

Motorola Technical Support service provides an additional layer of support through
centralized, telephone consultation for issues that require a high level of
communications network expertise and troubleshooting capabilities. Technical
Support is delivered by the SSC and is staffed 24 hours per day, 365 days a year. The
SSC is staffed with trained, skilled technologists specializing in the diagnosis and
swift resolution of network performance issues. These technologists have access to a
solutions database as well as in house test labs and development engineers. Technical
Support cases are continuously monitored against stringent inbound call management
and case management standards to ensure rapid and consistent issue resolution.
Technical Support service translates into measurable, customer-specific metrics for
assured network performance and system availability.

RFP# 101216
December 16, 2010

11.2.8 Infrastructure Repair Service with Advanced Replacement
Infrastructure Repair with our Advanced Replacement upgrade supplements your
spares inventory with Motorola’s centralized inventory of critical equipment. In
advance of Motorola repairing the malfunctioning unit, a replacement unit is sent to
you within 24 hours to ensure a spare unit is available. Upon receipt of the
malfunctioning unit, Motorola repairs the unit and replaces it in our centralized
inventory.
11.2.9 Software Maintenance Agreement (SMA)

The Motorola Software Maintenance Agreement (SMA) complements the lifecycle of
the ASTRO 25 system by providing periodic software updates which safeguard and
enhance the operation, and extend the lifespan of the ASTRO 25 system. Due to
normal advancements in technology, individual components within the ASTRO 25
platform require periodic updates and replacement to mitigate network vulnerabilities
and address technology obsolescence.
The SMA provides system release software for Motorola and third-party
infrastructure products, radio subscriber units (optional), product programming
software as well as commercial OS patch updates. Additionally, Motorola integrates
all third-party OEM updates and pre-tests and certifies functionality and
compatibility, mitigating risk of interference to the system operation.
The SMA is included in the proposed System Warranty and includes:
♦ Minor Release (patch release) – Available on a monthly/quarterly basis via

extranet web site or optional automated push, includes security patch updates to
third-party operating system (OS) and application software as well as host-based

December 16, 2010

intrusion detection sensor (IDS) signature file updates for Motorola supplied
equipment. Updates occur monthly for Microsoft Windows and quarterly for
Oracle, Sun Microsystems and Red Hat Unix/Linux OS and IDS signature files.
♦ Major Release (system release) – Floyd County’s system will be upgraded to
the latest available system release before the end of the system warranty.
11.2.10 Subscriber Support

Motorola’s authorized service station will provide Local Radio Support that includes
operational checks of subscriber equipment to identify external or internal defects. If
a subscriber unit has an external defect, or can be restored without opening the radio
case, the unit will be restored and returned to customer. If the unit has an internal
defect, or is not serviceable without opening the radio case, then the unit will be sent
to Motorola’s Depot for factory repair where we will test and restore the unit to
factory specifications. With this service, subscribers receive higher service priority,
which results in quicker repair times.
11.3 Summary
Motorola’s Support Services ensure peak network and operational performance by
offering a diverse portfolio of scalable support services. Motorola has an extensive
service organization to provide local, trained, and qualified service personnel to
manage your communications network. Motorola’s Support Services focuses on
performance, both technological and operational, to maximize the efficiency and
security of your communications network. These services can help increase both the
availability and the operating efficiency of your network, while effectively managing
costs and ensuring the safety of your employees and the citizens they protect.
Motorola’s in-depth and first-hand knowledge of mobility – communications
processes, technologies and integrated solutions is invaluable. We have more than 80
years of experience in designing, building, maintaining and managing large, complex
mobile networks. Our 6,500 Motorola Services professionals and over 8,000 world-
class partners and certified subcontractors, have the support of a global network of
R&D centers and test labs, as well as Motorola service and support centers at local,
regional and national levels. Few organizations claim to offer such a complete range
of professional services within the communications industry. Even fewer are prepared
to deliver.
11.4 Post Warranty Maintenance Services

In response to the RFP, Motorola has also included maintenance pricing for four
additional years of service and support to assist you in maintaining your
communications network after the first year warranty period. The continuation of
these services beyond the warranty year will help ensure maximum system uptime as
well as maintaining the highest level of system performance.

RFP# 101216
December 16, 2010

Motorola has provided post-warranty maintenance pricing for the following services
as required by the RFP:
♦ Dispatch Service
♦ Onsite Infrastructure Response
♦ Network Preventative Maintenance
♦ Technical support
♦ Infrastructure Repair with Advanced Replacement
The RFP also specifically states that it is the intention of Floyd County to use County
resources and rely minimally on outside contract labor to maintain the proposed
system after warranty. Motorola will be happy to work with the County to identify
the training and equipment required to ensure that your personnel is equipped to
provide the desired level of in house system support following system warranty.
Motorola has provided the requested technical training in our proposal per the RFP.
Once the County makes a determination with regard to post warranty maintenance,
Motorola will work with you to develop a service plan tailored to your specific needs
and budget.

December 16, 2010


RFP# 101216
December 16, 2010

Section 12. Pricing
Please refer to the separately submitted Price Proposal.

December 16, 2010
Pricing 12-1

December 16, 2010
12-2 Pricing
Section 13. Contractual Documentation
Please see Motorola’s Communications System Agreement on the following pages.

December 16, 2010
Contractual Documentation 13-1


December 16, 2010
13-2 Contractual Documentation

Communications System Agreement
Motorola, Inc. (“Motorola”) and Floyd County, Georgia (“Customer”) enter into this “Agreement,” pursuant
to which Customer will purchase and Motorola will sell the System, as described below. Motorola and
Customer may be referred to individually as a “Party” and collectively as the “Parties.” For good and
valuable consideration, the Parties agree as follows:
Section 1 EXHIBITS
The exhibits listed below are incorporated into and made a part of this Agreement. In interpreting this
Agreement and resolving any ambiguities, the main body of this Agreement takes precedence over the
exhibits and any inconsistency between Exhibits A through E will be resolved in their listed order.
Exhibit A Motorola “Software License Agreement”

Exhibit B “Payment Schedule”
Exhibit C “Technical and Implementation Documents”
C-1 “System Description” dated _______________
C-2 “Equipment List” dated _______________
C-3 “Statement of Work” dated _______________
C-4 “Acceptance Test Plan” or “ATP” dated _______________
C-5 “Performance Schedule” dated _______________
Exhibit D Service Statement(s) of Work and “Service Terms and Conditions” (if applicable)
Exhibit E “System Acceptance Certificate”
Section 2 DEFINITIONS
Capitalized terms used in this Agreement have the following meanings:
2.1. “Acceptance Tests” means those tests described in the Acceptance Test Plan.
2.2. “Administrative User Credentials” means an account that has total access over the operating
system, files, end user accounts and passwords at either the System level or box level. Customer’s
personnel with access to the Administrative User Credentials may be referred to as the Administrative
User.
2.3. “Beneficial Use” means when Customer first uses the System or a Subsystem for operational
purposes (excluding training or testing).
2.4. “Confidential Information” means any information that is disclosed in written, graphic, verbal, or
machine-recognizable form, and is marked, designated, or identified at the time of disclosure as being
confidential or its equivalent; or if the information is in verbal form, it is identified as confidential at the time
of disclosure and is confirmed in writing within thirty (30) days of the disclosure. Confidential Information
does not include any information that: is or becomes publicly known through no wrongful act of the
receiving Party; is already known to the receiving Party without restriction when it is disclosed; is or
becomes, rightfully and without breach of this Agreement, in the receiving Party’s possession without any
obligation restricting disclosure; is independently developed by the receiving Party without breach of this
Agreement; or is explicitly approved for release by written authorization of the disclosing Party.
2.5. “Contract Price” means the price for the System, excluding applicable sales or similar taxes and
freight charges.
2.6. “Effective Date” means that date upon which the last Party executes this Agreement.
2.7. “Equipment” means the equipment that Customer purchases from Motorola under this
Agreement. Equipment that is part of the System is described in the Equipment List.
Motorola.CSA.FINAL.08.19.10.revision.doc 1 Motorola Contract No. 10-29146/JHJ

Digital Trunked P25 Radio System
2.8. “Force Majeure” means an event, circumstance, or act of a third party that is beyond a Party’s
reasonable control (e.g., an act of God, an act of the public enemy, an act of a government entity, strikes
or other labor disturbances, hurricanes, earthquakes, fires, floods, epidemics, embargoes, war, and riots).
2.9. “Infringement Claim” means a third party claim alleging that the Equipment manufactured by
Motorola or the Motorola Software directly infringes a United States patent or copyright.
2.10. “Motorola Software” means Software that Motorola or its affiliated company owns.
2.11. “Non-Motorola Software” means Software that another party owns.
2.12. “Open Source Software” (also called “freeware” or “shareware”) means software that has its
underlying source code freely available to evaluate, copy, and modify.
2.13. “Proprietary Rights” means the patents, patent applications, inventions, copyrights, trade secrets,
trademarks, trade names, mask works, know-how, and other intellectual property rights in and to the
Equipment and Software, including those created or produced by Motorola under this Agreement and any
corrections, bug fixes, enhancements, updates or modifications to or derivative works from the Software
whether made by Motorola or another party.
2.14. “Software” means the Motorola Software and Non-Motorola Software, in object code format that
is furnished with the System or Equipment.
2.15. “Specifications” means the functionality and performance requirements that are described in the
Technical and Implementation Documents.
2.16. “Subsystem” means a major part of the System that performs specific functions or operations.
Subsystems are described in the Technical and Implementation Documents.
2.17. “System” means the Equipment, Software, and incidental hardware and materials that are
combined together into an integrated system; the System is described in the Technical and
Implementation Documents.
2.18. “System Acceptance” means the Acceptance Tests have been successfully completed.
2.19. “Warranty Period” means one (1) year from the date of System Acceptance or Beneficial Use,
whichever occurs first.
Section 3 SCOPE OF AGREEMENT AND TERM
3.1. SCOPE OF WORK. Motorola will provide, install and test the System, and perform its other
contractual responsibilities, all in accordance with this Agreement. Customer will perform its contractual
responsibilities in accordance with this Agreement.
3.2. CHANGE ORDERS. Either Party may request changes within the general scope of this
Agreement. If a requested change causes an increase or decrease in the cost or time required to
perform this Agreement, the Parties will agree to an equitable adjustment of the Contract Price,
Performance Schedule, or both, and will reflect the adjustment in a change order. Neither Party is
obligated to perform requested changes unless both Parties execute a written change order.
3.3. TERM. Unless terminated in accordance with other provisions of this Agreement or extended by
mutual agreement of the Parties, the term of this Agreement begins on the Effective Date and continues
until the date of Final Project Acceptance or expiration of the Warranty Period, whichever occurs last.
3.4. ADDITIONAL EQUIPMENT OR SOFTWARE. For three (3) years after the Effective Date,
Customer may order additional Equipment or Software if it is then available. Each order must refer to this
Agreement and must specify the pricing and delivery terms. Notwithstanding any additional or contrary

terms in the order, the applicable provisions of this Agreement (except for pricing, delivery, passage of
title and risk of loss to Equipment, warranty commencement, and payment terms) will govern the
purchase and sale of the additional Equipment or Software. Title and risk of loss to additional Equipment
will pass at shipment, warranty will commence upon delivery, and payment is due within twenty (20) days
after the invoice date. Motorola will send Customer an invoice as the additional Equipment is shipped or
Software is licensed. Alternatively, Customer may register with and place orders through Motorola Online
(“MOL”), and this Agreement will be the “Underlying Agreement” for those MOL transactions rather than
the MOL On-Line Terms and Conditions of Sale. MOL registration and other information may be found at
http://www.motorola.com/businessandgovernment/ and the MOL telephone number is (800) 814-0601.
3.5. MAINTENANCE SERVICE. During the Warranty Period, in addition to warranty services,
Motorola will provide maintenance services for the Equipment and support for the Motorola Software
pursuant to the Statement of Work set forth in Exhibit D. Those services and support are included in the
Contract Price. If Customer wishes to purchase additional maintenance and support services for the
Equipment during the Warranty Period, or any maintenance and support services for the Equipment
either during the Warranty Period or after the Warranty Period, the description of and pricing for the
services will be set forth in a separate document. If Customer wishes to purchase extended support for
the Motorola Software after the Warranty Period, it may do so by ordering software subscription services.
Unless otherwise agreed by the parties in writing, the terms and conditions applicable to those
maintenance, support or software subscription services will be Motorola’s standard Service Terms and
Conditions, together with the appropriate statements of work.
3.6. MOTOROLA SOFTWARE. Any Motorola Software, including subsequent releases, is licensed to
Customer solely in accordance with the Software License Agreement. Customer hereby accepts and
agrees to abide by all of the terms and restrictions of the Software License Agreement.
3.7. NON-MOTOROLA SOFTWARE. Any Non-Motorola Software is licensed to Customer in

accordance with the standard license, terms, and restrictions of the copyright owner on the Effective Date
unless the copyright owner has granted to Motorola the right to sublicense the Non-Motorola Software
pursuant to the Software License Agreement, in which case it applies and the copyright owner will have
all of Licensor’s rights and protections under the Software License Agreement. Motorola makes no
representations or warranties of any kind regarding Non-Motorola Software. Non-Motorola Software may
include Open Source Software. All Open Source Software is licensed to Customer in accordance with,
and Customer agrees to abide by, the provisions of the standard license of the copyright owner and not
the Software License Agreement. Upon request by Customer, Motorola will use commercially reasonable
efforts to determine whether any Open Source Software will be provided under this Agreement; and if so,
identify the Open Source Software and provide to Customer a copy of the applicable standard license (or
specify where that license may be found); and provide to Customer a copy of the Open Source Software
source code if it is publicly available without charge (although a distribution fee or a charge for related
services may be applicable).
3.8. SUBSTITUTIONS. At no additional cost to Customer, Motorola may substitute any Equipment,
Software, or services to be provided by Motorola, if the substitute meets or exceeds the Specifications
and is of equivalent or better quality to the Customer. Any substitution will be reflected in a change order.
3.9. OPTIONAL EQUIPMENT OR SOFTWARE. This paragraph applies only if a “Priced Options”
exhibit is shown in Section 1, or if the parties amend this Agreement to add a Priced Options exhibit.
During the term of the option as stated in the Priced Options exhibit (or if no term is stated, then for one
(1) year after the Effective Date), Customer has the right and option to purchase the equipment, software,
and related services that are described in the Priced Options exhibit. Customer may exercise this option
by giving written notice to Seller which must designate what equipment, software, and related services
Customer is selecting (including quantities, if applicable). To the extent they apply, the terms and
conditions of this Agreement will govern the transaction; however, the parties acknowledge that certain
provisions must be agreed upon, and they agree to negotiate those in good faith promptly after Customer
delivers the option exercise notice. Examples of provisions that may need to be negotiated are: specific
lists of deliverables, statements of work, acceptance test plans, delivery and implementation schedules,

payment terms, maintenance and support provisions, additions to or modifications of the Software
License Agreement, hosting terms, and modifications to the acceptance and warranty provisions.
Section 4 PERFORMANCE SCHEDULE
The Parties will perform their respective responsibilities in accordance with the Performance Schedule.
By executing this Agreement, Customer authorizes Motorola to proceed with contract performance.
Section 5 CONTRACT PRICE, PAYMENT AND INVOICING
5.1. CONTRACT PRICE. The Contract Price in U.S. dollars is $________________________. If

applicable, a pricing summary is included with the Payment Schedule. Motorola has priced the services,
Software, and Equipment as an integrated system. A reduction in Software or Equipment quantities, or
services, may affect the overall Contract Price, including discounts if applicable.
5.2. INVOICING AND PAYMENT. Motorola will submit invoices to Customer according to the
Payment Schedule. Except for a payment that is due on the Effective Date, Customer will make
payments to Motorola within twenty (20) days after the date of each invoice. Customer will make
payments when due in the form of a wire transfer, check, or cashier’s check from a U.S. financial
institution. Overdue invoices will bear simple interest at the maximum allowable rate. For reference, the
Federal Tax Identification Number for Motorola, Inc. is 36-1115800.
5.3. FREIGHT, TITLE, AND RISK OF LOSS. Motorola will pre-pay and add all freight charges to the
invoices. Title to the Equipment will pass to Customer upon shipment. Title to Software will not pass to
Customer at any time. Risk of loss will pass to Customer upon delivery of the Equipment to the
Customer. Motorola will pack and ship all Equipment in accordance with good commercial practices.
5.4. INVOICING AND SHIPPING ADDRESSES. Invoices will be sent to the Customer at the following
address:
____________________________________________________________________________________
____________________________________________________________________________________
The address which is the ultimate destination where the Equipment will be delivered to Customer is:
____________________________________________________________________________________
____________________________________________________________________________________
The Equipment will be shipped to the Customer at the following address (insert if this information is
known):
____________________________________________________________________________________
____________________________________________________________________________________
Customer may change this information by giving written notice to Motorola.
Section 6 SITES AND SITE CONDITIONS
6.1. ACCESS TO SITES. In addition to its responsibilities described elsewhere in this Agreement,
Customer will provide a designated project manager; all necessary construction and building permits,
zoning variances, licenses, and any other approvals that are necessary to develop or use the sites and
mounting locations; and access to the work sites or vehicles identified in the Technical and
Implementation Documents as reasonably requested by Motorola so that it may perform its duties in
accordance with the Performance Schedule and Statement of Work. If the Statement of Work so
indicates, Motorola may assist Customer in the local building permit process.
6.2. SITE CONDITIONS. Customer will ensure that all work sites it provides will be safe, secure, and
in compliance with all applicable industry and OSHA standards. To the extent applicable and unless the
Statement of Work states to the contrary, Customer will ensure that these work sites have adequate:
physical space; air conditioning and other environmental conditions; adequate and appropriate electrical

power outlets, distribution, equipment and connections; and adequate telephone or other communication
lines (including modem access and adequate interfacing networking capabilities), all for the installation,
use and maintenance of the System. Before installing the Equipment or Software at a work site, Motorola
will inspect the work site and advise Customer of any apparent deficiencies or non-conformities with the
requirements of this Section. This Agreement is predicated upon normal soil conditions as defined by the
version of E.I.A. standard RS-222 in effect on the Effective Date.
6.3. SITE ISSUES. If a Party determines that the sites identified in the Technical and Implementation
Documents are no longer available or desired, or if subsurface, structural, adverse environmental or
latent conditions at any site differ from those indicated in the Technical and Implementation Documents,
the Parties will promptly investigate the conditions and will select replacement sites or adjust the
installation plans and specifications as necessary. If change in sites or adjustment to the installation
plans and specifications causes a change in the cost or time to perform, the Parties will equitably amend
the Contract Price, Performance Schedule, or both, by a change order.
Section 7 TRAINING
Any training to be provided by Motorola to Customer will be described in the Statement of Work.
Customer will notify Motorola immediately if a date change for a scheduled training program is required.
If Motorola incurs additional costs because Customer reschedules a training program less than thirty (30)
days before its scheduled start date, Motorola may recover these additional costs.
Section 8 SYSTEM ACCEPTANCE
8.1. COMMENCEMENT OF ACCEPTANCE TESTING. Motorola will provide to Customer at least ten
(10) days notice before the Acceptance Tests commence. System testing will occur only in accordance
with the Acceptance Test Plan.
8.2. SYSTEM ACCEPTANCE. System Acceptance will occur upon successful completion of the
Acceptance Tests. Upon System Acceptance, the Parties will memorialize this event by promptly
executing a System Acceptance Certificate. If the Acceptance Test Plan includes separate tests for
individual Subsystems or phases of the System, acceptance of the individual Subsystem or phase will
occur upon the successful completion of the Acceptance Tests for the Subsystem or phase, and the
Parties will promptly execute an acceptance certificate for the Subsystem or phase. If Customer believes
the System has failed the completed Acceptance Tests, Customer will provide to Motorola a written notice
that includes the specific details of the failure. If Customer does not provide to Motorola a failure notice
within thirty (30) days after completion of the Acceptance Tests, System Acceptance will be deemed to
have occurred as of the completion of the Acceptance Tests. Minor omissions or variances in the System
that do not materially impair the operation of the System as a whole will not postpone System Acceptance
or Subsystem acceptance, but will be corrected according to a mutually agreed schedule.
8.3. BENEFICIAL USE. Customer acknowledges that Motorola’s ability to perform its implementation
and testing responsibilities may be impeded if Customer begins using the System before System
Acceptance. Therefore, Customer will not commence Beneficial Use before System Acceptance without
Motorola’s prior written authorization, which will not be unreasonably withheld. Motorola is not
responsible for System performance deficiencies that occur during unauthorized Beneficial Use. Upon
commencement of Beneficial Use, Customer assumes responsibility for the use and operation of the
System.
8.4 FINAL PROJECT ACCEPTANCE. Final Project Acceptance will occur after System Acceptance
when all deliverables and other work have been completed. When Final Project Acceptance occurs, the
parties will promptly memorialize this final event by so indicating on the System Acceptance Certificate.
Section 9 REPRESENTATIONS AND WARRANTIES
9.1. SYSTEM FUNCTIONALITY. Motorola represents that the System will perform in accordance
with the Specifications in all material respects. Upon System Acceptance or Beneficial Use, whichever

occurs first, this System functionality representation is fulfilled. Motorola is not responsible for System
performance deficiencies that are caused by ancillary equipment not furnished by Motorola which is
attached to or used in connection with the System or for reasons or parties beyond Motorola’s control,
such as natural causes; the construction of a building that adversely affects the microwave path reliability
or radio frequency (RF) coverage; the addition of frequencies at System sites that cause RF interference
or intermodulation; or Customer changes to load usage or configuration outside the Specifications.
9.2. EQUIPMENT WARRANTY. During the Warranty Period, Motorola warrants that the Equipment
under normal use and service will be free from material defects in materials and workmanship. If System
Acceptance is delayed beyond six (6) months after shipment of the Equipment by events or causes within
Customer’s control, this warranty expires eighteen (18) months after the shipment of the Equipment.
9.3. MOTOROLA SOFTWARE WARRANTY. Unless otherwise stated in the Software License
Agreement, during the Warranty Period, Motorola warrants the Motorola Software in accordance with the
terms of the Software License Agreement and the provisions of this Section 9 that are applicable to the
Motorola Software. If System Acceptance is delayed beyond six (6) months after shipment of the
Motorola Software by events or causes within Customer’s control, this warranty expires eighteen (18)
months after the shipment of the Motorola Software. TO THE EXTENT, IF ANY, THAT THERE IS A
SEPARATE LICENSE AGREEMENT PACKAGED WITH, OR PROVIDED ELECTRONICALLY WITH, A
PARTICULAR PRODUCT THAT BECOMES EFFECTIVE ON AN ACT OF ACCEPTANCE BY THE END
USER, THEN THAT AGREEMENT SUPERCEDES THIS SOFTWARE LICENSE AGREEMENT AS TO
THE END USER OF EACH SUCH PRODUCT.
9.4. EXCLUSIONS TO EQUIPMENT AND MOTOROLA SOFTWARE WARRANTIES. These

warranties do not apply to: (i) defects or damage resulting from: use of the Equipment or Motorola
Software in other than its normal, customary, and authorized manner; accident, liquids, neglect, or acts of
God; testing, maintenance, disassembly, repair, installation, alteration, modification, or adjustment not
provided or authorized in writing by Motorola; Customer’s failure to comply with all applicable industry and
OSHA standards; (ii) breakage of or damage to antennas unless caused directly by defects in material or
workmanship; (iii) Equipment that has had the serial number removed or made illegible; (iv) batteries
(because they carry their own separate limited warranty) or consumables; (v) freight costs to ship
Equipment to the repair depot; (vi) scratches or other cosmetic damage to Equipment surfaces that does
not affect the operation of the Equipment; and (vii) normal or customary wear and tear.
9.5. WARRANTY CLAIMS. To assert a warranty claim, Customer must notify Motorola in writing of
the claim before the expiration of the Warranty Period. Upon receipt of this notice, Motorola will
investigate the warranty claim. If this investigation confirms a valid warranty claim, Motorola will (at its
option and at no additional charge to Customer) repair the defective Equipment or Motorola Software,
replace it with the same or equivalent product, or refund the price of the defective Equipment or Motorola
Software. That action will be the full extent of Motorola’s liability for the warranty claim. If this
investigation indicates the warranty claim is not valid, then Motorola may invoice Customer for responding
to the claim on a time and materials basis using Motorola’s then current labor rates. Repaired or replaced
product is warranted for the balance of the original applicable warranty period. All replaced products or
parts will become the property of Motorola.
9.6. ORIGINAL END USER IS COVERED. These express limited warranties are extended by
Motorola to the original user purchasing the System for commercial, industrial, or governmental use only,
and are not assignable or transferable.
9.7. DISCLAIMER OF OTHER WARRANTIES. THESE WARRANTIES ARE THE COMPLETE

WARRANTIES FOR THE EQUIPMENT AND MOTOROLA SOFTWARE PROVIDED UNDER THIS
AGREEMENT AND ARE GIVEN IN LIEU OF ALL OTHER WARRANTIES. MOTOROLA DISCLAIMS
ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Section 10 DELAYS

10.1. FORCE MAJEURE. Neither Party will be liable for its non-performance or delayed performance if
caused by a Force Majeure. A Party that becomes aware of a Force Majeure that will significantly delay
performance will notify the other Party promptly (but in no event later than fifteen days) after it discovers
the Force Majeure. If a Force Majeure occurs, the Parties will execute a change order to extend the
Performance Schedule for a time period that is reasonable under the circumstances.
10.2. PERFORMANCE SCHEDULE DELAYS CAUSED BY CUSTOMER. If Customer (including its

other contractors) delays the Performance Schedule, it will make the promised payments according to the
Payment Schedule as if no delay occurred; and the Parties will execute a change order to extend the
Performance Schedule and, if requested, compensate Motorola for all reasonable charges incurred
because of the delay. Delay charges may include costs incurred by Motorola or its subcontractors for
additional freight, warehousing and handling of Equipment; extension of the warranties; travel;
suspending and re-mobilizing the work; additional engineering, project management, and standby time
calculated at then current rates; and preparing and implementing an alternative implementation plan.
Section 11 DISPUTES
The Parties will use the following procedure to address any dispute arising under this Agreement (a
“Dispute”).
11.1. GOVERNING LAW. This Agreement will be governed by and construed in accordance with the
laws of the State in which the System is installed.
11.2. NEGOTIATION. Either Party may initiate the Dispute resolution procedures by sending a notice
of Dispute (“Notice of Dispute”). The Parties will attempt to resolve the Dispute promptly through good
faith negotiations including 1) timely escalation of the Dispute to executives who have authority to settle
the Dispute and who are at a higher level of management than the persons with direct responsibility for
the matter and 2) direct communication between the executives. If the Dispute has not been resolved
within ten (10) days from the Notice of Dispute, the Parties will proceed to mediation.
11.3 MEDIATION. The Parties will choose an independent mediator within thirty (30) days of a notice
to mediate from either Party (“Notice of Mediation”). Neither Party may unreasonably withhold consent to
the selection of a mediator. If the Parties are unable to agree upon a mediator, either Party may request
that American Arbitration Association nominate a mediator. Each Party will bear its own costs of
mediation, but the Parties will share the cost of the mediator equally. Each Party will participate in the
mediation in good faith and will be represented at the mediation by a business executive with authority to
settle the Dispute.
11.4. LITIGATION, VENUE and JURISDICTION. If a Dispute remains unresolved for sixty (60) days
after receipt of the Notice of Mediation, either Party may then submit the Dispute to a court of competent
jurisdiction in the state in which the System is installed. Each Party irrevocably agrees to submit to the
exclusive jurisdiction of the courts in such state over any claim or matter arising under or in connection
with this Agreement.
11.5. CONFIDENTIALITY. All communications pursuant to subsections 11.2 and 11.3 will be treated
as compromise and settlement negotiations for purposes of applicable rules of evidence and any
additional confidentiality protections provided by applicable law. The use of these Dispute resolution
procedures will not be construed under the doctrines of laches, waiver or estoppel to affect adversely the
rights of either Party.
Section 12 DEFAULT AND TERMINATION
12.1 DEFAULT BY A PARTY. If either Party fails to perform a material obligation under this
Agreement, the other Party may consider the non-performing Party to be in default (unless a Force
Majeure causes the failure) and may assert a default claim by giving the non-performing Party a written
and detailed notice of default. Except for a default by Customer for failing to pay any amount when due
under this Agreement which must be cured immediately, the defaulting Party will have thirty (30) days

after receipt of the notice of default to either cure the default or, if the default is not curable within thirty
(30) days, provide a written cure plan. The defaulting Party will begin implementing the cure plan
immediately after receipt of notice by the other Party that it approves the plan. If Customer is the
defaulting Party, Motorola may stop work on the project until it approves the Customer’s cure plan.
12.2. FAILURE TO CURE. If a defaulting Party fails to cure the default as provided above in Section
12.1, unless otherwise agreed in writing, the non-defaulting Party may terminate any unfulfilled portion of
this Agreement. In the event of termination for default, the defaulting Party will promptly return to the non-
defaulting Party any of its Confidential Information. If Customer is the non-defaulting Party, terminates
this Agreement as permitted by this Section, and completes the System through a third Party, Customer
may as its exclusive remedy recover from Motorola reasonable costs incurred to complete the System to
a capability not exceeding that specified in this Agreement less the unpaid portion of the Contract Price.
Customer will mitigate damages and provide Motorola with detailed invoices substantiating the charges.
Section 13 INDEMNIFICATION
13.1. GENERAL INDEMNITY BY MOTOROLA. Motorola will indemnify and hold Customer harmless
from any and all liability, expense, judgment, suit, cause of action, or demand for personal injury, death,
or direct damage to tangible property which may accrue against Customer to the extent it is caused by
the negligence of Motorola, its subcontractors, or their employees or agents, while performing their duties
under this Agreement, if Customer gives Motorola prompt, written notice of any the claim or suit.
Customer will cooperate with Motorola in its defense or settlement of the claim or suit. This section sets
forth the full extent of Motorola’s general indemnification of Customer from liabilities that are in any way
related to Motorola’s performance under this Agreement.
13.2. GENERAL INDEMNITY BY CUSTOMER. Customer will indemnify and hold Motorola harmless
from any and all liability, expense, judgment, suit, cause of action, or demand for personal injury, death,
or direct damage to tangible property which may accrue against Motorola to the extent it is caused by the
negligence of Customer, its other contractors, or their employees or agents, while performing their duties
under this Agreement, if Motorola gives Customer prompt, written notice of any the claim or suit.
Motorola will cooperate with Customer in its defense or settlement of the claim or suit. This section sets
forth the full extent of Customer’s general indemnification of Motorola from liabilities that are in any way
related to Customer’s performance under this Agreement.
13.3. PATENT AND COPYRIGHT INFRINGEMENT.
13.3.1. Motorola will defend at its expense any suit brought against Customer to the extent it is based on
a third-party claim alleging that the Equipment manufactured by Motorola or the Motorola Software
(“Motorola Product”) directly infringes a United States patent or copyright (“Infringement Claim”).
Motorola’s duties to defend and indemnify are conditioned upon: Customer promptly notifying Motorola in
writing of the Infringement Claim; Motorola having sole control of the defense of the suit and all
negotiations for its settlement or compromise; and Customer providing to Motorola cooperation and, if
requested by Motorola, reasonable assistance in the defense of the Infringement Claim. In addition to
Motorola’s obligation to defend, and subject to the same conditions, Motorola will pay all damages finally
awarded against Customer by a court of competent jurisdiction for an Infringement Claim or agreed to, in
writing, by Motorola in settlement of an Infringement Claim.
13.3.2. If an Infringement Claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its
option and expense: (a) procure for Customer the right to continue using the Motorola Product; (b)
replace or modify the Motorola Product so that it becomes non-infringing while providing functionally
equivalent performance; or (c) accept the return of the Motorola Product and grant Customer a credit for
the Motorola Product, less a reasonable charge for depreciation. The depreciation amount will be
calculated based upon generally accepted accounting standards.
13.3.3. Motorola will have no duty to defend or indemnify for any Infringement Claim that is based upon:
(a) the combination of the Motorola Product with any software, apparatus or device not furnished by
Motorola; (b) the use of ancillary equipment or software not furnished by Motorola and that is attached to

or used in connection with the Motorola Product; (c) Motorola Product designed or manufactured in
accordance with Customer’s designs, specifications, guidelines or instructions, if the alleged infringement
would not have occurred without such designs, specifications, guidelines or instructions; (d) a
modification of the Motorola Product by a party other than Motorola; (e) use of the Motorola Product in a
manner for which the Motorola Product was not designed or that is inconsistent with the terms of this
Agreement; or (f) the failure by Customer to install an enhancement release to the Motorola Software that
is intended to correct the claimed infringement. In no event will Motorola’s liability resulting from its
indemnity obligation to Customer extend in any way to royalties payable on a per use basis or the
Customer’s revenues, or any royalty basis other than a reasonable royalty based upon revenue derived
by Motorola from Customer from sales or license of the infringing Motorola Product.
13.3.4. This Section 13 provides Customer’s sole and exclusive remedies and Motorola’s entire liability in
the event of an Infringement Claim. Customer has no right to recover and Motorola has no obligation to
provide any other or further remedies, whether under another provision of this Agreement or any other
legal theory or principle, in connection with an Infringement Claim. In addition, the rights and remedies
provided in this Section 13 are subject to and limited by the restrictions set forth in Section 14.
Section 14 LIMITATION OF LIABILITY
Except for personal injury or death, Motorola's total liability, whether for breach of contract, warranty,
negligence, strict liability in tort, indemnification, or otherwise, will be limited to the direct damages
recoverable under law, but not to exceed the price of the Equipment, Software, or services with respect to
which losses or damages are claimed. ALTHOUGH THE PARTIES ACKNOWLEDGE THE POSSIBILITY
OF SUCH LOSSES OR DAMAGES, THEY AGREE THAT MOTOROLA WILL NOT BE LIABLE FOR ANY
COMMERCIAL LOSS; INCONVENIENCE; LOSS OF USE, TIME, DATA, GOOD WILL, REVENUES,
PROFITS OR SAVINGS; OR OTHER SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL
DAMAGES IN ANY WAY RELATED TO OR ARISING FROM THIS AGREEMENT, THE SALE OR USE
OF THE EQUIPMENT OR SOFTWARE, OR THE PERFORMANCE OF SERVICES BY MOTOROLA
PURSUANT TO THIS AGREEMENT. This limitation of liability provision survives the expiration or
termination of the Agreement and applies notwithstanding any contrary provision. No action for contract
breach or otherwise relating to the transactions contemplated by this Agreement may be brought more
than one (1) year after the accrual of the cause of action, except for money due upon an open account.
Section 15 CONFIDENTIALITY AND PROPRIETARY RIGHTS
15.1. CONFIDENTIAL INFORMATION. During the term of this Agreement, the parties may provide
each other with Confidential Information. Each Party will: maintain the confidentiality of the other Party’s
Confidential Information and not disclose it to any third party, except as authorized by the disclosing Party
in writing or as required by a court of competent jurisdiction; restrict disclosure of the Confidential
Information to its employees who have a “need to know” and not copy or reproduce the Confidential
Information; take necessary and appropriate precautions to guard the confidentiality of the Confidential
Information, including informing its employees who handle the Confidential Information that it is
confidential and is not to be disclosed to others, but these precautions will be at least the same degree of
care that the receiving Party applies to its own confidential information and will not be less than
reasonable care; and use the Confidential Information only in furtherance of the performance of this
Agreement. Confidential Information is and will at all times remain the property of the disclosing Party,
and no grant of any proprietary rights in the Confidential Information is given or intended, including any
express or implied license, other than the limited right of the recipient to use the Confidential Information
in the manner and to the extent permitted by this Agreement.
15.2. PRESERVATION OF MOTOROLA’S PROPRIETARY RIGHTS. Motorola, the third party

manufacturer of any Equipment, and the copyright owner of any Non-Motorola Software own and retain
all of their respective Proprietary Rights in the Equipment and Software, and nothing in this Agreement is
intended to restrict their Proprietary Rights. All intellectual property developed, originated, or prepared by
Motorola in connection with providing to Customer the Equipment, Software, or related services remain
vested exclusively in Motorola, and this Agreement does not grant to Customer any shared development
rights of intellectual property. Except as explicitly provided in the Software License Agreement, Motorola

does not grant to Customer, either directly or by implication, estoppel, or otherwise, any right, title or
interest in Motorola’s Proprietary Rights. Customer will not modify, disassemble, peel components,
decompile, otherwise reverse engineer or attempt to reverse engineer, derive source code or create
derivative works from, adapt, translate, merge with other software, reproduce, distribute, sublicense, sell
or export the Software, or permit or encourage any third party to do so. The preceding sentence does not
apply to Open Source Software which is governed by the standard license of the copyright owner.
Section 16 GENERAL
16.1. TAXES. The Contract Price does not include any excise, sales, lease, use, property, or other
taxes, assessments or duties, all of which will be paid by Customer except as exempt by law. If Motorola
is required to pay any of these taxes, Motorola will send an invoice to Customer and Customer will pay to
Motorola the amount of the taxes (including any interest and penalties) within twenty (20) days after the
date of the invoice. Customer will be solely responsible for reporting the Equipment for personal property
tax purposes, and Motorola will be solely responsible for reporting taxes on its income or net worth.
16.2. ASSIGNABILITY AND SUBCONTRACTING. Except as provided herein, neither Party may
assign this Agreement or any of its rights or obligations hereunder without the prior written consent of the
other Party, which consent will not be unreasonably withheld. Any attempted assignment, delegation, or
transfer without the necessary consent will be void. Notwithstanding the foregoing, Motorola may assign
this Agreement to any of its affiliates or its right to receive payment without the prior consent of Customer.
In addition, in the event Motorola separates one or more of its businesses (each a “Separated Business”),
whether by way of a sale, establishment of a joint venture, spin-off or otherwise (each a “Separation
Event”), Motorola may, without the prior written consent of the other Party and at no additional cost to
Motorola, assign this Agreement such that it will continue to benefit the Separated Business and its
affiliates (and Motorola and its affiliates, to the extent applicable) following the Separation Event.
Motorola may subcontract any of the work, but subcontracting will not relieve Motorola of its duties under
this Agreement.
16.3 WAIVER. Failure or delay by either Party to exercise a right or power under this Agreement will
not be a waiver of the right or power. For a waiver of a right or power to be effective, it must be in a
writing signed by the waiving Party. An effective waiver of a right or power will not be construed as either
a future or continuing waiver of that same right or power, or the waiver of any other right or power.
16.4. SEVERABILITY. If a court of competent jurisdiction renders any part of this Agreement invalid or
unenforceable, that part will be severed and the remainder of this Agreement will continue in full force and
effect.
16.5. INDEPENDENT CONTRACTORS. Each Party will perform its duties under this Agreement as an
independent contractor. The Parties and their personnel will not be considered to be employees or
agents of the other Party. Nothing in this Agreement will be interpreted as granting either Party the right
or authority to make commitments of any kind for the other. This Agreement will not constitute, create, or
be interpreted as a joint venture, partnership or formal business organization of any kind.
16.6. HEADINGS AND SECTION REFERENCES. The section headings in this Agreement are
inserted only for convenience and are not to be construed as part of this Agreement or as a limitation of
the scope of the particular section to which the heading refers. This Agreement will be fairly interpreted in
accordance with its terms and conditions and not for or against either Party.
16.7. ENTIRE AGREEMENT. This Agreement, including all Exhibits, constitutes the entire agreement
of the Parties regarding the subject matter of the Agreement and supersedes all previous agreements,
proposals, and understandings, whether written or oral, relating to this subject matter. This Agreement
may be amended or modified only by a written instrument signed by authorized representatives of both
Parties. The preprinted terms and conditions found on any Customer purchase order, acknowledgment
or other form will not be considered an amendment or modification of this Agreement, even if a
representative of each Party signs that document.

16.8. NOTICES. Notices required under this Agreement to be given by one Party to the other must be
in writing and either personally delivered or sent to the address shown below by certified mail, return
receipt requested and postage prepaid (or by a recognized courier service, such as Federal Express,
UPS, or DHL), or by facsimile with correct answerback received, and will be effective upon receipt:
Customer Motorola, Inc.

Attn: ______________________________ Attn: Judy Jean-Pierre, Law Department
__________________________________ 1301 E. Algonquin Road, ILO2-SH5
__________________________________ Schaumburg, IL 60196
email: ______________________________ email: Judy.Jean-Pierre@motorola.com
16.9. COMPLIANCE WITH APPLICABLE LAWS. Each Party will comply with all applicable federal,
state, and local laws, regulations and rules concerning the performance of this Agreement or use of the
System. Customer will obtain and comply with all Federal Communications Commission (“FCC”) licenses
and authorizations required for the installation, operation and use of the System before the scheduled
installation of the Equipment. Although Motorola might assist Customer in the preparation of its FCC
license applications, neither Motorola nor any of its employees is an agent or representative of Customer
in FCC or other matters.
16.10. AUTHORITY TO EXECUTE AGREEMENT. Each Party represents that it has obtained all
necessary approvals, consents and authorizations to enter into this Agreement and to perform its duties
under this Agreement; the person executing this Agreement on its behalf has the authority to do so; upon
execution and delivery of this Agreement by the Parties, it is a valid and binding contract, enforceable in
accordance with its terms; and the execution, delivery, and performance of this Agreement does not
violate any bylaw, charter, regulation, law or any other governing authority of the Party.
16.11. ADMINISTRATOR LEVEL ACCOUNT ACCESS. Motorola will provide Customer with
Administrative User Credentials. Customer agrees to only grant Administrative User Credentials to those
personnel with the training or experience to correctly use the access. Customer is responsible for
protecting Administrative User Credentials from disclosure and maintaining Credential validity by, among
other things, updating passwords when required. Customer may be asked to provide valid Administrative
User Credentials when in contact with Motorola System support. Customer understands that changes
made as the Administrative User can significantly impact the performance of the System. Customer
agrees that it will be solely responsible for any negative impact on the System or its users by any such
changes. System issues occurring as a result of changes made by an Administrative User may impact
Motorola’s ability to perform its obligations under the Agreement or its Maintenance and Support
Agreement. In such cases, a revision to the appropriate provisions of the Agreement, including the
Statement of Work, may be necessary. To the extent Motorola provides assistance to correct any issues
caused by or arising out of the use of or failure to maintain Administrative User Credentials, Motorola will
be entitled to bill Customer and Customer will pay Motorola on a time and materials basis for resolving the
issue.
16.12. SURVIVAL OF TERMS. The following provisions will survive the expiration or termination of this
Agreement for any reason: Section 3.6 (Motorola Software); Section 3.7 (Non-Motorola Software); if any
payment obligations exist, Sections 5.1 and 5.2 (Contract Price and Invoicing and Payment); Subsection
9.7 (Disclaimer of Implied Warranties); Section 11 (Disputes); Section 14 (Limitation of Liability); and
Section 15 (Confidentiality and Proprietary Rights); and all of the General provisions in Section 16.
The Parties hereby enter into this Agreement as of the Effective Date.
Motorola, Inc. Customer
By: ______________________________ By: ______________________________

Name: ___________________________ Name: ____________________________
Title: ____________________________ Title: _____________________________
Date: ____________________________ Date: ____________________________

Exhibit A
SOFTWARE LICENSE AGREEMENT
This Exhibit A Software License Agreement ("Agreement") is between Motorola, Inc., (“Motorola"), and
Floyd County, Georgia (“Licensee”).
For good and valuable consideration, the parties agree as follows:
Section 1 DEFINITIONS
1.1 “Designated Products” means products provided by Motorola to Licensee with which or for which
the Software and Documentation is licensed for use.
1.2 “Documentation” means product and software documentation that specifies technical and
performance features and capabilities, and the user, operation and training manuals for the Software
(including all physical or electronic media upon which such information is provided).
1.3 “Open Source Software” means software with either freely obtainable source code, license for
modification, or permission for free distribution.
1.4 “Open Source Software License” means the terms or conditions under which the Open Source
Software is licensed.
1.5 “Primary Agreement” means the agreement to which this exhibit is attached.
1.6 “Security Vulnerability” means a flaw or weakness in system security procedures, design,
implementation, or internal controls that could be exercised (accidentally triggered or intentionally
exploited) and result in a security breach such that data is compromised, manipulated or stolen or the
system damaged.
1.7 “Software” (i) means proprietary software in object code format, and adaptations, translations, de-
compilations, disassemblies, emulations, or derivative works of such software; (ii) means any
modifications, enhancements, new versions and new releases of the software provided by Motorola; and
(iii) may contain one or more items of software owned by a third party supplier. The term "Software" does
not include any third party software provided under separate license or third party software not licensable
under the terms of this Agreement.
Section 2 SCOPE
Motorola and Licensee enter into this Agreement in connection with Motorola's delivery of certain
proprietary Software or products containing embedded or pre-loaded proprietary Software, or both. This
Agreement contains the terms and conditions of the license Motorola is providing to Licensee, and
Licensee’s use of the Software and Documentation.
Section 3 GRANT OF LICENSE
3.1. Subject to the provisions of this Agreement and the payment of applicable license fees, Motorola
grants to Licensee a personal, limited, non-transferable (except as permitted in Section 7) and non-
exclusive license under Motorola’s copyrights and Confidential Information (as defined in the Primary
Agreement) embodied in the Software to use the Software, in object code form, and the Documentation
solely in connection with Licensee's use of the Designated Products. This Agreement does not grant any
rights to source code.

3.2. If the Software licensed under this Agreement contains or is derived from Open Source Software,
the terms and conditions governing the use of such Open Source Software are in the Open Source
Software Licenses of the copyright owner and not this Agreement. If there is a conflict between the terms
and conditions of this Agreement and the terms and conditions of the Open Source Software Licenses
governing Licensee’s use of the Open Source Software, the terms and conditions of the license grant of
the applicable Open Source Software Licenses will take precedence over the license grants in this
Agreement. If requested by Licensee, Motorola will use commercially reasonable efforts to: (i) determine
whether any Open Source Software is provided under this Agreement; (ii) identify the Open Source
Software and provide Licensee a copy of the applicable Open Source Software License (or specify where
that license may be found); and, (iii) provide Licensee a copy of the Open Source Software source code,
without charge, if it is publicly available (although distribution fees may be applicable).
Section 4 LIMITATIONS ON USE
4.1. Licensee may use the Software only for Licensee's internal business purposes and only in
accordance with the Documentation. Any other use of the Software is strictly prohibited. Without limiting
the general nature of these restrictions, Licensee will not make the Software available for use by third
parties on a "time sharing," "application service provider," or "service bureau" basis or for any other
similar commercial rental or sharing arrangement.
4.2. Licensee will not, and will not allow or enable any third party to: (i) reverse engineer,
disassemble, peel components, decompile, reprogram or otherwise reduce the Software or any portion to
a human perceptible form or otherwise attempt to recreate the source code; (ii) modify, adapt, create
derivative works of, or merge the Software; (iii) copy, reproduce, distribute, lend, or lease the Software or
Documentation to any third party, grant any sublicense or other rights in the Software or Documentation
to any third party, or take any action that would cause the Software or Documentation to be placed in the
public domain; (iv) remove, or in any way alter or obscure, any copyright notice or other notice of
Motorola's proprietary rights; (v) provide, copy, transmit, disclose, divulge or make the Software or
Documentation available to, or permit the use of the Software by any third party or on any machine
except as expressly authorized by this Agreement; or (vi) use, or permit the use of, the Software in a
manner that would result in the production of a copy of the Software solely by activating a machine
containing the Software. Licensee may make one copy of Software to be used solely for archival, back-
up, or disaster recovery purposes; provided that Licensee may not operate that copy of the Software at
the same time as the original Software is being operated. Licensee may make as many copies of the
Documentation as it may reasonably require for the internal use of the Software.
4.3. Unless otherwise authorized by Motorola in writing, Licensee will not, and will not enable or allow
any third party to: (i) install a licensed copy of the Software on more than one unit of a Designated
Product; or (ii) copy onto or transfer Software installed in one unit of a Designated Product onto one other
device. Licensee may temporarily transfer Software installed on a Designated Product to another device
if the Designated Product is inoperable or malfunctioning, if Licensee provides written notice to Motorola
of the temporary transfer and identifies the device on which the Software is transferred. Temporary
transfer of the Software to another device must be discontinued when the original Designated Product is
returned to operation and the Software must be removed from the other device. Licensee must provide
prompt written notice to Motorola at the time temporary transfer is discontinued.
4.4. When using Motorola's Radio Service Software ("RSS"), Licensee must purchase a separate
license for each location at which Licensee uses RSS. Licensee's use of RSS at a licensed location does
not entitle Licensee to use or access RSS remotely. Licensee may make one copy of RSS for each
licensed location. Licensee shall provide Motorola with a list of all locations at which Licensee uses or
intends to use RSS upon Motorola’s request.
4.5. Licensee will maintain, during the term of this Agreement and for a period of two years thereafter,
accurate records relating to this license grant to verify compliance with this Agreement. Motorola or an
independent third party (“Auditor”) may inspect Licensee’s premises, books and records, upon reasonable
prior notice to Licensee, during Licensee’s normal business hours and subject to Licensee's facility and
security regulations. Motorola is responsible for the payment of all expenses and costs of the Auditor.

Any information obtained by Motorola and the Auditor will be kept in strict confidence by Motorola and the
Auditor and used solely for the purpose of verifying Licensee's compliance with the terms of this
Agreement.
Section 5 OWNERSHIP AND TITLE
Motorola, its licensors, and its suppliers retain all of their proprietary rights in any form in and to the
Software and Documentation, including, but not limited to, all rights in patents, patent applications,
inventions, copyrights, trademarks, trade secrets, trade names, and other proprietary rights in or relating
to the Software and Documentation (including any corrections, bug fixes, enhancements, updates,
modifications, adaptations, translations, de-compilations, disassemblies, emulations to or derivative works
from the Software or Documentation, whether made by Motorola or another party, or any improvements
that result from Motorola’s processes or, provision of information services). No rights are granted to
Licensee under this Agreement by implication, estoppel or otherwise, except for those rights which are
expressly granted to Licensee in this Agreement. All intellectual property developed, originated, or
prepared by Motorola in connection with providing the Software, Designated Products, Documentation or
related services, remains vested exclusively in Motorola, and Licensee will not have any shared
development or other intellectual property rights.
Section 6 LIMITED WARRANTY; DISCLAIMER OF WARRANTY
6.1. The commencement date and the term of the Software warranty will be a period of ninety (90)
days from Motorola's shipment of the Software (the "Warranty Period"). If Licensee is not in breach of
any of its obligations under this Agreement, Motorola warrants that the unmodified Software, when used
properly and in accordance with the Documentation and this Agreement, will be free from a reproducible
defect that eliminates the functionality or successful operation of a feature critical to the primary
functionality or successful operation of the Software. Whether a defect occurs will be determined by
Motorola solely with reference to the Documentation. Motorola does not warrant that Licensee’s use of
the Software or the Designated Products will be uninterrupted, error-free, completely free of Security
Vulnerabilities, or that the Software or the Designated Products will meet Licensee’s particular
requirements. Motorola makes no representations or warranties with respect to any third party software
included in the Software.
6.2 Motorola’s sole obligation to Licensee and Licensee’s exclusive remedy under this warranty is to
use reasonable efforts to remedy any material Software defect covered by this warranty. These efforts
will involve either replacing the media or attempting to correct significant, demonstrable program or
documentation errors or Security Vulnerabilities. If Motorola cannot correct the defect within a reasonable
time, then at Motorola’s option, Motorola will replace the defective Software with functionally-equivalent
Software, license to Licensee substitute Software which will accomplish the same objective, or terminate
the license and refund the Licensee’s paid license fee.
6.3. Warranty claims are described in the Primary Agreement.
6.4. The express warranties set forth in this Section 6 are in lieu of, and Motorola disclaims, any and
all other warranties (express or implied, oral or written) with respect to the Software or Documentation,
including, without limitation, any and all implied warranties of condition, title, non-infringement,
merchantability, or fitness for a particular purpose or use by Licensee (whether or not Motorola knows,
has reason to know, has been advised, or is otherwise aware of any such purpose or use), whether
arising by law, by reason of custom or usage of trade, or by course of dealing. In addition, Motorola
disclaims any warranty to any person other than Licensee with respect to the Software or Documentation.
Section 7 TRANSFERS
Licensee will not transfer the Software or Documentation to any third party without Motorola's prior written
consent. Motorola’s consent may be withheld at its discretion and may be conditioned upon transferee
paying all applicable license fees and agreeing to be bound by this Agreement. If the Designated
Products are Motorola's radio products and Licensee transfers ownership of the Motorola radio products

to a third party, Licensee may assign its right to use the Software (other than RSS and Motorola's
FLASHport® software) which is embedded in or furnished for use with the radio products and the related
Documentation; provided that Licensee transfers all copies of the Software and Documentation to the
transferee, and Licensee and the transferee sign a transfer form to be provided by Motorola upon
request, obligating the transferee to be bound by this Agreement.
Section 8 TERM AND TERMINATION
8.1 Licensee’s right to use the Software and Documentation will begin when the Primary Agreement
is signed by both parties and will continue for the life of the Designated Products with which or for which
the Software and Documentation have been provided by Motorola, unless Licensee breaches this
Agreement, in which case this Agreement and Licensee's right to use the Software and Documentation
may be terminated immediately upon notice by Motorola.
8.2 Within thirty (30) days after termination of this Agreement, Licensee must certify in writing to
Motorola that all copies of the Software have been removed or deleted from the Designated Products and
that all copies of the Software and Documentation have been returned to Motorola or destroyed by
Licensee and are no longer in use by Licensee.
8.3 Licensee acknowledges that Motorola made a considerable investment of resources in the
development, marketing, and distribution of the Software and Documentation and that Licensee's breach
of this Agreement will result in irreparable harm to Motorola for which monetary damages would be
inadequate. If Licensee breaches this Agreement, Motorola may terminate this Agreement and be
entitled to all available remedies at law or in equity (including immediate injunctive relief and repossession
of all non-embedded Software and associated Documentation unless Licensee is a Federal agency of the
United States Government).
Section 9 UNITED STATES GOVERNMENT LICENSING PROVISIONS
This Section applies if Licensee is the United States Government or a United States Government agency.
Licensee’s use, duplication or disclosure of the Software and Documentation under Motorola’s copyrights
or trade secret rights is subject to the restrictions set forth in subparagraphs (c)(1) and (2) of the
Commercial Computer Software-Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable,
unless they are being provided to the Department of Defense. If the Software and Documentation are
being provided to the Department of Defense, Licensee’s use, duplication, or disclosure of the Software
and Documentation is subject to the restricted rights set forth in subparagraph (c)(1)(ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. The
Software and Documentation may or may not include a Restricted Rights notice, or other notice referring
to this Agreement. The provisions of this Agreement will continue to apply, but only to the extent that they
are consistent with the rights provided to the Licensee under the provisions of the FAR or DFARS
mentioned above, as applicable to the particular procuring agency and procurement transaction.
Section 10 CONFIDENTIALITY
Licensee acknowledges that the Software and Documentation contain Motorola’s valuable proprietary
and Confidential Information and are Motorola’s trade secrets, and that the provisions in the Primary
Agreement concerning Confidential Information apply.
The Limitation of Liability provision is described in the Primary Agreement.
Section 12 NOTICES
Notices are described in the Primary Agreement.

Section 13 GENERAL
13.1. COPYRIGHT NOTICES. The existence of a copyright notice on the Software will not be
construed as an admission or presumption of publication of the Software or public disclosure of any trade
secrets associated with the Software.
13.2. COMPLIANCE WITH LAWS. Licensee acknowledges that the Software is subject to the laws
and regulations of the United States and Licensee will comply with all applicable laws and regulations,
including export laws and regulations of the United States. Licensee will not, without the prior
authorization of Motorola and the appropriate governmental authority of the United States, in any form
export or re-export, sell or resell, ship or reship, or divert, through direct or indirect means, any item or
technical data or direct or indirect products sold or otherwise furnished to any person within any territory
for which the United States Government or any of its agencies at the time of the action, requires an export
license or other governmental approval. Violation of this provision is a material breach of this Agreement.
13.3. ASSIGNMENTS AND SUBCONTRACTING. Motorola may assign its rights or subcontract its
obligations under this Agreement, or encumber or sell its rights in any Software, without prior notice to or
consent of Licensee.
13.4. GOVERNING LAW. This Agreement is governed by the laws of the United States to the extent
that they apply and otherwise by the internal substantive laws of the State to which the Software is
shipped if Licensee is a sovereign government entity, or the internal substantive laws of the State of
Illinois if Licensee is not a sovereign government entity. The terms of the U.N. Convention on Contracts
for the International Sale of Goods do not apply. In the event that the Uniform Computer Information
Transaction Act, any version of this Act, or a substantially similar law (collectively "UCITA") becomes
applicable to a party's performance under this Agreement, UCITA does not govern any aspect of this
Agreement or any license granted under this Agreement, or any of the parties' rights or obligations under
this Agreement. The governing law will be that in effect prior to the applicability of UCITA.
13.5. THIRD PARTY BENEFICIARIES. This Agreement is entered into solely for the benefit of
Motorola and Licensee. No third party has the right to make any claim or assert any right under this
Agreement, and no third party is deemed a beneficiary of this Agreement. Notwithstanding the foregoing,
any licensor or supplier of third party software included in the Software will be a direct and intended third
party beneficiary of this Agreement.
13.6. SURVIVAL. Sections 4, 5, 6.3, 7, 8, 9, 10, 11 and 13 survive the termination of this Agreement.
13.7. ORDER OF PRECEDENCE. In the event of inconsistencies between this Exhibit and the
Primary Agreement, the parties agree that this Exhibit prevails, only with respect to the specific subject
matter of this Exhibit, and not the Primary Agreement or any other exhibit as it applies to any other
subject matter.
13.8 SECURITY. Motorola uses reasonable means in the design and writing of its own Software and
the acquisition of third party Software to limit Security Vulnerabilities. While no software can be
guaranteed to be free from Security Vulnerabilities, if a Security Vulnerability is discovered, Motorola will
take the steps set forth in Section 6 of this Agreement.

Exhibit B
Payment Schedule
The Contract Price in U.S. dollars is ____________. Except for a payment that is due on the Effective
Date, Customer will make payments to Motorola within thirty (30) days after the date of each invoice.
Customer will make payments when due in the form of a check, cashier’s check, or wire transfer drawn on
a U.S. financial institution and in accordance with the following milestones.
1) 10% of Contract Price upon Execution;
2) 30% of Contract Price upon delivery and inventory of equipment by Floyd County designee of
network infrastructure components to Floyd County designated location(s).
3) 15% of Contract Price upon completion of Install
4) 15% of Contract Price upon satisfactory completion of audio quality and range coverage testing
5) 15% of Contract Price upon shipment of subscriber equipment and satisfactory completion of all
training.
6) 10% of Contract Price upon System Acceptance/Beneficial Use.
7) 5% of Contract Price upon Final Acceptance
Customer will complete inventory of equipment within five (5) business days of receipt of shipment.
Equipment will be deemed accepted by the Customer on the 6th business day for receipt of shipment if
the Customer has not completed the inventory within five (5) business days.
Motorola reserves the right to make partial shipments of equipment and to request payment upon
shipment of such equipment. In addition, Motorola reserves the right to invoice for installations or civil
work completed on a site-by-site basis, when applicable.


Exhibit C
MOTOROLA PROPOSAL DOCUMENTS


Exhibit D
Service Terms and Conditions and “Service Statements of Work”
Service Terms and Conditions
Motorola, Inc. (“Motorola”) and the customer named in this Agreement (“Customer”) hereby agree
as follows:
Section 1 APPLICABILITY
These Service Terms and Conditions apply to service contracts whereby Motorola will provide to
Customer either (1) maintenance, support, or other services under a Motorola Service Agreement, or (2)
installation services under a Motorola Installation Agreement.
Section 2 DEFINITIONS AND INTERPRETATION
2.1. “Agreement” means these Service Terms and Conditions; the cover page for the Service
Agreement or the Installation Agreement, as applicable; and any other attachments, all of which are
incorporated herein by this reference. In interpreting this Agreement and resolving any ambiguities, these
Service Terms and Conditions take precedence over any cover page, and the cover page takes
precedence over any attachments, unless the cover page or attachment states otherwise.
2.2. “Equipment” means the equipment that is specified in the attachments or is subsequently added
to this Agreement.
2.3. “Services” means those installation, maintenance, support, training, and other services described
in this Agreement.
Section 3 ACCEPTANCE
Customer accepts these Service Terms and Conditions and agrees to pay the prices set forth in the
Agreement. This Agreement becomes binding only when accepted in writing by Motorola. The term of
this Agreement begins on the “Start Date” indicated in this Agreement.
Section 4 SCOPE OF SERVICES

4.1. Motorola will provide the Services described in this Agreement or in a more detailed statement of
work or other document attached to this Agreement. At Customer’s request, Motorola may also provide
additional services at Motorola’s then-applicable rates for the services.
4.2. If Motorola is providing Services for Equipment, Motorola parts or parts of equal quality will be
used; the Equipment will be serviced at levels set forth in the manufacturer’s product manuals; and
routine service procedures that are prescribed by Motorola will be followed.
4.3. If Customer purchases from Motorola additional equipment that becomes part of the same
system as the initial Equipment, the additional equipment may be added to this Agreement and will be
billed at the applicable rates after the warranty for that additional equipment expires.
4.4. All Equipment must be in good working order on the Start Date or when additional equipment is
added to the Agreement. Upon reasonable request by Motorola, Customer will provide a complete serial
and model number list of the Equipment. Customer must promptly notify Motorola in writing when any
Equipment is lost, damaged, stolen or taken out of service. Customer’s obligation to pay Service fees for
this Equipment will terminate at the end of the month in which Motorola receives the written notice.

4.5. Customer must specifically identify any Equipment that is labeled intrinsically safe for use in
hazardous environments.
4.6. If Equipment cannot, in Motorola’s reasonable opinion, be properly or economically serviced for
any reason, Motorola may modify the scope of Services related to that Equipment; remove that
Equipment from the Agreement; or increase the price to Service that Equipment.
4.7. Customer must promptly notify Motorola of any Equipment failure. Motorola will respond to
Customer's notification in a manner consistent with the level of Service purchased as indicated in this
Agreement.
Section 5 EXCLUDED SERVICES

5.1. Service excludes the repair or replacement of Equipment that has become defective or damaged
from use in other than the normal, customary, intended, and authorized manner; use not in compliance
with applicable industry standards; excessive wear and tear; or accident, liquids, power surges, neglect,
acts of God or other force majeure events.
5.2. Unless specifically included in this Agreement, Service excludes items that are consumed in the
normal operation of the Equipment, such as batteries or magnetic tapes.; upgrading or reprogramming
Equipment; accessories, belt clips, battery chargers, custom or special products, modified units, or
software; and repair or maintenance of any transmission line, antenna, microwave equipment, tower or
tower lighting, duplexer, combiner, or multicoupler. Motorola has no obligations for any transmission
medium, such as telephone lines, computer networks, the internet or the worldwide web, or for Equipment
malfunction caused by the transmission medium.
Section 6 TIME AND PLACE OF SERVICE

Service will be provided at the location specified in this Agreement. When Motorola performs service at
Customer’s location, Customer will provide Motorola, at no charge, a non-hazardous work environment
with adequate shelter, heat, light, and power and with full and free access to the Equipment. Waivers of
liability from Motorola or its subcontractors will not be imposed as a site access requirement. Customer
will provide all information pertaining to the hardware and software elements of any system with which the
Equipment is interfacing so that Motorola may perform its Services. Unless otherwise stated in this
Agreement, the hours of Service will be 8:30 a.m. to 4:30 p.m., local time, excluding weekends and
holidays. Unless otherwise stated in this Agreement, the price for the Services exclude any charges or
expenses associated with helicopter or other unusual access requirements; if these charges or expenses
are reasonably incurred by Motorola in rendering the Services, Customer agrees to reimburse Motorola
for those charges and expenses.
Section 7 CUSTOMER Contact
Customer will provide Motorola with designated points of contact (list of names and phone numbers) that
will be available twenty-four (24) hours per day, seven (7) days per week, and an escalation procedure to
enable Customer’s personnel to maintain contact, as needed, with Motorola.
Section 8 PAYMENT
Unless alternative payment terms are stated in this Agreement, Motorola will invoice Customer in
advance for each payment period. All other charges will be billed monthly, and Customer must pay each
invoice in U.S. dollars within twenty (20) days of the invoice date. Customer will reimburse Motorola for
all property taxes, sales and use taxes, excise taxes, and other taxes or assessments that are levied as a
result of Services rendered under this Agreement (except income, profit, and franchise taxes of Motorola)
by any governmental entity.
Section 9 WARRANTY
Motorola warrants that its Services under this Agreement will be free of defects in materials and
workmanship for a period of ninety (90) days from the date the performance of the Services are
completed. In the event of a breach of this warranty, Customer’s sole remedy is to require Motorola to re-

perform the non-conforming Service or to refund, on a pro-rata basis, the fees paid for the non-
conforming Service. MOTOROLA DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
Section 10 DEFAULT/TERMINATION
10.1. If either party defaults in the performance of this Agreement, the other party will give to the non-
performing party a written and detailed notice of the default. The non-performing party will have thirty
(30) days thereafter to provide a written plan to cure the default that is acceptable to the other party and
begin implementing the cure plan immediately after plan approval. If the non-performing party fails to
provide or implement the cure plan, then the injured party, in addition to any other rights available to it
under law, may immediately terminate this Agreement effective upon giving a written notice of termination
to the defaulting party.
10.2. Any termination of this Agreement will not relieve either party of obligations previously incurred
pursuant to this Agreement, including payments which may be due and owing at the time of termination.
All sums owed by Customer to Motorola will become due and payable immediately upon termination of
this Agreement. Upon the effective date of termination, Motorola will have no further obligation to provide
Services.

Except for personal injury or death, Motorola's total liability, whether for breach of contract, warranty,
negligence, strict liability in tort, or otherwise, will be limited to the direct damages recoverable under law,
but not to exceed the price of twelve (12) months of Service provided under this Agreement. ALTHOUGH
THE PARTIES ACKNOWLEDGE THE POSSIBILITY OF SUCH LOSSES OR DAMAGES, THEY AGREE
THAT MOTOROLA WILL NOT BE LIABLE FOR ANY COMMERCIAL LOSS; INCONVENIENCE; LOSS
OF USE, TIME, DATA, GOOD WILL, REVENUES, PROFITS OR SAVINGS; OR OTHER SPECIAL,
INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES IN ANY WAY RELATED TO OR ARISING
FROM THIS AGREEMENT OR THE PERFORMANCE OF SERVICES BY MOTOROLA PURSUANT TO
THIS AGREEMENT. No action for contract breach or otherwise relating to the transactions contemplated
by this Agreement may be brought more than one (1) year after the accrual of the cause of action, except
for money due upon an open account. This limitation of liability will survive the expiration or termination
of this Agreement and applies notwithstanding any contrary provision.
Section 12 EXCLUSIVE TERMS AND CONDITIONS

12.1. This Agreement supersedes all prior and concurrent agreements and understandings between
the parties, whether written or oral, related to the Services, and there are no agreements or
representations concerning the subject matter of this Agreement except for those expressed herein. The
Agreement may not be amended or modified except by a written agreement signed by authorized
representatives of both parties.
12.2. Customer agrees to reference this Agreement on any purchase order issued in furtherance of this
Agreement, however, an omission of the reference to this Agreement will not affect its applicability. In no
event will either party be bound by any terms contained in a Customer purchase order,
acknowledgement, or other writings unless: the purchase order, acknowledgement, or other writing
specifically refers to this Agreement; clearly indicate the intention of both parties to override and modify
this Agreement; and the purchase order, acknowledgement, or other writing is signed by authorized
representatives of both parties.
Section 13 PROPRIETARY INFORMATION; CONFIDENTIALITY; INTELLECTUAL

PROPERTY RIGHTS
13.1. Any information or data in the form of specifications, drawings, reprints, technical information or
otherwise furnished to Customer under this Agreement will remain Motorola’s property, will be deemed
proprietary, will be kept confidential, and will be promptly returned at Motorola's request. Customer may
not disclose, without Motorola's written permission or as required by law, any confidential information or

data to any person, or use confidential information or data for any purpose other than performing its
obligations under this Agreement. The obligations set forth in this Section survive the expiration or
termination of this Agreement.
13.2. Unless otherwise agreed in writing, no commercial or technical information disclosed in any
manner or at any time by Customer to Motorola will be deemed secret or confidential. Motorola will have
no obligation to provide Customer with access to its confidential and proprietary information, including
cost and pricing data.
13.3. This Agreement does not grant directly or by implication, estoppel, or otherwise, any ownership
right or license under any Motorola patent, copyright, trade secret, or other intellectual property, including
any intellectual property created as a result of or related to the Equipment sold or Services performed
under this Agreement.
Section 14 FCC LICENSES AND OTHER AUTHORIZATIONS

Customer is solely responsible for obtaining licenses or other authorizations required by the Federal
Communications Commission or any other federal, state, or local government agency and for complying
with all rules and regulations required by governmental agencies. Neither Motorola nor any of its
employees is an agent or representative of Customer in any governmental matters.
Section 15 COVENANT NOT TO EMPLOY

During the term of this Agreement and continuing for a period of two (2) years thereafter, Customer will
not hire, engage on contract, solicit the employment of, or recommend employment to any third party of
any employee of Motorola or its subcontractors without the prior written authorization of Motorola. This
provision applies only to those employees of Motorola or its subcontractors who are responsible for
rendering services under this Agreement. If this provision is found to be overly broad under applicable
law, it will be modified as necessary to conform to applicable law.
Section 16 MATERIALS, TOOLS AND EQUIPMENT

All tools, equipment, dies, gauges, models, drawings or other materials paid for or furnished by Motorola
for the purpose of this Agreement will be and remain the sole property of Motorola. Customer will
safeguard all such property while it is in Customer’s custody or control, be liable for any loss or damage
to this property, and return it to Motorola upon request. This property will be held by Customer for
Motorola’s use without charge and may be removed from Customer’s premises by Motorola at any time
without restriction.
Section 17 GENERAL TERMS

17.1. If any court renders any portion of this Agreement unenforceable, the remaining terms will
continue in full force and effect.
17.2. This Agreement and the rights and duties of the parties will be interpreted in accordance with the
laws of the State in which the Services are performed.
17.3. Failure to exercise any right will not operate as a waiver of that right, power, or privilege.
17.4. Neither party is liable for delays or lack of performance resulting from any causes that are beyond
that party’s reasonable control, such as strikes, material shortages, or acts of God.
17.5. Motorola may subcontract any of the work, but subcontracting will not relieve Motorola of its
duties under this Agreement.
17.6. Except as provided herein, neither Party may assign this Agreement or any of its rights or
obligations hereunder without the prior written consent of the other Party, which consent will not be
unreasonably withheld. Any attempted assignment, delegation, or transfer without the necessary consent
will be void. Notwithstanding the foregoing, Motorola may assign this Agreement to any of its affiliates or

its right to receive payment without the prior consent of Customer. In addition, in the event Motorola
separates one or more of its businesses (each a “Separated Business”), whether by way of a sale,
establishment of a joint venture, spin-off or otherwise (each a “Separation Event”), Motorola may, without
the prior written consent of the other Party and at no additional cost to Motorola, assign this Agreement
such that it will continue to benefit the Separated Business and its affiliates (and Motorola and its
affiliates, to the extent applicable) following the Separation Event.
17.7. THIS AGREEMENT WILL RENEW, FOR AN ADDITIONAL ONE (1) YEAR TERM, ON EVERY
ANNIVERSARY OF THE START DATE UNLESS EITHER THE COVER PAGE SPECIFICALLY STATES
A TERMINATION DATE OR ONE PARTY NOTIFIES THE OTHER IN WRITING OF ITS INTENTION TO
DISCONTINUE THE AGREEMENT NOT LESS THAN THIRTY (30) DAYS OF THAT ANNIVERSARY
DATE. At the anniversary date, Motorola may adjust the price of the Services to reflect its current rates.
17.8. If Motorola provides Services after the termination or expiration of this Agreement, the terms and
conditions in effect at the time of the termination or expiration will apply to those Services and Customer
agrees to pay for those services on a time and materials basis at Motorola’s then effective hourly rates.


Exhibit E
System Acceptance Certificate
Customer Name: ______________________________________________________
Project Name: ________________________________________________________
This System Acceptance Certificate memorializes the occurrence of System Acceptance. Motorola and
Customer acknowledge that:
1. The Acceptance Tests set forth in the Acceptance Test Plan have been successfully completed.
2. The System is accepted.
Customer Representative: Motorola Representative:
Signature: ____________________________ Signature: ____________________________

Print Name: ___________________________ Print Name: ___________________________
Title: ________________________________ Title: ________________________________
Date: ________________________________ Date: ________________________________
FINAL PROJECT ACCEPTANCE:

Motorola has provided and Customer has received all deliverables, and Motorola has performed all other
work required for Final Project Acceptance.
Customer Representative: Motorola Representative:
Signature: ____________________________ Signature: ____________________________

Print Name: ___________________________ Print Name: ___________________________
Title: ________________________________ Title: ________________________________
Date: ________________________________ Date: ________________________________


Section 14. Product Literature
Product literature is provided on the following pages.

RFP# 101216
December 16, 2010
Product Literature 14-1


RFP# 101216
December 16, 2010
14-2 Product Literature

PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
G-SERIES SITE
EQUIPMENT FOR
ASTRO 25 SYSTEMS
®
FLEXIBLE DESIGN – SOFTWARE CONFIGURABLE
Motorola’s ASTRO 25 networks are LSM enables simulcast systems to be deployed with
greater site spacing without sacrificing coverage or
designed to meet the current and future
capability, resulting in fewer sites to build and maintain.
customer requirements for Project 25 This also allows current systems to deploy IP-based
solutions. The G-series portfolio of RF simulcast without the need to add fill-in sites.
stations, receivers, site controllers and
SERVICING MADE EASY
comparators, is designed to maximize The G-series site equipment has many features built in
channel up-time, simplify system to support ease of service. Six basic modules create the
migrations, and enable smaller, more entire G-series platform resulting in reduced spare parts
efficient site design while minimizing the inventory. Modules are hot-swappable with front-only
access required to ensure channels are back on the air
cost of ownership to the customer. in minimum possible time. Standard Battery Revert and
Charging capability is built into every G-series power
G-series equipment is designed so that many upgrades, supply thereby eliminating the need at the site for a
migrations, and conversions can be completed with only large Uninterrupted Power Supply (UPS) which saves
software installations. Information Assurance/Network valuable site space.
Security updates, migrations to new system releases,
and system migrations from Conventional to Trunking The equipment also has built in functionality such as
and from 12.5 kHz FDMA to 6.25e kHz TDMA can be Ultra High Stability Oscillators or GPS for frequency
completed simply with a software download. reference tuning which can significantly reduce or
eliminate site visits.
Software installations enable new features to be
quickly added to your existing system. Future upgrades, CUSTOMER-OPTIMIZED
for example, P25 Phase 2 TDMA, and activation of NETWORK SECURITY
Motorola’s Dynamic Dual Mode (dynamic assignment of Information Assurance capabilities are standard with
transmit modulations to a talkgroup based on subscriber G-series equipment and can be configured or disabled GTR 8000 Expandable Site
characteristics) can be enabled through a simple depending on your specific system maintenance and Subsystem
software installation. security requirements. G-series products provide the
necessary boundary defense capabilities required in
SIMULCAST mission critical infrastructure today including local user
Motorola is the industry-leader in simulcast system accounts and password controls, user privilege model
solutions with more mission critical systems fielded and support (2 levels), local and remote access services
fully-operational than any other LMR vendor systems controls, secure shell services support, SNMPv3, central
provider. G-series site equipment is designed with authentication via RADIUS, general OS and network
simulcast system design and functionality in mind.The services hardening, and device test services controls.
GTR 8000 Base Radios feature a linear modulation (LSM)
that provides industry-leading P25-compliant coverage in
700/800 MHz, UHF, & VHF.
PRODUCT SPEC SHEET
SYSTEM CONFIGURATIONS
ASTRO 25 CONVENTIONAL ASTRO 25 TRUNKING
ASTRO 25 Conventional is a feature-rich conventional GTR 8000 Base Radios, GCP 8000 Site Controllers,
system solution on the common-hardware G-series and GCM 8000 Comparators are the building blocks
platform. GTR 8000 Base Stations, GPW 8000 Receivers, of Motorola’s ASTRO 25 Trunking systems. Site
and GCM 8000 Comparators can be used together Repeater and Simulcast system architectures offer the
or separately to build everything from a small, single flexibility to deliver communications that fit customer
repeater site to a large, countywide or statewide requirements. ASTRO 25 Trunking is a fully scalable
receiver-voting or simulcast conventional system. solution from as small as a single Trunked site to large
statewide systems that include a mix of Site Repeater
The hardware will support IP-only or V.24 circuit system and Simulcast operation as well as additional data and
design while connectivity with consoles can be either mutual aid overlays. G-series equipment configured for
IP-based or 4-wire depending on migration plans and Trunking supports both V.24 circuit-based architectures
system-specific operational requirements. GTR 8000’s as well as state-of-the-art IP-based system designs.
can be configured for either base station or standalone
repeater operation. GPW 8000 receivers and GCM 8000 Motorola offers industry-leading channel resiliency in
comparators improve the in-bound subscriber signal Trunking systems with the GTR 8000 Expandable Site
coverage and re-broadcast a quality-improved composite Subsystem. The architecture ensures that no Single
signal respectively in simulcast or receiver-voting Point of Failure can remove more than one channel from
systems. service at the RF sites while the sites are simultaneously
simplified through the integration of base station
ASTRO 25 Conventional can also be deployed as a frequency references, Ethernet LAN switches, and
system overlay with ASTRO 25 Trunking systems network gateways.
by adding a GTR 8000 Base Radio configured for
conventional operation to an existing Trunking GTR 8000 Motorola also offers the industry’s only turn-key P25-
Expandable Site Subsystem and sharing the common compliant Trunking site with the ASTRO 25 Express
wide-area network connections as well as RF cavity System. The ASTRO 25 Express system is a GTR 8000
combiners and receiver multicouplers. Expandable Site Subsystem designed to operate as a
single-site solution. Stations, site controllers, Ethernet
ASTRO 25 DATA switches, RF combiners and multicouplers are all
ASTRO 25 Trunking and Conventional systems are integrated into a single rack or cabinet. If more capacity
offered with Integrated Voice & Data that enables is required, additional cabinets can be added to the site.
the customer to leverage their investment in voice
infrastructure for basic data needs.
For customers that require higher data throughput

while retaining the same coverage footprint, Motorola
offers 25 kHz HPD as an overlay on ASTRO 25 Trunking
systems.
PAGE 2
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT PRODUCTS

GTR 8000 EXPANDABLE SITE GTR 8000 SITE SUBSYSTEM
SUBSYSTEM This configuration supports Motorola’s 25 kHz High
A space-efficient, single rack design, the GTR 8000 Performance Data application, providing the redundant
Expandable Site Subsystem integrates up to six GTR site controllers and GTR 8000 Base Radio configured
8000 Base Radios, redundant GCP 8000 Site Controllers for data operation. The specially designed low-loss
or GPB 8000 Reference Distribution Modules, redundant RF system is designed to ensure that HPD signal
Ethernet LAN switches, redundant network gateways, coverage equals the coverage available from Motorola’s
transmit combiners, and receiver multicouplers. This IV&D solutions allowing complete data coverage in an
enables a highly resilient architecture that provides ASTRO 25 system without the inconvenience of fill-in
industry-leading protection against single-points-of- sites for coverage holes.
failure at the RF sites while providing a turn-key site
solution that minimizes site cabling connections and GCP 8000 SITE CONTROLLER
installation effort. Used at an ASTRO 25 Trunking site to assign voice
and data channels, manage and report alarms on site
It supports ASTRO 25 Simulcast & Site Repeater resources, provide Ethernet switching capability, and
Trunking operation, 25 kHz High Performance Data, and provide a frequency reference to GTR 8000 Base Radios.
Conventional operation when co-located with Trunking. The frequency reference is provided either via a GPS
When ordered as an ASTRO 25 Express System, the Receiver or an Ultra High Stability Oscillator. The nature
GTR 8000 Expandable Site Subsystem is the industry’s of these frequency references eliminates or minimizes
only turn-key, single-site Project 25 Trunking solution. site visits for frequency tuning servicing. GTR 8000 Site Subsystem
GTR 8000 BASE RADIO GCM 8000 COMPARATOR

Designed to support ASTRO 25 Trunking Simulcast, Performs frame-by-frame voting on multiple received
High Performance Data, and ASTRO 25 Conventional signals and recombines the frames to produce a signal
operation, the GTR 8000 Base Radios offer additional with the best possible audio quality. GPS launch-delay
design flexibility for infrastructure sites where timing ensures seamless broadcast of the voted frames
equipment may have to be interchanged individually from multiple voice signals into one high-quality transmit
during a migration or when used as a station signal. GPS launch-delay timing ensures seamless
replacement for QUANTAR or STR 3000 stations. broadcast of data packets from multiple voice signals
into one high quality transmit signal. Supports both
GPW 8000 RECEIVER trunking and conventional IP-based systems.
Increases in-bound signal coverage from subscribers in
conventional systems in both voting and simulcast voting
applications.
GTR 8000 Base Radio / GCP 8000 Site Controller / GCM 8000 Comparator / GPW 8000 Receiver
PAGE 3
PRODUCT SPEC SHEET
GTR 8000 EXPANDABLE SITE SUBSYSTEM

HPD INTEGRATED VOICE & DATA – TRUNKING OR CONVENTIONAL
GENERAL PERFORMANCE 700/800 MHz 700/800 MHz UHF: 380-524 MHz VHF: 136-174 MHz
Model Number SQMOISUM7054A SQMOISUM7054A SQMOISUM7054A SQMOISUM7054A
Number of Channels 1-5 1-6 1-6 1-6
Height* 90.4 in. (230 cm) 90.4 in. (230 cm) 90.4 in. (230 cm) 90.4 in. (230 cm)
Footprint (W x D)* 20.5 x 22.8 in. (52 x 58 cm) 20.5 x 22.8 in. (52 x 58 cm) 20.5 x 22.8 in. (52 x 58 cm) 20.5 x 22.8 in. (52 x 58 cm)
Weight (fully configured)* 520 lbs (235 kg) 520 lbs (235 kg) UHF 380-435 MHz: 475 lbs (215 kg) 475 lbs (215 kg)
UHF 450-512 MHz: 565 lbs (260 kg)
Temperature Range –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C)
Power Requirements
AC 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz
DC 43.2-60 VDC 43.2-60 VDC 43.2-60 VDC 43.2-60 VDC
Power Consumption
(fully configured) 2450 W C4FM: 3000 W C4FM: 3200 W C4FM: 3200 W
LSM: 2800 W LSM: 3500 W LSM: 2700 W
Input/Output Impedance 50 ohms 50 ohms 50 ohms 50 ohms
Antenna Connectors
Tx 7/16 Female 7/16 Female 7/16 Female N Female
Rx N Female N Female N Female BNC Female
Channel Spacing 25 kHz 12.5 kHz 12.5 kHz 12.5 kHz
Modulation
Tx 64QAM, 16QAM, QPSK C4FM, LSM C4FM, LSM C4FM, LSM
Rx 64QAM, 16QAM, QPSK C4FM C4FM C4FM
Frequency Stability GPS synchronized Repeater Site: 100 ppb/2 yr Repeater Site: 100 ppb/2 yr Repeater Site: 100 ppb/2 yr
Simulcast (Multisite): GPS synchronized Simulcast (Multisite): GPS synchronized Simulcast (Multisite): GPS synchronized
TRANSMITTER 700/800 MHz 700/800 MHz UHF: 380-524 MHz VHF: 136-174 MHz
(CABINET OUTPUT**)
Frequency Range 762-776, 851-870 MHz 762-776, 851-870 MHz 380-435, 435-524 MHz 136-174 MHz
Average Power output per channel 1-20 W 1-40 W C4FM:2-110W (380-450, 512-524 MHz) C4FM: 2-100 W
LSM: 2-100W (380-450, 512-524 MHz) LSM: 2-60 W
C4FM: 1-33W (450-512 MHz)
LSM: 1-30W (450-512 MHz)
Modulation Fidelity N/A 5% 5% 5%
EVM 10% N/A N/A N/A
Spurious and Harmonic
Emissions Attenuation 90 dB 90 dB 90 dB 90 dB
Emissions Designators 17K7D7D 8K70D1W, 8K10F1E, 8K70D7W, 8K70D1W, 8K10F1E 8K10F7W, 8K70D1W, 8K10F1E 8K10F7W,
8K10F7W, 8K10F1D, 16K0F3E, 8K10F1D, 8K70D7W, 16K0F3E, 8K10F1D, 8K70D7W, 16K0F3E,
9K80D7W, 11K0F3E 9K80D7W, 11K0F3E 9K80D7W, 11K0F3E
RECEIVER (TOP OF CABINET) 700/800 MHz 700/800 MHz UHF: 380-524 MHz VHF: 136-174 MHz
Frequency Range 792-825 MHz 792-825 MHz 380-435, 435-524 MHz 136-174 MHz
Sensitivity 1% Bit Error Rate Static (BER)
64 QAM –101 dBm NA NA NA
QPSK –115 dBm NA NA NA
C4FM NA –123 dBm –115.5 dBm (380-450, 512-524MHz) –117 dBm
–121.5 dBm (450-512 MHz)
Intermodulation Rejection 75 dB*** 80 dB 80 dB 80 dB
Adjacent Channel Rejection 50 dB*** 60 dB 60 dB 60 dB
Spurious and Image Response
Rejection 90 dB*** 100 dB 85 dB (380-435 MHz) 90 dB
110 dB (450-512 MHz)
Intermediate Frequency
1st 73.35 MHz 73.35 MHz 73.35 MHz 44.85 MHz
2nd 2.16 MHz 2.16 MHz 2.16 MHz 2.16 MHz
* X882AH 7.5 Ft Open Rack Option

** Includes Transmitter RF Distribution System for 700/800 MHz and UHF 450-512 MHz. Does not include Transmitter RF Distribution System for VHF and UHF 380-450, 512-524 MHz.
*** Reference signal is QPSK.
PAGE 4
PRODUCT SPEC SHEET
GTR 8000 EXPANDABLE SITE SUBSYSTEM (CONTINUED)

TRANSMITTER RF DISTRIBUTION SYSTEM
700/800 MHz UHF: 450-512 MHz
Frequency Range 762-776 or 851-870 MHz 450-512 MHz
Insertion Loss (150 kHz spacing) 3.1 dB typ 4.5 dB typ
Tx-Tx Isolation (150 kHz spacing) 32 dB 32 dB
RECEIVER RF DISTRIBUTION SYSTEM

700/800 MHz UHF: 450-512 MHz
Frequency Range 792-825 MHz 450-512 MHz
Typical Maximum Typical Maximum
Noise Figure 3.8 dB 5 dB 4.6 dB 5.5 dB
Gain 13 dB –16 to 24 dB adjustable 10 dB –16 to 24 dB adjustable
3rd Order Output Intercept 21 dBm 19 dBm
Preselector Bandwidth 792-825 MHz 2 or 3.5 MHz
RF Input Connector Type N N
RF Output Connector Type BNC BNC
GCP 8000 SITE CONTROLLER

GENERAL PERFORMANCE HPD IV&D
Model Number T7038A T7038A
Channel Capacity 5 Repeater Site: 28
Simulcast (Multicast): 30
Size (HxWxD) 5.25” x 19” x 18” (133 x 483 x 457 mm) 5.25” x 19” x 18” (133 x 483 x 457 mm)
Weight 40 lbs (18 kg) 40 lbs (18 kg)
Temperature Range –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C)
Rack Option 19” standard rack mountable 19” standard rack mountable
Frequency Stability GPS Synchronized Simulcast (Multisite): External
Repeater Site: 100 ppb/2 yr
ELECTRICAL HPD IV&D

Power Requirements AC: 90-264 VAC, 47-63 Hz AC: 90-264 VAC, 47-63 Hz
DC: 43.2-60 VDC DC: 43.2-60 VDC
Power Consumption AC: 160 W AC: 130 W
DC: 80 W DC: 60 W
GCM 8000 COMPARATOR

GENERAL PERFORMANCE IV&D AND CONVENTIONAL
Model Number T7321A
Channel Capacity 1 or 2
Size 5.25” x 19” x 18” (133 x 483 x 457 mm)
Weight 40 lbs (18 kg)
Operating Temperature Range –22 to 140 °F (–30 to 60°C)
Rack Option 19” standard rack mountable
Time Stability External Reference
Power Requirements 90-264 VAC, 47-63 Hz 43.2-60 VDC
Power Consumption
AC, 1 module 130 W
AC, 2 modules 160 W
DC, 1 module 60 W
DC, 2 modules 80 W
PAGE 5
PRODUCT SPEC SHEET
GTR 8000 BASE RADIO

HPD INTEGRATED VOICE & DATA – TRUNKING OR CONVENTIONAL
GENERAL PERFORMANCE 700/800 MHz 700/800 MHz UHF: 380-435 MHz VHF: 136-174 MHz
UHF: 435-524 MHz
Model Number T7039A T7039A T7039A T7039A
Size (HxWxD) 5.25” x 19” x 18” 5.25” x 19” x 18” 5.25” x 19” x 18” 5.25” x 19” x 18”
(133 x 483 x 457 mm) (133 x 483 x 457 mm) (133 x 483 x 457 mm) (133 x 483 x 457 mm)
Weight 46 lbs (21 kg) 46 lbs (21 kg) 46 lbs (21 kg) 46 lbs (21 kg)
Temperature Range –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C)
Power Requirements
AC 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz
DC 43.2-60 VDC 43.2-60 VDC 43.2-60 VDC 43.2-60 VDC
Power Consumption 450 W C4FM: 470 W C4FM: 500 W C4FM: 500 W
LSM: 530 W LSM: 550 W LSM: 410 W
Input/Output Impedance 50 ohms 50 ohms 50 ohms 50 ohms
Antenna Connectors
Tx N female N female N female N female
Rx BNC female BNC female BNC female BNC female
N female ** N female ** N female **
Channel Spacing 25 kHz 12.5 kHz 12.5 kHz 12.5 kHz
Modulation
Tx 64QAM, 16QAM, QPSK C4FM, LSM C4FM, LSM C4FM, LSM
Rx 64QAM, 16QAM, QPSK C4FM C4FM C4FM
Frequency Stability External Reference External Reference External Reference External Reference
Conventional: 100 ppb/2yr Conventional: 100 ppb/2yr Conventional: 100 ppb/2yr
TRANSMITTER 700/800 MHz 700/800 MHz UHF: 380-435 MHz VHF: 136-174 MHz
UHF: 435-524 MHz
Frequency Range 762-776, 851-870 MHz 762-776, 851-870 MHz 380-435, 435-524 MHz 136-174 MHz
Power output 2-50 W 2-100 W C4FM: 2-110 W C4FM: 2-100 W
LSM: 2-100 W LSM: 2-60 W
Electronic Bandwidth Full Bandwidth Full Bandwidth Full Bandwidth Full Bandwidth
Modulation Fidelity N/A 5% 5% 5%
EVM 10% N/A N/A N/A
Spurious and Harmonic
Emissions Attenuation 90 dB 90 dB 90 dB 90 dB
Emissions Designators 17K7D7D 8K70D1W, 8K10F1E, 8K70D7W, 8K70D1W, 8K10F1E, 8K10F7W, 8K70D1W, 8K10F1E, 8K10F7W,
8K10F7W, 8K10F1D, 16K0F3E, 8K10F1D, 8K70D7W, 16K0F3E, 8K10F1D, 8K70D7W, 16K0F3E,
9K80D7W, 11K0F3E 9K80D7W, 11K0F3E 9K80D7W, 11K0F3E
RECEIVER 700/800 MHz 700/800 MHz UHF: 380-435 MHz VHF: 136-174 MHz
UHF: 435-524 MHz
Frequency Range 792-825 MHz 792-825 MHz 380-435, 435-524 MHz 136-174 MHz
QPSK –111 dBm NA NA NA
C4FM NA –118 dBm –118 dBm –118 dBm
Intermodulation Rejection 75 dB* 80 dB 80 dB 80 dB
Adjacent Channel Rejection 50 dB* 60 dB 60 dB 60 dB
Rejection 85 dB* 85 dB 85 dB 90 dB
100 dB** 100 dB** 95 dB**
Intermediate Frequencies
1st 73.35 MHz 73.35 MHz 73.35 MHz 44.85 MHz
2nd 2.16 MHz 2.16 MHz 2.16 MHz 2.16 MHz
* Reference signal is QPSK.

** Optional Preselector
PAGE 6
PRODUCT SPEC SHEET
GPW 8000 RECEIVER

INTEGRATED VOICE & DATA – CONVENTIONAL
GENERAL PERFORMANCE 700/800 MHz UHF: 380-435 MHz VHF: 136-174 MHz
UHF: 435-524 MHz
Model Number T7540A T7540A T7540A
Size (HxWxD) 5.25” x 19” x 18” 5.25” x 19” x 18” 5.25” x 19” x 18”
(133 x 483 x 457mm) (133 x 483 x 457mm) (133 x 483 x 457mm)
Weight 35 lbs (16 kg) 35 lbs (16 kg) 35 lbs (16 kg)
Temperature Range –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C) –22 to 140 °F (–30 to 60°C)
Power Requirements
AC 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz 90-264 VAC, 47-63 Hz
DC 43.2-60 VDC 43.2-60 VDC 43.2-60 VDC
Power Consumption
AC 85 W 85 W 85 W
DC 50 W 50 W 50 W
Input/Output Impedance 50 ohms 50 ohms 50 ohms
Antenna Connectors BNC female BNC female BNC female
N female * N female * N female *
Channel Spacing 12.5 kHz 12.5 kHz 12.5 kHz
Modulation C4FM C4FM C4FM
Frequency Stability 100 ppb/2 years 100 ppb/2 years 100 ppb/2 years
RECEIVER 700/800 MHz UHF: 380-435 MHz VHF: 136-174 MHz

UHF: 435-524 MHz
Frequency Range 792-825 MHz 380-435, 435-524 MHz 136-174 MHz
C4FM –118 dBm –118 dBm –118 dBm
Intermodulation Rejection 80 dB 80 dB 80 dB
Adjacent Channel Rejection 60 dB 60 dB 60 dB
Rejection 8 5 dB* 85 dB 90 dB
100 dB* 100 dB* 95 dB*
Intermediate Frequencies
1st 73.35 MHz 73.35 MHz 44.85 MHz
2nd 2.16 MHz 2.16 MHz 2.16 MHz
* Optional Preselector
PAGE 7
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 RADIO NETWORKS
GTR 8000 SITE SUBSYSTEM

GENERAL PERFORMANCE INCLUDING RFDS
Model Number T7133A
Number of Channels 1
Height 27 RU, 50.4 in. (128 cm)
Footprint (W x D) 20.8 x 24.8 in. (52.8 x 62.9 cm)
Weight 225 lbs (102 kg)
Temperature Range –22 to 140 °F (–30 to 60°C)
Power Requirements AC: 90-264 VAC, 47-63 Hz
DC: 43.2-60 VDC
Power Consumption AC: 675 W
DC: 550 W
Input/Output Impedance 50 ohms
Antenna Connectors N Female
Channel Spacing 25 kHz
Modulation Tx: 64QAM, 16QAM, QPSK
Rx: 64QAM, 16QAM, QPSK
Frequency Stability GPS synchronized
TRANSMITTER INCLUDING RFDS RECEIVER INCLUDING RFDS

Frequency Range 762-792, 851-870 MHz Frequency Range 792-825 MHz
Power output 1-27 W Sensitivity 1% Bit Error Rate Static (BER) 64 QAM –101 dBm
Electronic Bandwidth 762-776, 851-870 MHz Sensitivity 1% Bit Error Rate Static (BER) 16 QAM –108 dBm
Error Vector Magnitude 10% Sensitivity 1% Bit Error Rate Static (BER) QPSK –115 dBm
Spurious and Harmonic Intermodulation Rejection* 75 dB
Emissions Attenuation 90 dB
Adjacent Channel Rejection* 50 dB
Emissions Designators 17K7D7W
Spurious and Image Response Rejection* 90 dB
Preselector Bandwidth 792-825 MHz
Intermediate Frequencies 1st: 73.35 MHz
2nd: 2.16 MHz
* Reference signal is QPSK.
FCC TYPE ACCEPTANCE

FCC Designation: Frequency Range Type Power Output Type Acceptance Number
762-776 MHz Transmitter HPD: 2-50 W ABZ89FC5812
IV&D: 2-100 W
851-870 MHz Transmitter HPD: 2-50 W ABZ89FC5810
IV&D: 2-100 W
792-825 MHz Receiver N/A ABZ89FR5811
406-435 MHz Transmitter 2-110 W ABZ89FC4821
406-435 MHz Receiver NA ABZ89FR4822
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. motorola.com/ASTRO25
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under
license. All other trademarks are the property of their respective owners. © 2010 Motorola, Inc. All rights reserved. Specifications subject to change without notice.
R3-11-2034I (1011)
Bird Dual Diversity Tower Top
®
Amplifier and Two Channel

Control Unit (CMU)
432-83H-01-T, 432-83H-01-C
(Motorola # DS43283H01T, # DS43283H01C)
Bird Technologies Group, TX RX Systems brand, Dual Diversity Tower-Top

Amplifier (TTA) system is a high performance, two channel quadrature-coupled
Low Noise Amplifier (LNA) designed to increase the performance of a Base
Transceiver Station (BTS) while ensuring reliable communications for critical
Public Safety applications. This increase in sensitivity can make up for the
imbalance between mobile and handheld users in critical systems and im-
prove marginal in-building penetration. The signal paths of the two channels
are carefully matched to maximize the aperture gain of a dual diversity
radio system.
The TTA consists of two components: the Tower-Top Amplifier mounted

close to the antenna and the Two Channel Control Unit. The CMU is specifi-
cally designed to interface directly with one or two GTR8000 receive net-
works. Each of the LNA’s within the TTA are of quadrature design with
separate bias circuits for maximum redundancy and superior intermodula-
tion (IM) performance. LNA current monitoring of each amplifier is per-
formed in the Control Unit to assess the health of the TTA system. Relay dry
contact closure alarms are generated in the rare occurrence of a fault. An
FEATURES
auxiliary “Test” transmission line may be used to help measure receiver Two channels of Redundant, quadrature LNA’s ensures re-
sensitivity or diagnose damage or degradation of the primary transmission liable communications.
line. This system can be used in any P25 land mobile radio application,
PolyPhaserTM impulse suppressors provide protection
HPD, and standard systems. from lightning damage on all I/O ports.
RF test port enables gain, sensitivity and degradation

PROBLEM SOLUTION measurements from ground level.
Your tower is high and feed-line loss is TTA establishes superior noise figure prior Form-C contacts for fault reporting through a supervisory
degrading noise figure. to feed-line loss. system.
New Diversity Radio systems have critical The Dual Diversity TTA conforms to all Test Output on each channel allows simple monitoring of
requirements. Motorola requirements for a P25 diver- actual signal levels into BTS radios.
sity radio system.
Bird® Dual Diversity Tower Top Amplifier and Two Channel Control Unit (CMU)
432-83H-01-T, 432-83H-01-C
(Motorola # DS43283H01T, # DS43283H01C)
S PECIFICATIONS, S YSTEMS COMBINED S PECIFICATIONS, CONTROL UNIT PRESELECTOR

Bandwidth 792 – 824 MHz Frequency Range 792-824 MHz
System Noise Figure 1.7 dB Typ, 2.0 dB Max Passband Insertion Loss < 3.0 dB
System IIP3 +13 dBm min Passband Return Loss >12 dB
System Net Gain 15 dB Min Stopband Rejection >50 dB @ 776 and 851 MHz
TTA Net Gain Fully settable by electronic attenuator
Filter Rejection 110 dB min, 776 and 851 MHz SPECIFICATIONS, 2 CHANNEL CONTROL UNIT
Net Weight Approximately 37 lbs.
Net Gain -11.5 dB typ.
P ART NUMBER, P RODUCT RF Input Impedance 50 ohms nominal
Input VSWR < 2:1
Dual Diversity Tower 432-83H-01-T
unit alone
RESERVE GAIN ADJUSTMENT (EACH CHANNEL)
2-Port Control Unit 432-83H-01-C
(90-240VAC) Power Coarse 0 – 15.5 dB in 0.5 dB steps
-48V Option 432-83H-01-C-48 Fine 0-0.8 dB in < 0.1 dB steps (Fine adjustment
accommodates accurate channel to channel
S PECIFICATIONS, T OWER TOP AMPLIFIER amplitude balance)
2 BNC Female Outputs Labeled RxA, RxA-Test, RxB, RxB-Test
Frequency Range 792-824 MHz for each channel
Net Gain 30 dB Typ. (Each Channel)
Noise Figure (Typ./Max) 1.9 dB / 2.0 dB CONNECTORS
IIP3: >13 dBm
N-Female RF Connections TTA, A, B and Test Lines
Integrated Test Port 33 dB (Typ.)
Isolation BNC Female Input to Test Line (on front panel)
Outputs to BTS radios
Antenna Port VSWR 1.5 :1 Typ.
Ethernet Rj45 Access from front panel for firmware update only
Power Requirements 12 VDC @ 1.3A max
Alarm Contacts Two Form C Contacts. Separate alarms for A
Lightning Protection Impulse Suppression on all external connectors
and B Channels
Operating Temp Range -30°C to +60°C
Power Requirements 48 VDC or 85-250 VAC 50/60 Hz, depending
Enclosure Modified NEMA 4X Water resistant Polyester Housing upon model
Connectors N-Female 120VAC input current TBD
Dimensions (HWD) 14”x12”x7” -48V DC input current TBD
Weight Approx 25 lbs Operating Temperature 0°C to +50°C at non-condensing humidity
Enclosure Standard EIA 19” Rack Mounting
SPECIFICATIONS, PRESELECTOR Dimensions (HWD) 1 RU x 19” x 18”
Net Weight 12 lbs
Passband Insertion Loss <0.8 dB
Passband Return Loss >15 dB 48V OPTIONS
Stopband Rejection >60 dB @ 776 and 851 MHz
75-83H-01EXp Expandable up to 32-ports by adding 16 port
Motorola # DS7583H01EXP expansion kit (only on MCU)
Y OU’RE HEARD, LOUD AND CLEAR.
30303 Aurora Rd. :: Solon, OH 44139 :: 866.695.4569 :: www.bird-technologies.com
Bird® Technologies Group combines the industry leading brands of both Bird Electronic and TX RX Systems and is a global, innovative supplier of RF products, sys-
tems, services and educational solutions. Bird® Technologies Group reserved the right to modify specifications or discontinue any product without notice.
Dual DiversityTTA-43286A01M:5000-XT 3/16/2010 1:18 PM Page 1
Bird Dual Diversity Tower Top

Amplifier and Multicoupler
Control Unit (MCU)
432-83H-01-T, 432-83H-01-M
(Motorola # DS43283H01T, # DS43283H01M)
Bird Technologies Group, TX RX Systems brand, The Dual Diversity Tower-

Top Amplifier (TTA) system is a high performance, two channel quadra-
ture-coupled Low Noise Amplifier (LNA) designed to increase the
performance of a Base Transceiver Station (BTS) while ensuring reliable
communications for critical Public Safety applications. This increase in
sensitivity can make up for the imbalance between mobile and handheld
users in critical systems and improve marginal in-building penetration.
The signal paths of the two channels are carefully matched to maximize
the aperture gain of a dual diversity radio system.
The TTA consists of two components: the Tower-Top Amplifier mounted

close to the antenna and the receiver Multicoupler Control Unit. The MCU
is designed to interface directly to 16 individual receivers operating in
dual diversity mode or single mode. Each of the LNA’s within the TTA are
of quadrature design with separate bias circuits for maximum redun-
dancy and superior intermodulation (IM) performance. LNA current moni-
toring of each amplifier is performed in the Control Unit to assess the
health of the TTA system. Relay dry contact closure alarms are generated FEATURES
in the rare occurrence of a fault. An auxiliary “test” transmission line Two channels of Redundant, quadrature LNA’s ensures
may be used to help measure receiver sensitivity or diagnose damage or reliable communications.
degradation of the primary transmission line. PolyPhaserTM impulse suppressors provide protection
from lightning damage on all I/O ports.
PROBLEM SOLUTION RF test port enables gain, sensitivity and degradation

measurements from ground level.
Your tower is high and feed-line loss is TTA establishes superior noise figure prior
Form-C contacts for fault reporting through a supervisory
degrading noise figure. to feed-line loss.
system.
New Diversity Radio systems have critical The Dual Diversity TTA conforms to all
Ethernet interface for fast ATP mode switching and alarm
requirements. Motorola requirements for a P25 diver-
details.
sity radio system.
Dual 16 port output with expansion capability.
Dual DiversityTTA-43286A01M:5000-XT 3/16/2010 1:18 PM Page 2
Bird® Dual Diversity Tower Top Amplifier and

Multicoupler Control Unit (MCU)
432-83H-01-T, 432-83H-01-M
(Motorola # DS43283H01T, # DS43283H01M)
S PECIFICATIONS, S YSTEM COMBINED S PECIFICATIONS, P RESELECTOR FILTER

Bandwidth 792 – 824 MHz Frequency Range 792-824 MHz
System Noise Figure 2.7 dB Typ, 3.0 dB Max Insertion Loss < 3.0 dB
System IIP3 +15 dBm min Return Loss >12 dB
System Net Gain > 15 dB Min Stopband Rejection >50 dB @ 776 and 851 MHz
TTA Net Gain Fully settable by electronic attenuator
Filter Rejection 110 dB min, 776 and 851 MHz
S PECIFICATIONS, D UAL 16-PORT RECEIVER MULTICOUPLER
Net Weight TBD lbs. Insertion Loss < 3.0 dB
Ship Weight TBD lbs Return Loss >12 dB
Stopband Rejection 50 dB Min @ 776 and 851 MHz
P ART NUMBER, P RODUCT Multicoupler Net Gain +1 dB typ., 0 dB min
RF Input Impedance 50 ohms
Dual Diversity Tower 432-83H-01-T
unit alone Input VSWR < 2:1
A and B Channel Quadrature-Coupled Dual Stage
Multicoupler Control Unit, Dual 16 port output Distribution Amps
90-240VAC Power 432-83H-01-M RESERVE GAIN ADJUSTMENT (EACH CHANNEL)

-48V Option 432-83H-01-M-48
Coarse 0 – 15.5 dB in 0.5 dB steps
S PECIFICATIONS, T OWER TOP AMPLIFIER Fine 0-0.8 dB in < 0.1 dB steps (Fine adjustment
accommodates accurate channel to channel
amplitude balance)
Frequency Range 792-824 MHz
Output IP3 (Before +48 dBm
Net Gain 30 dB Min (Each Channel)
output Attenuator and
Noise Figure (Typ./Max) 2.7 dB / 3.0 dB 16-way split)
IIP3: >15 dBm 16 BNC Female Outputs Labeled RxA-1 through RxA-16 and RxB-1
Integrated Test Port 36 dB (Typ.) for each channel through RxB-16
Isolation 2 BNC Female Outputs for splitting expansion
Antenna Port VSWR 1.5 :1 Max
Power Requirements 12 VDC @ TBD A CONNECTORS
Lightning Protection Impulse Suppression on all external connectors
Operating Temp Range -30°C to +60°C N-Female RF Connections TTA, A, B and Test Lines
Enclosure Modified NEMA 4X Water resistant Polyester Housing BNC Female input to Test Line (on front panel)
outputs to BTS radios
Connectors N-Female
Ethernet Rj45 Access from front panel
Dimensions (HWD) 14”x12”x7”
Alarm Contacts Two Form C Contacts. Separate alarms for A
Weight Approx 25 lbs and B Channels
Power Requirements 48 VDC or 85-250 VAC 50/60 Hz, depending
SPECIFICATIONS, PRESELECTOR upon model
120VAC input current TBD
Passband Insertion Loss <0.8 dB
-48V DC input current TBD
Passband Return Loss >15 dB
Operating Temperature 0°C to +50°C at non-condensing humidity
Stopband Rejection >60 dB @ 776 and 851 MHz
Enclosure Standard EIA 19” Rack Mounting
Dimensions (HWD) 2 RU x 19” x 18”
Net Weight <TBD lbs
Specification sheet
MCC 7500
IP Dispatch Console
The Motorola MCC 7500 eases migration and Trunked and conventional The number of calls and
IP Dispatch Console is minimizes user training radio channels are call information displayed
designed to ease the requirements. customizable with in the Activity Log is
complex job of a mission Intuitive and familiar GUI various controls, such as customizable to suit the
critical radio system is based on Microsoft patch status, frequency needs of the user(s).
dispatcher. Windows® and uses select, coded/clear The status of auxiliary
easily recognized icons select, and individual inputs and outputs is
Easy to Use, Flexible, and aliases. volume control, based conveniently interpreted
and Customizable User on user preferences. Per- from the GUI with the
Flexible and customizable
Interface channel controls can be use of familiar graphical
GUI provides multiple
Features the Elite fully or partially shown, icons, such as a door
screen layouts (folders)
Graphical User Interface or hidden to save space shown open or closed.
to organize resources
(GUI) that has been on the screen.
by agency, shift, or any
refined and proven criteria that meets the Busy dispatchers can
through years of use needs of the console respond to a missed call
in mission critical user(s). by simply clicking on an
dispatch operations. This entry in the Activity Log.
The MCC 7500 Dispatch Console is a Mission activity. Integration of the MCC 7500 positions
Critical IP command and control solution with the radio system enables full participation
designed to ensure optimal quality audio and in end-to-end voice encryption for secure
reliable communication. Console positions communication, priority handling of emergency
are connected directly to the IP network which calls, and Agency Partitioning. Each console
supports communication with both trunked is centrally configured and managed from the
and conventional radios and all other dispatch network manager, providing vital efficiency.
Specification sheet
MCC 7500
IP Dispatch Console
Operator Position Key Interoperability transmissions are able continuing operations. To help reduce dispatcher
Features to take over resources stress and potential
Components Enhanced Secure
Works with from lower priority Operation: Encryption errors when managing
CENTRACOM Gold transmissions. and decryption services encrypted audio
Elite™: The MCC Optimized Patch within each dispatch situations, indicators
7500 console can be Functionality: MCC operation position enable and alerts are provided
combined in the same 7500 console users can dispatchers to fully when the console mode
dispatch center with patch communication participate in secure does not match that of
CENTRACOM Gold between trunked and/or communications while a received call; or when
Voice Processor Module Elite, with robust conventional radios that keeping the sensitive, a patch or multi-select
feature interaction. are normally unable to vital information group is being set up
communicate with completely encrypted between a mix of clear
Agency Partitioning:
each other. between the dispatcher and secure channels.
Allows multiple agencies
to share a system to gain Patched radio users see and the radio users. Integrates with
interoperability and cost the ID or alias of the Dispatchers can interface Motorola PremierOne™
savings benefits, while other patched radio(s), with agencies that have CAD: The MCC 7500 can
still maintaining control as opposed to that of the different encryption be integrated with the
of their own channels, console. This minimizes configurations without Motorola PremierOne
encryption keys, console confusion and the need any manual intervention CAD common platform
configuration, etc. for the dispatcher to or delay. Up to 60 and intuitive user
intervene in the call. calls using up to four interface to simplify
Priority for Emergencies:
different algorithms dispatch operations,
Gooseneck Microphone Transmit Priority Levels Patches are automatically
and multiple secure improve data accuracy
provide an orderly and re-established if
keys can be supported and enhance operational
consistent method for interrupted so the
simultaneously. efficiencies.
ensuring higher priority MCC 7500 user
can concentrate on
The MCC 7500 dispatch solution consists of the following:

MCC 7500 Dispatch Console Operator Position and managing the entire radio system. Changes are
MCC 7500 operator positions connect directly to automatically distributed throughout the system.This
the radio system’s IP transport network without centralized approach saves valuable time and efforts
Recommended Plantronics gateways or interface boxes. Audio processing, for system administrators and technicians.
SupraPlus headset encryption, and switching intelligence for dispatch
pictured. Two headsets are
accommodated by the MCC is performed within each software-based operator Conventional Channel Gateway (CCGW)
7500 Headset Jack box (not position, without additional centralized electronics. The CCGW enables trunked system users to
shown), which is useful for Consoles function as integrated components of incorporate analog conventional channels into their
supervisory applications.
the total radio system, enabling full participation in dispatch operations without a separate hardware
system level features such as end-to-end encryption network and channel banks. Conventional audio is
and agency partitioning. transported between the dispatch consoles and the
Operator position hardware consists of a monitor, CCGWs by the same IP network that is used for
personal computer, keyboard and mouse/trackball/ the trunked audio. The CCGW provides E&M and
touchscreen, speakers, audio accessories, and a tone remote station control and supports the 4-wire
Voice Processor Module (VPM). The VPM provides analog connections for conventional. Each CCGW in
Standalone Speakers provide connections for analog devices to be connected a system can support up to four analog channels.
ample flexibility.
to the digital console. The low-profile VPM can be
rack mounted, furniture mounted, or placed on the Digital CCGW (DCCGW)
desktop. The DCCGW enables trunked system users to
Optional Footswitch
not pictured The MCC 7500 console system does not incorporate ASTRO 25 conventional channels
require separate configuration or performance into their dispatch operations without a separate
management equipment. The MCC 7500 console hardware network and channel banks. ASTRO 25
system is configured and managed by the radio conventional audio is transported by the same IP
system’s configuration manager, fault manager and network used for the trunked radio. The DCCGW
performance reporting applications. This provides provides digital control of the station via a V.24
the customer with a single point for configuring connection. Each DCCGW can support up to two
ASTRO 25 conventional channels.
Specification sheet
MCC 7500
IP Dispatch Console
Auxiliary Input/Output Server the AIS and recorder. Highly configurable, the MCC
The Auxiliary Input/Output server enables console 7500 logging solution includes:
operators to control and monitor external devices, •R
ecorded audio quality equivalent to audio heard at
such as doors and lights, from the console user console position
interface. Since the MCC 7500 Dispatch Console • Information associated with radio calls recorded in
does not rely on centralized electronics, contact addition to the call audio.
closures and input buffers required to interface to
•D
ispatcher and radio initiated events on radio
these devices are housed in Remote Terminal Units
channels (such as changing the frequency, sending
(RTUs). These RTUs can be physically located close
an alarm) are recorded.
to where they are needed, at any console site or RF
site. The dispatch consoles and RTUs communicate •R
ecorder capacity based on the number of radio
with each other across the radio system’s IP transmissions it will need to record simultaneously,
transport network. not on the number of channels it may record.
•S
upports Agency Partitioning, enhancing control
over which resources are recorded by which
Archiving Interface Server (AIS)
agency or department.
The AIS is a digital logging interface, comprised of a
•S
ecurity and fault management centralized at the
personal computer and a VPM. Each AIS works with
radio system’s network manager.
an IP-based logging recorder. Audio and call control
information is sent across the IP network between
The MCC 7500 Dispatch

Console connects directly
to the IP network without
interface boxes, digital voice
gateways, or backroom
electronics, providing your
organization with important
interoperability and cost
savings for today’s Mission
Critical operations.
Specification sheet
MCC 7500
IP Dispatch Console
specifications
System Compatibility ASTRO® 25 System and PremierOne™ CAD Application

Vocoder Algorithms supported AMBE, IMBE, ACELP, G.728 (for Analog Conventional)
Encryption Algorithms supported AES (256 bit), DES-OFB, DVI-XL, ADP (Advanced Digital Privacy)
Monitor requirements
With Mouse or Trackball 17” minimum, 20” recommended
Touchscreen 20” minimum
Voice Processor Module (VPM)
connections Device Connector type
One desktop microphone RJ45
Two headset jacks connectors DB15
Four desktop speakers RJ45
One local logging recorder RJ45
One radio instant recall recorder RJ45
One external telephone set RJ45
One external paging encoder RJ45
One footswitch RJ45
VPM mounting options EIA 19” rack mount, console furniture mount, Desktop – supports monitor up to 80 lbs
VPM audio inputs and outputs 600 Ohm, balanced and transformer coupled (except for microphone which is
2000 Ohm, balanced, and does not use a transformer)
Speaker Mounting Options Desktop, furniture mount, or wall mount (with bracket accessory)
Dispatch Console Cable Lengths VPM to Speaker cable 10.1 feet (3.09 meters) standard
VPM to Headset Jack cable 6 feet (1.8 meters) standard
Headset Jack Extension cable 6 feet (1.8 meters) standard
VPM to Microphone cable 10 feet (3.05 meters) standard
VPM to Footswitch cable 10 feet (3.05 meters) standard
Supported Console Site Link types Fractional T1/E1, Single T1/E1, Multiple T1/E1s
Redundant and non-redundant versions are supported
IP site links
MCC 7500 Dispatch Console Capacities Up to 60 simultaneous audio sessions per console
Up to 60 simultaneous encryption/decryption sessions per secure capable console
Up to 3 Multi-Select groups per dispatch console (with up to 20 members per
Multi-Select group)
Up to 16 Patch groups per dispatch console (with up to 20 members per Patch group)
160 resources per operator position
Conventional Channel Gateway
(CCGW) Rack mountable, 1 rack unit high
T1R1, T2R2, T4R4, T8R8, T12R12, T14R14 channels
Each CCGW provides four RJ45 connector ports for interfacing to analog
conventional base stations. Each port contains the following inputs and outputs:
• 600 Ohm, balanced analog audio input – To accept radio audio from the station
• 600 Ohm, balanced analog audio output – To send console transmit audio to the station
• Input buffer – To detect Carrier Operated Relay (COR) closure in the station
• 1 Amp, 24 VDC relay output – For relay keying of the station
Can be configured to support AGC, DLM, or no input conditioning
Digital Conventional Channel Gateway
(DCCGW) Rack mountable, 1 rack unit high
T1R1, T2R2, T4R4, T8R8, T12R12, T14R14
Each DCCGW provides two RJ45 connector ports for interfacing to ASTRO 25
conventional base stations
V.24 to station or comparator. No Digital Interface Unit (DIU) required
Specification sheet
MCC 7500
IP Dispatch Console
specifications (cont’d)
Auxiliary Input/Output
Server Hardware A simplified, user-friendly version of the MOSCAD SDM 3000 RTU is used to support
most MCC 7500 dispatch console Aux I/O needs.
The output relays are capable of switching 1A @ 24VDC or 1A @ 24VAC.
Input buffers are capable of sensing a dry closure through 1000 feet or less (round trip) of
24 AWG wire.
The RTU provides single pole Form A relay outputs. (Double pole, Form B or Form C relays
must be implemented using external relays which are controlled by the RTU relays.)
Auxiliary Input/Output Capacities Number of Output Relays Number of Input Buffers
Single SDM 3000 RTU 16 48
Single SDM 3000 RTU with 1 expansion chassis 32 96
Single SDM 3000 RTU with 2 expansion chassis 48 144
Auxiliary Input/Output Mounting
Each SDM 3000 RTU and each SDM 3000 RTU Expansion Chassis is rack mountable in a standard 19 inch rack and is
one rack unit high.
Size and Weight Device Height Width Depth Weight
VPM 1.75 inches 16.9 inches 12.3 inches 3.6 lbs

44.5 millimeters 430 millimeters 312 millimeters 1.6 kg
Speaker 4.9 inches 4 inches Without bracket: 0.7 lbs
124 millimeters 102 millimeters 3.5 inches 0.3 kg
89 millimeters
With bracket:
5.8 inches
146 millimeters
Headset Jack 1.6 inches 5 inches 6 inches 1.2 lbs
41 millimeters 127 millimeters 152 millimeters 0.5 kg
Microphone Gooseneck at 90º: 4.8 inches 6.6 inches 2.4 lbs
4.5 inches 121 millimeters 168 millimeters 1.1 kg
114 millimeters
Gooseneck at 180º:
21.8 inches
552 millimeters
Power Consumption and Thermal
Device Power Input Thermal Output

VPM 0.4 Amps at 120VAC 171 BTUs/hour
0.2 Amps at 240VAC
Speaker Add 0.05 Amps per speaker Add 15 BTUs/hour per speaker
to VPM power Input at 120VAC to VPM thermal output
(0.025 Amps at 240VAC)
Headset Jack negligible negligible
Microphone negligible negligible
Specification sheet
MCC 7500
IP Dispatch Console
Certifications
The various hardware elements of the Motorola MCC 7500 dispatch console product line are
certified to meet the requirements for UL, CSA and CE.
Safety CSA 60950-1-03 / UL 60950-1
EN60950-1 2001
EMC Emissions & Immunity FCC part 15 Class A
ICES-003
EN55022 1998 + A1: 2001 + A2:2003 (CISPR-22 Class A)
EN55024 + A1:2001 + A2:2003
EN61000-3-2 2000
EN61000-3-3 1995 + A1:2001
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com/governmentandenterprise +1 800 367 2346
MOTOROLA and the Stylized M Logo are registered in the U.S. Patent and Trademark Office.
All other product or service names are the property of their registered owners. © Motorola, Inc. 2010 (1004)
R3-13-2010D
PRODUCT SPEC SHEET
DISPATCH CONTROL WHEREVER A NETWORK CONNECTION IS AVAILABLE
MIP 5000 VoIP Radio

Console
You need a flexible and affordable VoIP radio provides multiple screen layouts (folders) to organize
console solution to transmit dispatch-quality resources by agency, shift or any criteria that meets the
needs of the console users. The GUI provides extensive
voice over your existing multicast-enabled user options for full-color control of the display and
Ethernet network. With the ability to connect re-sizeable windows and icons. To save time, dispatchers
up to 100 remote users and flexible licensing can easily access Page History and Activity Log windows
with 1, 4, 8, 12 and 24 channel software for real-time-status information.
options, the MIP 5000 VoIP Radio Console
is designed to meet your requirements. You CUSTOMIZABLE CHANNEL CONTROL
can connect up to 128 radio resources to the Customize MIP 5000 VoIP radio channels for user
preferences with patch status, frequency select, coded/
network and configure them in the Console clear select and individual volume controls. Per-channel
System Database Manager (CSDM). Plus, controls can be fully or partially shown, or hidden to save
save configuration files on each operator space on the screen. Busy dispatchers can respond to a
position to allow a dispatcher to access missed call by simply clicking on an entry in the Activity
and control different combinations of radio Log. The number of calls and call information displayed
in the Activity Log can be customized to suit the particular
resources (up to 24 at a time). The console needs of users. Digitally controlled resources can display
system consists of two parts – a graphical the radio channel name as the top line of the resource
user interface (GUI) and a radio gateway window. The second and third lines of the resource
or gateways. window display the control head text as supplied by
the radio.
FLEXIBLE AND CUSTOMIZABLE
In the Activity Log, Unit identifications (IDs) or alias
USER INTERFACE names for push-to-talk (PTT) IDs and emergency alarms
To minimize user-training requirements, the MIP 5000 are displayed for analog conventional, ASTRO® 25 and
features the familiar MCC 5500 GUI. This intuitive GUI is MOTOTRBO® systems.
based on Microsoft® Windows® with pull-down menus,
icons and tool tips. The flexible and customizable GUI
PRODUCT SPEC SHEET
Key Features
Fully featured to meet your needs, the MIP 5000 VoIP
Radio Console includes multi-select all-points bulletin
(APB) and single-button page capabilities. For local and
tone controlled resources, DTMF Decode and MDC 1200
inbound and outbound signaling is supported. MDC
signaling features include PTT ID Alias, Emergency, Call
Alert, Selective Call, Frequency Select and Radio Enable/
Disable, Voice Alert, Remote Monitor, Status Request,
Repeater Enable/Disable and Manual RAC. Mobile,
digitally controlled resources mimic the control head
functionality, including all buttons and display, for specific
Motorola radios including the MOTOTRBO® XPR 4550.
Interoperability
The MIP 5000 allows users to patch communication
between dissimilar radios with an easy drag and drop
capability; patches can contain active “Call Director” The MIP 5000 GUI provides extensive user options for full control of the display.
telephone calls. And the MIP 5000 VoIP Radio Console
meets the standard for Level 4 Interoperability with
Compatibility
dispatcher-controlled, radio-to-radio patching.
MIP 5000 software is compatible with Microsoft®
Licensing operating systems Windows XP® Professional-SP3,
A hardware USB HASP key is required at each operator Windows VISTA® Business Edition SP2, and Windows 7
position to license and enable radio resources. USB Professional deployed on a desktop or laptop computer.
HASP keys are available in 1, 4, 8, 12, or 24 resource Note: It is strongly recommended that public safety
configurations. customers use Motorola-certified desktop computers.
MIP 5000 Console Operator Position Trunked or Conventional

Audio processing, including routing and intelligence for The MIP 5000 VoIP Radio Console interfaces with
the MIP 5000 console, is performed within each software- trunked and conventional radio systems. Plus, the
based operator position, without additional centralized MIP 5000 can work in parallel with existing console
electronics. The MIP 5000 VoIP Radio Console system is systems for backup or migration applications.
configured and managed by the Console System Database
Manager (CSDM). This centralized approach, with a single
MIP 5000 VoIP Radio Gateway
point for configuring and managing the entire console, The MIP 5000 Radio Gateway provides access to multiple
saves valuable time and effort for system administrators radio types using local control, tone control, Motorola
and technicians. To help radio service and information digital control and MOTOTRBO control. Each Gateway
technology (IT) personnel with system troubleshooting, interfaces to one two-way radio. All MIP 5000 Gateways
the MIP 5000 operator position features a built-in network have temperature operating specifications of -30 to +60
monitoring tool that instantly reports changes in the degrees Celsius for use in extreme environments.
Ethernet network that could affect audio quality.
Network and VPN
MIP 5000 Audio Accessories The MIP 5000 Radio Console system requires a multicast-
The MIP 5000 supports public safety grade audio enabled network that is secure, non-congested and is
accessories, which can be supported with either quality of service (QoS) enabled. In all cases the gateways
Basic or Enhanced Motorola Headset Jackbox models. must be installed on a network where they are protected by
Both Headset Jackboxes model types support standard a firewall. The MIP 5000 Console position(s) may operate
Plantronics four or six-wire headsets, dual-pedal on the same network as the gateways or operate remotely
footswitches and Motorola Desktop Gooseneck using a secure virtual-private network (VPN) connection with
microphones. The Enhanced Jackbox has an additional a router-to-router configuration over the Internet. Additional
port to support a call director-equipped external phone, hardware may be required for VPN set up.
an external paging encoder, an analog recorder output,
or PTT/On-The-Air-Relay output for an operator position.
Any combination of Basic and Enhanced Jackboxes
(up to a maximum of three) can be added to each
console position.
PRODUCT SPEC SHEET
MIP 5000 VoIP MIP 5000 VoIP MIP 5000 VoIP

Operator Position Operator Position Operator/CSDM Position
USB Headset Jackboxes USB Headset Jackboxes USB Headset Jackboxes
CUSTOMER-PROVIDED ETHERNET LAN/WAN
LOCAL Gateway TONE Gateway DIGITAL Gateway DIGITAL Gateway MOTOTRBO Gateway
CDM Series MTR 3000 Tone ASTRO Spectra/ MCS 2000 Model III MOTOTRBO XPR 4550
Mobile in Tray Control Base/Repeater Spectra PLUS Control Station Mobile Control Station
W9 Consolette
COMPUTER REQUIREMENTS
Windows XP® Professional SP3 Computer Windows Vista® Business SP2 and Windows 7
Professional Computer
Intel® Pentium 4 (or better) personal computer, 1.5 GHz (or faster) Intel® Core™ 2 Duo (or better) personal computer, 2.13 GHz (or faster)
1 GB or more RAM 2 GB or more RAM
20 GB hard drive, CD-ROM drive 80 GB hard drive, DVD-ROM drive
Two serial ports, one parallel port, two USB ports, and 10/100 Base-T Four USB ports, and 10/100 Base-T Ethernet Adapter
Ethernet adapter
SVGA display adapter (1024 x 768 pixel or better resolution, 256 colors PCI Express video adapter (128 MB SDRAM)
minimum, 16 MB RAM minimum)
Integrated high-definition digital audio adapter (SoundBlaster® Live! 24-bit sound card equivalent or better)
Additional USB ports are required to support up to three USB JackBoxes. A USB 2.0 hub can be used to increase the number of USB ports available.
17-inch or larger, touch-sensitive (optional) or regular color monitor
Pointing device (two-button mouse or trackball; optional for touch-sensitive screens)
OTHER CONSOLE COMPONENTS
101- key Keyboard
Headset Interface (up to three USB enhanced or basic Jackboxes)
Two external speakers (4 W amplified, 3” minimum)
Desktop gooseneck microphone or headset
Dual-pedal footswitch
PRODUCT SPEC SHEET
LOCAL RADIO GATEWAY
Rx Impedance 47 Kohm
Receive input level 50 – 250 mVrms
Tx Impedance 130 ohm
Transmit output level 50 – 250 mVrms
Opto-Input Qty 1, for High Speed Mute or COR detect (selectable)
Opto-Input Rating 5-20mA input current, unbalanced, 5K Ohm impedance
Relay Output Qty 7, for PTT, Monitor, Takeover, Binary Freq. Select, PL Select. Wildcard, (Selectable)
Relay Output Type Form C, DPDT, Dry Closure, 150mA max., or 60VDC max.
Relay Output Switching Power 3 Watts max., non-inductive load
Radio Connector Type DB25
Tone Radio Gateway SPECIFICATIONS
Rx impedance 600 ohm
Receive input level -40 dBm – 0 dBm
Tx impedance 600 ohm
Transmit output level -40 dBm – 0 dBm
Guard Tones Supported 2175Hz (Default), 2100Hz, 2300Hz and 2325Hz
Function Tones Supported 550Hz - 2050Hz in 100Hz increments, qty 16
Tone Tolerance ± 2%
Opto-Input Qty 1, for High Speed Mute, COR detect, Cd/Clr Rx Status (selectable)
Opto-Input Rating 5-20mA input current, unbalanced, 5K Ohm impedance
Relay Output Qty 1, follows PTT command to radio
Radio Connector Type RJ45
Digital Radio Gateway SPECIFICATIONS
MIP Digital when interfacing with a Digital Junction Box (DJB)
Rx and Tx impedance 600 ohm
Rx and Tx levels -40 dBm – 0 dBm
MIP Digital when interfacing directly to radio speaker and microphone
Receive Impedance 47 Kohm
Transmit Impedance 130 ohm
Radio data interface RS485
Maximum cable length to radio 50 feet

PRODUCT SPEC SHEET
MOTOTRBO® Radio Gateway Specifications
Receive Impedance 47 Kohm
Relay Output Quantity 1 for PTT
Radio Connector type USB for Data and RJ45 for Audio
Max Cable Length to Radio 6 feet
GENERAL GATEWAY AUDIO SPECIFICATIONS
Transmit Line Outputs
Line Output Adjustable from -40 to +11 dBm.
Output Impedance 600 ohms and 10 kOhms (Tone control model only)
Receiver Line Inputs
Receive Sensitivity Adjustable from -40 to +11 dBm.
Call Light Sensitivity Adjustable from -5 to -32 dBm, relative to receive sensitivity.
Line Balance 60 dB @ 1004 Hz.
Input Impedance 600 ohms and 10 kOhms (Tone control model only)
Audio Controls
Individual Volume 34 dB range in 15 discrete steps. Muting configurable for -24 dB or full mute.
All Mute 24 dB below current setting or full muting of unselected channels with timer programmable from
1 to 120 seconds or for an infinite duration.
USB JACKBOX DESKTOP MICrophone INTERFACE
Impedance 2.2 Kohm
Input Level max 50 mVrms, nominal level at 5 mVrms
USB JACKBOX HEADSET INTERFACE
Receive Impedance 50 ohm
Receive Level max 150 mVrms, nominal level at 20 mVrms
Impedance max 100 mVrms, nominal level at 55 mVrms
Enhanced Usb Jackbox
Recorder Port The output shall consist of different sources (select, unselect, and Call Director) and the
transmit audio of the operator. The fixed nominal output is -10 dBm into 600 ohms.
Paging Input Adjustable from -40 to 0 dBm, balanced 600-ohm input.
Call Director Output –40 to –5 dBm, with a nominal –20 dBm,balanced 600-ohm input.
Call Director Input –40 to –5 dBm, with a nominal –10 dBm, balanced 600-ohm input.
Status Outputs and Inputs

Auxiliary Outputs (PTT, DTMF/STAT-ALERT, Recorder)
Form A dry closures 150 mA max. or 60VDC max. Switching power 3 watts max.
Maximum distance 200 ft within one building.
Auxiliary Input (Paging Encoder) Opto-coupled input, 5 to 20 mA input current, unbalanced.

Active: Ground. Maximum distance 200 ft within one building.
PRODUCT SPEC SHEET
gateway POWER SUPPLY
AC Input Voltage 90-264 VAC
Input Frequency 47–63 Hz
Power Output 12 W max.
DC Outputs +5 VDC @ 2.4 A
Agency Approvals UL (Underwriters Laboratories), CSA (Canadian Standards Association)

CE Mark (Conformité Européenne), FCC (Federal Communications Commission)
CALIFORNIA-COMPLIANT GATEWAY POWER SUPPLY
AC Input Voltage 90-264 VAC
Input Frequency 47–63 Hz
Power Output 12 W max.
DC Outputs +5 VDC @ 4.0 A
Agency Approvals UL (Underwriters Laboratories), CSA (Canadian Standards Association)

CE Mark (Conformité Européenne), FCC (Federal Communications Commission)
NETWORK REQUIREMENTS
Type Multicast and QoS enabled 10/100 Mbps Ethernet
Bandwidth Usage 100kbps per radio voice channel, gateway
Packet Loss 1% max.
End-To-End Delay 150ms max.
Jitter 100ms max.
CERTIFICATION S and Compliance
Radio Gateway (applies to all gateways) FCC Part 15, Class A; FCC Part 68/TIA968-A; Industry Canada CS03; Industry Canada ICES-003
UL and CSA listed PSU; CE/RTTE; WEEE
Headset Jackbox FCC Part 15, Class B; CE; ICES-003; UL and CS
Specifications subject to change without notice.
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. motorola.com/dispatch
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license.
All other trademarks are the property of their respective owners. © 2010 Motorola, Inc. All rights reserved.
R3-13-2011C (1009)
DATA sheet
MC SERIES
Deskset Controllers
Pictured from left to right are

the MC2000™ Advanced Model,
the MC2500™ Multi-channel Model,
and the MC1000™ Basic Model.
STANDARD FEATURES
• Multiple models for various applications • Internal microphone, intercom, and speaker
for convenient operation
– Extended Local Control for controlling an
on-site radio up to 1000 feet away • Push-to-talk (PTT) handset for private
communications
– Tone or DC Remote Control for controlling a
station with 600 ohm telephone lines • Monitor switch for monitoring channel activity
before transmitting
• Multiple control points allow up to 10 units to
operate in parallel
PRODUCT OVERVIEW
The MC Series Desktop Controllers allow remote access to the functions
of a compatible station (base station, repeater, or control station). These
desktop controllers support tone, DC, and E&M signalling for keying and
control of stations.
data sheet
MC SERIES
Deskset Controllers
MC1000 BASIC MODEL (non-signaling) FEATURES

For Local Control Models
• Single Frequency and Single Station Control • Monitor Button with LED
• Push-to-Talk Handset • Front panel programming (easy setup – no
RSS required)
• Speaker
• Intercom between MC1000 units and stations
• Speaker on/off (receive audio is heard through
handset and speaker simultaneously) • Operator cross mute
• Volume Control • 10 units can operate in parallel
• Full Duplex Capability • Parallel Operator Busy Indication
• Internal Mic (for use without handset) • 120 Vac - 60 Hz Power Supply
• Transmit Button with LED • Can be wall mounted
For Tone and DC Control Models Only in addition to Local Features

• 4 Frequency Single Station Control
• 2- or 4-Wire Audio
• Takeover/Line Select allows a supervisory unit to override other parallel units or allows
connection of two base stations for back-up control (Main/Alt operation)
MC2000 ADVANCED MODEL (signaling) FEATURES

• All MC1000 Basic Model features plus:
• 110/220 Vac 50/60 Hz Power Supply
• Parallel Status (Tone model only)........ Each deskset operator knows the selected frequency and
status of the station
• Programmable Voice Delay................. User can speak immediately after pressing PTT or
Transmit bar without message truncation
• Desk Mic Compatible......................... Allows another choice of audio accessory
• MDC1200 Signaling and Paging.......... Operator can selectively signal pagers, portables, or
mobile radios Supports the following: (E/D; E = Encode,
D = Decode)
– PTT Unit ID (E/D)............................. Displays unit ID of caller (250 aliases)
– Voice Alert........................................ Allows dispatcher to alert specific user prior to critical
voice transmission
– Call Alert/Short Call Alert (E/D) ....... Informs the user to call-in by sending a “page” to their
portable or mobile
– Status/Message (D)......................... Displays received status and message codes
– Radio Enable/Disable (E).................. Allows operator to remotely enable and disable a lost or
stolen portable
– Radio Check (E)............................... Console operator can determine if a radio is on the air and
within range without disturbing the radio user
data sheet
MC SERIES
Deskset Controllers
MC2000 ADVANCED MODEL (signaling) FEATURES (cont’d)

• MDC1200 Signaling and Paging (cont’d)
– Emergency Alarm (D)...................... Flashing display, audible tone, and an output for external
alarms can alert the console operator of emergency
situations
– Recent User Stack........................... Allows last nine records to be stored for review at a later
time
– RS232 Printer Port........................... Allows RSS programming via computer or the logging
of MDC1200 inbound/outbound message activity for
permanent record keeping on a serial printer
– Alert Tone......................................... 3 alert tones are supported
• Paging Encoder . ................................ Integrated paging encoder supporting 2 Tone, Quik-Call I &
II, DTMF, 5 Tone, 6 Tone, GE99, NEC5, NEC6, Reach 1+1,
Pulse and custom 2-tone with aliasing
• 18 Programmable Buttons.................. Allows for deskset flexibility. Button usage may include
single button paging, fast access to paging or MDC1200
signalling, alert tones, frequency selection, speaker mute,
relay control and wildcards
• Frequency Control............................... 16 Frequency Control (Tone) and 4 Frequency Control (DC)
with alias names
• DTMF Decode.................................... Allow ANI (Automatic Number Identification) or selective
call mode of operation
• Securenet Compatible........................ Allows control of coded/clear modes of operation on
Motorola secure equipped stations
• RSS Programming Available................ Allows the console to be customized to fit customer
requirements
• External connectors............................ For power, RSS/printing, base station connections, and
desk mic
• 2 line x 20 character
backlit display...................................... Displays important, easy to read information to the
operator such as channel status, alias names, emergency
ID’s, status/message information and VU meter
data sheet
MC SERIES
Deskset Controllers
MC2500 MULTI-CHANNEL MODEL FEATURES

• All MC2000 Advanced Model features plus:
• 4 channel control................................ Controls up to 4 radios or base stations. Includes ability
for DC control on 1 channel
• Individual channel select and
instant transmit................................... Individual status indicators and control
• Unselect speaker connector............... Allows connection of unselect speaker to separate audio
for ease of operation
• Individual volume control.................... Each channel has individual volume control
• All mute.............................................. Mutes audio on the unselected channels
• Dedicated logging recorder output..... Fixed 600 Ohm output (no keying tones) with all audio
summed for recording
• Radio Patch......................................... Patch any two channels
• Multi-Select......................................... All four channels can be selected for simultaneous
transmit
ACCESSORIES
For Extended Local Control
• Junction Box connects up to six local desksets to the station. When 7-10 desksets are operating
in parallel, two junction boxes are required.
TONE AND DC REMOTE CONTROL ADAPTERS

Tone and DC Remote Adapters allow local control base stations to be controlled remotely via a
Tone or DC Remote Deskset. Each adapter will accept up to 10 desksets.
standard features
Tone (L3276) DC (L3277)

LED Indicators for Power, Line PTT, LED Indicators for Power, Line PTT,
Monitor, Squelch Detect, Accessory Port Monitor, Squelch Detect, Accessory Port
and Desk Mic F1, F2, F3 and F4
Local Desk Mic Port N/A
16 Function Tone Decode 5 DC Current Detects
2 or 4-wire Audio
Accessory Port used for local deskset or data applications
Accessible audio level adjustments
Rackmountable
data sheet
MC SERIES
Deskset Controllers
DDN6338 Typical Local Control Configuration

10 ft Radio Cable
16 PIN
Accy. Minimum 22 gauge
Conn. Screw Term
D B25 Screw Term Multi-Conductor Cable Block
Block Max Distance 1000 ft.
Local Junction Box
(6 desksets max per box)
(Customer or Installer Provided)
Maxtrac, GM300, M1225 DDN6337
SM50/120, CDM Series L3211 – MC1000 (Basic Local)
(CDM1550•LS Shown)
Typical Mobile in a Tray

Tone or DC Remote Control Configuration
DDN6338
10 ft Radio Cable 2- or 4-Wire 600 ohm
Telco Line
16 PIN
Accy. (Customer or Installer Provided)
Conn.
D B25 RJ11
Remote Adapter
L3277 – DC Adapter L3212 – MC1000 (Basic DC)
Maxtrac, GM300, M1225 OR L3213 – MC1000 (Basic Tone)
SM50/120, CDM Series L3276 – Tone Adapter L3216 – MC2000 (Adv. Tone)
(CDM1550•LS Shown) (MC2000 Shown Above)
Screw Term
Typical Parallel Tone Control Configuration Block
Max of 10 MC Series
Units in Parallel L3213 – MC1000 (Basic Tone)
2- or 4-Wire 600 ohm

Telco Line RJ11
(Customer or Installer Provided)
Tone Remote Control Base or Repeater

MTR2000 (shown above), Quantar, MSF5000, L3216 – MC2000 (Adv. Tone)
MSR2000, Micor
DDN6338
10 ft Radio Cable
Typical MC2500 Multi-Channel Configuration
4 Tone Channel
6 PIN OR
Accy.
Conn. RJ11 3 Tone + 1 DC Channel
D B25
Remote Adapter
CDM1550•LS Shown L3277 – DC Adapter
OR CDN6669
L3276 – Tone Adapter DB25 to Bare
Lead cable DB25
DDN6481
2- or 4-Wire 600 ohm Telco Lines Surge
Tone Remote Control Base or Repeater (Customer or Installer Provided) Protected
Punchblock L3217 – MC2500 Multi-Channel
MTR2000 (shown above), Quantar, MSF5000,
Deskset (4 channels max)
MSR2000, Micor
data sheet
MC SERIES
Deskset Controllers
deskset specifications
Local Deskset DC Remote Deskset Tone Remote Deskset

MC1000 - L3211 MC1000 - L3212 MC1000 - L3213
MC2000 - L3216
MC2500 - L3217 MC2500 - L3217
Dimension 3.75” H x 8.5” W x 9.9” D (9.53 cm H x 21.59 cm W x 25.14 cm D)
Weight Maximum 3.75 lb. (1.7 kg)
Temperature Range 32°F to 122°F (0°C to 50°C)
Humidity 95% at 122°F (50°C) (non-condensing)
Power Input:
MC1000 Models +12 Vdc/1 A max
MC2000 Model +12 Vdc/2.5 A Max
MC2500 Models +12 Vdc/1 A, –12 Vdc/0.2 A, +5 Vdc/2 A
Frequency Response 300 to 3300 Hz +3, –3 dB @ less than 3% distortion
Hum and Noise 45 dB below rated output at any port
Audio Distortion Less than 3% THD
Audio Output to Speaker .8 W (1 W peak)
Line Impedance 600 or 10 K Ohm, or differential
Receive Audio Input 300 mv AC Adjustable from –30 to +11 dBm
Transmit Audio Output 80 mv AC Adjustable from –30 to +11 dBm
Maximum Number of Desksets 10 in Parallel
Control Functions (Maximum):
MC1000 Models PTT + Monitor 4 Freq Select + Monitor 4 Freq Select + Monitor
MC2000 Models PTT + Monitor 4 Freq Select + Monitor 15 Freq Select + Monitor
MC2500 Models 4 Freq Select + Monitor 15 Freq Select + Monitor
Number of Radios:
MC1000 and MC2000 Models 1 1 1
MC2500 Models 1 Max 4 Max
Outputs and Inputs:
PTT Relay Form C dry closure. 150 mA, 60 Vdc non-inductive load.
Monitor/Aux Outputs Form C dry closure. 150 mA, 60 Vdc non-inductive load.
Aux Inputs Opto-coupled inputs, 5 K Ohms impedance, 5 to 20 MA input current, unbalanced.
Recorder Port (MC2500 only) Nominal output –10 dBm @ 600 Ohm
Auxiliary/Paging Input (MC2500 only) Nominal output –10 dBm, balanced 600 Ohm input
All Mute (MC2500 only) –24 dB or full muting of unselected channels,
timer programmable 1 to 255 seconds or infinite durations.
data sheet
MC SERIES
Deskset Controllers
remote adapter specifications
DC (L3277) Tone (L3276)

Dimensions Approximately 8.2” W (20.8 cm) x 7.3” L (18.5 cm) x 1.3” H (3.3 cm)
Weight Approximately 1.55 lbs (.7 kg)
Operating Temperature Range –22°F to 140°F (–30°C to +60°C)
Humidity 95% at 122°F (50°C) (non-condensing)
Power Input 10.5 to 16 Vdc max.; 250 mA typical 10.5 to 16 Vdc max.; 350 mA typical
650 mA max. 650 mA max.
Frequency Range ±3 dB from 300 to 3000 Hz @ 1 KHz ref. ±3 dB from 300 to 3000 Hz @ 1 KHz ref.
except at 2175 Hz notch filter
Hum and Noise Less than –45 dB below rated output
Audio Distortion Less than 3% THD @ 1 KHz
Radio Rx Input (from Radio) 32 mVac to 4.5 Vac (nominal 300 mVac). Jumper selectable to between range:
32 mVac to 500 mVac (default) or 500 mVac to 4.5 Vac
Radio Tx Output (to Radio) 32 mVac to 800 mVac (nominal 80 mVac). Jumper selectable to between range:
32 mVac to 500 mVac (default) or 500 mVac to 800 mVac
Line Rx Input (from consoles/desksets) –24 dBm to 0 dBm (nominal –10 dBm into 600Ω)
Line Tx Output (to consoles/desksets) –15 dBm to +10 dBm (nominal –10 dBm into 600Ω)
Max. Number of Desksets Supported 10
Control Functions (Max.) 4 Freq. + Monitor 15 Freq. + Monitor
Input Tolerance ±20% ±2%
digital junction box specifications
Dimension 8-2/16” W (20.5 cm) x 8-1/4” L (21 cm) x 1-3/8” (3.5 cm)
Weight 1.5 pounds (680 grams)
Audio Distortion Less that 3% THD (total harmonic distortion)
Audio Transmit 0.78 Vac nominal
Audio Receive 0.78 Vac nominal
Data Interface RS-485 standard
Frequency Response ±3 dB from 300-3000 Hz @ 1 kHz ref.
Hum and Noise Less than –45 dB below rated outputs
Humidity 95% at 122°F (50°C)
Maximum distance between Master
Digital Junction Box and console/deskset 5000 feet (1524 meters) (50 feet [15 meters] for RCH 3000)
Maximum distance to digital radio 50 feet (15 meters)
Power Input 10.5 to 16 Vdc maximum
Temperature Range 32°F to 122°F (0°C to 50°C)
DATA sheet
MC SERIES
Deskset Controllers
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com/us/government 1-800-367-2346
R3-13-2003C POD
S P E C I F I C AT I O N S H E E T
ELEMENT MANAGER FOR

COMMUNICATION SITES Multiple ports, multiple communication protocols
Site Device Manager 3000 is an intelligent and variable speed data handling allow most data
Remote Terminal Unit (RTU) specifically created devices to be interfaced to the SDM 3000.
for use in Network Fault Management systems.
The SDM 3000 allows the system operators and BUILT IN WEB SERVER
technical staff to retrieve fault information via Using a standard Web Browser, you can access
FullVision INM (Integrated Network Manager), the status of all monitored devices, view exten-
MOSCAD GMC element manager or via a Web sive Event or Diagnostic Logs or SNMP Traps as
browser tool. well as download new firmware and monitoring
software.
Monitoring Devices in Communication Sites
It connects to a variety of communications and
support devices to monitor their activity and The Web Server is a convenient tool that includes
report problems to a supervisory center. secure access from a technician’s computer to the
entire network.
MULTI PROTOCOL AND PROXY CAPABILITY
The SDM 3000 unit incorporates a scalable, REMOTE ACCESS TO LOCAL TERMINALS
intelligent Network Manager proxy agent based AND CONSOLES
on advanced hardware; Linux based firmware and Telnet support provides connectivity to local
Plug-In SW components. The SDM 3000 RTU can device consoles via SDM 3000 serial ports. Even
communicate with multiple devices using a vari- without Telnet, device craft ports can be accessed
ety of media and protocols such as serial/ASCII, by using the RSS application layer supplied with
Ethernet/TCP/IP and discrete digital I/O or analog the SDM 3000 Builder configuration utility.
inputs. The unit also supports XML for logging Reach–Through connectivity for continued support
SDM 3000
messages, NTP for Network Time Sync, HTTP for of all legacy equipment.
Web Browser, etc. Information from these multi-
ple sources is translated to SNMP for forwarding. FULL CERTIFICATION FOR MOTOROLA
SYSTEMS AND NETWORK MANAGERS
The best modem protocols for the communication The SDM 3000 is certified for all ASTRO®25 6.7
task are used while providing commonly accepted and later and 7.X systems and Motorola Network
information exchange to other devices. Managers: FullVision INM and MOSCAD GMC.
PORT AND I/O FLEXIBILITY
Serial and Ethernet/IP ports permit connectivity
to on-site devices to remotely monitor their opera-
tion. In cases where additional I/O is required to
monitor discrete devices such as security systems,
HVAC equipment, Tower lighting and power
systems, an expansion unit is available.
The SDM 3000 is the newest unit in the Motorola ment and site security. This crucial data is only
Network Fault Management family of monitoring available through the SDM 3000 which reports to
products. It adds two very important enhance- its Graphic Master Central (GMC) manager or a
ments to the standard NMO monitoring supplied subset to FullVision INM. The second is providing
by the built-in box agents and FullVision INM man- additional information on Motorola manufactured
ager. The first is providing important monitoring devices such as Base Stations, Site Controllers
and control of critical RF and support equipment and Comparators through a separate IP polling
required at most remote sites. This includes third mechanism in addition to receiving all the SNMP
party devices such as Channel Banks, microwave Trap messages.
radios, GPS, Antenna monitoring, power manage-
TYPICAL THIRD PARTY NETWORK FAULT MANAGEMENT APPLICATIONS
Antenna Monitoring Power Management

• Forward Power • AC Power Status
• Reflected Power • Main Battery Voltage
• Receive Path Test • Battery Charging Current
• Antenna VSWR • Generator Status, Operation
• Tower Lighting • Fuel/Oil Levels, Remote Exercise
Site Security Environmental Alarms

• Intrusion Alarm • HVAC Operation & Alarms
• Fire Alarm • Air Flow
• Smoke Alarm • Ambient Temperature
• Access Control • Relative Humidity
• Flood Water Level
Rear Panel View of F4544 and F4548
MOTOROLA NETWORK MANAGERS
The SDM 3000 reports all Status and Events information to

MOSCAD GMC and a functional subset to FullVision INM
Element Managers. The SDM 3000 is required to receive or
output information to these devices.
FullVision INM View of SDM 3000
GMC View of TeNSr channel bank at a Site

The following tables include the Specifications and Model numbers for the four types of SDM 3000 units:
S D M 3 0 0 0 S P E C I F I C AT I O N S – A DVA N C E D U N I T M O D E L F 4 5 4 4 A
Ethernet Port Data rates 10/100 Mb/s

Port Description 2 Ethernet user Ports; 1 Console Port
RS232 Port Data rates Up to 115,200 Kb/s
Port Description 3 Full Flow Control RS232
1 Non Flow Control RS232
RS232/RS485 Port Data rates Up to 115,200 Kb/s
Port Description Full Flow Control RS232 or RS485
I/O RS485 Port Data Rates 115,200 Kb/s
Port Description RS485 Port for I/O Communication
Discrete Inputs/Outputs I/O Descriptions 48 Digital Inputs (wet/dry contacts)
16 Digital Outputs (SPST relay, contact rating 75 VA/30W, 0.5A@30Vac/60Vdc)
8 Analog Inputs (±5 VDC, 12 bits including sign)
LED Displays CPU Display Front Panel: Console Port LEDs (2 LEDs),Communication Ports LEDs (9 Bi-color LEDs),
PWR LED, Diagnostic LED
Rear Panel: Communication Ports LEDs on the connectors RJ45 - 16 LEDs (2 x 8)
I/O Display 48 Digital Input LEDs, 16 Digital Output LEDs
Operating Power Primary Power IN ±24 VDC (18.6-32V)/Max 14W or ±48 VDC (36-60V)/Max 14W
100-240 VAC; 47-440 Hz, Max 20W
Auxiliary Power IN 12 VDC /Max 12W Alternate/Backup power source
Two 12 VDC Combined drain from two outputs, max 12W (12V@1A). Each output can supply power
Power OUT to one SDM 3000 I/O expansion unit (1A fuse for each AUX OUT).
Physical Dimensions 1 Rack Unit high (17”W x 1.65”H x 12.9”D, 435 x 42 x 328 mm)
Weight Approx. 2.5 kg (5.5 pounds)
Temperature Operating: –30 to +60°C (excluding lithium battery –20 to +60°C);
Storage: –55 to +85°C
Humidity 90-95% RH @ +50°C
S D M 3 0 0 0 S P E C I F I C AT I O N S – B AS I C U N I T, M O D E L F 4 5 4 3 A
Ethernet Port Data rates 10/100 Mb/s

Port Description 1 Ethernet user Port; 1 Console Port
RS232 Port Data rates Up to 115,200 Kb/s
Port Description Full Flow Control RS232
RS232/RS485 Port Data rates Up to 115,200 Kb/s
Port Description Full Flow Control RS232 or RS485
I/O RS485 Port Data Rates 115,200 Kb/s
Port Description RS485 Port for I/O Communication
LED Displays CPU Display Front Panel: Console Port LEDs on the connector (2 LEDs), Communication Ports LEDs
(4 Bi-color LEDs), PWR LED, Diagnostic LED
Rear Panel: Communication Ports LEDs on the connectors RJ45 - 8 LEDs (2 x 4)
Operating Power Primary Power IN ±24 VDC (18.6-32V)/Max 14W or ±48 VDC (36-60V)/Max 14W
100-240 VAC; 47-440 Hz, Max 20W
Auxiliary Power IN 12 VDC /Max 12W Alternate/Backup power source
Two 12 VDC Combined drain from two outputs, max 10W (12V@1A). Each output can supply power
Power OUT to one SDM 3000 I/O expansion unit (1A fuse for each AUX OUT).
Physical Dimensions 1 Rack Unit high (17”W x 1.65”H x 12.9”D, 435 x 42 x 328 mm);
Weight Approx. 2.5 kg (5.5 pounds)
Temperature Operating: –30 to +60°C (excluding lithium battery –20 to +60°C);
Storage: –55 to +85°C
S D M 3 0 0 0 I / O E X PA N S I O N U N I T S P E C I F I C AT I O N S – A DVA N C E D U N I T, M O D E L F 4 5 4 8 A
Communication Ports I/O (RS485) Data rates 115,200 Kb/s

Number of Ports 2
Port Description Multiple RS485 Ports (IN/OUT)
Discrete Inputs / Outputs I/O Descriptions 48 Digital Inputs (wet/dry contacts)
8 Analog Inputs (±5 VDC, 12 bits including sign)
LED Displays CPU Display Front Panel: I/O Comm. LED (1 Bi-color LED), PWR LED, Diagnostic LED
Rear Panel: I/O Comm. Ports LEDs on the IN connector RJ45 (2 LEDs)
I/O Display 48 Digital Input LEDs 16 Digital Output LEDs
Operating Power Primary Power IN ±24 VDC (18.6-32V)/Max 7W
±48 VDC (36-60V)/ Max 7W
100-240 VAC, 47-440 Hz, Max 10W
12VDC Power IN 12 VDC /Max 6W Alternate/Backup power source;
Two 12 VDC Combined drain from two outputs, max 12W (12V@1A.) 1A fuse for each AUX OUT.
Power OUT
Weight Approx. 2.5 kg (5.5 pounds).
Temperature Operating: –30 to +60°C; Storage: –55 to +85°C
S D M 3 0 0 0 I / O E X PA N S I O N U N I T S P E C I F I C AT I O N S – B AS I C U N I T, M O D E L F 4 5 4 7 A
Communication Ports I/O (RS485) Data rates 115,200 Kb/s

Number of Ports 2
Port Description Multiple RS485 Ports (IN/OUT)
LED Displays CPU Display Front Panel: I/O Comm. LED (1 Bi-color LED), PWR LED, Diagnostic LED
Rear Panel: I/O Comm. Ports LEDs on the IN connector RJ45 (2 LEDs)
Operating Power Primary Power IN ±24 VDC (18.6-32V)/Max 7W
±48 VDC (36-60V)/ Max 7W
100-240 VAC, 47-440 Hz, Max 10W
12VDC Power IN 12 VDC /Max 6W Alternate/Backup power source
Two 12 VDC Combined drain from two outputs, max 12W (12V@1A.) 1A fuse for each AUX OUT.
Power OUT
Weight Approx. 2.5 kg (5.5 pounds).
Temperature Operating: –30 to +60°C; Storage: –55 to +85°C
R E G U L ATO RY STA N DA R D S
Safety UL listed: UL 60950-1, CSA 22.2-950-1, EN60950-1, IEC 60950-1

Radiated & Conducted Emission CFR 47 FCC part 15, subpart B (class B); CE EMC: EN55022 (class B), EN50081-1, EN61000-6-3,
EN61000-3-2, EN61000-3-3 (AC only)
Electro-Static Discharge EN55024/EN61000-4-2 (air discharge 8 kV, contact discharge 4 kV)
Surge EN55024/EN61000-4-5
Radiated Immunity EN55024/EN61000-4-3 3 V/m 80%AM @ 1kHz
Electrical Fast Transients EN55024/EN61000-4-4 AC: 1.0kV DC & I/Os: 0.5kV
Conducted RF Immunity EN55024/EN61000-4-6 (3 Vrms)
Power Freq Magnetic Field EN55024/EN61000-4-8 (1 A/m)
Voltage Dips & Interruptions EN55024/EN61000-4-11 95% AC reduction for 0.5 period; 30% AC reduction for 25 periods;
95% AC reduction for 250 periods
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A.

www.motorola.com/governmentandenterprise 1-800-367-2346
R3-11-2030
Flatpack2 Power System
Data Sheet # Preliminary Rev.0
Flatpack2 48V 300A Power Core

-48V Potential, Current Maximum 294A
Models: FP2 (Power Core)
Key System Features ______________________________
Power Core 4U- Distribution & Control Section consisting

of:
One (1) Low Voltage Battery Disconnect (LVBD) contactor
Main Battery feed and return connections
20 position plug-in circuit breaker / fuse distribution
Each distribution bus is work rated for 300A continuous duty
Smartpack System Controller - Plug-in, hot swappable
Connectivity to alarm relays and external control input
connections
Positions for up to sixteen (7) Flatpack2 rectifiers. -48V with
42A maximum each
Individual AC Input feed configuration
Plug-in, hot swappable operation
Optional System Equipment

Optional TCP / IP or SNMP Agent via 10/100Mb Ethernet WAN port
Optional load shedding. Each distribution bus individually configurable.
Optional Front access for battery terminations
Product Description
The Flatpack2 power core uses a 20 position, by three bus, Breaker matrix capable targeting compact system
solutions where minimum rack footprint is a primary consideration. Systems using the Flatpack2 300A design
are ideal for compact sites with minimum available floor space. This system is mounted in a 19” standard
telecommunication equipment rack. The compact size of this system allows more space for additional telecom
equipment even within the same rack. The standard system configuration accommodates (7) -48 VDC
Flatpack2 rectifiers, with a total power output of 14KW / 294A.
• Digital Communication over CAN-bus with Smartpack controller

FP2 Rectifier
• Autonomous, active current sharing between rectifier modules
• Wide input voltage range, from 85 VAC to 300 VAC
(Reduced power factor above 275VAC)
• Automatic shutdown for input voltages above 300VAC
• Surge Protection
• Near-unity Power Factor; low input current distortion (THD)
• High efficiency
• Temperature monitoring and over-temperature protection
• Short circuit protection
• Constant power charging during battery recharge
• LED status indicators
1 Copyright ©: ELTEK Energy, LLC - 2007

Mechanical Power Core 17”W x 24.0” D x 10.5” H (including all covers)

Dimensions
Racked System 24.0”W x 24.0” D x 84” H (including all covers)
Power Core
Racked system total weight may vary depending on qty of
Weights Racked System
populated rectifiers and batteries.
Rectifier 4 pounds (1.8kg) each
Clearances Zero clearance needed below, left or right of unit. 4-6”
suggested rear clearance for proper airflow. Cable egress from
top / rear. Vertical clearance required, dependant on load cable
size/bend radius.
Electrical Full power output: 185 to 275 VAC (230VAC input nominal)
Voltage Range
Reduced power output: 85 to 184 VAC
Input Current 10.5 A AC at nominal input and full load
(Per rectifier) 12.2 A AC at 185VAC input and full load
Frequency 45-66 Hz
Voltage Range 43 – 59.5VDC (53.5VDC Nominal)
Scalable to 294A @48 VDC 42.0 A per rectifier
Current Maximum 14KW constant power during recharge (294 A
Output
@48VDC)
Ripple and < 100 mV peak to peak, 30 MHz bandwidth,
Noise < 1 mV RMS psophometric / 32dBrn-C
Connections Pluggable terminal blocks at rear of each rectifier power rack,
capable of accepting up to #10 AWG cables; one rectifier per
feed. Two 3/4” trade size conduit entries to covered rear AC
AC Input junction box. Two ¼”-20 ground studs are provided for direct
connection of chassis to (“green wire”) ground.
AC input breakers required: Seven (7) 15A feed breakers.

Frame Ground Four positions at top of rack, ¼”-20 on 1” centers
Landings for 20 sets of 2-hole lugs, ¼”-20 on 5/8” centers,
capable of accepting up to #1 AWG cables. 04 plug-in fuse or
DC Output
breaker positions, up to 100 ampere each
CO Ground One 2-hole lug, ¼”-20 on 5/8” centers

Battery Landings for Four sets of 2-hole lugs, 3/8”-16 on 1” centers.
Environmental Operating Temperature Range -40 to +45°C without derating, up to 75°C operation derated,
0 to +65°C - Ethernet interface
Storage Temperature Range -40 to +85°C
Relative Humidity 0-95%, non-condensing
Cooling - Rectifier Dual front to back fans, alarmed, temperature-controlled speed
Acoustic Noise < 55dBA @ 1 meter

Interface (Optional) Ethernet Interface WebPower interface, using TCP/IP standard Web Browser
The Web Interface will also support SNMP Protocol
Alarm Relays A minimum of Six (6) Form “C” relays,
Applicable Electrical safety IEC 60950-1, UL 60950
Standards EMC ETSI EN 300 386 V.1.3.2 (telecommunication network)
EN 61000-6-3 (emission, light industry)
EN 61000-6-2 (immunity, industry)
Harmonics EN 61000-3-2
Environment ETSI EN 300 019-2
ETSI EN 300 132-2

Product Ordering Information

DC System Product Description Part Number #
FP2 -48-300 -6U -48 VDC 6U Power Core
Consists of:
Core Power System with 7 rectifier positions, Smartpack Controller, 20
individually configured plug-in distribution positions.
FP2 -48 300 System -48 VDC complete power system in rack
Consists of:
Core Power System Installed in a 7’ high 23” wide rack rated for seismic
zone 4 applications. 7 rectifier positions, Smartpack Controller, 20
individually configured plug-in distribution positions.
Flatpack2 Rectifier Switchmode rectifier -48VDC 2000W (42A each @-48V)
ELTEK Energy LLC

115 Erick Street
Crystal Lake, Illinois 60014
USA
Phone: +1 (800) 447-3484 24-hour domestic service Helpline +1 (800) 435-4872

Phone: +1 (815) 459-9100 24-hour international service Helpline +1 (815) 479-0682
Sales FAX: +1 (815) 459-9118 Service FAX +1 (815) 459-0453
www.eltekenergy.com
info.americas@eltekenergy.com
Copyright ©: ELTEK Energy 2007

Flatpack2 Power
Flatpack2 48V 600A Power Core

-48V Potential, Current Maximum 672A
Models: FP2 (Power Core) with optional converters and front access features
Key System Features ______________________________

Power Core 5U- Distribution & Control Section consisting of:
One (1) Low Voltage Battery Disconnect (LVBD) contactor
Main Battery feed and return connections
24 position plug-in circuit breaker / fuse distribution
Each distribution bus is work rated for 600A continuous duty
Smartpack System Controller - Plug-in, hot swappable
Second controller position for I/O or Web expansion
Connectivity to alarm relays and external control input
connections
Service override switch (for controller replacement)
Power Core 4U- Rectifier Mounting Section, consisting of:

Positions for up to sixteen (16) Flatpack2 rectifiers. -48V with
42A maximum each
Dual AC Input feed configuration
Plug-in, hot swappable operation
Optional System Equipment

Optional TCP / IP or SNMP Agent via 10/100Mb Ethernet WAN port
Optional load shedding. Each distribution bus individually configurable.
Optional second 24 position distribution panel
Optional Front access for battery terminations
Positions for up to eight (8) Flatpack DC-DC Converters
Product Description
The Flatpack2 power core uses a 24 position, by three bus, Breaker matrix capable targeting compact system
solutions where minimum rack footprint is a primary consideration. Systems using the Flatpack2 600A design
are ideal for compact sites with minimum available floor space. This system is mounted in a 23” standard
telecommunication equipment rack. The compact size of this system allows more space for additional telecom
equipment even within the same rack. The standard system configuration accommodates (16) -48 VDC
Flatpack2 rectifiers, with a total power output of 32KW / 672A.
• Digital Communication over CAN-bus with Smartpack controller

FP2 Rectifier
• Autonomous, active current sharing between rectifier modules
• Wide input voltage range, from 85 VAC to 300 VAC
(Reduced power factor above 275VAC)
• Automatic shutdown for input voltages above 300VAC
• Surge Protection
• Near-unity Power Factor; low input current distortion (THD)
• High efficiency
• Temperature monitoring and over-temperature protection
• Short circuit protection
• Constant power charging during battery recharge
• LED status indicators

Flatpack2 Power
Smartpack Controller
The Smartpack extended digital controller is located in the control & alarm section and provides power system
control and monitoring functions. The system can be provided with the standard Smartpack extended by itself,
or along with the Smartpack slave for additional I/O capabilities. Standard Features include:
• Local user interface via a three-button keypad on the front panel
• 2 line x 16 character, high-contrast backlit LCD display
• Digital Communication over CAN-bus with each Flatpack2 rectifier
• Storage of setup parameters, alarm configuration and system history
in non-volatile memory
• Hot swappable
• Real time clock with battery backup
• Advanced battery monitoring and protection
• Recording of rectifier serial numbers and other information
• Load shedding control
Intersystem communications (between the • 6 digital inputs for site equipment alarms
Smartpack controller and each Flatpack2 • 6 user defined form “C” output contacts
rectifier) occurs via an internal LAN. Eltek
utilizes a digital communications network for real-time monitoring and control of critical equipment within the
power system. The Smartpack Controller is provided with the PowerSuite Software for local access to control
parameters via a PC.
Smartpack Web
The Smartpack Web unit will be located in the control & alarm section’s Primary slot. The second slot will
contain the Smartpack Slave unit. The Optional Webpack unit provides connectivity for optional access to the
WebPower user interface. This unit is removable from the front of the system to facilitate wiring access,
installation, and service. All wiring is routed out the rear of the unit. Features include:
• Web interface capability via a web browser
With SNMP Agent for remote monitoring and control via an
SNMP NMS
WAN connectivity at rear using standard RJ-45 UTP cabling
• (2) Additional alarm relays for customer connection
• Additional Battery temperature probe and symmetry monitoring
connections
• (2) Additional Digital (contact input) remote control connections
Smartpack Slave
The Smartpack slave unit, if ordered, will be located in the top control & alarm section’s second slot. The
addition of the Smartpack slave unit increases the I/O functionality by 6 additional inputs, and 6 additional
Form C contact outputs. This unit is removable from the front of the system to facilitate wiring access,
installation, and service. All wiring is routed out the rear of the unit. Features include:
• The Slave unit does not include a display or front interface

• (6) Additional alarm relays for customer connection
• Additional Battery temperature probe and symmetry monitoring
connections
• (6) Additional Digital (contact input) remote control connections
• Local Area communication with Master Smartpack Controller

Flatpack2 Power
Alarm & Control Connections
All customer control and alarm wiring terminations are accessible from the front of the system by opening the
Control cover. Wire clamp terminals are provided for the various input and output interface connections. All
control wiring entering the Smartpack interface area can pass through the cable management openings provided
at both the front side and rear side of the control section. A thermoplastic grommet guide prevents cable and
wire damage and reduces the sliding friction when installing interface connections.
DC Distribution Bus Connections
Each of the 24 positions can be individually configured to any bus.
AC Input Configuration
Requires: Eight (8) 30A feed breakers.
Each AC feed supplies two rectifiers. The power racks house four rectifiers each.
Rear View (Cover removed)

Flatpack2 Power
Optional Second Breaker Distribution

The power system can be delivered equipped with an additional distribution section consisting of an additional
24 Plug-in positions and can have various bus configuration capabilities.
Optional DC-DC Converters

The power system can be delivered equipped with DC-DC converters for –48V requirements. The system can
accept either 2 or 4 converter mounting shelves. Each mounting shelf houses Two (2) DC-DC converters. Each
Converter is capable of supplying 23A at –48V. The converters are fed directly from the DC bus and will each
draw a maximum load of 63A at a low input voltage of 19.0 VDC. The Converter output is Fixed at 55.0 VDC.
Converter output power will be routed to one of the three DC busses in the distribution, and can be accessed by
any of the variable breaker positions.
• +24V - -48V 1250W (23A Max each)

• Input Voltage Range: 19.5V – 30V
• Operating Temp: -40 to +65°C (-40 to +149°F)
• Output Efficiency: 90% Typical
• Output Voltage Fixed: -55.0 VDC

Flatpack2 Power
Mechanical Power Core 17”W x 24.0” D x 19.0” H (including all covers)

Dimensions
Racked System 24.0”W x 24.0” D x 84” H (including all covers)
Power Core
Racked system total weight may vary depending on qty of
Weights Racked System
populated rectifiers and batteries.
Rectifier 4 pounds (1.8kg) each
Clearances Zero clearance needed below, left or right of unit. 4-6”
suggested rear clearance for proper airflow. Cable egress from
top / rear. Vertical clearance required, dependant on load cable
size/bend radius.
Electrical Full power output: 185 to 275 VAC (230VAC input nominal)
Voltage Range
Reduced power output: 85 to 184 VAC
Input Current 10.5 A AC at nominal input and full load
(Per rectifier) 12.2 A AC at 185VAC input and full load
Frequency 45-66 Hz
Voltage Range 43 – 59.5VDC (53.5VDC Nominal)
Scalable to 672A @48 VDC 42.0 A per rectifier
Current Maximum 32KW constant power during recharge (672 A
Output
@48VDC)
Ripple and < 100 mV peak to peak, 30 MHz bandwidth,
Noise < 1 mV RMS psophometric / 32dBrn-C
Connections Pluggable terminal blocks at rear of each rectifier power rack,
capable of accepting up to #10 AWG cables; two rectifiers per
feed. Four (4) each, 1¼” trade size conduit entries to covered
rear AC junction box. Four (4) each ¼”-20 ground studs are
AC Input
provided for direct connection of chassis to PE (“green wire”)
ground.
AC input breakers required: eight (8) 30A feed breakers.

Frame Ground Four positions at top of rack, ¼”-20 on 1” centers
Landings for 24 sets of 2-hole lugs, ¼”-20 on 5/8” centers,
capable of accepting up to #1 AWG cables. 24 plug-in fuse or
DC Output
breaker positions, up to 100 ampere each
CO Ground One 2-hole lug, 3/8”–16 on 1” centers

Battery Landings for Eight sets of 2-hole lugs, 3/8”-16 on 1” centers.
Environmental Operating Temperature Range -40 to +45°C without derating, up to 75°C operation derated,
0 to +65°C - Ethernet interface
Storage Temperature Range -40 to +85°C
Relative Humidity 0-95%, non-condensing
Cooling - Rectifier Dual front to back fans, alarmed, temperature-controlled speed
Acoustic Noise < 55dBA @ 1 meter

Interface (Optional) Ethernet Interface WebPower interface, using TCP/IP standard Web Browser
The Web Interface will also support SNMP Protocol
Alarm Relays A minimum of Six (6) Form “C” relays,
Applicable Electrical safety IEC 60950-1, UL 60950
Standards EMC ETSI EN 300 386 V.1.3.2 (telecommunication network)
EN 61000-6-3 (emission, light industry)
EN 61000-6-2 (immunity, industry)
Harmonics EN 61000-3-2
Environment ETSI EN 300 019-2
ETSI EN 300 132-2

Flatpack2 Power
Product Ordering Information

DC System Product Description Part Number #
FP2 -48-600 -9U -48 VDC 9U Power Core
Consists of:
Core Power System with 16 rectifier positions, Smartpack Controller,
Smartpack expansion slot, 24 individually configured plug-in distribution
positions.
FP2 -48 600 System -48 VDC complete power system in rack
Consists of:
Core Power System Installed in a 7’ high 23” wide rack rated for seismic
zone 4 applications. 16 rectifier positions, Smartpack Controller, Smartpack
expansion slot, 24 individually configured plug-in distribution positions.
Flatpack2 Rectifier Switchmode rectifier -48VDC 2000W (42A each @-48V)
ELTEK Energy LLC

115 Erick Street
Crystal Lake, Illinois 60014
USA
Phone: +1 (800) 447-3484 24-hour domestic service Helpline +1 (800) 435-4872

Phone: +1 (815) 459-9100 24-hour international service Helpline +1 (815) 479-0682
Sales FAX: +1 (815) 459-9118 Service FAX +1 (815) 459-0453
www.eltekenergy.com
info.americas@eltekenergy.com
Copyright ©: ELTEK Energy 2007

F R O N T T E R M I N A L
The EnerSys® range of PowerSafe® V Front Terminal Valve Regulated Lead Acid
(VRLA) batteries has been designed specifically for use in applications that BATTERY
demand the highest levels of quality and reliability, now with optional top RANGE SUMMARY
termination on many V series models. With proven compliance to the most
rigorous international standards, PowerSafe V batteries are recognized
worldwide as the premium battery for Telecom applications. The PowerSafe V
battery’s reputation for long service life, together with excellent high rate
performance, also makes it ideal for high integrity, utility-industry switch gear
applications.
PowerSafe V batteries deliver superior performance while occupying less space

than conventional standby power batteries. The PowerSafe V Front Terminal
battery's compact design, suitable for 19 inch, 23 inch and ETSI (European
Telecommunications Standards Institute) racking, provides users with the benefit
of increased energy density. With electrical connections at the front or on top on
many models, installation and inspection are safer, quicker and easier.
PowerSafe V batteries are designed using proven gas recombination VRLA

technology, which removes the need for regular water addition by controlling the
evolution of hydrogen and oxygen during charging. Each cell incorporates its
own safety valve that allows automatically the controlled release of small
amounts of gas when pressure builds up within the cell.
The use of gas recombination technology for lead acid batteries has totally
changed the concept of standby power. This technology provides the user with
the freedom to use lead acid batteries in a wide range of applications. NCR48-V-170-4 NCR24-V-170-5-B
Features & Benefits

Capacity range: 31Ah - 170Ah
10 year design life
Front or top terminal connections available on many
models for safer installation and maintenance
Fully Wired 24VDC & 48VDC 23" NCR NEBS™ certified
relay racks with top common bus and optional individual
string side mounted circuit breakers
19” & 23” SpaceSaver™ relay racks with common bus
also with optional individual string side mount circuit
breakers available
UL94 V-0 flame retardant container and cover
High reliability
Proven long service life
NEBS certified
RESERVE
POWER
Publication No: US-VFT-RS-009 August 2010

Construction Installation & Operation Standards
• Robust positive plates are designed to • The PowerSafe V Front Terminal battery
® • Meets criteria for “non-spillable”
prolong service life and enhance corrosion range is designed for safer installation batteries. Properly packaged and
resistance and easy maintenance in cabinets or on identified non-spillable batteries are
• Separators are low resistance stands, close to the point of use. A exempt from U.S. and international
microporous Absorbed Glass Mat (AGM) separate battery room is not necessary dangerous goods regulations for ground,
fiber. The electrolyte is absorbed within sea and air transportation. See applicable
• It is recommended that PowerSafe V
the AGM, preventing acid spills in case of regulations and special provisions of the
Front Terminal batteries are installed on
accidental damage US DOT (U.S. Department of
their base
Transportation), ICAO (International Civil
• Container and cover in flame retardant • Recommended float charge voltage Aviation Organization), IATA (The Air
UL94-V0 ABS material, highly resistant to (27.36 VDc, 54.72 VDc) at 68°F (20°C) Transport Association) and IMDG
shock and vibration (27.18 VDc, 54.36 VDc) at 77°F (25°C) (International Maritime Code for
• Terminals are stainless steel front access • Six-month shelf life Dangerous Goods)
M6 studs (10mm wrench) with top access
• Reduced maintenance - no water addition • The management systems governing the
M8 (13mm wrench) copper alloy insert.
required manufacture of this product are ISO™
Top and front access terminations provide
• Maximum AC ripple voltage 0.5% RMS or 9001:2000 and ISO™ 14001:2004 certified
maximum conductivity. Retorque
connectors at 80% of installation torque. 1.5% P.P. • Complies with Telcordia ®
SR-4228,
8V100F does not have top access • Operating temperature Network Equipment Building System
capability On Charger: -4°F (-20°C) to 122°F (50°C) (NEBS™) Criteria Levels
• Self-regulating one way pressure relief Off Charger: -20°F (-30°C) to 113°F (45°C)
valves prevents ingress of atmospheric • Only water should be used to clean cover
oxygen and container
General Specifications
Capacity (Ah) Dimensions
PowerSafe® V Number Nominal 10 hr rate 8 hr rate Overall Typical Internal Installation
Battery of Voltage to 1.80Vpc to 1.75Vpc Length Width Height Weight Short Circuit Resistance Torque
Type Cells (V) @ 20°C @ 77°F mm in mm in mm in kg lbs Current (A) (mΩ) in-lbs Nm
12V30FT† 6 12 31 31 303 11.9 97 3.8 159 6.3 10.8 23.8 1327 9.87 44 5
12V38FT† 6 12 38 38 303 11.9 97 3.8 184 7.2 12.5 27.6 1500 8.53 44 5
12V62FT† 6 12 62 62 303 11.9 97 3.8 264 10.4 19.7 43.5 2100 5.87 44 5
12V92F-FT* 6 12 92 92 417 16.4 105 4.1 256 10.1 28.0 61.7 2500 5.05 44 5
8V100F* 4 8 100 100 384 15.1 125 4.9 228 9.0 32.0 70.5 3636 2.20 44 5
12V100FC 6 12 100 100 395 15.6 108 4.3 287 11.3 30.8 67.9 1900 6.60 44 5
12V101F 6 12 100 101 510 20.8 110 4.3 235 9.3 33.5 73.9 2108 5.92 80 9
12V105FS* 6 12 105 107 561 22.1 125 4.9 228 9.0 40.5 90.0 2455 4.40 80 9
12V125F* 6 12 125 126 561 22.1 105 4.1 316 12.4 46.0 101.4 2845 5.07 80 9
12V145F* 6 12 145 145 452 17.8 172 6.8 238 9.4 47.6 105.0 4100 3.00 80 9
Publication No. US-VFT-RS-009 - August 2010 - Subject to revisions without prior notice. E.&O.E.
12V155FS* 6 12 150 155 561 22.1 125 4.9 283 11.1 57.0 125.6 3714 3.30 80 9
12V170F* 6 12 170 170 561 22.1 125 4.9 316 12.4 67.0 147.7 3667 3.40 80 9
12V170FS* 6 12 170 170 561 22.1 125 4.9 283 11.1 50.5 111.3 2950 4.30 80 9
12V190F* 6 12 190 190 561 22.1 125 4.9 316 12.4 57.3 126.3 3625 3.50 80 9
Notes:
* With rope handles; † Optional handle MISC-0345 Telcordia® Values
Data subject to change without notice PowerSafe ®
Battery Type CLEI CPR

W 8V100F PWCYAT96AA 135660
L
12V92F PWHYAFPPAA 208135
12V100F PWCYAUA6AA 106531
12V125F PWCYAT26AA 203719
12V105FS PWHYANTPRA 213661
H 12V155FS PWHYAFSPAA 208137

12V170F PWHYAJNPAA 209645
12V155FS New Front or Top
Terminal Option
Distributed by:
EnerSys EnerSys Europe EnerSys Asia
P.O. Box 14145 Löwenstrasse 32 152 Beach Road
Reading, PA 19612-4145 8001 Zurich, Switzerland Gateway East Building
USA Level 11
Tel: +1-610-208-1991 189721 Singapore
+1-800-538-3627 Tel: +65 6508 1780
Fax: +1-610-372-8613 © 2010 EnerSys. All rights reserved.
www.enersys.com Trademarks and logos are the property of EnerSys
and its affiliates, except ISOTM, NEBSTM, SpaceSaverTM
and Telcordia®, which are not the property of
EnerSys.
DDm
RANGE SUMMARY
Publication No. US-DDm-RS-003 January 2005

Introducing the PowerSafe DDM
Construction
• Positive plate - Thick 0.252” lead-calcium-tin grids minimize corrosion and prolong life.
• Negative plate - Balanced lead-calcium grids optimize recombination efficiency.
• AGM separator - Mechanically strong, low electrical resistance, microporous glass fiber which
completely absorbs the electrolyte into its structure.
DDm • Container/Cover - Polypropylene standard. Optional flame retardant polypropylene available.
(UL94 V-0/L.O.I. 28%).
• Containers are single-piece construction.

The PowerSafe DDm range • Electrolyte - Diluted sulfuric acid.
offers an ideal solution for • Terminal post - Lead casting terminal. Threaded copper insert, with large surface area, to provide
large capacity valve regulated maximum conductivity.
lead-acid battery requirements.
PowerSafe DDm’s steel can • Terminal seal - Ring burn with secondary epoxy resin seal is 100% water bath tested in the
factory and proven in service.
(module) design concept, with
its integral racking system, • Relief valve - Operates at 2-3 psi and is complete with integral flame arrestor.
provides a cost effective
battery system with a compact,
Features
quick and simple installation
process. • 100% “out of box” initial battery capacity.
• VRLA recombinant technology - low maintenance - no watering required.
The PowerSafe DDm battery • Up to 2000 Ah in a single cell.
system’s cutting-edge • Frame design allows for maximum heat dissipation.
technology incorporates an
enhanced cell design with a • Certified to 1997 UBC Zone 4 to six high (48V) on DDm125 and eight high on DDm50,
DDm85 and DDm100 sizes.
superior racking system. The
enhanced cell incorporates • Steel module design. Cells factory installed in permanent steel modules with 1 or 2 cells per can.
thicker positive plates for
• Module can be configured 2, 3, 4 or 6 cells wide in single cell modules; 2, 4 or 6 cells wide in
longer life. The welded/epoxy, 2-cell modules for maximum flexibility.
dual post seal design provides
the highest integrity seal in the • Simplified installation.
industry. The large copper • Top termination standard.
post design also enhances the
high rate performance. • Clear flame retardant safety shields allow for easy visual inspection without removal.
Cells are encased in dedicated Benefits of the steel can (module) design
protective steel cans (modules) • Ease of installation. Simply set up rack and install modules.
that maintain constant, uniform
• Uniform and consistent compression.
compression for the life of the
cell. The easy to assemble • “Designed-In” thermal management allows maximum air flow.
racking system provides total
• Flexible configuration.
flexibility for system
configuration and allows fast, • Cell protection from damage during transport.
simple installation even in the
most difficult locations.
Installation
• Steel module design is easier to install. Does not require removal from protective
PowerSafe DDm, with its steel cans (modules) during installation.
optimized recombination
technology and extra thick
• Flexible configuration - 2, 3, 4 or 6 cells wide in single cell modules or 2, 4 or 6 cells wide in
2-cell modules.
plates, provides excellent
performance and service life • Total front access for easy maintenance.
across a wide range of • Floor anchoring - easy access during install, rack can be set before stowing modules.
applications including:
telecommunications, power • Top termination standard - optional side termination available.
generation/distribution sites, • Transition kits available to mount relay rack above battery system.
and UPS.
• Grounding kits available for bonding of all steel components.
www.enersys.com Publication No. US-DDm-RS-003 January 2005

Range Summary
DDm
GENERAL SPECIFICATIONS
Nominal Capacity (Ah) Nominal Dimensions
Cells 10hr. rate 8hr. rate Typical

Type per Nominal 1.80Vpc 1.75Vpc Length Height Depth (can) Depth (module) Weight
Module Voltage (V) @ 20°C @ 77°F mm in mm in mm in mm in kg lbs
2DDm50-09 2 4 200 200 188 7.4 165 6.5 333 13.1 366 14.4 34.3 75.4
2DDm50-13 2 4 300 300 265 10.4 165 6.5 333 13.1 366 14.4 49.5 108.9
DDm50-17 1 2 400 400 176 6.9 165 6.5 333 13.1 366 14.4 34.0 74.7
2DDm85-13 2 4 510 510 265 10.4 165 6.5 519 20.4 554 21.8 75.7 166.5
2DDm85-15 2 4 595 595 303 11.9 165 6.5 519 20.4 554 21.8 88.5 194.8
DDm85-21 1 2 850 850 214 8.4 165 6.5 519 20.4 554 21.8 64.5 142.0
DDm85-25 1 2 1020 1020 252 9.9 165 6.5 519 20.4 554 21.8 74.4 163.7
DDm85-27 1 2 1105 1105 271 10.7 165 6.5 519 20.4 554 21.8 80.8 177.8
DDm85-33 1 2 1360 1360 328 12.9 165 6.5 519 20.4 554 21.8 97.9 217.5
DDm100-21 1 2 1000 1000 214 8.4 165 6.5 590 23.2 624 24.5 73.5 163.4
DDm100-25 1 2 1200 1200 252 9.9 165 6.5 590 23.2 624 24.5 86.5 192.1
DDm100-27 1 2 1300 1300 271 10.7 165 6.5 590 23.2 624 24.5 92.0 204.3
DDm100-33 1 2 1600 1600 328 12.9 165 6.5 590 23.2 624 24.5 115.3 256.3
DDm125-25 1 2 1500 1500 252 9.9 226 8.9 562 22.1 597 23.5 112.3 249.6
DDm125-27 1 2 1625 1625 271 10.7 226 8.9 562 22.1 597 23.5 120.8 268.4
DDm125-33 1 2 2000 2000 328 12.9 226 8.9 562 22.1 597 23.5 144.1 320.3
CAN DEPTH CAN DEPTH
HEIGHT HEIGHT
H. NOM.
TYPE DD 50-YY
MODULE DEPTH MODULE DEPTH

ZZZ AH. NOM.
ZZZ AH. NOM.

TYPE DD 50-YY
TYPE DD 125-YY
LENGTH LENGTH
www.enersys.com Publication No. US-DDm-RS-003 January 2005

System Configurator
Nominal Stack Length Typical Cell Weight (1)

Nominal Nominal
Cells Row Stack
Type Ah per Height Depth 2 Wide 3 Wide 4 Wide 6 Wide Unpacked Packed
Capacity module mm in mm in mm in mm in mm in mm in kg Ibs. kg lbs
2DDm50-09 200 2 219.2 8.63 412.8 16.25 277.6 10.93 N/A N/A 467.6 18.41 657.9 25.90 21.3 47.0 22.8 50.3
2DDm50-13 300 2 219.2 8.63 412.8 16.25 353.8 13.93 N/A N/A 620.0 24.41 886.5 34.90 29.5 65.0 31.0 68.3
DDm50-17 400 1 219.2 8.63 412.8 16.25 441.5 17.38 619.0 24.37 791.2 31.15 1144.5 45.06 39.9 88.0 41.4 91.3
2DDm85-13 510 2 219.2 8.63 596.9 23.50 353.8 13.93 N/A N/A 620.0 24.41 886.5 34.90 43.6 96.0 45.1 99.3
2DDm85-15 595 2 219.2 8.63 596.9 23.50 391.9 15.43 N/A N/A 696.2 27.41 1000.8 39.40 50.4 111.0 51.9 114.3
DDm85-21 850 1 219.2 8.63 596.9 23.50 517.4 20.37 732.0 28.82 943.6 37.15 1412.2 55.60 72.1 159.0 73.6 162.3
DDm85-25 1020 1 219.2 8.63 596.9 23.50 593.6 23.37 846.3 33.32 1096.0 43.15 1640.1 64.57 83.0 183.0 84.5 186.3
DDm85-27 1105 1 219.2 8.63 596.9 23.50 631.7 24.87 903.7 35.58 1172.5 46.16 1755.4 69.11 90.3 199.0 91.8 202.3
DDm85-33 1360 1 219.2 8.63 596.9 23.50 746.0 29.37 1074.9 42.32 1400.8 55.15 2098.0 82.60 111.1 245.0 112.6 248.3
DDm100-21 1000 1 219.2 8.63 666.8 26.25 517.4 20.37 732.0 28.82 943.6 37.15 1412.2 55.60 83.9 185.0 85.4 188.3
DDm100-25 1200 1 219.2 8.63 666.8 26.25 593.6 23.37 846.3 33.32 1096.0 43.15 1640.1 64.57 99.3 219.0 100.9 222.3
DDm100-27 1300 1 219.2 8.63 666.8 26.25 631.7 24.87 903.7 35.58 1172.5 46.16 1172.5 69.11 107.1 236.0 108.6 239.3
DDm100-33 1600 1 219.2 8.63 666.8 26.25 746.0 29.37 1074.9 42.32 1400.8 55.15 2098.0 82.60 130.2 287.0 131.7 290.3
DDm125-25 1500 1 279.4 11.00 698.5 27.50 621.8 24.48 870.5 34.27 1127.0 44.37 1668.3 65.68 122.0 269.0 123.5 272.3
DDm125-27 1625 1 279.4 11.00 698.5 27.50 659.9 25.98 927.9 36.53 1203.2 47.37 1783.6 70.22 131.5 290.0 133.3 293.3
DDm125-33 2000 1 279.4 11.00 698.5 27.50 774.2 30.48 1099.0 43.27 1431.8 56.37 2126.2 83.71 161.0 355.0 162.5 358.3
(1) Includes hardware for calculating system weight
FORMULA
SYSTEM HEIGHT = (ROW HEIGHT x # OF CELL HIGH) + 9.0”
SYSTEM LENGTH = STACK LENGTH x # OF STACKS
SYSTEM WEIGHT = CELL WEIGHT x # OF CELLS
ACTUAL EXAMPLE: 24-DDm85-21, HEIGHT
4 cells wide per stack x 6 cells high per stack
SYSTEM HEIGHT = (8.63” x 6) + 9.0” = 60.78”

SYSTEM LENGTH = 37.15” x 1 = 37.15”
Publication No. US-DDm-RS-003 January 2005

SYSTEM WEIGHT = 159.0 lbs. x 24 = 3816.0 lbs.
ADDITIONAL EXAMPLE: 240-DDm125-25,

4 cells wide per stack x 6 cells high per stack
SYSTEM HEIGHT = (11.00” x 6) + 9.0” = 75.00”

SYSTEM LENGTH = 44.37” x 10 = 443.70”
SYSTEM WEIGHT = 269.0 lbs x 240 = 64,560.0 lbs.
LENGTH
DEPTH
EnerSys EnerSys EMEA Represented by:

P.O. Box 14145 Brussels, Belgium
Reading, PA 19612-4145 Tel:+32 (0)2 247 94 47
USA EnerSys Asia
Tel:+1-610-208-1991 Guangdong, China
+1-800-538-3627 Tel:+86 755 2689 3639
www.enersys.com
Printed in USA
Rackmount - Inverters
These inverters provide seamless back-up power for AC powered communications equipment from the site’s 48 or 24 VDC
battery system. A fast-acting transfer switch ensures voice and data transmissions remain uninterrupted in the event of a
power grid failure or if the site utility power is disconnected for maintenance and upgrade purposes. Built in a 2RU case
adaptable for 19” and 23” rack installations.
Features Specifications
• Pure sine wave AC output powers telecom equipment without
Model DC Input AC Output
performance degradation
Voltage Amps KVA WATTS
• Continuous duty rated – full output wattage maintained even
during extended power outages
48-1000RM 40-60 25 1 KVA 800
• 1000 VA and 2000 VA models available – easily cascaded for
N+1 redundancy, providing maximum reliability required by 48-2000RM 40-60 50 2 KVA 1600
data centers 24-1000RM 20-30 50 1 KVA 800
• Low EMI and RFI interference characteristics
• User-friendly Status and Diagnostic LCD/LED displays
• Utility bypass function with fast load transfer switch
• Remote Power Management optional via RS-232 port Displays
• Optional SNMP card LED: Inverter On, Overload, DC Abnormal, Fault
• Numerous circuit and load protections – over-current, over- LCD: Inverter On, Output Voltage and Frequency, Input
temp, overload, reverse polarity, high/low battery voltage Voltage, Load Percentage, DC Voltage, System Model, Internal
• Form C alarm contacts for monitoring AC “Fault” and “DC Environment Temperature, Utility Status, Short Circuit, Over
Abnormal” conditions Temperature
• Adapts for 19” or 23” racks; occupies only 2 RU (3.5”) Operating Temperature: 0° to 45° C
• UL and cUL listed Cooling: Forced air, front-to-back
Humidity: 0-90% relative humidity
Mechanical Acoustic Noise: 46 dBA @ 1 M
Dimensions: 17.4”W x 3.5”H x 11.6”D
Mounting: 19” or 23” Rack Alarms
Weight: 24-1000RM and 48-1000RM – 15.4 Lbs. Form C (Dry Contact) terminals (two sets – “DC ABNORMAL”
48-2000RM – 17.6 Lbs. and “FAULT”)
AC Characteristics Communication Interface

Voltage: 100/110/115/120 VAC (selectable using RS-232 port RS-232 port, serial cable included
and additional software); Factory set at 115 VAC
Frequency: 60 Hz. Standard, 50 Hz. Optional
Protection Features
Regulation: +/- 2%
DC Input Fuse and Breaker, AC Input Breaker, Output Breaker,
Wave Form: Pure Sine
Short Circuit, Overload, Over
Outlets Rear Panel:
Temperature, Over/Under Output Voltage, Over/Under Input
24-1000RM and 48-1000RM – (4 ea.) NEMA 5-15R
Voltage, Fan Failure Detection
48-2000RM – (4 ea.) NEMA 5-20R
Total Harmonic Distortion: 6% 120V/100% linear load 4%
Options
120V/100% SPS load
• Remote monitor via RS 232 port. SNMP card required.
Transfer Time: <4 ms.
Powering the Network

Newport Beach, CA USA www.newmartelecom.com • 800-854-3906
Specification sheet
ASTRO® DIGITAL
XTL™ 5000 Consolette
ASTRO Digital XTL 5000

Consolette models shown are
G80 (top) and G81 (bottom)
MODEL FEATURES
Local Control option G80 Compatible Digital Remote Control G81 Compatible
(G80) Options (G81) Options
• Up to 512 Modes • DC Power Supply • Up to 512 Modes •D
C Power Supply
• Full Keypad Interface •R
equires Digital Interface
• 8 Character/One Line • VU Meter/Clock Remote Deskset •D
igital ID Display via
Alphanumeric Display • Digital ID Display via (See R3-13-2006 for Digital Remote Deskset
Front Panel and Gold MC3000 Digital • Audio Interface board
• Includes Desk
Elite or MCC 5500 Desktop Controller) for Interface via a
Microphone and
Internal 5 Watt Speaker Console (requires • Allows Multiple Digital Remote Deskset
option L146) Remote Desksets to be
• Lightweight
• Tone Remote Control Connected
(16.1 lbs/7.3 kg)
and Digital connection •L
ightweight
to Gold Elite or (15.3 lbs/6.9 kg)
MCC 5500 Consoles
• Audio Interface board
for Interface via a W7
Style Local Control
Head
Motorola’s XTL 5000 Consolette is ideal for local It also supports ASTRO Spectra Consolette legacy
law enforcement, utility, and transportation users accessories such as the MC3000 Digital Deskset
that need a low cost RF control station within an and Junction Box.
ASTRO 25 system and want a wireless dispatch The XTL 5000 Consolette is offered in Local and
solution. The XTL 5000 Consolette can also be Digital Remote Control configurations to meet
utilized as an emergency backup station when the your organization’s particular needs.
infrastructure is off-line, as a low cost dispatch
center for state and local agencies, or as a fire
station alerting system.
The XTL 5000 Consolette supports the 896-940 MHz,
764-870 MHz, 380-470 MHz, 450-520 MHz, and
136-174 MHz frequency bands.
Specification sheet
ASTRO DIGITAL XTL 5000 Consolette
MODEL TYPE Local Control (G80 Option) Digital Remote Control (G81 Option)
Hardware Configuration Front Panel Operation with 3 x 4 Keypad for No Control Head on Station, Requires Digital
Direct Dialing, Electronic Mode/Volume Control Remote Deskset
Bands Supported VHF R1 (136-174 MHz) VHF R1 (136-174 MHz)
UHF R1 (380-470 MHz) UHF R1 (380-470 MHz)
UHF R2 (450-520 MHz) UHF R2 (450-520 MHz)
700-800 MHz (764-776 MHz (Talk-around) 700-800 MHz (764-776 MHz (Talk-around)
794-806 MHz 794-806 MHz
806-825 MHz 806-825 MHz
851-870 MHz (Talk-around)) 851-870 MHz (Talk-around))
900 MHz (896-901 MHz 900 MHz (896-901 MHz
935-940 MHz) 935-940 MHz)
Display 1 Line/8 Characters - Vacuum Fluorescent Display See R3-13-2006 for MC3000 Digital Desktop Controller
Channel Capability 512 512
Antenna Connector Type-N Female Type-N Female
External Equipment DB-25 Connector on Back Panel DB-25 Connector on Back Panel
Connectors RJ-45 Connector on Back Panel (requires L146)
Included with 6 Foot AC Line Cord 6 Foot AC Line Cord
Basic Package Desk Mic (Paddle Mic)
Internal 5 Watt Speaker
Optional Features Digital ID Display via Front Panel and Gold Elite or Digital ID Display via Digital Remote Deskset
(In addition to the standard MCC 5500 Console (requires L146)
XTL 5000 mobile features) Tone Remote Control and Digital connection to Gold
Elite or MCC 5500 Console
Dimensions 4.25” x 15.75” x 17” 4.25” x 15.75” x 17”
(107.95mm x 400.05mm x 431.8mm) (107.95mm x 400.05mm x 431.8mm)
Weight 16.1 lbs/7.3 kg 15.3 lbs/6.9 kg
L146 Option Tone Remote Control Console Control (Gold Elite or MCC 5500)
Supported Controllers Tone Desksets, Consoles, etc. Gold Series Elite Console with 3.0 Conventional and
MCC 5500 Dispatch Console
Analog Audio Connections 2 wire/4 wire 2 wire/4 wire
Selectable Modes Up to 8 modes Varies with Console options
(See R3-13-41C for Gold Series Elite Console and
RC-13-2012 for MCC 5500 Console)
Encryption Select Supported Supported
Monitor Supported Supported
ID Display at Remote Location Not Supported Supported
ID Types Displayed Remotely N/A PTT-ID
Emergency Call ID
Call Alerts
Emergency Alarm*
ID Signalling Types Supported N/A Digital Conventional
Digital Trunking (3600 Baud)
Digital Trunking (9600 Baud)
GENERAL PERFORMANCE SPECIFICATIONS
Modulation C4FM of QPSK-C family (Compatible Quadrature Phase Shift Keying)

Protocol Project 25-CAI 4.4 kbps IMBE, 2.8 kbps Error Correction Coding,
2.4 kbps Embedded Signalling
Channel Bandwidth VHF UHF R1 & R2 700-800 MHz 900 MHz
Analog 12.5/25 kHz 12.5/25 kHz 20/25 kHz 12.5 kHz
Digital 12.5/25 kHz 12.5/25 kHz 12.5/20/25 kHz N/A
Temperature Range –20° to +50°C
Humidity 90-95% Relative Humidity @ 50°C
Specification sheet
VOICE CODER*
Voice Coding Method IMBE (CAI): Improved Multi Band Excitation

Voice Truncation None
Frame Re-sync Interval 180 mSec (Clear Digital Mode)
Forward Error Correction Golay Code
Error Mitigation Project 25-CAI
(IMBE) Dual Level Level 1: Extrapolates & replaces 20 mSec voice frames that exceed the error correction
algorithm tolerance.
Level 2: Progressive muting of 20 mSec voice frames that are too severely damaged for
Level 1 replacement.
Code Book Structure APCO Project-25 (IMBE): No Code Book
SIGNALING (ASTRO MODE)*
Signaling Rate 9.6 kbps

Digital ID Capacity 10,000,000 Conventional/64,000 Trunking
Digital Network Access Codes 4,096 Network Site Addresses
ASTRO Digital User
Group Addresses 4,096
Project 25-CAI Digital
User Group Addresses 65,000 Conventional/4,094 Trunking
Error Correction Techniques Golay, BCH, Reed-Solomon Codes
Data Access Control Slotted CSMA: Utilizes infrastructure-sourced data status bits embedded in both voice and
data transmissions
ENCRYPTION*
Encryption Algorithm Capacity 5 algorithms per radio

Encryption Keys per Radio 48 keys (ASTRO compatible)
Encryption Frame Re-sync
Interval Project 25-CAI: 360 mSec
Encryption Keying Key Variable Loader
Synchronization Counter Addressing and Cipher Feedback and Output Feedback
Code Key Generator External hand-held microprocessor controlled key Variable Loader and Key Management Controller
Encryption Key Tag Capacity
per System 65,000
Number of Unique Keys Dependent on encryption algorithm
Code Key Initialization Internally derived pseudo-random initializing vector
Key Storage Volatile electronic memory or non volatile electronic memory
Key Erasure Keyboard command and tamper detection
FCC TYPE ACCEPTANCE ID
Band Transmitter Power Output Number

VHF (136-174 MHz) 10-50 Watts AZ492FT3806
UHF R1 (380-470 MHz) 10-40 Watts AZ492FT4862
UHF R2 (450-520 MHz) 10-45 Watts AZ492FT4862
700/800 MHz (764-870 MHz) 10-35 Watts AZ492FT5823**
900 MHz (896-940 MHz) 10-30 Watts AZ492FT5847
POWER REQUIREMENTS
AC Requirements 105-132, 187-265 VAC, 47-63 Hz

Power Supply AC Current Drain (Typical) (110 VAC/220 VAC) duty Cycle EIA 10-10-80
VHF UHF 800 MHz 900 MHz

* Not available on 900 MHz models.
RF Output 0-50W 10-40W Range 1 10-35W** 10-30W
** 30 Watts Maximum in Talkaround. 10-45W Range 2
The ASTRO Digital XTL 5000 Consolette
Receive 0.7A/0.4A 0.7A/0.4A 0.7A/0.4A 0.7A/0.4A
is FCC approved as a control station
under part 90.213. Transmit 2.30A/1.16A 2.30A/1.16A 2.30A/1.16A 2.30A/1.16A
Specification sheet
TRANSMITTER
VHF UHF R1 & R2 700-800 MHz 900 MHz

Frequency Range/Bandsplits 136-174 MHz 380-470 MHz 794-806, 764-776 MHz 896-901 MHz
450-520 MHz 806-825, 851-870 MHz 935-940 MHz
Channel Spacing 12.5/25 kHz 12.5/25 kHz 12.5/20/25 kHz 12.5 kHz
Maximum Frequency Separation Full Bandsplit Full Bandsplit Full Bandsplit Full Bandsplit
Frequency Stability†
Operating Frequency Accuracy*
(–20°C to +50°C; +25°C Ref.) ±0.00020% ±0.00020% ±0.00015% ±0.00015%
Modulation Limiting†
25 kHz Channels ±5.0 kHz ±5.0 kHz ±5.0 kHz (NPSPAC)
20 kHz Channels ±4.0 kHz (NPSPAC)
12.5 kHz Channels ±2.5 kHz ±2.5 kHz ±2.5 kHz ±2.5 kHz
Modulation Fidelity (C4FM)*
12.5 kHz Digital Channels ±2.8 kHz ±2.8 kHz ±2.8 kHz N/A
FM Hum & Noise†
20/25 kHz –50 dB –45 dB –40 dB
12.5 kHz –40 dB –40 dB –34 dB –38 dB
(Hear Clear off)
Emissions (Conducted & Radiated)†* –85 dBc –85 dBc –70 dBc/–85 dBc (GNSS) –70 dBc
Audio Response†
(6 dB/Octave Pre-emphasis from
300 to 3000 Hz) +1, –3 dB (EIA) +1, –3 dB (EIA) +1, –3 dB (EIA) +1, –3 dB (EIA)
Audio Distortion per EIA† 2% 2% 2% 3%
Output Impedance 50 ohms
RECEIVER
VHF UHF R1 & R2 700-800 MHz 900 MHz

Frequency Range/Bandsplits 136-174 MHz 380-470 MHz 764-776 MHz 935-940 MHz
450-520 MHz 851-870 MHz
Channel Spacing 12.5/25 kHz 12.5/25 kHz 12.5/20/25 kHz 12.5 kHz
Optional Pre-Amp No No No No
Analog Sensitivity†
20 dB Quieting (20/25 kHz channel) 0.4 µV 0.4 µV 0.30 µV 0.30 µV
12 dB SINAD per EIA (20/25 kHz channel) 0.3 µV 0.3 µV 0.25 µV 0.25 µV
Digital Sensitivity*
1% BER (12.5 kHz channel) 0.4 µV 0.4 µV 0.30 µV
5% BER (12.5 kHz channel) 0.3 µV 0.3 µV 0.25 µV N/A
Adjacent Channel Rejection (Selectivity)†
(20/25 kHz channel) –80 dB –82 dB –80 dB
(12.5 kHz channel) –70 dB –75 dB –65 dB –65 dB
Intermodulation Rejection†*
(20/25 kHz channel) –85 dB –85 dB –80 dB –70 dB
† Measured in the analog mode per
Spurious Response Rejection†* –90 dB –90 dB –90 dB –80 dB
TIA/EIA 603.
* Measured in digital mode per TIA/EIA
Audio Output at External Speaker
TSB102.CAAB (Local Control Only) 5 Watts @ less than 3% Distortion
All specifications are typical. Input Impedance 50 ohms
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com/governmentandenterprise 1-800-367-2346
R3-1-2022D
Specification sheet
ASTRO XTL™ 1500 ®
Digital Mobile Radio
MODEL FEATURES
Frequency Bands
• 136-174 MHz
• 380-470 MHz
• 450-520 MHz
• 764-870 MHz
Power Levels
• 10-50 Watt (136-174 MHz)
• 10-40 Watt (380-470 MHz)
• 10-45 Watt (450-520 MHz)
• 10-35 Watt (764-870 MHz)
48 Channels (Standard)
Meets Military Specs 810 (C,D, E and F)
Dual mode operation (ASTRO Digital and Analog)
Utilizes Windows®-based customer
9600 or 3600 Baud features
programming software
Project 25 capability on Conventional and
Built in FLASHport™ support
Trunking systems
Optional Keypad microphone
Project 25 compliance interoperable voice
signaling features Internal Speaker
Bandwidth Receiver Text Messaging
• 12.5/25/30 kHz (analog) – 136-174 MHz OTAP (Over the air programming)
• 12.5/25 kHz (analog) – 380-470 MHz and
450-520 MHz
• 12.5/20/25 kHz (analog) – 764-870 MHz AVAILABLE WITH SOFTWARE
ENHANCEMENT PACKAGE
12.5 kHz bandwidth receiver (digital)
512 Channels
4 Programmable buttons
Encryption capability (ADP)
Emergency button
Integrated voice and data capable
Dash mount
Motorola’s XTL 1500 Project 25 compliant 380-470MHz, 450-520 MHz 764-870 MHz frequency
mobile radio is tough and well suited for users bands and supports a subset of the accessories
in a construction, utility, petroleum, and local common to the XTL 2500 mobile radio.
law enforcement environment. Taking into The XTL 1500 digital mobile radio is specifically
consideration your work environment and various designed to meet the needs of your organization.
job responsibilities, this robust mobile radio will When you want high performance, quality, and
support the type of consistent, high quality reliability in your daily communications, the XTL 1500
communication you need. digital mobile radio is the radio of choice.
The XTL 1500 digital mobile radio supports APCO
Project 25 and is available in 136-174 MHz,
Specification sheet
ASTRO® XTL™ 1500

Frequency range 36-174 MHz

1
380-470 MHz
450-520 MHz
764-870 MHz
Modulation C4FM of QPSK-C family
(Compatible 4-Level Frequency Modulation and Compatible Quadrature Phase Shift Keying)
Protocol
Project 25-CAI 4.4 kbps IMBE, 2.8 kbs Error Correction Coding, 2.4 kbps
Embedded Signaling
Channel Bandwidth
Analog 2.5/25/30 kHz (136-174 MHz)
1
12.5/25 kHz (380-470 MHz and 450-520 MHz);
12.5/20/25 kHz (764-870 MHz)
Digital 12.5 kHz
VOICE CODER
Voice Coding Method IMBE (CAI) Improved Multi Band Excitation (IMBE)
Forward Error Correction Golay code
Error Mitigation Project 25-CAI (IMBE)
Dual Level evel 1: Extrapolates and replaces 20 mSec voice frames that exceed
L
the error correction algorithm tolerance.
Level 2: Progressive muting of 20 mSec voice frames that are too
severely damaged for Level 1 replacement.
Code Book Structure APCO Project 25 (IMBE): No code book
SIGNALLING (ASTRO MODE)
Signalling Rate 9.6 kbps

Digital ID Capacity 10,000,000 Conventional / 48,000 Trunking
Digital Network Access Codes 4,096 network site addresses
ASTRO Digital User Group Addresses 4,096 network site addresses
Project 25 – CAI Digital
User Group Addresses 65,000 Conventional / 4,094 Trunking
Error Correction Techniques Golay, BCH, Reed-Solomon codes
Data Access Control lotted CSMA: Utilizes infrastructure-sourced data status bits embedded in
S
both voice and data transmissions.
speaker MOBILE
Dimensions .5” x 5.5” x 2.5”

5 Dimensions Radio Transceiver
(139.7 x 139.7 x 63.5 mm) 2” x 7” x 7.8” (51 x 179 x 197 mm)
(Excluding mounting bracket) Control Head
Weight 1.5 lbs (0.7 kg) 2.6” x 7.3” x 2.7” (65 x 185 x 69 mm)
Radio Transceiver and Control Head
2.6” x 7.3” x 9.8” (65 x 185 x 248 mm)
Weight Radio Transceiver and Control Head
5.2 lbs (2.34 kg) (764-870 MHz and 136-174 MHz)
5.2 lbs (2.32 kg) (380-470 MHz and 450-520 MHz)
Specification sheet
ASTRO® XTL™ 1500

transmitter
Frequency 764-776 MHz 380-470 MHz (Range 1) 136-174 MHz

794-806 MHz and
806-825 MHz 450-520 MHz (Range 2)
851-870 MHz
RF Power 10-30W (764-806 MHz) 10-45W (450-500 MHz) 10-50W
10-35W (806-870 MHz) 10-40W (500-512 MHz)
10-25W (512-520 MHz)
Max Freq Separation Full Bandsplit Ref Above Bandsplit Full Bandsplit
Freq Stability Operating Freq Accuracy
(–30°C to +60°C;+25°C Ref) - 700/800 & UHF
(± 2 ppm (–30°C to +60°C) - VHF 1.5 ppm 2 ppm 2 ppm
Modulation Limiting
25/20 kHz, 25 kHz, 25/30 kHz channel ±5 kHz, +/-4 kHz (NPSPAC) ±5 kHz ±5 kHz
12.5 kHz channel ±2.5 kHz ±2.5 kHz ±2.5 kHz
Modulation Fidelity (C4FM)
12.5 kHz digital channel ±2.8 kHz ±2.8 kHz ±2.8 kHz
Channel Spacing Analog 12.5/20/25 kHz 12.5/25 kHz 12.5/25/30 kHz
FM Hum and Noise
20/25 kHz, 25 kHz, 20/25 kHz 40 dB 45 dB 45 dB
12.5 kHz 34 dB 40 dB 40 dB
Emissions Conducted Radiated Conducted Radiated Conducted Radiated
(GNSS=Global Navigation Satellite System) –70 dBc –20 dBm –85 dBc –20 dBm –85 dBc –20 dBm
–85 dBc (GNSS) –40 dBm (GNSS)
Audio Response
(6 dB/Octave Pre-emphasis
from 300 to 3000 Hz) +1, –3 dB (EIA) +1, –3 dB (EIA) +1, –3 dB (EIA)
Audio Distortion per EIA 3% 3% 3%
POWER AND BATTERY DRAIN FCC TYPE ACCEPTANCE ID
Model Type 36-174 MHz

1 Output Transmitter
380-470 MHz Band Power Number
450-520 MHz 136-174 MHz 10-50 W AZ492FT3806
764-870 MHz
380-470MHz 10-40 W AZ492FT4862
Minimum RF Power Output 0-50 Watt (136-174 MHz)
1
450-520 MHz 10-45 W AZ492FT4867
10-40 Watt (380-470 MHz)
10-45 Watt (450-520 MHz) 764-870 MHz 10-35 W AZ492FT5823
10-35 Watt (764-870 MHz)
25-110 Watt (136-174 MHz)
ENVIRONMENTAL SPECIFICATIONS
25-110 Watt (380-470 MHz)
Operation 3.8V DC ±20% Negative
1 Operating Temperature –30ºC / +60ºC
Ground Storage Temperature –55ºC / +85ºC
Standby at 13.8V Ingress Protection IP54 certified
136-174 MHz (10-50 Watt) 0.85A
380-470 MHz (10-40 Watt) 0.85A
450-520 MHz (10-45 Watt) 0.85A
764-870 MHz (10-35 Watt) 0.85A
Receive at Rate Audio at 13.8V
136-174 MHz (10-50 Watt) 3.2A
380-470 MHz (10-40 Watt) 3.2A
450-520 MHz (10-45 Watt) 3.2A
764-870 MHz (10-35 Watt) 3.2A
Transmit Current (A) at Rated Power (W)
136-174 MHz (10-50 Watt) 13A (50W)
380-470 MHz (10-40 Watt) 11A (40W)
450-520 MHz (10-45 Watt) 11A (45W)
764-870 MHz (10-35 Watt) 12A (35W)
Specification sheet
ASTRO® XTL™ 1500

receiver

794-806 MHz and
806-825 MHz 450-520 MHz (Range 2)
851-870 MHz
Channel Spacing 12.5 / 20 / 25 kHz 12.5 / 25 kHz 12.5 / 25 / 30 kHz
Maximum Frequency Separation Full Bandsplit Full Bandsplit Full Bandsplit
Option Pre-Amp No No No
Analog Sensitivity
20 dB Quieting .30 µV 0.40 µV 0.40 µV
12 dB SINAD per EIA .25 µV 0.30 µV 0.30 µV
Digital Sensitivity
1% BER (12.5 kHz channel) .30 µV 0.40 µV 0.40 µV
5% BER (12.5 kHz channel) .25 µV 0.30 µV 0.30 µV
Intermodulation Distortion 80 dB 85 dB 85 dB
Spurious Response Rejection 90 dB 90 dB 90 dB
Audio Output Power at 3% distortion 7.5 W (8 Ω ext. speaker) 7.5 W (8 Ω ext. speaker) 7.5 W (8 Ω ext. speaker)
(External/Internal Speaker) 3 W (int. speaker) 3 W (int. speaker) 3 W (int. speaker)
Adjacent Channel Rejection Selectivity 65 dB / 80 dB 75 dB / 82 dB 75 dB / 82 dB
(12.5 kHz/25 kHz)
Audio Response (6 dB/Octave De-emphasis
MILITARY STANDARDS 810 C, D, E, & F
MIL-STD 810C MIL-STD 810D MIL-STD 810E MIL-STD 810F

Method Proc./Cat. Method Proc./Cat. Method Proc./Cat. Method Proc./Cat.
Low Pressure 500.1 I 500.2 II 500.3 II 500.4 II
High Temperature Storage 501.1 I 501.2 I/A1 501.3 I/A1 501.4 I/Hot
High Temperature Operational 501.1 II 501.2 II/A1 501.3 II/A1 501.4 I/Hot
Low Temperature Storage 502.1 I 502.2 I/C3 502.3 I/C3 502.4 I/C3
Low Temperature Operational 502.1 I 502.2 II/C1 502.3 II/C1 502.4 II/C1
Temperature Shock 503.1 - 503.2 I/A1-C3 503.3 I/A1-C3 503.4 I/Hot-C3
Solar Radiation 505.1 II 505.2 I 505.3 I 505.4 I
Rain Blowing 506.1 I 506.2 I 506.3 I 506.4 I
Rain Steady 506.1 II 506.2 II 506.3 II 506.4 III
Humidity 507.1 II 507.2 II 507.3 II 507.4 -
Salt Fog 509.1 - 509.2 - 509.3 - 509.4 -
Blowing Dust 510.1 I 510.2 I 510.3 I 510.4 I
Blowing Sand 510.2 II 510.3 II 510.4 II
Vibration Minimum Integrity 514.2 VIII/F, Curve-W 514.3 I/10 514.4 I/10 514.5 I/24
Vibration Loose Cargo 514.3 II/3 514.4 II/3 514.5 II/5
Shock Functional 516.2 I 516.3 I 516.4 I 516.5 I
Shock Crash Hazard 516.2 III 516.3 V 516.4 V 516.5 V
Shock Bench Handling 516.2 V 516.3 VI 516.4 VI 516.5 VI
R3-1-2027E
Specification sheet
MODEL FEATURES
Frequency Bands
• 136-174 MHz
• 380-470 MHz
• 450-520 MHz
• 764-870 MHz
Power Levels
• 10-50 Watt (136-174 MHz)
• 10-40 Watt (380-470 MHz)
• 10-45 Watt (450-520 MHz)
• 10-35 Watt (764-870 MHz)
• 25-110 Watt (136-174 MHz)
• 25-110 Watt (380-470 MHz) Utilizes Windows®-based customer
870 Channels (Standard) software programming
Dual mode operation (ASTRO Digital and Analog) Built in FLASHport™ support
9600 and 3600 Baud capable Optional Keypad microphone
Project 25 capability on Conventional and External Speaker
Trunking systems USB/RS232 connectivity
Type II Trunking Only Optional Siren PA
Project 25 compliance interoperable voice Optional DEK
signaling features Upgradable
Integrated voice and data capable Encryption Capable:
Bandwidth Receiver • Type III (optional)
• 12.5/25/30 kHz (analog) – 136-174 MHz • Allows for MultiKey for single algorithms ONLY
• 12.5/25 kHz (analog) – 380-470 MHz and • Algorithms supported:
450-520 MHz - DVI-XL
• 12.5/20/25 kHz (analog) – 764-870 MHz - DVP-XL
12.5 kHz bandwidth receiver (digital) - DES
- DES-XL
5 Programmable buttons x 4 deep in menu functions
- DES-OFB
14 digit character display - AES
Tri-color Backlit LCD display - Advanced Digital Privacy (ADP)
Emergency button Dual Control Head
Multi level display dim button OTAP (Over-the-air programming)
Dash/Remote mount Tactical OTAR (Over-the-air re-keying)
Meets Military Specs 810 (C,D, E and F) Text Messaging
Motorola’s XTL 2500 Project 25 compliant mobile 380-470MHz, 450-520 MHz 764-870 MHz frequency
radio is tough and well suited for users in Police, bands and supports the accessories common to the
Fire, EMS, State/Local/Federal Government XTL 5000 mobile radio.
agencies. Taking into consideration your work The XTL 2500 digital mobile radio is specifically
environment and various job responsibilities, designed to meet the needs of your organization.
this robust mobile radio will support the type of When you want high performance, quality, and
consistent, high quality communication you need. reliability in your daily communications, the XTL 2500
The XTL 2500 digital mobile radio supports APCO digital mobile radio is the radio of choice.
Specification sheet
ASTRO® XTL™ 2500


1
380-470 MHz
450-520 MHz
764-870 MHz
Protocol
Embedded Signaling
Channel Bandwidth
Analog 2.5/25/30 kHz (136-174 MHz)
1
12.5/25 kHz (380-470 MHz and 450-520 MHz);
12.5/20/25 kHz (764-870 MHz)
Digital 12.5 kHz
VOICE CODER
L

S
speaker MOBILE

5 Dimensions Mid Power Radio Transceiver
(139.7 x 139.7 x 63.5 mm) 2” x 7” x 7.8” (50.8 x 177.8 x 198.1 mm)
Weight 1.5 lbs (0.68 kg) 2.35” x 7.1” x 2.5” (59.7 x 180.3 x 63.5 mm)
Mid Power Radio Transceiver and Control Head–
Dash Mount
2.35” x 7.1” x 9.1” (59.7 x 180.3 x 231.1 mm)
High Power Transceiver
2.765” x 8.08” x 12.31” (70.2 x 205.2 x 312.7 mm)
Weight Mid Power Radio Transceiver and Control Head
6.1 lbs (2.77 kg) (764-870 MHz and 136-174 MHz)
6.1 lbs (2.77 kg) (380-470 MHz and 450-520 MHz)
High Power Radio Transceiver with Handle
8.8 lbs (3.99 kg) (136-174 MHz and 380-470 MHz)
Specification sheet
ASTRO® XTL™ 2500

transmitter

794-806 MHz and
806-825 MHz 450-520 MHz (Range 2)
851-870 MHz
RF Power 10-30W (764-806 MHz) 10-45W (450-500 MHz) 10-50W or 25-110W
10-35W (806-870 MHz) 10-40W (500-512 MHz)
10-25W (512-520 MHz)
(–30°C to +60°C;+25°C Ref) - 700/800 & UHF
Modulation Limiting
FM Hum and Noise
12.5 kHz 34 dB 40 dB 40 dB
(GNSS=Global Navigation Satellite System) –85 dBc (GNSS) –40 dBm (GNSS) –85 dBc –20 dBm –85 dBc –20 dBm
Audio Response

450-520 MHz
136-174 MHz 10-50 W AZ492FT3806
764-870 MHz
380-470MHz 10-40 W AZ492FT4862
1
10-35 Watt (764-870 MHz)
1
Ground
Standby at 13.8V
136-174 MHz (10-50 Watt) 0.85A Operating Temperature –30ºC / +60ºC
380-470 MHz (10-40 Watt) 0.85A Storage Temperature –55ºC / +85ºC
450-520 MHz (10-45 Watt) 0.85A
Ingress Protection IP54 certified
764-870 MHz (10-35 Watt) 0.85A
136-174 MHz (25-110 Watt) 0.85A
380-470 MHz (25-110 Watt) 0.85A
136-174 MHz (10-50 Watt) 3.2A
380-470 MHz (10-40 Watt) 3.2A
450-520 MHz (10-45 Watt) 3.2A
764-870 MHz (10-35 Watt) 3.2A
136-174 MHz (25-110 Watt) 3.2A
380-470 MHz (25-110 Watt) 3.2A
136-174 MHz (10-50 Watt) 13A (50W)
380-470 MHz (10-40 Watt) 11A (40W)
450-520 MHz (10-45 Watt) 11A (45W)
764-870 MHz (10-35 Watt) 12A (35W)
136-174 MHz (25-110 Watt) 20A (100W)
380-470 MHz (25-110 Watt) 24A (100W)
Specification sheet
ASTRO® XTL™ 2500

receiver

794-806 MHz and
806-825 MHz 450-520 MHz (Range 2)
851-870 MHz
Analog Sensitivity Pre-amp Standard Pre-Amp Standard
20 dB Quieting .30 µV 0.25 µV 0.40 µV 0.25 µV 0.40 µV
12 dB SINAD per EIA .25 µV 0.20 µV 0.30 µV 0.20 µV 0.30 µV
Digital Sensitivity
1% BER (12.5 kHz channel) .30 µV 0.25 µV 0.40 µV 0.25 µV 0.40 µV
Intermodulation Distortion 80 dB 80 dB 85 dB 80 dB 85 dB
Spurious Response Rejection 90 dB 90 dB 90 dB 90 dB 90 dB
(External/Internal Speaker) 13 W (3.2 Ω ext. speaker) 13 W (3.2 Ω ext. speaker) 13 W (3.2 Ω ext. speaker)
(12.5 kHz/25 kHz)

Humidity 507.1 II 507.2 II 507.3 II 507.4 -
Salt Fog 509.1 - 509.2 - 509.3 - 509.4 -
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com/secondnature 1-800-367-2346
R3-1-2028D
Specification sheet
MODEL FEATURES
Frequency Bands
• 136-174 MHz
• 380-470 MHz
• 450-520 MHz
• 764-870 MHz
Power Levels
• 10-50 Watt (136-174 MHz)
• 10-40 Watt (380-470 MHz)
• 10-45 Watt (450-520 MHz)
• 10-35 Watt (764-870 MHz)
• 25-110 Watt (136-174 MHz)
• 25-110 Watt (380-470 MHz) Multi level display dim button
1000 Channels (Standard) Dash/Remote mount
Dual mode operation (ASTRO Digital and Analog) Meets Military Specs 810 (C,D, E and F)
9600 and 3600 Baud capable Utilizes Windows®-based customer
Project 25 capability on Conventional and programming software
Trunking systems Built in FLASHport™ support
Type II Trunking Only Optional Keypad microphone
Project 25 compliance interoperable voice External Speaker
signaling features
USB/RS232 connectivity
Integrated voice and data or RS232 capable
Optional Siren PA
Programming Over Project 25 (POP25)
Optional DEK
Over the Air Re-key (OTAR)
Upgradable
Multiple Control Heads (up to 4)
Encryption Capable:
Bandwidth Receiver • Type III (optional)
• 12.5/25/30 kHz (analog) – 136-174 MHz • Allows for MultiKey for single algorithms ONLY
• 12.5/25 kHz (analog) – 380-470 MHz and • Algorithms supported:
450-520 MHz - DVI-XL
• 12.5/20/25 kHz (analog) – 764-870 MHz - DVP-XL
12.5 kHz bandwidth receiver (digital) - DES
- DES-XL
5 Programmable buttons x 4 deep in menu functions
- DES-OFB
4 line / 14 digit character display - AES
Multiple Color Backlit LCD display - Advanced Digital Privacy (ADP)
Emergency button Reuse of most ASTRO/MCS accessories
Motorola’s XTL 5000 Project 25 compliant mobile 380-470MHz, 450-520 MHz 764-870 MHz frequency
radio is tough and well suited for users in Police, bands and supports the accessories common to the
Fire, EMS, State/Local/Federal Government XTL platform.
agencies. Taking into consideration your work The XTL 5000 digital mobile radio is specifically
environment and various job responsibilities, designed to meet the needs of your organization.
this robust mobile radio will support the type of When you want high performance, quality, and
consistent, high quality communication you need. reliability in your daily communications, the XTL 5000
The XTL 5000 digital mobile radio supports APCO digital mobile radio is the radio of choice.
Specification sheet
ASTRO® XTL™ 5000


1
380-470 MHz
450-520 MHz
764-870 MHz
Protocol
Embedded Signaling
Channel Bandwidth
Analog 2.5/25/30 kHz (136-174 MHz)
1
12.5/25 kHz (380-470 MHz and 450-520 MHz);
12.5/20/25 kHz (764-870 MHz)
Digital 12.5 kHz
VOICE CODER
L

S
speaker MOBILE

5 Dimensions Mid Power Radio Transceiver
(139.7 x 139.7 x 63.5 mm) 2” x 7” x 7.8” (50.8 x 177.8 x 198.1 mm)
Weight 1.5 lbs (0.68 kg) 2.0” x 7.1” x 2.5” (50.8 x 180.3 x 63.5 mm)
Mid Power Radio Transceiver and Control Head–
Dash Mount
2.0” x 7.1” x 9.1” (50.8 x 180.3 x 231.1 mm)
High Power Transceiver
2.765” x 8.08” x 12.31” (70.2 x 205.2 x 312.7 mm)
6.1 lbs (2.77 kg) (764-870 MHz and 136-174 MHz)
6.1 lbs (2.77 kg) (380-470 MHz and 450-520 MHz)
8.8 lbs (3.99 kg) (136-174 MHz and 380-470 MHz)
Specification sheet
ASTRO® XTL™ 5000

transmitter

794-806 MHz and
806-825 MHz 450-520 MHz (Range 2)
851-870 MHz
RF Power 10-30W (764-806 MHz) 10-45W (450-500 MHz) 10-50W or 25-110W
10-35W (806-870 MHz) 10-40W (500-512 MHz)
10-25W (512-520 MHz)
(–30°C to +60°C;+25°C Ref) - 700/800 & UHF
Modulation Limiting
FM Hum and Noise
12.5 kHz 34 dB 40 dB 40 dB
(GNSS=Global Navigation Satellite System) –70 dBc –20 dBm –85 dBc –20 dBm –85 dBc –20 dBm
–85 dBc (GNSS) –40 dBm (GNSS)
Audio Response

450-520 MHz
136-174 MHz 10-50 W AZ492FT3806
764-870 MHz
380-470MHz 10-40 W AZ492FT4862
1
10-35 Watt (764-870 MHz)
1
Ground
Standby at 13.8V
136-174 MHz (10-50 Watt) 0.85A Operating Temperature –30°C / +60°C
380-470 MHz (10-40 Watt) 0.85A Storage Temperature –55ºC / +85ºC
450-520 MHz (10-45 Watt) 0.85A
International Protection IP54 certified
764-870 MHz (10-35 Watt) 0.85A
136-174 MHz (25-110 Watt) 0.85A
380-470 MHz (25-110 Watt) 0.85A
136-174 MHz (10-50 Watt) 3.2A
380-470 MHz (10-40 Watt) 3.2A
450-520 MHz (10-45 Watt) 3.2A
764-870 MHz (10-35 Watt) 3.2A
136-174 MHz (25-110 Watt) 3.2A
380-470 MHz (25-110 Watt) 3.2A
136-174 MHz (10-50 Watt) 13A (50W), 8A (15W)
380-470 MHz (10-40 Watt) 11A (40W), 8A (15W)
450-520 MHz (10-45 Watt) 11A (45W), 8A (15W)
764-870 MHz (10-35 Watt) 12A (35W), 8A (15W)
136-174 MHz (25-110 Watt) 20A (100W)
380-470 MHz (25-110 Watt) 24A (100W)
Specification sheet
ASTRO® XTL™ 5000

receiver

851-870 MHz and
450-520 MHz (Range 2)
Analog Sensitivity Pre-amp Standard Pre-Amp Standard
20 dB Quieting .30 µV 0.25 µV 0.40 µV 0.25 µV 0.40 µV
12 dB SINAD per EIA .25 µV 0.20 µV 0.30 µV 0.20 µV 0.30 µV
Digital Sensitivity
Intermodulation Distortion 80 dB 80 dB 85 dB 80 dB 85 dB
Spurious Response Rejection 90 dB 90 dB 90 dB 90 dB 90 dB
(External/Internal Speaker) 13 W (3.2 Ω ext. speaker) 13 W (3.2 Ω ext. speaker) 13 W (3.2 Ω ext. speaker)
(12.5 kHz/25 kHz)

Humidity 507.1 II 507.2 II 507.3 II 507.4 -
Salt Fog 509.1 - 509.2 - 509.3 - 509.4 -
R3-1-2029C
specification sheet
APX 7500 ™
Project 25 Multi-Band Mobile Radio
standard FEATURES
Available in 700/800 MHz and VHF bands Unified Call List
Up to 1250 Channels Expansion Slot Standard
Optional multi-band operation Meets applicable MIL-specs 810C, D, E, F and G
Trunking Standards supported: Ships standard IP54
• Clear or digital encrypted ASTRO® 25 Trunked Operation Utlizes Windows XP and Vista Customer Programming Software
• Capable of SmartZone®, SmartZone Omnilink, SmartNet® (CPS)
Analog MDC-1200 and Digital APCO P25 Conventional System • Supports USB Communications
Configurations • Built in FLASHport™ support
Narrow and wide bandwidth digital receiver Re-use of most XTL™ accessories
(6.25 kHz equivalent /12.5 kHz/25 kHz)
Embedded digital signaling (ASTRO and ASTRO 25) Optional Features
Integrated GPS capable Enhanced Encryption Software Options
Integrated Encryption Hardware Programming over Project 25 (POP25)
Seamless wideband scan Text Messaging
Intelligent lighting Over the Air Re-Key (OTAR)
Radio profiles 12 character RF ID asset tracking
The APX 7500 mobile exemplifies Motorola’s commitment to meet the voice and
data demands of today’s first responders in mission critical environments—to
enable, anywhere, anyplace, anytime connectivity. With integrated voice and
data capabilities, these radios offer improved communications between multiple
agencies, as well as neighboring communities, from everyday operations to
disaster response.
Motorola’s newest P25 mobile is multi-band (700/800 MHz and VHF),
communicates with current and future networks (FDMA and TDMA)
specification sheet
APX 7500
O3 Handheld Control Head features

4 lines: 2 lines text (14 characters), 1 line icons, 1 line soft menu keys
3 x 6 keypad with up to 24 programmable soft keys
Cellular style user interface and color display
O5 Control head features

Tri-color LCD display
4 lines: 2 lines text (14 characters), 1 line icons, 1 line soft menu keys
3 x 6 keypad microphone accessory with 3 programmable soft keys
5 programmable soft key buttons and 5 scroll-through menus with
up to 24 programmable soft keys
Multiple control head configuration to fully control a single radio
with up to 4 different wired locations
Motorcycle configuration available
O9 Integrated Control head available as a future release.

ASTRO Digital User
Group Addresses 4,096 network site addresses
Data Access Control Slotted CSMA: Utilizes infrastructure-sourced data status bits embedded in both voice and
data transmissions.
MOBILE APX7500
Dimensions Mid Power Radio Transceiver

2” x 7” x 8.6” (50.8 x 177.8 x 218.4 mm)
O5 Control Head
2” x 7” x 2.5” (50.8 x 180.3 x 63.5 mm)
Mid Power Radio Transceiver and O5 Control Head–Dash Mount
2” x 7” x 9.6” (50.8 x 180.3 x 243.8 mm)
Mid Power Radio Transceiver and Remote Mount
2.0” x 7” x 9.6” (50.8 x 180.3 x 243.8 mm)
High Power Radio Transceiver
2.9” x 11.5” x 8.8” (74 x 293 x 223 mm)
3.4” x 11.5” x 8.8” (87 x 293 x 223 mm)
7.0 lbs (3.17 kg)
High Power Radio Transceiver
14.2 lbs with trunnion (6.4 kg)
12 lbs without trunnion (5.4 kg)
specification sheet
APX 7500
TRANSMITTER – TYPICAL PERFORMANCE SPECIFICATIONS
700MHz 800MHz VHF

Frequency Range /Bandsplits 764-776 806-824 136-174
794-806 851-870
Channel Spacing 25/12.5 kHz 25/20/12.5 kHz 30/25/12.5 kHz
Rated RF Output Power Adj* 10-30 Watts 10-35 Watts 25-100 Watts
Frequency Stability*
(–30°C to +60°C; +25°C Ref.) ±0.00015 % ±0.00015 % ±0.0002 %
Modulation Limiting* ±5 kHz /±2.5 kHz ±5 kHz /±4 kHz (NPSPAC) /±2.5 kHz ±5 kHz /±2.5 kHz
12.5kHz Digital Channel ±2.8 kHz ±2.8 kHz ±2.8 kHz
Emissions* Conducted+ Radiated+ Conducted Radiated Conducted Radiated
–70/–85 dBc –20/–40 dBm –70 dBc –20 dBm –85 dBc –20 dBm
Audio Response* +1, –3 dB (EIA) +1, –3 dB (EIA) +1, –3 dB (EIA)
FM Hum & Noise
(25 & 20 KHz /12.5 KHz) 40/34 dB 40/34 dB 50/40 dB
Audio Distortion* 2% 2% 2%
RECEIVER – TYPICAL PERFORMANCE SPECIFICATIONS
700MHz 800MHz VHF

Frequency Range /Bandsplits 764-776 851-870 136-174 MHz
Channel Spacing 25/12.5 kHz 25/20/12.5 kHz 30/25/12.5 kHz
Audio Output Power at 3% distortion* 7.5 W or 13 W ++ 7.5 W or 13 W ++ 7.5 W or 13 W ++
(–30°C to +60°C; +25°C Ref.) ±0.00015 % ±0.00015 % ±0.0002 %
Pre-Amp Standard
Analog Sensitivity* 12 dB SINAD 0.25 µV 0.25 µV 0.2 µV 0.3 µV
Digital Sensitivity 1% BER 0.3 µV 0.3 µV 0.25 µV 0.4 µV
5% BER 0.25 µV 0.25 µV 0.2 µV 0.3 µV
Intermodulation 80 dB 80 dB 80 dB 85 dB
Spurious Rejection 90 dB 90 dB 90 dB
Audio Distortion at rated* 3.00% 3.00% 3.00%
Selectivity* 25 kHz /30 kHz 80 dB 80 dB 90 dB
12.5 kHz 65 dB 65 dB 70 dB
GPS specifications
Channels 12
Tracking Sensitivity –153 dBm
Accuracy** <10 meters (95%)
Cold Start <60 seconds (95%)
Hot Start <10 seconds (95%)
Mode of Operation Autonomous (Non-Assisted) GPS
POWER AND BATTERY DRAIN

764-870 MHz
25-100 Watt (136-174 MHz)
Operation 13.8V DC ±20% Negative Ground
Standby at 13.8V 764-870 MHz (10-35 Watt) 0.85A
136-174 MHz (25-100 Watt) 0.85A
Receive at Rate Audio at 13.8V 764-870 MHz (10-35 Watt) 3.2A
136-174 MHz (25-100 Watt) 3.2A
Transmit Current (A) at Rated Power (W) 764-870 MHz (10-35 Watt) 12A (35W), 8A (15W)
136-174 MHz (25-100 Watt) 20A (100W)
specification sheet
APX 7500
mobile MILITARY STANDARDS 810 C, D, E, F, & G
MIL-STD-810C MIL-STD-810D MIL-STD-810E MIL-STD-810F MIL-STD-810G

Method Proc./Cat. Method Proc./Cat. Method Proc./Cat. Method Proc./Cat. Method Proc./Cat.
Low Pressure 500.1 I 500.2 II 500.3 II 500.4 II 500.5 II
High Temperature 501.1 I,II 501.2 I/A1,II/A1 501.3 I/A1,II/A1 501.4 I/Hot, II/Hot 501.5 I-A1, II
Low Temperature 502.1 I 502.2 I/C3, II/C1 502.3 I/C3, II/C1 502.4 I/C3, II/C1 502.5 I-C3, II
Temperature Shock 503.1 – 503.2 I/A1C3 503.3 I/A1C3 503.4 I 503.5 I-C
Solar Radiation 505.1 II 505.2 I 505.3 I 505.4 I 505.5 I-A1
Rain 506.1 I,II 506.2 I,II 506.3 I,II 506.4 I,III 506.5 I, III
Humidity 507.1 II 507.2 II 507.3 II 507.4 – 507.5 II - Aggravated
Salt Fog 509.1 – 509.2 – 509.3 – 509.4 – 509.5 –
Blowing Dust 510.1 I 510.2 I,II 510.3 I,II 510.4 I,II 510.5 I, II
Vibration 514.1 VIII/F, Curve-W 514.3 I/10, II/3 514.4 I/10, II/3 514.5 I/24 514.6 I-cat.24
Shock 516.1 I,II 516.3 I,IV 516.4 I,IV 516.5 I,IV 516.6 I, V, VI
ENCRYPTION ENVIRONMENTAL SPECIFICATIONS
Supported Encryption Algorithms ADP, AES, DES, DES-XL, DES-OFB, DVP-XL Operating Temperature –30°C / +60°C
Encryption Algorithm Capacity 7 Storage Temperature –40°C / +85°C
Encryption Keys per Radio Module capable of storing 1024 keys. Humidity Per MIL-STD
Programmable for 48 Common Key ESD IEC 801-2 KV
Reference (CKR) or 16 Physical Identifier (PID)
Water & Dust Intrusion IP54, MIL-STD
Encryption Frame Re-sync Interval P25 CAI 300 mSec
Encryption Keying Key Loader
Synchronization XL – Counter Addressing FCC Type Acceptance ID
OFB – Output Feedback
Vector Generator National Institute of Standards and Band Output Power Transmitter Number
Technology (NIST) approved random 136-174 MHz 25-100 Watt AZ492FT3821
number generator 764-870 MHz 10-35 Watt AZ492FT5858
Encryption Type Digital
Key Storage Tamper protected volatile or non-volatile
memory
Standards FIPS 140-2
FIPS 197
* Measured in the analog mode per TIA /EIA 603 under nominal conditions
** Accuracy specs are for long-term tracking (95th percentile values >5 satellites visible at a nominal

–130 dBm signal strength)

+
Specs includes performance for the non-GNSS/GNSS bands
++
Output power in to 8 and 3.2 Ohm external speakers respectively
Specifications subject to change without notice. All specifications shown are typical.
Radio meets applicable regulatory requirements.
R3-1-2037A
SPECIFICATION SHEET
PRELIMINARY
APX™ 6500
Project 25 MOBILE Radio
We’ve put exceptional flexibility into an Flexible Platform

advanced mission critical mobile radio that’s Interchangeable control heads (O3 and
easy to operate and intuitive to use. The O5) and transceivers (mid power and high
APX 6500 P25 mobile allows users to choose power). Dual control head support offered
from 2 control heads, mid and high power on the O5
models and multiple installation configurations 3 hand held control head – this unique,
O
in an easy to install design. Innovative safety palm-sized device is easy to read and
operate, with its large color display and
features such as GPS location tracking, keypad
intelligent lighting and one-touch controls help
5 control head – gives you a rugged
O
to keep first responders safer than ever before. display, easy-to-use controls and five
programmable soft buttons for even more
Focus on the task not the technology, with the radio flexibility
hardworking mission critical mobile that turns
mission critical into mission complete. Easy to install and
effortless to use
M id-power model fits into any existing
XTL footprint, so you can reuse mounting
holes and cables
H igh-power model trunnion design lets
you remove the radio without removing
the cables
1 2 character RF ID label helps you track
information without uninstalling your
radio
Cutting-edge technology and

advanceD features
P roject 25 Phase 2 technology provides
twice the voice capacity
Integrated GPS lets you locate and track
an individual or vehicle
A dvanced features like intelligent lighting,
radio profiles and text messaging improve
communication and coordination
APX ™ 6500 Specifications
Features and Benefits:

Available in 700/800 frequency bands Meets applicable MIL-STD 810C, D, E, F and G
Up to 870 Channels Ships standard IP54
Trunking Standards supported: Utlizes Windows XP, Vista and Windows 7
Clear or digital encrypted Trunked Operation Customer Programming Software (CPS)
Capable of SmartZone®, SmartZone Omnilink, Supports USB Communications
SmartNet® Built in FLASHport™ support
Analog MDC-1200 and Digital APCO P25 Conventional Re-use of most XTL™ accessories, plus new
System IMPRES accessories
Configurations
Narrow and wide bandwidth digital receiver OPTIONAL FEATURES:
(6.25kHz/12.5kHz/25kHz) Enhanced Encryption Software Options
Embedded digital signaling (ASTRO and ASTRO 25) Programming over Project 25 (POP25)
Integrated GPS capable Text Messaging
Integrated Encryption Hardware Over the Air Re-Key (OTAR)
Intelligent lighting 12 character RF ID asset tracking
Radio profiles Tactical OTAR
Unified Call List
Transmitter - Typical performance specifications

700 MHz 800 MHz
764-776 806-825
Frequency Range/Bandsplits
794-806 851-870
Channel Spacing 25/12.5 kHz 25/20/12.5 kHz
Maximum Frequency Separation Full Bandsplit Full Bandsplit
Rated RF Output Power Adj* 10-30 Watts Max 10-30 Watts Max
±0.00015 % ±0.00015 %
(–30°C to +60°C; +25°C Ref.)
Modulation Limiting* ±5 kHz /±2.5 kHz ±5 kHz /±4 kHz (NPSPAC) /±2.5 kHz
±2.8 kHz ±2.8 kHz
12.5kHz Digital Channel
Conducted+ –70/–85 dBc –70 dBc
Emissions*
Radiated+ –20/–40 dBm –20 dBm
Audio Response* +1, –3 dB (EIA) +1, –3 dB (EIA)
FM Hum & Noise (25 & 20 KHz /12.5 KHz) 40/34 dB 40/34 dB
Audio Distortion* 2% 2%
dimensions
Inches Millimeters
Mid Power Radio Transceiver 2 x 7 x 8.6 50.8 x 177.8 x 218.4
O5 Control Head 2 x 7 x 2.5 50.8 x 180.3 x 63.5
Mid Power Radio Transceiver and O5 Control Head–Dash Mount 2 x 7 x 9.6 50.8 x 180.3 x 243.8
Mid Power Radio Transceiver and Remote Mount 2.0 x 7 x 9.6 50.8 x 180.3 x 243.8
High Power Radio Transceiver 2.9 x 11.5 x 8.8 74 x 293 x 223
High Power Radio Transceiver with Handle 3.4 x 11.5 x 8.8 87 x 293 x 223
Mid Power Radio Transceiver and Control Head Weight 7.0 lbs 3.17 kg
With Trunnion 14.2 lbs 6.4 kg
High Power Radio Transceiver Weight
Without Trunnion 12 lbs 5.4 kg
O3 Hand Held Control Head features O5 Control Head features

4 lines: 2 lines text (14 characters), 1 line icons, 1 line T ri-color LCD display
soft menu keys 4 lines: 2 lines text (14 characters),
3 x 6 keypad with up to 24 programmable soft keys 1 line icons, 1 line soft menu keys
Cellular style user interface and color display 3 x 6 keypad microphone accessory with
3 programmable soft keys
5 programmable soft key buttons and 5
scroll-through menus with
Up to 24 programmable soft keys
D ual control head configuration to fully
control a single radio from 2 different
wired locations
receiver - Typical performance specifications

700 MHz 800 MHz
Frequency Range/Bandsplits 764-776 851-870
Channel Spacing 25/12.5 kHz 25/20/12.5 kHz
Maximum Frequency Separation Full Bandsplit Full Bandsplit
Audio Output Power at 3% distortion* 7.5W or 13W++ 7.5W or 13W++
±0.00015 % ±0.00015 %
(–30°C to +60°C; +25°C Ref.)
Analog Sensitivity* 12 db SINAD 0.25 μV 0.25 μV
Digital Sensitivity 1% BER 0.3 μV 0.3 μV
5% BER 0.25 μV 0.25 μV
Intermodulation 80 dB 80 dB
Spurious Rejection 90 dB 90 dB
Audio Distortion at rated* 3.00% 3.00%
Selectivity 25 kHz/30 kHz 80 dB 80 dB
12.5 kHz 65 dB 65 dB
Signaling (astro mode)

Signaling Rate 9.6 kbps
ASTRO® Digital User Group Addresses 4,096 network site addresses
Project 25 – CAI Digital User Group Addresses 65,000 Conventional / 4,094 Trunking
Data Access Control Slotted CSMA: Utilizes infrastructure-sourced data status bits embedded in both voice and data transmissions.
power and battery drain GPS SPEcifications

Model Type 764-870 MHz Channels 12
Minimum RF Power Output 10-35 Watt (764-870 MHz) Tracking Sensitivity –153 dBm
Operation 13.8V DC ±20% Negative Ground Accuracy** <10 meters (95%)
Standby at 13.8V 764-870 MHz (10-35 Watt) 0.85A Cold Start <60 seconds (95%)
Receive at Rate Audio at 13.8V 764-870 MHz (10-35 Watt) 3.2A Hot Start <10 seconds (95%)
Transmit Current (A) at 764-870 MHz (10-35 Watt) 12A (35W), 8A (15W) Mode of Operation Autonomous (Non-Assisted) GPS
Rated Power (W)
PORTABLE MILITARY STANDARDS 810 C, D, E , F & G

MIL-STD 810C MIL-STD 810D MIL-STD 810E MIL-STD 810F MIL-STD 810G
High Temperature 501.1 I, II 501.2 I/A1, II/A1 501.3 I/A1, II/A1 501.4 I/Hot, II/Hot 501.5 I-A1, II
Low Temperature 502.1 I 502.2 I/C3, II/C1 502.3 I/C3, II/C1 502.4 I/C3, II/C1 502.5 I-C3, II
Temperature Shock 503.1 – 503.2 I/A1C3 503.3 I/A1C3 503.4 I 503.5 I-C
Solar Radiation 505.1 II 505.2 I 505.3 I 505.4 I 505.5 I-A1
Rain 506.1 I, II 506.2 I, II 506.3 I, II 506.4 I, III 506.5 I, III
Humidity 507.1 II 507.2 II 507.3 II 507.4 – 507.5 II-Aggravated
Salt Fog 509.1 – 509.2 – 509.3 – 509.4 – 509.5 –
Blowing Dust 510.1 I 510.2 I, II 510.3 I, II 510.4 I, II 510.5 I, II
Vibration 514.1w VIII/F, Curve-W 514.3 I/10, II/3 514.4 I/10, II/3 514.5 I/24 514.6 I-cat.24
Shock 516.2 I, III 516.3 I, IV 516.4 I, IV 516.5 I, IV 516.6 I, V, VI
encryption environmental SPEcifications

Supported Encryption Algorithms ADP, AES, DES, DES-XL, DES-OFB, DVP-XL Operating Temperature -30ºC / +60ºC
Encryption Algorithm Capacity 1 Storage Temperature -40ºC / +85ºC
Encryption Keys per Radio Module capable of storing 1024 keys. Humidity Per MIL-STD
Programmable for 64 Common Key Reference ESD IEC 801-2 KV
(CKR) or 16 Physical Identifier (PID)
Water and Dust Intrusion IP54, MIL-STD
FcC Type Acceptance ID
XL – Counter Addressing Transmitter
Synchronization Band Output Power
OFB – Output Feedback Number
National Institute of Standards and Technology 764-870 MHz 10-35 Watt AZ492FT5858
Vector Generator
(NIST) approved random number generator
Encryption Type Digital * Measured in the analog mode per TIA/EIA 603 under nominal conditions
** Accuracy specs are for long-term tracking
Key Storage Tamper protected volatile or non-volatile memory (95th percentile values >5 satellites visible at a nominal –130 dBm signal strength)
+ Specs includes performance for the non-GNSS/GNSS bands
++ Output power in to 8 and 3.2 Ohm external speakers respectively
FIPS 140-2
Standards Specifications subject to change without notice. All specifications shown are typical.
FIPS 197 Radio meets applicable regulatory requirements.
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com
MOTOROLA and the stylized M Logo are registered in the U.S. Patent and Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2010 R3-1-2047
Specification sheet
ASTRO XTS 2500 and ® ®
XTS 2500I
®
Digital Portable Radios
MODEL I: MODEL I.5: MODEL II: MODEL III:

• PTT button Same as XTS Model I features Same as XTS Model I features Same as XTS Model I features
• On/Off volume knob plus the following: plus the following: plus the following:
• Programmable orange • Large Bitmap Display • 870 channels • 870 channels
emergency button – 2 lines of icons • Dial from pre-stored lists • Dial from pre-stored lists or
• 16-position top mounted – 2 lines of text with • Programmable soft keys for direct entry
rotary knob 12 characters per line easy access to radio menu • Programmable soft keys for
• 3-position concentric switch – Status icons including • Backlit Keypad easy access to radio menu
• Programmable monitor battery and received signal – 3 soft keys • Backlit Keypad
button strength indicator – 3 navigation keys – 3 soft keys
• 2 programmable side buttons • 96 Channels • Large Bitmap Display – 3 navigation keys
• Transmit LED indicator – 2 lines of icons – 4 x 3 alphanumeric keypad
• No keypad – 4 lines of text with • Large Bitmap Display
• No display 12 characters per line – 2 lines of icons
• Up to 48 channels – Status icons including – 4 lines of text with
battery and received signal 12 characters per line
strength indicator – Status icons including
battery and received signal
strength indicator
When lives are at stake, a rapid, coordinated response is imperative. Motorola’s

XTS® 2500 high performance digital radio lets you respond immediately and
interoperate effectively helping turn Mission Critical into mission complete. Our IP
enabled, digital APCO Project 25 compliant portable delivers sophisticated features
and advanced technology in a light, compact design. Whether en route or on site,
this robust radio assures crisp, continuous, high-quality communication and is an
affordable way to migrate seamlessly to the APCO Project 25 digital standard.
Specification sheet
ASTRO® XTS® 2500 and XTS® 2500I

FEATURES AND BENEFITS

• Available in 700/800 MHz, VHF, UHF R1, UHF R2 and • Convenience Features
900 MHz* bands – Time / Date
• Trunking standards supported – Caller ID
– APCO Project 16 (3600 control channel) and • Utilizes Windows-Based Customer Programming Software (CPS)
– APCO Project 25 (9600 control channel) – Supports USB and RS-232 communications
• System configurations – Built in FLASHport support
– ASTRO® Analog and Digital Trunking with Mutual Aid and • Meets Mil Specs 810 C, D, E and F
– ASTRO®25 Digital Trunking with Mutual Aid • Compatible with most MTS and XTS accessories
• Narrow and wide bandwidth digital receiver • Available with an Immersible Housing Option
(12.5 kHz, 20 kHz, 25 kHz) • Available with Secure Hardware Encryption
• Embedded digital signaling (ASTRO & ASTRO 25)
• Enhanced Audio Features
– High quality, error corrected digital voice
– Noise Reduction Software
– Audio Gain Control
700/800 MHz UHF R1 VHF UHF R2

Frequency Range 700 MHz: 764-776, 380-470 MHz 136-174 MHz 450-520 MHz
794-806
800 MHz: 806-870
Channel Spacing 12.5 / 20 / 25 kHz 12.5/25 kHz 12.5/25 kHz 12.5/25 KHz
Maximum Frequency
Separation Full Bandsplit Full Bandsplit Full Bandsplit Full Bandsplit
Rated RF Output Power Adj** 764-806 MHz: 1 to 3 W 1 to 5 W 1 to 5 W 1 to 5 W
806-870 MHz: 1 to 3 W
Frequency Stability**
(–30°C to +60°C; +25°C Ref.) ±0.00015% ±0.0002% ±0.00025% ±0.0002%
Modulation Limiting**:
25 kHz channel ±5.0 kHz ±5.0 kHz ±5.0 kHz ±5.0 kHz
NPSPAC channel ±4.0 kHz N/A N/A N/A
12.5 kHz channel ±2.5 kHz ±2.5 kHz ±2.5 kHz ±2.5 kHz
Emissions**
(Conducted & Radiated) –75 dBc –70 dBc –73 dBc (<1 GHz) –70 dBc
Audio Response**
from 300 to 3000 Hz) +1, –3 dB +1, –3 dB +1, –3 dB +1, –3 dB
FM Hum & Noise Radio**
25 kHz –43 dB –45 dB –46 dB –45 dB
12.5 kHz –40 dB –40 dB –42 dB –40 dB
Audio Distortion** 2.0% 2.0% 1.0% 2.0%
VOICE CODER
Dual Level Level 1: Extrapolates and replaces 20 mSec voice frames that exceed the error
correction algorithm tolerance.
Level 2: Progressive muting of 20 mSec voice frames that are too severely damaged
for Level 1 replacement.
* Separate 900 MHz specification sheets available.

** Measured in the analog mode per TIA / EIA 603
*** Measured in digital mode per TIA/EIA IS 102.CAAA

Specification sheet


Frequency Range 700 MHz: 764-776 380-470 MHz 136-174 MHz 450-520 MHz
Note: Radio covers entire 700 MHz 800 MHz: 851-870
and 800 MHz frequency ranges.
Channel Spacing 12.5 / 20 / 25 kHz 12.5/25 kHz 12.5 / 25 kHz 12.5/25 KHz
Audio Output Power at Rated** 500 mW 500 mW 500 mW 500 mW
Frequency Stability**
(–30°C to +60°C; 25°C Ref.) ±0.00015% ±0.0002% ±0.00025% ±0.0002%
Analog Sensitivity**
12 dB SINAD .25 µV .25 µV .25 µV .25 µV
Digital Sensitivity***
1% BER .40 µV .35 µV .25 µV .35 µV
5% BER .25 µV .25 µV .20 µV .25 µV
Selectivity**
25 kHz chnl –72 dB –73 dB –80 dB –73 dB
12.5 kHz chnl –63 dB –63 dB –63 dB –63 dB
Intermodulation** –75 dB –73 dB –78 dB –75 dB
Spurious Rejection** –75 dB –75 dB –80 dB –75 dB
FM Hum and Noise**
25 kHz –47 dB –47 dB –52 dB –50 dB
12.5 kHz –40 dB –40 dB –40 dB –47 dB
Audio Distortion** 2.5% 2.0% 1.0% 2.0%
RADIO MODELS
Channel 700/800 MHz Band UHF R1 VHF UHF R2

Display Keypad Capacity (764-870 MHz) (380-470 MHz) (136-174 MHz) (450-520 MHz)
Model I N/A N/A 48 H46UCC9PW5BN H46QDC9PW5BN H46KDC9PW5BN H46SDC9PW5BN
Model I.5 2 lines of icons
4 lines
12 characters N/A 96 H46UCD9PW5BN H46QDD9PW5BN H46KDD9PW5BN H46SDD9PW5BN
per line LCD
Model II 2 lines of icons
4 lines
12 characters 3x2 870 H46UCF9PW6BN H46QDF9PW6BN H46KDF9PW6BN H46SDF9PW6BN
per line LCD
Model III 2 lines of icons
4 lines
12 characters 3x6 870 H46UCH9PW7BN H46QDH9PW7BN H46KDH9PW7BN H46SDH9PW7BN
per line LCD
FCC Designation AZ489FT5804 UHF: AZ489FT4865 VHF: AZ489FT3807 AZ489FT4866
FCC Emissions Designators 11K0F3E, 16K0F3E, 8K10F1E, 8K10F1D, 20K0F1E
Power Supply One rechargeable nickel-cadmium, nickel-metal hydride, or lithium ion battery
Dimensions without battery (HxWxL) 6.00” x 2.30” x 1.50”
Weight without battery 11.0 oz
BATTERIES FOR ASTRO DIGITAL XTS 2500
Battery Type Dimensions (HxWxD) Weight Battery Part Numbers mAH Duty Cycle
NiCD 4.86” x 2.37” x .968” 8.85 oz NTN9815 1525 5-5-90 / 8 hr
NiCD FM 4.86” x 2.37” x .968” 8.85 oz NTN9816 1525 5-5-90 / 8 hr
IMPRES™ NiMH 4.86” x 2.37” x .968” 9.63 oz NTN9858 2100 5-5-90 / 10 hr
IMPRES NiMH FM 4.86” x 2.37” x .968” 9.63 oz NTN9857 2000 5-5-90 / 10 hr
IMPRES Immersible NiMH FM 4.86” x 2.37” x .968” 10.16 oz NNTN6263 2000 5-5-90 / 10 hr
IMPRES High Capacity Immersible LiIon 4.86” x 2.37” x .968” 6.70 oz NNTN7335 2700 5-5-90 / 13 hr
Specification sheet

PORTABLE MILITARY STANDARDS 810 C, D, E & F

High temperature 501.1 I, II 501.2 I/A1, II/A1 501.3 I/A1, II/A1 501.4 I/Hot, II/Hot
Low Temperature 502.1 I 502.2 I/C3, II/C1 502.3 I/C3, II/C1 502.4 I/C3, II/C1
Temperature Shock 503.1 I* 503.2 I/A1C3 503.3 I/A1C3 503.4 I
Rain 506.1 I, II 506.2 I, II 506.3 I, II 506.4 I, III
Humidity 507.1 II 507.2 II 507.3 II 507.4 I*
Salt Fog 509.1 I* 509.2 I* 509.3 I* 509.4 I*
Vibration 514.2 VIII/F, Curve-W 514.3 I/10, II/3 514.4 I/10, II/3 514.5 I/24
Shock 516.2 I, II 516.3 I, IV 516.4 I/IV 516.5 I, IV
* Military Standards specify a single procedure for this test.
Supported Encryption Operating Temperature –30°C / +60°C

Algorithms ADP, AES, DES, DES-XL and Storage Temperature –40°C / +85°C
DES-OFB, DVP-XL
Humidity Per MIL-STD
Encryption Algorithm Capacity 1
ESD IEC 801-2KV
Encryption Keys per Radio odule capable of storing 1024 keys.
M
Water & Dust Intrusion IP54, MIL-STD, IP67**
Programmable for 48 common Key Reference
Encryption Frame Re-sync Interval P25 CAI 360 mSec IMMERSIBLE OPTION SPECIFICATIONS
Encryption Keying Key Loader MIL-STD-810, C, D, E, F

Synchronization CFB – Cipher Feedback IP67 rating
XL - Counter Addressing ** For XTS2500I (immersible) models only.
OFB - Output Feedback
Vector Generator National Institute of Standards and Technology
Encryption Type Digital and 12 k-bit Analog Conventional
Key Storage Tamper protected volatile or non volatile memory
Standards • FIPS 46-2
• FIPS 140-2
• FIPS 197
R3-4-2003K
Specification sheet
XTS 1500 ®
Digital Portable Radio
XTS 1500 Portable Radios Feature:

Available Frequency:
• 136-174 MHz (5W)
• 380-470 MHz (5W)
• 450-520 MHz (5W)
• 764-870 MHz (3W)
Supports APCO Project 16
(3600 control channel) and
APCO Project 25 (9600 control
channel)
Works with ASTRO® Analog and
Digital Trunking with Mutual Aid
or ASTRO 25 Digital Trunking
with Mutual Aid
Meets Military Standards 810,
C, D, E and F
Utilizes Customer Programming
Software and supports USB
and RS-232
Compatible with most
XTS 3000, XTS 3500, XTS 2500,
HT 1000, JT 1000 and MTS 2000
portable radio accessories
Supports enhanced audio
features: noise reduction
software, Hear Clear and audio
gain control
Model 1 Model 1.5
Affordability in action. Durability to depend on. Simplicity that succeeds.
Motorola’s XTS 1500 portable radio is the cost-effective, convenient, compact solution for public
works and public utilities. This high-quality APCO Project 25 radio features two-way functionality
in a durable, dependable unit that is very easy to use.
Both Model 1 and Model 1.5 (display version) are available in 700/800 MHz, VHF, UHF R1 and UHF
R2 bands, and supports APCO Project 16 or Project 25 operation. Use the analog functionality on
the XTS 1500 or migrate to wide-area Project 25 operation.
For true simplicity, affordability and reliability make the right call with the XTS 1500 digital radio
from Motorola.
Specification sheet
XTS® 1500
TRANSMITTER TYPICAL PERFORMANCE SPECIFICATIONS

794-806
800 MHz: 806-870
Channel Spacing 12.5 / 20 / 25 kHz 12.5 / 25 kHz 12.5 / 25 kHz 12.5 / 25 kHz
Rated RF Output Power Adj* 764-806 MHz: 1 to 3 W 1 to 5 W 1 to 5 W 1 to 5 W
806-870 MHz: 1 to 3 W
(–30°C to +60°C; +25°C Ref.) 0.00015% 0.0002% 0.00025% 0.0002%
Modulation Limiting*
25 kHz channel 5.0 kHz 5.0 kHz 5.0 kHz 5.0 kHz
NPSPAC channel 4.0 kHz N/A N/A N/A
12.5 kHz channel 2.5 kHz 2.5 kHz 2.5 kHz 2.5 kHz
Emissions* (Conducted & Radiated) –75 dBc –70 dBc –73 dBc (<1 GHz) –70 dBc
Audio Response* (6 dB/Octave
Pre-emphasis from 300 to 3000 Hz) +1, –3 dB +1, –3 dB +1, –3 dB +1, –3 dB
FM Hum & Noise Ratio*
25 kHz –43 dB –45 dB –46 dB –45 dB
12.5 kHz –40 dB –40 dB –42 dB –40 dB
Audio Distortion* 2.0% 2.0% 1.0% 2.0%
RECEIVER TYPICAL PERFORMANCE SPECIFICATIONS

Note: Radio covers entire 700 MHz 800MHz: 851-870
and 800 MHz frequency ranges
Channel Spacing 12.5 / 20 / 25 kHz 12.5 / 25 kHz 12.5 / 25 kHz 12.5 / 25 kHz
Audio Output Power at Rated* 500 mW 500 mW 500 mW 500 mW
(–30°C to +60°C; +25°C Ref.) 0.00015% 0.0002% 0.00025% 0.0002%
Analog Sensitivity*
12 dB SINAD .25 µV .25 µV .25 µV .25 µV
Digital Sensitivity**
1% BER .40 µV .35 µV .25 µV .35 µV
5 % BER .25 µV .25 µV .20 µV .25 µV
Selectivity*
25 kHz channel –72 dB –73 dB –80 dB –73 dB
12.5 kHz channel –63 dB –63 dB –63 dB –63 dB
Intermodulation* –75 dB –73 dB –78 dB –75 dB
Spurious Rejection* –75 dB –75 dB –80 dB –75 dB
FM Hum & Noise Ratio*
25 kHz –47 dB –47 dB –52 dB –50 dB
12.5 kHz –40 dB –40 dB –40 dB –47 dB
Audio Distortion* 2.5% 2.0% 1.0% 2.0%
* Measured in the analog mode per TIA / EIA 603

** Measured in digital mode per TIA / EIA IS 102.CAAA
Specification sheet
XTS® 1500
RADIO MODELS
Channel 700/800MHz Band UHF R1 VHF UHF R2

Display Keypad Capacity (764-870 MHz) (380-470 MHz) (136-174 MHz) (450-520 MHz)
Model 1 None None 48 H66UCC9PW5_N H66QDC9PW5_N H66KDC9PW5_N H66SDC9PW5_N
Model 1.5 Yes None 96 H66UCD9PW5_N H66QDD9PW5_N H66KDD9PW5_N H66SDD9PW5_N
FCC Designation AZ489FT5804 AZ489FT4865 AZ489FT3807 AZ489FT4866
FCC Emissions
Designators 11K0F3E, 16K0F3E, 8K10F1E, 8K10F1D
Power Supply One rechargeable nickel-cadmium, or nickel-metal hydride
Dimensions without
battery (HxWxL) 6.00” x 2.30” x 1.50”
Weight
without battery 11.0 oz
Battery Type Dimension (HxWxD) Weight Battery Part Numbers mAH Duty Cycle
NiCD 4.86” x 2.37” x .968” 8.85 oz NTN9815 1525 5-5-90 / 8 hr
NiCD FM 4.86” x 2.37” x .968” 8.85 oz NTN9816 1525 5-5-90 / 8 hr
IMPRES™ NiMH 4.86” x 2.37” x .968” 9.63 oz NTN9858 2100 5 -5-90 / 10 hr
IMPRES NiMH FM 4.86” x 2.37” x .968” 9.63 oz NTN9857 2000 5-5-90 / 10 hr
MIL-STD-810C MIL-STD-810D MIL-STD-810E MIL-STD-810F

Temperature Shock 503.1 – 503.2 I/A1C3 503.3 I/A1C3 503.4 I
Humidity 507.1 II 507.2 II 507.3 II 507.4 –
Salt Fog 509.1 – 509.2 – 509.3 – 509.4 –
Shock 516.2 I, II 516.3 I, IV 516.4 I/IV 516.5 I, IV
Operating Temperature –30°C / +60°C

Storage Temperature –40°C / +85°C
ESD IEC 801-2 KV
Water & Dust Intrusion IP54, MIL-STD

R3-4-2007I
Specification sheet
ASTRO® XTS® 5000

MODEL I: MODEL II: MODEL III:

Large PTT button Same as XTS Model I features Same as XTS Model I features
Angled On/Off plus the following: plus the following:
volume knob 1000 channels 1000 channels
Orange emergency button Dial from pre-stored lists Dial from pre-stored lists or
Illuminated 16 position top Programmable soft keys for free-form entry
mounted rotary knob easy access to radio menu Programmable soft keys for
2 position concentric switch Backlit Keypad easy access to radio menu
3 position toggle switch • 3 soft keys Backlit Keypad

• 3 navigation keys • 3 soft keys
3 programmable side buttons • 3 navigation keys
Full Bitmap Display
Transmit LED indicator • 2 lines of icons • 4 x 3 keypad
No keypad / No display • 4 lines of text with Full Bitmap Display
Up to 48 channels 12 characters per line • 2 lines of icons
• Status icons including battery • 4 lines of text with
and power indicator 12 characters per line
• Status icons including battery
and power indicator
The XTS 5000 Project 25 Digital Radio is the toughest and most interoperable
radio Motorola makes. It assures seamless, high quality communication in a
robust design that stands up to the most demanding environments.
Motorola’s IP-enabled portable two-way performer offers a full array of

sophisticated features and progressive technology. Designed specifically for law
enforcement, firefighters, emergency medical, military and federal agencies, the
XTS 5000 digital portable radio is the preferred tool of life-saving professionals.
Specification sheet
ASTRO® XTS® 5000

FEATURES AND BENEFITS

GPS enabled using GPS Radio Speaker Microphone Ruggedized housing option available in traditional black or public safety yellow
Available in the 700/800 MHz, VHF, UHF R1 and R2 bands Enhanced encryption capability (optional)
Trunking standards supported: clear or digital encrypted APCO P16 and APCO P25 Utilizes Windows®-based Customer Programming
Capable of SmartZone , SmartZone Omnilink, SmartNet , and Conventional System
® ®
Software (CPS)
Configurations and ASTRO®25 Trunked Operation • Supports USB and RS-232 communications
Narrow and wide bandwidth digital receiver (12.5 kHz / 25 kHz) • Built in FLASHport™ support
Embedded digital signaling (ASTRO & ASTRO 25) Meets Applicable Mil Specs 810C, D, E and F
Enhanced audio features XTS 5000 VHF is now approved for FCC Rule Part 80, Maritime Services
• High quality, error corrected digital voice Compatible with most MTS and XTS accessories
• Noise Shield™ Enhanced Noise Reduction Software Interchangeable display labels
• Audio Gain Control
Convenience Features
• Time / Date
• Digital Caller ID
700/800 MHz VHF UHF R1 UHF R2

Frequency Range/Bandsplits 700 MHz: 764-777, 794-806, 136-174 MHz 380-470 MHz 450-512 MHz
800 MHz: 806-824, 851-870
Channel Spacing 12.5 / 20 / 25 kHz 12.5 / 25 kHz 12.5 / 25 kHz 12.5 / 25 KHz
Maximum Frequency
Rated RF Output Power Adj* 764-806 MHz: 1 to 3 W 1 to 6 W 1 to 5 W 1 to 5 W
806-870 MHz: 1 to 3 W
(–30°C to +60°C; +25°C Ref.) ±0.00015% ±0.00020% ±0.00020% ±0.00020%
Modulation Limiting*:
25 kHz channel ±5.0 kHz ±5.0 kHz ±5.0 kHz ±5.0 kHz
NPSPAC channel ±4.0 kHz N/A N/A N/A
12.5 kHz channel ±2.5 kHz ±2.5 kHz ±2.5 kHz ±2.5 kHz
Emissions*
(Conducted & Radiated) –75 dBc –75 dBc –70 dBc –75 dBc
Audio Response*
from 300 to 3000 Hz) +1, –3 dB +1, –3 dB +1, –3 dB +1, –3 dB
FM Hum & Noise Radio*
25 kHz –45 dB –48 dB –45 dB –45 dB
12.5 kHz –40 dB –42 dB –40 dB –40 dB
Audio Distortion* 1.50% 1% 1.50% 1.50%
VOICE CODER
Voice Coding Method IMBE (CAI) Improved Multi Band Excitation (IMBE) (4.4 Kbps IMBE, 2.8 Kbs Error Correction Coding 2.4 Kbps Embedded Signaling)
Dual Level Level 1: Extrapolates and replaces 20 mSec voice frames that exceed the error correction algorithm tolerance.
Level 2: Progressive muting of 20 mSec voice frames that are too severely damaged for Level 1 replacement.
* Measured in the analog mode per TIA / EIA 603 under nominal conditions
**Measured in digital mode per TIA/EIA IS 102.CAAA under nominal conditions
Specification sheet
ASTRO® XTS® 5000

700/800 MHz VH1 UHF R1 UHF R2

Frequency Range/Bandsplits 700 MHz: 764-777 136-174 MHz 380-470 MHz 450-512 MHz
800 MHz: 851-870
Channel Spacing 12.5 / 25 kHz 12.5 / 25 kHz 12.5 / 25 kHz 12.5 / 25 KHz
Maximum Frequency
Audio Output Power at Rated* 500 mW 500 mW 500 mW 500 mW
(–30°C to +60°C; 25°C Ref.) ±0.00015% ±0.00020% ±0.00020% ±0.00020%
Analog Sensitivity* 12 dB SINAD .25 µV .20 µV .25 µV .20 µV
Digital Sensitivity** 1% BER .40 µV .25 µV .40 µV .25 µV
5% BER .25 µV .20 µV .25 µV .20 µV
Selectivity* 25 kHz channel –72 dB –80 dB –78 dB –79 dB
12.5 kHz channel –63 dB –63 dB –63 dB –65 dB
Intermodulation* –75 dB –78 dB –75 dB –77 dB
Spurious Rejection* –75 dB –80 dB –80 dB –85 dB
FM Hum and Noise* 25 kHz –48 dB –56 dB –54 dB –53 dB
12.5 kHz –40 dB –50 dB –45 dB –45 dB
Audio Distortion* 1.5% 1% 1% 1%
RADIO MODELS
Channel FLASHport 700/800 MHz Band VHF UHF R1 Band UHF R2 Band
Display Keypad Capacity Memory (764-870 MHz) (136-174 MHz) (380-470 MHz) (450-520 MHz)
Model I none none 16/48 8MB H18UCC9PW5_N H18KEC9PW5_N H18QDC9PW5_N H18SDC9PW5_N
Model II 2 lines of icons
4 lines
12 characters 3x2 1000 8MB H18UCF9PW6_N H18KEF9PW6_N H18QDF9PW6_N H18SDF9PW6_N
per line LCD
Model III 2 lines of icons
4 lines
12 characters 3x6 1000 8MB H18UCH9PW7_N H18KEH9PW7_N H18QDH9PW7_N H18SDH9PW7_N
per line LCD
FCC Designation AZ489FT5806 AZ489FT3804 AZ489FT4855 AZ489FT4864
FCC Emissions
Designators 8K10F1E, 20K0F1E, 16K0F3E, 8K10F1D, 11K0F3E
Power Supply 700/800 MHz: One rechargeable nickel-cadmium, or one optional nickel-metal hydride of lithium ion battery
VHF/UHF R1&2: One rechargeable nickel-metal hydride, or one optional nickel cadmium or lithium ion battery
Dimensions without
battery (HxWxL) 6.58” x 2.44” x 1.83”
Weight without
battery 12.5 oz
Battery Capacity / Type Dimensions (HxWxD) Weight Battery Part Numbers Smart Battery Battery Capacity
High Capacity NiCD 6.15” x 2.3” x .92” 11.10 oz HNN9031 Y 1525 mAH
High Capacity NiCD FM 6.15” x 2.3” x .92” 11.10 oz HNN9032 Y 1525 mAH
High Capacity NiCD Rugged FM 6.15” x 2.3” x .92” 11.10 oz NTN8297 N 1525 mAH
High Capacity NiMH 6.15” x 2.3” x .92” 9.53 oz NNTN4435 Y 1800 mAH
High Capacity NiMH FM 6.15” x 2.3” x .92” 9.53 oz NNTN4436 Y 1750 mAH
High Capacity NiMH Rugged FM 6.15” x 2.3” x .92” 9.53 oz NNTN4437 Y 1750 mAH
Ultra High Capacity NiMH 6.15” x 2.3” x .92” 13.18 oz RNN4006 N 3000 mAH
Ultra High Capacity NiMH FM 6.15” x 2.3” x .92” 13.18 oz RNN4007 N 3000 mAH
High Capacity Lithium Ion 6.15” x 2.3” x .60” 6.98 oz NTN8810 N 1650 mAH
High Capacity Lithium Ion 6.15” x 2.3” x .60” 6.98 oz NTN9862 Y 2000 mAH
Specification sheet
ASTRO® XTS® 5000


Temperature Shock 503.1 * 503.2 I/A1C3 503.3 I/A1C3 503.4 I
Humidity 507.1 II 507.2 II 507.3 II 507.4 –
Salt Fog 509.1 I 509.2 I 509.3 I 509.4 **
Blowing Dust 510.1 I 510.2 I 510.3 I 510.4 **
Immersion* 512.1 I 512.2 I 512.3 I 512.4 I
Vibration 514.2 VIII/F, Curve-W, XI 514.3 I/10, II/3 514.4 I/10, II/3 514.5 I/24
Mechanical Shock 516.2 I, II 516.3 I, IV 516.4 I/IV 516.5 I, IV
Supported Encryption Operating Temperature –30°C / +60°C

Algorithms ADP, AES, DES, DES-XL and DES-OFB, Storage Temperature –40°C / +85°C
DVP-XL, DVI-XL
Encryption Algorithm Capacity 8
ESD IEC 801-2KV
Encryption Keys per Radio Module capable of storing 1024 keys.
Water & Dust Intrusion IP54, IPX7*, MIL-STD
Programmable for 48 common Key Reference
Encryption Frame Re-sync Interval P25 CAI 360 mSec RUGGED OPTION SPECIFICATIONS
Encryption Keying Key Loader Leakage (immersion) MIL-STD-810 C, D, E, F

Synchronization CFB – Cipher Feedback Method 512.X Procedure I:
XL - Counter Addressing IPX7*
OFB - Output Feedback
Encryption Type Digital and 12 k-bit Analog Conventional
Key Storage Tamper protected volatile or non volatile memory
Standards • FIPS 46-2
• FIPS 140-2
• FIPS 197
* For rugged models only.

** Only single procedure defined.
R3-4-2009F
MOBEXCOMP25
Keep In Touch! DIGITAL VEHICULAR REPEATER SYSTEM
P25 COVERAGE TO GO
MOBEXCOM P25
The P25 Digital Vehicular Repeater System (DVRS) is the most cost effective
solution for providing reliable portable radio coverage in buildings and other
RF shielded areas.
Futurecom Vehicular Repeaters have been successfully deployed and in use
by numerous Fire Departments across the US and Canada for more then 15
years.
MOBEXCOM P25 SPECIAL FEATURES FOR FIRE GROUND APPLICATIONS

• Rugged, self contained trunk mount DVRS package specially designed for public safety use.
• Transportable (TDVRS) Package with battery backup provides extra coverage flexibility
and can be deployed where radio coverage is most needed.
• Programmable Simplex and Full Duplex mode.
• Can be configured for both Analog and P25 Digital operation to facilitate
transitions from old to new infrastructure.
• Provides instant interoperability between digital and analog users.
Can be used to bridge two different frequency bands (cross-band models only).
• Easily controlled from the Mobile radio control head.
• Programmable remote control capabilities.
• High power (up to 10 Watts) for better in-building penetration.
• Automated activation option available.
MOBEXCOM P25 TECHNICAL HIGHLIGHTS KEY P25 TRUNKING SYSTEM FEATURES

• Seamlessly interfaced to a remote mount Motorola radio: The following list describes some key P25 trunking
- XTL™5000 (O3 / O5 Control Head) system features, which can be made available to the
portable radio users via DVRS:
- XTL™2500 (M5 Control Head)
• Group Call (clear or coded).
• Available in VHF / UHF / 700 / 800MHz bands (25 or 12.5kHz).
• Private Call (clear or coded).
• In-band or Cross-Band models available.
• Emergency Alarm / Call.
• Digital (Conventional) DVRS mode can be used to extend
portable radio range in P25 Trunking (9600 Baud) or P25 • Portable PTT ID pass-through.
Conventional Systems. • Call Alert Paging.
• Analog Conventional DVRS mode can be used to extend • Talk permit / Prohibit tone.
portable radio range in P25 Trunking, P25 Conventional, • Talk Group Proxing.
3600 Trunking or Conventional Analog Systems.
• Radio Check / Inhibit.
• Can be used as a stand-alone repeater.
• Portable radio adaptive power control.
• 64 channels capable.
• P25 Over The Air Re-keying (OTAR).
• Fully synthesized and field programmable.
• Failsoft , Out of Range and Site Trunking indication
• Field flash upgradeable. pass through.
• Programmable output power 1-10 Watts (at Antenna port). • Dynamic regrouping.
• Advanced Simulcast Prevention Algorithm. • P25 Encryption.
• Fireground signaling support. Note: Some of the P25 features listed above require the
use of ‘DVRS Enabled’ XTS™2500 or XTS™5000 portable
radios.
KEY TYPE II TRUNKING SYSTEM FEATURES
The following list describes key 3600 trunking system features, which can
be made available to the portable radio user via DVRS:
• Group Call (clear only)
• Emergency Alarm / Call
• Portable Emergency MDC ID pass-through
• Talk Permit / Prohibit tone
MOBEXCOM APPLICATIONS
The mode of the Digital Vehicular Repeater (DVRS) can be selected from the mobile radio control head, automatically
by an external switch (portable charger, door or brake switch etc) or remotely.
The following modes are available: OFF, SYSTEM and LOCAL (optional).
In the OFF mode the DVRS is not active and the Mobile radio operates as if there were no Vehicular Repeater present.
This mode is to be used when the vehicle is in motion and no portable radio coverage extension is required.
SYSTEM mode is used when the portable radio users are attending to a fire incident and require extended portable
radio communications (typically in-building), Call Logging and reliable communications with the System users.
LOCAL mode can be programmed as an option for use in cases when the portable users and DVRS / Mobile radio
operators do not want to be heard by the system users or when the DVRS is deployed in an area where no system radio
coverage is available.
The communications capabilities available in each DVRS mode are summarized in the table below.
SELECTED DVRS MODE

COMMUNICATIONS SUPPORTED VIA DVRS OFF LOCAL SYSTEM
PORTABLE TO PORTABLE NO YES YES
PORTABLE TO DVRS / MOBILE RADIO OPERATOR NO YES YES
PORTABLE TO SYSTEM NO NO YES
SYSTEM TO PORTABLE NO NO YES
SYSTEM TO DVRS / MOBILE RADIO OPERATOR YES YES YES
DVRS / MOBILE RADIO OPERATOR TO PORTABLE NO YES YES
DVRS / MOBILE RADIO OPERATOR TO SYSTEM YES PROGRAMMABLE YES
Simplex
Full Duplex
Half Duplex
Portable Radio Users on selected DVRS Equipped Vehicle DVRS / Mobile Radio Operator
(Simplex or Full-Duplex) DVRS channel (inside Vehicle)
DVRS MODE (SIMPLEX OR FULL DUPLEX)

XTL™2500/XTL™5000 SELECTED MODE ANALOG P25 DIGITAL
P25 9600 BAUD TRUNKING YES YES
P25 CONVENTIONAL YES YES
3600 TRUNKING ANALOG OR DIGITAL YES NO
CONVENTIONAL ANALOG YES NO
Firefighter Image Copyright © 2007 Futurecom and its licensors. All rights reserved.
General Specifications
Dimensions (DVR & Duplexer only):
Height / Width / Depth 185mm (7.28”) / 186mm (7.32”) / 315mm (12.41”)
Weight (DVR Only, without filtering) 10.3kg (22.7lb)
Channel Spacing 12.5 or 25 kHz programmable
Number of Channels 64
CTCSS/DCS Programmable per channel
Power Supply 13.8V DC +/- 20%
DC Current Drain RPTR off 0.01 A Max
Standby/Receive 0.8 A Max
Transmit 4.5 A Max
Operating Temperature -30° to +60° C
Protection Against Liquids IP6 (water jet proof)
Antenna Impedance 50 Ohms
Duty Cycle Continuous
External Connectors Antenna Mini UHF
Computer Interface USB
Equipment Type Acceptance VHF UHF 700 800
FCC LO6-DVRSVHF LO6-DVRSUHF LO6-DVRS700 LO6-DVRS800

Industry Canada 2098B-DVRSVHF 2098B-DVRSUHF 2098B-DVRS700 2098B-DVRS800
Transmitter Specifications VHF UHF 700 800

Frequency Band [MHz] 136-174 380-430 764-776 851-870
450-470
470-512
Power Output @ Antenna Port 10W (programmable per channel from 1W to 10W)
CCT Option 15 sec to 15 min or Disabled
Max Spurious Output -20dBm
Frequency Stability +/- 1.5ppm
FM Hum and Noise 12.5 / 25 kHz 37 dB / 43 dB
Audio Response +1, -3 dB of 6 dB / octave pre-emphasis characteristic over
300 Hz – 3 kHz
Audio Distortion <2%
Receiver Specifications VHF UHF 700 800
Frequency Band [MHz] 136-174 380-430 794-806 806-825
450-470
470-512
Receiver Sensitivity -115 dBm (0.39µV)
Frequency Stability +/- 1.5ppm
Selectivity 12.5 / 25 kHz 60 dB / 75 dB
Intermodulation 75 dB
Deviation 12.5 / 25 kHz +/-2.5 kHz / +/-5 kHz
FM Hum and Noise 12.5 / 25 kHz 37 dB / 43 dB
Audio Output (Repeater Detect Audio) 600 mV RMS nominal, flat response
Audio Response +1, -3 dB of 6 dB / octave pre-emphasis characteristic over
300 Hz – 3 kHz
Audio Distortion <2%
MOBEXCOM P25 DVRS AVAILABLE EXCLUSIVELY FROM MOTOROLA
3277 Langstaff Rd., Concord, ON Canada L4K 5P8

Tel. 1-800-701-9180 or (905) 660-5548, Fax (905) 660-6858
© Futurecom Systems Group Inc. 2007 Printed in Canada 8Q100X07 Rev. 1
specification sheet
APX 7000 ™
Project 25 Multi-Band Portable Radio
Top Display Model: Dual Display Model:

Up to 96 channels Same as APX Top Display model
Universal Push-to-Talk plus the following features:
T-Grip 1250 channels
Dual Battery Latch Dial from pre-stored lists or free-

form entry
Orange emergency button
Programmable soft keys for easy
16 position rotary knob access to radio menus
2 position concentric switch Backlit Keypad
3 position toggle switch • Home and Data buttons
3 programmable side buttons • 3 soft keys
• 4 direction navigation key
Transmit LED indicator • 4 x 3 keypad
Full Bitmap Top Display Full Bitmap Display
• 1 line of icons • 2 lines of icons
• 1 line x 8 characters of text • 4 lines x 14 characters of text
No keypad • Status icons
The APX 7000 Multi-Band P25 Portable Radio delivers exceptional performance
combining advanced voice and data technology driven by the challenges of
mission critical users.
Motorola’s 4th generation P25 subscriber is multi-band (700/800 MHz, VHF,
and UHF Range 1), communicates with current and future networks (FDMA
and TDMA) and has integrated GPS. Designed specifically for first responders
the dual-sided mission critical design has both an audio and data side providing
optimal functionality and loud and clear audio in a compact rugged form factor.
specification sheet
APX 7000

Available in 700/800 MHz, VHF, and UHF Range 1 bands Ships standard IP67 (Submersible at 1 meter, 30 minutes)
Optional multi-band operation Rugged option available
Trunking standards supported: Public Safety Yellow and High Impact Green Rugged Housing options
• Clear or digital encrypted ASTRO®25 Trunked Operation Custom recessed label areas
• Capable of SmartZone®, SmartZone Omnilink, SmartNet® Superior Audio Features:
Analog MDC-1200 and Digital APCO P25 Conventional System • 1W high audio speaker
Configurations • Dual speakers (Dual Display model only)
• Dual microphones
Narrow and wide bandwidth digital receiver
• 2-mic noise canceling technology
(6.25 kHz /12.5 kHz / 25 kHz)
Utilizes Windows XP and Vista Customer Programming Software (CPS)
Embedded digital signaling (ASTRO & ASTRO 25)
• Supports USB communications
Integrated GPS capable • Built in FLASHport™ support
Seamless wideband scan Full portfolio of accessories including IMPRES batteries, chargers
Intelligent Lighting and audio devices
Radio Profiles
Unified Call List (Dual Display model only) OPTIONAL FEATURES:
Expansion Slot Enhanced Encryption capability
Micro SD removable memory card Programming Over Project 25
User programmable voice announcement Over the Air Rekey
Meets Applicable Mil Specs 810C, D, E and F Text Messaging
700 MHz 800 MHz VHF UHF Range 1

Frequency Range/Bandsplits 764-776 806-825 136-174 380-470 MHz
794-806 851-870
Channel Spacing 25/20/12.5 kHz 25/20/12.5 kHz 25/12.5 kHz 25/12.5 kHz
Rated RF Output Power Adj1 1-3 Watts Max 1-3 Watts 1-6 Watts 1-5 Watts
Frequency Stability1
(–30°C to +60°C; +25°C Ref.) ±0.000020 % ±0.000030 % ±0.000025 % ±0.000025 %
Modulation Limiting1 ±5 kHz / ±4 kHz / ±2.5 kHz ±5 kHz / ±4 kHz / ±2.5 kHz ±5 kHz / ±2.5 kHz ±5 kHz / ±2.5 kHz
Emissions (Conducted and Radiated)1 –75 dB –75 dB –75dB –75dB
Audio Response1 +1, –3 dB +1, –3 dB +1, –3 dB +1, –3 dB
FM Hum & Noise –48 dB –47 dB –47 dB –47dB
Audio Distortion1 0.60 % 1 % 0.50 % 0.50 %
BATTERIES FOR APX 7000
Battery Capacity / Type Dimensions (HxWxD) Weight Battery Part Numbers Battery Capacity
Li-Ion IMPRES 2900 mAh (Ruggedized) 3.07” x 2.34” x 1.65” 6.53 oz NNTN7038 2900 mAh
Li-Ion IMPRES 4200 mAh Ruggedized (IP67) 5.12” x 2.34” x 1.65” 11.29 oz NNTN7034 4200mAh
Li-Ion IMPRES 4100 FM2 Ruggedized (IP67) 5.12” x 2.34” x 1.65” 11.29 oz NNTN7033 4100 mAh
NiMH IMPRES 2100 mAh Ruggedized (IP67) 5.07” x 2.34” x 1.57” 11.82 oz NNTN7037 2100 mAh
NIMH IMPRES 2000 mAh FM2 Ruggedized (IP67) 5.07” x 2.34” x 1.57” 11.82 oz NNTN7036 2000 mAh
NiMH IMPRES 2000 mAh FM2 Ruggedized PLUS 5.07” x 2.34” x 1.57” 11.82 oz NNTN7035 2000 mAh
NiMH IMPRES 2100 mAh Ruggedized PLUS 5.07” x 2.34” x 1.57” 11.82 oz NNTN7573 2100 mAh
specification sheet
APX 7000
700 MHz 800 MHz VHF UHF Range 1

Frequency Range/Bandsplits 764-776 851-870 136-174 MHz 380-470 MHz
Channel Spacing 12.5/25 kHz 12.5/25 kHz 12.5/25 kHz 12.5/25 kHz
Audio Output Power at Rated1 1000mW 1000mW 1000mW 1000mW
(–30°C to +60°C; +25°C Ref.) ±0.000080 % ±0.000080 % ±0.000086 % ±0.000086 %
Analog Sensitivity3 12 dB SINAD 0.250 µV 0.250 µV 0.216 µV 0.234 µV
Digital Sensitivity4 1% BER 0.347 µV 0.333 µV 0.277 µV 0.307 µV
5% BER 0.251 µV 0.251 µV 0.188 µV 0.207 µV
Selectivity1 25 kHz channel 75.7 dB 75.7 dB 79.3 dB 78.3 dB
12.5 kHz channel 67.5 dB 67.5 dB 70 dB 68.1 dB
Intermodulation 80 dB 80 dB 80.5 dB 80.2 dB
Spurious Rejection 76.6 dB 76.6 dB 93.2 dB 80.3 dB
FM Hum and Noise 25 kHz –54 dB –54 dB –53.8 dB –53.5 dB
12.5 kHz –48 dB –48 dB –48 dB –47.4 dB
Audio Distortion1 .9 % .9 % 1.20 % 0.91 %
GPS specifications
Channels 12
Tracking Sensitivity –151 dBm
Accuracy 5 <10 meters (95%)
Cold Start <60 seconds (95%)
Hot Start <10 seconds (95%)
Mode of Operation Autonomous (Non-Assisted) GPS
RADIO MODELS
Channel FLASHport 700/800 MHz VHF UHF Range 1 Embedded

Display Keypad Capacity Memory (764-870 MHz) (136-174 MHz) (380-470 MHz) Buttons/Switches GPS LED
Top Display Full bitmap None 96 64 MB H97TGD9PW1_N H97TGD9PW1_N H97TGD9PW1_N Large PTT button Yes Multi-color
monochromatic LCD (using zone QA00569 QA00570 QA00571 Angled On/Off
display bank feature) Volume knob
1 line text x 8 Orange emergency button
characters 16-position top-mounted
1 line of icons rotary knob
No menu support 2-position concentric switch
Multi-color backlight 3-position toggle switch
3 programmable side buttons
Dual Display Top display, plus: Multi-color backlight 1250 64 MB H97TGD9PW1_N H97TGD9PW1_N H97TGD9PW1_N Large PTT button Yes Multi-color
Full bitmap color Keypad QA00569 QA00570 QA00571 Angled On/Off
LCD display: 3 soft keys QA00577 QA00577 QA00575 Volume knob
4 lines text x 14 4-direction Orange emergency button
characters navigation key 16-position top-mounted
2 lines of icons 4x3 keypad rotary knob
1 menu line x Home and Data 2-position concentric switch
3 menus buttons 3-position toggle switch
White backlight 3 programmable side buttons
Transmitter Certification AZ489FT7036 AZ489FT7036 AZ489FT7040 (UHF/700/800)
AZ489FT4886 (UHF/VHF)
FCC Emissions Designators 11K0F3E, 16K0F3E, 8K10F1D, 8K10F1E, 8K10F1W, 20K0F1E
Power Supply One rechargeable Li-Ion 2900 mAh battery, or one optional NiMH
specification sheet
APX 7000
Dimensions of the radios without battery
Inches Millimeters
Length 6.29 159.71
Width Push-to-Talk button 2.31 58.69
Depth Push-to-Talk button 1.34 34
Width Top 2.98 75.69
Depth Top 1.6 40.52
Depth Bottom of Battery 1.65 41.78
Weight of the radios without battery 12.2 oz

High Temperature 501.1 I, II 501.2 I/A1, II/A1 501.3 I/A1, II/A1 501.4 I/Hot, II/Hot
Temperature Shock 503.1 – 503.2 I/A1C3 503.3 I/A1C3 503.4 I
Rain 506.1 I, II 506.2 I, II 506.3 I, II 506.4 I, II
Humidity 507.1 II 507.2 II 507.3 II 507.4 –
Salt Fog 509.1 – 509.2 – 509.3 – 509.4 –
Blowing Dust 510.1 I 510.2 I, II 510.3 I, II 510.4 I, II
Immersion6 512.1 I 512.2 I 512.3 I 512.4 I
Mechanical Shock 516.1 I, II 516.3 I, IV 516.4 I/IV 516.5 I, IV
ENCRYPTION RUGGED OPTION SPECIFICATIONS
Supported Encryption Algorithms ADP, AES, DES, DES-XL, DES-OFB, DVP-XL Leakage (immersion)6 MIL-STD-810 C, D, E, F
Encryption Algorithm Capacity 8 Method 512.X Procedure I
Encryption Keys per Radio Module capable of storing 1024 keys. Housing Availability Standard, Public Safety Yellow
Programmable for 64 Common Key Reference and High Impact Green
Encryption Frame Re-sync Interval P25 CAI 300 mSec ENVIRONMENTAL SPECIFICATIONS
Encryption Keying Key Loader Operating Temperature –30° C / +60° C
Synchronization XL – Counter Addressing Storage Temperature7 –40° C / +85° C
OFB – Output Feedback
ESD IEC 801-2 KV
Water & Dust Intrusion IP67 MIL-STD
Encryption Type Digital
Key Storage Tamper protected volatile or non-volatile memory 1
Measured in the analog mode per TIA / EIA 603 under nominal conditions
2
When used with an FM approved intrinsically safe radio.
Key Erasure Keyboard command and tamper detection 3
Measured conductively in analog mode per TIA / EIA 603 under nominal conditions
Standards FIPS 140-3 4
Measured conductively in digital mode per TIA / EIA IS 102.CAAA under nominal
conditions
FIPS 197 5
Accuracy specs are for long-term tracking (95th percentile values >5 satellites visible
at a nominal –130 dBm signal strength)
6
For rugged models only
7
Temperatures listed are for radio specifications. Battery storage is recommended at
25°C, ±5°C to ensure best performance
R3-4-2021B
SPECIFICATION SHEET
PRELIMINARY
APX™ 7000XE
We take the safety of first responders personally, Advanced ergonomics FOR
which is why we designed the APX™ 7000XE – the
EXTREME CONDITIONS
most advanced, ultra-rugged radio with innovative
features designed by first responders for first E asy to grip, hold and control in harsh
conditions
responders working in extreme environments.
G love-friendly controls are big, recognizable
Together we have created an ergonomically- and easy to distinguish
superior radio that is easy to operate, with W ell-spaced knobs eliminate accidental
glove-friendly controls and a large top display. activation
Significantly louder and clearer so that every word E nlarged top display is easy to read, in dark
or low light
is heard when you’re battling noise in almost any
environment. A mission critical multiband, multi- S hielded push-to-talk button is easy to use
with a gloved hand
protocol radio so seamless, you can be confident
your communications are truly interoperable. L argest emergency button in the industry
with programmable time delay
Focus on the task, not the technology, with the
high-performing portable that stands up and Exceptional audio means every
stands out in the toughest conditions. word is heard
5 0% louder and clearer without distorting
transmissions
D ual microphone locates the talker, cancels
Channel Capacity out ambient noise
96 standard E xtreme Audio Profile reduces background
1250 max noise and improves voice clarity
Universal Push-to-Talk
Equipped
with the latest AMBE digital voice
T-Grip vocoder
Dual Battery Latch New
speaker grill design for improved water
Orange emergency button runoff
16 position rotary knob
2 position concentric switch Next generation technology
3 position toggle switch to rely on now
3 programmable side buttons P roject 25 Phase 2 technology provides
Transmit LED indicator twice the voice capacity
Full Bitmap Top Display M ultiband operation ensures seamless
1 line of icons interoperability
1 line x 8 characters of text
B ackwards and forwards compatible with all
Standard Rugged Motorola mission critical radio systems
FM (Intrinsically Safe) F uture-ready for applications like Mission
Critical Wireless and GPS location tracking
APX™ 7000XE Specifications
Available in 700/800 MHz, VHF and UHF Range 1 and 2 Yellow and green colored housing options
Optional multiband operation Superior Audio Features:
Trunking standards supported: Extreme Audio Profile
Clear or digital encrypted ASTRO®25 Trunked Operation 1 W high audio speaker
Capable of SmartZone®, SmartZone Omnilink, SmartNet® Dual sided 2 microphone noise canceling
Analog MDC-1200 and Digital APCO P25 Conventional technology
System Configurations Utilizes Windows XP, Windows 7 and Vista
Narrow and wide bandwidth digital receiver Customer Programming Software (CPS)
(6.25 kHz /12.5 kHz / 25 kHz) Supports USB communications
Embedded digital signaling (ASTRO & ASTRO 25) Built in FLASHport™ support
Integrated GPS capable Full portfolio of accessories including
Seamless wideband scan IMPRES batteries, chargers and
audio devices
Intelligent Lighting
Radio Profiles OPTIONAL FEATURES:
Expansion Slot Mission Critical Wireless
Micro SD removable memory card Enhanced Encryption capability
User programmable voice announcement Programming Over Project 25
Meets Applicable MIL-STD 810C, D, E, F and G Over the Air Rekey
Ship standard Intrinsically Safe and Rugged Text Messaging
* Rugged radios exceed industry standards (IPx7) for immersion and provide a higher level of water protection—MIL-STD-810E,
Method 512.3 Immersion. These radios meet the incremental requirement of submersion in 1 meter of fresh water that is 27C colder
than the product.
Transmitter - Typical performance specifications

700/800 VHF UHF Range 1 UHF Range 2
700 MHz 764-776 MHz
Frequency Range/Bandsplits 136-174 MHz 380-470 MHz 450-520 MHz
800 MHz 794-806 MHz
Channel Spacing 25/20/12.5 kHz 12.5/20/25 kHz 12.5/20/25 kHz 12.5/25 kHz
Rated RF Output Power Adj1 1-3 Watts Max 1-6 Watts Max 1-5 Watts Max 1-5 Watts Max
Frequency Stability 1
±0.000010 % ±0.000010 % ±0.000010 % ±0.000020 %
(–30°C to +60°C; +25°C Ref.)
Modulation Limiting1 ±5 kHz / ±4 kHz / ±2.5 kHz ±5 kHz / ±2.5 kHz ±5 kHz / ±2.5 kHz ±5 kHz / ±2.5 kHz
Emissions (Conducted and Radiated)1 –75 dB –75 dB –75 dB –75 dB
Audio Response1 +1, –3 dB +1, –3 dB +1, –3 dB +1, –3 dB
700 MHz –48 dB
FM Hum & Noise –47 dB –47 dB –47 dB
800 MHz –47 dB
700 MHz 0.60 %
Audio Distortion1 0.50 % 0.50 % 0.50 %
800 MHz 1%
BATTERIES FOR APX 7000XE

Battery Capacity / Type Dimensions (HxWxD) Weight Battery Part Number Battery Capacity
Li-Ion IMPRES 2300 mAh FM2 Rugged 3.39” x 2.34” x 1.65” 6.53 oz NNTN8092 2300 mAh
Li-Ion IMPRES 2150 mAh IP67 3.39” x 2.34” x 1.45” 5.0 oz PMNN4403 2150 mAh
Li-Ion IMPRES 2900 mAh IP67 3.39” x 2.34” x 1.65” 6.53 oz NNTN7038 2900 mAh
Li-Ion IMPRES 4200 mAh IP67 5.07” x 2.34” x 1.65” 11.29 oz NNTN7034 4200 mAh
Li-Ion IMPRES 4100 mAh FM2 IP67 5.07” x 2.34” x 1.65” 11.29 oz NNTN7033 4100 mAh
NiMH IMPRES 2100 mAh IP67 5.12” x 2.34” x 1.57” 11.82 oz NNTN7037 2100 mAh
NIMH IMPRES 2000 mAh FM IP67 2
5.12” x 2.34” x 1.57” 11.82 oz NNTN7036 2000 mAh
NiMH IMPRES 2000 mAh FM2 Rugged 5.12” x 2.34” x 1.57” 11.82 oz NNTN7035 2000 mAh
NiMH IMPRES 2100 mAh Rugged 5.12” x 2.34” x 1.57” 11.82 oz NNTN7573 2100 mAh
APX ™ 7000XE Specifications
receiver - typical performance specifications

700/800 VHF UHF Range 1 UHF Range 2
700 MHz 764-776 MHz
Frequency Range/Bandsplits 136-174 MHz 380-470 MHz 450-520 MHz
800 MHz 851-870 MHz
Channel Spacing 12.5/25 kHz 12.5/20/25 kHz 12.5/20/25 kHz 12.5/25 kHz
Audio Output Power at Rated1 1000mW 1000mW 1000mW 1000mW
±0.00010 % ±0.00010 % ±0.00010 % ±0.00086 %
(–30°C to +60°C; +25°C Ref.)
Analog Sensitivity3 12 dB SINAD 0.250 μV 0.216 μV 0.234 μV 0.234 μV
Digital Sensitivity4 1% BER (800 MHz) 0.347 μV (0.333 μV) 0.277 μV 0.307 μV 0.307 μV
5% BER 0.251 μV 0.188 μV 0.207 μV 0.207 μV
Selectivity1 25 kHz channel 75.7 dB 79.3 dB 78.3 dB 78.3 dB
12.5 kHz channel 67.5 dB 70 dB 68.1 dB 67.5 dB
Intermodulation 80 dB 80.5 dB 80.3 dB 80.2 dB
Spurious Rejection 76.6 dB 93.2 dB 80.3 dB 80.3 dB
FM Hum and Noise 25 kHz -54 dB -53.8 dB -53.5 dB -53.5 dB
12.5 kHz -48 dB -48 dB -47.4 dB -47.4 dB
Audio Distortion1 .9 % 1.20 % 0.91 % 0.91 %
radio models
Top Display
Display Full bitmap monochromatic LCD display 1 line text, 8 characters 1 line of icons No menu support Multi-color backlight
Keypad none
Channel Capacity 96 channels standard, optional 1250 with Enhanced Zone Bank
FLASHport Memory 64 MB
700/800 MHz (764-870 MHz) H49TGD9PW1AN QA00569
VHF (136-174 MHz) H49TGD9PW1AN QA00570
UHF Range1 (380-470 Mhz) H49TGD9PW1AN QA00571
UHF Range2 (450-520 Mhz) H49TGD9PW1AN QA00572
Large PTT button Angled On/Off Volume knob X-large emergency button 16 position top mounted rotary knob 1 line of icons /
Buttons & Switches
no menu support 2-position concentric switch Multi-color backlight 3-position toggle switch 3 programmable side buttons
GPS Yes
Embedded
LED Multi-color
Transmitter Certification
700/800 (764-870 MHz) AZ489FT7036
VHF (136-174 MHz) AZ489FT7036
UHF Range1 (380-470 MHz) AZ489FT7040 (UHF/700/800)
UHF Range2 (450-520 MHz) AZ489FT4886 (UHF/VHF)
FCC Emissions Designators
FCC Emissions Designators 11K0F3E, 16K0F3E, 8K10F1D, 8K10F1E, 8K10F1W, 20K0F1E
Power Supply
Power Supply One rechargeable 2300 FM/Rugged Li-Ion Battery Standard, optional NiMH or high capacity Li-Ion
dimensions of the radios without battery GPS SPEcifications

Inches Millimeters Channels 12
Length 6.94 176.32 Tracking Sensitivity –151 dBm
Width Push-To-Talk button 2.39 60.81 Accuracy5 <10 meters (95%)
Depth Push-To-Talk button 1.47 37.29 Cold Start <60 seconds (95%)
Width Top 3.32 84.34 Hot Start <10 seconds (95%)
Depth Top 2.13 54.1 Mode of Operation Autonomous (Non-Assisted) GPS
Depth Bottom of Battery 1.64 41.78
Weight of the radios without battery 15.4 oz 438 g
APX ™ 7000XE Specifications
PORTABLE MILITARY STANDARDS 810 C, D, E , F & G

MIL-STD 810C MIL-STD 810D MIL-STD 810E MIL-STD 810F MIL-STD 810G
I/Hot, II/Basic
High Temperature 501.1 I, II 501.2 I/A1, II/A1 501.3 I/A1, II/A1 501.4 501.5 I/A1, II/A2
Hot
Low Temperature 502.1 I 502.2 I/C3, II/C1 502.3 I/C3, II/C1 502.4 I/C3, II/C1 502.5 I/C3, II/C1
Temperature Shock 503.1 I 503.2 I/A1C3 503.3 I/A1C3 503.4 I 503.5 I/C
Solar Radiation 505.1 II 505.2 I 505.3 I 505.4 I 505.5 I/A1
Rain 506.1 I, II 506.2 I, II 506.3 I, II 506.4 I, III 506.5 I, III
Humidity 507.1 II 507.2 II 507.3 II 507.4 – 507.5 II/Aggravated
Salt Fog 509.1 I 509.2 I 509.3 I 509.4 – 509.5 –
Blowing Dust 510.1 I 510.2 I 510.3 I 510.4 I 510.5 I
Blowing Sand – – 510.2 II 510.3 II 510.4 II 510.5 II
Immersion (Delta-T) 512.1 I 512.2 I 512.3 I 512.4 I 512.5 I
Vibration 514.2 VIII/F, Curve-W 514.3 I/10, II/3 514.4 I/10, II/3 514.5 I/24 514.6 I/24
Shock 516.2 I, III, V 516.3 I, V, VI 516.4 I, V, VI 516.5 I, V, VI 516.6 I, V, VI
Shock (Drop) 516.2 II 516.2 IV 516.4 IV 516.5 IV 516.6 IV
* Applicable to Rugged products only
encryption RUGGED OPTION SPECIFICATIONS

Supported Encryption Algorithms ADP, AES, DES, DES-XL, DES-OFB, DVP-XL MIL-STD-810 C,D,E,F and G
Leakage (immersion)
Encryption Algorithm Capacity 8 Methood 512.X Procedure I
Encryption Keys per Radio Module capable of storing 1024 keys. Black, Public Safety Yellow
Housing Availability
Programmable for 128 Common Key Reference and High Impact Green
environmental SPEcifications
Operating Temperature -30ºC / +60ºC
Storage Temperature -40ºC / +85ºC
XL – Counter Addressing
Synchronization
OFB – Output Feedback Humidity Per MIL-STD
National Institute of Standards and Technology ESD IEC 801-2 KV
Vector Generator
(NIST) approved random number generator Water and Dust Intrusion IP67, MIL-STD
Encryption Type Digital Immersion (Delta-T) MIL-STD 512.X/I
Key Storage Tamper protected volatile or non-volatile memory
1
Measured in the analog mode per TIA / EIA 603 under nominal conditions
2
When used with an FM approved intrinsically safe radio
FIPS 140-3 3
Measured conductively in analog mode per TIA / EIA 603 under nominal conditions
Standards 4
Measured conductively in digital mode per TIA / EIA IS 102.CAAA under nominal conditions
FIPS 197 5
Accuracy specs are for long-term tracking (95th percentile values >5 satellites visible at a
nominal –130 dBm signal strength)
6
Temperatures listed are for radio specifications. Battery storage is recommended at 25°C,
±5°C to ensure best performance
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com
MOTOROLA and the stylized M Logo are registered in the U.S. Patent and Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2010 R3-4-2034
®
Bird Omnidirectional Collinear

Antenna
CC807-06
Bird Technologies Group, TX RX Systems brand, offers a Corporate

Collinear Antenna that is PIM and PIP rated. The true corporate feed
of these arrays maintains total pattern integrity over a very broad
operating bandwidth. This is now achieved in the preferred form
factor of a fully enclosed fiberglass radome.
PROBLEM SOLUTION
Bandwidth needed Extraordinary bandwidth characteristics

with superior pattern control over an
extended band coverage
PIM Concerns Industry leading PIM specifications
maintained over the service life of the A PPLICATIONS
antenna
PIP Concerns PIP Rated ensuring compatability These high gain collinear arrays allow site
with Multi Channel Transmitter
applications employing newer digital
operators to combine, with complete integrity,
modulation schemes a large number of communications services into
Antenna Orientation Invertible in the field to suit all a single, low profile collinear antenna array.
applications
Bird Omnidirectional Collinear Antenna
®
CC807-06
Specifications, Electrical Specifications, Mechanical
Model Number CC807-06 Construction & Configuration Composite fiberglass with sky
Nominal Gain dBi (dBd) 7.7 (5.5) blue radome, aluminum
mounting tube
Frequency (MHz) 746-870
Tuned Bandwidth Full Length (inches) 72
VSWR 1.5:1 Radome Diameter (inches) 3
Nominal Impedance (ohms) 50 Weight (lbs) 16
Vertical Beamwidth (degrees) 17 Shipping Weight (lbs) 45
Horizontal Beamwidth (degrees) 360 Shipping Dimensions (inches) 6 (H) x 6 (W) x 79 (L)
Power (W)* 500 Termination 7/16” DIN female flange mount
Passive IM 3rd order (dBc)** -150 Mounting Area (inches) 20 x 3.5 diam. Aluminum
Peak Instantaneous Power (kW) 25 Suggested Clamps (not included) 91-00-111
Invertible Mounting Yes
*This is a continuous power rating based on internal temperatures stabilizing at
no greater than 50° Celsius above ambient. Projected Area (ft2) 1.4 (no ice)
**Referenced to 2 x 20W carriers. 1.8 (with ice)
Lateral thrust @ 100 (mph) 36
Wind Gust Rating >150 (no ice)
>150 (with ice)
Torque @ 100 (ft-lbs) 54
Antennas
700-1000 MHz Antennas
SC479 - PIM Certified Series
SC479-HF1LDF(E5608) Collinear omni antenna, 9 dBd gain, HD, 746-869 MHz

• Covers the 746-869 MHz frequency range
• Higher power handling capability
• Optimized null fill for close-in coverage enhancement
• Recommend using the SMK-325-A3 side mounting kit
This broadband, heavy duty, omni-directional antenna covers the entire 746-869
MHz frequency range. It is constructed to minimize intermodulation products in multi
-carrier systems. It is ideal for applications requiring a broad band antenna with
limited tower space.
www.sinctech.com
Region United States Europe, Middle East and Africa Caribbean and Latin America Canada and rest of the world
Canada: 1 800 263 3238
Telephone USA: 1 800 288 2763 International: +44 (0) 1223 42 03 03 International: +1 305 235 2706
International: +1 905 727 0165
E-mail salesusa@sinctech.com salesuk@sinctech.com salesla@sinctech.com salescan@sinctech.com
Product Specification Sheet SC479-HF1LDF(E5608) Issue: 21 Dated: 09-01-09
EPR 000000 Dated: 28-10-08
Sinclair’s commitment to product leadership may result in improvement or change to this product
Copyright © Sinclair Technologies Page 1/2
Antennas
700-1000 MHz Antennas
SC479 - PIM Certified Series
Notes
*1 : Other down tilt available up request
Electrical Specifications *2 : Recommend #6C Clamp
Bandwidth MHz 123
Frequency Range 1 (F1) MHz 746 to 869
Polarization vertical
Gain (nominal) dBd (dBi) 9 (11.1)
Electrical tilt (available) 1,3, 5 *1
Impedance Ω 50
Null fill % 25
Lightning protection DC ground
Passive intermod. (2x20W, 3rd ord.) dBc -150
Pattern Omni-directional Ordering Information
Vertical beamwidth degrees 5.7 Upside mount only. Recommend using the SMK-325-A3
Average power input (max) W 500 side mounting kit.
Mechanical Specifications
Width in (mm) 3.5 (89)
Depth in (mm) 3.5 (89)
Shipping dimensions in (mm) 192x6.5x6.5 (4877x165x165)
Weight lbs (kg) 34 (15.4)
Shipping weight lbs (kg) 76 (34.5)
Length in (mm) 172.5 (4382)
Connector 7/16 DIN (female)
Weight iced lbs (kg) 66 (30)
Base pipe diameter in (mm) 3.5 (89)
Mounting hardware clamps not supplied *2
www.sinctech.com
Environmental Specifications
Rated wind velocity (1/2" radial ice) mph (km/h) 155 (250)
Rated wind velocity (no ice) mph (km/h) 170 (274)
Temperature range °F (°C) -40 to +140 (-40 to +60)
Tip deflection degrees 1.5
Projected area (Flat Plate Equivalent) ft² (m²) 2.46 (0.23)
Projected area (ice) ft² (m²) 3.25 (0.3)
Lateral thrust (100mph) lbs (N) 97 (431.5)
Bending moment ft-lbs (Nm) 520 (702)
Product Specification Sheet SC479-HF1LDF(E5608) Issue: 21 Dated: 09-01-09

EPR 000000 Dated: 28-10-08
Sinclair’s commitment to product leadership may result in improvement or change to this product
Copyright © Sinclair Technologies Page 2/2
Section 15. Appendix
Additional items are included on the following pages.

RFP# 101216
December 16, 2010
Appendix 15-1

RFP# 101216
December 16, 2010
15-2 Appendix

Motorola Technical Original

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Motorola Technical Original

Transféré par

Droits d'auteur :

Formats disponibles

Table of Contents

Section 1. Executive Summary ______________________________________________1-1

Floyd County, Georgia

Table of Contents -1-

Floyd County, Georgia

-2- Table of Contents

9.2 Site Development Statement of Work 9.2-1

Floyd County, Georgia

Table of Contents -3-

Floyd County, Georgia

-4- Table of Contents

Floyd County, Georgia

Project 25 Digital Public Safety Radio

1700 Belle Meade Ct., Lawrenceville, GA 30043

Floyd County, Georgia

Executive Summary 1-1

Floyd County, Georgia

1-2 Executive Summary

.....the public safety and public service personnel within Floyd

.....the community by ensuring radio coverage throughout schools

.....the long term protection of your investment, which is ensured

..…the regional interoperability between Floyd County first

P25 Open Standard Infrastructure

Rome-Floyd System Design

Mobile and Portable Radios

Our proposal reflects compliance to the RFP specifications with

Motorola understands the critical importance of coverage to the City of Rome

Regional interoperability starts with first responders and how compatible

As noted in the RFP, the reliability and hardening of communications network

Motorola’s proposal directly addresses the RFP requirements for

Local Experience and Commitment

Motorola’s Coverage Advantage - Linear Simulcast Modulation

Local Motorola Service Shop (MSS)

Local Experience and Commitment

Detailed System Engineering

EXPERIENCE + TECHNOLOGY + LOCAL PARTNERS

MORE COVERAGE DESIGN EXPERIENCE, GUARANTEED

Required Signed Forms

Floyd County, Georgia

Required Signed Forms 2-1

Floyd County, Georgia Motorola Confidential Restricted

2-2 Required Signed Forms

Floyd County, Georgia

Point-by-Point Responses 3-1

Floyd County, Georgia

3-2 Point-by-Point Responses

Motorola Confidential Restricted Floyd County, Georgia

Point-by-Point Response 3-1

Floyd County, Georgia Motorola Confidential Restricted

3-2 Point-by-Point Response

Motorola Confidential Restricted Floyd County, Georgia

Point-by-Point Response 3-3

Per Addendum 1, released October 21, 2010:

Floyd County, Georgia Motorola Confidential Restricted

3-4 Point-by-Point Response

1.2.2.1 Proposal Release

Motorola Confidential Restricted Floyd County, Georgia

Point-by-Point Response 3-5

Floyd County, Georgia Motorola Confidential Restricted

3-6 Point-by-Point Response

Floyd County reserves the right to discontinue consideration of a Proposer’s submittal if

Motorola Confidential Restricted Floyd County, Georgia

Point-by-Point Response 3-7