Académique Documents
Professionnel Documents
Culture Documents
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
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.
2
PROPOSED SYSTEM DESIGN
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.
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.
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
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.
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)
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.
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!
11
11
MOTOROLA HELPS PEOPLE BE THEIR BEST IN THE MOMENTS THAT MATTER.
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
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
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
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
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
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
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
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
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
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
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
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
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.
Comply
Motorola exceeds the above stated requirements.
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.
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.
Per Addendum 1, released October 21, 2010:
Question:
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.
Per Addendum 1, released October 21, 2010:
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?
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.
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
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 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
Motorola will comply with the following clarifications:
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.
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.
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”.
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”.
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
The call signs of the existing VHF and UHF systems are as follows:
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
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.
Per Addendum 1, released October 21, 2010:
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 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.
Per Addendum 1, released October 21, 2010:
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
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
Comply
A P25 800MHz digital repeater is provided to meet the Floyd County Prison requirements
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
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
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
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
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.
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
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
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.
Per Addendum 1, released October 21, 2010:
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.
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.
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
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
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
• Frequency Range: 764 to 870MHz (standard post rebanding public safety
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
• Modulation Deviation:
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
• Frequency Range: 764 to 870MHz (standard post rebanding public safety
frequencies)
• Channel Spacing: 25/12.5/6.25 KHz/NPSPAC Mod. Acceptance: +/-7KHz
• Selectivity: -70db (25KHz channel)
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
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:
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
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.
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 exceeds the above stated requirements.
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
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
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)
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
The Control Point equipment site shall contain, minimally, the following major equipment
groupings:
System Controller
Simulcast Equalization/Sync Equipment
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:
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:
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.
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.
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.
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
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:
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
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:
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.
Per Addendum 1, released October 21, 2010:
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
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
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
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
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
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
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.
Per Addendum 3, released November 19, 2010:
Question:
Comply
Motorola exceeds the above stated requirements.
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 exceeds the above stated requirements.
Motorola is providing an integrated Fire Station Alerting interface incorporated into the MCC
7500 console system.
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.
Per Addendum 2, released October 29, 2010:
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
Comply
Motorola’s offering will reuse a decommissioned VHF MTR2000 repeater to provide
800MHz Trunking dispatch traffic to the existing fire pagers.
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.
Per Addendum 1, released October 21, 2010:
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..
Per Addendum 3, released November 19, 2010:
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.
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.
Per Addendum 1, released October 21, 2010:
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.”
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.
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
Per Addendum 1, released October 21, 2010:
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
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.
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
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:
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.
Per Addendum 1, released October 21, 2010:
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.
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:
Comply
This is indicated in the RF Site Table in Section 7.01
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
This is indicated in the RF Site Table in Section 7.01
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.
Per Addendum 1, released October 21, 2010:
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.”
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
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.
Per Addendum 3, released November 19, 2010:
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.
Per Addendum 1, released October 21, 2010:
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.
Comply
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.
Per Addendum 1, released October 21, 2010:
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
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
Per Addendum 1, released October 21, 2010:
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.
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.
Per Addendum 1, released October 21, 2010:
Question:
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.
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:
Per Addendum 1, released October 21, 2010:
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
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
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
Comply
User Configuration 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.
Per Addendum 1, released October 21, 2010:
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.
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
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 exceeds the above stated requirements.
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
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
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
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.
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
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
Each generator package shall include a dual-fuel (natural/LP Gas fueled) four-cycle, or diesel
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.
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
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 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
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
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
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
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.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
D. Interior halo shall be bonded to an exterior, buried ground network using low
impedance copper conductors.
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
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
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:
Comply
a) ASTM, STP 479 Bunnister method.
Comply
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:
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. 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
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
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
1. This Specification includes concrete, forms, and steel reinforcement as used for:
Comply
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
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
1. Concrete Materials
a. Cement
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
Comply
f. Water Reducing Admixture
a. Ready-mixed Concrete
Comply
1) Concrete shall meet requirements of ASTM C94, and of materials and
proportions specified.
Comply
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
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
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
a. Float Finish
Comply
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
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
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
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
2. Quality Assurance
a. Applicable Standards
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
11.4.2 Requirements
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
Comply
b. Top and bottom selvage twisted and barbed.
Comply
c. Fabric fastenings of 9-gauge galvanized wire ties.
Comply
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
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
Comply
e. Barbed wire supporting arms
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
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) 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
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
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) Weave through the fabric and tie to each post with minimum 6 gauge
galvanized wire.
Comply
6) Fabric
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) 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.
Per Addendum 1, released October 21, 2010:
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
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
a. Applicable Standards
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
1. General
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) Establish and maintain by means of grade stakes, properly spaced so string lines
a. Placing
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
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
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
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.
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
A. Transmitter Equipment
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.);
Per Addendum 1, released October 21, 2010:
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
D. Dispatch Centers
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:
Per Addendum 1, released October 21, 2010:
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.
Question:
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.
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
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
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.
Per Addendum 1, released October 21, 2010:
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.
Per Addendum 2, released October 29, 2010:
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.
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.
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.
Per Addendum 1, released October 21, 2010:
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.
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.
Per Addendum 1, released October 21, 2010:
Question:
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,
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
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
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
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
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
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:
Microwave Related
Equipment
Console Equipment
Control Station
Equipment
%
Subscriber Equipment
Accessories
Spare Parts
Maintenance Agreement
Comply
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
delivered to their authorized sales agents, shall be as follows:
Console Equipment %
Subscriber Equipment %
Accessories %
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
delivered to their authorized sales agents, shall be as follows:
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
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:
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 Equipment $
Subtotal Labor $
Total Equipment/Labor $
Total Annual Maintenance $
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
Comply
Mid-Tier Portable
Comply
High-Tier Mobile Radio
Comply
Mid-Tier Mobile Radio
Comply
Low-Tier Mobile Radio
1. 800MHz Operation
2. Front-Mount Package
3. At least 120 modes/talk groups/channels
4. Two-Line alphanumeric display
5. Network/Radio Icons
6. IMBE vocoder
7. Programmable option buttons
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
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:
Comply
Comply
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
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
TOTAL 99 34 134
Public Safety 56 30 87
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
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
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.
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.
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.
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.
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.
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
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.
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.
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
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.
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
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.
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
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.
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.
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.
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
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.
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
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.
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.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-
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
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.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.
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 –
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.
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.
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.
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).
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
Router w/
CCGW
4W Analog
Lines Conventional Only Site
Resource Radio
Folders Resources
Patch &
Radio
Multi-Select
Resource
Folders
Auxiliary
Inputs/Outputs
Radio
Radio
Resources
Resource
Activity Log
Window
Status Bar
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.
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
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
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.
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.
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 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 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.
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.
Activity Log
Resource
Tile
List of Calls
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
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.
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.
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
Supported Configurations
The Motorola MCC7500 conventional channel gateway supports the following types
of analog conventional base stations.
♦ R1
♦ T1R1
♦ T1R1 w/Paging
♦ T2R2
♦ T4R4
Floyd County, Georgia
Project 25 Digital Public Safety Radio Network
RFP# 101216
December 16, 2010
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.
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.
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.
Floyd County, Georgia
Project 25 Digital Public Safety Radio Network
RFP# 101216
December 16, 2010
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.
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.
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.
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.
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.
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.
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
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
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
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,
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.
Security Management
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.
Fault Management
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.
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
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.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.
Customer
Network
Mobile radio
transmits audio
Gateway translates
digitized voice packets
into analog & re-transmits
as analog voice
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.
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.
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.
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
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.
Detection: Alarm on Manager Terminal.
Table 5-14: Failure of Single Base Station at an ASTRO 25 Simulcast or Repeater Site
The SMRS-650 3-Bay deployable trailer comes equipped with the following:
Generator
Trailer
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:
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).
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
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
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.
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.
Figure 5-26: The APX significantly improves voice intelligibility using Motorola’s Noise
Reduction Software
Figure 5-27: The APX line of radios is the first P25 multi-band radios in the public safety market.
Figure 5-28: Enhanced user interface provides intelligent lighting to significantly improve
legibility (APX 7000 example)
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.
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.
Figure 5-29: The APX Portable is the most advanced portable in our portfolio.
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.
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.
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
Figure 5-30: The APX has hard gold contacts molded into plastic to eliminate loose wires and
parts
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
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.
Figure 5-32: The XTS 2500 portable radio is the cost-effective choice
Programmable monitor
button
2 programmable side
buttons
Transmit LED indicator
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.
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.
Required Components
♦ PC to run the CPS software.
♦ Programming cable to connect PC with the subscriber unit.
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.
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.
Diagrams 5.1-1
This page left intentionally blank.
5.1-2 Diagrams
8 7 6 5 4 3 2 1
Primary/Back-up Site Router Links
J J
T1 Connections
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
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
Gig-T Ports
SFP Ports
CEN Switch
MOSCAD SNT
ST6000 Router
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
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
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
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
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
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
(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
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
SuperStack II SUPER
R
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
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
Lawrenceville, GA 30043
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
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-3
8 7 6 5 4 3 2 1
HP2610 Switch #1
CCGW #1
CCGW #2
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
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
Lawrenceville, GA 30043
B PROJECT:
Floyd MCC7500 Console System B
TITLE
C
Main & Backup Rack Layouts
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A Gary Brady A
A O 11/19/10 RLB ORIGINAL RELEASE
PROGRAM DRAWN
Gary Brady
CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION 11/19/10
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-4
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
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
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
C C
Networks & Enterprise
Systems Engineering
H
Lawrenceville, GA 30043
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
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
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
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION 11/08/2010 PRJ-xxx
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-5
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
TTA
H H
MOSCAD RTU
Unused until TDMA TTA
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
C C
Networks & Enterprise
Systems Engineering
H
Lawrenceville, GA 30043
G PROJECT:
F Floyd County, GA - ASTRO 25
B E 10 Channel Simulcast Sub-Site B
TITLE
D
C
SYSTEM DIAGRAM – Simulcast Remote RF
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
Gary J Brady Jr NONE B
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
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION 12/10/2010 PRJ-xxx
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-6
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
Networks & Enterprise
Systems Engineering
Lawrenceville, GA 30043
B PROJECT:
Floyd County, Georgia B
ESS Odd Chnls ESS Even Chnls ASTRO25 Project
TITLE
C
Mount Alto Prime/RF Site – Rack Layout Row 1
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Mt Alto with CS
PROGRAM DRAWN CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-7
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
D D
10 10 10
C 5 5 5
C
C
Mount Alto Prime/RF Site – Rack Layout Row 2
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Mt Alto with CS
PROGRAM DRAWN CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-8
8 7 6 5 4 3 2 1
J J
5 5
GGM Site Gateway S2500
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
Networks & Enterprise
Systems Engineering
Lawrenceville, GA 30043
B PROJECT:
Floyd County, Georgia B
ESS Odd Chnls ESS Even Chnls ASTRO25 Project
TITLE
C
Remote Simulcast RF Site – Rack Layout Row 1
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Final Design w/ CS
PROGRAM DRAWN CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-9
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
C
Remote Simulcast RF Site – Rack Layout Row 2
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A
A
A O 12/13/2010 G.Brady Changed to match Final Design w/ CS
PROGRAM DRAWN CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-10
8 7 6 5 4 3 2 1
J J
RX-A
Ethernet Microwave to
I Prime Site I
GGM8000 Site Gateway
R
TTA
H H
MOSCAD RTU
Unused until TDMA TTA
RMC TX
7' Schroff
Junction Panel
G 48 DI G
16 DO Site RMC/LNA “A”
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
Networks & Enterprise
Systems Engineering
H
Lawrenceville, GA 30043
G PROJECT:
F Floyd County, GA - ASTRO 25
B E 5 Channel ASTRO25 Site Repeater B
TITLE
D
C
SYSTEM DIAGRAM – RF Site Repeater
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
Gary J Brady Jr NONE B
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
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION 12/10/2010 PRJ-xxx
8 7 6 5 4 3 2 1
Motorola Confidential and Restricted 5.1-11
This page intentionally left blank.
J J
45
5
GGM Site Gateway S2500
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
Networks & Enterprise
Systems Engineering
Lawrenceville, GA 30043
B PROJECT:
Floyd County, Georgia B
ESS Even Chnls ASTRO25 Project
TITLE
C
Rocky Mtn ASTRO 25 Repeater RF Site – Rack Layout
B CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
A
½” = 1' A
A O 12/13/2010 G.Brady Changed to match Final Design
PROGRAM DRAWN CHECKED SHEET REV
O A
FILE DATE CODE IDENT DWG NO
REV DATE ENGNR DESCRIPTION
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-14
Taylors
1+1 Spur Link Ridge
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
Motorola Confidential, Proprietary and Trade Secret 5.1-15
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
C C
B B
Networks & Enterprise
Systems Engineering
Lawrenceville, GA 30043
PROJECT:
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
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
PROJECT:
B Floyd County Jail & Courthouse, Rome, Georgia B
800 MHz P25 Repeater System
TITLE
B
CONTRACT ENGINEER PROGRAM MGR SCALE SIZE
Gary Brady A
A
8 7 6 5 4 3 2 1
Motorola Confidential, Proprietary and Trade Secret 5.1-17
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
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:
In-Field Draft
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____
Floyd County, Georgia
Project 25 Digital Public Safety Radio Network
RFP# 101216
December 16, 2010
VERSION #1.240
Pass____ Fail____
Pass____ Fail____
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 1
RADIO-3 - TALKGROUP 1
RADIO-3 - SITE - SITE 1
VERSION #1.080
VERSION #1.060
Pass____ Fail____
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.
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
RADIO-3 - TALKGROUP 1
VERSION #1.090
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1 Pass____ Fail____
RADIO-3 - TALKGROUP 1
VERSION #1.150
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.
Pass____ Fail____
Pass____ Fail____
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
VERSION #1.070
Pass____ Fail____
Pass____ Fail____
VERSION #1.170
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.
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
RADIO-3 - EMERGENCY TG
Pass____ Fail____
* EMERGENCY TG is the talkgroup programmed for
emergency reverts.
VERSION #1.070
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 2
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 1
RADIO-3 - TALKGROUP 2
RADIO-3 - SITE - SITE 1
VERSION #1.140
Pass____ Fail____
VERSION #1.070
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
Pass____ Fail____
RADIO-3 - EMERGENCY TG
VERSION #1.050
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
VERSION #1.070
Pass____ Fail____
"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-1 - SITE - SITE 1
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____
VERSION #1.060
Pass____ Fail____
Pass____ Fail____
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
VERSION #1.080
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.
Pass____ Fail____
Pass____ Fail____
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
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
RADIO-3 - TALKGROUP 2
RADIO-4 - TALKGROUP 2
Pass____ Fail____
VERSION #1.150
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.
Pass____ Fail____
Floyd County, Georgia
Project 25 Digital Public Safety Radio Network
RFP# 101216
December 16, 2010
Pass____ Fail____
Pass____ Fail____
"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.
subscriber until the power is cycled or the talkgroup is
changed. Step 6. Set SITE 1 to be a non-valid site for
RADIO-2 through the UCM.
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 2
RADIO-3 - TALKGROUP 1
RADIO-3 - SITE - SITE 3 (SITE 2 if only 2 Sites)
Pass____ Fail____
VERSION #1.090
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
VERSION #1.250
MOBILE-1 - TALKGROUP 1
MOBILE-2 - TALKGROUP 2
MOBILE-3 - TALKGROUP 3
VERSION #1.040
Pass____ Fail____
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
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
RADIO-3 - TALKGROUP 2
RADIO-4 - TALKGROUP 2
Pass____ Fail____
VERSION #1.140
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 2
RADIO-2 - SITE - SITE 1 Pass____ Fail____
RADIO-3 - RANDOM (Not part of MG)
RADIO-3 - SITE - SITE 2
RADIO-4 - ATG 1
RADIO-4 - SITE - SITE 2
VERSION #1.160
VERSION #1.130
Pass____ Fail____
Pass____ Fail____
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.
Pass____ Fail____
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.
Pass____ Fail____
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.
Pass____ Fail____
VERSION #1.040
Pass____ Fail____
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.
Pass____ Fail____
VERSION #1.140
Pass____ Fail____
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.
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 2
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 1
RADIO-3 - TALKGROUP 2
RADIO-3 - SITE - SITE 1
VERSION #1.120
Pass____ Fail____
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-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 2
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.
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
SITE-1 - ZONE 1
CONSOLE-1 -TALKGROUP 1
CONSOLE-1 - SITE - CSITE 1
VERSION #1.030
Pass____ Fail____
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
RADIO-1 - CONVCH1
RADIO-2 - CONVCH1
VERSION #1.030
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 2
RADIO-2 - SITE - SITE 2
RADIO-3 - TALKGROUP 3
RADIO-3 - SITE - SITE 3
RADIO-4 - TALKGROUP 4
RADIO-4 - SITE - SITE 4
CONSOLE-1 - TALKGROUP 1, TALKGROUP 2,
TALKGROUP 3 and TALKGROUP 4
Pass____ Fail____
VERSION #1.090
Pass____ Fail____
VERSION #1.020
VERSION #1.020
Pass____ Fail____
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.
Pass____ Fail____
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
RADIO-1 - TALKGROUP 1
CONSOLE-1 - TALKGROUP 1
Pass____ Fail____
VERSION #1.070
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.
RADIO-1- CCH1
RADIO-2 - CCH2
CONSOLE-1 CCH1
CONSOLE-2 CCH2
VERSION #1.040
Pass____ Fail____
SETUP
CONSOLE-1 - CONVCH 1
VERSION #1.030
Pass____ Fail____
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
VERSION #1.030
Pass____ Fail____
Pass____ Fail____
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
Aux I/O 2 - pins 27,2
Aux I/O 3 - pins 28,3
Aux I/O 4 - pins 29,4
VERSION #1.010
Pass____ Fail____
SETUP
VERSION #1.030
VERSION #1.110
Pass____ Fail____
VERSION #1.000
Pass____ Fail____
VERSION #1.050
Pass____ Fail____
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)
RADIO-2 - SITE - CONVSITE 1
CONSOLE-1 - CONVCH1
CONSOLE-1 - SITE - CONSITE 1
VERSION #1.010
Pass____ Fail____
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.
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
CONSOLE-1 - TALKGROUP 1
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
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.
VERSION #1.020
Pass____ Fail____
VERSION #1.020
Pass____ Fail____
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.
Step 6. Initiate a wide area coded call from
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.
CONSOLE-1 - TALKGROUP 1
CONSOLE-2 - TALKGROUP 2
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
VERSION #1.020
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
TG-1 - Crypto Key - CKR1
SITE-1 - ZONE 1
CONSOLE-1 -TALKGROUP 1
CONSOLE-1 - SITE - CSITE 1
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 - TALKGROUP 1
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.
RADIO-4 - SITE - SITE 2
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____
1. DESCRIPTION
SETUP
SITE-1 - ZONE 1
CONSOLE-1 - TALKGROUP 1
CONSOLE-1 - TALKGROUP 2
CONSOLE-1 - SITE - CSITE-1
PATCH-1-TG-1-TALKGROUP 2
RADIO-2 - TALKGROUP 2
RADIO-2 - SITE- SITE-1
VERSION #1.040
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
CONSOLE-1 - TALKGROUP 1
VERSION #1.070
Pass____ Fail____
Pass____ Fail____
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-2 - TALKGROUP 2
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____
SETUP
RADIO-1 - CONVCH1
CCGW-1 - CONVCH1
CCGW-1 - SITE 1
CONSOLE-1 - CONVCH1
CONSOLE-1 - SITE - CSITE 1
VERSION #1.030
Pass____ Fail____
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.
Step 6. Initiate a wide area coded call from
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-3 - SITE - SITE 2
RADIO-4 - TALKGROUP 1 (Secure TX Mode)
RADIO-4 - SITE - SITE 2
CONSOLE-1 - TALKGROUP 1
CONSOLE-2 - TALKGROUP 2
TALKGROUP 1 Loaded with CKR1 Keys Pass____ Fail____
TALKGROUP 2 Loaded with CKR2 Keys
VERSION #1.100
VERSION #1.030
Pass____ Fail____
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.
VERSION #1.040
Pass____ Fail____
VERSION #1.050
Pass____ Fail____
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.
VERSION #1.080
Pass____ Fail____
VERSION #1.120
Pass____ Fail____
Pass____ Fail____
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 1
VERSION #1.090
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
SETUP
Pass____ Fail____
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 1
RADIO-3 - TALKGROUP 2
RADIO-3 - SITE - SITE 1
RADIO-4 - TALKGROUP 2
RADIO-4 - SITE - SITE 1
VERSION #1.040
Pass____ Fail____
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).
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
VERSION #1.000
Pass____ Fail____
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 2
VERSION #1.060
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
-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____
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.
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
Pass____ Fail____
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 1
RADIO-2 - SITE - SITE 1
RADIO-3 - TALKGROUP 2
RADIO-3 - SITE - SITE 2
RADIO-4 - TALKGROUP 2
RADIO-4 - SITE - SITE 2
VERSION #1.040
VERSION #1.050
Pass____ Fail____
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.
Pass____ Fail____
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.
Pass____ Fail____
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.
Pass____ Fail____
Pass____ Fail____
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.
Pass____ Fail____
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.
Pass____ Fail____
Note - Radios are not required to be locked to a Step 5. Initiate the Snapshot command for
specific site for this test. RADIO-1.
Pass____ Fail____
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.
VERSION #1.030
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.
Pass____ Fail____
Pass____ Fail____
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.
VERSION #1.060
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 - TALKGROUP 2
RADIO-3 - SITE - SITE 3 Pass____ Fail____
RADIO-4 - TALKGROUP 2
RADIO-4 - SITE - SITE 4
VERSION #1.060
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
Pass____ Fail____
* Configure RADIO-1 in the manager to use a
particular status set.
VERSION #1.020
Pass____ Fail____
No prior setup is required for this test. Step 8. Close the report window.
Pass____ Fail____
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.
VERSION #1.060
Pass____ Fail____
SETUP
Pass____ Fail____
VERSION #1.050
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.
Pass____ Fail____
VERSION #1.060
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-2 - TALKGROUP 1
VERSION #1.050
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
RADIO-1 - TALKGROUP 1
VERSION #1.110
Pass____ Fail____
Pass____ Fail____
SETUP
No set up required.
VERSION #1.030
Pass____ Fail____
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
VERSION #1.060
Pass____ Fail____
VERSION #1.000
Pass____ Fail____
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____
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.
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 2
RADIO-2 - SITE - SITE 1
NMclient01 - UEM session up and running.
Pass____ Fail____
VERSION #1.070
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.
VERSION #1.110
Pass____ Fail____
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.
Pass____ Fail____
Pass____ Fail____
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
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
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____
Pass____ Fail____
SETUP
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.
VERSION #1.060
Pass____ Fail____
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
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.030
Pass____ Fail____
SETUP
VERSION #1.060
Pass____ Fail____
SETUP
VERSION #1.080
Pass____ Fail____
SETUP
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
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____
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
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"
Pass____ Fail____
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).
Step 5. Acknowledge the alarm on either
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____
SETUP
Pass____ Fail____
Pass____ Fail____
SETUP
VERSION #1.040
Pass____ Fail____
SETUP
VERSION #1.030
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
Pass____ Fail____
SETUP
VERSION #1.010
Pass____ Fail____
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____
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.
VERSION #1.040
Pass____ Fail____
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____
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.
Pass____ Fail____
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____
VERSION #1.040
Pass____ Fail____
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.
RADIO-1 - TALKGROUP 1
RADIO-1 - SITE - SITE 1
RADIO-2 - TALKGROUP 2
RADIO-2 - SITE - SITE 1
VERSION #1.040
Pass____ Fail____
Pass____ Fail____
* 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____
VERSION #1.030
Pass____ Fail____
NOTE: This feature only works on a multi-site system. Step 4. Place the site the radios are
affiliated to into Site Trunking.
VERSION #1.120
VERSION #1.030
Pass____ Fail____
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.
Pass____ Fail____
VERSION #1.030
Pass____ Fail____
CONSOLE-1 - CONVCH1
CONSOLE-1 - SITE - CONSITE 1
CONSOLE-2 - CONVCH1
CONSOLE-2 - SITE - CONSITE 1
CCGW-1 - CONVCH1
CCGW-1 - SITE - CONVSITE 1
VERSION #1.050
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
VERSION #1.030
CCGW-1 - CONVCH1
CCGW-1 - SITE - CONVSITE 1
VERSION #1.050
Pass____ Fail____
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
MAIN - CONVCH1
ALTERNATE - CONVCH2
VERSION #1.020
SETUP
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
CCGW-1 - CONVCH1
CCGW-1 - SITE - CONVSITE-1
SETUP
SYSTEM 2
RADIO-4 - TALKGROUP 4 @ SITE 1
RADIO-5 - TALKGROUP 4 @ SITE 2
RADIO-6 - TALKGROUP 3 @ SITE 1
CONSOLE-2 - TALKGROUP 4
VERSION #1.010
SYSTEM 1
RADIO-1 - TALKGROUP 1 @ SITE 1
RADIO-2 - TALKGROUP 1 @ SITE 2
RADIO-3 - TALKGROUP 2 @ SITE 1
SYSTEM 2
RADIO-4 - TALKGROUP 3 @ SITE 1
RADIO-5 - TALKGROUP 3 @ SITE 2 Pass____ Fail____
RADIO-6 - TALKGROUP 4 @ SITE 1
VERSION #1.010
SYSTEM 2
RADIO-4 - TALKGROUP 3
RADIO-5 - TALKGROUP 3
RADIO-6 - TALKGROUP 4
CONSOLE-2 TALKGROUP 4
SYSTEM 1
RADIO-1 - TALKGROUP 1 @ SITE 1
RADIO-2 - TALKGROUP 1 @ SITE 2
RADIO-3 - TALKGROUP 2 @ SITE 1
CONSOLE-1 - TALKGROUP 1
VERSION #1.010
SETUP
SYSTEM 1
RADIO-1 - TALKGROUP 2
RADIO-2 - TALKGROUP 2
RADIO-3 - TALKGROUP 1
CONSOLE-1 TALKGROUP 2
SYSTEM 2
RADIO-4 - TALKGROUP 4 Pass____ Fail____
RADIO-5 - TALKGROUP 4
RADIO-6 - TALKGROUP 3
CONSOLE-2 - TALKGROUP 4
VERSION #2.000
SETUP
RADIO-1 – TALKGROUP 1
RADIO-2 – TALKGROUP 1
RADIO-3 – 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
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-2 – TALKGROUP 1
RADIO-3 – AG1
Note:
TALKGROUP 1 is configured in wait mode
Pass____ Fail____
TALKGROUP 1 is assigned to multigroup MG1
VERSION #1.030
By their signatures below, the following witnesses certify they have observed the In-Field System
Acceptance Test Procedures.
Signatures
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.
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.
Table 7-4: Net Target Signal Strength Indication – Portable in Swivel Case at Hip
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:
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.
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.
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
APX6000 Portable with Halfwave Antenna In 15dB Building
APX6000 Portable with Halfwave Antenna In 20dB Building
APX6000 Portable with Halfwave Antenna In 25dB 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:
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring
Rocky Mountain
Shannon AT&T
Fouche Gap
Blossom Hill
Mt Alto
Hillindale
Leonard Rd
Cave Spring
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
Rocky Mtn
Shannon AT&T
Fouche Gap
Blossom HIll
Mt Alto
Hillindale
Leonard Rd
Cave Spring
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)
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-4c
Floyd County
Portable In 6 dB Building
7-Site Simulcast + Rocky Mtn ASR
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)
Scale 1/260193
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-4d
Floyd County
Portable in 15 dB Building
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)
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)
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
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-5c
Floyd County
Portable In 15 dB Building
7-Site Simulcast + Rocky Mtn ASR
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)
Scale 1/260193
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-5d
Floyd County
Portable in 20 dB Building
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)
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)
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
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-6c
Floyd County
Portable In 20 dB Building
7-Site Simulcast + Rocky Mtn ASR
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)
Scale 1/260193
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-6d
Floyd County
Portable in 25 dB Building
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)
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)
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
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-7c
Floyd County
Portable In 25 dB Building
7-Site Simulcast + Rocky Mtn ASR
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)
Scale 1/260193
Monday, December 13 2010 3.40 Build 3671 Job Id : 2757711302.8.000.1.14
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-7d
Floyd County
Portable On-Street
Blossom Hill
Blossom Hill
95% AREA BLOSSOM HILL OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Blossom Hill
95% AREA BLOSSOM HILL INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Cave Spring
95% AREA CAVE SPRING OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Cave Spring
95% AREA CAVE SPRING INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Fouche Gap
95% AREA FOUCHE GAP OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Fouche Gap
95% AREA FOUCHE GAP INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Hillindale
Hillindale
Leonard Rd
Leonard Rd
Mt Alto
Mt Alto
Rocky Mountain
95% AREA ROCKY MOUNTAIN OUTRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Rocky Mountain
95% AREA ROCKY MOUNTAIN INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
Shannon AT&T
95% AREA SHANNON AT&T OUTRELIABILITY APX6000 PORTABLE HALFWAVE SWIVELCASE WALKING CH 6
Shannon AT&T
95% AREA SHANNON AT&T INRELIABILITY APX6000 W HALFWAVE ANTENNA IN SWIVELCASE WALKING CH 6
ITAC
Operator C00145
Monday, December 13 2010 3.40 Build 3671 Job Id : 231221775.1.000.1.12
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-16a
Floyd County
Mobile
800 MHz Mutual Aid System
5 Channels
ITAC
Operator C00145
Monday, December 13 2010 3.40 Build 3671 Job Id : 231221775.1.000.1.12
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-16b
Floyd County
Portable
800 MHz Mutual Aid System
5 Channels
ITAC
95% AREA MSE APX6000 HALFWAVE HIP OUTSIDE 3W OUTBOUND OVERLAY (BEST OF)
Operator C00145
Monday, December 13 2010 3.40 Build 3671 Job Id : 231221775.1.000.1.12
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-17a
Floyd County
Portable
800 MHz Mutual Aid System
5 Channels
ITAC
95% AREA MSE APX6000 HALFWAVE HIP OUTSIDE 3W INBOUND OVERLAY (BEST OF)
Operator C00145
Monday, December 13 2010 3.40 Build 3671 Job Id : 231221775.1.000.1.12
Portion(s) Of GIS Source Data Provided By ESRI, Inc.
Motorola Confidential and Restricted 8.1-17b
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
APX6000 Portable with Halfwave Antenna In 15dB Building
APX6000 Portable with Halfwave Antenna In 20dB Building
APX6000 Portable with Halfwave Antenna In 25dB 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:
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.
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:
Any additional concerns of either Floyd County or Motorola will be added to the
general agenda.
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.
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
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.
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.
Motorola will install the following equipment at the Mount Alto Prime Site:
♦ Prime site controllers
♦ Comparators
♦ GPS Trak unit
♦ MOSCAD NFM RTU
♦ Associated switches and routers
♦ (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
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:
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)
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.
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.
• 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.
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.
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.
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.
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.
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.
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.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.
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
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 RFP# 101216
December 16, 2010
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).
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
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.
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
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
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 35-foot deep soil boring test at tower location and prepare
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.
♦ 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.
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
♦ Application of regionally specific soil sterilant
♦ Provide, install and connectorize alarm contacts for compound gates per
specifications
♦ Dewatering process as required
♦ Disposal of spoils
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
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
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).
♦ 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).
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.
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
Motorola Will:
Site Engineering
♦ Prepare site construction drawings showing the layout of various new and
existing site components.
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.
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
Tower Work
♦ Construct tower foundations for a guyed tower (base and three anchors) including
excavation, rebar and concrete (not to exceed 53 cubic yards).Rock coring and
hazardous material removal have not been included and will be considered extra.
♦ Erect new 350-foot guyed tower with strobe lighting.
♦ Dismantle and remove the existing 160 ft. guyed tower structure.
♦ Ground each of the 3 guy anchors using galvanized steel ground rods.
Miscellaneous Work
♦ Cut, load and haul existing CMU shelter to a certified disposal facility.
♦ Application of regionally specific soil sterilant
♦ Provide, install and connectorize alarm contacts for compound gates per
specifications
♦ Dewatering process as required
♦ Disposal of spoils
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
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.
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 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).
♦ 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 100
cubic yards).
♦ Provide minimal grading in a 15-foot x 30-foot compound around each of 3 guy
anchors to allow anchor installation.
♦ 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).
♦ Supply and install gravel surfacing to a depth of 6 inches around each of 3 guy
anchors underlain with geotextile fabric.
♦ Provide silt fence around the compound to control soil erosion (not to exceed 200
linear feet).
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
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.
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.
Completion Criteria
♦ Site development completed and approved by Floyd County, GA
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.
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 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).
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
Tower Work
♦ Construct tower foundations for a guyed tower (base and three anchors) including
excavation, rebar and concrete (not to exceed 33 cubic yards).Rock coring,
Note: Please see MACTEC tower structural report located at the end
of this document.
Miscellaneous Work
♦ Application of regionally specific soil sterilant
♦ Provide, install and connectorize alarm contacts for compound gates per
specifications
♦ General Repairs for Generator Room
♦ Wall boring for utility penetration
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.).
♦ 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 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
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.
Miscellaneous Work
♦ DC Connectivity
♦ Install HVAC Compressor, Air Handler Thermostat and condensate drain system
in new equipment room
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.
♦ 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.
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
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 tower. Utility transformer,
transformer upgrades, line, or pole extensions have not been included.
♦ 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 or 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 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.
Completion Criteria
♦ Site development completed and approved by Floyd County, GA
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.).
♦ 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 a boundary and topographic survey for the property on which the
communication site is located or will be located.
♦ 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
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 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.
Site Preparation
♦ 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.
Motorola Will:
Site Engineering
♦ 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
by the proposed construction activity. This does not include the additional field
investigations to document site conditions if it is determined that the proposed
Site Preparation
♦ 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.
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.
♦ 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.
Completion Criteria
♦ Site development completed and approved by Floyd County, GA
Motorola Will:
Site Engineering
♦ 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
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.
Site Preparation
♦ 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.
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 installation effort and on an ongoing basis.
♦ Pay for application fees, taxes and recurring payments for lease/ownership of the
property.
♦ Provide personnel to observe progress and testing of site equipment according to
the schedule provided by Motorola.
♦ Provide a right of entry letter from the site owner for Motorola to conduct field
investigations.
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, electrical, Telco] will be borne by the Customer or site owner.
♦ Pricing has been based on National codes such IBC or BOCA. Local codes or
jurisdictional requirements have not been considered in this proposal.
♦ 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 crane access.
Completion Criteria
♦ Site development completed and approved by Floyd County, GA
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,
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.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.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.
** 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.
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.
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.
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.
Construction Management
♦ Review civil design drawings
♦ Prepare construction bid packages
♦ Prepare construction closeout binders
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
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
Metropolitan Comm
Transcomm
Savannah Comm
Columbus Comm
Macon Comm
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
GA-10Q123A 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
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
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
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
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
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-4 Prepare, Review and Approve Site Sketch 7 6/8/2011 6/16/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-4 New Tower Zoning App and Approval 70 7/15/2011 10/20/2011
Task CivNEPA-4 NEPA/SHPO Studies and Approvals 70 6/21/2011 9/26/2011
Task CivGEO-4 GeoTech Testing and Report 8 7/5/2011 7/14/2011
Task MWPathSur-4 MW Path Studies 3 7/15/2011 7/19/2011
Task BldDes-4 Design Tower and Building 6 7/22/2011 7/29/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-4 Land Disturbance Permit App and Approval 5 11/11/2011 11/17/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-4 Mobilization 1 12/6/2011 12/6/2011
Task CivSitPrep-4-5 Locate Utilities 1 12/9/2011 12/9/2011
Task CivSitPrep-4-6 Construction Staking 2 12/12/2011 12/13/2011
Task CivSitPrep-4-7 Heavy Clearing and Grubbing 14 12/7/2011 12/26/2011
Task CivSitPrep-4-8 Compound Grading and Silt Fencing 3 12/23/2011 12/27/2011
Task CivSitPrep-4-9 Pickup Meter and Install Meterboard 2 12/28/2011 12/29/2011
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 TowCnstShip-4 Ship Anchor Bolts and Base Plate to Site 4 12/14/2011 12/19/2011
Task TowCnstFndn-4 Drill, Rebar, and Pour Drilled Pier Foundation 5 12/28/2011 1/3/2012
Task TowCnstFndn-4-4 Foundation Inspection / Concrete Testing 1 1/2/2012 1/2/2012
Task TowCnstGrd-4 Tower Grounding 1 1/2/2012 1/2/2012
Task TowCnstShip-4-4 Ship Forms, Backfill, and Compaction 1 1/9/2012 1/9/2012
Task TowCnstShip-4-5 Ship Tower to Site 4 1/9/2012 1/12/2012
Task TowCnstFAA-4 Notify FAA of Impending Tower Construction 1 1/10/2012 1/10/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 TowCnstFAA-4-4 Notify FAA of Tower Completion 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 BldUtilHU-4 Trench and Install Underground Power Conduits 5 1/10/2012 1/16/2012
Task BldGrnd-4 Trench and Install Grounding 2 1/17/2012 1/18/2012
Task BldGrnd-4-4 Grounding Inspection 1 2/7/2012 2/7/2012
Task BldUtilHU-4-4 Conduit Inspection and Backfill 1 1/17/2012 1/17/2012
Task BldFndCnst-4 Excavate, Form, and Rebar Shelter Foundations 3 1/19/2012 1/23/2012
Task BldFndCnst-4-4 Excavate, Form, and Rebar Fuel Tank Foundation 1 1/19/2012 1/19/2012
Task BldFndCnst-4-5 Excavate, Form, and Rebar Generator Foundation 1 1/20/2012 1/20/2012
Task BldFndInsp-4 Foundation Inspection, Concrete Pour and Testing 1 1/24/2012 1/24/2012
Task BldConDel-4 Ship Shelter to the Site 2 2/1/2012 2/2/2012
Task BldConDel-4-4 Offload and Install Equipment Shelter 2 2/3/2012 2/6/2012
Task BldConDel-4-5 Offload and Install Generator 2 2/3/2012 2/6/2012
Task BldConDel-4-6 Install Fuel Tank and Piping 2 2/9/2012 2/10/2012
Task BldConDel-4-7 Piping Inspection, Leakage Test, and Backfill 3 2/13/2012 2/15/2012
Task BldExtCon-4 Cabling and Hookup Power System to Shelter 3 2/16/2012 2/20/2012
12/10/10 3/13
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
Task BldElecInsp-4 Building/Electrical Inspection 1 2/21/2012 2/21/2012
Task BldGrnd-4-5 Install Icebridge from Shelter to Tower 2 2/16/2012 2/17/2012
Task BldCln-4 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldFnc-4 Fencing of Tower Compound 3 3/6/2012 3/8/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 BldWrkCom-4 Line Termination and Sweep Test 1 2/22/2012 2/22/2012
Task BldWrkCom-4-4 Generator Startup / Test Power System 1 2/27/2012 2/27/2012
Task BldWrkCom-4-5 Grounding Test of the Site 1 3/12/2012 3/12/2012
Task BldWrkCom-4-6 Startup / Test Shelter Power System 1 3/1/2012 3/1/2012
Task BldWrkCom-4-7 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/2/2012 3/2/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
Task CivSur-7 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-7-7 Prepare, Review and Approve Site Sketch 7 6/8/2011 6/16/2011
Task CivSur-7-8 Site Survey and Mapping 7 6/22/2011 6/30/2011
Task CivArch-7 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task CivArch-7-7 New Tower Zoning App and Approval 70 7/15/2011 10/20/2011
Task CivNEPA-7 NEPA/SHPO Studies and Approvals 70 6/21/2011 9/26/2011
Task CivGEO-7 GeoTech Testing and Report 8 7/5/2011 7/14/2011
Task MWPathSur-7 MW Path Studies 3 7/15/2011 7/19/2011
Task BldDes-7 Design Tower and Building 6 7/22/2011 7/29/2011
Task CivArch-7-8 Final Approval of Site Drawings by County 12 10/21/2011 11/7/2011
Task CivSitPerm-7 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-7-7 Land Disturbance Permit App and Approval 5 11/11/2011 11/17/2011
Task CivSitPerm-7-8 Electrical Permit App and Approval 10 11/11/2011 11/24/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
Task CivSitPrep-7-7 Mobilization 1 12/6/2011 12/6/2011
Task CivSitPrep-7-8 Locate Utilities 1 12/9/2011 12/9/2011
Task CivSitPrep-7-9 Construction Staking 2 12/12/2011 12/13/2011
Task CivSitPrep-7-10 Heavy Clearing and Grubbing 14 12/7/2011 12/26/2011
Task CivSitPrep-7-11 Compound Grading and Silt Fencing 3 12/23/2011 12/27/2011
Task CivSitPrep-7-12 Pickup Meter and Install Meterboard 2 12/28/2011 12/29/2011
Task CivSitPrep-7-13 Utility Hookup to the Site by Electric Co 5 12/30/2011 1/5/2012
Activity TowConst-7 Tower Construction - Fouche Gap 31 12/14/2011 1/25/2012
Task TowCnstShip-7 Ship Anchor Bolts and Base Plate to Site 4 12/14/2011 12/19/2011
Task TowCnstFndn-7 Drill, Rebar, and Pour Drilled Pier Foundation 5 12/28/2011 1/3/2012
Task TowCnstFndn-7-7 Foundation Inspection / Concrete Testing 1 1/2/2012 1/2/2012
Task TowCnstGrd-7 Tower Grounding 1 1/2/2012 1/2/2012
Task TowCnstShip-7-7 Ship Forms, Backfill, and Compaction 1 1/9/2012 1/9/2012
Task TowCnstShip-7-8 Ship Tower to Site 4 1/9/2012 1/12/2012
Task TowCnstFAA-7 Notify FAA of Impending Tower Construction 1 1/10/2012 1/10/2012
Task TowAssem-7 Tower Assembly and Stacking 4 1/16/2012 1/19/2012
Task TowAssem-7-7 Tower Plumbness Testing 1 1/20/2012 1/20/2012
Task TowCnstFAA-7-7 Notify FAA of Tower Completion 1 1/20/2012 1/20/2012
Task AntRxInv 7 Ship Antennas, Lines, and Accessories to the Site 5 1/10/2012 1/16/2012
Task AntRxInv 7-7 Install Antennas and Lines 4 1/20/2012 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
Task BldUtilHU-7 Trench and Install Underground Power Conduits 5 1/10/2012 1/16/2012
12/10/10 4/13
FFloyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
Task BldGrnd-7 Trench and Install Grounding 2 1/17/2012 1/18/2012
Task BldGrnd-7-7 Grounding Inspection 1 1/19/2012 1/19/2012
Task BldUtilHU-7-7 Conduit Inspection and Backfill 1 1/17/2012 1/17/2012
Task BldFndCnst-7 Excavate, Form, and Rebar Shelter Foundations 3 1/19/2012 1/23/2012
Task BldFndCnst-7-7 Excavate, Form, and Rebar Fuel Tank Foundation 1 1/19/2012 1/19/2012
Task BldFndCnst-7-8 Excavate, Form, and Rebar Generator Foundation 1 1/20/2012 1/20/2012
Task BldFndInsp-7 Foundation Inspection, Concrete Pour and Testing 1 1/24/2012 1/24/2012
Task BldConDel-7 Ship Shelter to the Site 2 2/1/2012 2/2/2012
Task BldConDel-7-7 Offload and Install Equipment Shelter 2 2/3/2012 2/6/2012
Task BldConDel-7-8 Offload and Install Generator 2 2/3/2012 2/6/2012
Task BldConDel-7-9 Install Fuel Tank and Piping 2 2/9/2012 2/10/2012
Task BldConDel-7-10 Piping Inspection, Leakage Test, and Backfill 3 2/13/2012 2/15/2012
Task BldExtCon-7 Cabling and Hookup Power System to Shelter 3 2/16/2012 2/20/2012
Task BldElecInsp-7 Building/Electrical Inspection 1 2/21/2012 2/21/2012
Task BldGrnd-7-8 Install Icebridge from Shelter to Tower 2 2/16/2012 2/17/2012
Task BldCln-7 Finish Grade and Gravel Compund 3 2/28/2012 3/1/2012
Task BldFnc-7 Fencing of Tower Compound 3 3/6/2012 3/8/2012
Task BldGrnd-7-9 Complete Grounding Connections 1 3/9/2012 3/9/2012
Task BldCln-7-7 Site Touchup and Restoration 2 3/12/2012 3/13/2012
Task BldWrkCom-7 Line Termination and Sweep Test 1 2/22/2012 2/22/2012
Task BldWrkCom-7-7 Generator Startup / Test Power System 1 2/27/2012 2/27/2012
Task BldWrkCom-7-8 Grounding Test of the Site 1 3/12/2012 3/12/2012
Task BldWrkCom-7-9 Startup / Test Shelter Power System 1 3/1/2012 3/1/2012
Task BldWrkCom-7-10 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/2/2012 3/2/2012
Task BldPunRes-7 Punch List with Floyd County 1 3/14/2012 3/14/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
Task CivSur-3 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-3-3 Prepare, Review and Approve Site Sketch 7 6/8/2011 6/16/2011
Task CivSur-3-4 Site Survey and Mapping 7 6/22/2011 6/30/2011
Task CivArch-3 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task CivArch-3-3 New Tower Zoning App and Approval 70 7/15/2011 10/20/2011
Task CivNEPA-3 NEPA/SHPO Studies and Approvals 70 6/21/2011 9/26/2011
Task CivGEO-3 GeoTech Testing and Report 8 7/5/2011 7/14/2011
Task MWPathSur-3 MW Path Studies 3 7/15/2011 7/19/2011
Task BldDes-3 Design Tower and Building 6 7/22/2011 7/29/2011
Task CivArch-3-4 Final Approval of Site Drawings by County 12 10/21/2011 11/7/2011
Task CivSitPerm-3 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-3-3 Land Disturbance Permit App and Approval 5 11/11/2011 11/17/2011
Task CivSitPerm-3-4 Electrical Permit App and Approval 10 11/11/2011 11/24/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-3 Mobilization 1 12/6/2011 12/6/2011
Task CivSitPrep-3-4 Locate Utilities 1 12/9/2011 12/9/2011
Task CivSitPrep-3-5 Construction Staking 2 12/12/2011 12/13/2011
Task CivSitPrep-3-6 Light Clearing and Grubbing 1 12/7/2011 12/7/2011
Task CivSitPrep-3-7 Compound Grading and Silt Fencing 3 12/6/2011 12/8/2011
Task CivSitPrep-3-8 Pickup Meter and Install Meterboard 2 12/9/2011 12/12/2011
Task CivSitPrep-3-9 Utility Hookup to the Site by Electric Co 5 12/13/2011 12/19/2011
Activity TowConst-3 Tower Construction - Hillindale 31 11/25/2011 1/6/2012
Task TowCnstShip-3 Ship Anchor Bolts and Base Plate to Site 4 11/25/2011 11/30/2011
Task TowCnstFndn-3 Drill, Rebar, and Pour Drilled Pier Foundation 5 12/9/2011 12/15/2011
12/10/10 5/13
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
Task TowCnstFndn-3-3 Foundation Inspection / Concrete Testing 1 12/14/2011 12/14/2011
Task TowCnstGrd-3 Tower Grounding 1 12/14/2011 12/14/2011
Task TowCnstShip-3-3 Ship Forms, Backfill, and Compaction 1 12/21/2011 12/21/2011
Task TowCnstShip-3-4 Ship Tower to Site 4 12/21/2011 12/26/2011
Task TowCnstFAA-3 Notify FAA of Impending Tower Construction 1 12/22/2011 12/22/2011
Task TowAssem-3 Tower Assembly and Stacking 4 12/28/2011 1/2/2012
Task TowAssem-3-3 Tower Plumbness Testing 1 1/3/2012 1/3/2012
Task TowCnstFAA-3-3 Notify FAA of Tower Completion 1 1/3/2012 1/3/2012
Task AntRxInv 3 Ship Antennas, Lines, and Accessories to the Site 5 12/22/2011 12/28/2011
Task AntRxInv 3-3 Install Antennas and Lines 4 1/3/2012 1/6/2012
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 BldUtilHU-3 Trench and Install Underground Power Conduits 5 12/22/2011 12/28/2011
Task BldGrnd-3-0 Trench and Install Grounding 2 12/29/2011 12/30/2011
Task BldGrnd-3-1 Grounding Inspection 1 1/2/2012 1/2/2012
Task BldUtilHU-3-3 Conduit Inspection and Backfill 1 12/29/2011 12/29/2011
Task BldFndCnst-3 Excavate, Form, and Rebar Shelter Foundations 3 1/2/2012 1/4/2012
Task BldFndCnst-3-3 Excavate, Form, and Rebar Fuel Tank Foundation 1 1/2/2012 1/2/2012
Task BldFndCnst-3-4 Excavate, Form, and Rebar Generator Foundation 1 1/3/2012 1/3/2012
Task BldFndInsp-3 Foundation Inspection, Concrete Pour and Testing 1 1/5/2012 1/5/2012
Task BldConDel-3 Ship Shelter to the Site 2 2/1/2012 2/2/2012
Task BldConDel-3-3 Offload and Install Equipment Shelter 2 2/3/2012 2/6/2012
Task BldConDel-3-4 Offload and Install Generator 2 2/3/2012 2/6/2012
Task BldConDel-3-5 Install Fuel Tank and Piping 2 2/9/2012 2/10/2012
Task BldConDel-3-6 Piping Inspection, Leakage Test, and Backfill 3 2/13/2012 2/15/2012
Task BldExtCon-3 Cabling and Hookup Power System to Shelter 3 2/16/2012 2/20/2012
Task BldElecInsp-3 Building/Electrical Inspection 1 2/21/2012 2/21/2012
Task BldGrnd-3-2 Install Icebridge from Shelter to Tower 2 2/16/2012 2/17/2012
Task BldCln-3 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldFnc-3 Fencing of Tower Compound 3 3/6/2012 3/8/2012
Task BldGrnd-3-3 Complete Grounding Connections 1 3/9/2012 3/9/2012
Task BldCln-3-3 Site Touchup and Restoration 2 3/12/2012 3/13/2012
Task BldWrkCom-3 Line Termination and Sweep Test 1 2/22/2012 2/22/2012
Task BldWrkCom-3-3 Generator Startup / Test Power System 1 2/27/2012 2/27/2012
Task BldWrkCom-3-4 Grounding Test of the Site 1 3/12/2012 3/12/2012
Task BldWrkCom-3-5 Startup / Test Shelter Power System 1 3/1/2012 3/1/2012
Task BldWrkCom-3-6 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/2/2012 3/2/2012
Task BldPunRes-3 Punch List with Floyd County 1 3/14/2012 3/14/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
Task CivSur-5 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-5-5 Prepare, Review and Approve Site Sketch 7 6/8/2011 6/16/2011
Task CivSur-5-6 Site Survey and Mapping 7 6/22/2011 6/30/2011
Task CivArch-5 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task CivArch-5-5 New Tower Zoning App and Approval 70 7/15/2011 10/20/2011
Task CivNEPA-5 NEPA/SHPO Studies and Approvals 70 6/21/2011 9/26/2011
Task CivGEO-5 GeoTech Testing and Report 8 7/5/2011 7/14/2011
Task MWPathSur-5 MW Path Studies 3 7/15/2011 7/19/2011
Task BldDes-5 Design Tower and Building 6 7/22/2011 7/29/2011
Task CivArch-5-6 Final Approval of Site Drawings by County 12 10/21/2011 11/7/2011
Task CivSitPerm-5 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-5-5 Land Disturbance Permit App and Approval 5 11/11/2011 11/17/2011
12/10/10 6/13
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
Task CivSitPerm-5-6 Electrical Permit App and Approval 10 11/11/2011 11/24/2011
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
Task CivSitPrep-5-5 Mobilization 1 12/6/2011 12/6/2011
Task CivSitPrep-5-6 Locate Utilities 1 12/9/2011 12/9/2011
Task CivSitPrep-5-7 Construction Staking 2 12/12/2011 12/13/2011
Task CivSitPrep-5-8 Light Clearing and Grubbing 1 12/7/2011 12/7/2011
Task CivSitPrep-5-9 Compound Grading and Silt Fencing 3 12/6/2011 12/8/2011
Task CivSitPrep-5-10 Pickup Meter and Install Meterboard 2 12/9/2011 12/12/2011
Task CivSitPrep-5-11 Utility Hookup to the Site by Electric Co 5 12/13/2011 12/19/2011
Activity TowConst-5 Tower Construction - Cave Springs 31 11/25/2011 1/6/2012
Task TowCnstShip-5 Ship Anchor Bolts and Base Plate to Site 4 11/25/2011 11/30/2011
Task TowCnstFndn-5 Drill, Rebar, and Pour Drilled Pier Foundation 5 12/9/2011 12/15/2011
Task TowCnstFndn-5-5 Foundation Inspection / Concrete Testing 1 12/14/2011 12/14/2011
Task TowCnstGrd-5 Tower Grounding 1 12/14/2011 12/14/2011
Task TowCnstShip-5-5 Ship Forms, Backfill, and Compaction 1 12/21/2011 12/21/2011
Task TowCnstShip-5-6 Ship Tower to Site 4 12/21/2011 12/26/2011
Task TowCnstFAA-5 Notify FAA of Impending Tower Construction 1 12/22/2011 12/22/2011
Task TowAssem-5 Tower Assembly and Stacking 4 12/28/2011 1/2/2012
Task TowAssem-5-5 Tower Plumbness Testing 1 1/3/2012 1/3/2012
Task TowCnstFAA-5-5 Notify FAA of Tower Completion 1 1/3/2012 1/3/2012
Task AntRxInv 5 Ship Antennas, Lines, and Accessories to the Site 5 12/22/2011 12/28/2011
Task AntRxInv 5-5 Install Antennas and Lines 4 1/3/2012 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 BldUtilHU-5 Trench and Install Underground Power Conduits 5 12/22/2011 12/28/2011
Task BldGrnd-5-5 Trench and Install Grounding 2 12/29/2011 12/30/2011
Task BldGrnd-5-6 Grounding Inspection 1 1/2/2012 1/2/2012
Task BldUtilHU-5-5 Conduit Inspection and Backfill 1 12/29/2011 12/29/2011
Task BldFndCnst-5 Excavate, Form, and Rebar Shelter Foundations 3 1/2/2012 1/4/2012
Task BldFndCnst-5-5 Excavate, Form, and Rebar Fuel Tank Foundation 1 1/2/2012 1/2/2012
Task BldFndCnst-5-6 Excavate, Form, and Rebar Generator Foundation 1 1/3/2012 1/3/2012
Task BldFndInsp-5 Foundation Inspection, Concrete Pour and Testing 1 1/5/2012 1/5/2012
Task BldConDel-5 Ship Shelter to the Site 2 2/1/2012 2/2/2012
Task BldConDel-5-5 Offload and Install Equipment Shelter 2 2/3/2012 2/6/2012
Task BldConDel-5-6 Offload and Install Generator 2 2/3/2012 2/6/2012
Task BldConDel-5-7 Install Fuel Tank and Piping 2 2/9/2012 2/10/2012
Task BldConDel-5-8 Piping Inspection, Leakage Test, and Backfill 3 2/13/2012 2/15/2012
Task BldExtCon-5 Cabling and Hookup Power System to Shelter 3 2/16/2012 2/20/2012
Task BldElecInsp-5 Building/Electrical Inspection 1 2/21/2012 2/21/2012
Task BldGrnd-5-7 Install Icebridge from Shelter to Tower 2 2/16/2012 2/17/2012
Task BldCln-5-5 Finish Grade and Gravel Compound 3 2/28/2012 3/1/2012
Task BldFnc-5 Fencing of Tower Compound 3 3/6/2012 3/8/2012
Task BldGrnd-5 Complete Grounding Connections 1 3/9/2012 3/9/2012
Task BldCln-5 Site Touchup and Restoration 2 3/12/2012 3/13/2012
Task BldWrkCom-5-8 Line Termination and Sweep Test 1 2/22/2012 2/22/2012
Task BldWrkCom-5-7 Generator Startup / Test Power System 1 2/27/2012 2/27/2012
Task BldWrkCom-5-6 Grounding Test of the Site 1 3/12/2012 3/12/2012
Task BldWrkCom-5-5 Startup / Test Shelter Power System 1 3/1/2012 3/1/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
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
Activity Civ-8 A&E - Blossom Hill 71 6/3/2011 9/9/2011
Task CivSur-8-10 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-8-9 Structural Analysis of Existing Tower 6 6/6/2011 6/13/2011
Task CivSur-8-8 Prepare, Review and Approve Site Sketch 7 6/14/2011 6/22/2011
Task CivSur-8 Site Survey and Mapping 7 6/28/2011 7/6/2011
Task CivArch-8-8 Existing Tower Zoning App and Approval 20 7/7/2011 8/3/2011
Task CivNEPA-8 NEPA/SHPO Studies and Approvals 30 6/23/2011 8/3/2011
Task MWPathSur-8 MW Path Studies 3 7/7/2011 7/11/2011
Task CivArch-8 Final Approval of Site Drawings by County 12 8/4/2011 8/19/2011
Task CivSitPerm-8 Building and Construction Permit App and Approval 15 8/22/2011 9/9/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-11 Mobilization 1 9/14/2011 9/14/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
Task AntRxInv 8-8 Ship Antennas, Lines, and Accessories to the Site 5 9/16/2011 9/22/2011
Task AntRxInv 8 Install Antennas and Lines 4 9/28/2011 10/3/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 BldGrnd-8-14 Trench and Install Grounding 2 9/26/2011 9/27/2011
Task BldGrnd-8-13 Grounding Inspection 1 9/28/2011 9/28/2011
Task BldCln-8 Conduit Inspection and Backfill 1 10/6/2011 10/6/2011
Task BldFndCnst-8-8 Excavate, Form, and Rebar Fuel Tank Foundation 1 10/7/2011 10/7/2011
Task BldFndCnst-8 Excavate, Form, and Rebar Generator Foundation 1 10/10/2011 10/10/2011
Task BldConDel-8-9 Offload and Install Generator 2 10/14/2011 10/17/2011
Task BldConDel-8-8 Install Fuel Tank and Piping 2 10/20/2011 10/21/2011
Task BldConDel-8 Piping Inspection, Leakage Test, and Backfill 3 10/24/2011 10/26/2011
Task BldExtCon-8 Cabling and Hookup Power System to Shelter 3 10/27/2011 10/31/2011
Task BldGrnd-8-12 Install Icebridge from Shelter to Tower 2 11/1/2011 11/2/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 BldGrnd-8 Complete Grounding Connections 1 10/3/2011 10/3/2011
Task BldWrkCom-8 Line Termination and Sweep Test 1 11/3/2011 11/3/2011
Task BldPunRes-8-8 Punch List with Floyd County 1 11/4/2011 11/4/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 CivSur-6-8 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-6-7 Structural Analysis of Existing Tower 6 6/6/2011 6/13/2011
Task CivSur-6-6 Prepare, Review and Approve Site Sketch 7 6/14/2011 6/22/2011
Task CivSur-6 Site Survey and Mapping 7 6/28/2011 7/6/2011
Task CivArch-6 Existing Tower Zoning App and Approval 20 7/7/2011 8/3/2011
Task CivNEPA-6 NEPA/SHPO Studies and Approvals 30 8/4/2011 9/14/2011
Task MWPathSur-6 MW Path Studies 3 7/7/2011 7/11/2011
Task CivSitPerm-6 Building and Construction Permit App and Approval 15 9/15/2011 10/5/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
Task CivSitPrep-6-6 Mobilization 1 10/10/2011 10/10/2011
12/10/10 8/13
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
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
Task AntRxInv 6 Install Antennas and Lines 4 10/26/2011 10/31/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 BldGrnd-6-7 Trench and Install Grounding 2 10/19/2011 10/20/2011
Task BldGrnd-6-6 Grounding Inspection 1 10/21/2011 10/21/2011
Task BldCln-6-6 Finish Grade and Gravel Compund 2 10/31/2011 11/1/2011
Task BldFnc-6 Fencing of Tower Compound 3 11/4/2011 11/8/2011
Task BldGrnd-6 Complete Grounding Connections 1 11/9/2011 11/9/2011
Task BldCln-6 Site Touchup and Restoration 2 11/10/2011 11/11/2011
Task BldWrkCom-6 Line Termination and Sweep Test 1 11/1/2011 11/1/2011
Task BldPunRes-6-6 Punch List with Floyd County 1 11/14/2011 11/14/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 CivSur-2-3 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-2-2 Prepare, Review and Approve Site Sketch 7 6/8/2011 6/16/2011
Task CivSur-2 Site Survey and Mapping 7 6/22/2011 6/30/2011
Task CivArch-2-3 Review and Approval of Prelim Site Drawings by County 10 7/1/2011 7/14/2011
Task CivArch-2-2 New Tower Zoning App and Approval 70 7/15/2011 10/20/2011
Task CivNEPA-2 NEPA/SHPO Studies and Approvals 70 6/21/2011 9/26/2011
Task CivGEO-2 GeoTech Testing and Report 8 7/5/2011 7/14/2011
Task MWPathSur-2 MW Path Studies 3 7/15/2011 7/19/2011
Task BldDes-2 Design Tower 6 7/22/2011 7/29/2011
Task CivArch-2 Final Approval of Site Drawings by County 12 10/21/2011 11/7/2011
Task CivSitPerm-2-3 Building and Construction Permit App and Approval 15 11/11/2011 12/1/2011
Task CivSitPerm-2-2 Land Disturbance Permit App and Approval 5 11/11/2011 11/17/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-5 Mobilization 1 12/6/2011 12/6/2011
Task CivSitPrep-2-4 Locate Utilities 1 12/9/2011 12/9/2011
Task CivSitPrep-2-3 Construction Staking 1 12/12/2011 12/12/2011
Task CivSitPrep-2-2 Light Clearing and Grubbing 1 12/7/2011 12/7/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 TowCnstGrd-2 Tower Grounding 1 12/23/2011 12/23/2011
Task TowCnstShip-2-2 Ship Forms, Backfill, and Compaction 1 12/30/2011 12/30/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
Task AntRxInv 2-2 Ship Antennas, Lines, and Accessories to the Site 5 1/4/2012 1/10/2012
Task AntRxInv 2 Install Antennas and Lines 4 1/16/2012 1/19/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
Task BldGrnd-2-4 Trench and Install Grounding 2 1/9/2012 1/10/2012
12/10/10 9/13
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
Task BldGrnd-2-3 Grounding Inspection 1 1/11/2012 1/11/2012
Task BldUtilHU-2 Conduit Inspection and Backfill 1 1/9/2012 1/9/2012
Task BldConDel-2-9 Offload and Install Generator 2 1/12/2012 1/13/2012
Task BldExtCon-2 Cabling and Hookup Power System to Shelter 3 1/16/2012 1/18/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 BldFnc-2 Fencing of Tower Compound 3 3/2/2012 3/6/2012
Task BldGrnd-2 Complete Grounding Connections 1 3/27/2012 3/27/2012
Task BldCln-2 Site Touchup and Restoration 2 3/28/2012 3/29/2012
Task BldWrkCom-2-5 Line Termination and Sweep Test 1 1/20/2012 1/20/2012
Task BldWrkCom-2-4 Generator Startup / Test Power System 1 1/25/2012 1/25/2012
Task BldWrkCom-2-3 Grounding Test of the Site 1 3/28/2012 3/28/2012
Task BldWrkCom-2-2 Startup / Test Shelter Power System 1 1/26/2012 1/26/2012
Task BldWrkCom-2 Fan Test of Fire Suppression System and Fire Marshall Permit 1 3/20/2012 3/20/2012
Task BldPunRes-2-2 Punch List with Floyd County 1 3/30/2012 3/30/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 CivSur-9 Site Visit with A&E 1 6/3/2011 6/3/2011
Task CivSur-9-9 Structural Analysis of Existing Tower 6 6/6/2011 6/13/2011
Task CivArch-9 Existing Tower Zoning App and Approval 20 6/14/2011 7/11/2011
Task CivNEPA-9 NEPA/SHPO Studies and Approvals 30 7/12/2011 8/22/2011
Task MWPathSur-9 MW Path Studies 3 8/23/2011 8/25/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 CivSitPrep-9-9 Mobilization 1 9/6/2011 9/6/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 BldWrkCom-9 Line Termination and Sweep Test 1 9/15/2011 9/15/2011
Task BldPunRes-9 Punch List with Floyd County 1 9/30/2011 9/30/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
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
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
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
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
Floyd County, Georgia -Preliminary Project Gantt
GA-10Q123A 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
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.
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.
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.
10-2 Training
System Administrator
Course Target Audience No. of Duration Location Date No. of
Sessions (days) Attendees
Training 10-3
System Administrator
Course Target Audience No. of Duration Location Date No. of
Sessions (days) Attendees
(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.
10-4 Training
Technician Maintenance Training
Course Target Audience No. of Duration Location Date No. of
Sessions (days) Attendees
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.
(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.
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)
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.
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 Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce console training.
10-6 Training
Optional – Console Cutover Support
Course Target Audience No. of Duration Location Date No. of Attendees
Sessions (days)
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.
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.
Course Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce APX training
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
(Instructor-led) sessions)
Accep-
tance
Course Synopsis:
This tailored refresher will be based on a needs assessment, frequently asked questions and best practices to reinforce APX training
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
(Instructor-led) session)
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.
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.
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
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
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
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
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-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
Training 10-15
I. User Configuration Manager (UCM)
J. Zone Configuration Manager (ZCM)
K. Unified Network Configurator (UNC)
L. Configuration/Service Software (CSS)
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
10-16 Training
Computer Requirements
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
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
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
10-18 Training
Computer Requirements
♦ 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
Prerequisites
None
Course Outline
I. RF Basics
A. Making the Link
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-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
♦ Completion of the following courses or equivalent experience:
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
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-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
♦ 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 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
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-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
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-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
♦ Completion of the following courses or equivalent experience:
♦ 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
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
Prerequisites
♦ A basic understanding of Windows navigation
♦ Laptop computer with Windows XP
♦ Windows program files must be on the “C” directory
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
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
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
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
Recommended Prerequisites
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
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
Recommended Prerequisites
None
Key Topics
♦ Overview
♦ Communicating with Radios
♦ Advanced Signaling Features
♦ Resource Groups
♦ Working with Configurations
♦ Working with Aux IOs
♦ Troubleshooting
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
Recommended Prerequisites
♦ 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
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
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
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
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
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
10-40 Training
10.3.21 CCSA IP-10/IP-10G class curriculum
Agenda:
Day 1: 9:00 to 4:30
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
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
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
10-42 Training
Lab 7
♦ Troubleshooting the radio
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.
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
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
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.
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.
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.
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.
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.
Pricing 12-1
This page left intentionally blank.
12-2 Pricing
Section 13. Contractual Documentation
Please see Motorola’s Communications System Agreement on the following pages.
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.
Section 2 DEFINITIONS
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.
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.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.
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
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.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,
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.
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):
____________________________________________________________________________________
____________________________________________________________________________________
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
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.
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.
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
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.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.
Section 10 DELAYS
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.
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
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.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
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.
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.
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.
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.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.
This Exhibit A Software License Agreement ("Agreement") is between Motorola, Inc., (“Motorola"), and
Floyd County, Georgia (“Licensee”).
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.
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.
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.
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.
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.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
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).
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.
Section 12 NOTICES
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.
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.
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).
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.
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.
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.
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.
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.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.
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 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-
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.
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.
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.
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
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.
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.
G-SERIES SITE
EQUIPMENT FOR
ASTRO 25 SYSTEMS
®
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
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
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.
PAGE 2
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
GTR 8000 Base Radio / GCP 8000 Site Controller / GCM 8000 Comparator / GPW 8000 Receiver
PAGE 3
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
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
16 QAM –108 dBm NA NA NA
QPSK –115 dBm NA NA NA
Sensitivity 5% Bit Error Rate Static (BER)
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
PAGE 4
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
PAGE 5
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
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
Sensitivity 1% Bit Error Rate Static (BER)
64 QAM –98 dBm NA NA NA
16 QAM –104 dBm NA NA NA
QPSK –111 dBm NA NA NA
Sensitivity 5% Bit Error Rate Static (BER)
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
Spurious and Image Response
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
PAGE 6
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 SYSTEMS
* Optional Preselector
PAGE 7
PRODUCT SPEC SHEET
G-SERIES SITE EQUIPMENT FOR ASTRO®25 RADIO NETWORKS
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
®
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)
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
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
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.
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
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
MCC 7500
IP Dispatch Console
specifications
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.
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
MIP 5000 VoIP Radio Console
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.
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)
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.
Dual-pedal footswitch
PRODUCT SPEC SHEET
MIP 5000 VoIP Radio Console
Rx Impedance 47 Kohm
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.
Tone Tolerance ± 2%
Opto-Input Qty 1, for High Speed Mute, COR detect, Cd/Clr Rx Status (selectable)
Relay Output Type Form C, DPDT, Dry Closure, 150mA max., or 60VDC max.
Relay Output Type Form C, DPDT, Dry Closure, 150mA max., or 60VDC max.
Radio Connector type USB for Data and RJ45 for Audio
Output Impedance 600 ohms and 10 kOhms (Tone control model only)
Call Light Sensitivity Adjustable from -5 to -32 dBm, relative to receive sensitivity.
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.
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.
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.
Form A dry closures 150 mA max. or 60VDC max. Switching power 3 watts max.
Maximum distance 200 ft within one building.
NETWORK REQUIREMENTS
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
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
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
MC SERIES
Deskset Controllers
MC SERIES
Deskset Controllers
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.
standard features
MC SERIES
Deskset Controllers
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)
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
MC SERIES
Deskset Controllers
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)
Specifications subject to change without notice.
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
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. 2009 (0904)
R3-13-2003C POD
S P E C I F I C AT I O N S H E E T
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
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
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
R E G U L ATO RY STA N DA R D S
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. 2006 (0604)
R3-11-2030
Flatpack2 Power System
Data Sheet # Preliminary Rev.0
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.
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.
www.eltekenergy.com
info.americas@eltekenergy.com
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.
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:
AC Input Configuration
Requires: Eight (8) 30A feed breakers.
Each AC feed supplies two rectifiers. The power racks house four rectifiers each.
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.
www.eltekenergy.com
info.americas@eltekenergy.com
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.
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
RESERVE
POWER
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 ®
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
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%).
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.
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
HEIGHT HEIGHT
H. NOM.
TYPE DD 50-YY
TYPE DD 125-YY
LENGTH LENGTH
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
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”)
ASTRO® DIGITAL
XTL™ 5000 Consolette
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
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)
VOICE CODER*
ENCRYPTION*
POWER REQUIREMENTS
TRANSMITTER
RECEIVER
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. 2009 (0906)
R3-1-2022D
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)
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
VOICE CODER
Voice Coding Method IMBE (CAI) Improved Multi Band Excitation (IMBE)
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 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
speaker MOBILE
transmitter
receiver
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. 2008 (0809)
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.
Project 25 and is available in 136-174 MHz,
Specification sheet
VOICE CODER
Voice Coding Method IMBE (CAI) Improved Multi Band Excitation (IMBE)
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 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
speaker MOBILE
transmitter
receiver
Motorola, Inc. 1301 E. Algonquin Road, Schaumburg, Illinois 60196 U.S.A. www.motorola.com/secondnature 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. 2008 (0809)
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.
Project 25 and is available in 136-174 MHz,
Specification sheet
VOICE CODER
Voice Coding Method IMBE (CAI) Improved Multi Band Excitation (IMBE)
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 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
speaker MOBILE
transmitter
receiver
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. 2008 (0809)
R3-1-2029C
specification sheet
APX 7500 ™
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
Project 25 Multi-Band Mobile Radio
MOBILE APX7500
APX 7500
Project 25 Multi-Band Mobile Radio
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
APX 7500
Project 25 Multi-Band Mobile Radio
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
Key Erasure Keyboard command and tamper detection
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
Specifications subject to change without notice. All specifications shown are typical.
Radio meets applicable regulatory requirements.
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. 2009 (0910)
R3-1-2037A
SPECIFICATION SHEET
PRELIMINARY
APX™ 6500
Project 25 MOBILE Radio
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
APX ™ 6500 Specifications
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
XTS 2500I
®
VOICE CODER
Voice Coding Method IMBE (CAI) Improved Multi Band Excitation (IMBE)
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 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.
Code Book Structure APCO Project 25 (IMBE): No code book
RADIO MODELS
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
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. 2008 (0809)
R3-4-2003K
Specification sheet
XTS 1500 ®
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
Digital Portable Radio
XTS® 1500
Digital Portable Radio
RADIO MODELS
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
ENVIRONMENTAL SPECIFICATIONS
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. 2008 (0809)
R3-4-2007I
Specification sheet
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.
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
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)
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 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.
Code Book Structure APCO Project 25 (IMBE): No code book
* 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
Specifications subject to change without notice.
Specification sheet
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
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. 2008 (0809)
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.
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.
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)
APX 7000 ™
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
Project 25 Multi-Band Portable Radio
Radio Profiles
Unified Call List (Dual Display model only) OPTIONAL FEATURES:
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
Project 25 Multi-Band Portable Radio
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
APX 7000
Project 25 Multi-Band Portable Radio
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
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
(CKR) or 16 Physical Identifier (PID)
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
Humidity Per MIL-STD
Vector Generator National Institute of Standards and Technology
ESD IEC 801-2 KV
(NIST) approved random number generator
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
Specifications subject to change without notice. All specifications shown are typical.
Radio meets applicable regulatory requirements.
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. 2009 (0910)
R3-4-2021B
SPECIFICATION SHEET
PRELIMINARY
APX™ 7000XE
Project 25 Multi-Band Portable Radio
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
Features and Benefits:
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.
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
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
(CKR) or 16 Physical Identifier (PID)
Encryption Frame Re-sync Interval P25 CAI 300 mSec
environmental SPEcifications
Operating Temperature -30ºC / +60ºC
Encryption Keying Key Loader
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
Key Erasure Keyboard command and tamper detection
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
Specifications subject to change without notice. All specifications shown are typical.
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-4-2034
®
PROBLEM SOLUTION
CC807-06
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
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.
Antennas
700-1000 MHz Antennas
SC479 - PIM Certified Series
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)
Appendix 15-1
This page left intentionally blank.
15-2 Appendix