COLUMBIA COUNTY BOARD OF COUNTY COMMISSIONERS AGENDA ITEM REQUEST FORM

Transcription

1 COLUMBIA COUNTY BOARD OF COUNTY COMMISSIONERS AGENDA ITEM REQUEST FORM # 1 The Board of County Commissioners meets the 1st and 3rd Thursday of each month at 5:30 p.m. in the Columbia County School Board Administrative Complex Auditorium, 372 West Duval Street, Lake City, Florida All agenda items are due in the Board s office one week prior to the meeting date. Today's Date: Meeting Date: November 16, 2017 Name: Lawrence Wilson Department: Communications Division Manager's Signature: 1. Nature and purpose of agenda item: Approve Bid Award _RFP-2017-O Negotiated Contract.- $5,500,000 BA 18-12; total amendment $750,000. Attach any correspondence information, documents and forms for action i.e., contract agreements, quotes, memorandums, etc. 2. Fiscal impact on current budget. Is this a budgeted item? N/A Yes Account No. X No Please list the proposed budget amendment to fund this request Budget Amendment Number: BA Fund: 102-MSBU FROM: TO: AMOUNT: RESERVES / CASH BALANCE FORWARD INTERFUND TRANSFERS OUT / TO GENERAL CAP PROJECTS $250, CASH BALANCE FORWARD TO GENERAL CAP PROJECTS $250, RESERVES / FUTURE ENHANCEMENT INTERFUND TRANSFERS OUT / TO GENERAL CAP PROJECTS $250, INTERFUND TRANSFERS IN / FROM GENERAL FUND CAPITAL OUTLAY / IMP OTHER THAN BLDS $250, Consent Item p. 86 For Use of County Manger Only: X Discussion Item

2 COLUMBIA COUNTY BOARD OF COUNTY COMMISSIONERS AGENDA ITEM REQUEST FORM # 1 The Board of County Commissioners meets the 1st and 3rd Thursday of each month at 5:30 p.m. in the Columbia County School Board Administrative Complex Auditorium, 372 West Duval Street, Lake City, Florida All agenda items are due in the Board s office one week prior to the meeting date. Today's Date: Meeting Date: November 16, 2017 Name: Lawrence Wilson Department: Communications Division Manager's Signature: INTERFUND TRANSFERS IN / FROM MSBU CAPITAL OUTLAY / IMP OTHER THAN BLDS $250, XX FROM SHERIFF FUND IMP OTHER THAN BLDS $250, For Use of County Manger Only: Consent Item X Discussion Item p. 87

3 District No. 1 - Ronald Williams District No. 2 - Rusty DePratter District No. 3 - Bucky Nash District No. 4 - Everett Phillips District No. 5 Timothy Murphy Date: To: Ben Scott, County Manager Re: Columbia County Communications RFP 2017-O Central Communications respectfully request the approval of the negotiated contract with Motorola Solutions (Motorola) for a new County-wide public safety radio system in the amount of $5,500, Motorola was the highest ranking proposal out of three responses received from RFP 2016-O. Staff successfully negotiated turnkey pricing for a radio system that will give Columbia County s public safety agencies and local government users portable outdoor radio coverage County-wide. Motorola has contractually agreed and guaranteed to deliver 95% outdoor portable radio coverage and 81% light inbuilding coverage (6dB) based upon the County s borders. To achieve this level of County-wide coverage requires the addition of a 6 th site in the northern part of the County. Below is a breakdown of the system costs with the 6 th site option: Total proposed system turnkey cost five (5) sites (after discounts): $4,760, Addition of a 6 th site in the northern part of the County: (after discounts): $739, Total proposed system turnkey cost six (6) sites (after discounts): $5,500, Total proposed costs for fourteen (14) years of extended maintenance and technology refreshes at years five (5) and ten (10): $2,123, ($151,672.76/year) Total Cost of Ownership: $7,623, Staff negotiated the addition of the 6 th site in the northern part of the County to ensure that all users would have County-wide portable outdoor radio coverage. If the County implements the 6 th site at this time there is a direct cost savings of approximately $200, which does not consider cost increase due to inflation if the 6 th site were built at a later date. Coverage maps are attached to show the significant difference this 6 th site will make in covering the northern 8 miles of the County. The system as negotiated will be a trunked simulcast P25 Phase 2 system with six (6) transmit/receive sites with five (5) channels at each, three (3) 800 MHz conventional mutual aid channels, (3) VHF conventional mutual aid channels and integration of the County s existing VHF simulcast paging system. There will be a new 200 Mbps licensed indoor microwave network for backhaul, over 500 new user radios, 20 new radio dispatch console positions (10 fixed and 10 mobile) and a new communications site (including tower, shelter and emergency power systems). Staff also negotiated an extended maintenance contract with Motorola to cover the County s investment for the next 15 years. This extended maintenance contract will include two (2) technology refreshes (network core equipment and system software) at years five (5) and ten (10). BOARD MEETS THE FIRST THURSDAY AT 5:30 P.M. AND THIRD THURSDAY AT 5:30 P.M. p. 88 P.O. BOX 1529 LAKE CITY, FLORIDA PHONE: (386)

4 It is anticipated that this new radio system will serve the needs of the citizens of Columbia County for the at least the next 15 years. Cc: Scott Ward, Assistant County Manager, Columbia County 2 of 2 p. 89

5 Communications System Agreement: P25 700/800 MHz Radio System Motorola Solutions, Inc. ( Motorola ) and Columbia County Board of County Commissioners, Florida ( 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 G will be resolved in their listed order. Exhibit A Motorola s Software License Agreement Exhibit B Payment Schedule Exhibit C Motorola s Negotiated Proposal C-1 Negotiated Section 3 Project Management Plan, Implementation, Schedule and Cutover C-2 Negotiated Section 4 Technical Approach and Proposed Solution C-3 Negotiated Section 8 Cost Proposal Exhibit D Service Terms and Conditions Schedule A Technology Refresh Exhibit E System Acceptance Certificate Exhibit F Motorola s Proposal dated July 31, 2017 Exhibit G Columbia County RFP O Section 2 DEFINITIONS Capitalized terms used in this Agreement have the following meanings: 2.1. Acceptance Tests means those tests described in the Section 11 of Columbia County s RFP 2017 O (Exhibit G) and Motorola s presented Acceptance Test Plans as detailed in Exhibit C Beneficial Use means when Customer first uses the System or a Subsystem for operational purposes (excluding training or testing) 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; is explicitly approved for release by written authorization of the disclosing Party; or is released pursuant to law Contract Price means the price for the System, excluding applicable sales or similar taxes and freight charges Effective Date means that date upon which the last Party executes this Agreement 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 Force Majeure means an event, circumstance, or act of a third party that is beyond a Party s reasonable control (e.g., an act of God, an act of the public enemy, an act of a government entity, strikes or other labor disturbances, hurricanes, earthquakes, fires, floods, harsh and difficult weather conditions, p. 90 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents i

6 epidemics, embargoes, war, and riots) Infringement Claim means a third party claim alleging that the Equipment manufactured by Motorola or the Motorola Software infringes upon the third party s United States patent or copyright Motorola Software means Software that Motorola or its affiliated company owns Non-Motorola Software means Software that another party owns Open Source Software (also called freeware or shareware ) means software that has its underlying source code freely available to evaluate, copy, and modify Performance Schedule means the project implementation schedule included in Exhibit C Section 3.3 as finalized at the Detail Design Review 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 Software means the Motorola Software and Non-Motorola Software, in object code format that is furnished with the System or Equipment Specifications means the functionality and performance requirements that are described in Exhibit C and Exhibit G Subsystem means a major part of the System that performs specific functions or operations. Subsystems are described in Exhibit C System means the Equipment, Software, and incidental hardware and materials that are combined together into an integrated system; the System is described in Exhibit C System Acceptance means that all test specified in Section 11 of Columbia County s RFP 2017 O and Motorola s presented Acceptance Test Plans as detailed in Exhibit C. have been successfully completed Final System Acceptance means that all System Acceptance Test have been successfully completed, all outstanding punch list items have been addressed and all final System Documentation as required in Section 13 of Exhibit G have been completed Warranty Period means one (1) year from the date of Final System Acceptance. Section 3 SCOPE OF AGREEMENT AND TERM 3.1. SCOPE OF WORK. Motorola will provide, install and test the System, and perform its other contractual responsibilities, all in accordance with this Agreement and as detailed in Exhibit C. Customer will perform its contractual responsibilities in accordance with this Agreement 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 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. p. 91

7 3.4. ADDITIONAL EQUIPMENT OR SOFTWARE. For three (3) years after the Effective Date, Customer may order additional Equipment or Software if it is then available. Each order must refer to this Agreement and must specify the pricing and delivery terms. Notwithstanding any additional or contrary terms in the order, the applicable provisions of this Agreement (except for pricing, delivery, passage of title and risk of loss to Equipment, warranty commencement, and payment terms) will govern the purchase and sale of the additional Equipment or Software. Title and risk of loss to additional Equipment will pass at shipment, warranty will commence upon delivery, and payment is due within thirty (30) days after the invoice date. Motorola will send Customer an invoice as the additional Equipment is shipped or Software is licensed. Alternatively, Customer may register with and place orders through Motorola Online ( MOL ), and this Agreement will be the Underlying Agreement for those MOL transactions rather than the MOL On-Line Terms and Conditions of Sale. MOL registration and other information may be found at and the MOL telephone number is (800) MAINTENANCE SERVICE. During the Warranty Period, Motorola will provide maintenance services for the Equipment and support for the Motorola Software pursuant to this Agreement. 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 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 the maintenance, support or software subscription services will be Motorola s standard Service Terms and Conditions, together with the appropriate statements of work 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 NON-MOTOROLA SOFTWARE. Any Non-Motorola Software is licensed to Customer in accordance with the standard license, terms, and restrictions of the copyright owner on the Effective Date unless the copyright owner has granted to Motorola the right to sublicense the Non-Motorola Software pursuant to the Software License Agreement, in which case it applies and the copyright owner will have all of Licensor s rights and protections under the Software License Agreement. Motorola makes no representations or warranties of any kind regarding Non-Motorola Software. Non-Motorola Software may include Open Source Software. All Open Source Software is licensed to Customer in accordance with, and Customer agrees to abide by, the provisions of the standard license of the copyright owner and not the Software License Agreement. Upon request by Customer, Motorola will use commercially reasonable efforts to determine whether any Open Source Software will be provided under this Agreement; and if so, identify the Open Source Software and provide to Customer a copy of the applicable standard license (or specify where that license may be found); and provide to Customer a copy of the Open Source Software source code if it is publicly available without charge (although a distribution fee or a charge for related services may be applicable) 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 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 p. 92 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents iii

8 that certain provisions must be agreed upon, and they agree to negotiate those in good faith promptly after Customer delivers the option exercise notice. Examples of provisions that may need to be negotiated are: specific lists of deliverables, statements of work, acceptance test plans, delivery and implementation schedules, payment terms, maintenance and support provisions, additions to or modifications of the Software License Agreement, hosting terms, and modifications to the acceptance and warranty provisions. Section 4 PERFORMANCE SCHEDULE The Parties will perform their respective responsibilities in accordance with this Agreement and as detailed in Exhibit C. By executing this Agreement, Customer authorizes Motorola to proceed with contract performance. The Customer will not be issuing a Purchase Order (PO) or any other Notice to Proceed (NTP) for the entirety of this Agreement and will appropriate according to Exhibit B and project schedule. The annual payments can be processed solely against this Agreement. Section 5 CONTRACT PRICE, PAYMENT AND INVOICING 5.1. CONTRACT PRICE. The Contract Price in U.S. dollars is $ for the work described in Exhibit C. A pricing summary is included with the Payment Schedule. Motorola has priced the services, Software, and Equipment as an integrated system. A reduction in Software or Equipment quantities, or services, may affect the overall Contract Price, including discounts if applicable INVOICING AND PAYMENT. Motorola will submit invoices to Customer according to the Payment Schedule (Exhibit B). 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 wire transfer, check, or cashier s check from a U.S. financial institution. For reference, the Federal Tax Identification Number for Motorola Solutions, Inc. is FREIGHT, TITLE, AND RISK OF LOSS. Motorola will pre-pay and add all freight charges to the invoices. For the FNE, Title to the Equipment will pass to Customer upon receipt of the shipment, and title will revert back to Motorola if the Equipment fails to pass Acceptance Testing. Title to Software will not pass to Customer at any time. Risk of loss will pass to Customer upon Final System Acceptance. For the Subscribers, Title and Risk of Loss will pass upon receipt of the shipment. Motorola will pack and ship all Equipment in accordance with good commercial practices INVOICING AND SHIPPING ADDRESSES. Invoices will be sent to the Customer at the following address: Columbia County Board of County Commissioners 135 NE Hernando Ave., Suite 203, Lake City, FL The Equipment will be shipped to the Customer to the site locations detailed in Exhibit C. Section 6 SITES AND SITE CONDITIONS 6.1. ACCESS TO SITES. In addition to its responsibilities described elsewhere in this Agreement, Customer will provide a designated project manager; all necessary construction and building permits, zoning variances, licenses, and any other approvals that are necessary to develop or use the sites; and access to the work sites 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 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; electrical power outlets, distribution and equipment; and telephone or other communication lines (including modem access and adequate interfacing networking capabilities), all for the installation, use and maintenance of the System. Before installing the Equipment or Software at a work site, Motorola will inspect the work site and advise Customer of any apparent deficiencies or non-conformities with the requirements of this p. 93

9 Section. This Agreement is predicated upon normal soil conditions as defined by the version of E.I.A. standard RS-222 in effect on the Effective Date 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 and as detailed in Exhibit C. Customer will notify Motorola immediately if a date change for a scheduled training program is required. If Motorola incurs additional costs because Customer reschedules a training program less than thirty (30) days before its scheduled start date, Motorola may recover these additional costs. Section 8 SYSTEM ACCEPTANCE 8.1. COMMENCEMENT OF ACCEPTANCE TESTING. Motorola will provide to Customer at least ten (10) days notice before the Acceptance Tests commence. System testing will occur only in accordance with the Acceptance Test Plan 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. 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 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 SYSTEM ACCEPTANCE. Final System Acceptance will occur after System Acceptance when all deliverables and other work have been completed. When Final System Acceptance occurs, the parties will promptly memorialize this final event by so indicating on the System Acceptance Certificate. Section 9 REPRESENTATIONS AND WARRANTIES 9.1. SYSTEM FUNCTIONALITY. Motorola represents that the System will perform in accordance with the Specifications in all material respects. Upon Final System Acceptance or Beneficial Use, whichever occurs first, this System functionality representation is fulfilled. Motorola is not responsible for System performance deficiencies that are caused by ancillary equipment not furnished by Motorola which is attached to or used in connection with the System or for reasons or parties beyond Motorola s control, such as natural causes; the construction of a building that adversely affects the microwave path reliability or radio frequency (RF) coverage; the addition of frequencies at System sites that cause p. 94 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents v

10 RF interference or intermodulation; or Customer changes to load usage or configuration outside the Specifications 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 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 EXCLUSIONS TO EQUIPMENT AND MOTOROLA SOFTWARE WARRANTIES. These warranties do not apply to: (i) defects or damage resulting from: use of the Equipment or Motorola Software in other than its normal, customary, and authorized manner; accident, liquids, neglect, or acts of God; testing, maintenance, disassembly, repair, installation, alteration, modification, or adjustment not provided or authorized in writing by Motorola; Customer s failure to comply with all applicable industry and OSHA standards; (ii) breakage of or damage to antennas unless caused directly by defects in material or workmanship; (iii) Equipment that has had the serial number removed or made illegible; (iv) batteries (because they carry their own separate limited warranty) or consumables; (v) freight costs to ship Equipment to the repair depot; (vi) scratches or other cosmetic damage to Equipment surfaces that does not affect the operation of the Equipment; and (vii) normal or customary wear and tear 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. 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 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 DISCLAIMER OF OTHER WARRANTIES. THESE WARRANTIES ARE THE COMPLETE WARRANTIES FOR THE EQUIPMENT AND MOTOROLA SOFTWARE PROVIDED UNDER THIS AGREEMENT AND ARE GIVEN IN LIEU OF ALL OTHER WARRANTIES. TO THE EXTENT ALLOWED BY FLORIDA LAW, MOTOROLA DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Section 10 DELAYS FORCE MAJEURE. Neither Party will be liable for its non-performance or delayed performance if caused by a Force Majeure. A Party that becomes aware of a Force Majeure that will significantly delay performance will notify the other Party promptly (but in no event later than fifteen days) after it discovers the Force Majeure. If a Force Majeure occurs, the Parties will execute a change order to extend the Performance Schedule for a time period that is reasonable under the circumstances PERFORMANCE SCHEDULE DELAYS CAUSED BY CUSTOMER. If Customer (including its other contractors) delays the Performance Schedule, the Parties will execute a change order to extend the Performance Schedule and, if requested, compensate Motorola for all reasonable charges incurred because of the delay. Delay charges may include costs incurred by Motorola or its subcontractors for additional freight, warehousing and handling of Equipment; extension of the warranties; travel; p. 95

11 suspending and re-mobilizing the work; additional engineering, project management, and standby time calculated at then current rates; and preparing and implementing an alternative implementation plan PERFORMANCE SCHEDULE DELAYS CAUSED BY MOTOROLA. If Motorola (including its other contractors) delays the Performance Schedule by more than 30 calendar days beyond the stated Final System Acceptance date, the Parties will execute a change order to extend the Performance Schedule and Motorola will be liable for liquidated damages not to exceed 3% of the Contract Price. Given the nature of implementing a complex communications system, specifically scheduled activities are regularly rearranged to allow for the most efficient or expedient implementation schedule. As such, Motorola needs the flexibility to make changes to the detailed Performance Schedule and time is not to be considered of the essence with regard to the many specific time related obligations detailed in the Project Schedule. However, time is of the essence with regard to the Final System Acceptance date and Columbia County shall have the right to either seek to enforce the Performance Bond or levy liquidated damages if Motorola is more than 30 calendar days beyond the specified Final System Acceptance date. Motorola agrees to pay liquidated damages of $500 per day for each day beyond 30 calendar days after the Final System Acceptance date (as may be adjusted by mutual agreement) if it fails to meet that date due solely to delays it or its subcontractors caused or could have prevented with commercially reasonable means. Any additional delay damages beyond that term may be negotiated between the parties. The parties specifically agree that the liquidated damages herein are not considered as a penalty. Section 11 DISPUTES SETTLEMENT PREFERRED. The Parties, by their project managers, will attempt to settle any dispute arising from this Agreement (except for a claim relating to intellectual property or breach of confidentiality) through consultation and a spirit of mutual cooperation. The dispute will be escalated to appropriate higher-level managers of the Parties, if necessary LITIGATION. A Party may submit to a state court of competent jurisdiction in the Third Judicial Circuit Court in and for Columbia County, Florida any claim relating to intellectual property or a breach of confidentiality provisions. Each Party consents to jurisdiction over it by that court. Either Party may resort to the judicial proceedings described in this section if good faith efforts to resolve the dispute under these procedures have been unsuccessful; or interim relief from the court is necessary to prevent serious and irreparable injury to the Party. The prevailing Party in any litigation arising between the parties to this Agreement and under or through this Agreement, including appellate proceedings, shall recover its reasonable attorneys fees and taxable costs from the non-prevailing Party. Section 12 DEFAULT AND TERMINATION 12.1 DEFAULT BY A PARTY. If either Party fails to perform a material obligation under this Agreement, the other Party may consider the non-performing Party to be in default (unless a Force Majeure causes the failure) and may assert a default claim by giving the non-performing Party a written and detailed notice of default. Except for a default by Customer for failing to pay any amount when due under this Agreement which must be cured immediately, the defaulting Party will have thirty (30) days after receipt of the notice of default to either cure the default or, if the default is not curable within thirty (30) days, provide a written cure plan. The defaulting Party will begin implementing the cure plan immediately after receipt of notice by the other Party that it approves the plan. If Customer is the defaulting Party, Motorola may stop work on the project until it approves the Customer s cure plan 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 p. 96 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents vii

12 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 In the event Customer elects to terminate this Agreement for any reason other than default, Customer shall pay Motorola for the conforming Equipment and/or Software delivered and all services performed. Section 13 INDEMNIFICATION 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, intentional misconduct or omissions of Motorola, its subcontractors, or their employees or agents, while performing their duties under or arising out of 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. Neither this nor any other provision of this Agreement shall be construed as a waiver of the defense of sovereign immunity in any action arising under or through this Agreement PATENT AND COPYRIGHT INFRINGEMENT Motorola will defend at its expense any suit brought against Customer to the extent it is based on an Infringement Claim, and Motorola will indemnify Customer for those costs and damages finally awarded against Customer for an 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 If an Infringement Claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its option and expense procure for Customer the right to continue using the Equipment or Motorola Software, replace or modify it so that it becomes non-infringing while providing functionally equivalent performance, or grant Customer a credit for the Equipment or Motorola Software as depreciated and accept its return. The depreciation amount will be calculated based upon generally accepted accounting standards for such Equipment and Motorola Software Motorola will have no duty to defend or indemnify for any Infringement Claim that is based upon: (a) the combination of the Motorola Product with any software, apparatus or device not furnished by Motorola; (b) the use of ancillary equipment or software not furnished by Motorola and that is attached to or used in connection with the Motorola Product; (c) Motorola Product designed or manufactured in accordance with Customer s designs, specifications, guidelines or instructions, if the alleged infringement would not have occurred without such designs, specifications, guidelines or instructions; (d) a modification of the Motorola Product by a party other than Motorola; (e) use of the Motorola Product in a manner for which the Motorola Product was not designed or that is inconsistent with the terms of this Agreement; or (f) the failure by Customer to install an enhancement release to the Motorola Software that is intended to correct the claimed infringement. In no event will Motorola s liability resulting from its indemnity obligation to Customer extend in any way to royalties payable on a per use basis or the Customer s revenues, or any royalty basis other than a reasonable royalty based upon revenue derived by Motorola from Customer from sales or license of the infringing Motorola Product 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 p. 97

13 legal theory or principle, in connection with an Infringement Claim. In addition, the rights and remedies provided in this Section 13 are subject to and limited by the restrictions set forth in Section 14. Section 14 LIMITATION OF LIABILITY Except for personal injury, death or tangible property damage, 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. An action for contract breach or otherwise relating to the transactions contemplated by this Agreement may be brought within one year. Neither this nor any other provision of this Agreement shall be construed as a waiver of the defense of sovereign immunity in any action arising under or through this Agreement. Section 15 CONFIDENTIALITY AND PROPRIETARY RIGHTS Confidentiality Obligation. Each party is a disclosing party ( Discloser ) and a receiving party ( Recipient ) under this Agreement. During the term of this Agreement, for a period of three (3) years from the date of expiration or termination of this Agreement, and except to the extent allowed or required by Chapter 119, Florida statute or other applicable public records law, recipient will (i) not disclose Confidential Information to any third party; (ii) restrict disclosure of Confidential Information to only those employees (including, but not limited to, employees, officers, officials, agents, volunteers or consultants) who must be directly involved with the Confidential Information for the purpose and who are bound by confidentiality terms substantially similar to those in this Agreement; (iii) not reverse engineer, de-compile or disassemble any Confidential Information; (iv) use the same degree of care as for its own information of like importance, but at least use reasonable care, in safeguarding against disclosure of Confidential Information; (v) promptly notify discloser upon discovery of any unauthorized use or disclosure of the Confidential Information and take reasonable steps to regain possession of the Confidential Information and prevent further unauthorized actions or other breach of this Agreement; and (vi) only use the Confidential Information as needed to fulfill this Agreement Required Disclosure. If a recipient is required to disclose Confidential Information pursuant to applicable law, statute, or regulation, or court order, the recipient will give to the discloser prompt written notice of the request and a reasonable opportunity to object to such disclosure and seek a protective order or appropriate remedy. If, in the absence of a protective order, the recipient determines, upon the advice of counsel, that it is required to disclose such information, it may disclose only Confidential Information specifically required and only to the extent required to do so Confidential Exceptions. Recipient is not obligated to maintain as confidential, Confidential Information that recipient can demonstrate by documentation (i) is now available or becomes available to the public without breach of this Agreement; (ii) is explicitly approved for release by written authorization of discloser; (iii) is lawfully obtained from a third party or parties without a duty of confidentiality; (iv) is known to the recipient prior to such disclosure; or (v) is independently developed by recipient without the use of any discloser s Confidential Information or any breach of this Agreement Ownership and Retention. All Confidential Information remains the property of the discloser and will not be copied or reproduced without the express written permission of the discloser, except for copies that are absolutely necessary in order to fulfill this Agreement. Within ten (10) days of receipt of discloser s written request, recipient will return all Confidential Information to discloser along with all copies and portions thereof, or certify in writing that all such Confidential Information has been p. 98 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents ix

14 destroyed. However, recipient may retain one (1) archival copy of the Confidential Information that it may use only in case of a dispute concerning this Agreement. No license, express or implied, in the Confidential Information is granted other than to use the Confidential Information in the manner and to the extent authorized by this Agreement. The discloser warrants that it is authorized to disclose any Confidential Information it discloses pursuant to this Agreement PRESERVATION OF MOTOROLA S PROPRIETARY RIGHTS. Motorola, the third party manufacturer of any Equipment, and the copyright owner of any Non-Motorola Software own and retain all of their respective Proprietary Rights in the Equipment and Software, and nothing in this Agreement is intended to restrict their Proprietary Rights. All intellectual property developed, originated, or prepared by Motorola in connection with providing to Customer the Equipment, Software, or related services remain vested exclusively in Motorola, and this Agreement does not grant to Customer any shared development rights of intellectual property. Except as explicitly provided in the Software License Agreement, Motorola does not grant to Customer, either directly or by implication, estoppel, or otherwise, any right, title or interest in Motorola s Proprietary Rights. Customer will not modify, disassemble, peel components, decompile, otherwise reverse engineer or attempt to reverse engineer, derive source code or create derivative works from, adapt, translate, merge with other software, reproduce, distribute, sublicense, sell or export the Software, or permit or encourage any third party to do so. The preceding sentence does not apply to Open Source Software which is governed by the standard license of the copyright owner PUBLIC RECORDS. Motorola understands that the public shall have access at all reasonable times to all documents and information pertaining to County contracts subject to the provision of Chapter 119, Florida Statutes, and agrees to allow access to such public records in accordance with Section , Florida Statutes. Failure by Motorola to grant such public access shall be grounds for immediate cancellation of this contract by the County. IF THE CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE CONTRACTOR S DUTY TO PROVIDE PUBIC RECORDS RELATING TO THIS CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT: (386) , penny_stanley@columbiacountyfla.com, PO BOX 1529, Lake City, FL Section 16 GENERAL 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 forty-five (45) 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 ASSIGNABILITY AND SUBCONTRACTING. Neither Party may assign this Agreement without the prior written consent of the other Party, except that Motorola may assign this Agreement to any of its affiliates or its right to receive payment without the prior consent of Customer. Motorola may subcontract any of the work, but subcontracting will not relieve Motorola of its duties under this Agreement 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 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 INDEPENDENT CONTRACTORS. Each Party will perform its duties under this Agreement as p. 99

15 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 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 GOVERNING LAW. This Agreement and the rights and duties of the Parties will be governed by and interpreted in accordance with the laws of the State of Florida 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 NOTICES. Notices required under this Agreement to be given by one Party to the other must be in writing and either personally delivered or sent to the address shown below by certified mail, return receipt requested and postage prepaid (or by a recognized courier service, such as Federal Express, UPS, or DHL), or by facsimile with correct answerback received, and will be effective upon receipt: Motorola Solutions, Inc. Attn: Judy Jean-Pierre, Sr. Counsel Legal, Corporate Affairs & Government Affairs 500 West Monroe Street, 43rd Floor Chicago, IL Judy.Jean-Pierre@motorolasolutions.com Columbia County Attn: 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 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 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. p. 100 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents xi

16 The Parties hereby enter into this Agreement as of the Effective Date. This Agreement may be executed by each of the Parties hereto in separate counterparts, and shall have the same legal force and effect as if the Parties had executed it as a single document. The parties may sign in writing, or by electronic signature, including by . An electronic signature, or a facsimile copy or computer image, such as a PDF or tiff image, of a signature, shall be treated as and shall have the same effect as an original signature. In addition, an electronic signature, a true and correct facsimile copy or computer image of this Agreement shall be treated as and shall have the same effect as an original signed copy of this document. Motorola Solutions, Inc. Columbia County Board of Commissioners By: Name: Title: Date: By: Name: Title: Date: p. 101

17 Exhibit A SOFTWARE LICENSE AGREEMENT This Exhibit A Software License Agreement ("Agreement") is between Motorola Solutions, Inc. ( Motorola") and Columbia County Board of County Commissioners, Florida ( Licensee ). For good and valuable consideration, the parties agree as follows: Section 1 DEFINITIONS 1.1 Designated Products means products provided by Motorola to Licensee with which or for which the Software and Documentation is licensed for use. 1.2 Documentation means product and software documentation that specifies technical and performance features and capabilities, and the user, operation and training manuals for the Software (including all physical or electronic media upon which such information is provided). 1.3 Open Source Software means software with either freely obtainable source code, license for modification, or permission for free distribution. 1.4 Open Source Software License means the terms or conditions under which the Open Source Software is licensed. 1.5 Primary Agreement means the agreement to which this exhibit is attached. 1.6 Security Vulnerability means a flaw or weakness in system security procedures, design, implementation, or internal controls that could be exercised (accidentally triggered or intentionally exploited) and result in a security breach such that data is compromised, manipulated or stolen or the system damaged. 1.7 Software (i) means proprietary software in object code format, and adaptations, translations, de-compilations, disassemblies, emulations, or derivative works of such software; (ii) means any modifications, enhancements, new versions and new releases of the software provided by Motorola; and (iii) may contain one or more items of software owned by a third party supplier. The term "Software" does not include any third party software provided under separate license or third party software not licensable under the terms of this Agreement. Section 2 SCOPE Motorola and Licensee enter into this Agreement in connection with Motorola's delivery of certain proprietary software or products containing embedded or pre-loaded proprietary software, or both. This Agreement contains the terms and conditions of the license Motorola is providing to Licensee, and Licensee s use of the proprietary software and related documentation. Section 3 GRANT OF LICENSE 3.1. Subject to the provisions of this Agreement and the payment of applicable license fees, Motorola grants to Licensee a personal, limited, non-transferable (except as permitted in Section 7) and non-exclusive license under Motorola s copyrights and Confidential Information (as defined in the Primary Agreement) embodied in the Software to use the Software, in object code form, and the Documentation solely in connection with Licensee's use of the Designated Products. This Agreement does not grant any rights to source code If the Software licensed under this Agreement contains or is derived from Open Source Software, the terms and conditions governing the use of such Open Source Software are in the Open Source Software Licenses of the copyright owner and not this Agreement. If there is a conflict between the terms and conditions of this Agreement and the terms and conditions of the Open Source Software Licenses governing Licensee s use of the Open Source Software, the terms and conditions of the p. 102 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents xiii

18 license grant of the applicable Open Source Software Licenses will take precedence over the license grants in this Agreement. If requested by Licensee, Motorola will use commercially reasonable efforts to: (i) determine whether any Open Source Software is provided under this Agreement; and (ii) identify the Open Source Software and provide Licensee a copy of the applicable Open Source Software License (or specify where that license may be found). Section 4 LIMITATIONS ON USE 4.1. Licensee may use the Software only for Licensee's internal business purposes and only in accordance with the Documentation. Any other use of the Software is strictly prohibited. Without limiting the general nature of these restrictions, Licensee will not make the Software available for use by third parties on a "time sharing," "application service provider," or "service bureau" basis or for any other similar commercial rental or sharing arrangement 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 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 Licensee will maintain, during the term of this Agreement and for a period of two years thereafter, accurate records relating to this license grant to verify compliance with this Agreement. Motorola or an independent third party ( Auditor ) may inspect Licensee s premises, books and records, upon reasonable prior notice to Licensee, during Licensee s normal business hours and subject to Licensee's facility and security regulations. Motorola is responsible for the payment of all expenses and costs of the Auditor. Any information obtained by Motorola and the Auditor will be kept in strict confidence by Motorola and the Auditor and used solely for the purpose of verifying Licensee's compliance with the terms of this Agreement. Section 5 OWNERSHIP AND TITLE Motorola, its licensors, and its suppliers retain all of their proprietary rights in any form in and to the Software and Documentation, including, but not limited to, all rights in patents, patent applications, inventions, copyrights, trademarks, trade secrets, trade names, and other proprietary rights in or relating to the Software and Documentation (including any corrections, bug fixes, enhancements, updates, modifications, adaptations, translations, de-compilations, disassemblies, emulations to or derivative works from the Software or Documentation, whether made by Motorola or another party, or p. 103

19 any improvements that result from Motorola s processes or, provision of information services). No rights are granted to Licensee under this Agreement by implication, estoppel or otherwise, except for those rights which are expressly granted to Licensee in this Agreement. All intellectual property developed, originated, or prepared by Motorola in connection with providing the Software, Designated Products, Documentation or related services, remains vested exclusively in Motorola, and Licensee will not have any shared development or other intellectual property rights. Section 6 LIMITED WARRANTY; DISCLAIMER OF WARRANTY 6.1. Unless otherwise stated in the Primary Agreement, 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. Notwithstanding, any warranty provided by a copyright owner in its standard license terms will flow through to Licensee for third party software provided by Motorola. 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 Warranty claims are described in the Primary Agreement The express warranties set forth in this Section 6 are in lieu of, and Motorola disclaims, any and all other warranties (express or implied, oral or written) with respect to the Software or Documentation, including, without limitation, any and all implied warranties of condition, title, non- infringement, merchantability, or fitness for a particular purpose or use by Licensee (whether or not Motorola knows, has reason to know, has been advised, or is otherwise aware of any such purpose or use), whether arising by law, by reason of custom or usage of trade, or by course of dealing. In addition, Motorola disclaims any warranty to any person other than Licensee with respect to the Software or Documentation. Section 7 TRANSFERS Licensee will not transfer the Software or Documentation to any third party without Motorola's prior written consent. Motorola s consent may be withheld at its discretion and may be conditioned upon transferee paying all applicable license fees and agreeing to be bound by this Agreement. If the Designated Products are Motorola's radio products and Licensee transfers ownership of the Motorola radio products to a third party, Licensee may assign its right to use the Software (other than CPS and Motorola's FLASHport software) which is embedded in or furnished for use with the radio products and the related Documentation; provided that Licensee transfers all copies of the Software and Documentation to the transferee, and Licensee and the transferee sign a transfer form to be provided by Motorola upon request, obligating the transferee to be bound by this Agreement. Section 8 TERM AND TERMINATION 8.1 Licensee s right to use the Software and Documentation will begin when the Primary p. 104 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents xv

20 Agreement is signed by both parties and will continue for the life of the Designated Products with which or for which the Software and Documentation have been provided by Motorola, unless Licensee breaches this Agreement, in which case this Agreement and Licensee's right to use the Software and Documentation may be terminated immediately upon notice by Motorola. 8.2 Within thirty (30) days after termination of this Agreement, Licensee must certify in writing to Motorola that all copies of the Software have been removed or deleted from the Designated Products and that all copies of the Software and Documentation have been returned to Motorola or destroyed by Licensee and are no longer in use by Licensee. 8.3 Licensee acknowledges that Motorola made a considerable investment of resources in the development, marketing, and distribution of the Software and Documentation and that Licensee's breach of this Agreement will result in irreparable harm to Motorola for which monetary damages would be inadequate. If Licensee breaches this Agreement, Motorola may terminate this Agreement and be entitled to all available remedies at law or in equity (including immediate injunctive relief and repossession of all non-embedded Software and associated Documentation unless Licensee is a Federal agency of the United States Government). Section 9 Commercial Computer Software 9.1 U.S. GOVERNMENT END USERS. The Software, Documentation and updates are commercial items as that term is defined at 48 C.F.R. Part 2.101, consisting of commercial computer software and computer software documentation as such terms are defined in 48 C.F.R. Part (a)(1) and 48 C.F.R. Part (a)(5), and used in 48 C.F.R. Part and 48 C.F.R. Part , as applicable. Consistent with 48 C.F.R. Part , 48 C.F.R. Part , 48 C.F.R. Part through , 48 C.F.R. Part , and other relevant sections of the Code of Federal Regulations, as applicable, the Software, Documentation and Updates are distributed and licensed to U.S. Government end users: (i) only as commercial items, and (ii) with only those rights as are granted to all other end users pursuant to the terms and conditions contained herein. 9.2 If Licensee is licensing Software for end use by the United States Government or a United States Government agency, Licensee may transfer such Software license, but only if: (i) Licensee transfers all copies of such Software and Documentation to such United States Government entity or interim transferee, and (ii) Licensee has first obtained from the transferee (if applicable) and ultimate end user an enforceable end user license agreement containing restrictions substantially identical to the ones contained in this Agreement. Except as stated in the foregoing, Licensee and any transferee(s) authorized by this subsection 9.2 may not otherwise use or transfer or make available any Motorola software to any third party nor permit any party to do so. 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 11 LIMITATION OF LIABILITY The Limitation of Liability provision is described in the Primary Agreement. Section 12 NOTICES Notices are described in the Primary Agreement. Section 13 GENERAL COPYRIGHT NOTICES. The existence of a copyright notice on the Software will not be p. 105

21 construed as an admission or presumption of publication of the Software or public disclosure of any trade secrets associated with the Software 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 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 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 of Florida. 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 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 SURVIVAL. Sections 4, 5, 6.3, 7, 8, 9, 10, 11 and 13 survive the termination of this Agreement 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 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. p. 106 Columbia County, Florida Motorola Solutions Confidential Restricted July 31, 2017 Table of Contents xvii

22 Exhibit B Payment Schedule The Contract Price in U.S. dollars is. Customer will make payments to Motorola within thirty (30) days after the date of each invoice. Customer will make payments when due in the form of a check, cashier s check, or wire transfer drawn on a U.S. financial institution and in accordance with the following milestones. 1) 25% of Contract Value upon completion of Customer Detail Design Review; 2) 50% of Contract Value upon Shipment of Equipment; 3) 15% of Contract Value upon Installation of Equipment; and 4) 10% of Contract Value upon Final System Acceptance 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. For Extended Maintenance and Technology Refresh Plan Motorola will invoice Customer annually in advance of each year of the plan. The detailed costs can be found in Exhibit C. The total costs for the Extended Maintenance and Technology Refresh Plan for years 2 through 14 will be made in equal payments annualy to Motorola by the County. p. 107

23 Exhibit C Motorola s Negotiated Proposal, including C-1 through C-3 Columbia County, Florida p. 108

24 p. 109

25 PROPOSAL TO COLUMBIA COUNTY, FLORIDA SECTION 3 NEGOTIATED PROJECT MANAGEMENT PLAN, IMPLEMENTATION, SCHEDULE AND CUTOVER APCO P25 700MHZ RADIO SYSTEM PROJECT NOVEMBER 8, 2017 RFP-2017-O The design, technical, pricing and other information ( Information ) furnished with this submission is proprietary and/or trade secret information of Motorola Solutions, Inc. ( Motorola Solutions ) and is submitted with the restriction that it is to be used for evaluation purposes only. To the fullest extent allowed by applicable law, the Information is not to be disclosed publicly or in any manner to anyone other than those required to evaluate the Information without the express written permission of Motorola Solutions. MOTOROLA SOLUTIONS, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Solutions Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners Motorola Solutions, Inc. All rights reserved. p. 110

26 p. 111

27 TABLE OF CONTENTS Section 3 Project Management Plan, Implementation, Schedule and Cutover Project Management Plan Overview Risk Management Schedule Management Change Control Process Quality Management Subcontractor Management Implementation Plan General Information System Implementation Overview Communications Plan Project Team Communication Plan Elements Statement of Work Overview Contract Negotiation Contract Execution / Notice to Proceed (Milestone) Contract Administration Project Kickoff Detailed Site Walks Detailed Design Detailed Design Review Detailed Design Completed (Milestone) Develop Fleetmap Create Templates Manufacturing and Staging Order Processing Manufacture Motorola Solutions Fixed Network Equipment Manufacture Motorola Solutions Subscribers Manufacture Non-Motorola Solutions Equipment Stage System Perform Staging Acceptance Test Procedures for LMR and Microwave Customer Ship Acceptance (Milestone) Ship Equipment to Field Site Development and FNE Installation EOC Communications Room EOC Tower Site Columbia County, Florida p. 112 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover i

28 CCSO Site Deep Creek Site Cumorah Hill Site Lulu Site Franklin Site Greenfield Site System Installation Program and Distribute Portables Program and Install Mobiles Install Fixed Network Equipment Console Installation at EOC PSAP Control Station Installation System Installation Acceptance (Milestone) System Optimization Optimize System FNE Link Verification Optimization Complete Audit and Acceptance Testing Perform R56 Installation Audit Perform Equipment Testing Perform Functional Testing Perform Coverage Testing Training Perform Training Day Performance Test Perform 30-Day Performance Period Cutover Perform System Cutover Final System Acceptance Resolve Punch List Project Transition Certificate Finalize Documentation Final System Acceptance (Milestone) Project Administration Project Status Meetings Progress Milestone Submittal Change Order Process Sample Change Control Document Implementation Schedule Training Training Approach Proposed Courses ii Project Management Plan, Implementation, Schedule and Cutover Columbia County, Florida Motorola Solutions Confidential Restricted p. 113

29 3.4.3 Course Descriptions Cutover Plan Phase I Preliminary Cutover Plan Outline Cutover Steps Overview Identification of Prerequisites/Constraints/Assumptions Detailed Timeline/Sequence of Events Post-Cutover Strategy Phase II Migrate Trunking Infrastructure Existing System Decommission Columbia County, Florida p. 114 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover iii

30 p. 115

31 SECTION 3 PROJECT MANAGEMENT PLAN, IMPLEMENTATION, SCHEDULE AND CUTOVER 3.1 PROJECT MANAGEMENT PLAN Overview Columbia County, Florida Motorola Solutions, Inc. (Motorola Solutions) has been the market leader in mission-critical wireless communications for more than 87 years. We are proud to provide state, federal and local jurisdictions with quality products and integration services. Surveys show our customers consistently rate us very satisfied because we deliver high-quality projects that perform exceptionally. Systems Integration management is the reason for our favorable performance in this arena. Motorola Solutions uses an integrated approach to project management to deliver projects on time and on schedule. Our proven system integration skills have been successfully employed on over 1,100 mission-critical implementations of wireless communications systems, including 35 of the 41 statewide P25 system deployments Risk Management Motorola Solutions utilizes risk management processes during the project so that any impact to the project s overall cost and schedule are eliminated or minimized. During proposal development, use of the process ensures accurate system design and implementation. After the project starts, our established risk management process provides system awareness, analysis, assignment and answers. Our overall risk management objectives include: Minimize adverse events. Provide you with cost and schedule certainty from the very beginning of the project. Maintain commitments during project delivery. Establish an environment leading to positive results. Motorola Solutions risk management process serves to detect any problems that affect delivery or performance and if discovered, we rapidly develop an action plan, then execute and monitor it. We also continuously communicate this status to all system stakeholders Schedule Management Successful schedule management depends on these key approaches: Up-front schedule development using local understanding Real-time collaboration and communication with team members p. 116 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-1

32 Effective scope and change management Accurate and timely reporting A schedule must reflect all project work activities and their sequencing. We base our standard for schedule management on similar past projects, providing you with the most complete and accurate schedule possible. The schedule tracks tasks, milestones, start/end dates, predecessors, critical path and owners based on a work breakdown structure (WBS) agreed upon by both Columbia County and Motorola Solutions Change Control Process Fully understanding what is and is not included in the scope of the project is a critical element of a successful communications project. Our ability to analyze all the components of the work and how each component affects cost, schedule and performance defines Scope management. Our scope management methods put a strong emphasis on communications. We keep all project participants properly informed, so everyone can respond quickly and effectively. Up-front scope definition as part of the proposal process We have provided a complete Statement of Work that defines our proposed solution in detail. The County s RFP was very straightforward with regard to vendor requirement. We are confident that our turnkey proposal includes all deliverables and will meet the County s expectation for a complete response. Because we accurately and comprehensively scope projects as part of proposal development, our projects remove unforeseeable surprises for you. We do not under-scope your work, to provide the appearance of value, then change the costs or schedule during the project. Effective change management during project delivery - Due diligence during the proposal process reduces unforeseen scope creep. Based on the clarity of the RFP requirements and vendor responsibilities, Motorola Solutions is confident that the County will not experience scope creep if selected as your vendor partner. A key to our scope management success is our change management process. This approach enables us to respond effectively to customer requested changes, adapting our delivery schedule, resource allocation scheme and individual task assignments if you require a scope change. We keep all project participants properly informed, so everyone can respond quickly and effectively. Our change order process is an effective tool to record and manage changes in the contract whether it is functionality, deliverables, enhancements, schedule, or costs. When a change is required, Motorola Solutions analyzes the potential impact to the entire project and determines whether any adjustments within the project can be made to scope, schedule, or costs to mitigate or neutralize or offset the impact of the change. A sample change order form is included in Section below Quality Management We are the quality leader in the communications systems industry. We are the first two-time recipient of the Malcolm Baldrige National Quality Award, the nation s most prestigious recognition for corporate excellence. We invented Six Sigma in 1986 as an internal metric for measuring defects and improving quality. Since then, it has become an industry-standard, recognized as a robust business improvement methodology. Six Sigma helps focus an organization on its customer requirements, process alignment, analytical rigor and timely execution. Motorola Solutions Standards and Guidelines for Communication Sites (R56) define our quality equipment installation processes. These standards for high quality system implementation are used throughout the industry. 3-2 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 117

33 3.1.6 Subcontractor Management Columbia County, Florida Our project management philosophy ensures that our subcontractors and third-party suppliers follow the same high quality standards as Motorola Solutions. We ensure all subcontractors are experienced and have a successful performance history with Motorola Solutions. We will utilize minimal subcontractor participation for delivery of the County s system. Specifically, our subcontractors will perform structural analysis of existing towers, limited electrical improvements and installation/removal of antenna networks. We have been the prime contractor for the majority of our successful public safety communications systems. During this time, through the careful up-front selection of our subcontractors, the rigorous oversight of their work and the integration of their team members as part of our core customer project team, we have achieved continued success. We will work with subcontractors to bring the total system solution to the County. Each of these subcontractors will supply unique skill sets and expertise. Table 3-1 outlines their contribution. Task Table 3-1: Subcontractor Responsibilities Responsibility Mobile Communications Fixed Network Equipment Installation Dispatch Center Installation Subscriber Installation and Programming Aviat Microwave Installation / Configuration Services Clifton s Tower Service Antenna Installation/Removal Implementation Plan General Information This Implementation Plan defines the principal activities and responsibilities of all parties for the implementation of the ASTRO 25 system for the County System Implementation Overview Motorola Solutions proposal to the County provides systems integration and implementation services to deploy a fully functional communications system. Motorola Solutions experience as a system integrator, deploying large and complex communication and software systems, will ensure a smooth system implementation and cutover to the new communications system. A Phased Approach to Implementation Motorola Solutions will provide the County with an implementation approach that includes the following phases: Project Initiation and Kickoff Design Review Order Processing, Manufacturing, Staging and Factory Testing Site Development Infrastructure Installation Systems Integration and Optimization p. 118 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-3

34 Coverage and Functional Acceptance Testing Training of Technicians and End Users 30-Day Performance Period and Cutover Project Finalization System Warranty Support Project Initiation, Kickoff and Design Review Motorola Solutions has provided a RFP-compliant design as a part of this proposal, which serves as a baseline for the Design Review. The Design Review encompasses the design finalization of the major subsystems, such as finalization of the site requirements, coverage design and FCC licensing tasks. Additionally, during this review, we will work closely with the County to finalize a detailed cutover plan to transition to the new communications system. Detailed Design Documents will be given to the County at the end of the Design Review phase. Order Processing, Manufacturing, Staging and Factory Testing Factory staging of the radio infrastructure follows equipment manufacturing at Motorola Solutions Customer Center for Solutions Integration (CCSi) in Elgin, Illinois. Factory staging provides for initial assembly and testing of all radio system components. Factory staging will allow complete testing of the functional capabilities of the communications system. We will stage all new equipment, which will provide a high ability to verify the system functionality of the new equipment. This process will allow the County to witness factory testing in a controlled environment, as well as provide for a smooth and easy field installation. Site Development Review The detailed SOW for each site is included below providing an overview of site deliverables and responsibilities for both Motorola Solutions and the County during the project implementation. Prior to the completion of Detailed Design Review (DDR), we will re-visit all existing sites to be utilized for the proposed County system to develop updated documentation. At the DDR, Motorola Solutions will submit the following to the County: Electrical load calculations Equipment enclosure drawings Site layout Antenna placement drawing Grounding layout Upon approval of the site design documentation and drawings and upon issuance to proceed by the County, we will move forward with the County project. To meet the County s project timeline, we will begin electrical upgrades and antenna network installations while the manufacturing and staging process is underway, so that the sites will be ready for installation when the equipment ships from the Motorola Solutions staging facility. 3-4 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 119

35 We will conduct a final site inspection along with a County representative for its readiness to install radio communications equipment. Installation and Testing Our local implementation team will install, optimize and test the system at the defined sites as staged at CCSi. Our implementation includes the integration of all proposed subsystems to provide an endto-end solution. To verify the delivered system s functionality, we will execute Acceptance Testing according to an Acceptance Test Plan (ATP). The ATP is a multi-stage plan that includes Factory Testing and Staging, Functional Acceptance Testing, Coverage Acceptance Testing and 30-Day Performance Period. Sample functional acceptance test plans (both Motorola Solutions and Aviat microwave) are included in Section 9, Appendix. A guaranteed coverage acceptance test plan is included in Section 4, Technical Solution. Training and Cutover Following Functional Acceptance Testing, Motorola Solutions and the County will begin the cutover to the new system. Motorola Solutions and the County will coordinate training with the cutover schedule to ensure a smooth transition to the new communications system. Details of the preliminary cutover plan follow in Section 0. Final Acceptance and Warranty Support The final steps to full system implementation are the delivery of system documentation, punchlist resolution and final acceptance. The project team and the post-acceptance service team will work with the County during this phase to ensure a smooth transition to the post-acceptance support period Communications Plan Project Team An effective communications plan between the Motorola Solutions project team and County representatives is critical to the success of the County s project. Effective team integration occurs only when everyone is operating with the same information and all share information in a timely and effective manner. The Motorola Solutions Project Manager will be the focal point for all communications between the County and Motorola Solutions during the system implementation phase of the project. Motorola Solutions Communication Plan will identify the key stakeholders and project team members on the County project. The key communication tool will be our dedicated Project Manager supported by on-site meetings, , status reports, phone and websites. These tools will be used by the project team to inform and report on progress during the project. Project Manager Project team members who will interact with the County are subject to reasonable approval by the County. There will be a Motorola Solutions Project Manager, Systems Engineer, System Technologist, as well as other integration partners. Motorola Solutions will designate a Project Manager who will direct Motorola Solutions efforts and serve as the primary point of contact for the County. The Motorola Solutions Project Manager has the overall responsibility for the delivery and implementation of the system and management of the Motorola Solutions responsibilities pursuant to the performance schedule and budget. The PM will coordinate the Motorola Solutions Project Team s role for installation and implementation. The p. 120 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-5

36 Motorola Solutions Project Manager responsibilities are outlined in Table 3-1. Task Table 3-1: Project Manager Responsibilities Responsibility Project Ownership Primary point of Contact for the County Significant authority within Motorola Solutions Motorola Solutions Executive Management access Project Communication Attend regular Project meetings as scheduled Generate meeting minutes for each Project meeting within 3 days of the respective meeting Produce a running log of Project issues and punch list items Provide written monthly status reports in draft and final forms in a format approved by the County no later than the 5th business day after the end of each month Archive all Project correspondence to be supplied with final system documentation Provide written Schedule updates to the County every 14 days as required using Microsoft Project conforming to the County s formatting and content requirements and transmitted to the County in electronic PDF format Project Schedule Maintain the Project Schedule based on the approved WNS. Report status and deviations/mitigation. Project Plan Management of subcontractors. Management of Motorola Solutions labor. Coordination of activities with the County. Risk Management Ownership of the Project Risk Plan Maintain the action item log. Resolution and reporting of issues. Quality Assurance Coordinate all system and acceptance tests with the County. Maintain the agreed upon action log Resolution and reporting of issues. R56 Quality Installations. Project Engineer We will designate a Project Engineer who will lead the engineering and design personnel assigned to the project. The engineering team will interface with our factory engineers and plant production managers to ensure proper delivery for the required specification and functionality. The Project Engineer will be the primary technical point of contact for the County. Project Engineer responsibilities are outlined in Table Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 121

37 Table 3-2: Motorola Solutions Project Engineer Responsibilities Task Responsibility Design Ownership Technical point of Contact for the County Significant authority within Motorola Solutions Access to product engineering teams Detailed Design Document Documenting the Detailed System Design Design for Eltek DC Power Aviat Microwave backhaul NICE Logging Recorders Implementation RF Frequency Plan MW Coordination Fleet-mapping Factory Staging System Optimization Acceptance Planning Work with County to create test plans for: System Technologist Factory Test Component Test Functional Test Coverage Test 30 Day Performance Period The lead Systems Technologist (ST) is responsible for assuring that the system is tested and optimized to perform as designed. The lead ST oversees the team of technologists responsible for all sub-systems and the integration of those sub-systems into the final system. System Technologist responsibilities are outlined in Table 3-3. Table 3-3: System Technologist Responsibilities Task Responsibility Staging Configuration and test the system at Motorola Solutions Customer Center for Solutions Integration (CCSi). Site Links Ensure site link verification testing occurs to validate connectivity and adequate performance at RF sites. Integration and Optimization Oversee the integration and optimization of all system hardware and software, which includes programming, configuration and optimization of RF equipment, optimization of the consoles, acceptance testing, Motorola Solutions R56 site audits and development of the system cutover plan. Site Design Manager The Site Design Manager is responsible for supporting Sales and Project Management with the effective design and implementation of site development/civil construction solutions for communications systems. Site Design Manager s responsibilities are outlined in Table 3-5. p. 122 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-7

38 Task Table 3-5: Site Design Manager Responsibilities Responsibility Design Design antenna and electrical solutions in support of complex communications systems and information solutions for the public sector and business critical enterprise customers. Implementation Implement site development solutions within the customers required time frame and budget given communication system equipment requirements and site specific limitations. Customer Service Manager The Customer Service Manager (CSM) is responsible for development of the proposed service delivery and customer support plans for the warranty and extended maintenance during the maintenance program. Customer Service Manager responsibilities are outlined in Table 3-6. Table 3-6: Customer Service Manager Responsibilities Task Responsibility Service Plan Develop service delivery plan. Develop customer support plan. Customize plans the meet needs of the County. Support The CSM will work with the County s System Manager during the transition from implementation to warranty and from warranty to post warranty maintenance to ensure that Motorola Solutions service support is continuous and provided with the highest degree of satisfaction. We have carefully selected an experienced project team with firsthand knowledge of the County, both technically and operationally; understanding both local and regional considerations. Resumes of key project team members are included in Section 6 Project Team, Qualifications, Experience and Capabilities Communication Plan Elements Escalation Procedures The initial escalation process for the County will be through the Motorola Solutions Project Manager. The Project Manager will have significant authority to make certain decisions relative to the project on behalf of Motorola Solutions and has full authority and direct access to our executive management and resources for resolving problems beyond his immediate authority. Weekly and Bi-Weekly Meetings Motorola Solutions will host regular project meetings as required and agreed upon by the County. Meeting Cycles Motorola Solutions agrees that a regular weekly project meeting should begin immediately after contract signing. Additional meetings to be scheduled as required or requested by the County. 3-8 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 123

39 Meeting Agendas Motorola Solutions will prepare meeting agendas that address project issues updates, schedule status, action and open items for the next meeting. Meeting Report Motorola Solutions will generate meeting minutes for each project meeting within three days of the respective meeting. The report will include a running log of project issues and punchlist item, noting progress to date, meetings held, schedule adherence and variances. Meeting Attendees Motorola Solutions attendees will include Project Manager, Lead System Engineering, Lead System Technologist and County representatives, as determined by the County. Project Status Reports Status reports will highlight any potential issues and identify mitigation action(s). Individuals will own action items and track completion dates to ensure the items are completed. Status reports will also be used to provide the County an accurate assessment of the progress of the project and give visibility to the resource requirements to complete the near term tasks. To identify and resolve identified items, action item lists are maintained and updated on a weekly basis. Status Report Cycle No later than five days after the end of the preceding month, a final monthly report is provided to the County. The Project Manager will provide written schedule updates to the County project team every 14 days, as required, using Microsoft Project conforming to the County s formatting and content requirements and transmitted to Project Manager in both hardcopy and soft format. Status Report Content The status report will include the project status, milestones achieved, action items, tasks behind schedule and actual and potential problems. A written report of any corrected punchlist items will be included. The status report will include next steps and activity schedule for the following month. Status Report Recipients Lead Engineer, Lead System Technologist, Service representatives, impacted subcontractors and the appropriate County representatives and stakeholders will receive status reports. Secure Web Site for Document Sharing All project documentation will be stored on and retrieved from a Motorola Solutions shared website. The County will have online access to project documents such as schedules, status reports, risk logs, requirements documents and change requests. Version control will ensure that the most current documentation and all past versions are available for review. p. 124 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-9

40 3.2 STATEMENT OF WORK Overview Motorola Solutions has based the system design on strict adherence to your RFP requirements. This Statement of Work (SOW) describes the implementation deliverables provided to Columbia County. Motorola Solutions, our Sub-Contractors and Columbia County radio personnel will perform the tasks described herein to implement the solution described in the System Description. The document describes the actual work involved in installation and identifies the installation standards that are required. This SOW also clarifies the responsibilities for both Motorola Solutions and Columbia County during the project implementation. Specifically, this SOW provides: A summary of the phases and tasks for that are required for completion within the project lifecycle. A list of the deliverables associated with the project. Descriptions outlining the responsibilities for Motorola Solutions, our Subcontractors and Columbia County. An outline of assumptions and responsibilities to address any item that may need to be amended during the development of this project. This SOW provides the most current understanding of the work required by every party to ensure a successful project implementation. In particular, Motorola Solutions has made assumptions of the sites proposed for the new system. Should any of the sites change, a revision to the SOW and associated pricing will be required. Understand that this SOW is a working document and revision may be required to incorporate any changes associated with contract negotiations, Contract Design Review (CDR) and any other change orders that may occur during the execution of the project. The new RF trunking system will consist of one Simulcast cell with the main Master Core network, primary Dispatch Center, main Prime Site and Remote Site at the EOC. The backup Master Core network, backup Prime Site and Remote Site will be located at Deep Creek. Additional Remote RF Sites will be installed at CCSO, Cumorah Hill, Lulu and the Greenfield Site. The proposed Countywide Simulcast network consists of the following sites: EOC Communications Room: Main Master Core Network, Dispatch Network Equipment, Main Prime Site Equipment, EOC Tower Site: Five (5) TDMA/FDMA RF Channels EOC PSAP: Dispatch Consoles CCSO: Five (5) TDMA/FDMA RF Channels Deep Creek: Backup Master Core Network, Backup Prime Site Equipment, Remote Site Equipment, and five (5) TDMA/FDMA RF Channels Cumorah Hill: Remote Site Equipment, five (5) TDMA/FDMA RF Channels Lulu: Remote Site Equipment, five (5) TDMA/FDMA RF Channels Greenfield Site: Tower, Shelter, Remote Site Equipment, five (5) TDMA/FDMA RF Channels The Primary Dispatch Center will be located at the Columbia County EOC and will consist of nine (9) IP-based MCC 7500E operator dispatch positions, nine (9) backup control stations and nine (9) mobile MCC 7100 operator dispatch laptops. Each dispatch position will be capable of accessing the new 700 MHz ASTRO P25 IP Simulcast Trunked system in addition to the legacy stations outlined in the RFP. The existing VHF paging network will be integrated into the new console system Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 125

41 Infrastructure features include inter-system gateway (ISSI) for P25 interoperability with neighboring P25 systems, mutual aid interoperability base radios, WAVE Smartphone Talkgroup interface, link layer radio authentication and P25 Integrated Voice & Data for Over-the-air-programming and Location services. The programming and installation of multiple tiers of portables, mobiles and control stations are included as well Contract Negotiation Contract Execution / Notice to Proceed (Milestone) Columbia County and Motorola Solutions execute the contract and both parties receive all the necessary documentation. Within 10 days of the Effective Date of the Communications System Agreement executed by Motorola Solutions and the County, Motorola Solutions will furnish to the County, a performance and payment bond in the full amount of the Contract Price as security for the faithful performance of Motorola Solutions obligations under the Communications System Agreement Contract Administration Motorola Solutions Responsibilities: Assign a Project Manager, as the single point of contact with authority to make project decisions. Assign resources necessary for project implementation. Set up the project in the Motorola Solutions information system. Schedule the project kickoff meeting with the County. Columbia County Responsibilities: Assign a Project Manager, as the single point of contact responsible for County-signed approvals. Assign other resources necessary to ensure completion of project tasks for which Columbia County is responsible. Completion Criteria: Motorola Solutions internal processes are set up for project management. Both Motorola Solutions and the County assign all required resources. Project kickoff meeting is scheduled Project Kickoff Motorola Solutions Responsibilities: Conduct a project kickoff meeting during the CDR phase of the project. Ensure key project team participants attend the meeting. Introduce all project participants attending the meeting. Review the roles of the project participants to identify communication flows and decision-making authority between project participants. Review the overall project scope and objectives with the County. Review the resource and scheduling requirements with the County. Review the Project Schedule with the County to address upcoming milestones and/or events. Review the teams interactions (Motorola Solutions and the County), meetings, reports, milestone acceptance and the County s participation in particular phases. p. 126 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-11

42 Columbia County Responsibilities: The County s key project team participants attend the meeting. Review Motorola Solutions and County responsibilities. Completion Criteria: Project kickoff meeting completed. Meeting notes identify the next action items Detailed Site Walks Motorola Solutions Responsibilities: Perform detailed site audit. Columbia County Responsibilities: Provide access to all sites for Motorola Solutions personnel. If required, proved a resource from the County to escort Motorola Solutions representative(s). Completion Criteria: Site audit completed Detailed Design Detailed Design Review Motorola Solutions Responsibilities: Meet with the County project team. Review the operational requirements and the impact of those requirements on various equipment configurations. Review the System Design, Statement of Work, Project Schedule and Acceptance Test Plans and update the contract documents accordingly. Discuss the proposed Cutover Plan and methods to document a detailed procedure. Submit design documents to the County for approval. These documents form the basis of the system, which Motorola Solutions will manufacture, assemble, stage and install. Incorporate any system design options selected. Prepare equipment layout plans for staging. Finalize site development plan. Determine each site s ability to accommodate proposed equipment based upon physical capacity. Test existing equipment with which Motorola Solutions equipment will interface. Obtain new frequency licensing to include 700 MHz FDMA/TDMA. Restrictions: Motorola Solutions is not responsible for issues outside of its immediate control. Such issues include, but are not restricted to non-compliant operation of other radios. Motorola Solutions 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 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 127

43 Columbia County Responsibilities: The County s key project team participants attend the meeting. Make timely decisions, according to the Project Schedule. Confirm Site locations. Confirm Microwave design. Completion Criteria: Complete Design Documentation, which may include updated System Description, Equipment List, system drawings, or other documents applicable to the project. Incorporate any deviations from the proposed system into the contract documents accordingly. The system design is frozen in preparation for subsequent project phases such as Order Processing and Manufacturing. If necessary, a Change Order is executed in accordance with all material changes resulting from the Design Review to the contract. Customer approval of Detailed Design Detailed Design Completed (Milestone) The County executes a Design Approval milestone document Develop Fleetmap Motorola Solutions Responsibilities: Schedule required meeting(s) with the appropriate Columbia County representatives/agencies. Meet with the County s user groups. Provide details on the features and functionality of the Motorola Solutions equipment/system. Work with the County and participating agencies to develop and obtain approval of the fleetmap for the system. Program the infrastructure equipment, subscribers, terminals and any other radio system FNE, based on fleetmap. Columbia County Responsibilities: Designate a representative for the user groups, to make timely decisions on their behalf. Identify the County s System Manager who will set up a steering committee consisting of various members from user groups. The System Manager, with the help of the steering committee, will be responsible for setting standardized system management and operational policies (SOP) that will apply to all users. A sample of SOP committee decisions includes: User Access Management Protocol User Database Management Protocol System Security Protocol Subscriber Radio Standards Configure, Manage and Control the Fleetmap Database. User group reviews its radio standard operational policies and then determines what modifications will be required, if any. Create a Console Dispatch and Radio Programming Policy to decide how each Subscriber group will operate on the system and what features will be activated. User group representative(s) makes Fleetmap programming decisions. p. 128 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-13

44 Complete the initial fleetmapping process prior to staging of the system. Completion Criteria: Fleetmap requirements completed and approved by the County Create Templates Motorola Solutions Responsibilities: Motorola Solutions will develop console templates for the Dispatch Center: Elite Supervisor Elite Operator Motorola Solutions will develop radio templates for the fleet of subscribers: Public Safety Mobiles Public Safety Portables Local Government Mobiles Local Government Portables Motorola Solutions participates in a meeting to finalize any changes among user groups. Program the approved templates into a radio-programming template tool. Program sample radios with approved templates and deliver for the Customer evaluation. Columbia County Responsibilities: User groups create templates in a spreadsheet format. Forward electronic copies of the spreadsheets to the committee members for their review and comment. Evaluate sample radios and provide feedback. Approve templates. Completion Criteria: Templates completed and approved by Columbia County Manufacturing and Staging Order Processing Motorola Solutions Responsibilities: Validate Equipment List by checking for valid model numbers, versions and compatible options to main equipment and delivery data. Enter order into Motorola Solutions Customer Order Fulfillment (COF) system. Create Ship Views, to confirm with the County the secure storage location(s) to which the equipment will ship. Ship Views are the mailing labels that carry complete equipment shipping information, which direct the timing, method of shipment and ship path for ultimate destination receipt. Create equipment orders. Reconcile the equipment list(s) to the Contract. Procure third-party equipment. Columbia County Responsibilities: Approve shipping location(s). Complete and provide Tax Certificate information verifying tax status of shipping location Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 129

45 Completion Criteria: Verify that the Equipment List contains the correct model numbers, version, options and delivery data. Trial validation completed. Bridge the equipment order to the manufacturing facility Manufacture Motorola Solutions Fixed Network Equipment Motorola Solutions Responsibilities: Manufacture the Fixed Network Equipment (FNE) necessary for the system based on equipment order. Columbia County Responsibilities: None Completion Criteria: FNE shipped to either the field or the staging facility Manufacture Motorola Solutions Subscribers Motorola Solutions Responsibilities: Manufacture the subscribers necessary for the system, based on equipment order and project schedule. Columbia County Responsibilities: None Completion Criteria: Subscribers (mobile or portable radios) shipped to the field Manufacture Non-Motorola Solutions Equipment Motorola Solutions Responsibilities: Procure non-motorola Solutions equipment necessary for the system based on equipment order. Columbia County Responsibilities: None Completion Criteria: Ship non-motorola Solutions manufactured equipment to the field and/or the staging facility Stage System Motorola Solutions Responsibilities: Kick-off Staging effort with call between Field and CCSi teams to collect staging documentation (i.e. system description, equipment lists, rack diagrams, etc.). Set up and rack the system equipment on a site-by-site basis, in planned field configuration at each of the transmitter/receiver sites. p. 130 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-15

46 Cut and label cables according to the approved CDR documentation. Label the cables with to/from information to specify interconnection for field installation and future servicing needs. Complete the cabling/connecting of the subsystems to each other. Assemble required subsystems to assure system functionality. Power up, program and test all staged equipment. Confirm system configuration and software compatibility to the existing system. Load application parameters on all equipment according to input from Systems Engineering. Complete programming of the Fixed Network Equipment. Program the approved templates into a radio-programming template tool. Complete programming of sample Subscriber units. Inventory the equipment with serial numbers and installation references. Complete system documentation. Third party subsystems may be staged at the manufacturer s facilities and integrated in the field. Provide a Factory Acceptance Test Plan. Columbia County Responsibilities: Provide information on existing system interfaces as may be required. Provide information on room layouts or other information necessary for the assembly to meet field conditions. Review and approve proposed Factory Acceptance Test Plan. Completion Criteria: System staging completed and ready for testing Perform Staging Acceptance Test Procedures for LMR and Microwave Motorola Solutions Responsibilities: Test and validate system software and features. Functional testing of standard system features. Conduct site and system level testing. Perform system burn-in 24 hours a day during staging to isolate and capture any defects. Perform County-witnessed tests based upon Factory Acceptance Test Plan. Columbia County Responsibilities: Attend Factory Acceptance Testing. Pay for travel, lodging, meals and all incidental expenses for Columbia County personnel and representatives to witness the Factory Acceptance Testing. Approve Factory Acceptance Testing Customer Ship Acceptance (Milestone) Equipment audited and prepared for shipment to the field Ship Equipment to Field Motorola Solutions Responsibilities: Pack system for shipment to final destination Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 131

47 Arrange for shipment to the field. Columbia County Responsibilities: None Completion Criteria: All equipment shipped to the field Site Development and FNE Installation EOC Communications Room Site Scope Summary Utilize the existing EOC building for Dispatch communications. Motorola Responsibilities: Equipment Installation and Optimization RF fixed network and console backroom electronics. Facility Improvement Work Supply and install new conduit and wiring from existing UPS panel E to new UPS panel in the communications room. Install new 3p/100amp breaker in existing UPS panel E. Install new 100amp/3ph/5w feed from Panel E to new UPS panel. Provide and install (1) new 225amp/42cir/ v/3ph panel board with (42) 1p/20a breakers and (1) new 100a/3p main breaker. Install new 1" emt conduit and #12 wire from new UPS panel to (5) owner provided OP8 outlet panels. Install new flexible conduits and wire from ceiling boxes to new OP8's Ground all new panels, conduit and OP8's to #2 ground cable that runs back to existing MGB. On a return trip install new conduit from newly installed UPS panel with 2 circuits to 6th OP8. Reroute (6) circuits from old UPS panel to 6th OP8. Ground new OP EOC Tower Site Site Scope Summary Existing 300 self-supporting tower and 12x12 shelter to be utilized. Motorola Responsibilities: Equipment Installation and Optimization RF fixed network and microwave equipment. Supply and install new antenna system and customer supplied VHF mutual aid station (The VHF antenna only will be provided by the County). Optimize VHF mutual aid station and integrate its operation into the new dispatch console system. Antenna and Transmission Line Installation and Optimization Install two (2) antenna(s) for the RF system. p. 132 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-17

48 Install two (2) 6-foot side arm(s) for antenna mounts. Install one (1) tower top amplifier(s). Install required linear feet of 1/2-inch transmission line. Install required linear feet of 7/8-inch transmission line. Install required linear feet of 1-5/8-inch transmission line. Install two (2) microwave dishes with radomes. Install required linear feet of elliptical waveguide. Perform sweep tests on transmission lines. Facility Improvement Work Install DC Power System. Site Engineering: Motorola Solutions has performed the tower reanalysis report and has included it in Section 9.2 in the Appendix. 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 CCSO Site Site Scope Summary Existing 154 self-supporting tower and 12x12 shelter to be utilized. Motorola Responsibilities: Equipment Installation and Optimization RF fixed network and microwave equipment. Antenna and Transmission Line Installation Install two (2) antenna(s) for the RF system. Install two (2) heavy-duty mount(s) for antennas. Install one (1) tower top amplifier(s). Install required linear feet of 1/2-inch transmission line. Install required linear feet of 7/8-inch transmission line. Install required linear feet of 1-5/8-inch transmission line. Install two (2) microwave dishes with radomes. Install required linear feet of elliptical waveguide. Perform sweep tests on transmission lines. Facility Improvement Work Install DC Power System. Site Engineering: Motorola Solutions has performed the tower reanalysis report and has included it in Section 9.2 in the Appendix Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 133

49 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 Deep Creek Site Site Scope Summary Existing 300 self-supporting and 12x12 shelter to be utilized. Motorola Responsibilities: Equipment Installation and Optimization RF fixed network and microwave. Supply and install new antenna systems for customer supplied VHF simulcast paging and VHF mutual aid station (The VHF antennas only will be provided by the County). Optimize both VHF simulcast paging and mutual aid stations and integrate their operation into the new dispatch console system. Antenna Installation Install two (2) antenna(s) for the RF system. Install two (2) heavy-duty mount(s) for antennas. Install one (1) tower top amplifier(s). Install required linear feet of 1/2-inch transmission line. Install required linear feet of 7/8-inch transmission line. Install required linear feet of 1-5/8-inch transmission line. Install three (3) microwave dishes with radomes. Install required linear feet of elliptical waveguide. Perform sweep tests on transmission lines. Facility Improvement Work Supply and install amp breakers in the distribution panel and wire to designated outlets. Supply and install four (4) each 40-amp breakers in the distribution panel and wire to designated outlets. Install one (1) 8' long outlet bars made from 2-channel wire mold panel (8 inches wide) supported on threaded bars of the cable tray using insulated standoffs and wire each outlet to individual breaker. Install one (1) new single-phase UPS. Install DC Power System. Site Engineering: Motorola Solutions has performed the tower reanalysis report and has included it in Section 9.2 in the Appendix. 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. p. 134 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-19

50 Cumorah Hill Site Lulu Site Site Scope Summary Existing 315 guyed tower and 10x15 shelter to be utilized. Motorola Responsibilities: Equipment Installation and Optimization RF fixed network and microwave equipment. Optimize VHF mutual aid station and integrate its operation into the new dispatch console system. Optimize VHF Simulcast paging station and integrate its operation into the new dispatch console system. Antenna and Transmission Line Installation Install two (2) antenna(s) for the RF system. Install two (2) 6-foot side arm(s) for antenna mounts. Install one (1) tower top amplifier(s). Install required linear feet of 1/2-inch transmission line. Install required linear feet of 7/8-inch transmission line. Install required linear feet of 1-5/8-inch transmission line. Install two (2) microwave dishes with radomes. Install required linear feet of elliptical waveguide. Perform sweep tests on transmission lines. Remove Existing Antennas and Lines Facility Improvement Work Supply and install four (4) each 40-amp breakers in the distribution panel and wire to designated outlets. Install DC Power System. 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 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. 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. Site Scope Summary Existing 148 monopole tower and 12x12 shelter to be utilized Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 135

51 Motorola Responsibilities: Equipment Installation and Optimization RF fixed network and microwave equipment. Antenna and Transmission Line Installation Install two (2) antenna(s) for the RF system. Install two (2) 6-foot side arm(s) for antenna mounts. Install one (1) tower top amplifier(s). Install required linear feet of 1/2-inch transmission line. Install required linear feet of 7/8-inch transmission line. Install required linear feet of 1-5/8-inch transmission line. Install two (2) microwave dishes with radomes. Install required linear feet of elliptical waveguide. Perform sweep tests on transmission lines. Remove existing antennas and lines. Facility Improvement Work Install DC Power System. 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 Franklin Site Site Scope Summary Existing 225 self-supporting tower to be used for microwave only and 10x15 shelter to be used for indoor microwave. Motorola Responsibilities: Equipment Installation and Optimization Aviat microwave equipment. Optimize VHF Simulcast paging station and integrate its operation into the new dispatch console system. Site Engineering: Preparation, submission and tracking of application for electrical permits. 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 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. Antenna and Transmission Line Installation Install two (2) microwave dishes with radomes. p. 136 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-21

52 Install required linear feet of elliptical waveguide. 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. Columbia County Responsibilities: 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. Ensure availability of the existing access road in order to provide clear and stable entry to the site for vehicles. Ensure availability of space on the structure for installation of new antennas at the proposed heights on designated existing antenna-mounting structures. Provide as-built structural and foundation drawings of the structure and site location(s) along with geotechnical report(s) for Motorola to conduct necessary structural analysis. Assumptions: All work is assumed to be performed during normal business hours as dictated by time zone (Monday thru Friday, 7:30 a.m. to 5:00 p.m.). Structural analysis reports for the system sites are to be provided by Columbia County. The County will relinquish Motorola from any responsibility for the analysis report contents and/or recommendation therein. The floors can support the proposed new loading at the existing shelters being utilized at the Franklin and Cumorah sites. Physical or structural improvements to the existing rooms/shelters will not be required. Completion Criteria: Site development completed per issued for construction (IFC) construction drawings, project requirements, contractual obligations (including any customer/motorola approved changes) and approved by Columbia County. Contractor will confirm and review with Motorola construction manager and project manager will confirm before inspections occur. All jurisdictional and contractual required testing and inspections to be performed by the contractor. (Contractual testing and inspections defined and agreed to with project team and customer prior to project kick off; vendor solely responsible for conducting, coordinating and paying for all jurisdictional testing and inspections). Customer will sign off a Motorola Solutions-completed site development checklist prior to customer inspection. (Review with project team and customer and amend checklist as required at project kick off or before work begins). Site turn-over package completed and turned over to Motorola (As defined and agreed to with project team and customer). All punch list and deficiencies shall be completed prior to customer and Motorola inspections Greenfield Site Site Scope Summary New 250 self-supporting tower and 12x12 shelter with an outdoor Cummins generator. Specifications for the shelter will be consistent with the as-builts for the Deep Creek Site Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 137

53 New outdoor generator security wall. Engineering services for site drawings and regulatory approvals. New 60 x60 fenced compound. New 100 power run, 200-amp, 120/240 volt, single phase New 205-gallon diesel sub-base fuel tank New 35kW outdoor generator. Motorola Responsibilities: Site Engineering: Preparation, submission and tracking of application for electrical permits. 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 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. 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 communications site is located or will be located. Prepare a lease exhibit and 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. Conduct deep soil boring test at each tower leg, backfill holes with spoils, and prepare geotechnical report of soil conditions at locations of the tower foundation. Rock coring, extensive dewatering of foundations, or hazardous material removal have not been included. Conduct construction inspection of foundation steel prior to pour, materials testing of concrete, and field density tests of backfill to ensure quality construction. 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. Equipment Installation and Optimization RF fixed network and microwave equipment. Construct one reinforced concrete foundation necessary for a 12 foot x 12 foot shelter. Construct one foundation for the 35 kw generator with reinforcing steel necessary for foundations. Construct 8' high generator wall with a 2' x 2' footer made from cinder blocks filled with concrete. The back side of the wall will be 22 LF, end walls (2) will be 15 LF, side adjacent to the shelter will have two 6 LF walls coming off the corners. Supply and install one prefabricated shelter 12 foot x 12 foot. Supply and install one 205-gallon sub base diesel fuel tank, fill it with fuel, and connect it to the generator. p. 138 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-23

54 Supply and install fuel tank monitors on the tanks to monitor low fuel in tanks and run alarm wiring to the building located within 50 feet of the tank. Supply and install one standby power generator (35 kw) located within 20 feet of the ATS, including interconnection wiring between the generator, transfer switch, and site electrical service mains. Overhead power hookup of power to the site from nearby utility termination located within 100 cable feet. Coordinate 120/240 volt, 200 amp, single phase overhead electrical service, including installation of weather head and connection to utility pole within 100 feet. Provide all trenching and conduit necessary for underground hookup of Telco lines to the shelter. Supply and install a perimeter grounding system around the compound and shelter. The ground system is to tie to the fence and all new metal structures within the compound to meet current Motorola Solutions R56 standards. Design and install of grounding system will be consistent with the recently completed Deep Creek site design. Terrafil will be added in all trenches used in the grounding system to enhance grounding effectiveness. Conduct one three point ground resistance test of the site. Should any improvements to grounding system be necessary after ground testing, the cost of such improvements shall be the responsibility of Columbia County. Supply and install one freestanding 24 inch wide cable/ice bridge from the tower to the shelter. Spread spoils on site. Tower Work Construct a drilled pier tower foundation for a self-supporting tower including excavation, rebar, and concrete. This is three drilled pier foundations, each one is 60" W x 30' D with a 12" cap. The foundations have been designed for a total of 67.6 cubic yards of concrete. Erect new 250 foot self-supporting tower with dual LED medium intensity lighting. Supply and install grounding for the tower base. Antenna and Transmission Line Installation Install two (2) antenna(s) for the RF system. Install two (2) 6-foot side arm(s) for antenna mounts. Install one (1) tower top amplifier(s). Install required linear feet of 1/2-inch transmission line. Install required linear feet of 7/8-inch transmission line. Install required linear feet of 1-5/8-inch transmission line. Install one (1) microwave dishes with radomes. Install required linear feet of elliptical waveguide. Perform sweep tests on transmission lines. Site Preparation Light clearing and development of a 60X60 foot compound. Obtain the permits such as electrical, building, and construction permits, and coordinate any inspections with local authorities that may be needed 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 Solutions control will result in additional costs. Grade the site compound and 10 foot path around it to provide a level, solid, undisturbed surface for installation of site components Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 139

55 Supply and install gravel surfacing to a depth of six inches, including herbicide treatment and geotextile fabric installation within the fenced in site compound area, and a three foot path around it. Provide silt fence around the compound to control soil erosion. Supply and install eight foot high, razor wire topped, chain link fencing with a 10 foot wide gate around the shelter compound. Perform site touchup (fertilize, seed, and straw) to disturbed areas not covered with gravel after completion of construction work. Landscaping, decorative fencing, or any other aesthetic improvement that may be required by local jurisdictions has not been included and will be handled through a negotiated contract change notice. Columbia County Responsibilities: Site acquisition and any required zoning. Extensive clearing (i.e. trees, shrubs), grubbing and removal or excavation of rock. Pay for all utility connection, pole or line extensions, and any easement or usage fees. Review and approve site design drawings within seven calendar days of submission by Motorola Solutions or its subcontractor(s). Should a re submission be required, the County shall review and approve the re submitted plans within seven calendar days from the date of submittal. 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 Solutions. Provide a right of entry letter from the site owner for Motorola to conduct field investigations. Ensure availability of the existing access road in order to provide clear and stable entry to the site for vehicles. Assumptions: All work is assumed to be performed during normal business hours as dictated by time zone (Monday thru Friday, 7:30 a.m. to 5:00 p.m.). Soil conditions similar to those encountered at the Deep Creek tower site have been factored in to the tower foundation design. Should the geotech report results require a foundation design change, the cost of such changes shall be the responsibility of Columbia County. The new tower location will pass the FAA hazard study, zoning, FCC, and environmental permitting. The restoration of the site surroundings by fertilizing, seeding, and strawing the disturbed areas will be adequate. Tower and foundation sizing is based on the tower loading requirements as defined in the RFP. If after physical path studies, the dish sizes and locations change, then Motorola Solutions will then review the impact to tower structure and foundations and revise applicable costs. If as a result of NEPA studies, any jurisdictional authority should determine that a proposed communications facility may have a significant environmental impact, the environmental impact studies or field testing and evaluation related to such determination have not been included. Completion Criteria: Site development completed per issued for construction (IFC) construction drawings, project requirements, contractual obligations (including any customer/motorola approved changes) and approved by Columbia County. Contractor will confirm and review with Motorola construction manager and project manager will confirm before inspections occur. p. 140 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-25

56 All jurisdictional and contractual required testing and inspections to be performed by the contractor. (Contractual testing and inspections defined and agreed to with project team and customer prior to project kick off; vendor solely responsible for conducting, coordinating and paying for all jurisdictional testing and inspections). Coverage testing CATP for site completed. Customer will sign off a Motorola Solutions-completed site development checklist prior to customer inspection. (Review with project team and customer and amend checklist as required at project kick off or before work begins). Site turn-over package completed and turned over to Motorola (As defined and agreed to with project team and customer). All punch list and deficiencies shall be completed prior to customer and Motorola inspections System Installation Program and Distribute Portables Motorola Solutions Responsibilities: Program test portables with each template version and activate them on the system. Once all templates and client software is tested and approved by the County, Motorola Solutions Program all the portables, as identified in the equipment list, based upon the County approved programming templates, client software and fleetmap. One-time only programming is included in the project pricing. Deliver units to authorized Columbia County personnel and inventory upon receipt. Columbia County Responsibilities: Approve final template(s) and initiate portable programming. Upon receipt of portables, a County-authorized signatory acknowledges receipt of all portables and accessories and proper operation of a sampling of portables. Distribute the portables to end users. Completion Criteria: All portables are successfully programmed and approved by the County Program and Install Mobiles Motorola Solutions Responsibilities: Program test mobiles with each template version and activate them on the system. Once all templates and client software is tested and approved by the County, Motorola Solutions requests written approval of template acceptance. Install and program all the mobiles, as identified in the equipment list, based upon the County approved programming templates, client software and fleetmap. One-time only programming is included in the project pricing. Columbia County Responsibilities: Approve final template(s) and initiate mobile programming. Upon receipt of mobiles, a County-authorized signatory acknowledges receipt of all mobiles and proper operation of a sampling of mobiles Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 141

57 Coordinate the installation of the mobiles to end user vehicles with Motorola Solutions and its partners. Completion Criteria: All mobiles are successfully installed, programmed and approved by the County Install Fixed Network Equipment Motorola Solutions Responsibilities: Motorola Solutions will be responsible for the installation of all fixed equipment contained in the equipment list and outlined in the System Description based upon the agreed to floor plans, at the sites where the physical facility improvement is complete and the site is ready for installation. All equipment will be properly secured to the floor and installed in a neat and professional manner, employing a standard of workmanship consistent with its own R-56 installation standards and in compliance with applicable National Electrical Code (NEC), EIA, Federal Aviation Administration (FAA) and FCC standards and regulations. For installation of the fixed equipment at the various sites, Motorola Solutions will furnish all cables for power, audio, control and radio transmission to connect the Motorola Solutions supplied equipment to the power panels or receptacles and the audio/control line connection point. During field installation of the equipment, any required changes to the installation will be noted and assembled with the final as-built documentation of the system. Provide storage location for the Motorola Solutions-provided equipment. Receive and inventory all equipment. Bond the supplied equipment to the site ground system in accordance with Motorola Solutions R56 standards. Interface the site network connections with microwave connections. Remove and properly dispose of existing equipment. Columbia County Responsibilities: Provide access to the sites, as necessary. Completion Criteria: Fixed Network Equipment installation completed and ready for optimization Console Installation at EOC PSAP Motorola Solutions Responsibilities: Install the console workstations in the space provided by the County. Connect the appropriate equipment to the County-supplied ground system in accordance with Motorola Solutions R56 Site Installation standards. Perform the console programming, based on the console templates designed during the fleet mapping process. For consoles not located at the master site, additional network link resources will be required, as identified in the network diagram provided by Motorola Solutions. Completion Criteria: Console installation is complete. p. 142 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-27

58 Control Station Installation Motorola Solutions Responsibilities: Properly connect and ground the cabling, which will be run to the antenna location using the least obtrusive method. Protect the cabling by providing and installing a bulkhead lightning surge protector. Survey the exact mounting locations and develop control station installation plan. Perform the following tasks for the local control stations installations: Create installation plan. Install RF local control stations identified in the equipment list. Connect to the County-supplied ground point. Program all control stations once, from the template (approved by the County) prior to delivery. Columbia County Responsibilities: Supply a ground point of 5 ohms or less located in the immediate vicinity (within 6 feet) of the finalized location of the antenna and control station. Provide antenna-mounting facilities at each of the RF control station points specified, while providing an adequate means of feed-line routing and support. Completion Criteria: County approves completion of all the control station installations System Installation Acceptance (Milestone) All equipment installations are completed and accepted by the County System Optimization Optimize System FNE Motorola Solutions Responsibilities: Motorola Solutions and its subcontractors optimize each subsystem. Verify that all equipment is operating properly and that all electrical and signal levels are set accurately. Verify that all audio and data levels are at factory settings. Check forward and reflected power for all radio equipment, after connection to the antenna systems, to verify that power is within tolerances. Check audio and data levels to verify factory settings. Verify communication interfaces between devices for proper operation. Test features and functionality are in accordance with manufacturers specifications and that they comply with the final configuration established during the CDR/system staging. Test and optimize the simulcast system. Install and integrate the RF sites with the system, then optimize and activate the Master controller. Integrate the consoles and RF sites into the system to ensure proper operation. Set up the consoles on the radio system to perform the dispatching operation Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 143

59 Columbia County Responsibilities: Provide access/escort to the sites. Provide required radio ID and alias information to enable alias database setup for interface to console. Define talkgroups to be recorded by the logging recorder tracks by talkgroup. Dispatchers to use the existing conventional consoles for dispatching until cutover. Completion Criteria: System FNE optimization is complete Link Verification Motorola Solutions Responsibilities: Perform test to verify site link performance, prior to the interconnection of the Motorola Solutions-supplied equipment to the link equipment. Columbia County Responsibilities: Make available the required links which meet the specifications supplied by Motorola Solutions at the CDR. Completion Criteria: Link verification successfully completed Optimization Complete System optimization is completed. Motorola Solutions and the County agree that the equipment is ready for acceptance testing Audit and Acceptance Testing Perform R56 Installation Audit Motorola Solutions Responsibilities: Perform R56 site-installation quality audits, verifying proper physical installation and operational configurations. Create site evaluation report to verify site meets or exceeds requirements, as defined in Motorola Solutions Standards and Guidelines for Communication Sites (R56). Columbia County Responsibilities: Provide access/escort to the sites. Witness tests. Completion Criteria: All R56 audits completed successfully. Customer signs off on the completion of system inspection. p. 144 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-29

60 Perform Equipment Testing Motorola Solutions Responsibilities: Test individual components of the system to verify compliance to the equipment specifications. Repeat any failed test(s) once Motorola Solutions (or the County) has completed the corrective action(s). Prepare documentation of component tests to be delivered as part of the final documentation package. Successful demonstration of all functionality as required by RFP Section 11 Performance Verification and Acceptance Requirements. Columbia County Responsibilities: Witness tests if desired. Completion Criteria: Successful completion of equipment testing Perform Functional Testing Motorola Solutions Responsibilities: Verify the operational functionality and features of the individual subsystems and the system supplied by Motorola Solutions, as contracted. If any major task as contractually described fails, repeat that particular task after Motorola Solutions determines that corrective action has been taken. Document all issues that arise during the acceptance tests. Document the results of the acceptance tests and present to the County for review. Resolve any minor task failures before Final System Acceptance. Successful demonstration of all functionality as required by RFP Section 11 Performance Verification and Acceptance Requirements Columbia County Responsibilities: Witness the functional testing. Completion Criteria: Successful completion of functional testing. Columbia County approval of functional testing Perform Coverage Testing Motorola Solutions Responsibilities: Motorola Solutions and the Customer determine the required number of test vehicles for simultaneous testing of multiple service areas. Perform coverage testing according to the Coverage Acceptance Test Plan (CATP), Submit test reports within the agreed period. If any area fails, Motorola will re-test that particular area when corrective action has been completed. Document all issues that arise during the coverage testing. Submit final test reports, according to the agreed period Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 145

61 Successful demonstration of all functionality as required by RFP Section 11 Performance Verification and Acceptance Requirements. A second CATP will be performed to document performance associated with the Greenfield Site at a date in adherence to the implementation schedule. Columbia County Responsibilities: Provide the required number of test vehicles, drivers and resources to witness the coverage testing. Review the test results in a timely manner. Timely approval of the test results, if the reports indicate compliance with the agreed requirements. Completion Criteria: Customer approves successful completion of the coverage testing Training Perform Training Motorola Solutions Responsibilities: Finalize training schedules purchased as part of this project with the County Project Manager. Conduct the training classes outlined in the Training Plan in Section 3.4 below. Columbia County Responsibilities: Attend training classes. Comply with the prerequisites in the Training Plan. Completion Criteria: All training classes completed Day Performance Test Perform 30-Day Performance Period Motorola Solutions Responsibilities: Turn on the complete system and monitor for the entire test duration. Respond to any problems, according to the agreed period. Resolve any problems, according to the agreed period. Categorize the problems as major and minor, based upon agreed definitions. If a major failure occurs, correct the problem and re-start the test. If a minor failure occurs, correct the problem and continue the 30-day performance period. Complete the 30-day performance period test successfully and prepare the required reports, in the agreed period. Columbia County Responsibilities: Report any problems immediately to Motorola Solutions. Compile punch list of issues. p. 146 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-31

62 Cutover Completion Criteria: Customer approves successful completion of the coverage testing Perform System Cutover A preliminary cutover plan describing the transition of users to the new communications system is located in Section 3.5 Cutover Plan. Motorola Solutions Responsibilities: Motorola Solutions and Columbia County finalize a mutually agreed upon cutover plan based upon discussions held during the CDR. During cutover, follow the written plan and implement the defined contingencies, as required. Conduct cutover meeting(s) with user group representatives to address both how to mitigate technical and communication problem impact to the users during cutover and during the general operation of the system. Columbia County Responsibilities: Attend cutover meetings and approve the cutover plan. Notify the user group(s) affected by the cutover (date and time). Conduct a roll call of all users working during the cutover, in an organized and methodical manner. Ensure that all Subscriber users are trained and the Subscribers have been activated on the system. Provide Motorola Solutions with the subscriber information for input into the system database, for activation. Ensure that all subscribers are operating on new system prior to old system being removed. Completion Criteria: Successful migration from the old system to the new system Final System Acceptance Resolve Punch List Motorola Solutions Responsibilities: Work with Columbia County to resolve punch list items, documented during the Acceptance Testing phase, in order to meet all the criteria for final system acceptance. Columbia County Responsibilities: Assist Motorola Solutions with resolution of identified punch list items by providing support, such as access to the sites, equipment and system and approval of the resolved punch list item(s). Completion Criteria: All punch list items resolved and approved by the County Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 147

63 Project Transition Certificate Motorola Solutions Responsibilities: Review the items necessary for transitioning the project to warranty support and service. Provide a Customer Support Plan detailing the warranty and post-warranty support, if applicable, associated with the Contract equipment. Columbia County Responsibilities: Participate in the Transition Service/Project Transition Certificate (PTC) process. Completion Criteria: Customer receives and approves all service information Finalize Documentation Motorola Solutions Responsibilities: Provide the County with three (3) sets of electronic as-built system manual on a flash drive and one (1) bound hard copy. The complete system documentation will but not limited to the following: System-Level and Site Block Diagrams Site Floor Plans and Equipment Rack Configurations Cable/wiring Lists Antenna Network Drawings for RF Sites Antenna Drawings for Microwave Sites Acceptance Test Procedure Checklists Functional Acceptance Test Plan Test Sheets and Results Equipment Inventory List Maintenance Manuals (Charts and Tables) Operations Manuals Technical Service and Specification Manuals Alignment and Calibration Procedures Final parts/equipment lists will be supplied a minimum of 30 days prior to overall system acceptance. Drawings are created utilizing design software and will be delivered in Adobe PDF format. All other system manual documents converted from native format to Adobe PDF format to be included on the System Manual CD. Provide an operator manual with each subscriber. Provide console operator manuals at every dispatch position. All documentation not specifically listed here but is referenced in the RFP document Section 13 Columbia County Responsibilities: Receive and approve all documentation provided by Motorola Solutions. Completion Criteria: Customer receives and approves all required documentation Final System Acceptance (Milestone) All deliverables completed, as contractually required. p. 148 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-33

64 Final System Acceptance received from the Customer Project Administration Project Status Meetings Motorola Solutions Responsibilities: The Motorola Solutions Project Manager, or designee, will attend all project status meetings with the Customer, as determined during the CDR. Record the meeting minutes and supply the report. The agenda will include the following: Overall project status compared to the Project Schedule. Product or service related issues that may affect the Project Schedule. Status of the action items and the responsibilities associated with them, in accordance with the Project Schedule. Any miscellaneous Customer or Motorola Solutions concerns. Columbia County Responsibilities: Attend meetings. Respond to issues in a timely manner. Completion Criteria: Completion of the meetings and submission of meeting minutes Progress Milestone Submittal Motorola Solutions Responsibilities: Submit progress (non-payment) milestone completion certificate/documentation. Columbia County Responsibilities: Approve milestone, which will signify confirmation of completion of the work associated with the scheduled task. Completion Criteria: Customer approves Milestone Completion document(s) Change Order Process Either Party may request changes within the general scope of this Agreement. If a requested change causes an increase or decrease in the cost, change in system configuration or adds time to the project s timeline 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 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 149

65 Sample Change Control Document CHANGE ORDER [Type CO# here] Change Order No.: Date: Project Name: Customer Name: Customer Project Manager: The purpose of this Change Order is to: (highlight the key reasons for this Change Order) Contract No.: REQUIRED Contract Date: In accordance with the terms and conditions of the contract identified above between [enter customer name] and Motorola Solutions, Inc., the following changes are approved: Contract Price Adjustments Original Contract Value: $ Previous Change Order Amounts for Change Order Numbers through : $ This Change Order: $ New Contract Value: $ Completion Date Adjustments Original Completion Date: Current Completion Date prior to this Change Order: New Completion Date: p. 150 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-35

66 Changes in Equipment: (additions, deletions or modifications) Include attachments if needed Changes in Services: (additions, deletions or modifications) Include attachments if needed Schedule Changes: (describe change or N/A) Pricing Changes: (describe change or N/A) Customer Responsibilities: (describe change or N/A) Payment Schedule for this Change Order: (describe new payment terms applicable to this Change Order) Motorola Solutions, Inc. By: Printed Name: Title: Date: Unless amended above, all other terms and conditions of the Contract shall remain in full force. If there are any inconsistencies between the provisions of this Change Order and the provisions of the Contract, the provisions of this Change Order will prevail. IN WITNESS WHEREOF, the parties have executed this Change Order as of the last date signed below. Customer By: Printed Name: Title: Date: Reviewed By: Motorola Solutions Project Manager Date: 3-36 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 151

67 3.3 IMPLEMENTATION SCHEDULE Columbia County, Florida In accordance with RFP requirement 2.17.C.b, Motorola Solutions has included a preliminary implementation schedule at the end of this document. p. 152 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-37

68 This page intentionally left blank Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 153

69 3.4 TRAINING Overview Motorola Solutions understands that successful implementation and use of your communications system depends on effective training. We have developed a training proposal for Columbia County to ensure a comprehensive understanding of your proposed system and all user equipment. We are leveraging over 85 years of training experience working with customers just like you to provide recommendations for your consideration. The training proposal detailed in the following pages incorporates customer feedback coupled with a best practices systematic approach to produce effective course delivery and content. Our commitment to Columbia County is to provide unsurpassed services that ensure the equipment operates efficiently for the life of the system. To do so, we directly train your personnel to utilize the system to its maximum potential. Columbia County personnel will gain in-depth understanding of the power of your new system through education and proficient daily use. Our high-quality training focuses on student needs and is complemented by detailed documentation and available continuing education programs. We will collaborate with Columbia County to develop a final customized training plan that fits your needs. Our goal is to insure system administrators, technicians and end users are skilled in using your new system Training Approach Our training solutions deliver a combination of online training and field based instructor-led training in classrooms at Columbia County locations using operational equipment. Motorola Solutions will employ knowledgeable and experienced instructors to deliver well-designed courseware and integrated lab activities. Training is based upon several key criteria: Analysis of student needs drives course design. It focuses on specific application rather than theory. Student need drives learning objectives. Hands-on lab opportunities using Columbia County-specific job aids are incorporated to maximize learning and retention. Our instructors bring invaluable experience and knowledge of customer communication solutions into their training approach. This gives them better insight and understanding into the practical aspects of Columbia County manager, technician and end user job functions. Each instructor has the proven ability to communicate with a novice as well as expert personnel Proposed Courses We have identified the following course(s) that are necessary to achieve the training goals for Columbia County. The tables on the following pages detail recommended courses and their descriptions. Instructor-led courses, delivered in the field, will be tailored for your system and features. Specifically, our proposed training plan addresses the following categories as identified in your request for proposal: p. 154 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-39

70 System Administrators Maintenance Technicians Console Supervisors and Operator Trainers Radio User Trainers If the County elects to include post warranty maintenance and lifecycle services, Motorola Solutions will also include at no additional expense with the Technology Refresh offering, system upgrade Impact and Implementation training. Participants are encouraged to bring their laptop computers for all system administrator and technician classes. Planning Stage Training Plan Course Title Target Audience Sessions Duration Location Date Participants ASTRO 25 Systems Fleetmapping Workshop (Instructor-led) System Managers and Technicians days FL Early in Planning Stage Up to 12 Course Synopsis: This workshop addresses topics necessary for the effective planning and mapping of an ASTRO 25 IV&D radio system. During this course, the participants will learn about ASTRO 25 features, capabilities and restrictions in order to effectively plan for a new or upgraded ASTRO 25 system. System Administrator Training Plan Course Title ASTRO 25 IV&D System Overview (Self-paced; On- Line) Prerequisite Target Audience System Managers Sessions Duration Location Date Participants hours On-Line Prior to Workshop Course Synopsis: The ASTRO 25 IV&D System Overview course will provide participants with knowledge and understanding of the ASTRO 25 IV&D system. This course will address M, L and K Core systems. System architecture, components and features will be explained. In addition, RF and console sites and their architecture, features and components will be discussed. Finally, call processing for voice and mobile data applications will be covered and an introduction to applications available in the ASTRO 25 system will be provided. ASTRO 25 IV&D Radio System Administrator Workshop (Instructor-led) System Managers 1 5 days FL Prior to managing the system Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 155

71 Course Title Target Audience Sessions Duration Location Date Participants Course Synopsis: This workshop covers administrator functions for an ASTRO 25 Integrated Voice and Data (IV&D) System. Learning activities in this course focus on how to use the different ASTRO 25 IV&D System Management applications. Participants will be provided with an opportunity to discuss how to structure their organization and personnel for optimal ASTRO 25 IV&D system use. ASTRO 25 ISSI 8000 / CSSI 8000 Feature Overview (Self-paced; On- Line) System Managers 1 3 days FL Prior to managing the system Course Synopsis: The ISSI 8000 / CSSI 8000 Feature Overview self-paced course describes the optional Inter-RF Subsystem Interface available in an ASTRO 25 IV&D System. It presents a description of the feature, its benefits and components, call processing scenarios and an overview of the installation process. Maintenance Technician Training Plan Course Title ASTRO 25 IV&D System Overview (Self-paced; On- Line) Prerequisite Target Audience System Technicians Sessions Duration Location Date Participants hours On-Line Prior to Workshop Course Synopsis: The ASTRO 25 IV&D System Overview course will provide participants with knowledge and understanding of the ASTRO 25 IV&D system. This course will address M, L and K Core systems. System architecture, components and features will be explained. In addition, RF and console sites and their architecture, features and components will be discussed. Finally, call processing for voice and mobile data applications will be covered and an introduction to applications available in the ASTRO 25 system will be provided. ASTRO 25 GTR8000 Repeater Site and IP Digital Simulcast Workshop (Instructor-led) System Technicians 1 5 days FL Prior to maintaining p. 156 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-41

72 Course Title Target Audience Sessions Duration Location Date Participants GTR8000 Course Synopsis: This workshop describes the components in the ASTRO 25 IV&D 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. IP Simulcast Course Synopsis: The ASTRO 25 IV&D IP Based Digital Simulcast workshop provides an understanding of the components that comprise the ASTRO 25 IV&D IP Simulcast subsystem and how they operate in conjunction with each other. The workshop also explains the tools and methods available for troubleshooting components within the IP Based Simulcast subsystem. APX CPS Programming and Template Building (Instructor-led) Radio Technicians 1 2 days FL Prior to programming radios Course Synopsis: The APX CPS Programming and Template Building course provides communications management personnel and technicians with the knowledge and training necessary to build templates and program APX subscriber radio s in the most efficient way possible. The content, parameters and exercises demonstrated in this class apply to the APX portable and mobile. APX Technical Subscriber Academy (Instructor-led) Radio Technicians 1 5 days FL Prior to maintaining radios 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. 5 5 Console Supervisor Plan Course Title MCC7500E/7100 Console Operator and Admin 3 Training consoles (Instructor-led) Target Audience Supervisory Personnel (Per RFP) Sessions Duration Location Date Participants 1 (8 hr session) 1 day FL Prior to training Dispatchers Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 157

73 Course Title Target Audience Sessions Duration Location Date Participants Operator 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. ADMIN Course Synopsis: This course provides participants with the knowledge and skills to manage and utilize the MCC7500E console administrator functions. Through facilitation and hands-on activities, the participant learns how to customize the console screens. Console Train-the-Trainers Plan Course Title MCC7500E/7100 Console Operator Train-the- Trainers 3 Training consoles (Instructor-led) Target Audience Dispatch Trainers Sessions Duration Location Date Participants 2 (4 hr sessions) 1 day FL Prior to training Dispatchers 12 (6 per) Operator 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. Radio User Train-the-Trainer Plan Course Title APX Portable and APX Mobile and WAVE Train-the- Trainer (Instructor-led) APX Portable and APX Mobile Train-the- Trainer (Instructor-led) Target Audience Public Safety Trainers Local Govt. Trainers Sessions Duration Location Date Participants 1 (8 hour session) 1 (8 hour session) 1 day FL Prior to training users 1 day FL Prior to training users p. 158 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-43

74 Course Title Target Audience Sessions Duration Location Date Participants Course Synopsis: This course provides APX radio trainers with an introduction to their radio, its basic operation and tailored job aids available for assistance in operation. The learning experience is a mix of facilitation and hands-on activities to help users perform common tasks associated with their radio operation. Segmentation between user groups (i.e. Police, Fire/EMS and Public Service) is encouraged to help focus instruction on the specific operational issues of the individual user group. This course is geared for customers who have an experienced dedicated training staff in their organization. It provides the customer s identified training personnel with the knowledge and practice applying training techniques that will enable them to successfully train their students. Trainers will use audio visual (Interactive End User Toolkits ieutk), facilitation and hands-on activities to facilitate learning events supported by tailored or customized training materials and job aides. They will become proficient in discussing common tasks associated with the operation of the customer s radios. Interactive End User Tool Kit (ieutk) 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 the operational theory of their specific device. The tailored materials are developed onsite 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 Solutions 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. Technology Refresh Training Plan Course Title Target Audience Sessions Duration Location Date Participants Impact Training System 1 1 day FL 3-6 months Up to 12 for ASTRO 25 Management (8 hr prior to System Release Personnel session) system (Instructor-led) upgrade Implementation Training for ASTRO 25 System Release (Instructor-led) System Management Personnel 1 3 day FL Following system upgrade Up to Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 159

75 Course Title Target Audience Sessions Duration Location Date Participants Impact Course Synopsis: This onsite training course lasts an average of one day and educates your system managers on the features of the current system release, while highlighting operational deltas. This allows you to initiate planning within your organization to prepare for the changes to your ASTRO 25 system and fully integrate this plan into both existing and new technologies and processes to help ensure a smooth operational transition. Implementation Course Synopsis: This course addresses Operations, Maintenance, Applications and Provisioning aspects of your ASTRO 25 system. Lasting an average of 3 days, this course helps ensure that you are familiar with the new aspects of your system and that you understand how to maximize their utilization. NICE Inform Training Course Title Inform Pre Training Call Target Audience Administrators and Support Sessions Duration Location 1 1 day Remote System /User Administrator Training End User Training Evaluator Training Administrators and Support Hours Onsite End Users Hours Onsite End Users 1 1 day Onsite Pre-Training Call Course Synopsis: Establishes the timeline for scheduling training on the use of NICE Inform. Ensures and understanding of the information to be delivered. System/User Administrator Training Course Synopsis: Delivery of content necessary for users to administer the NICE Inform system: Inform System Administration Inform User Administration Inform Audit NRX System Administration End User Training Course Synopsis: Delivery of content for users responsible for searching/saving audio, creating reports and incidents: Monitor application Reconstruction application Organizer application Verify Reporter Evaluator Training Course Synopsis: Delivery of content for users responsible for creating evaluation forms and completing evaluations on agents: Template designer p. 160 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-45

76 Course Title Target Audience Evaluation processes Evaluation design Sessions Duration Location Aviat Microwave Training Course Title ProVision Installation, Configuration & Management Target Audience Network Operations Center operators and Engineers Sessions Duration Location 1 2 days Columbia County, FL IRU600 Installation, Operation & Maintenance Installation and service personnel 1 3 days Columbia County, FL ProVision Installation, Configuration & Management Course Synopsis: Aviat ProVision is a powerful, standards-based Element Management System (EMS). Designed to simplify Carrier Ethernet and TDM network designs and services, it provides superior intelligence for mobile and private network operators. ProVision delivers network management across the full Aviat product portfolio, key partner products and many third party SNMP-based platforms. It provides efficient, seamless end-to-end network management solutions for TDM, Carrier Ethernet and hybrid microwave networks. The ProVision Installation, Configuration and Management course provides full guidance on the installation, use and administration of ProVision EMS software. The course will cover in detail all aspects of using the EMS for fault management, configuration management, performance monitoring and reporting. IRU600 Installation, Operation & Maintenance Course Synopsis: The Aviat Networks IRU600 is an all outdoor packet-millimeter wave radio that integrates the latest radio technology into a small and compact housing with low power consumption. It is designed to support Carrier Ethernet over the E-band air interface. The IRU600 Installation, Operation and Maintenance course teaches students key functions of the IRU wave radios. The course includes an overview of all available equipment, basic configuration with the Portal craft tool, system commissioning, maintenance, diagnostics and troubleshooting. Extensive hands-on labs (nearly 50% of the course duration) offer students with scenarios they will face in real deployments in their networks Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 161

77 3.4.3 Course Descriptions Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: ASTRO 25 Systems Fleetmapping Workshop RDS days ILT Instructor-led training Pre-Sale System Owners, Planners, Administrators and Technicians This workshop addresses topics necessary for the effective planning and mapping of an ASTRO 25 IV&D radio system. During this course, the participants will learn about ASTRO 25 features, capabilities and restrictions in order to effectively plan for a new or upgraded ASTRO 25 system. None After completing the course, the participant will be able to: Define what a fleetmap is and why one is needed. Understand the methodologies used to configure radio users groups with the goal of optimizing the system resources. Enable participants to knowledgably assist with fleetmapping decisions. Discuss frequency band plan, organization and management. Describe basic planning requirements. Complete worksheets required to create a fleetmap based on sample operational requirement information. Module 1: Introduction Module 2: ASTRO 25 System Architecture 2-1: Overview 2-2: Supported Architecture Types 2-3: ASTRO 25 IP Integration 2-4: Basic Components 2-5: Characteristics 2-6: Network Management Applications 2-7: Radio Frequency Subsystems 2-8: Repeater Site 2-9: Multisite Subsystems Simulcast Module 3: Frequency Band Plan Management 3-1: Considerations and Warnings 3-2: Overview 3-3: Elements 3-4: Foreign System Frequency Plan 3-5: Channel Assignment Methods 3-6: UNC Wizard 3-7: Channel Access p. 162 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-47

78 ASTRO 25 Systems Fleetmapping Workshop RDS1017 Module 4: Fleetmapping Technical Overview 4-1: Set Up 4-2: System Organization 4-3: Benefits 4-4: Talkgroups/Multi-groups/Agency groups 4-5: Radio Users 4-6: Talkgroups in an Organization 4-7: Organizing Fleetmap Tasks 4-8: Organizing Fleetmap Other Factors 4-9: Identifying Radio Users 4-10: Identifying Data Services Users 4-11: Radio Users into Talkgroups 4-12: Radio Users and All Assigned Talkgroups 4-13: Talkgroups in Multi-groups 4-14: Multi-groups in Agency Groups 4-15: Assigning IDs and Aliases 4-16: Creating ID Ranges 4-17: Identifying Talkgroup, Multi-group and Agency Group IDs 4-18: Identifying Console IDs 4-19: Console ID Assignment 4-20: Alias Assignment 4-21: Home Zones 4-22: Home Location Register (HLR) 4-23: Visitor Location Register (VLR) 4-24: HLR and VLR per Zone 4-25: Priority Levels 4-26: Secure Keys Module 5: Fleetmapping Configuration 5-1: Feature Assignment 5-2: Home Zone Assignments 5-3: Data Services 5-4: Secure Voice Requirements 5-5: System Access 5-6: User Access 5-7: Hierarchy of System Management Users 5-8: System Management 5-9: Database Access 5-10: Subscriber Programming 5-11: Radio Programming 5-12: Subscriber Ranges 5-13: Subscriber Range Assignment 5-14: Additional Considerations 3-48 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 163

79 ASTRO 25 Systems Fleetmapping Workshop RDS1017 Module 6: Fleetmapping Operation 6-1: ASTRO 25 System Checklist 6-2: Contingency Planning 6-3: Escalation Plan 6-4: Additional Contingency Planning Module 7: Worksheets 7-1: List of Fleetmapping Worksheets 7-2: Current and Future Equipment Quantities Worksheet 7-3: Available Sites Worksheet 7-4: Individual Radio Users Worksheet 7-5: Serial Number to Radio ID Worksheet 7-6: Radio User to Radio ID Worksheet 7-7: Talkgroup IDs and Aliases Worksheet 7-8: Multi-groups and Associated Talkgroups Worksheet 7-9: Agency Groups and Associated Multi-groups 7-10: Radio Users Assigned to Talkgroups Worksheet 7-11: Communications and Radio Feature Mapping Worksheet 7-12: Console IDs Worksheet 7-13: Secure Keys Worksheet 7-14: Talkgroup Matrix Worksheet 7-15: Lab - Create a Fleetmap 7-16: Course Conclusion Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: 2.5 Hours OLT Online Training ASTRO 25 IV&D System Overview Core Technicians, Site Technicians, Console Technicians and Core Managers The ASTRO 25 IV&D System Overview course will provide participants with knowledge and understanding of the ASTRO 25 IV&D system. This course will address M, L and K Core systems. System architecture, components and features will be explained. In addition, RF and console sites and their architecture, features and components will be discussed. Finally, call processing for voice and mobile data applications will be covered and an introduction to applications available in the ASTRO 25 system will be provided. None By the end of this course, you will be able to: Understand the general architecture of an ASTRO 25 IV&D Radio System Understand key features of available in the ASTRO 25 IV&D Radio System Understand the components of the ASTRO 25 Zone Core Understand site components in the ASTRO 25 system Understand the features, capabilities and components of the MCC7000 series dispatch consoles p. 164 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-49

80 ASTRO 25 IV&D System Overview Understand concepts of Mobility and Call Processing in the ASTRO 25 Understand the applications for managing the ASTRO 25 system Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: ASTRO 25 IV&D Radio System Administration Workshop 5 days ILT = Instructor Led Training System Administrators, Technical System Administrators, System Technicians and other Application Users. This workshop covers administrator functions for an ASTRO 25 Integrated Voice and Data (IV&D) System. Learning activities in this 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. Completion of the following courses or equivalent knowledge: ASTRO System Applied Networking ASTRO 25 IV&D with M and L Core System Overview (ACS716200) ASTRO 25 IV&D Introduction to Radio System Management Applications (ACS716201) After completing the course the participant will be able to: 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. Identify the advantages and disadvantages of options available for the configuration of system infrastructure and user parameters. Use the report and real-time data to monitor performance and make adjustments necessary to maintain acceptable system performance levels. Module 1: Course Introduction Module 2: Basic Concepts of Radio System Administration Topic 3-1: Configuration Process and Tools Topic 3-2: Adding Radios and Talkgroups to the System Topic 3-3: Editing Existing Records in PM Topic 3-4: Setting System-Level Parameters Topic 3-5: Creating Managers and Controlling Access Topic 3-6: Managing Configurations with UNC Topic 3-7: Configuring Sites and Channels with PM Topic 4-1: License Sharing Topic 4-2: Live Monitoring of the System Topic 4-3: Report Generation Topic 4-4: Network Maintenance Tools 3-50 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 165

81 Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: 1 Hour ASTRO 25 ISSI 8000 / CSSI 8000 Feature Overview OLT Online Training System Managers, Technical System Managers, System Technicians, Application Users The ISSI 8000 / CSSI 8000 Feature Overview self-paced course describes the optional Inter-RF Subsystem Interface available in an ASTRO 25 IV&D System. It presents a description of the feature, its benefits and components, call processing scenarios and an overview of the installation process. Suggested completion of the following courses or equivalent experience: ACS ASTRO 25 IV&D with M Core System Overview By the end of this course, you will be able to: Describe the ISSI 8000 / CSSI 8000 feature Describe the components of the ISSI 8000 / CSSI 8000 feature Describe the communication scenarios if this feature is enabled Follow the installation and configuration process if this feature is added to an ASTRO system. Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: ASTRO 25 IV&D System Overview 2.5 Hours OLT Online Training Core Technicians, Site Technicians, Console Technicians and Core Managers The ASTRO 25 IV&D System Overview course will provide participants with knowledge and understanding of the ASTRO 25 IV&D system. This course will address M, L and K Core systems. System architecture, components and features will be explained. In addition, RF and console sites and their architecture, features and components will be discussed. Finally, call processing for voice and mobile data applications will be covered and an introduction to applications available in the ASTRO 25 system will be provided. None By the end of this course, you will be able to: Understand the general architecture of an ASTRO 25 IV&D Radio System Understand key features of available in the ASTRO 25 IV&D Radio System Understand the components of the ASTRO 25 Zone Core Understand site components in the ASTRO 25 system Understand the features, capabilities and components of the MCC7000 series dispatch consoles Understand concepts of Mobility and Call Processing in the ASTRO 25 Understand the applications for managing the ASTRO 25 system p. 166 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-51

82 Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: 3 days ASTRO 25 GTR8000 Repeater Site Workshop ILT = Instructor Led Training GTR 8000 Site Technicians This workshop describes the components in the ASTRO 25 IV&D 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. Completion of the following courses or equivalent experience: ASTRO Systems Applied Networking (NWT003) ASTRO 25 IV&D with M core System Overview (ACS715200) ASTRO 25 IV&D Introduction to Radio System Management Applications (ACS715201) After completing this course, the participant will be able to: Describe the ASTRO 25 IV&D Repeater Site with GTR 8000 Expandable Site Subsystem configurations and components. Identify the GCP 8000 Site Controller functions and configuration requirements. Describe the connections and interfaces to the GCP Diagnose and troubleshoot the GCP Describe the functionality of the GTR 8000 Expandable Site Subsystem. Configure and troubleshoot the ASTRO 25 Repeater Site with GTR 8000 Expandable Site Subsystem. Configure and troubleshoot the Network Transport subsystem. Module 1: Course Introduction Module 2: GTR 8000 Repeater Site Topic 2-1: GTR 8000 Repeater Site Overview Topic 2-2: Operational Modes Topic 2-3: Site Configurations Topic 2-4: Site Components Topic 2-5: Time Synchronization and Frequency Reference Test Your Understanding Exercise Module 3: GCP 8000 Site Controller Topic 3-1: GCP 8000 Overview Topic 3-2: GCP 8000 Physical Description Topic 3-3: GCP 8000 Configuration Topic 3-4: GCP 8000 Diagnostics and Troubleshooting Test Your Understanding Exercise 3-52 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 167

83 ASTRO 25 GTR8000 Repeater Site Workshop Module 4: GTR 8000 Expandable Site Subsystem Topic 4-1: GTR 8000 Expandable Site Subsystem Overview Topic 4-2: GTR 8000 Expandable Site Subsystem Theory of Operation Topic 4-3: GTR 8000 Expandable Site Subsystem Configuration Topic 4-4: GTR 8000 Expandable Site Subsystem Diagnostics and Troubleshooting Test Your Understanding Exercise Module 5: Radio Frequency Distribution System (RFDS) Topic 5-1: RFDS Overview Topic 5-2: RFDS Physical Description Topic 5-3: RFDS Configuration Topic 5-4: RFDS Diagnostics and Troubleshooting Test Your Understanding Exercise Module 6: Network Transport Subsystem Topic 6-1: Network Transport Subsystem Overview Topic 6-2: Ethernet Switch Diagnostics and Troubleshooting Topic 6-3: Site Gateways Topic 6-4: Gateway Diagnostics and Troubleshooting Test Your Understanding Exercise Module 7: GTR 8000 Site Maintenance and Troubleshooting Topic 7-1: Unified Event Manager Topic 7-2: Troubleshooting Tools Topic 7-3: Troubleshooting Methodology Topic 7-4: Troubleshooting Repeater Site Link Topic 7-5: Motorola Support Centers Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: 3 days ASTRO 25 IP Digital Simulcast Workshop ILT = Instructor Led Training Simulcast Site Technicians The ASTRO 25 IV&D IP Based Digital Simulcast workshop provides an understanding of the components that comprise the ASTRO 25 IV&D IP Simulcast subsystem and how they operate in conjunction with each other. The workshop also explains the tools and methods available for troubleshooting components within the IP Based Simulcast subsystem. Completion of the following courses or equivalent knowledge: ASTRO Systems Applied Networking (NWT003) ASTRO 25 IV&D with M core System Overview (ACS715200) p. 168 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-53

84 Course Objectives: Course Modules: ASTRO 25 IP Digital Simulcast Workshop After completing this course, the participant will be able to: 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. Module 1: Course Introduction Module 2: Repeater Site Topic 2-1: Simulcast Review Topic 2-2: IP Simulcast with GTR 8000 Subsystem Overview Topic 2-3: Site Configurations Topic 2-4: IP Simulcast Integrated Voice and Data Module 3: GCP 8000 Site Controller Topic 3-1: GCP 8000 Overview Topic 3-2: GCP 8000 Physical Description Topic 3-3: GCP 8000 Configuration Topic 3-4: GCP 8000 Diagnostics and Troubleshooting Module 4: GTR 8000 Comparator Topic 4-1: GCM 8000 Overview Topic 4-2: GCM 8000 Physical Description Topic 4-3: GCM 8000 Configuration Topic 4-4: GCM Diagnostics and Troubleshooting Module 5: IP Simulcast Network Topic 5-1: Ethernet LAN Switches 5-1.1: Ethernet Switch Overview 5-1.2: Ethernet Switch Physical Description 5-1.3: Ethernet Switch Configuration 5-1.4: Ethernet Switch Diagnostics and Troubleshooting Topic 5-2: Prime Site Routers/Gateways 5-2.1: Prime Site Routers/Gateways Overview 5-2.2: Prime Site Routers/Gateways Physical Description 5-2.3: Prime Site Routers/Gateways Configuration 5-2.4: Prime Site Routers/Gateways Diagnostics and Troubleshooting Topic 5-3: Remote Site Routers/Gateway 5-3.1: Remote Site Routers/Gateway Overview 5-3.2: Remote Site Routers/Gateway Physical Description 5-3.3: Remote Site Routers/Gateway Configuration 5-3.4:Remote Site Routers/Gateway Diagnostics and Troubleshooting 3-54 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 169

85 ASTRO 25 IP Digital Simulcast Workshop Module 6: TRAK 9100 Site Reference Topic 6-1: TRAK 9100 Site Reference Overview Topic 6-2: TRAK 9100 Site Reference Physical Description Topic 6-3: TRAK 9100 Site Reference Installation and Configuration Topic 6-4: TRAK 9100 Site Reference Diagnostics and Troubleshooting Module 7: GTR 8000 Base Radio Subsystem Topic 7-1: GTR 8000 Base Radio Subsystem Overview Topic 7-2: GTR 8000 Base Radio Subsystem Physical Description Topic 7-3: GTR 8000 Base Radio Subsystem Configuration Topic 7-4: GTR 8000 Base Radio Subsystem Diagnostics and Troubleshooting Module 8: IP Simulcast Subsystem Maintenance and Troubleshooting Topic 8-1: Maintenance and Troubleshooting Overview Topic 8-2: Unified Event Manager Topic 8-3: Device Fault Management Topic 8-4: Troubleshooting Process Topic 8-5: Troubleshooting Site Links Topic 8-6: Motorola Support Centers Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: 2 Days APX CPS Programming and Template Building ILT Instructor-led training Radio Technicians, System Managers and anyone responsible for programming APX subscriber radios The APX CPS Programming and Template Building course provides communications management personnel and technicians with the knowledge and training necessary to build templates and program APX subscriber radio s in the most efficient way possible. The content, parameters and exercises demonstrated in this class apply to the APX portable and APX mobile. Knowledge of the basic features and options of two-way radios and the basic concepts of conventional and trunking systems After completing this course, the student will be able to: Build APX 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 p. 170 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-55

86 Course Modules: APX CPS Programming and Template Building Introduction to APX Radio Introduction to APX CPS APX CPS Install, Setup and Configuration Navigating APX CPS APX CPS Data Transfer including POP25/OTAP 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 Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: 5 Days APX Technical Subscriber Academy ILT Instructor-led training Radio technicians 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. Completion of the following courses: APX CPS Programming and Template Building Overview (APX7001-V) 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) After completing this course, the student will be able to: Distinguish between the features and specifications of APX portable and mobile radios Verify the correct operations of the APX portable and mobile radios Maintain and troubleshoot an APX portable and mobile radios Disassemble and reassemble the radio using the documented procedures Verify the housing integrity of an APX portable radio Flash upgrade an APX portable and mobile radio 3-56 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 171

87 Course Modules: APX Technical Subscriber Academy APX Radio Introduction APX Radio Performance Checks APX Radio Alignment APX Radio Theory Of Operation Radio Disassembly / Reassembly Vacuum Testing For Submergibility Mobile Radio Installation and Configuration Advanced Customer Programming Software Radio Troubleshooting Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: MCC7500E/7100 Console Operator and Train-the-Trainers 4 hours Full Course ILT - Instructor-led training Dispatch Console Operators, Supervisors, System Administrators and Support Personnel 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. Trainers will also learn how to use the tailored tools to train staff. None 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 Overview Communicating with Radios Advanced Signaling Features Resource Groups Working with Configurations Working with Aux IOs Troubleshooting Tailored training tools Duration: MCC7500E/7100 Console ADMIN for Supervisor 4 hours Operator, plus 4 hours ADMIN Full Course p. 172 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-57

88 Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: MCC7500E/7100 Console ADMIN for Supervisor ILT - Instructor-led training Dispatch Supervisors and System Administrators This course provides participants with the knowledge and skills to manage and utilize the MCC7500E console administrator functions. Through facilitation and hands-on activities, the participant learns how to customize the console screens. None Understand the menu items and tool bar icons Edit folders, multi-select/patch groups, auxiliary input output groups, windows and toolbars Add/delete folders 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 Duration: APX Portable and APX Mobile Train-the-Trainer Up to 8 hours Delivery Method: Target Audience: Course Synopsis: ILT - Instructor-led training APX Trainers, Supervisors and Support Personnel This course provides APX radio trainers with an introduction to their radio, its basic operation and tailored job aids available for assistance in operation. The learning experience is a mix of facilitation and hands-on activities to help users perform common tasks associated with their radio operation. Segmentation between user groups (i.e. Police, Fire/EMS and Public Service) is encouraged to help focus instruction on the specific operational issues of the individual user group. This course is geared for customers who have an experienced dedicated training staff in their organization. It provides the customer s identified training personnel with the knowledge and practice applying training techniques that will enable them to successfully train their students. Trainers will use audio visual (Interactive End User Toolkits ieutk), facilitation and hands-on activities to facilitate learning events supported by tailored or customized training materials and job aides. They will become proficient in discussing common tasks associated with the operation of the customer s radios Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 173

89 Prerequisite: Course Objectives: Course Modules: APX Portable and APX Mobile Train-the-Trainer Previous two-way radio and training experience High-level overview of the customer system configuration General radio operation Proper operating procedures for specific customer features Perform basic operational tasks of the radio Utilize the provided job aids to perform specific tasks associated with the radio Basics Controls Top and Side Buttons Switches 3 Position toggle 2 Position Concentric Home key Data Key Display Front Display Top Display Display light Intelligent Lighting Navigating Menu Screen Recent Call List (Model 3.5) Unified Call List - Contacts (Model 3.5) Dual Sided Radio (Model 3.5) Dual Mics Dual Speakers Accessory Connector Specific Features Changing Talkgroups/Channels Changing Zones Mute tones of keypad Talkgroup Call Private Call Accessing Private Call Feature Initiating Private Call Call List Programming Announcement/All Call (Calls involving Multiple Talkgroups) Initiating Announcement/All Call Direct/Talkaround Failsoft Radio Profiles Accessing and changing Radio Profile p. 174 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-59

90 APX Portable and APX Mobile Train-the-Trainer Optional Features Scan Scan program Priority Scan Dynamic Priority Telephone Interconnect Accessing Telephone Interconnect Feature Initiating a Phone Call Phone List Programming Data Services Text Messaging Accessing the Text Messaging Feature Creating a Free Form Text Message Sending a Canned Text Message GPS OTAP Encryption Emergency Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: Impact Training for ASTRO 25 System Release ILT - Instructor-led training System Administrators This onsite training course lasts an average of one day and educates your system managers on the features of the current system release, while highlighting operational deltas. This allows you to initiate planning within your organization to prepare for the changes to your ASTRO 25 system and fully integrate this plan into both existing and new technologies and processes to help ensure a smooth operational transition. None Identify changes as a result of the upgrade early to more easily manage the changes. Identify operational procedures that will go away as a result of the upgrade. Identify operational procedures that will change as a result of the upgrade. Identify new operational procedures that will be available as a result of the upgrade. Introduction System Upgrade New System Features 3-60 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 175

91 Delivery Method: Target Audience: Course Synopsis: Prerequisite: Course Objectives: Course Modules: Implementation Training for ASTRO 25 System Release ILT - Instructor-led training System Administrators This course addresses Operations, Maintenance, Applications and Provisioning aspects of your ASTRO 25 system. Lasting an average of 3 days, this course helps ensure that you are familiar with the new aspects of your system and that you understand how to maximize their utilization. Prior ASTRO 25 training in the previous system release. After completing this course, the student will be able to understand the differences in equipment or software application differences between the customers previous and upgraded system release. Introduction New System Differences ProVision Installation, Configuration & Management Duration: 2 days Delivery ILT - Instructor-led training Method: Target Audience: Network Operations Center operators and engineers involved in managing microwave networks using the ProVision EMS. 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. Trainers will also learn how to use the tailored tools to train staff. Prerequisite: Participants must complete ProVision System Overview e-learning course Participants should have knowledge and experience in the areas of network operations fundamentals and telecommunications fundamentals. The student will need a Notebook computer with an Ethernet port and running on one of the following Operating Systems: Windows XP Pro Windows Vista Windows 7 Windows 2003 Server Windows 2008 Server Course Outline: ProVision Introduction Functions & features Minimum hardware specifications Understand ProVision Architecture Deployment Options Navigating ProVision Main user interface Menu bar p. 176 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-61

92 ProVision Installation, Configuration & Management Tree Viewer Map Viewer View and change radio configuration View and change network IP addresses Fault Management Managing Events Event Browser Viewing Security Logs Configure Event Notifications Configure and Interpret Scoreboards Performance Monitoring Configure device data collection Interpret performance history & trends Set up Performance thresholds Interpret Ethernet Bandwidth Utilization Produce inventory & fault reports Eclipse Features Create, trace, view and diagnose circuits Perform bulk software loads Produce capacity, inventory & fault reports ProVision Installation and User Administration Requirements for ProVision Installation ProVision Server and Client Installation Verifying ProVision server is running Logging in to Client Software Navigation ProVision Basic User Account creation and access level Deploying and Managing Radios and Generic Devices Information required for deployment Deploying containers Deploy, Manage, Rename, Delete and Unmanage Radios and Generic devices Re-parenting an object Create, verify and delete a link Reposition Map viewer objects Verify ProVision is receiving events Configuration Management View and Change Network IP addresses Uploading Eclipse licenses Perform Bulk configuration for devices on the network Network Auto-Discover of Radios and Devices Circuit provisioning and collection Configure logical containers 3-62 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 177

93 ProVision Installation, Configuration & Management Creating map annotation Reports Generate helpdesk reports Generate capacity, inventory and fault reports Generate network health reports Generate security status report of radios and devices Configure schedule reports Customize reports from report fields and objects ProVision Installation and Administration Understand ProVision server/client relationship Creating regional access for users Session manager administration server configuration Understand communication with network elements Administer database manual and scheduled backup and security profiles Northbound Interface (NBI) description and configuration Configure ProVision redundancy controller Discuss remote access options Understand licensing requirements and procedures Duration: Delivery Method: Target Audience: Course Synopsis: Prerequisite: 3 days IRU600 Installation, Operation and Maintenance ILT - Instructor-led training Installation and service personnel responsible for installation, configuration, test and maintenance procedures for the IRU600 radio platform. Upon successfully completing this course, participants will be able to perform: List the functions and features of the Eclipse w/ IRU600 RFU Describe the hardware and configurations of the Eclipse w/ IRU600 RFU Configure and commission the Eclipse w/ IRU600 RFU Perform local and remote troubleshooting using Portal Participants should have a basic understanding of Microwave and IP Fundamentals and have basic computer skills. Each student must bring an IBM compatible laptop PC or an equivalent and have administrator rights on the PC. The PC must have minimum parameters of: Pentium 4 or later w/ 1GB of RAM and 250 Mb of free hard drive space USB Port Ethernet 10Base-T LAN port with RJ-45 connector for local Ethernet connection 800x600 resolution, 256 color display (16-bit color) Microsoft Windows XP, Vista, or Windows 7 p. 178 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-63

94 Course Outline: Overview IRU600 Installation, Operation and Maintenance TCP/IP installed and configured for LAN operation Web browser (Google Chrome recommended) Description and Features System layout RF options Capacity options Portal Intelligent Nodal Unit Configurations Basic Architecture and Capabilities Plug-ln cards Backplane bus Slot assignment rules Node capacity rules and licensing Path capacity and bandwidth options Eclipse packet node Ethernet with DAC GE3 and DAC GE IDU GE3 16x Basic Microwave Theory Technical parameters Bandwidth, modulation and capacity Indoor RF vs. Split Mount Nodal Concept Radio Frequency Unit Configurations IRU 600v.1, v.2 and v.3 Standard and high power ACU Fans Protection options TDM ring protection, NCM and SPDH ACM Link aggregation ATPC CCDP w/xpic Software Configuration and Commissioning Introduction to Portal Craft Tool Portal PC configuration for Ethernet and V.24/RS-232 connections Portal screens Configuring a new installation Portal and configuration LAB Diagnostics Tools Introduction to portal diagnostics System summary 3-64 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 179

95 IRU600 Installation, Operation and Maintenance Event browser System controls: locks and loopbacks Performance and history screens Alarm screens Parts Diagnostics lab Maintenance Maintenance overview / Annual PM IRU600 software configuration Configuration lab Troubleshooting Troubleshooting overview Troubleshooting lab p. 180 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-65

96 This page intentionally left blank Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 181

97 3.5 CUTOVER PLAN Phase I Columbia County, Florida Leveraging our technical and operational understanding of Columbia County, we are uniquely positioned to ensure a seamless transition and cutover to the new system with no impact to user operation. In order to transition from Columbia County s existing radio system(s) to the proposed new ASTRO 25 radio system, Columbia County and Motorola Solutions will need to develop a system migration and cutover plan. This plan, when executed precisely, will allow Columbia County users to transition as smoothly as possible and with minimal interruption onto the new system. It is not the purpose of this document to present a final plan, but rather to identify the key components that will be transitioned, to highlight the challenges associated with those transitions and to present recommended directions and solutions for each one of the key components. The final detailed plan will be developed as a joint collaboration between Motorola Solutions, the Columbia County technical team and the individual system users or their representatives. The Cutover Plan will be divided into two phases: Phase I: Pre-Cutover Preparation Phase II: Cutover Execution The pre-cutover phase is the most important phase. This is where all the planning of the detailed cutover plan occurs for a successful cutover execution. The following outline establishes the starting point for cutover planning to aid Columbia County and Motorola Solutions in the crafting of a viable cutover strategy. Careful up-front cutover planning will require Columbia County and Motorola Solutions to work closely with end users to assure minimum disruption. Upon conclusion of the Detailed Design Review phase of the project, the Columbia County and Motorola Solutions project teams will commence activities to transform the following Preliminary Cutover Plan Outline into a comprehensive and detailed Cutover Plan complete with a timeline of events that will guide the collective actions leading up to, during and following the actual transition from the existing radio system(s) to the new ASTRO 25 system Preliminary Cutover Plan Outline We propose the installation of the new ASTRO 25 radio system in parallel with the existing radio system infrastructure. Once the new ASTRO 25 radio system is installed and operational, this will enable a seamless migration from the existing radio system(s) to ASTRO 25 system. Below is a detailed list of prerequisites, constraints and assumptions that will need to be taken into consideration during this cutover planning phase Cutover Steps Overview The major steps of a migration include: 1. Build subscriber database (fleet mapping) for new ASTRO 25 system 2. Installation of the new antennas and microwave network equipment 3. Installation of the ASTRO 25 Master Site and Backup Master Site equipment 4. Installation of the Simulcast Prime Site and Backup Prime Site equipment 5. Installation of the Simulcast Remote Site equipment 6. Installation of subsystems (MCC 7500 dispatch console and backup control stations, etc.) p. 182 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-67

98 7. Test and configure interfaces to the new ASTRO 25 system 8. Migrate users to ASTRO 25 system Identification of Prerequisites/Constraints/Assumptions 1. Motorola Solutions will install, configure, optimize and test the following prior to cutover: A. Microwave transport network infrastructure B. ASTRO 25 radio system infrastructure C. MCC 7500 dispatch consoles and associated interfaces D. Network management clients E. Program consoles for existing Fire Paging System F. Program new mobile and portable subscriber radios G. Develop migration plan to new ASTRO 25 system 2. FCC Licensing: A. Licensing will have been completed to add new 700 MHz licenses to the sites to operate on the new ASTRO P25 radio system prior to the cutover date. 3. Acceptance/Reliability/Redundancy Testing: A. Functional Testing: All Field Functional Testing should be performed and approved by Columbia County B. Coverage Testing: Coverage test should be completed and accepted by Columbia County prior to the cutover date 4. Fleetmapping: A. Subscribers: All P25 subscribers capable of operating in the new ASTRO 25 system should have been programmed by Motorola Solutions with the new ASTRO 25 code plug information tested and verified by the Columbia County and Motorola Solutions implementation teams. B. Dispatch Consoles: All new proposed MCC 7500 and MCC 7100 Dispatch Consoles should be tested and all screen layouts should be approved by Columbia County prior to cutover. C. Interoperability: All interoperability interfaces should have been tested by the Columbia County and Motorola Solutions implementation teams. D. Database Provisioning/Archiving: System databases should have been created in the new ASTRO 25 system, tested and verified by the Columbia County and Motorola Solutions implementation teams. 5. Training: A. All required training should have been performed prior to cutover Detailed Timeline/Sequence of Events A. Inter-System Scheduling Relationships (Radio/Dispatch /Logging): A detailed schedule of events for the cutover will be developed jointly with Columbia County and Motorola Solutions. This schedule will include details about other systems essential for the operations of the EOC Dispatch Center like Radio Logging Recorder. B. Fallback Strategies/Contingency Plans: A detailed fallback plan will be identified by the Columbia County and Motorola Solutions implementation teams. This fallback plan will clearly identify the failures, causes and/or events that will activate the fallback plan, the 3-68 Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 183

99 backup subsystems to use and who in Columbia County will have the ultimate responsibility to activate the fallback plan. C. Dates/Timeframes to Avoid (Holidays, etc.): The detailed timeline and schedule will avoid holidays or special events occurring that impact agency operations. It is desired to implement the cutover at a time and date of low traffic in the system to minimize the impact on the users. D. Personnel/Staffing Requirements (County and Vendors): Columbia County will coordinate the staffing required of its personnel for the dates of cutover. The Motorola Solutions team will coordinate the staffing required of the involved vendors for the dates of the cutover Post-Cutover Strategy Phase II Short-Term and Long-Term Support Requirements: Once the transition to the new system is completed Columbia County and Motorola Solutions will determine how long the legacy system(s) should be kept in operations to support any agency or radio users that have not made the transition to the new system after the cutover. Phase II of the plan is where the execution of the pre-defined plan in Phase I takes place. A high-level view of the cutover is outlined below Migrate Trunking Infrastructure Motorola Solutions proposes a parallel implementation of the new ASTRO 25 radio system with the existing radio system. This will include complete installation of the microwave transport network, installation of the ASTRO 25 radio equipment and installation of the MCC 7500 dispatch consoles at the Columbia County EOC PSAP. Once installation, optimization and testing of the system has been completed, a cutover of Columbia County s operations to the new system will be performed. The following are prerequisites to the cutover of to the ASTRO 25 radio system infrastructure: Licensing of all frequencies, which will be utilized by the ASTRO 25 radio system. This includes new licenses for all microwave network frequencies, as well as new licenses to add the 700 MHz, frequencies at new sites, as well as any necessary modifications to the existing frequencies at existing sites. Installation, optimization and testing of the microwave transport. Installation, optimization and testing of the ASTRO 25 radio system infrastructure. Installation, optimization and testing of the MCC 7500 dispatch consoles. Installation, optimization and testing of any other purchased subsystems. Programming of all mobile and portable subscriber radios capable of operation on the new radio system. The County and Motorola Solutions will collaborate on identifying groups of radios ( fleets or user groups ) that will be transitioned together onto the new system and an appropriate timetable for each group transition. Radios in each user group will be identified and a determination will be made for each radio as to the appropriate procedure to transition it. Once all groups have been identified and each radio classified, it will be necessary for the project team to choose the order, set a transition schedule and create the detailed procedure for each group transition. Motorola Solutions will do the bulk of the work for this process but will require regular meetings with Columbia County technical authorities to refine and approve each step. p. 184 Motorola Solutions Confidential Restricted Project Management Plan, Implementation, Schedule and Cutover 3-69

100 Existing System Decommission When the successful migration from the existing system to the new ASTRO 25 radio system has been completed, the effort to decommission the existing system will begin. Motorola Solutions will remove and dispose of the legacy antennas, microwave and radio at each applicable site. With the completion of the equipment removal, Columbia County and Motorola Solutions can transition into the Final System Acceptance phase Project Management Plan, Implementation, Schedule and Cutover Motorola Solutions Confidential Restricted p. 185

101 ID Task Name Duration Start Finish Resource Names 1 COMMUNICATION SITE DEVELOPMENT PROJECT SITE DEVELOPMENT SCHEDULE days Wed 1/3/18 Mon 10/8/18 rter 1st Quarter 2nd Quarter 3rd Quarter 4th Quart Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov 2 PRE CONSTRUCTION PHASE 101 da... Wed 1/3/18 Wed 5/23/18 3 Contract Signed/NTP from Columbia County, FL 0 days Wed 1/3/18 Wed 1/3/18 4 SITE ENGINEERING 39 days Wed 1/3/18 Mon 2/26/18 12 PERMITTING AND FINAL DRAWINGS 77 days Tue 2/6/18 Wed 5/23/18 30 MANUFACTURING PHASE 41 days Thu 3/22/18 Thu 5/17/18 33 CONSTRUCTION PHASE Thu 3/29/18 Fri 9/14/18 34 SITE PREPARATION 15 days Thu 5/24/18 Wed 6/13/18 41 TOWER WORK 69.5 d... Thu 3/29/18 Wed 7/4/18 50 SITE COMPONENTS INSTALLATION 28 days Tue 7/3/18 Fri 8/10/18 67 SITE RESTORATION 10 days Fri 8/17/18 Fri 8/31/18 72 FINAL TESTING 21 days Thu 8/16/18 Fri 9/14/18 80 TOWER MW days Tue 1/30/18 Tue 9/4/18 85 P25 SYSTEM INSTALLATION/OPTIMIZATION 7 days Tue 9/4/18 Thu 9/13/18 86 Install 5 days Tue 9/4/18 Tue 9/11/18 87 Optimization 2 days Tue 9/11/18 Thu 9/13/18 88 AUDIT AND ACCEPTANCE TESTING 8 days Tue 9/11/18 Fri 9/21/18 89 PERFORM R-56 AUDIT 4 days Tue 9/11/18 Mon 9/17/18 92 TESTING 6 days Thu 9/13/18 Fri 9/21/18 95 FINAL SYSTEM ACCEPTANCE 10 days Fri 9/21/18 Fri 10/5/18 1/3 5/23 1/3 1/3 2/26 2/6 5/23 3/22 5/17 3/29 9/14 5/24 6/13 3/29 7/4 7/3 8/10 8/17 8/31 8/16 9/14 1/30 9/4 9/4 9/13 9/4 9/11 9/11 9/13 9/11 9/21 9/11 9/17 9/13 9/21 9/21 10/5 Page 1 of 1 Printed Wed 10/25/17 at 6:38 PM Motorola Confidential & Proprietary Non-critical Task Split Milestone Summary Critical Task Inactive Task Inactive Milestone Inactive Summary Manual Task Duration-only Manual Summary Rollup Manual Summary Start-only Finish-only Progress p. 186

102 ID Task Name Duration Start Finish Resource Names 1 COMMUNICATION SITE DEVELOPMENT PROJECT days Wed 1/3/18 Mon 10/8/18 2 PRE CONSTRUCTION PHASE 101 da... Wed 1/3/18 Wed 5/23/18 3 Contract Signed/NTP from Columbia County, FL 0 days Wed 1/3/18 Wed 1/3/18 4 SITE ENGINEERING 39 days Wed 1/3/18 Mon 2/26/18 5 Site location agreement between owner and 0 days Wed 1/3/18 Wed 1/3/18 Columbia County, FL 6 Site visit with A&E 2 days Mon 1/8/18 Tue 1/9/18 7 Prepare site sketch/lease Exhibit 2 days Fri 1/12/18 Mon 1/15/18 8 Review and approval of site sketch by 10 days Tue 1/16/18 Mon 1/29/18 Columbia County, FL, owner and Motorola 9 Site survey and mapping 7 days Fri 2/2/18 Mon 2/12/18 10 Preliminary drawings for zoning/columbia 5 days Tue 2/13/18 Mon 2/19/18 County, FL approval 11 Review and approval of drawings by Columbia County, FL, owner and Motorola 5 days Tue 2/20/18 Mon 2/26/18 12 PERMITTING AND FINAL DRAWINGS 77 days Tue 2/6/18 Wed 5/23/18 13 New tower zoning application and approvals 30 days Tue 2/27/18 Mon 4/9/18 BY COUNTY 14 NEPA/SHPO studies and approvals - LIMITED 50 days Tue 2/6/18 Mon 4/16/18 15 Geotechnical Testing and Report 9 days Thu 2/15/18 Tue 2/27/18 16 FAA application (7460-1) and approval - BY 20 days Tue 2/20/18 Mon 3/19/18 COUNTY 17 FCC Tower Registration Application - BY COU 3 days Tue 4/17/18 Thu 4/19/18 18 Confirm tower foundation designs based on 5 days Wed 2/28/18 Tue 3/6/18 Geotech Report 19 Order Tower Materials based on final antenna 5 days Wed 3/7/18 Tue 3/13/18 locations 20 Tower design and drawings 6 days Wed 3/14/18 Wed 3/21/18 21 Place order for building based on entry port 5 days Wed 3/7/18 Tue 3/13/18 orientation 22 Shelter design and drawings 5 days Wed 3/14/18 Tue 3/20/18 23 Complete Final Detailed drawings for 7 days Tue 4/10/18 Wed 4/18/18 Columbia County, FL review 24 Columbia County, FL approval of Final 5 days Thu 4/19/18 Wed 4/25/18 Construction drawings 25 Site release/ Construction NTP to Contractor 0 days Fri 4/27/18 Fri 4/27/18 26 Building and construction permit application 15 days Thu 5/3/18 Wed 5/23/18 and approval 27 Land Disturbance permit application and appro 10 days Thu 5/3/18 Wed 5/16/18 28 Electrical Permit application and approval 10 days Thu 5/3/18 Wed 5/16/18 29 Permits Approved 0 days Wed 5/23/18 Wed 5/23/18 30 MANUFACTURING PHASE 41 days Thu 3/22/18 Thu 5/17/18 31 Tower Manufacturing 40 days Thu 3/22/18 Wed 5/16/18 32 Shelter manufacturing 40 days Fri 3/23/18 Thu 5/17/18 33 CONSTRUCTION PHASE Thu 3/29/18 Fri 9/14/18 34 SITE PREPARATION 15 days Thu 5/24/18 Wed 6/13/18 35 Mobilization 1 day Thu 5/24/18 Thu 5/24/18 36 Locate existing utilities 1 day Tue 5/29/18 Tue 5/29/18 37 Construction staking 1 day Wed 5/30/18 Wed 5/30/18 38 Light compound grading and silt fencing 4 days Fri 6/1/18 Wed 6/6/18 39 Pick up meter panel and Install meterboard 2 days Thu 6/7/18 Fri 6/8/18 40 Utility hookup to the site by Electric Co. 5 days Thu 6/7/18 Wed 6/13/18 41 TOWER WORK 69.5 d... Thu 3/29/18 Wed 7/4/18 42 Ship anchor bolts and base plates to the site 4 days Thu 3/29/18 Tue 4/3/18 43 Drill, rebar and pour pier and pad foundation 5 days Thu 6/7/18 Wed 6/13/18 44 Foundation Inspection/concrete testing 0.5 days Tue 6/12/18 Tue 6/12/18 45 Tower grounding 1 day Tue 6/12/18 Wed 6/13/18 46 Strip forms, backfill and compaction 1 day Tue 6/19/18 Wed 6/20/18 SITE DEVELOPMENT SCHEDULE 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov 1/3 5/23 1/3 1/3 2/26 1/3 1/8 1/9 1/12 1/15 1/16 1/29 2/2 2/12 2/13 2/19 2/20 2/26 2/6 5/23 2/27 4/9 2/6 4/16 2/15 2/27 2/20 3/19 2/28 3/6 3/7 3/13 3/14 3/21 3/7 3/13 4/17 4/19 3/14 3/20 4/10 4/18 4/19 4/25 4/27 5/3 5/23 5/3 5/16 5/3 5/16 5/23 3/22 5/17 3/22 5/16 3/23 5/17 3/29 9/14 5/24 6/13 5/24 5/24 5/29 5/29 5/30 5/30 6/1 6/6 6/7 6/8 6/7 6/13 3/29 7/4 3/29 4/3 6/7 6/13 6/12 6/12 6/12 6/13 6/19 6/20 Page 1 of 2 Printed Wed 10/25/17 at 6:21 PM Motorola Confidential & Proprietary Non-critical Task Split Critical Task Inactive Task Manual Task Duration-only Start-only Finish-only Milestone Inactive Milestone Manual Summary Rollup Progress Summary Inactive Summary Manual Summary p. 187

103 ID Task Name Duration Start Finish Resource Names 47 Ship tower to site 4 days Tue 6/19/18 Mon 6/25/18 48 Tower assembly and stacking 5 days Tue 6/26/18 Tue 7/3/18 49 Tower plumbness testing 1 day Tue 7/3/18 Wed 7/4/18 50 SITE COMPONENTS INSTALLATION 28 days Tue 7/3/18 Fri 8/10/18 51 Trench and Install underground power conduits 5 days Tue 7/3/18 Tue 7/10/18 52 Trench and Install conduits for underground tel 2 days Thu 7/5/18 Mon 7/9/18 53 Trench and install grounding 2 days Tue 7/10/18 Thu 7/12/18 54 Grounding Inspection 0.5 days Thu 7/12/18 Thu 7/12/18 55 Conduit inspection and backfill 1 day Tue 7/10/18 Wed 7/11/18 56 Excavate, form and rebar shelter foundations 3 days Wed 7/11/18 Mon 7/16/18 57 Excavate, form and rebar generator foundation 1 day Fri 7/13/18 Mon 7/16/18 58 Foundation inspection, concrete pour and testin 1 day Mon 7/16/18 Tue 7/17/18 59 Ship shelter to site 2 days Fri 7/20/18 Tue 7/24/18 60 Offload and Install equipment shelter 2 days Tue 7/24/18 Thu 7/26/18 61 Offload and Install generator 2 days Tue 7/24/18 Thu 7/26/18 62 Install fuel tank and piping 2 days Tue 7/31/18 Thu 8/2/18 63 Piping inspection, leakage test and trench back 2 days Thu 8/2/18 Mon 8/6/18 64 Cabling and hook up power system to shelter, 3 days Mon 8/6/18 Thu 8/9/18 ATS, generator 65 Building/Electrical inspection 1 day Thu 8/9/18 Fri 8/10/18 66 Install ice bridge from shelter to the tower 2 days Mon 8/6/18 Wed 8/8/18 67 SITE RESTORATION 10 days Fri 8/17/18 Fri 8/31/18 68 Finish Grade and gravel compound 2 days Fri 8/17/18 Tue 8/21/18 69 Fencing of tower compound 3 days Thu 8/23/18 Tue 8/28/18 70 Complete grounding connections 1 day Tue 8/28/18 Wed 8/29/18 71 Site touchup and restoration 2 days Wed 8/29/18 Fri 8/31/18 72 FINAL TESTING 21 days Thu 8/16/18 Fri 9/14/18 73 Generator Startup/Test power system 1 day Thu 8/16/18 Fri 8/17/18 74 Grounding test of the site 0.5 days Wed 8/29/18 Wed 8/29/18 75 Startup/Test shelter power System 1 day Mon 8/20/18 Tue 8/21/18 76 Punch List with Columbia County, FL 0.5 days Fri 8/31/18 Fri 8/31/18 77 Punch List completion 10 days Fri 8/31/18 Fri 9/14/18 78 As-Built drawings from A&E 7 days Fri 8/31/18 Tue 9/11/18 79 Site Development Completion 0 days Fri 9/14/18 Fri 9/14/18 80 TOWER MW days Tue 1/30/18 Tue 9/4/18 81 MW Path Survey 3 days Tue 1/30/18 Thu 2/1/18 82 MW Path Survey Report 5 days Fri 2/2/18 Thu 2/8/18 83 MFG MW Equipment Antenna/LMR Antennas 50 days Fri 2/9/18 Thu 4/19/18 84 Installation/Optimization 10 days Tue 8/21/18 Tue 9/4/18 85 SYSTEM INSTALLATION/OPTIMIZATION 7 days Tue 9/4/18 Thu 9/13/18 86 Install 5 days Tue 9/4/18 Tue 9/11/18 87 Optimization 2 days Tue 9/11/18 Thu 9/13/18 88 AUDIT AND ACCEPTANCE TESTING 8 days Tue 9/11/18 Fri 9/21/18 89 PERFORM R-56 AUDIT 4 days Tue 9/11/18 Mon 9/17/18 90 Audit R-56 RF Sites 1 day Tue 9/11/18 Wed 9/12/18 91 R-56 Punch List Resolution 3 days Wed 9/12/18 Mon 9/17/18 92 TESTING 6 days Thu 9/13/18 Fri 9/21/18 93 Perform System ATP 1 day Thu 9/13/18 Fri 9/14/18 94 Perform CATP 5 days Fri 9/14/18 Fri 9/21/18 95 FINAL SYSTEM ACCEPTANCE 10 days Fri 9/21/18 Fri 10/5/18 96 Punch List Resolution 5 days Fri 9/21/18 Fri 9/28/18 97 Create Documentation 5 days Fri 9/28/18 Fri 10/5/18 98 Final System Acceptance 0 days Fri 10/5/18 Fri 10/5/18 SITE DEVELOPMENT SCHEDULE 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov 6/19 6/25 6/26 7/3 7/3 7/4 7/3 8/10 7/3 7/10 7/5 7/9 7/10 7/12 7/12 7/12 7/10 7/11 7/11 7/16 7/13 7/16 7/16 7/17 7/20 7/24 7/24 7/26 7/24 7/26 7/31 8/2 8/2 8/6 8/6 8/9 8/9 8/10 8/6 8/8 8/17 8/31 8/17 8/21 8/23 8/28 8/28 8/29 8/29 8/31 8/16 9/14 8/16 8/17 8/29 8/29 8/20 8/21 8/31 8/31 8/31 9/14 8/31 9/11 9/14 1/30 9/4 1/30 2/1 2/2 2/8 2/9 4/19 8/21 9/4 9/4 9/13 9/4 9/11 9/11 9/13 9/11 9/21 9/11 9/17 9/11 9/12 9/12 9/17 9/13 9/21 9/13 9/14 9/14 9/21 9/21 10/5 9/21 9/28 9/28 10/5 10/5 Page 2 of 2 Printed Wed 10/25/17 at 6:21 PM Motorola Confidential & Proprietary Non-critical Task Split Critical Task Inactive Task Manual Task Duration-only Start-only Finish-only Milestone Inactive Milestone Manual Summary Rollup Progress Summary Inactive Summary Manual Summary p. 188

104 Columbia County, FL - Project Schedule ID Task Name Duration Start Finish 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug 0 COLUMBIA COUNTY, FL PROJECT SCHEDULE 196 days Thu 11/16/17 Thu 8/16/18 1 CONTRACT NEGOTIATION 0 days Thu 11/16/17 Thu 11/16/17 2 Contract Execution / Notice to Proceed 0 days Thu 11/16/17 Thu 11/16/17 3 CONTRACT DESIGN REVIEW 6 days Thu 11/16/17 Thu 11/23/17 4 CDR Development 5 days Thu 11/16/17 Wed 11/22/17 5 Contract Design Review with Columbia 1 day Thu 11/23/17 Thu 11/23/17 6 Invoice Milestone: Completion of Detailed Design 0 days Thu 11/23/17 Thu 11/23/17 7 MANUFACTURING AND STAGING 69 days Fri 11/17/17 Wed 2/21/18 8 ORDER PROCESSING 5 days Fri 11/24/17 Thu 11/30/17 12 EQUIPMENT MANUFACTURING 43 days Fri 12/1/17 Tue 1/30/18 16 STAGING KICK-OFF 8 days Fri 11/17/17 Tue 11/28/17 19 STAGING AT CCSI 34 days Fri 1/5/18 Wed 2/21/18 20 Receipt and Inventory Equipment 1 day Fri 1/5/18 Fri 1/5/18 21 Install 15 days Mon 1/8/18 Fri 1/26/18 22 Optimization 15 days Mon 1/29/18 Fri 2/16/18 23 Factory Acceptance Test 1 day Mon 2/19/18 Mon 2/19/18 24 Acceptance by the Customer 0 days Mon 2/19/18 Mon 2/19/18 25 Ship Staged Equipment to Field 2 days Tue 2/20/18 Wed 2/21/18 26 Invoice Milestone: Equipment Shipment 0 days Wed 2/21/18 Wed 2/21/18 27 FLEET MAPPING 124 days Thu 12/14/17 Tue 6/5/18 28 Initial Fleet Mapping/Training Meeting 5 days Thu 12/14/17 Wed 12/20/17 29 Customer Develops Initial Fleet map Configurations 40 days Thu 12/21/17 Wed 2/14/18 30 Develop Final Fleet map Configurations 5 days Thu 2/15/18 Wed 2/21/18 31 COUNTY Approval of Fleet Map 3 days Thu 2/22/18 Mon 2/26/18 32 Develop Programming code plugs 5 days Tue 2/27/18 Mon 3/5/18 33 Review Radio Programming w/o system 10 days Tue 3/6/18 Mon 3/19/18 34 Test Radios TGs and features w/system Radio 10 days Wed 5/23/18 Tue 6/5/18 Programming w/o system 35 SITE DEVELOPMENT 83 days Thu 11/16/17 Mon 3/12/18 36 Tower MW Survey/SA/Permits 38 days Thu 11/16/17 Mon 1/8/18 37 MW Path Survey 3 days Thu 11/16/17 Mon 11/20/17 Preliminary Project Schedule.mpp Tue 10/31/17 Page 1 of 4 p. 189

105 Columbia County, FL - Project Schedule ID Task Name Duration Start Finish ter 4th Quarter 1st Quarter 2nd Quarter 3rd Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul 38 MW Path Survey Report 5 days Tue 11/21/17 Mon 11/27/17 39 Structural Analysis Complete 5 days Tue 11/28/17 Mon 12/4/17 40 Complete/Submit Permit Applications 10 days Tue 12/5/17 Mon 12/18/17 41 Permits Issued 15 days Tue 12/19/17 Mon 1/8/18 42 RF Antenna/Lines 32 days Fri 1/26/18 Mon 3/12/18 43 Receive RF Antenna/Lines 2 days Fri 1/26/18 Mon 1/29/18 44 Mobilization 10 days Tue 1/30/18 Mon 2/12/18 45 EOC 4 days Tue 2/13/18 Fri 2/16/18 46 CCSO 4 days Mon 2/19/18 Thu 2/22/18 47 LULU 4 days Fri 2/23/18 Wed 2/28/18 48 CUMORAH 4 days Thu 3/1/18 Tue 3/6/18 49 DEEP CREEK 4 days Wed 3/7/18 Mon 3/12/18 50 RF Antenna Complete 0 days Mon 3/12/18 Mon 3/12/18 51 Microwave 88 days Tue 11/28/17 Thu 3/29/18 52 MW FNE Install 72 days Tue 11/28/17 Wed 3/7/18 53 MFG and Receive FNE 55 days Tue 11/28/17 Mon 2/12/18 54 Mobilization 5 days Tue 2/13/18 Mon 2/19/18 55 EOC 2 days Tue 2/20/18 Wed 2/21/18 56 CCSO 2 days Thu 2/22/18 Fri 2/23/18 57 LULU 2 days Mon 2/26/18 Tue 2/27/18 58 CUMORAH 2 days Wed 2/28/18 Thu 3/1/18 59 DEEP CREEK 2 days Fri 3/2/18 Mon 3/5/18 60 FRANKLIN 2 days Tue 3/6/18 Wed 3/7/18 61 MW FNE Complete 0 days Wed 3/7/18 Wed 3/7/18 62 MW Antenna Install 83 days Tue 11/28/17 Thu 3/22/18 63 MFG and Receive MW Antenna/Lines 60 days Tue 11/28/17 Mon 2/19/18 64 Mobilization 5 days Tue 2/20/18 Mon 2/26/18 65 EOC 3 days Tue 2/27/18 Thu 3/1/18 66 CCSO 3 days Fri 3/2/18 Tue 3/6/18 67 LULU 3 days Wed 3/7/18 Fri 3/9/18 68 CUMORAH 3 days Mon 3/12/18 Wed 3/14/18 Preliminary Project Schedule.mpp Tue 10/31/17 Page 2 of 4 p. 190

106 Columbia County, FL - Project Schedule ID Task Name Duration Start Finish ter 4th Quarter 1st Quarter 2nd Quarter 3rd Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul 69 DEEP CREEK 3 days Thu 3/15/18 Mon 3/19/18 70 FRANKLIN 3 days Tue 3/20/18 Thu 3/22/18 71 MW Antenna Complete 0 days Thu 3/22/18 Thu 3/22/18 72 MW Optimization 5 days Fri 3/23/18 Thu 3/29/18 73 Burn-in 5 days Fri 3/23/18 Thu 3/29/18 74 SYSTEM INSTALLATION 39 days Thu 3/1/18 Tue 4/24/18 75 EOC (Prime/Master) 8 days Thu 3/1/18 Mon 3/12/18 76 EOC (Remote) 3 days Tue 3/13/18 Thu 3/15/18 77 CCSO (Prime/Master/Remote) 8 days Fri 3/16/18 Tue 3/27/18 78 LULU 4 days Wed 3/28/18 Mon 4/2/18 79 CUMORAH 5 days Tue 4/3/18 Mon 4/9/18 80 DEEP CREEK 4 days Tue 4/10/18 Fri 4/13/18 81 EOC Console 7 days Mon 4/16/18 Tue 4/24/18 82 FNE Install Complete 0 days Tue 4/24/18 Tue 4/24/18 83 SYSTEM OPTIMIZATION 35 days Wed 4/25/18 Tue 6/12/18 84 Remote Site Optimization 10 days Wed 4/25/18 Tue 5/8/18 85 Master/Prime and Console Config 25 days Wed 5/9/18 Tue 6/12/18 86 System Optimization Complete 0 days Tue 6/12/18 Tue 6/12/18 87 AUDIT AND ACCEPTANCE TESTING 49 days Wed 4/25/18 Mon 7/2/18 88 PERFORM R-56 AUDIT 15 days Wed 4/25/18 Tue 5/15/18 89 Audit R-56 RF Sites 5 days Wed 4/25/18 Tue 5/1/18 90 R-56 Punch List Resolution 10 days Wed 5/2/18 Tue 5/15/18 91 R-56 Audit Complete 0 days Tue 5/15/18 Tue 5/15/18 92 FUNCTIONAL TESTING 3 days Wed 6/13/18 Fri 6/15/18 93 Perform System ATP 3 days Wed 6/13/18 Fri 6/15/18 94 Functional Testing Acceptance 0 days Fri 6/15/18 Fri 6/15/18 95 PERFORM CATP 11 days Mon 6/18/18 Mon 7/2/18 96 Perform CATP 8 days Mon 6/18/18 Wed 6/27/18 97 Document CATP Results 3 days Thu 6/28/18 Mon 7/2/18 98 CATP Acceptance 0 days Mon 7/2/18 Mon 7/2/18 99 TRAINING 44 days Wed 4/11/18 Mon 6/11/18 Preliminary Project Schedule.mpp Tue 10/31/17 Page 3 of 4 p. 191

107 Columbia County, FL - Project Schedule ID Task Name Duration Start Finish ter 4th Quarter 1st Quarter 2nd Quarter 3rd Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul 100 PERFORM TRAINING 44 days Wed 4/11/18 Mon 6/11/ Training Complete 0 days Mon 6/11/18 Mon 6/11/ DAY PERFORMANCE 14 days Tue 7/3/18 Sun 7/22/ Begin 30 Day Performance Period (Colander days days Tue 7/3/18 Sun 7/22/18 Business) Day Performance Period Complete 0 days Sun 7/22/18 Sun 7/22/ CUTOVER/SUBSCRIBER INSTALLATION 40 days Wed 6/6/18 Tue 7/31/ Program and Distribute Portables 10 days Wed 6/6/18 Tue 6/19/ Program and Install Mobiles (Can we install prior to 30 days Wed 6/20/18 Tue 7/31/18 cutover) 108 Perform System Cutover (Portables Only) 7 days Mon 7/23/18 Tue 7/31/ Cutover Complete 0 days Tue 7/31/18 Tue 7/31/ FINAL SYSTEM ACCEPTANCE 12 days Wed 8/1/18 Thu 8/16/ Remove Old Equipment 12 days Wed 8/1/18 Thu 8/16/ Punch List Resolution 5 days Wed 8/1/18 Tue 8/7/ Create Documentation 5 days Wed 8/1/18 Tue 8/7/ Final System Acceptance 0 days Thu 8/16/18 Thu 8/16/18 Preliminary Project Schedule.mpp Tue 10/31/17 Page 4 of 4 p. 192

108 Columbia County, FL - Project Schedule ID Task Name Duration Start Finish 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug 0 COLUMBIA COUNTY, FL PROJECT SCHEDULE 196 days Thu 11/16/17 Thu 8/16/18 1 CONTRACT NEGOTIATION 0 days Thu 11/16/17 Thu 11/16/17 3 CONTRACT DESIGN REVIEW 6 days Thu 11/16/17 Thu 11/23/17 7 MANUFACTURING AND STAGING 69 days Fri 11/17/17 Wed 2/21/18 8 ORDER PROCESSING 5 days Fri 11/24/17 Thu 11/30/17 12 EQUIPMENT MANUFACTURING 43 days Fri 12/1/17 Tue 1/30/18 16 STAGING KICK-OFF 8 days Fri 11/17/17 Tue 11/28/17 19 STAGING AT CCSI 34 days Fri 1/5/18 Wed 2/21/18 27 FLEET MAPPING 124 days Thu 12/14/17 Tue 6/5/18 35 SITE DEVELOPMENT 83 days Thu 11/16/17 Mon 3/12/18 36 Tower MW Survey/SA/Permits 38 days Thu 11/16/17 Mon 1/8/18 42 RF Antenna/Lines 32 days Fri 1/26/18 Mon 3/12/18 51 Microwave 88 days Tue 11/28/17 Thu 3/29/18 52 MW FNE Install 72 days Tue 11/28/17 Wed 3/7/18 62 MW Antenna Install 83 days Tue 11/28/17 Thu 3/22/18 72 MW Optimization 5 days Fri 3/23/18 Thu 3/29/18 74 SYSTEM INSTALLATION 39 days Thu 3/1/18 Tue 4/24/18 83 SYSTEM OPTIMIZATION 35 days Wed 4/25/18 Tue 6/12/18 87 AUDIT AND ACCEPTANCE TESTING 49 days Wed 4/25/18 Mon 7/2/18 88 PERFORM R-56 AUDIT 15 days Wed 4/25/18 Tue 5/15/18 92 FUNCTIONAL TESTING 3 days Wed 6/13/18 Fri 6/15/18 95 PERFORM CATP 11 days Mon 6/18/18 Mon 7/2/18 99 TRAINING 44 days Wed 4/11/18 Mon 6/11/ DAY PERFORMANCE 14 days Tue 7/3/18 Sun 7/22/ CUTOVER/SUBSCRIBER INSTALLATION 40 days Wed 6/6/18 Tue 7/31/ FINAL SYSTEM ACCEPTANCE 12 days Wed 8/1/18 Thu 8/16/18 Preliminary Project Schedule.mpp Tue 10/31/17 Page 1 of 1 p. 193

109 PROPOSAL TO COLUMBIA COUNTY, FLORIDA SECTION 4 NEGOTIATED TECHNICAL APPROACH AND PROPOSED SOLUTION APCO P25 700MHZ RADIO SYSTEM PROJECT NOVEMBER 8, 2017 RFP-2017-O The design, technical, pricing and other information ( Information ) furnished with this submission is proprietary and/or trade secret information of Motorola Solutions, Inc. ( Motorola Solutions ) and is submitted with the restriction that it is to be used for evaluation purposes only. To the fullest extent allowed by applicable law, the Information is not to be disclosed publicly or in any manner to anyone other than those required to evaluate the Information without the express written permission of Motorola Solutions. MOTOROLA SOLUTIONS, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Solutions Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners Motorola Solutions, Inc. All rights reserved. p. 194

110 p. 195

111 TABLE OF CONTENTS Section 4 Technical Approach and Proposed Solution Solution Overview System Description Main Master Site at Columbia County EOC Communications Room Dynamic System Resilient (DSR) Master Site at the Deep Creek Radio Site Simulcast Subsystem Equipment Simulcast Prime Equipment at the EOC Communications Room Geo-Redundant Simulcast Prime Equipment at the Deep Creek Radio Site Simulcast Remote Site Overview Dispatch Consoles Subsystem IP Console Design and Dispatch Centers Integration with the ASTRO 25 Network City of Columbia County Dispatch Systems Columbia County EOC PSAP MCC 7500E Enhanced Dispatch Experience MCC 7100 Dispatch Console APX 7500 Consolettes Logging Recorder (Option) ISSI/CSSI 8000 Gateway System Project 25 ISSI Trunking Interface Project 25 CSSI 8000 Console Interface Integrated Voice and Data Capabilities Applications Utilizing the IV&D System Enhancement Encryption Capabilities- Optional Encryption Types - Option Rekeying Methods - Optional Project 25 Phase 2 TDMA FDMA/TDMA Interoperability Motorola Solutions Wave Broadband PTT Land Mobile Radio (LMR) Interface WAVE Server Features Mutual Aid RF MHz Mutual Aid Repeaters Microwave Backhaul Network Microwave Path Design Backup Power Systems System Spares ASTRO25 System Features Columbia County, Florida p. 196 Motorola Solutions Confidential Restricted Table of Contents i

112 4.4.1 Simulcast /800 MHz Operation Centralized System Management ASTRO25 Trunking Call Services Call Categories Network Management System Zone Database Server User Configuration Server Unified Event Manager (UEM) UEM Event Browser UEM Alarm Browser Environmental Alarms Inputs and Outputs Included on Each SDM 3000 RTU Example of Local Environmental Alarms Alerting Network Management Terminals and Licenses Provisioning Manager Radio Control Manager ZoneWatch Channel Grid and Control Zone Historical Reports Dynamic Reports Affiliation User Display Radio Authentication MCC 7500E System Description Architecture Overview Connection of MCC 7500E to IP Network Feature Descriptions ASTRO25 System Failure Mode Analysis Wide Area Trunking Site Trunking Failsoft by Talkgroup Narrative of Failure Analyses ASTRO25 Fixed Network Equipment Design Zone Core Zone Core LAN Switch Configuration ASTRO25 Prime Site Design GCP 8000 Site Controller Prime Site Routers GCM 8000 Channel Comparators Prime Site Ethernet LAN Switches TRAK 9100 Time and Frequency Standard Redundant Remote Site Routers ii Table of Contents Columbia County, Florida Motorola Solutions Confidential Restricted p. 197

113 Ethernet LAN Switches GTR8000 Expandable Site Subsystem (ESS) IV&D System Design RF Infrastructure and Subscriber Units GPRS Gateway Support Node Packet Data Gateway (PDG) Packet Data Router MCC 7500E Dispatch Console Workstation Computer Audio Interface Module Desktop Gooseneck Microphone Headset Jack Dispatch Speaker Footswitch Backup Operations and Failure Indications Analog Conventional Equipment Design GTR Regional Interoperability Levels of Interoperability Interoperability with Surrounding Jurisdictions Subscribers Radio Equipment Requirements APX Durability APX Advanced Hardware Features APX Advanced Software Features APX End-to-End Voice Encryption APX End-to-End Data Encryption Option APX Transmitter and Receiver Performance APX XE Portable Radios APX Accessories Remote Speaker Microphones (RSMs) Motorola Solutions Mission Critical Wireless Advantages IMPRES 2 Technology Batteries and Battery Chargers Mobile Radio and Control Station Equipment Portable Radio Equipment System-Level Block Diagrams Acceptance Testing Coverage Methodology Hydra SM Overview Hydra Development Hydra Detailed Description Hydra Capabilities Columbia County, Florida p. 198 Motorola Solutions Confidential Restricted Table of Contents iii

114 Summary Coverage Acceptance Test Plan (CATP) CATP Definitions Equipment Configurations In Building Coverage CATP Method Responsibilities and Preparation CATP Procedures CATP Documentation and Coverage Acceptance Mobile/Portable Equipment Checklist Spares List Coverage Maps iv Table of Contents Columbia County, Florida Motorola Solutions Confidential Restricted p. 199

115 SECTION 4 TECHNICAL APPROACH AND PROPOSED SOLUTION The intent of this proposal is to provide Columbia County with a Project 25 (P25) radio system that is rich in features, highly redundant and manageable long into the future. This section provides an overview of Motorola Solutions latest ASTRO25 system release solution. Our ASTRO25 system provides the County with system reliability, fault tolerance, ease of migration, highest return on investment and additional numerous advantages including redundant geographically diverse Simulcast Prime Site Controllers and Master Sites. Based on the requirements of the RFP, we have developed a system design for Columbia County s consideration: 700 MHz Simulcast System This system design would provide Columbia County with a high level of redundancy for the radio system infrastructure. Motorola Solutions has carefully reviewed the RFP released by Columbia County to develop a 100% technically compliant, comprehensive solution for a Project 25 (P25) 700 MHz communications system. We propose the utilization of five of the County s existing allotment of 700 MHz frequencies and use of the five tower sites identified in the RFP. This solution will replace the County s VHF radio system currently in use and provide a single solution empowering Columbia to communicate in a manner that has not been achievable before. Our proposed solution will provide reliable communications through redundant master and prime simulcast sites, controlling a coverage network that meets the RFP s required simulcast and site selection requirements. By consolidating the various radio systems currently in use by the County and County s local government agencies, the proposed system will enable them to communicate seamlessly with one another and leverage the features of our ASTRO25 technology to interoperate with other P25 and conventional systems in the area. Motorola Solutions is also proposing several subsystems, as required in the RFP: Digital Microwave Radio Ethernet Backhaul Transport System We propose a licensed 6 GHz Ethernet microwave backhaul network to support the operation of the radio system. This microwave radio system s design will provide the performance, bandwidth and reliability requirements of the RFP. MCC 7500E and MCC7100 Dispatch Consoles We propose a 9-position MCC 7500E radio dispatch console, which will be installed at the existing Columbia County EOC PSAP. We are also including an additional nine console positions for mobile operation that can be used outside of the Radio Network Infrastructure (RNI) and interfaced through a Firewall connected to the County s network. These operator positions use the MCC7100 dispatch application on a Windows 10 Laptop. These nine mobile operator Laptops will interface via a Proxy Server that will reside in the EOC and may also serve as a tenth operator position for maintenance. We propose using the existing VHF analog Tone and Voice paging system. The existing paging system will interface with the proposed MCC 7500E dispatch console through a Conventional Channel Gateway (CCGW) and will provide the capability for dispatchers to page Fire stations and personnel throughout Columbia County as they are operating today. Included in the ASTRO25 proposed system is the trunking Call Alert p. 200 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-5

116 feature. Many Fire Departments have transitioned to the Call Alert operation and this exists as an attractive alternative that Columbia County may consider either as a replacement or as a compliment to the existing legacy Fire Paging system. We are also introducing the MCC7500EE Dispatch Console, available in early The new features available through the MCC7500EE include the following: Fault-tolerant, dual network connection (dual NIC cards) Smaller form factor Dispatch assistant window Knowledge transfer Improved telephony capabilities Integrated Instant Recall Recorder (IRR) Columbia County may elect to implement the MCC7500EE at no additional cost should this product delivery be acceptable to your implementation schedule. Additionally, Motorola has included the CSSI option for the County s consideration if you elect to entertain an alternative dispatch solution. We have included a technical overview of CSSI functionality as well as optional pricing for a Zetron dispatch solution in the cost proposal. ISSI 8000 The proposed ASTRO25 radio system includes all the hardware and software needed for a P25 Inter Subsystem Interface (P25 ISSI). We are including the cost for three (3) systems with a minimum of twenty (20) talkgroups for each system. 800 MHz Analog Simulcast Mutual Aid Radio Repeaters We propose analog 800 MHz Mutual Aid interoperability repeaters, which will consist of the 8CALL92, 8TAC93 and 8TAC94. These repeaters will interface with the proposed MCC 7500E dispatch console through a CCGW and will provide the capability for dispatchers to monitor the channels and enable/disable the repeat function. These repeaters will be use a common receive and transmit antenna with the main 700 MHz trunked channels by separate transmit combiner and diplexer. NICE Inform logging Integration (Option) We propose to the County a new logging recorder (optional) for the trunked ASTRO25 radio system. This design includes an optional NICE Logging Recorder, Playback workstation and Archiving Interface Server at the Columbia County EOC PSAP. NICE is one of Motorola Solutions premier partners that provide a certified logging solution superior to non-certified solutions in many ways. Some of the key differentiators are: Supported by Motorola Solutions System Support Center Monitored by the ASTRO25 Unified Event Manager Fully featured solution tightly integrated with the ASTRO25 radio system Certified in Motorola Solutions SIT lab to reside on the Radio Network (RNI) Ongoing collaborative partnership between NICE and Motorola Solutions to test and verify that the software of both platforms is fully compatible in every system release Logging recorders not certified by Motorola Solutions do not provide these benefits, which can lead to degraded performance of the logging recorder; longer response times for repairs and adds 4-6 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 201

117 uncertainty during system upgrades. The optional NICE logging recorder is certified for integration with an ASTRO25 radio system. APX 7500 Consolettes Motorola Solutions is proposing nine (9) APX 7500 consolettes for use on the proposed ASTRO25 radio system. These consolettes are intended for use at the Columbia County EOC Dispatch for backup control stations and will be interfaced to the proposed MCC 7500E dispatch console through CCGWs and rack mounted with the console network equipment. Each consolette will provide talkgroup selection either through Tone Remote Control or v.24 digital. 5 site 700 MHz simulcast cell We have proposed a 5-site 700 MHz simulcast configuration as required by the RFP. The Service Area Reliability tables within the coverage section detail the guaranteed reliability for the Modified Columbia County area for a portable radio outside on the street and the attenuation for 6dB loss buildings for both FDMA and TDMA modulations as well as mobile radios. 6 site 700 MHz simulcast cell (Optional) We have proposed an optional 6-site 700 MHz simulcast configuration as required by the RFP. The Service Area Reliability tables within the coverage section detail the guaranteed reliability for the Modified Columbia County area for a portable radio outside on the street and the attenuation for 6dB loss buildings for both FDMA and TDMA modulation as well as mobile radios. p. 202 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-7

118 This page intentionally left blank. 4-8 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 203

119 4.1 SOLUTION OVERVIEW Columbia County, Florida Motorola Solutions, Inc. is pleased to propose our advanced ASTRO 25 portfolio of radio solutions for the next generation radio network system for Columbia County (County). ASTRO25 is the most widely deployed Project 25 (P25), mission-critical, integrated voice and data (IV&D) network for public safety agencies, with proven high availability features in a scalable platform that combines uncompromising, real-world performance and the legendary reliability of Motorola Solutions. ASTRO25 networks provide a fully open P25 standards-based framework for maximum interoperation of P25 networks and P25 subscriber equipment. We have consistently championed and promoted the P25 standardization effort, with a substantial list of successful multi-vendor subscriber and console deployments, an industry-leading number of deployed P25 inter-system links and extensive technical contributions to the P25 and TIA standards forums. Our primary offering is a five-site, five-channel simulcast P25 standards-based Phase 2 TDMA digital trunked radio system. Furthermore, the proposed system will utilize five of 700 MHz channels, provided by the County, from the frequencies allotted to it by the Region 9 Planning. Columbia County PSAP will house the master site (zone core) and the County dispatch site. We are the recognized industry leader in linear simulcast modulation (LSM) technology and simulcast phasing design, with the most successful deployments (100+). We have leveraged engineering advances in our base station equipment and developed the P25 compatible simulcast technology, called LSM, which enables IP simulcast system deployment with greater site spacing, without sacrificing coverage or capability. To preserve wide area trunking communications, even in the event of the failure of major hardware components, the system design includes a geographically redundant (geo-redundant) master site called Dynamic System Resilience (DSR). The DSR master is proposed to be located at the CCSO radio site. The radio system includes a geographically geo-redundant simulcast Prime site to preserve simulcast radio system operation even in the event of a complete failure of a simulcast prime site. The simulcast prime sites are configured to provide redundancy to key equipment components, such as prime controllers, prime LAN switches, prime gateways, remote site gateways and remote site backhaul switches. These redundant components have been distributed within the Prime sites in order to eliminate single points of failure, which could result in a loss of simulcast operation to the radio system. One of these prime sites will be co-located with the DSR master site at the CCSO radio site and the other proposed location is the EOC PSAP site. The RF sites consist of base radios, IP networking and antenna networks and are controlled/linked by the simulcast prime and master network control sites. The sites are synchronized by a Global Positioning System (GPS) time and frequency reference in order to keep the network timing synchronized. To preserve remote RF site operation, even in the event of the failure of major hardware components, each RF site has been configured to provide redundancy to key equipment components. These key equipment components, such as GPB 8000 Reference Distribution Modules (RDM), X-HUB remote site LAN, remote site gateways (site routers), GPS and antenna systems, will eliminate single points of failure, which could result in the complete loss of the site. The proposed offering also includes an MCC 7500E IP-based radio dispatch console. This dispatch console will have nine positions, located at the existing Columbia County EOC PSAP. To preserve console site operation, even in the event of the failure of major hardware components, the console sites configuration provides redundancy to key equipment components, such as console site LAN p. 204 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-9

120 switches and console site gateways. This will eliminate single points of failure, which could result in a loss of console site operation on the system. To allow capability to configure system parameters, monitor system activity and generate system reports and to monitor all critical systems and site status alarms, Network Management (NM) client workstations have been included in the proposed system. One of these will be located at the Columbia County EOC in the system manager s office. The other NM client terminal will be located in the EOC. Each NM terminal is a Windows 10 PC with 22 touch screen monitor. A licensed 6GHz Ethernet microwave backhaul provides all site connectivity, which will provide an Ethernet transport for all dispatch and radio infrastructure sites. The microwave network is configured in loop configuration to preserve connectivity and avoid any single point of failure. This will eliminate single points of failure, which could result in a loss of connectivity between the remote RF and console sites and the control sites Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 205

121 4.2 SYSTEM DESCRIPTION Columbia County, Florida The following paragraphs provide a list of the detailed equipment included in our proposed solution Main Master Site at Columbia County EOC Communications Room The system design for the ASTRO25 master site, referred interchangeably as the zone core, will be located at the Columbia County EOC Communications Room and will be the main control point for the operation of the radio communications system. Call processing and system management occur at the master site. The master site contains the computing backbone for the system and all the components necessary for controlling voice calls within the proposed system. The zone controller performs voice and data call processing for each zone. The zone controller(s) maintain constant communication between the RF sites, simulcast sites and NM subsystems via the network transport subsystem. In addition, the master site provides the hardware and software components used for network management and system configuration. The master site configuration provides redundancy to key zone core servers in order to eliminate single points of failure that could result in a loss of wide area trunking operation to the radio system. The following lists the major zone-level components, which will be located at the Columbia County EOC PSAP: Primary Zone Controller Core LAN Switch GGM 8000 routers Out of band management GPS sourced NTP for syncing all Ethernet-based computer systems Network database server Network Management client access terminal The master site block diagram is shown in Section 4.8 System Level Block Diagrams Dynamic System Resilient (DSR) Master Site at the Deep Creek Radio Site The system design for the DSR solution consists of a back-up master core site located at the Deep Creek radio site. Should the Columbia County PSAP main master core no longer function, the DSR will automatically take over the control of the system thus keeping the system in wide area operation and provide system management. The following lists the major zone-level components, which will be located at the Deep Creek site: Secondary Zone Controller Core LAN Switch GGM 8000 routers Out of band management GPS sourced NTP for syncing all Ethernet-based computer systems Network database server Network Management client access terminal The DSR master site block diagram is shown in Section 4.8 System Level Block Diagrams. p. 206 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-11

122 4.2.3 Simulcast Subsystem Equipment The ASTRO25 Simulcast infrastructure consists of a central simulcast prime site and distributed simulcast remote sites. The prime site acts as a control and digitized audio processing center for the simulcast subsystem. Each simulcast remote site routes audio to the prime site. To ensure that the best audio from the simulcast voting receivers is processed, a voting comparator compares and selects the best signal. The prime site contains redundant prime site simulcast controllers, GCM 8000 comparators and networking equipment to interface to the remote simulcast sites. At the prime site, the site controller manages radio traffic assignments and data communications to the remote sites. The traffic comprises integrated voice, data and control to and from the air interface and infrastructure status and provides control messaging between the comparators and the base radios. Other types of network traffic between the IP simulcast prime site and remote sites, such as conventional traffic for the MCC 7500E, are supported. Simulcast solutions extend a system s RF coverage, especially in areas where available frequencies are limited and in areas where physical barriers (e.g. mountains and buildings) can cause reduced signal coverage. We developed trunked simulcast to meet the needs of users who were outgrowing their single-site radio systems. Simulcast offers the following advantages: Improved Coverage - One radio site may not provide the coverage necessary for the application in question. Simulcast expands the coverage area by expanding the number of radio sites without adding additional frequencies. Efficient Use of Frequencies - Adding sites typically requires more frequencies. The same frequencies are used at every site in a simulcast system. This makes very efficient use of the available spectrum. Simplified Radio Operations - Because the simulcast architecture operates like a single-site system, operations are simplified and radios are easy to use. The frequency efficiency, benefits of receiver voting for inbound coverage and improved in-building and difficult terrain outbound coverage from multiple transmitter paths makes this the most common solution for urban coverage. Motorola Solutions simulcast systems exclusively use LSM to overcome the issues of delay spread and phase distortion. The use of LSM increases the resilience of the receiver to handle larger delay spreads resulting in wider site separations for 12.5 khz channel bandwidths than possible with C4FM. Geographically redundant ASTRO25 prime sites keep wide-area simulcast subsystems operating even after a catastrophic loss of one of the prime sites. If the prime site becomes unavailable, the system automatically restores wide area operation with the secondary prime site. The ASTRO25 system keeps users connected through a major catastrophe: All channels at the subsites have full functionality. Redundant systems are easy to operate: All equipment is centrally managed Simple, familiar system configuration and maintenance Multiple locations appear to the system as a single prime site We propose a geographically redundant prime site configuration for Columbia County in compliance with the RFP. The geo-redundant simulcast subsystem proposed will consist of one primary prime site located at the EOC PSAP and one backup prime site located at the CCSO radio site. Figure 4-1 shows the general architecture of a geo-redundant prime site configuration Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 207

123 Figure 4-1: Sample geographically redundant prime site configuration Simulcast Prime Equipment at the EOC Communications Room The active prime site hardware will be co-located with the Main master site at the EOC Communciations Room site. This site will host the active prime site hardware. This site will include redundant GCP 8000 prime site controllers, which will provide control of the simulcast network under normal operations. The site will also include the primary voting and LAN/WAN equipment, for the prime site. The following lists the major simulcast prime site components at this site: Two (2) redundant GCP 8000 prime site controllers Five (5) GCM 8000 ASTRO25 IP comparators One (1) prime site LAN switch One (1) TRAK 9100 GPS with full internal redundancy (shared with the master) One (1) GGM 8000 sub-site access router for link to remote sites One (1) sub-site backhaul LAN switch One (1) GGM 8000 router for link to master sites The simulcast prime equipment block diagram is shown in Section 4.8 System Level Block Diagrams Geo-Redundant Simulcast Prime Equipment at the Deep Creek Radio Site The Deep Creek site will host the backup or GEO prime site hardware. This site will also include a GCP 8000 prime site controller, which will provide control of the simulcast network under normal operations. The site will also include the backup voting and LAN/WAN equipment, for the prime site. The following lists the major simulcast prime site components at this site: One (1) GCP 8000 prime site controller. Five (5) GCM 8000 ASTRO25 IP comparators One (1) prime site LAN Switch One (1) TRAK 9100 GPS with full internal redundancy (shared with the master) One (1) GGM 8000 sub-site access router for link to remote sites One (1) sub-site backhaul LAN switch One (1) GGM 8000 router for link to master sites p. 208 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-13

124 The geo-redundant simulcast prime equipment block diagram is shown in Section 4.8 System Level Block Diagrams Simulcast Remote Site Overview Each remote RF site consists of base radios, IP networking, and antenna networks and is controlled/linked by the simulcast prime and master network control sites. GPS time and frequency reference synchronizes the sites to keep the network timing synchronized. Each RF site is configured to provide redundancy to key equipment components to preserve remote RF site operation, even in the event of the failure of major hardware components. Key components such as GPB 8000 Reference Distribution Modules (RDM), X-HUB remote site LAN, remote site gateways (site routers), GPS and antenna systems, eliminate single points of failure, which could result in the complete loss of the site. Our design includes five simulcast remote RF sites, with an option for a sixth site. The main master and prime sites will be at the same location as one of the tower sites but will be housed in the EOC with the dispatch center and connected to the local tower site via County provided fiber. One of these simulcast remote sites will be co-located with the DSR master site and the backup prime site, while the remaining sites will be standalone remote RF sites. The configuration of each site is shown in Table 4-1. Table 4-1: Simulcast remote sites No. Site Name Site Type Latitude Longitude 1 EOC Communications Main Master/Prime N W Room 2 EOC Tower Remote N W 3 Cumorah Hill Remote N W 4 Lulu Remote N W 5 CCSO Remote N W 6 Franklin Microwave Only N W 7 Deep Creek DSR Master/Prime/Co- Remote N W 8 Greenfield (Option Only) Remote N W The following major equipment is located at each of the simulcast RF sites: Two (2) redundant GPB 8000 Reference Distribution Modules Two (2) redundant X-Hub Two (2) redundant GGM 8000 sub-site gateways Five (5) GTR MHz ASTRO25 simulcast trunking repeaters One (1) 800 MA analog standalone repeater at Deep Creek, EOC & Cumorah Hill sites One (1) 4-port CCGW (12 ports for EOC tower site) One (1) NFM SDM 3000 alarm and monitoring RTU One (1) TX 700 MHz combiner One (1) Tx 800 MHz combiner at Deep Creek, EOC & Cumorah Hill One (1) receiver multi-coupler One (1) tower top amplifier One (1) receive antenna and distribution network One (1) transmit antenna and distribution network 4-14 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 209

125 RF subsystems include all applicable coax cable, hangers, cable boot, ground kits and gas tube lighting arrestors (Polyphasors). The individual RF site block diagrams are shown in Section 4.8 System Level Block Diagrams. 4.3 DISPATCH CONSOLES SUBSYSTEM IP Console Design and Dispatch Centers Motorola Solutions proposed dispatch solution for Columbia County is our MCC 7500 Enhanced (MCC 7500E) Dispatch Console, offering IP-based seamless connectivity between Columbia County dispatch operators and field personnel. The MCC 7500E Dispatch Console will provide Columbia County with scalable, flexible system architecture, sophisticated network management and security, and an easy migration to future capabilities. The MCC 7500E is an evolution of the MCC 7500 dispatch console. It is intended to better meet the needs of dispatch customers who require more highly available dispatch console systems. The MCC 7500E is based on the software-based MCC 7100 console platform with the following enhancements: Increased Availability The MCC 7500E can be used inside or outside the ASTRO Radio Network Infrastructure (RNI). Enhanced Integrated Instant Recall Recording (IRR) This enhancement creates an IRR that can be used with the MCC 7100 and the MCC 7500E consoles. Fault Tolerance This enhancement adds support for dual Network Interface Cards (NICs) on the dispatch position to address failures of LAN switches affecting multiple dispatch position Small Form Factor Dispatch Computer This enhancement adds support for a physically smaller computer to be used with MCC 7500E and the MCC 7100 consoles. The small form factor computer will be no more than 653 cubic inches in volume, which is one-third the size of an HP Z440 workstation. It will be rack mountable in a 19 EIA rack and is planned to consume no more than 1 rack unit of space. It will also support being remotely located from the dispatch position. Dispatch Assistant The Dispatch Assistant feature enables dispatchers to see information and control functionality on their MCC 7500E dispatch positions using the monitors, keyboards, and mice (or touch screens) of other computer-based systems in their dispatch centers Integration with the ASTRO 25 Network The MCC 7500E IP Dispatch Console will be seamlessly integrated into Columbia County s ASTRO 25 system, without interface boxes, digital voice gateways, or backroom electronics, for an integrated mission critical network. This tight union between radio infrastructure and dispatch console equipment has several operational benefits. An MCC 7500E system diagram is shown in Figure 4-2. p. 210 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-15

126 Figure 4-2: Radio System Infrastructure with Motorola Solutions MCC 7500E consoles City of Columbia County Dispatch Systems The proposed solution offers Columbia County nine (9) MCC 7500E Enhanced Dispatch Consoles. Table 5-2 outlines the number of consoles and their location. Number of Operator Positions Table 5-2: Dispatch Locations Location 9 Columbia County EOC PSAP 9 Laptops for Remote Dispatch Columbia County EOC PSAP Dispatch Networking Equipment Two (2) Site Gateways. Two (2) 24-port LAN Switches. Nine (9) MCC 7500E Dispatch Consoles, each including: One (1) MCC 7500E Certified MINI Workstation with mouse and keyboard. One (1) 24 inch Dell P2414H Monitor. Two (2) Desktop Speakers (Select and Unselect Audio). One (1) Dual Pedal Footswitch. One (1) Gooseneck Microphone. Two (2) Headset Jacks. One (1) Dual Instant Recall Recorder (IRR) with speakers Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 211

127 Additional Dispatch Equipment One (1) Conventional Site Controller. Three (3) Conventional Channel Gateway (CCGW). One (1) Aux I/O SDM MCC 7500E Enhanced Dispatch Experience The MCC 7500E Dispatch Console offers Columbia County state-of-the-art communications, console management, and configuration functionality, as well as dispatch operation and communications security. The proposed system also offers Columbia County the capability to maintain both audio and data recording of calls made on the communications system. Network Connectivity Details on the connectivity between the MCC 7500E dispatch console and the ASTRO 25 system are described below. The IP network equipment below is used to route audio and control signals between the dispatch operators and the P25 trunked system. Redundant switches and gateway will negate a single point of failure within the common electronics equipment category. The MCC 7500E console site(s) for Columbia County is remote from the core site and is provided with redundant site links to provide path diversity. The console site has two logical connections to the core site, with each connection using a different core router. Each console site gateway provides an interface that handles all of the IP Network Management traffic between the MCC 7500E console center and Columbia County s ASTRO 25 system core site. The site gateways fragment large IP packets according to industry standards, prioritize packets, and convert Ethernet data to the desired transport medium. The site LAN switches provide LAN interfaces for dispatch site equipment and a LAN port for the link to the core site. The MCC 7500E console also supports the use of dual network connections on dispatch positions to prevent a console site LAN switch failure from rendering a dispatch position unusable. Console Configurations Management The MCC 7500E console system is configured and managed by the same configuration manager, fault manager, and performance reporting applications as the radio system. The user can define exactly which resources are available and how they are presented to the dispatch console user. This provides Columbia County with a single point for configuring and managing the entire ASTRO 25 system. Changes are automatically distributed throughout the system. This centralized approach saves valuable time and effort for system administrators and technicians and reduces the errors that can occur when radio IDs and other data are entered at multiple locations. In addition, call traffic and performance reports for each console can be generated from the system s network manager. This enables administrators to quickly and easily ensure optimal effectiveness and efficiency. Agency Partitioning With Agency Partitioning, City and County agencies will gain the interoperability benefits of being on the same system, be able to leverage cost savings in the maintenance of a shared system, and still maintain control of their own console configurations, channels, and encryption keys when applicable. p. 212 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-17

128 The Agency Partitioning feature enables Columbia County system administrators to control who has access to functionality for the console network as a whole. It controls access for conventional RF channels, trunking talkgroups, auxiliary I/Os, pre-programmed pages, encryption keys, and configuration data. Agency Partitioning helps keep an agency's resources available for its users, while preventing unauthorized people from accessing or modifying the network configuration. Dispatch Interface The MCC 7500E Elite Dispatch GUI is an enhanced version of Motorola Solutions Gold Elite Dispatch GUI. For existing Gold Elite users, the GUI allows a smooth transition and minimal training for radio dispatch operators. For new users, the graphical icons and customization options make the MCC 7500E console GUI easy to learn and operate. The versatile MCC 7500E Dispatch Interface also supports many methods for operators to perform dispatch functions, including touch screen operation. An example of the MCC 7500E GUI in shown in Figure 4-3. Figure 4-3: The MCC 7000e series GUI delivers critical real-time information to the console operator when and where they need it. The MCC 7500E GUI allows for unlimited screen layouts. Based on operator preference, the MCC 7500E GUI can be customized to show details of trunked and conventional RF channels on a perchannel basis. Customization capabilities include background colors of resources, buttons and folders, the sizes and positions of resources, the fonts, sizes and colors of text, the number of folders and the icons used on the buttons and indicators. Various controls can be highlighted, such as patch status, frequency select, coded/clear select, and individual volume control. Per-channel controls can be fully or partially shown, or hidden to save space on the screen. Busy dispatch operators can respond to a missed call by simply clicking on an entry in the Activity Log. The number of calls and call information displayed in the Activity Log is customizable to suit the needs of the user. The status of 4-18 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 213

129 auxiliary inputs and outputs can be conveniently interpreted from the GUI with the use of familiar graphical icons, such as a door shown open or closed. Auxiliary Inputs/Outputs Dispatch Consoles support Global Auxiliary Inputs/Outputs (Aux I/Os) for remote status indications or remote control through dispatch consoles. Global Aux I/Os are typically implemented by hardware that is independent of the dispatch console positions in a system and may be accessible to multiple dispatch consoles. For dispatch consoles, Aux I/O functionality and support is provided by: Configuration of dispatch console Aux I/O parameters through network managers. Dispatch console display of status inputs/control outputs. The Aux I/O Servers are used to provide the Aux I/O feature for the dispatch consoles. The consoles communicate to the Servers to perform the Aux I/O function. Emergency Radio Transmission and Reception As part of a mission-critical communications network, the MCC 7500E console facilitates immediate prioritization and resolution of emergency communications between Columbia County dispatch and first responders in the field. This enables dispatch operators and first responders to focus on their mission, not their equipment especially during critical situations. When a field user or another dispatch operator initiates an emergency call, the console emits both visual and audible indications ( Emergency Alarm ). The operator can then recognize the emergency call, which ends the audible emergency indication and notifies all console operators that the emergency is being addressed ( Emergency Recognize ). The audible emergency indication may also be muted by a console operator without recognizing the emergency alarm ( Mute Tones at a Single Op ). When an emergency is over, the dispatch console user can end the Emergency Alarm. The emergency mode remains active on the initiating radio unit until it is ended (reset) by the radio user. Multi-Select Control 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. Resources can be added or removed from a Multi-Select group while it is open or while it is closed. The dispatcher can transmit on several resources simultaneously or can listen to multiple resources simultaneously in their headset or select speakers. Channel Marker The MCC 7500E is capable of transmitting a channel marker tone to be used as needed by Columbia County for priority transmissions and situations. Radio Patch Control MCC 7500E console users can patch communication between trunked and/or conventional radios that are normally unable to communicate with each other due to different features, programming, or even different frequency bands. A patch group is a group of linked resources that can both receive messages from a console and transmit to all other members of the patch group. The MCC 7500E supports a maximum of 16 active patch groups per dispatch position. p. 214 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-19

130 Automatic Prioritization of Calls Calls on the MCC 7500E console are prioritized through a transmission hierarchy. Calls from primary supervisors take priority over those from secondary supervisors, which take priority over nonsupervisors. Instant Transmit or All-Points Bulletin (APB) transmissions, regardless of whether they are from a supervisor, will take priority over general or patch transmissions. Multiple dispatch console operators can be designated as primary supervisors on the same system, which is useful when multiple agencies share one system, each with their own primary supervisor. With the Network Manager Client installed, console supervisors can disable and enable operator console functionality as necessary. Manual Prioritization of Calls System Access Priority Select allows a dispatch operator to prioritize trunked resources on the system as either normal or tactical. A dispatch operator can change the priority of a trunked resource to tactical in order to give the resource a better chance of gaining communication access on a busy system. Only emergency calls have a higher priority than tactical. When the System Access Priority status of a resource is changed, it is updated at all dispatch consoles in the systems that are monitoring that trunked resource. Dispatch Assistant The Dispatch Assistant feature enables dispatchers to see information and control functionality on their MCC 7500E dispatch positions using the monitors, keyboards, and mice (or touch screens) of other computer-based systems in their dispatch centers. Dispatchers can respond to calls, incidents, and events without having to divert their attention to the dispatch position s monitor or take their hands off of whatever keyboard and mouse they might be using. Small browser-based windows containing various types of resources and/or console features can be placed next to the GUIs of CAD systems, mapping applications, fire station alerting systems, 911 systems, etc. The browser windows provide great flexibility in where they can be placed. Each dispatcher can utilize custom arrangements to suit their individual needs and preferences. A dispatch position supports the following browser window placements: One or more browser windows can be placed on a single monitor connected to a single computer. Multiple browser windows can be placed on multiple monitors connected to a single computer. Multiple browser windows can be placed on monitors connected to multiple computers. Alert Tones The MCC 7500E is capable of sending up to 100 distinct alert tones that can be used to indicate levels of priority. Interoperability Options ASTRO 25 is specifically designed around APCO P25 standards. All voice messages are digitized, all Land Mobile Radio (LMR) system features are compliant with P25 standards, with many features exceeding the P25 standards, and the system uses the P25-defined, 9600-bps control channel format for all control channel commands. As part of ongoing enhancements to this solution, Motorola Solutions has joined and actively participated in the P25 interoperability committee to ensure continuously improving interoperability with the radios of other P25 vendors. ASTRO 25 is also fully Common Air Interface (CAI) compliant Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 215

131 As shown in Figure 4-4, interoperable communications can be provided through a dispatcher-initiated interface (patch) to the Mutual Aid radios and TACN channels. The Motorola Solutions Conventional Channel Gateway (CCGW) forms the bridge between the MCC 7500E dispatch console on the ASTRO 25 radio network and Columbia County radio resources. This allows the dispatcher to patch together Mutual Aid radios and required subscribers on the ASTRO 25 system, as situations dictate. Figure 4-4: Mutual Aid Components Conventional Channel Gateway Enhanced Conventional Channel Gateways (Enhanced CCGWs) are used to interface analog and ASTRO 25 conventional channels to the ASTRO 25 radio system infrastructure. Enhanced CCGWs provide 4-wire analog interfaces for analog channels and V.24 and IP digital interfaces for ASTRO 25 conventional channels. The platform that is hosting an enhanced CCGW may be solely dedicated to that task, or it may also be used as a console site router or an RF site router, provided the WAN link is not redundant. The enhanced CCGW provides two sets of ports that are used with analog channels. One set (called the Analog Ports) contains the analog inputs and outputs for the channels along with a COR/Coded/Clear input and a PTT Relay output. The other set (called the Supplemental I/O Ports) contain analog logging recorder outputs and various inputs that can be used with the analog channel. One (1) HD CCGW with 8 ports will be provided for each dispatch center to allow for mutual aid and TACN integrations with customer control stations. Conventional Site Controller (CSC) The GCP 8000 conventional site controller allows dispatch console users to continue to access and control local conventional channels if connectivity to the radio system s controller is lost. This mode of operation is often called fallback operation or site conventional operation. One CSC is provided for each dispatch center. Only one conventional site controller is required per console site or conventional subsystem. This single conventional site controller is capable of supporting the full set of dispatch consoles, archiving interface servers and CCGWs that can be placed in a console site or conventional subsystem. p. 216 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-21

132 The console site block diagram is shown in Section 4.8 System Level Block Diagrams MCC 7100 Dispatch Console The Motorola Solutions MCC 7100 Dispatch Console is a software based wireline console for use on Motorola Solutions ASTRO25 systems. It offers scalable capacity and flexible deployment options and is a software-based dispatch console that requires no external hardware connections (no VPM or GPIOM) to perform dispatch operations. Audio Vocoding is performed within the Windows operating system. The MCC 7100 Dispatch Console allows the flexibility to be deployed at a console site within the ASTRO25 radio network or outside of the ASTRO25 network. The MCC 7100 Dispatch Console includes the features expected in a high tier Console including Emergency and Console Priority and offers a choice of Motorola Solutions or COTS accessories. The MCC 7100 Dispatch Console supports: ASTRO25 Trunking (Phase 1 & Phase 2) ASTRO25 Digital Conventional (P25) Analog & MDC 1200 Analog Conventional Mixed Mode Analog / Digital Conventional The MCC 7100 console is proposed to be utilized in the Columbia County Emergency Command Post vehicle, with wireless connectivity back to the ASTRO25 network per the requirements of the RFP. The MCC 7100 software application will be installed on a laptop and will connect back to the Radio Network through public or private 4G/LTE and WiFi service provided by Columbia County. Since the MCC 7100 includes access to the same conventional radio resources as the MCC 7500E, the MCC 7100 will also be able to provide remote access to the paging system. The MCC 7100 components included in the proposal are: Nine (9) laptop computers: One (1) pair external USB speakers One (1) USB headset One (1) PRX 7000 Proxy server installed at the Columbia County PSAP One (1) Fortinet Firewall installed at the Columbia County PSAP MCC 7100 software including up to twenty trunking channels and secure operation APX 7500 Consolettes Motorola Solutions APX 7500 Consolettes provide the features of the APX 7500 mobile in a housing with built in power supply (Figure 4-5). They are ideal for local law enforcement, utility and transportation users who need a low cost desktop-based control station or wireless dispatch solution. These control stations can also be used as emergency backup stations, a low-cost dispatch center for local agencies and as a fire station alerting system. They are offered in both local and digital remote control configurations Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 217

133 Figure 4-5: APX 7500 control station This proposal includes nine APX 7500 consolettes. All of these consolettes are intended for use at the Columbia County EOC PSAP. The consolettes at the EOC will interface to the proposed MCC 7500E dispatch console through CCGW Logging Recorder (Option) In order to support the County s requirements to record trunking radio system traffic, one Archiving Interface Server (AIS) is included to interface with the proposed certified NICE logging recorder. Motorola Solutions certified logging recorder solutions are superior to non-certified solutions in many ways. Some of the key differentiators of a Motorola Solutions certified logging recorder solution are: Supported by Motorola Solutions System Support Center Monitored by the ASTRO25 Unified Event Manager Fully featured solution tightly integrated with the ASTRO25 radio system Certified in Motorola Solutions SIT lab to reside on the Radio Network Infrastructure (RNI) Ongoing collaborative partnership between NICE and Motorola Solutions to test and verify that the software of both platforms is fully compatible in every system release Logging recorders that are not certified by Motorola Solutions do not provide these benefits, which can lead to degraded performance of the logging recorder; longer response times for repairs and adds uncertainty during system upgrades. The proposed NICE logging recorder has been certified for integration with an ASTRO25 radio system ISSI/CSSI 8000 Gateway System The ISSI 8000 solution is an Interoperability Solution that enables an ASTRO25 system to connect to other P25 systems regardless of their RF bands, manufacturer type and release versions. ISSI 8000 is built to the TIA 102 suite of standards used for the design of Project 25 interoperable communication products. The ISSI 8000 provides customers more interoperability choices and allows them more features (automatic seamless roaming, PTT ID, P25 TDMA support) ISSI 8000 can save capital expenses by leveraging the infrastructure of neighboring P25 systems to extend the range of their network without investing in additional RF sites and their associated costs. Thus, users can maintain communication with their home system when they roam beyond it: e.g., inter-agency task forces, car chases into a neighboring system. ISSI 8000 is useful for the Deploy and Assist Scenario, where a user from one system can roam onto a foreign system to help users in that system with specific tasks and establish communication with the foreign system: e.g., inter-agency task forces, disaster recovery, car chases into a neighboring system. ISSI 8000 is useful for Coordinated Incident Management, where users in separate systems responding to a region-wide event can communicate with each other while remaining in their own systems: e.g., inter-agency task forces, disaster recovery. p. 218 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-23

134 As required in the RFP Motorola Solutions is proposing an Inter RF Subsystem Interface (ISSI) connection on the ASTRO25 radio system, which Columbia County has indicated they would like to utilize to connect into neighboring radio systems such as Lowndes County, GA, Alachua County, FL and the State of Florida. The proposed ASTRO25 Core includes all of the hardware necessary to provide up to one ISSI connection to the radio system, which will minimize the investment required by Columbia County to realize this capability. Motorola Solutions has included cost on a per link basis for the software licensing needed to make a connection to a foreign radio system with 20 roaming talkgroups. It is Columbia County s responsibility to obtain any necessary agreements with the other radio system owners with whom an ISSI connection is desired Project 25 ISSI Trunking Interface Motorola Solutions has demonstrated its leadership in the P25 ISSI community by being the first manufacturer to announce shipping a product that supports the P25 ISSI. Motorola Solutions has also participated in multi vendor ISSI demonstrations at IWCE (2007) and APCO (2008 and 2009) and hosted the first P25 ISSI Interoperability Event in February The ISSI.1 Network Gateway is Motorola Solutions first P25 ISSI solution and has been shipping since December Motorola Solutions current Generation Interoperability solution is the ISSI This is a software application that resides on an Interoperability System Gateway Server (ISGW). The ISSI 8000 solution is an interoperability solution that enables an ASTRO25 system release 7.13 or higher to connect to other P25 systems regardless of their RF bands, manufacturer type and release versions. The ISSI 8000 is built to the TIA-102 suite of standards used for the design of Project 25 interoperable communication products. The ISSI 8000 provides customers more interoperability choices and allows them more features (automatic seamless roaming, PTT ID, P25 TDMA support) than the original ISSI.1 solution. Below is a list of features that define what Project 25 ISSI Trunking features Motorola Solutions supports in the ISSI.1 and ISSI 8000 product offerings (Table 4-3). Table 4-3: Project 25 ISSI Trunking Features Offered by Motorola Solutions P25 ISSI Trunking Feature Name Offered by Motorola Solutions ISSI.1 Voice & Mobility Features Voice Features Offered by Motorola Solutions ISSI 8000 TIA 102 Standards Document Broadcast Call No Yes TIA 102.BACA A Announcement Group Call No Yes TIA 102.BACA A Confirmed Group Voice Service No Yes TIA 102.BACA A Unconfirmed Group Voice Service Yes Yes Note 1 TIA 102.BACA A Emergency Group Call Yes Yes TIA 102.BACA A Encrypted Voice (AES) Yes Yes TIA 102.BACA A P25 Full rate vocoder (FDMA) Yes Yes TIA 102.BACA A P25 Half rate vocoder (TDMA) No Yes Future SU and Group Mobility Management SU Registration No Yes TIA 102.BACA A 4-24 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 219

135 P25 ISSI Trunking Feature Name Offered by Motorola Solutions ISSI.1 Offered by Motorola Solutions ISSI 8000 TIA 102 Standards Document Transport of Authentication Credential No Yes TIA 102.BACA A Secure SU registration (SU authentication) No Yes TIA 102.BACA A SU Deregistration No Yes TIA 102.BACA A Group Affiliation Yes Yes TIA 102.BACA A Call Restriction No Yes TIA 102.BACA A Roaming Inter WACN (manual) Yes Yes TIA 102.BACA A Inter WACN (automatic) No Yes TIA 102.BACA A Inter System (manual) Yes Yes TIA 102.BACA A Inter System (automatic) No Yes TIA 102.BACA A Intra System (automatic) No Yes TIA 102.BACA A RFSS Service Capability Polling Yes Yes TIA 102.BACA A 2 Supplementary Services Features Transport of Talking Party Identity No Yes TIA 102.BACA A Priority Call No Yes TIA 102.BACA A Emergency Alarm No Yes TIA 102.BACD B Emergency Alarm Cancellation No Yes TIA 102.BACD B Group Emergency Cancellation No Yes TIA 102.BACD B NOTES Note 1: Motorola Solutions ISSI 8000 support unconfirmed group call only as a serving system When used between Motorola Solutions systems, ISSI 8000 also provides a richer set of features than the suite of features included in the P25 standard. These features, described in Table 4-4, enhance the user roaming experience, provide greater emergency management functionality and provide more granular system management features. Features Motorola Solutions System Manager Control Yes Table 4-4: ISSI 8000 Features Functionality Enables system managers to create a site access profile for not just the home talkgroups on a system, but also the foreign talkgroups foreign users may roam on. System Managers can set talkgroup site access profiles that help them control roaming options on their own system. p. 220 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-25

136 Features Motorola Solutions Functionality Faster Auto Roaming Yes Allows control channel information from neighboring sites to be added into the base stations located at fringe sites. Radio users in these sites that have the latest roaming software in their subscribers will know the control channel information of neighboring systems when they roam outside of the system. Additionally, ISSI 8000 capable P25 radio users can roam automatically and switch between enabled P25 systems faster (< 5 seconds) thus reducing the potential for missed calls or joining a call late. PTT ID and Alias Information Sharing Yes Provides the ability for Alias information to appear on the visited system and the home system while it is maintained only in the home system. Customers don t have to maintain multiple databases for displaying aliases. Fast Start / All Start Yes System managers have the flexibility to decide what sites/consoles are deemed critical for a call and if a call should start without them if that site is busy. Busy Queuing w/ Call Back Yes With Busy queuing, a call over the ISSI 8000 link gets queued and the user is alerted with an audible tone once all required sites/consoles are available. DSR Configuration Yes ISSI 8000 gateways enjoy the same geographic redundancy provided by Motorola Solutions Dynamic System resiliency as other master site equipment. The ISSI link will function reliably from either core. P25 TDMA Yes The ISSI 8000 gateway will allow TDMA talkgroups to interface with foreign systems Project 25 CSSI 8000 Console Interface CSSI 8000 provides an interconnection to a third-party console subsystem and complies with P25 TIA 102.BACA for voice interoperability and TIA 102.BACD for supplementary data interoperability (i.e., emergency alarm, emergency cancel, and call alert). CSSI 8000 uses the same instance of the ISSI 8000 Gateway server hardware and application, but provides different capabilities. CSSI 8000 provides ASTRO25 conventional system interaction to foreign P25 systems, third-party console subsystems, and other ISSI standard-compliant radio systems using conventional talkgroups. This expands conventional talkgroup operation across systems. CSSI 8000 uses the ISSI 8000 Gateway within the master site to connect through the InterSystem Firewall to a third-party console subsystem. The ASTRO 25 system only supports one set of redundant ISSI 8000 Gateways. All the operator positions in the third party console subsystem must connect to the ASTRO25 system through a single interface, or a single redundant link Integrated Voice and Data Capabilities Integrated Voice and Data (IV&D) is Motorola Solutions integrated mobile data and is supported on the ASTRO25 trunking system. Motorola Solutions ASTRO25 IV&D capability enhances the ASTRO25 system by adding packet data capability to subscriber units. This system enhancement will provide voice and data communications throughout the service area, without the extra expense of 4-26 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 221

137 installing and maintaining separate systems for voice and data. All new Motorola Solutions ASTRO25 systems include Integrated Voice and Data. There are four main components required to equip the system with IV&D. They are a GGSN (Gateway GPRS Support Node) router, a firewall, a PDG (Packed Data Gateway) and system software. These have all been included in the proposed radio system. ASTRO25 IV&D uses the same infrastructure components needed for P25 voice communications. The simulcast and repeater sites that form the backbone of the County communications network will support both voice and data communications. This will allow the system to allocate resources to voice and data communications, depending on user demands. Allowing sites to exchange both voice and data information ensures that system resources are used as efficiently as possible. This capability also minimizes the number of separate components that the system will be required to support Applications Utilizing the IV&D System Enhancement Intelligent Middleware (IMW) Intelligent Middleware (IMW) is the Motorola Solutions software platform that provides common services, such as Presence and Location for multiple Motorola Solutions networks. IMW replaces the Unified Network Services (UNS) application in the ASTRO25 IV&D system and supports data applications such as Outdoor Location Solution, Over the Air Programming (POP25), Over the Air Rekeying (OTAR) and the Advanced Messaging Solution (AMS). IMW provides standard web based APIs for mapping tools and applications that utilize Presence and Location and allow application development to be more efficient. IMW Location and Presence APIs are available to third party application developers in order to support customers with an end to end Location and/or Presence Solution. GPS Location The Responder Location Feature allows the location of subscriber radios via the ASTRO25 infrastructure. This capability allows dispatchers and supervisors to monitor the location of personnel who are using ASTRO subscribers. The location update rate is configured on a per Unit Status basis allowing specific location cadences for statuses such as Emergency, In-Route, etc. Location on Push to Talk is also available with the with the latest ASTRO25 release proposed. Location services are enabled on a per subscriber basis allowing agencies to limit its use to portable radios or other specific groups. The Location feature requires a third party mapping program to be integrated into the system. Over the Air Rekeying (OTAR) Optional OTAR of AES encryption keys requires the ASTRO25 integrated data functionality on the trunked infrastructure. Secure users operating on the proposed ASTRO25 trunked system via IV&D and OTAR are able to deliver new AES encryption keys over the RF channel instead of manually rekeying through a Key Loader. As it is generally recommended to perform periodic updates to the encryption keys for security reasons, this option works well for large numbers of encrypted subscribers that require updated keys. OTAR is compatible with subscriber radios equipped with the AES OTAR option. POP25 The proposed ASTRO25 radio system can be outfitted with the capability to provide the County with the functional and cost benefits of Motorola Solutions Programming Over Project 25 (POP25) over the air programming (OTAP) technology. POP25 functionality reduces the time, effort and costs needed to update radio functionality by allowing radios configuration to be accessed and updated p. 222 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-27

138 over the air. POP25 is an application enabled by the ASTRO25 integrated data pipe. POP25 allows 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 ASTRO25 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 ASTRO25 trunked data system. Advanced Messaging Service (AMS) Optional The ASTRO25 Advanced Messaging Solution is the latest messaging platform from Motorola Solutions and replaces the ASTRO25 Text Messaging Service (TMS). The application allows responders to send/receive messages to/from dispatch using their ASTRO25 data enabled portable radios. Core Messaging high level capabilities include the ability to create, address, send, receive and replay to text messages: To/From data enabled ASTRO25 radios To/From Dispatch equipped with a Smart Client to data enabled ASTRO25 radios To/From Dispatch (Smart Client) to Dispatch (Smart Client) Encryption Capabilities- Optional Encryption is configured on radio systems for those critical times when unauthorized parties should not monitor communications. Encryption ensures only authorized units in the system can listen to transmissions being made. Encrypted calls are protected end-to-end throughout the network. Encryption and decryption services are provided by the system s secure endpoints: consoles, logging interfaces and field radio units. Communications remains completely secure between the source and the destination. No decoding of information occurs at any other intermediate point along the communications path, ensuring a much higher level of security. Encryption keys are distributed to consoles and subscribers and that is the only place the audio is decrypted. Figure 4-6: End-to-End Encryption Concept on ASTRO25 Radio System To increase the effectiveness of encryption, Columbia County users have the ability to be able to update encryption keys while radios and their users can stay in the field. Motorola Solutions Over 4-28 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 223

139 the Air Rekeying (OTAR) option offers the County s users the benefit of real time, ongoing security for deployed APX subscribers. OTAR will require the Infrastructure to be configured for IV&D as previously described. To enable OTAR operation, a Key Management Facility (KMF) must be added to the system. The KMF is a computer system that securely houses the encryption keys for all subscribers in the system. The KMF server will connect to the infrastructure via a firewall. System managers load the appropriate encryption leys in the KMF and enter instructions to remotely re key radios via the IV&D data link. A KMF server is not required to enable secure operation. Digital operation in general offers some level of security to system users. However, the proposed ASTRO25 simulcast system can support several standards-based algorithms such as DES-OFB and AES. The proposed equipment is capable of AES encryption, as required in the RFP. Encryption keys can be changed routinely to keep communications secure. System managers can insert encryption keys in each radio with a local cable connection and handheld key loader (KVL 4000). Motorola Solutions has supplied two of the KVL4000s to key the subscribers that have the encryption option Encryption Types - Option Project 25 Encryption Algorithms ASTRO systems can be equipped with current Project 25 algorithms and are fully compliant with all Federal Information Processing Standards (FIPS). The following encryption is available: DES-OFB, DVI-XL, DVP-XL, DES-XL, AES and ADP. As required by the RFP the proposed Motorola Solutions radio system infrastructure and dispatch consoles include the capability of end-to-end encryption using the P25 standard AES encryption algorithm. Software-Based Encryption Algorithms Advanced Digital Privacy (ADP) is an entry-level encryption algorithm, offered exclusively by Motorola Solutions. ADP allows users to protect all communications from eavesdroppers and scanners for less cost than the hardware-based encryption algorithms Rekeying Methods - Optional KVL 4000 Key Variable Loader The KVL 4000 is our encryption Key Variable Loader for secure enabled Motorola Solutions products. Equipped with the Motorola Solutions MC55 handheld, the key has state-of-the-art features and user interface for increased efficiency and programming flexibility. A large LCD color display, paired with an easy-to-use alphanumeric keypad, enables simple viewing and data entry. Built with legendary Motorola Solutions quality and security, the KVL 4000 can withstand everyday use in federal and public safety environments. The KVL4000 utilizes the Motorola Solutions MC55 handheld computer with a large 3.5-inch color display, touch screen interface and QWERTY keyboard. The device can withstand everyday use in federal and public safety environments. Features of the KVL 4000 are outlined in Table 4-5. Figure 4-7: KVL 4000 The KVL 4000 provides the capability to load, manually, encryption keys into the subscriber radios and consoles or can be used in conjunction with the KMF to perform Store and Forward operations. p. 224 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-29

140 The KVL is capable of transferring the rekey messages originated within the KMF server database to a radio or infrastructure device. Each unit s response is securely stored inside the KVL and then forwarded directly back to the KMF. The KMF user interface shows an operator which units successfully acknowledged the re-key message for easy key management. Motorola Solutions has included the pricing for the optional KMF OTAR server. Feature Automatic key generation Enhanced security Dead battery operation Key Management Facility support Table 4-5: KVL 4000 Features Description Automatically generates random keys for any algorithm. Can auto-generate a single key or a bulk set of keys. FIPS Level 3 provides the highest level of security for your data. User timeout automatically logs out the user after a specified period of inactivity. User and administrator authentication allows users and administrators to perform and restrict firmware upgrades, changes and key management. Ability to operate the KVL, including key management and key downloading while charging. With store and forward capability, the encryption keys are downloaded from the KMF, stored in the KVL and delivered to the end units. Key Management Facility - Optional OTAR The Key Management Facility (KMF) is a Project 25-compliant mission critical solution that can facilitate secure key management and distribution and is the essential key management controller for Motorola Solutions P25 Over-The-Air Rekeying (OTAR) feature. Utilizing the KMF, information can be easily created, inventoried, archived and distributed to end-users. Combining centralized key management with our standards-based OTAR capability enables effective planning, implementation and execution of robust security procedures. OTAR keys over the air without physically touching the radio. OTAR is designed to work on the IV&D transport layer. Distributing unique keys to designated user(s) configures encryption. OTAR eliminates the burden of manually rekeying your radios on a regular basis. It enables key distribution and key management to be conducted securely over-the-air. Feature Over the Air Rekeying Automated Rekey Retries Device and Group Key Currency Store and Forward Remote Inhibit/Enable Table 4-6: KMF Features Description Eliminate the burden of manually rekeying devices with secure over the air distribution and management of keys When radios are out of range or powered down automated rekey retries via KMF will update units automatically when they are back on the system Quickly find devices that are not up-to date ensuring all devices have latest encryption keys and parameters Reach units out of range with key variable loader enabling operator to be more efficient with managing their system Securely inhibit a compromised device over-the-air and protect the integrity of the network. Easily inhibit the radio once it s been recovered 4-30 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 225

141 KMF Hello Feature Description Quick and efficient method of determining whether a radio is within the range of the system without unnecessary voice traffic Project 25 Phase 2 TDMA The proposed ASTRO25 system is configured with APCO Project 25 Phase 2 TDMA operation. With P25 TDMA operation, the ASTRO25 system leverages 2:1 TDMA channel efficiency to double voice path capability as compared to a P25 FDMA channel. This enhanced capability improves the Grade of Service (GoS) leading to fewer busied calls and faster callbacks during busy situations relative to a standard P25 FDMA system. This improvement is because TDMA provides double the talk path capability in the same RF bandwidth allocation. Having this additional capability improves grade of service by reducing channel busies. Furthermore, callbacks are faster due to the greater availability of talk paths in the TDMA solution. P25 TDMA also provides 6.25e (6.25 equivalent ) operation for satisfying certain future FCC spectral efficiency requirements FDMA/TDMA Interoperability It is important to note that Motorola Solutions Phase 2 TDMA operation compliments Phase 1 FDMA operation on the ASTRO25 platform; it does not replace it. Channels may be configured to operate as either TDMA-only or FDMA-only. Columbia County may configure channels to operate as either TDMA-only or FDMA-only. Talkgroups configured in TDMA mode will operate on the TDMA-configured channels; likewise, talkgroups configured in FDMA mode will operate on the FDMA configured channels. With TDMA operation enabled, voice-calling capacity increases compared to FDMA operation. With FDMA operation enabled, Columbia County may support subscribers that are only capable of Phase 1 FDMA operation. In addition to the separate operation of FDMA and TDMA enabled talkgroups on the system, the system is capable of allowing FDMA and TDMA enabled talkgroups to interoperate on the system. This interoperation capability is possible through two methods, Dynamic Talkgroup Assignment and Dynamic Channel Assignment. When both are used, they are known collectively as Dynamic Dual Mode. Dynamic Dual Mode allows users to interoperate between P25 FDMA and P25 TDMA services. It is part of the call processing application and uses an advanced control channel that dynamically switches call assignments between FDMA and TDMA. Dynamic Dual Mode is seamless to users and requires no intervention from users or network operators. For example, if a user in an active P25 TDMA talkgroup call roams onto a P25 FDMA-only site, the system automatically initiates P25 FDMA mode at the next push-to-talk (PTT). Alternatively, if an active P25 TDMA talkgroup call is underway at a site and a P25 FDMA-only member of the talkgroup joins (or affiliates ) with the call, the system automatically switches the call to P25 FDMA mode at the next PTT. The FDMA-only user is now included in the call. The call can be switched without any user intervention or awareness. As an added benefit in encrypted systems, the call set-up automatically switches between FDMA and TDMA while maintaining end-to-end encryption. This provides a high level of assurance that the system remains secure from dispatcher to radio user. Dynamic Dual Mode improves ease of use in ASTRO25 systems with a mixed fleet of P25 FDMA and P25 TDMA radios. For example: Radio users have seamless interoperability regardless of the operations mode. p. 226 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-31

142 Dispatch operators can automatically coordinate between P25 TDMA radio users and P25 FDMA radio users with no need to track or patch users together. System administrators do not need to pre-assign base stations as P25 TDMA or P25 FDMA; the system automatically assigns the appropriate station mode based on the needs of the user. The proposed system includes Dynamic Dual Mode operation on all sites and voice channels Motorola Solutions Wave Broadband PTT The proposed radio system includes WAVE Broadband PTT. This will allow Columbia County the opportunity to test this feature. We will provide the WAVE hardware and the WAVE software with the ASTRO25 radio system. These include the following: WAVE Hardware Components One (1) WAVE Server capable of supporting up to 500 broadband users One (1) Ethernet Switch One (1) Firewall One (1) ISGW Gateway Server and WAVE Radio Gateway software license One (1) WAVE Encryption Kit (Astro AES 256, DES-OFB, ADP) WAVE Software Components One (1) WAVE Server License - 12 Month License One (1) WAVE LMR Communication Channel - 12 Month License Fifty (50) WAVE Mobile Communicator Licenses for Android & ios - 12 Month License Columbia County will provide user hardware and networking requirements to connect their devices into WAVE. These include the following: Smartphones, tablets, laptops or desktops to use as WAVE clients Broadband connection into the WAVE server location Cellular and/or WiFi service Two (2) IP routable IP addresses Two (2) Fully Qualified Domain Names (FQDN) Two (2) SSL certificates WAVE provides a secure, high performance voice push-to-talk (PTT) service that operates over corporate Local / Wide Area Networks, commercial 4G/3G networks and Android/iOS devices, as well as desktop PCs. This service supports interactive connection capabilities from those commercial devices running on a data network to Land Mobile Radio (LMR) and Project 25 (P25) devices. Seamless communications and interoperability are mission critical requirements for LMR users and non LMR users to maintain daily operations. Our WAVE solution also provides enhanced communications and interoperability between commercial 4G/3G device users and P25 device users. Our WAVE solution consists of three major applications: the Mobile Communicator, the Desktop Communicator and the Advanced Desktop Communicator. WAVE Mobile Communicator - This PTT Smartphone application allows mobile users to access any authorized talkgroup using a data connection from their device. With this PTT software client, users can listen/talk on broadband talkgroups and talkgroups interconnected to LMR systems from anywhere (in the world) with cellular data service. This capability is currently supported via the 3G/4G carrier of choice over ios s and Android mobile devices Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 227

143 WAVE Desktop Communicator (Optional not supplied) This PTT software client allows users to monitor/talk on talkgroups and has features such as instant playback, status/presence information and location/maps. WAVE Dispatch Communicator (Optional not supplied) This WAVE software client provides dispatch functionality to users, allowing them to monitor/talk on WAVE talkgroups, perform patching, make/take phone calls, respond to man down alarms, etc., all through a unified software interface that can run on virtually any computer. Figure 4-4-8: ASTRO25 Broadband WAVE Land Mobile Radio (LMR) Interface WAVE supports wireline interface with the Motorola Solutions ASTRO25 network via the WAVE radio gateway. This interface leverages the protocols of Project 25 ISSI and the unique value added features of our ISSI 8000 platform WAVE Server Features The WAVE solution is comprised of an integrated PTT server (Proxy/Media/Management applications) to support PTT communication over commercially available ios android Smartphone devices over the customer-preferred choice of 3G/4G public carrier networks. Broadband users can make use of following features: Individual Private Call (One to One) - An individual private call can be made between two 4G/3G commercial device users. The initiating PTT user selects an individual from the PTT contact list and presses the PTT button. All communication between broadband and LMR users are group calls and one to one communication between broadband and LMR users is not supported currently. Talkgroup Call - This represents a call to a group of PTT users associated and defined as part of the talkgroup established in the Enterprise Management System. A WAVE talkgroup call can include 4G/3G commercial device users and P25 radio users. p. 228 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-33

144 Late Call Entry - The 4G/3G commercial device user will join in progress talkgroup calls if they happen to miss the start of the call. PTT User Presence & Location - 4G/3G commercial device users will see the current presence & location of WAVE contacts. User can also choose to map/locate WAVE talkgroup members. Enterprise Management Capabilities - To manage individual and group contact lists. PTT Use Cases and Benefits Extending Reach to radio users outside the coverage of the ASTRO25 system, enabling Global Broadband Connectivity Enhancing Choice for users who cannot or do not carry a radio, but still need occasional interoperability with radio users Increasing Productivity by enabling non radio users to collaborate efficiently via secure PTT communication Mutual Aid RF MHz Mutual Aid Repeaters Motorola Solutions is providing the standalone 800 mutual aid base/repeaters at the three designated RF sites required by the RFP as indicated in Table 4-7. The dispatch console will interface to the mutual aid repeaters by a CCGW at the three RF sites required, which will make it possible for the dispatch console to patch channels between the trunking system and mutual aid GTR8000 base/repeaters along with enabling and disabling the repeater function required by Region 9. The base/repeater will use the same antenna system as the trunked radio stations. Table 4-7: Simulcast remote sites No. Site Name Base/Repeater Channel Latitude Longitude 1 Deep Creek 8TAC N W 2 EOC 8CALL N W 3 Cumorah Hill 8TAC N W Microwave Backhaul Network Aviat Networks is providing a quote for the Columbia County microwave backhaul system. This system will include an indoor solution with IRU600v3 radios and the Eclipse Packet Node on the microwave system. The microwave hops will consist of MHSB for the Spur hops and 1+0 for the hops included on the ring. Each radio hop will provide up to 200 Mbps in airlink capacity. All hops will be on the L6Ghz frequency band. The network topology will be a ring configuration for diversity in the event of a hop failure with one spur hops with 1+1 Protection. All hops are configured with a reliability of % or better at 90MB capacity and at least 99.9% reliability with capacity of 200MB. Careful consideration was given to balancing stringent path availability criteria will minimizing antenna size for all paths. Also a three growth of 10.0 FT was considered for Clearance with a 100% of the Fresnel Zone with a K= Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 229

145 The new antenna sizes, types and cable lengths are preliminary, subject to field surveys and frequency coordination / FCC licensing results, to be finalized later during project engineering phase. The path model used in the Pathloss 5 calculations is Vigants-Barnett. The antennas are single pole dishes using standard performance RFS PAD6-59. The antennas used has a survival wind rate of at latest 125mph winds. The Ethernet Traffic will be protected using Ethernet Ring Protection (ERP) protocol, to provide an alternative route in case one of the hops fail. For the Spur, a 1+1 protection will be used as protection. For this project, we are proposing the use of Aviat Eclipse Radio systems. Indoor radio unit (IRU600v3) and an Indoor Nodal Unit (INUe). At each location of the loop a 7.0 rack of will be installed with one IRU600 v3 unit with a 1+0 Repeater configuration that will used 2RU positions on the rack, this radio will interconnect to 2 RAC units located on an INue also installed on the new rack, occupying 2RU also. The INue will be configure with 2 RAC cards to connect to the RFU units, at least 2 DACGE3 cards that will provide the availability of ETH traffic and 1AUX card that will provide up to 6 contacts or 4 relay alarms inputs/outputs. Inside the loop the only site that will have a modified Forest Tower on a MHSB configuration. Customer will provide -48V DC Power at all locations to connect to the provided Breaker Panel installed on the rack. The only exception is the Franklin ST location where an Eltec Flat Pack rectifier will be provided to connect to an AC source and provide -48V DC for the equipment. Also, a 45AH Battery bank is provided for 8 hours of power backup in case of a power failure. p. 230 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-35

146 To connect the ETH traffic the customer will connect to the RJ45 ports on the DACGE3 cards and in case additional ports are needed and Electrical SFP is provided to use the available SFP ports. In this project, each location provide at least 4 RJ45 ports and at the Prime Sites EOC and Deep Creek 8 ports connections are provided. The equipment to be used on the project will require and NMS plan to communicate in the system this plan will be provided by the customer and will be discuss if solution is selected. The sections below will provide more information on the products to be used on the Aviat Design present above. The Eclipse Packet Node Platform Introduction Aviat Networks is pleased to propose the Eclipse platform for microwave transport. Eclipse is in service with nearly every major service provider in the world and is the backbone of Aviat s long legacy of mission critical public safety networks. It is designed to meet existing TDM based requirements as well as new packet based networks. The Eclipse platform delivers a unique combination of high capacity TDM, scalable high capacity packet transport, intelligent IP networking and key convergence features. At the heart of the platform is the capability to transport native Mixed Mode operation comprehensive hybrid support for TDM, TDM+IP, and all IP. This is accomplished with the Data Packet Plane that can accelerate nodal networking with 5 Gbit/s of packet handling capacity, interconnecting with the 200 Mbit/s native TDM backplane that supports TDM transport. The Eclipse platform logically and seamlessly addresses transitioning from TDM, to Ethernet + TDM, and ultimately to a fully converged Ethernet network. Eclipse is the leading wireless backhaul solution available, with an outstanding combination of compelling features: Optimized Wireless Nodes. Eclipse nodal solution supports indoor and multiple outdoor RF units with built-in traffic routing, add-and-drop, aggregation and selectable traffic interfaces, including DS1, DS3, OC3, Fast Ethernet, and Gigabit Ethernet Optimized redundancy options. 1+1, space diversity, frequency diversity and dual diversity protection options. Super-PDH ring protection, built-in T1 loop switch, 2+0 Layer 1 (L1) or Layer 2 (L2) link aggregation on GigE links, redundant interfaces on DS1, DS3, OC3, and Ethernet Scalable Capacity Architecture. Only pay for the capacity you need today. Migration can be delivered at minimal cost and service disruption Intelligent high speed data transport. Eclipse supports high speed Ethernet plus TDM traffic over a single radio channel, configurable bandwidth assignments with low latency, built-in L2 operation, service differentiation and QoS features Control and intelligence. Advanced network-wide management and diagnostics Eclipse Platform Packet Capabilities The Eclipse platform introduces a data Packet Plane with a 5 Gbit/s switching capacity, adaptive coding and modulation, extended link aggregation, and solutions for timing over Ethernet. The Data Packet Plane operates seamlessly with the existing TDM backplane (circuit plane). The Data Packet Plane routes Ethernet traffic directly between the GigE switch and packet radio modem(s) to deliver maximum payload efficiency with lowest latency 4-36 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 231

147 The Packet Plane can also connect to the TDM backplane to support hybrid mixed-mode operation and to access wider aggregation and synchronization options In combination, they optimize transport options for TDM + Ethernet and Ethernet-only traffic In the Eclipse platform, operation is enabled on plug-in cards, selecting various data access cards (DACs) for DS1, DS3, Gigabit Ethernet, or SONET traffic. Radio access cards connect to the RF unit, allowing a variety of frequencies, capacities, protection and TX power levels. Key Eclipse packet handling features include: Major increases in nodal throughput Advanced GigE switch with 1+1 redundancy options High-capacity links with QPSK to 256 QAM ACM and CCDP/XPIC options Advanced L1 and L2 link aggregation Timing over Ethernet solutions Easy upgrades with low incremental cost Maximum flexibility and scalability. Comprehensive OAM capabilities in conjunction with its ProVision EMS. Figure 4-9: High Level Eclipse Overview The Eclipse platform is made up of the indoor nodal unit (INUe), with split-mount outdoor units (ODUs) or an all-indoor RF unit, the IRU600. The INUe replaces the traditional terminal or single-link based approach to networking with a nodal solution. One Eclipse INUe directly supports up to six links. Radio paths and customer interfaces are customized by plug-in cards, now supported by two switched planes: packet and circuit. This nodal concept dramatically reduces equipment, cabling and rack space, delivers superior network flexibility and resilience and minimizes costs. p. 232 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-37

148 Operation on licensed bands 5 to 38 GHz in North America Each link can be configured for a raw air-capacity up to 382 Mbit/s With data optimization techniques, each supports throughput up to 55 percent higher An INU or INUe is simply populated with the mix of cards needed at any time to provide the required performance and operation Equipment, cabling, and rack space is dramatically reduced Cards are hot-pluggable for easy upgrading and maintenance Field reliability exceeds the theoretical MTBF INUE Extended ODU and RFU Options While many customers choose the all-indoor IRU600 option, Eclipse also has split-mount ODU options. ODU 600 for frequency bands from 5 to 38 GHz The all-indoor IRU600 RFU is for frequency bands from 5.8 GHz to 11 GHz: Industry-leading system gain coupled with lowest power consumption 1+1 optimized Diplexer and filter-based antenna coupler options Expansion port Expandable to M+N configurations Over-the-air compatible with ODU 600 ODU and RFU options have been fine-tuned for the needs of the North American markets. The INUe has 10 slots available for RACs (radio access cards), DACs (data access cards, which provide multiple interface options including GigE, DS1, DS3 and OC3), and other optional cards. The Eclipse Node Control Card (NCC) is the primary power supply and performs node management and control functions. The Node Protection Card (NPC) is the secondary power supply and provides protection in the event of an NCC failure. The NCC also supports the Network Management System (NMS) channel. The NMS channel is a 512kbps link in the radio overhead, so no customer payload capacity is consumed. This NMS channel runs across every radio hop in the microwave system, providing connectivity to each Eclipse node in the network. For routing of the NMS between nodes and to other NMS connected devices, each NCC features an OSPF router supporting both dynamic and static routing which is hosted behind the node IP address. Links across a radio hop use routed Layer 3 (L3) connections so nodes at different sites must have unique network addresses. The NCC card also has four NMS ports on the front for connecting co-located nodes or other NMS connected devices. These connections use LAN Layer 2 (L2) connections so these nodes must have common network addresses. Once configured, the NMS channel can be viewed as a separate OSPF routed network allowing connectivity to every device in the network. The Eclipse INUe supports basic password log-in security as well as Strong log-in security as a licensed feature (Secure Management). There are three user permissions that can be assigned to a username based on access required, with Secure Management adding a 4 th permission level. The list below details the access rights for each level with the Secure Management features added shown in parenthesis: 4-38 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 233

149 Admin Add, modify, delete user accounts and view alarms and event browser (Access to RADIUS screens) Engineer Read / write access for configurations and diagnostics Operator / Read Only User can only read configuration and diagnostics (Crypto) (Access to security & log management, Payload Encryption, SNMPv3 traps, and diagnostics for alarms, event browser, and security/controls screens) The Strong Security suite consists of three licensable features: Secure Management, Payload Encryption, and RADIUS Client. Secure Management consists of additional permissions as discussed above in addition to providing advanced encryption and authentication options on the Ethernet connections between the Eclipse INUe node and the Portal or ProVision machines to provide secure communications. Payload Encryption encrypts all traffic carried over a radio link using randomly generated encryption keys to prevent eves-dropping and man-in-the-middle attacks. RADIUS Client (Remote Authentication Dial In User Service) supports centralized access control to the Eclipse nodes rather than in each individual node. RAC 70 This new generation radio access card delivers the latest technology for modems to Gigabit Ethernet transport. GigE port for direct front-panel connection to DAC GE switch Interconnect to TDM backplane for hybrid mixed-mode transport Channel bandwidths: 10 to 60 MHz ANSI Link capacities to 454 Mbit/s or 127xDS1 Cards are paired to provide fully redundant 1+1 hot-standby and diversity operation Offers QPSK to 1024 QAM adaptive coding and modulation RAC 70 DAC GEv3 The DAC GEv3 provides a Gigabit Ethernet interface and advanced packet processing for the Eclipse platform. It includes a 5 Gbit/s Packet Plane that inter-operates with INUe backplane to provide unmatched flexibility to support hybrid mixed mode TDM+IP or all-ip transport. The DAC GE delivers Quality of Service (QoS) controls and performance monitoring capabilities and will also support advanced data networking features such as internal link aggregation (802.3ad), Rapid Spanning Tree Protocol (802.1w) and VLAN support. Programmable 5 Gbit/s switching fabric IPv4 and IPv6 packet handling 1+1 redundancy via a stacking switch Supports L1 and L2 link aggregation DAC GE V3 p. 234 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-39

150 Traffic Policing Service OAM Supports jumbo frame size up to 9600 bytes, the largest such frame support available 3x1000 Base-T and two SFP ports for optical or electrical 1000Base-LX Power consumption: Less than 3 watts Weight: Less than 0.34 kg (0.74 lb) Power Requirements For location power requirements, please refer to the attach Power Calculation Spreadsheet. Conclusion The hardware solution provided allows for the most flexible deployment now, accommodating Native Ethernet. It also allows the users of this network to install the network now to meet your current needs and upgrade as the necessities varies over time. With a product designed and built in the USA and supported in the USA by a company that has been the single largest microwave radio systems supplier and integrator for 60 years you get unmatched support from Aviat Networks Professional services team that understands your network and has decades of experience supporting mission critical microwave radio systems. Aviat Networks has the complete team of resources to support the network not only from the initial design but through implementation and over the life of the system with local US based resources Microwave Path Design All microwave paths used in the transport are designed to exceed Columbia County s requirements. Table 6-5: Microwave Path Reliability Data Path Frequency (GHz) Dish Size (Ft) EOC Cumorah Hill Cumorah Hill Lulu Lulu CCSO CCSO Franklin Franklin Deep Creek Deep Creek EOC Deep Creek Forest Annual 2 Way Availability (%) Backup Power Systems Motorola Solutions has chosen Eltek to provide the required -48vdc DC Power system for each RF site. This system consists of a charger-rectifier and battery plant that will provide the requested 30 minutes of reserve power to the RF sites assuming 100% transmit time for base repeaters on each site. In addition, the system will provide an additional 7.5 hours of reserve power for the microwave system. Load shedding accomplishes two different reserve times for the trunked radio and 4-40 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 235

151 associated equipment. The DC system includes a 50% growth factor for future additions and the required 1 for N redundancy for rectifier modules. The Eltek charger-rectifier will be factory racked, wired and tested assembly. The assembly will contain individual DC circuit breaker distribution panel(s), voltage and current continuous metering capabilities, high/low DC voltage disconnect switching and all necessary maintenance and management alarm and control functions. The charger is provided in redundant arrangement with units of identical capacity and type working on a load-sharing basis during normal operation. Solid state monitoring by the power board will be continuous and automatic switchover employed in the event of failure of either unit. Upon switchover, the surviving rectifiers will be able to carry the entire site load and provide 24-hour recharge in the event of any loss of AC power. The DC distribution circuit breaker panels and the main -48 VDC ground (return) buss will be isolated in this rack as part of the Eltek power board assembly. The main distribution circuit breaker panel will provide the main bus feed for the radio racks. Each 19-inch radio rack will have a split breaker sub-panel for the various peripheral radio equipment, such as CCGW and RTU equipment breakers. The battery plants use EnerSys PowerSafe SBSXL80F-FT 48V 80Ah Battery Strings (2) 20-year life series batteries using proven gas recombination technology, which removes the need for water addition by controlling the evolution of hydrogen and oxygen during charging. The batteries will be mounted in the Charger-Rectifier rack for floor space conservation System Spares Motorola Solutions has included a set of recommended spares in Section 4.11 below to aid in the maintenance of the ASTRO25 system as required by the RFP. p. 236 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-41

152 This page intentionally left blank Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 237

153 4.4 ASTRO25 SYSTEM FEATURES Columbia County, Florida The proposed ASTRO25 system features P25 compliant trunking, as described in the TIA-102 standard. In order to achieve this compliance, Motorola Solutions optimizes custom solutions for mission-critical voice communications performance, more efficiently than solutions that use commercial-off-the-shelf network components. When public safety life or death decisions depend upon clear uninterrupted voice, Motorola Solutions has the correct IP solution. Table 4-8 provides a list of the published P25 trunked system features and their applicable standards. TIA-102 Standard Published P25 Trunked Features Table 4-8: P25 trunked system feature matrix FDMA TDMA TIA Standards Documents P25 CAI TRUNKING PROJECT 25 COMMON AIR INTERFACE Voice Calls Group Voice Call Yes Yes TSB102-A/TIA-102.AABD/ TIA-102.AABC-B/ TIA-102.AABF-A Individual Voice Call Yes Yes TSB102-A/TIA-102.AABD/ TIA-102.AABC-B/ TIA-102.AABF-A Availability Check on Called Party Yes Yes TIA-102.AABD Broadcast Voice Call Yes Yes TSB102-A/TIA-102.AABD Announcement Group Call Yes Yes TIA-102.AABD Emergency Group Voice Call Yes Yes TIA-102.AABD Mobility Management Roaming Yes Yes TSB102-A/TIA-102.AABD/ TIA-102.AABC-B Intra-System Roaming (Automatic) Yes Yes TSB102-A/TIA-102.AABD/TIA- 102.AABC-B Inter-System Roaming (Manual) Yes Yes TSB102-A/TIA-102.AABD/TIA- 102.AABC-B Registration Yes Yes TSB102-A/TIA-102.AABD/TIA- 102.AABC-B Restricting service access only to valid Yes Yes TIA-102.AABD SU De-registration Yes Yes TIA-102.AABD/TIA-102.AABC-B Group Affiliation Yes Yes TSB102-A/TIA-102.AABD/TIA- 102.AABC-B Call Restriction Yes 1 Yes 1 TSB102-A/TIA-102.AABC-B Call Routing Yes Yes TSB102-A 1 Motorola Solutions Network Management provides the capability to provision the services available to both subscriber radios and talkgroups. p. 238 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-43

154 TIA-102 Standard Published P25 Trunked Features FDMA TDMA TIA Standards Documents Wide Area Call Yes Yes TIA-102.AABD Location Registration Yes Yes TIA-102.AABD WUID Validity Timer Yes Yes TIA-102.AABD KEY MANAGEMENT KFD Based Key Management Manual Rekeying Features Yes Yes TIA-102.AACD Key Load Yes Yes TIA-102.AACD Key Erase Yes Yes TIA-102.AACD Erase all Keys Yes Yes TIA-102.AACD View Key Info Yes Yes TIA-102.AACD KMF Based Key Management Unique Key Encryption Key (UKEK) Yes N/A2 2 TIA-102.AACD, TIA-102.AACA Individual Radio Set Identifier (Ind RSI) Yes N/A 2 TIA-102.AACD, TIA-102.AACA Key Management Facility Radio Set Yes N/A 2 TIA-102.AACD, TIA-102.AACA Identifier (KMF RSI) Message Number Period (MNP) Yes N/A 2 TIA-102.AACD, TIA-102.AACA Key Load Yes N/A 2 TIA-102.AACD, TIA-102.AACA View Individual RSI Yes N/A 2 TIA-102.AACD, TIA-102.AACA Load Individual RSI Yes N/A 2 TIA-102.AACD, TIA-102.AACA View KMF RSI Yes N/A 2 TIA-102.AACD, TIA-102.AACA Load KMF RSI Yes N/A 2 TIA-102.AACD, TIA-102.AACA View MNP Yes N/A 2 TIA-102.AACD, TIA-102.AACA Load MNP Yes N/A 2 TIA-102.AACD, TIA-102.AACA View Keyset Info Yes N/A 2 TIA-102.AACD, TIA-102.AACA Activate Keyset Yes N/A 2 TIA-102.AACD, TIA-102.AACA SECURITY SERVICES AND CONFIDENTIALITY Encryption Transformation Traffic Encryption Yes 3 Yes 3 TIA-102.AAAB-A, TIA-102.AAAD/ TIA-102.AAAA-A/TIA-102.AAAC/ TIA-102.AAAD Integrity Chronological Integrity Yes 4 Yes 4 TIA-102.AAAB-A 2 The P25 KMF utilizes the Phase 1 FDMA data channel. There is no P25 Phase 2 TDMA data channel. 3 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 Solutions offers. Today there is no published P25 standard for Encrypted Integrated Data however Motorola Solutions started offering this feature in the 7.8 release 4 Today the Project 25 standard defines Chronological Integrity for OTAR, which Motorola Solutions offers Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 239

155 TIA-102 Standard Published P25 Trunked Features FDMA TDMA TIA Standards Documents Message Integrity Yes 5 Yes 5 TIA-102.AAAB-A SU Authentication Yes Yes TIA-102.AACE/TIA-102.BBAC Key Management Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Physical Key Distribution Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Over-the-Air Key Distribution Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Key Download Procedures Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Key Activation Procedures Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Destruction of Keys Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Rekey Request Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Provisioning of the MR Yes N/A 2 TIA-102.AAAB-A/TIA-102.AACA Key Compromise Yes 6 N/A 2 TIA-102.AAAB-A/TIA-102.AACA Encryption Encryption Yes Yes TSB102-A/TIA-102.AAAB-A/ TIA-102.AAAD/TIA-102.AACD/ TIA-102.AACA/TIA- 102.AACB/TIA-102.BBAC DES-OFB Encryption of Voice Yes Yes TSB102-A/TIA-102.AAAD/TIA- 102.BBAC AES Encryption of Voice Yes Yes TIA-102.AAAD/TIA-102.BBAC AES Encryption of Packet Data Yes Yes TIA-102.AAAD/TIA-102.BBAC Multiple Encryption Algorithms Yes Yes TIA-102.AACA/TIA-102.BBAC Multiple Encryption Keys Yes Yes TIA-102.AAAD/TIA-102.BBAC SUPPLEMENTARY SERVICES Priority Call Yes Yes TSB102-A/TIA-102.AABD/TIA- 102.BBAC Preemptive Priority Call Yes 7 Yes 7 TSB102-A/TIA-102.AABD-A/TIA- 102.BACA/TIA-102.BACE/TIA- 102.BBAC Dispatcher Audio Takeover Yes Yes TSB102-BAGA/TIA-102.BBAC Emergency Alarm Yes Yes TSB102-A/TIA-102.AABD/ TIA-102.AABC-B/TIA-102.BBAC Silent Emergency Yes Yes TSB102-A 5 Today the Project 25 standard defines Message Integrity for OTAR, which Motorola Solutions offers. The Project 25 standard will also support Message Integrity in the future Packet Data Security standard. Currently, Motorola Solutions supports Message Integrity for Encrypted Integrated Data. 6 Zerorize and No Service procedures can be used in Key Compromise situation. 7 Motorola Solutions understands this feature to mean Emergency Priority will Pre-empt a Non-Emergency Call p. 240 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-45

156 TIA-102 Standard Published P25 Trunked Features FDMA TDMA TIA Standards Documents Radio Unit Monitoring Yes 8 Yes 8 TSB102-A/TIA-102.AABD/TIA- 102.AABC-B/TIA-102.BBAC Talking Party Identification Yes Yes TSB102-A Call Alerting Yes Yes TSB102-A/TIA-102.AABD/TIA- 102.AABC-B/TIA-102.BBAC Radio Check Yes Yes TIA-102.AABD/TIA-102.AABC- B/TIA-102.BBAC Radio Inhibit Yes Yes TIA-102.AABD/TIA-102.AABC- B/TIA-102.BBAC Radio Uninhibit Yes Yes TIA-102.AABD/TIA-102.AABC- B/TIA-102.BBAC Alert Tones Yes Yes TIA-102.AABD/TIA-102.BBAC Emergency Call Yes Yes TIA-102.AABD/TIA-102.BBAC Pre-Programmed Emergency Group Call Yes Yes TIA-102.AABD/TIA-102.BBAC SU Status Update Yes Yes TIA-102.AABC-B/TIA-102.AABD- A/TIA-102.AABG/TIA- 102.BACD/TIA-102.BBAC SYSTEM SERVICES Network Status Broadcast Message Yes Yes TIA-102.AABD/TIA-102.BBAC System Status Broadcast Message Yes Yes TIA-102.AABD/TIA-102.BBAC Channel Identifier Update Broadcast Yes Yes TIA-102.AABD/TIA-102.BBAC Message Adjacent Status Broadcast Message Yes Yes TIA-102.AABD/TIA-102.BBAC Backup Control Channel Broadcast Message Yes Yes TIA-102.AABD/TIA-102.BBAC MISCELLANEOUS Electronic Serial Number Yes Yes TSB102-A Queuing Yes Yes TIA-102.AABD/TIA-102.BBAC Message Trunking Yes Yes TIA-102.AABD/TIA-102.BBAC Transmission Trunking Yes Yes TIA-102.AABD/TIA-102.BBAC Network Access Code Yes Yes TIA-102.AABD/TIA-102.BBAC Extended hunt sequence Yes Yes TIA-102.AABD/TIA-102.BBAC 8 Motorola Solutions supports remote Motorola Solutions supports remote unit monitor for talkgroup calls however it will not support the U2U version of remote unit monitor.e unit monitor for talkgroup calls however it will not support the U2U version of remote unit monitor Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 241

157 TIA-102 Standard Published P25 Trunked Features FDMA TDMA TIA Standards Documents PHYSICAL LAYER P25 Phase 1 FDMA P25 Phase 1 FDMA CAI Yes N/A TSB102-A/TIA-102.BAAA-A Enhanced Full Rate Vocoder Yes N/A TSB102-A/TIA-102.BABA 12.5 KHz Channel Bandwidth Yes N/A TIA-102.CAAA-B/ TIA-102.CAAB-B Frequency Division Multiple Access Yes N/A TSB102-A/TIA-102.BAAA-A (FDMA) 9.6 kbps Gross Bit Rate Yes N/A TSB102-A/TIA-102.BAAA-A C4FM and CQPSK Modulation Yes N/A TSB102-A/TIA-102.BAAA-A/TIA- 102.CAAA-C/TIA-102.CAAB-B P25 Phase 2 TDMA P25 Phase 2 TDMA CAI N/A Yes TIA-102.BBAB Enhanced Half Rate Vocoder N/A Yes 9 TIA-102.BBAB/TIA-102.BABA KHz Channel Bandwidth N/A Yes TIA-102.BBAB Frequency Division Multiple Access N/A Yes TIA-102.BBAB (FDMA) 9.6 kbps Gross Bit Rate N/A Yes TIA-102.BBAB HCPM and HDQPSK Modulation N/A Yes TIA-102.BBAB DATA SERVICES Packet Switched Confirmed Delivery Yes N/A 10 TSB102-A/TIA-102.BAEB-A Data Packet Switched Unconfirmed Delivery Yes N/A 10 TSB102-A/TIA-102.BAEB-A Data Packet Switched Data Network Access Yes N/A 10 TSB102-A/TIA-102.BAEB-A Data Configuration Radio to FNE Yes N/A 10 TIA-102.BAEA-A/TIA-102.BAEB- A/TIA-102.BAEE-A Packet Data Registration Yes N/A 10 TIA-102.BAAD-1./TIA-102.BAEB- A SU Registration Yes N/A 10 TIA-102.BAAD-1./TIA-102.BAEB- A SU Deregistration Yes N/A 10 TIA-102.BAAD-1./TIA-102.BAEB- A 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 The P25 Phase 1 FDMA data channel is used for P25 Packet Data Delivery. There is no P25 Phase 2 TDMA data channel.overall Comment This matrix comments on Motorola Solutions ASTRO 25 System Release 7.11 System Infrastructure Capabilities, this matrix does not comment on Motorola Solutions Subscriber Capabilities. Motorola Solutions offers a diverse portfolio of P25 solutions to address a wide variety of customer needs. Customers should work with Motorola Solutions representatives to ensure that their specific requirements are addressed. p. 242 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-47

158 TIA-102 Standard Published P25 Trunked Features FDMA TDMA TIA Standards Documents SU Location Tracking Yes N/A 10 TIA-102.BAAD-1./TIA-102.BAEB- A Mobile Data Interface (A) Yes N/A 10 TSB102-A/TIA-102.BAEB-A Link Layer and Physical Layer Protocols Yes N/A 10 TIA-102.BAEA-A/TIA-102.BAEB-A SNDCP (Sub network Dependent Yes N/A 10 TIA-102.BAEB-A Convergence Protocol) Fixed Host Data Interface (Ed) Yes N/A 10 TSB102-A/TIA-102.BAEB-A Ethernet (802.3) Yes N/A 10 TIA-102.BAEB-A Internet Protocol Suite Yes N/A 10 TIA-102.BAEB-A Simulcast Our ASTRO25 simulcast solution allows for extended system coverage, especially in areas where spectrum is scarce. Motorola Solutions digital simulcast technology is IP-based and extremely costeffective, eliminating the typical audio distribution equipment found in previous generation simulcast networks. Motorola Solutions P25 simulcast enables systems to be deployed with greater site separation without sacrificing coverage or capability. The simulcast and repeater site designs offer ease of radio operator use over large geographic areas. The proposed solution also takes advantage of Motorola Solutions proven narrowband 12.5 khz, 700 MHz platform and adds IP-based network design for the highest degree of reliability and flexibility /800 MHz Operation The ASTRO25 system infrastructure is capable of operation in both the 700 and 800 MHz Public Safety bands of operation. All RF remote-site base station radios and mobile and portable subscriber radios are all capable of operation in both bands. The system configuration includes antennas, lines, Tower Top Amplifiers (TTA) and multi-couplers, which all support operation in both bands. Although it is not possible to include 700 MHz and 800 MHz channels in the proposed combiners, compatible 800 MHz channels may be added to the proposed system by interfacing 800 MHz combiners with the proposed combiners using a diplexer. This is the proposed method that is used for the 800 MHz mutual aid repeaters at three of the Columbia sites Centralized System Management Alerts, diagnostics and faults in the system are reported to the supervisor/network management console. Two NM client workstations have been included in the proposed system design. One will be located at the Columbia County EOC (exact location to be determined). The other NM client will be located at the System Managers office in the Columbia County EOC. In addition to the fixed client workstation locations, the County and other dispatch supervisors will be able to access the Network Management functions remotely on the network, using remote desktop to one of these master site clients as authorized by the County System Manager. This will allow centralized system monitoring and management to keep the system healthy. Motorola Solutions has included in the proposed offering two concurrent user sessions for each of these Network Management application: Provisioning Manager Unified Event Manager 4-48 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 243

159 Zone Watch Channel Grid Radio Control Manager The network management subsystem is composed of Virtual Machine Servers (VMS), which host the necessary system-wide applications and databases required to maintain the ASTRO25 radio system. The VMSs incorporate server virtualization technology, which maximizes the utilization of the servers, provides adaptability to technology enhancements and better provides for future communication needs and migration. Additional information on the NM system and alerting is located in Section Network Management System ASTRO25 Trunking Call Services Motorola Solutions ASTRO25 trunking system offers a wide range of advanced call services to meet the demanding communications needs of a diverse, mission-critical workforce. The following sections describe several key calling features and benefits Call Categories Talkgroup Call is the primary communication level in an ASTRO25 trunked system as the majority of conversations take place within a talkgroup. Talkgroup Call provides the effect of a dedicated channel for each talkgroup. Emergency Alarm/Call provides users the ability to inform personnel of a life-threatening situation by depressing the radio s emergency alarm button. The emergency indication is also logged and cleared at the network management client terminal. The system is capable of functioning in one of the following two modes if all voice channels are occupied. Emergency Top-of-Queue places the unit initiating the emergency at the top of the busy queue list and allows access to the next available voice channel. Emergency Ruthless Preemption allows the unit initiating the emergency access to the voice channel with the lowest priority user currently assigned. Once the non-emergency user de-keys, the channel belongs to the emergency user. Private Call allows selective call to another individual user in the system regardless of what talkgroup either unit has selected. Call Alert allows selective sending of a signal to another user to call back the alerting party. Call alert remains enabled until cleared by the alerted party. This feature helps ensure that important messages get through, even if the called party is away from the radio. Call alert signaling takes place over the system control channel, so it is no burden on the valuable voice channels. Busy Queuing and Callback Although ASTRO25 trunking systems are considerably more frequency efficient than conventional radio systems, there may still be times when all of the voice channels are busy. If a radio user attempts to initiate a call while all the system channels are in use, the requesting user is put into a busy queue and then automatically notified when a channel becomes available. This feature allows the radio user to place the microphone down during a busy situation instead of continually re-keying in an effort to gain channel access. p. 244 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-49

160 Multiple Priority Levels ASTRO25 IP provides multiple levels of priority allowing system access to the most critical users during busy periods. Individual users and talkgroups may be assigned specific priority level(s), with up to ten levels supported for each, which will place higher priority users higher in the busy queue for quicker system access. The ASTRO25 IP system allows for flexible assignment of priority levels to meet your organizational needs. Continuous Assignment Updating This feature is designed to assure that a radio just coming into service during an active talkgroup conversation will be immediately assigned to the appropriate voice channel. The user will be included in his or her active talkgroup call with no special action required. To achieve this, the ASTRO25 IP system control channel continuously transmits the channel assignment for talkgroups involved in active calls Network Management System The Network Management System (NMS) is crucial for the proper operation, support and maintenance of your public safety radio system. Ensuring security and being able to diagnose efficiently issues is essential to maintaining the health of your radio system throughout its lifecycle. The standard Network Management applications are the tools an administrator requires to manage activity, monitor system health and configure changes to the system. The NMS supports the following services: Network Monitoring - Applications are included for monitoring the status of the transport network and the individual infrastructure components; displaying status information; forwarding alert information; and performing diagnostic procedures. Configuration Management - Facilities are provided for entering and maintaining the operational parameters of the infrastructure components and user devices (i.e., the mobile and portable radios). Accounting Management - NMS supports the tracking of radio usage of the system by providing an optional interface to third party accounting and/or billing applications. Performance Management - Standard and optional applications are available for monitoring, reporting, controlling and optimizing the use of system resources. Security Management - NMS includes features for setting user privileges and controlling their access to view and/or modify information contained in the configuration databases. The NMS subsystem includes the following virtual, zone-level servers within the zone core of the ASTRO25 system and is available from either the Columbia County PSAP, one of the master/dsr sites or remotely from other locations on the network when authorized by the System Manager: Zone Database Server (ZDS) User Configuration Server (UCS) Unified Event Manager (UEM) Zone Database Server The ZDS handles a variety of tasks; including hosting the zone configuration database, administering applications licenses, authenticating network manager users accessing the system and performing back-end support for user applications Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 245

161 The ZDS performs the following database server functions: Maintains the infrastructure (zone configuration) database for the zone Exports the infrastructure information from its database to the zone controller where it is stored as the local infrastructure database Maintains a replica of the current UCS database and home zone map Exports the radio information it receives from the UCS to the zone controller The ZDS also performs all network management and fault management polling of system devices to support the network management clients. The fault management information that the ZDS collects passes on to the UEM server. The ZDS handles a variety of administrative tasks, including the following: Administering the standard and optional applications licenses Authenticating network manager users accessing the system Performing back-end support services for user applications Handling telephone interconnect (optional) record processing User Configuration Server The UCS provides database storage and back-end processes required for most system-wide functions. The UCS makes it possible for management personnel to configure home zone maps, users, radios, talkgroups, critical sites, Adjacent Control Channels (ACC), security information at a system-level and other system-level parameters. Also made at the UCS level are Group and Unit ID home zone assignments. This information is configured using the PM application and is saved in the UCS database Unified Event Manager (UEM) UEM Enhanced Navigation uses the latest geo-map navigation to provide a high-level system view, with the ability to drill down to get device-specific status. With the use of the SDM 3000, this feature supports device metering, environmental inputs and digital controls, through a single interface. UEM Enhanced Navigation can also configure role-based access for different UEM users. This feature is ideal for organizations utilizing the ASTRO25 UEM for fault management functions. The UEM tracks all devices and environmental information from a single-user interface. The organization and accessibility of this data allows for a more intuitive end-user experience. p. 246 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-51

162 UEM Enhanced Navigation Tools: Integrated Fault Management allows a single-user interface to view, organize and manage fault data. Interactive Maps provide a system-wide view, zone view and site view. A detailed user-interface provides contextbased navigation, name aliasing, acknowledgment of alarms, digital commands and control, analog input readings and device metering. Environmental Alarms monitor environmental inputs and provide a high-level view of the site, including digital input status, analog input status or valve and digital output control status. ALL THE INFORMATION YOU NEED TO KEEP YOUR SYSTEM RUNNING AT PEAK PERFORMANCE Real-time Metering allows users to view readings remotely, assess signal strength and power and diagnose issues remotely. Command and Control features allow users to enable or disable channels, view multiple channels at once and set role-based or permissions-based access. The UEM provides a central location for managing all radio, transport and environmental devices on the system. The Enhanced UEM introduces support for microwave devices, device metering, environmental inputs and digital controls. There are also new site and network element overview screens with interactive maps and drill down navigation. The UEM application includes new functionality. IP connectivity to sites is required Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 247

163 New functionality (standard): Interactive Map View Zone level Ability to Acknowledge Alarms Display Name Aliasing Saved Settings for Reports Figure 4-10: Example of Site Topology The new UEM system, zone, site and network element views provide high-level status at a variety of levels. Improved navigation allows a user to drill down from high-level status alarms to the finest detail. Context based menus also allow users to jump straight to the details from any screen. View of Collocated Sites - View relative locations of Zone Core, RF Sites and Console Sites to better understand impact of fault alarms. Site Icons - identify site types and alarm status from a single screen. The application automatically discovers devices on the network to determine their real-time status. Color-coded symbols displayed on a topography map provide a geographical and hierarchical representation of the entire network. The UEM allows each user to filter out and customize the pertinent information important to their roles and responsibilities. Features and benefits of the UEM are outlined in Table 4-9. p. 248 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-53

164 Feature Centralized View of Entire Communications Network Intuitive Graphical User Interface (GUI) Auto Discovery of Devices Active Alarms View and Alarm Summary Secure Device Access (optional) Northbound Interface (optional) Notifications (included) Table 4-9: Benefits of the UEM Benefit Network Managers can view the entire ASTRO25 system status and quickly isolate problems to the board level. Network Managers can be quickly notified of failures on the system and diagnose device problems, utilizing a display and an intuitive GUI. Components are automatically discovered and map views are created to show the overall health of the network. Persistent single view all failure conditions in the network and a quick reference summary of alarms by severity allows users to quickly pinpoint the highest priority failures. SNMPv3 protocol with Triple DES and AES 256 bit encryption to prevent security breach attempts. Real time event stream using a standard industry protocol that can be used to forward events to a higher-level management application for added flexibility. User specified event notifications sent via , which can also be forwarded to a portable mobile device, allows System Managers to simultaneously address other tasks. The UEM gives the Network Manager virtually instantaneous notification of any system deficiency or element failure UEM Event Browser All events (or a filtered subset of events) that are received by UEM are viewable via the UEM event browser. By default, when viewing an event, the event browser displays Severity, Date/Time, Managed Resource, Entity and Message (Figure 4-10). Additional display properties are available. Up to 10,000 of the most recent events from any managed device within a zone can be displayed UEM Alarm Browser The UEM alarm browser (Figure 4-10) allows the user to view all alarms, or a filtered subset of alarms. By default, when viewing an alarm, the alarm browser displays Severity, Date/Time, Managed Resource, Entity, Message and Owner/Assignee information. Additional display properties are available. UEM supports exporting events and alarms for future analysis Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 249

165 Figure 4-11: UEM Alarm Browser sample screen Environmental Alarms The SDM 3000 Remote Terminal Units (RTU) provides interfaces for the environmental alarms at the radio sites. The SDM 3000 RTU acts as the primary interface to the site devices. The SDM 3000 RTU acts as an intelligent site management terminal that allows for continuous monitoring of critical site components and alarms. The NFM SDM 3000 RTU routes alarms information to the Network Management System and to the Motorola Solutions System Support Center via the IP-interface at each remote site, located on the ASTRO25 LAN. As proposed, this system includes an SDM 3000 RTU for each RF and Dispatch site in the system. This will allow for monitoring of the required alarms at each location. Digital alarm inputs and relay outputs for control of external devices are provided on each SDM 3000 RTU. These inputs and outputs may be used by the County to interface to site alarm devices such as power, intrusion, lights and other site alarms Inputs and Outputs Included on Each SDM 3000 RTU Any of the forty-eight Digital Inputs (DI), providing 48 dry-contact inputs, may be used as low-speed counters under application control. The module provides an isolated current so that the open/closed p. 250 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-55

166 state of the sensor may be determined. Each of the inputs is opto-isolated from the remaining circuitry on the module to provide maximum input surge immunity. Sixteen (16) Digital Outputs (DO) provide 16 low-current relay outputs: 12 of the relays have Form A contacts and four relays have Form C contacts. Magnetically latched relays should be used in systems that require long operation from the backup battery when the mains power fails; electrically energized relays should be used when it is mandatory that the relays open following loss of power or when the module is removed from the SDM 3000 RTU. Each relay has an internal feedback contact that the application may use to verify that the relay is open or closed. All connections to the relays are made via plug-in screw terminals on the module and all relays have surge arresting devices installed Example of Local Environmental Alarms Table 4-10 shows a general listing of the site equipment alarms (as applicable at each site), which can be monitored at the sites. Site Environmental Alarms Tower Lighting Building Intrusion Building Low Temperature Building High Temperature Building Smoke/Fire Fire Suppression System Discharge Generator Alarms Generator Running Generator Low Fuel Generator Over Crank Generator Other Failure Generator Battery Charger Alarm Generator High Coolant Temperature Alarm UPS Power System Alarms UPS Online Chgr AC Main Chgr Distribute Chgr Hi Voltage Chgr Lo Voltage Rectifier Fail DC Power Alarms Table 4-10: Site Alarms Site Environmental Alarms Fire Suppression System Trouble Fault Air Conditioner A Failure Air Conditioner B Failure Commercial Power Failure Transfer Switch Position TVSS Failure Generator Alarms Generator Control Switch Not Set Generator Low Oil Pressure Pre-Alarm Generator Low Coolant Temperature Pre-Alarm Generator High Coolant Temperature Pre-Alarm Generator Low Oil Pressure Alarm Generator Low Coolant Temperature Alarm Battery Charger Low Voltage AC Off Distribution Breaker tripped UPS Power System Alarms DC Power System Alarms Rectifier/Battery Charger High Voltage Rectifier/Battery Charger Low Voltage Rectifier Module Alarmed 4-56 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 251

167 Alerting Columbia County, Florida Alarm and event notifications are sent to the appropriate personnel through alerting which provides the capability to interface the UEM into a customer s mail server Network Management Terminals and Licenses The NMS Windows-based client/server architecture distributes most of the user application processing to the client PC workstations. The following applications run on, or be accessed from, the Network Management terminal: Provisioning Manager Radio Control Manager ZoneWatch Channel Grid Zone Historical Reports Unified Event Manager Unified Network Configuration Provisioning Manager The PM provides data entry screens for the mobile and portable radio units authorized to use the system. The PM is also used to set security information at a system level. The user interface is web-based and has intuitive browser-based user navigation features. Configuration reports can be generated. A sample PM screen is shown in Figure The subscriber profiles feature allows the replication of parameters that are common to multiple radio units, thereby reducing the time and effort to load the user configuration database. Working in concert with the UCS, radio unit data is entered once only for each unit and automatically distributed to the user configuration database residing in the ZDS at its resident zone and all other zones in a multi-zone system. p. 252 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-57

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

169 Other features include: GUI for ease of use Status function Online Help Figure 4-13: RCM screen example ZoneWatch Channel Grid and Control ZoneWatch Channel Grid and Control is a performance management tool with customizable displays and graphs to monitor real-time communications activity in a zone. The information displayed can help system managers be proactive in making better resource planning decisions, such as when channels need to be added to busier sites. Motorola Solutions has included the ZoneWatch application to the Network Management suite for Columbia County. ZoneWatch Channel Grid Screen - Air traffic within a single zone is displayed on a Site/Channel grid. Real-time call activity for each channel is displayed in its respective cell. ZoneWatch Control Display - This display presents call activity messages. These can be used to isolate errors, trace the progress of a call and troubleshoot or analyze current system activity. It also provides information about activity occurring on the control channel, such as rejects, emergency alarms and unit affiliations. A ZoneWatch Channel Grid and Control sample screen is shown in Figure p. 254 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-59

170 Figure 4-14: ZoneWatch Control Display Example Zone Historical Reports Zone Historical Reports have been included on the system. This application produces reports on radio infrastructure and radio resource usage across a single zone. A predefined set of reports, with field selection capability, is supplied to produce standard or tailored reports. Historical reports are generated automatically or on demand. Automatic reports are produced at a specific scheduled time and date or on a recurring time and date interval. Reports can be sent to the monitor screen, a printer, Hyper Text Markup Language (HTML), or CSV files Dynamic Reports Dynamic Reports is a PNM Suite application that provides near real-time call data collection and allows a user to display usage trends and patterns of activity for effective monitoring and reporting. Dynamic Reports is based on a third-party application (Seagate Crystal Reports). Dynamic Reports provides predefined parameters and template formats to display the value of multiple statistics for one or more managed objects. Once a report is activated, a Dynamic Report window appears and data is plotted according to the object and the time interval selected. At the end of each interval, a new set of statistical values is added to the display. When the display reaches the specified number of intervals, 4-60 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 255

171 each new interval added causes the oldest interval to be removed from the display. Dynamic Reports have been included in the proposed ASTRO25 radio system Network Management suite Affiliation User Display The Affiliation Display provides a dynamic view of the sites to which all operating subscriber units are currently affiliated, displaying zone, site and talkgroup details. It displays the association of a radio with a talkgroup and a site and information about conventional channels, console sites and consoles. It enables a user to monitor how radio users travel between different sites in a zone and how they communicate with other members of their assigned talkgroup and those outside of their talkgroup. The focus of the Affiliation Display can be on an individual site, a specific talkgroup, or an individual radio. Graphing capabilities are also included, which makes it easy to track and troubleshoot radios in the system. Optional pricing for the add-on the Affiliation Display application to the Network Management suite has been provided with this proposal Radio Authentication ASTRO 25 Radio Authentication provides a mechanism that allows a radio to prove that it is genuine and therefore can utilize the trunking system. It is based on the P25 TIA 102.AACE Link Layer Authentication standard; it can be incorporated on existing ASTRO 25 systems and most ASTRO 25 radios and it allows P25 radios from other vendors to use the feature. Systems without the optional Radio Authentication feature are susceptible to cloned and otherwise unwanted radios on the system. Radio Authentication prevents these unwanted P25 radios from successfully unit registering, thus preventing them from using the services of the system. Unregistered radios cannot listen to calls, place calls or otherwise disrupt customer operations. Radios are authenticated by the infrastructure using a challenge and response authentication protocol on the control channel. On Unit Registration for the radio is authenticated as shown below. Two additional control channel messages are added to the middle of the Unit Registration sequence for Radio Authentication. p. 256 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-61

172 Figure 4-15: On Unit Registration Authentication The security is based on the authentication key, which is a 128-bit AES key. Every Radio should use a different authentication key so that loss or compromise of one radio does not affect other radios. More specifically, the 56 bit Subscriber Unit Identity (SUID) is associated with an authentication key (K) to create a K-SUID pair. The SUID consists of the WACN (20 bits), System (12 bits) and Subscriber ID (24 bits). The radio unit registers using the SUID that has been CPS programmed into the radio. The authentication key is not used for End-to-End Voice Encryption or OTAR MCC 7500E System Description The MCC 7500E console features an intuitive, GUI (sample screenshot in Figure 4-15) that operates under the Microsoft Windows platform and follows the same standards as other Windows programs around the world. The screen layout is simple and uses valuable space efficiently. Key information and critical functions are identified clearly, with easy to understand icons. Dispatchers can quickly recognize these icons instead of reading text, hence maximizing their productivity. Many tasks can be completed more quickly and easily than ever before with the MCC 7500E consoles. Channels or talkgroups are displayed in on-screen folders for prioritization. Flashing red indicators easily identify incoming emergencies. Dispatchers can see information about who is calling, such as the time and call type. Trunked callers can be identified by real names versus numerical IDs Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 257

173 Figure 4-16: Sample Elite Dispatch Application Architecture Overview The MCC 7500E dispatch console is Motorola Solutions IP high-tier radio dispatch console system designed for use in our ASTRO25 trunking systems. Some of the more important features of the MCC 7500E console include: Seamless integration with ASTRO25 trunking systems: Supports the IP protocols of the trunking system s transport network; no circuit-switched network to packet-switched network conversion equipment is necessary Encryption and decryption are performed within the dispatch consoles, which allow true endto-end encryption in the radio system. Participation in the radio system s agency partitioning functionality. Configuration of the console subsystem via the radio system s centralized configuration subsystem (NM) so the user has a single point to configure the radio system. The configuration subsystem may be accessed from multiple remote locations so users can still have convenient access while enjoying the benefits of centralized configuration. Management of the console subsystem via the radio system s centralized network management subsystem so the customer has a single point for managing faults, accounting, performance and security of the radio system. The network management subsystem may be accessed from multiple remote locations so customers can still have convenient access while enjoying the benefits of centralized management. p. 258 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-63

174 Centralized and/or distributed logging of conventional and trunked radio audio associated radio call information and certain radio system events. Higher capacities in numerous areas Connection of MCC 7500E to IP Network Motorola Solutions MCC 7500E console equipment connects directly to the trunking system s IP transport network. It uses the IP packet protocols for passing call control data and call audio through the system. Elite Dispatch GUI The MCC 7500E dispatch console uses the Elite Dispatch GUI for displaying information to and accepting commands from the dispatch console user. The Elite Dispatch GUI is efficient, easy to use and intuitive, having been refined and proven through years of use in public safety dispatch centers around the world. The Elite Dispatch GUI used by the County today is the same as the proposed GUI and therefore will require minimal training for operators. An example of the Elite Dispatch GUI is shown in Figure Figure 4-17: Elite Dispatch GUI The Elite Dispatch GUI is based on Microsoft Windows GUI programming standards and contains many controls, displays and features, which are familiar to anyone who has used Windows-based applications. These features are described in detail in the following sections. Pull Down Menus The Elite Dispatch GUI provides the following pull down menus on a menu bar across the top of the dispatch window: 4-64 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 259

175 Configuration - Provides access to the configuration files used by the Elite Dispatch GUI. Also allows the dispatch application to be exited. Edit - Allows various aspects of how audio, resources and features are presented to the user on the Elite Dispatch GUI to be edited. Changes made using this menu are not permanent and are lost when the dispatch application is exited. View - Allows the dispatch console user to control whether or not the Activity Log and Auxiliary I/O Windows are shown. Folders - Allows the dispatch console user to switch between folders, add folders and change the folder tab width. Changes made using this menu are not permanent and are lost when the dispatch application is exited. Help - Provides access to detailed online help for using the Elite Dispatch GUI. The user may customize which menus are displayed and what they contain via the Elite Admin application. Toolbars Up to two toolbars may be present across the top of the dispatch window and may be used to provide quick access to frequently used features. The following are examples of the items that may be placed in the toolbars: Clock General Transmit Button Monitor Button All Mute Button Many other items may be placed in the toolbars. The Elite Admin application is used to define how many tool bars are displayed and what they contain. Status Line A status bar is provided across the bottom of the dispatch window for viewing the status of the dispatch console as well as various error messages. The most current status or error message is displayed in the status line until cleared by the dispatch console user. The dispatch console user may scroll through the last 10 statuses/error messages to view them and may clear them by using the Features menu on the menu bar. Resource Folders The Elite Dispatch GUI provides up to twenty 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. p. 260 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-65

176 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 this is done, these changes are not saved if the user logs off or changes configuration files for the dispatch application. Up to 36 compressed radio resources may be viewed on one folder when the program is run in the standard 800 x 600 resolution and there is no patch or multi-select folders. If patch and multi-select folders are used and are set to the minimum height, then 31 compressed resources may be viewed. To figure the number of auxiliary input/output resources that could also be viewed, use the rule of thumb that two auxiliary resources can fit in the same space as one radio resource. In other words, instead of 10 radio resources, 20 auxiliary resources could fit in the same space. If the program is run in 1024 x 768 resolution, there is room for even more radio and auxiliary resources per folder. Radio Resources Voice communication paths in the radio system are represented as radio resources on the Elite Dispatch GUI. Radio resources are also referred to as tiles on the Elite Dispatch GUI. These radio resources are used by the dispatch console user to communicate on and control the radio system. The following radio resources are supported: Trunked Talkgroups Trunked Announcement Groups Trunked Private Calls Analog Conventional Channels Indicators and Controls A radio resource contains indicators and controls that allow the dispatch console user to monitor and control various aspects of the radio channel. Examples of the indicators and controls that may appear on a radio resource include: Instant Transmit Button Transmit Active/Transmit Busy Indications Patch Active/Patch Busy Indications Received Call Indication Received Call Stack Individual Volume Control The types of indicators and controls that appear on the radio resource depend on the type of radio channel represented and its configuration in the Elite Admin application. The radio resource may be configured to always show the indicators and controls or to allow the dispatch console user to hide them when not in use to save space on the screen. Compressed, Larger Compressed and Expanded Resources Figure 4-17 shows a radio resource that allows the dispatch console user to hide the indicators and controls. This is also called a compressed resource. Notice the small arrow button that allows the resource to be opened and closed to show the controls and indicators Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 261

177 Figure 4-18: Compressed radio resource Figure 4-18 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. Figure 4-19: Larger compressed radio resource Figure 4-19 shows a radio resource that always shows the indicators and controls. This is also called an expanded resource. Notice there is no arrow button on the resource. Figure 4-20: Expanded radio resource Full parallel status for radio resources is reflected across all the dispatch consoles that have these radio resources assigned on them. That is, any activity or change on a radio resource appears on all dispatch consoles that have that resource assigned on them. p. 262 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-67

178 Received Call Stack The received call stack provides the dispatch console user with a visual record of the most recent inbound calls on radio resources. This allows the dispatch console user to keep track of calls during busy traffic periods. Outbound calls on radio resources from dispatch consoles (both the dispatch console containing the received call stack or parallel dispatch consoles) are not shown in the received call stack. The calls are displayed in list format on a radio resource with the most recent calls at the top of the list. The number of calls displayed in the list is configurable as is the type of information displayed. The types of information that can be displayed are unit ID, unit ID alias, site ID, zone ID and, type of call and time. If an alias is available for a piece of information it is displayed, otherwise the raw information is displayed. Figure 4-20 shows a radio resource containing a received call stack. Figure 4-21: Received call stack on a radio resource The received call stack provides a quick way for a dispatch console user to respond to calls in the stack. Various types of mouse clicks on calls in the stack provide the dispatch console user with different ways to reply to the call. The received call stack is configurable on a per-resource per-console basis, so a resource on one dispatch console can have it while the same resource on another dispatch console does not have it. The received call stack has a fixed memory of 25 calls, but the number of calls that are displayed is configurable via the Elite Admin application. The number displayed may be set anywhere from three to 24 calls in increments of three. Regardless of how many calls are actually displayed, the dispatch console user can always scroll through all 25 calls in the stack s memory. Stack display size is configured on a per radio resource per dispatch console basis. That is, each resource on a dispatch console may have different sized stack displays and the same resource on different dispatch consoles may have different sized stack displays. The dispatch console user can delete individual calls from the received call stack. All of the calls listed in a received call stack can also be deleted with a single action. Auxiliary Input and Output Resources Control relays and input buffers are represented as auxiliary input and output resources on the Elite Dispatch GUI. The dispatch console user uses the auxiliary input and output resources to monitor the state of input buffers and monitor/control the state of control relays. The auxiliary input and output resources are represented by various graphical icons that change their appearance based on the state of the resource. The particular icon that is associated with an input or 4-68 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 263

179 output is configured by the Elite Admin application. Examples of some of the icons that may be used are shown in Figure Figure 4-22: Auxiliary I/O resource icons Auxiliary input and output resources may be grouped together so that they can be moved or assigned/de-assigned as a group. This is useful for situations where the auxiliary input output resources are being used to interface to comparators or other devices that require multiple control relays or input buffers. A safety switch to help prevent unintended activation or deactivation may protect auxiliary output resources. 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. A safety switch to help prevent unintended clearing of an active input may also protect latched auxiliary input resources. 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 used infrequently, without permanently consuming space on the screen. Patch and Multi-Select Folders The patch and multi-select features are accessed via a set of dedicated folders on the Elite Dispatch GUI. These folders are smaller than the resource folders and may be placed on the screen to suit the dispatch console user s preferences. The placement is done in the Elite Admin application. There can be up to sixteen patch folders and three multi-select folders. Patch Folders Clicking on one of the patch folder tabs brings it into view. The patch group is then opened by clicking on the left-most button on the folder. Once the patch group is open, the patch group is editable and members may be added or removed from the patch group by clicking on the desired radio resources. Note that patch groups are active whenever there are members assigned to them. This is true even if the patch group is not open. p. 264 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-69

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

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

182 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 whether or not a dispatch console has the capability of displaying the activity log. The second level is via the dispatch console user interface where the dispatch console user can choose to view or not view the activity log. Note that if the dispatch console has not been given the capability of displaying the activity log, then the dispatch console user cannot see the activity log at all. The number of lines that are initially displayed by the activity log is configurable via the Elite Admin application or the dispatch console user interface. The number of lines that are displayed may also be changed in real-time by changing the size of the activity log window using standard Microsoft Windows resizing techniques. The user can scroll through all the entries in the activity log even if they cannot all be displayed at once. The information listed in the activity log can be stored in a text file on the dispatch console s hard disk. The size of the text file can be specified to be between 1 MB and 20 MB. When the file fills up, new data overwrites old data beginning with the oldest data. All data associated with a call is logged to the file, regardless of what portion of the data is actually shown in the activity log window. Help The dispatch console is designed to allow the dispatch console user to quickly access information on how to use its features. This help is available right on the dispatch console graphical user interface. There are three types of help available to the dispatch console user: On Line, Micro and Tool Tips. Online Help Online Help provides detailed information on how to use the dispatch console. The user accesses Online Help via the Help menu on the menu bar. The user can search for topics or keywords to find quickly 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 remember quickly 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 4-25 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 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 267

183 Figure 4-26: Micro Help Text The text displayed by the Micro Help feature may be edited via the Elite Admin application. Micro Help allows a dispatch console user to view the status of a control or indicator textually instead of graphically. Tool Tips Help Tool Tips Help provides information about tool bar buttons and menu bar menus to the dispatch console user. When the cursor is placed over a toolbar button, the button s name appears in a small pop-up window next to the cursor and a short explanation of the button appears in the status bar at the bottom of the dispatch user interface window. When the cursor is moved across a menu item in a menu, a description of the menu item appears in the status bar at the bottom of the dispatch user interface window. The text displayed by the Tool Tips feature may be edited via the Elite Admin application. Tool Tips allow a dispatch console user to see a short explanation of the button or menu item of interest quickly. Elite Admin Application The manner in which resources and audio are presented to the dispatch console user on the MCC 7500E dispatch console is managed by the Elite Admin application. Users can optimize how received audio is routed on the dispatch console, in addition to the look and feel of the Elite Dispatch GUI and how The following sections describe how configurations for the Elite Dispatch GUI are managed and what can be configured on the dispatch console via the Elite Admin application. Managing Dispatch Screens The Elite Dispatch GUI application reads a configuration file that tells it what should appear on the GUI and how received audio should be routed on the dispatch console when it first starts running. Properly trained personnel, using the Elite Admin configuration, create the configuration files (often called ELT files due to the.elt suffix in the file name). Multiple ELT files may be created to address different situations. For example, different ELT files can be created for different shifts in a dispatch center if the scope of dispatching changes significantly between shifts. Alternatively, different configuration files can be created for individual dispatch console users to meet their personal preferences. p. 268 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-73

184 A dispatch console user may switch between ELT files during normal operations, but cannot access any resources while the original file is being closed and the new file is being opened. The ELT files may be stored locally on the dispatch console computer, on a different dispatch console computer, or in a central location. The choice on where to store the files depends on many factors such as: Accessibility to the files - Do all dispatch console users need to access all the ELT files? If multiple agencies share a dispatch center, do they want to be able to access each other s files? Ease of managing the files - Are the dispatch consoles located in one physical location or are they geographically separated? Is one person managing the files or are multiple people managing them? The topology of the radio system s IP network - Are there servers (such as Domain Controllers) located at the dispatch console location that can be used to store the files? If the files are stored on a server, do the dispatch consoles have to retrieve them across WAN links? By default, when the Elite Dispatch GUI application starts up it asks the dispatch console user to specify which ELT file it should use. If this is not the customer s preferred mode of operation, the dispatch console can be configured so that it automatically opens a particular ELT file. Admin Capabilities The Elite Admin application allows a properly trained user to do the following: Create new configurations Modify existing configurations Save configurations Determine how many toolbars are present Determine items that should go on the toolbar(s) and where on the toolbar(s) they should go Determine the number of resource folders Determine the number of patch/multi-select folders Name the resource folders and patch/multi-select folders Determine the location of patch/multi-select folders Determine the height of patch/multi-select folders (e.g., taller if there are many members in the groups) Create pre-assigned patch/multi-select/primary groups Determine if dispatch console users have the ability to assign and de-assign resources Determine if the activity log is shown initially and where on the screen it is shown (dispatch console users may still hide or show the activity log) Assign/unassign radio and auxiliary input/output resources to various folders Determine location of radio and auxiliary input/output resources in the folders (dispatch console users may temporarily change the locations by dragging and dropping the resources) Determine where features are placed on each radio resource Modify the icons used for resource features Add a safety switch on radio resources Determine the size of each radio resource (compressed, larger compressed, or expanded) Determine whether selected radio audio stays in a speaker or moves to a headset when headsets are used (this is done on a per-resource, per-console basis) Determine border color for each radio resource Determine audio routing of resources to speakers Determine icons used for auxiliary input and outputs 4-74 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 269

185 Determine if auxiliary inputs and outputs appear in a separate window Set initial volume level of each radio resource Determine if auxiliary outputs are safety switch protected Determine border color for each auxiliary input and output Modify Tool Tips and Micro Help text Conventional Channel Gateway Conventional channels are much more integrated into the trunking systems than in previous radio - console configurations. The zone controller manages conventional channels in a manner similar to how it manages trunked talkgroups. The physical interface to the analog conventional stations also changes from previous radio systems. RF site routers are fitted with 4-wire interface cards, which are connected to the analog stations. Doing this provides two key benefits: It allows the conventional audio to use the same transport network as the trunked audio. It reduces the number of individual interface devices in the radio system. The portion of the router hardware and software that support the conventional stations is called the CCGW. To interface to analog conventional stations, the routers must be able to vocode and de-vocode the conventional audio, key the station, detect when the station sends audio to the router and detect when a parallel deskset console transmits on the station. This capability has been added to the routers used in Motorola Solutions trunking systems. Motorola Solutions has proposed CCGWs that match the existing configuration for conventional resources. Physical Interface to Station The MCC 7500E conventional channel gateway provides eight ports (per router) to which analog conventional base stations may be connected. Each port contains the following inputs and outputs. 600 Ohm, balanced analog audio input - Used to accept radio audio from the base station 600 Ohm, balanced analog audio output - Used to send console transmit audio to the base station Input buffer - Used to detect Carrier Operated Relay (COR) closure in the base station 1 Amp, 24 VDC relay output - Used for relay keying of the base station Each port is manifested as an RJ45 connector on the router Supported Configurations The MCC 7500E conventional channel gateway supports the following types of analog conventional base stations. R1 T1R1 T1R1 with Paging T2R2 T4R4 T8R8 T12R12 T14R14 p. 270 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-75

186 TnnR channels must be supported using combinations of T1R1 channels. Auxiliary Inputs and Outputs The MCC 7500E supports the ability to control or monitor Auxiliary inputs and outputs (Aux I/Os) that allow customers to control external devices via relay closures and sense the state of external devices via input buffers from the dispatch console. These Aux I/Os are referred to as Public Aux I/Os. Public Aux I/Os are accessible by more than one dispatch console. A change in state of the Aux I/O is reflected across all of the dispatch consoles that have it assigned on their user interfaces. These Aux I/Os are typically physically located in a common location that is shared by all the dispatch consoles. The MCC 7500E dispatch console supports Public Aux I/Os by accessing and controlling RTUs and displaying the status of the RTUs inputs and outputs on its user interface. A separate window to display the inputs and outputs is not required on the dispatch console. Graphical icons provided by the dispatch console GUI are used to represent both the function and state of relay outputs. For example, an icon consisting of a light bulb may be used to represent a relay output that is controlling lighting of some type. The dispatch console user would click on the button associated with the icon to change the state of the relay output and the icon would change between a lighted bulb and an unlighted bulb to reflect the state of the lighting. Graphical icons are also used to provide a visual indication of both the function and state of external inputs. For example, an icon consisting of a door may be used to represent an external input that is connected to a door position sensor. The door can be shown in the open state when the sensor says the door is open and it can be shown in the closed state when the sensor says it is closed. Multiple dispatch consoles may monitor and control the same relay output and/or external inputs. In this case, state changes are indicated across all dispatch consoles simultaneously. Individual relay outputs can be configured so that they require a safety switch to be pressed before they respond to any commands from the dispatch console user. It is possible that a relay output on one dispatch console may be protected by a safety switch, while the same relay output on a different dispatch console is not. The resetting of latched inputs may also be protected by using the safety switch. Supported Aux I/O Configurations The following Aux I/O configurations are supported: Momentary Input - This is an input where the user interface always shows the true state of the input. If the input is active, it is shown as active. If it is not active, it is shown as such. Latched Input - This is an input where the user interface does not necessarily show the true state of the input. When the input goes active, the user interface shows the state as active. The display will continue to show the state as active even if the input changes to the inactive state. A dispatch console user must manually reset the display to return it to the inactive state. Note that a dispatch console user cannot clear the display until the input itself is in the inactive state. Momentary Output - This output relay is activated when the dispatch console user presses the button on the user interface and deactivated when the dispatch console user releases the button. Latched Output - This output relay changes state only when the dispatch console user presses the button. The release of the button has no effect on the state of the relay. One press activates the relay; the next press deactivates the relay. Interlocked Latched Output - This latched output relay is part of a group of latched output relays. Only one of the relays in the group may be active at a time. Pressing the button for a relay 4-76 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 271

187 automatically deactivates the previously active relay. Pressing the same button twice does not deactivate that relay. There is always one and only one relay active in the group at all times. Interlocked relays work in a break before make fashion; that is, the previously active relay is deactivated before the new relay is activated. Aux I/O Hardware The SDM 3000 RTU is used to support most dispatch console Aux I/O needs. The SDM 3000 RTU is rack mountable in a standard 19-inch rack and is one rack unit high. The SDM 3000 RTU is capable of supporting up to 16 outputs and 48 inputs. Expansion chassis can be added to increase the number of inputs and outputs. The output relays are capable of switching 24VDC or 24VAC. Input buffers are capable of sensing a dry closure through 1000 feet or less (round trip) of 24 AWG wire. The RTUs can be physically located at console sites or trunking RF sites. The dispatch consoles and RTUs communicate with each other across the radio system s IP transport network. This allows much greater flexibility in putting Aux I/Os where they are needed compared to CENTRACOM Gold Series, which required all the Aux I/Os to be located in the CEB. The RTU provides single pole Form A relay outputs. Double pole, Form B, or Form C relays must be implemented using external relays that are controlled by the RTU relays Feature Descriptions High-level descriptions for all the features supported by the MCC 7500E dispatch console are given in this section. Centralized System Management The trunking system s configuration manager, fault manager and performance reporting applications configure and manage the MCC 7500E console. This provides the customer with a single point for configuring and managing the entire radio system, including the console portion. The MCC 7500E console system is able to control certain conventional resources in addition to the trunking system. The trunking system s configuration manager, fault manager and performance reporting applications also configure and manage the parts of the system interfacing to the conventional resources. End-to-End Encryption The addition of secure capability to the dispatch console allows true end-to-end encryption in the radio system. This provides the highest degree of security possible to those customers who wish to take advantage of this feature. The dispatch consoles support multiple encryption algorithms and multiple secure keys to allow them to access and control talkgroups from different agencies, if necessary. Gaining Access to Resources in the Communication System Resource Assignment Resource Assignment is a feature that allows a dispatch console user to choose which radio resources are monitored and controlled by the dispatch console. Resources must be assigned before they can be monitored and controlled. Once the assignment is made, the dispatch console starts receiving audio and status updates for the resource. p. 272 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-77

188 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 Assignment allows the flexibility to change which resources are monitored and controlled at a dispatch console. This can be useful, for example, on shift changes. It does not force one shift to deal with resources that are only used by a different shift. Resources can be unassigned when they are no longer needed at a dispatch console. Once resources are unassigned, the dispatch console stops receiving audio and status updates for the resource. Aux I/O Assignment Aux I/O Assignment is a feature that allows a dispatch console user to choose which Aux I/Os are monitored and controlled by the dispatch console. Aux I/Os must be assigned before they can be monitored and controlled. Once an Aux I/O assignment is made, the dispatch console starts receiving status updates for the Aux I/O. Aux I/O Assignment allows the flexibility to change which Aux I/Os are assigned at a dispatch console. This can be useful, for example, on shift changes. It does not force one shift to deal with Aux I/Os that are only used by a different shift. Aux I/Os can be unassigned when they are no longer needed at a dispatch console. Once Aux I/Os are unassigned, the dispatch console stops receiving status updates for the Aux I/O. Resource Status The Resource Status feature informs a dispatch console user of the operational condition of radio resources and Aux I/Os. This gives the dispatch console user greater control by knowing which resources are available and which are not available. Operational failures of the resources and Aux I/Os can be displayed to the dispatch console user so the lack of operational ability is known. Configuration of Audio Presentation for Resources Audio Destination Assignment A dispatch console supports multiple speakers and can be configured so that the audio associated with different resources is routed to different speakers at the dispatch console. Audio Destination Assignment is a console feature that allows a dispatch console user to choose which audio destinations (speakers) are to be used for a given resource. Audio for a resource is generally directed to one of two destinations, depending upon the resource s current select status. Selected resources have their audio sent to the speaker designated as the select audio destination for that resource. When a resource is not selected, its audio is sent to the speaker designated as the unselect audio destination for that resource. In most cases, a single speaker is designated as the select audio destination for all resources monitored by that console. In this case, whichever resource is currently selected has its audio presented in that speaker. On some console installations, it may be desirable to route audio for a resource to a particular destination regardless of that resource s select status. This is accomplished by setting a resource s select audio destination to be the same as its unselect audio destination. Speakers configured in this way are often referred to as dedicated or monitor speakers Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 273

189 Basic Audio (Talk/Listen) Functions Single-Select The Single-Select feature allows only one radio resource to be selected at a time. When a resource is single-selected, the previously selected resource becomes deselected. The Single-Select feature is active when there are no Multi-Select groups open. When a Multi-Select group is closed without opening another Multi-Select group, the Single-Select feature becomes active and the resource that had been selected prior to opening a Multi-Select group is once again selected. Single-Selecting a resource routes the inbound audio on the resource to the designated speaker allowing that audio to be easily distinguishable from the other audio at the dispatch console. It automatically raises the resource s individual volume level to full so inbound audio on that resource can be heard clearly. It also designates that resource as the one to be used by console features such as General Transmit, Monitor and Page PTT. The main advantage of the Single-Select feature over the Multi-Select feature is that the previously selected resource is deselected when another resource is selected. This saves having to deselect one resource before selecting another. Multi-Select The Multi-Select feature allows a dispatch console to define groups of selected radio resources. When a Multi-Select group is opened, all of the resources in the group are simultaneously selected. A dispatch console can support multiple Multi-Select groups, each of which supports multiple, potentially overlapping, resources If a Multi-Select group is opened while another Multi-Select group is open, the first group is closed and all of its resources deselected before the second group is opened. If a Multi-Select group is opened while no other Multi-Select group is open, the Single Selected resource is first deselected. When a Multi-Select group is closed without opening another Multi-Select group, the Single Select feature becomes active and the resource that had been selected prior to opening the Multi-Select group is once again selected. Resources can be added or removed from a Multi-Select group while it is open or while it is closed. Multi-Selecting a group of resources routes the inbound audio on the resources to the resources select audio destinations, allowing that audio to be easily distinguishable from the other audio at the dispatch console. It automatically raises the resources individual volume level to full, so inbound audio on the resources can be heard clearly. It also designates those resources as the ones to be used by console features such as General Transmit, Monitor and Page PTT. The Multi-Select feature has two advantages over the Single Select feature. It allows multiple resources to be selected simultaneously. It also allows groups of resources to be defined and stored so that multiple resources can be conveniently selected and deselected. The resources of Multi-Select groups can also be simultaneously transmitted easily on without having to open the Multi-Select group by using the APB Transmit feature. Inbound Call Indication The Inbound Call Indication feature is used to indicate audio activity on a radio resource. If the resource is selected on the dispatch console, the indication flashes when inbound audio is detected. If p. 274 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-79

190 it is not selected on the dispatch console, the indication does not flash. The indication is not affected by the select status of the resource on any other dispatch console. It is also used to associate audio being heard from the dispatch console s speakers with a resource. The Inbound Call Indication can have different sources depending on the type of resource on which it appears. For trunked resources, the source is the trunking controller. For some conventional resources, the source can be an input that detects an external dry closure. This is called a Carrier Operated Relay (COR) Input. For some conventional resources, the source is audio activity on the receive path from the station. This is called VOX detection. Individual Resource Volume Control The Individual Resource Volume Control feature allows the dispatch console user to change the level at which each resource is mixed into a speaker. (It is common to have the audio from many resources routed to the same speaker, especially when these resources are unselected.) The Individual Resource Volume Control feature can be used at individual dispatch consoles to lower the volume level of less important resources and raise the volume level of resources as they become important. The initial volume level is set when the resource is assigned. The volume level for a resource is automatically raised to the full volume level when the resource is selected. If the volume level is adjusted while a resource is selected, it remains at the new volume level even after the resource is deselected. If the resource s volume level is not adjusted while the resource is selected, deselecting the resource restores its volume level to its volume level in effect prior to being selected. All Mute The All Mute feature is used to mute all of the audio on resources that are not currently selected at a dispatch console. When the All Mute feature is activated, all audio on resources that are not selected is muted until the All Mute feature is deactivated or a certain amount of time elapses, typically 30 seconds. The amount of time the All Mute feature stays active and the amount of attenuation it applies to the audio are programmable through the radio system s configuration application. If a resource s individual volume setting is such that it is lower than the All Mute feature s attenuated level, the resource s volume setting will not be changed by the All Mute feature. That is, the dispatch console will not increase the resource s volume setting above the level set by the dispatch console user. The All Mute feature is used when the dispatch console user does not want to be disturbed by the audio from the unselect resources. Using the All Mute feature is better than turning down the volume of the Unselect speaker because the volume is restored automatically when the All Mute feature is deactivated. Acoustic Cross Mute The Acoustic Cross Mute feature is used to prevent acoustic feedback from occurring when dispatch consoles are physically located near each other. Dispatch consoles that are monitoring the same radio resource can normally hear each other s outbound audio transmissions. This is called parallel operator audio. If two dispatch consoles are physically close to each other and the parallel operator audio appears in a speaker, the potential exists for a feedback condition between the speaker on the nontransmitting dispatch console and the microphone on the transmitting dispatch console. The Acoustic Cross Mute feature provides the means to specify groups of dispatch consoles, which mute parallel operator audio on all radio resources that they have in common Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 275

191 High Speed Mute The High Speed Mute feature allows an external device to provide a dry contact closure to the dispatch console subsystem that, when activated, mutes the receive audio of a conventional radio resource at all dispatch consoles monitoring that resource. The audio received remains muted as long as the closure is present and un-mutes when it is removed. The High Speed Mute feature provides the customer with the means to control what audio appears at the dispatch consoles for a given conventional radio resource. General Transmit General Transmit is a feature that initiates a voice transmission on the currently selected resources. General Transmit is one of the most convenient methods for transmitting since it can be initiated with the footswitch, the headset transmit button, the microphone transmit button, or the General Transmit API functions. General Transmit is a medium-priority transmission. Please refer to the Transmission Priority Levels feature on the following page for more information on transmit priorities. It is important to note that a dispatch console can transfer control of an active General Transmit freely between the General Transmit API functions, the headset transmit button, the microphone transmit button and the footswitch while not losing the transmission. This can be used to free up a dispatch console user s hands for other activities such as writing notes. The General Transmit feature provides easy access to transmitting on the selected resources. Instant Transmit Instant Transmit is a feature that allows a dispatch console user to initiate a transmission on a specific resource regardless of its select state. It is the most direct method of transmitting on a resource. Instant Transmit is a high-priority transmission. Please refer to the Transmit Priority Levels feature on the following page for more information on transmit priorities. It is important to note that the dispatch console user can Instant Transmit even when the dispatch console user is currently performing a General Transmit or APB Transmit. In this case, microphone audio will be sent to both the selected resource(s) and the one upon which is being instantly transmitted. The Instant Transmit feature gives the dispatch console user an additional level of control that is not available with the General Transmit feature. It gives a dispatch console user the ability to transmit quickly on a resource that is unselected. It allows a dispatch console user to monitor the audio from the selected resources in the headset and simultaneously transmit to another resource. It also allows a dispatch console user to take over a lower-priority transmit from a parallel dispatch console. Instant Transmit Safety Switch Instant Transmit Safety Switch is a feature that requires a dispatch console user to press a safety switch before initiating an instant transmit on a specific resource (regardless of whether it is selected or not). This helps ensure the dispatcher does not accidentally instant transmit on a particular radio channel. p. 276 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-81

192 All Points Bulletin Transmit All Points Bulletin (APB) Transmit is a feature that initiates a voice transmission on the resources of a Multi-Select group. An APB Transmit control on a dispatch console must have one and only one Multi-Select group associated with it. APB Transmit is a high-priority transmission. Please refer to the Transmit Priority Levels feature in the following section for more information on transmit priorities. The APB Transmit feature allows transmission to all resources in its associated Multi-Select group even when the group is closed. The APB Transmit feature provides easy access for transmitting to a pre-selected group of resources. APB Transmit is commonly used to make an announcement to many radio users. It also allows a dispatch console user to take over a lower priority transmit from a parallel dispatch console. Transmit Priority Levels The Transmit Priority Levels feature is a hierarchy of transmit privileges for different types of transmissions on the same dispatch console or between dispatch consoles. It provides an orderly and consistent method for allowing higher priority transmissions to take over resources from lower priority transmissions. The priority levels from highest to lowest are: Primary supervisor console instant transmit or APB transmit Secondary supervisor console instant transmit or APB transmit Non-supervisor console instant transmit or APB transmit General transmit on any type of console (single- or multi-select) Patch transmit on any type of console Console Transmits While Receiving Audio The Console Transmits While Receiving Audio feature allows a dispatch console to receive audio from other radio resources while transmitting on a particular radio resource. This allows a dispatch console user to hear audio from other resources while transmitting. Note that this is different from full duplex audio on a single radio resource. Resource Transmit Status Transmitting The Resource Transmit Status - Transmitting feature is used on a per dispatch console basis to indicate when a dispatch console is transmitting on a resource. A visual indication is provided on the user interface to indicate it is transmitting. Each dispatch console uses the Resource Transmit Status - Transmitting feature to display its own transmit status. It is not used to display the status of parallel dispatch consoles. Refer to the Resource Transmit Status - Parallel MCC 7500E Op Busy feature for more information about parallel dispatch console status. Resource Transmit Status Parallel MCC 7500E Op Busy The Resource Transmit Status - Parallel MCC 7500E Op Busy feature is used to indicate when a parallel Motorola Solutions MCC 7500E dispatch console is transmitting on a resource. A visual indication is provided on the non-transmitting dispatch consoles to indicate a parallel dispatch console is transmitting. This feature, in conjunction with the Resource Transmit Status - Parallel Non-MCC 4-82 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 277

193 7500E Op Busy feature, provides the means for a dispatch console user to know if a particular resource is available for use. The dispatch console user can see the alias of the parallel MCC 7500E dispatch console that is transmitting on either trunked or conventional resources. Each dispatch console uses the Resource Transmit Status - Parallel MCC 7500E Op Busy feature to display the parallel console transmit status of each resource to which it has been assigned. Resource Transmit Status - Trunking Busy/Callback The Resource Transmit Status - Trunking Busy/Callback feature is used to indicate when a trunking resource is not available for a dispatch console user to use and to alert the user when it becomes available. Audible indications are provided on the dispatch console to indicate a trunking resource is not available and when it becomes available. This feature allows the dispatch console user to know when a trunked resource is available again without having to try to transmit on it continuously. Trunked Base Station/Repeater Control The Repeat Control feature (also known as Repeat Enable) allows a dispatch console user to enable and disable the ability of radio users in a talkgroup to hear the transmissions of other radio users in that talkgroup. When the feature is enabled on a talkgroup, transmit audio from a radio is made available to all of the radios monitoring the talkgroup. If the feature is disabled on a talkgroup, transmit audio from a radio is not made available to other radio users monitoring the talkgroup. In either case, the radio s transmit audio is routed to the dispatch consoles. When repeat control is enabled or disabled, all dispatch consoles with this resource assigned are updated with the current status of the feature. This feature can be controlled from any dispatch console. System Access Priority Select (Normal/Tactical) The System Access Priority Select feature allows a dispatch console user to select the relative system access priority of a trunked resource within the resource s communication system. Currently, there are only two possible priorities: NORMAL priority and TACTICAL priority. Call requests from a trunked resource with TACTICAL priority have priority over call requests from a trunked resource with NORMAL priority in obtaining a repeater for communications. Only emergency calls have a higher priority than TACTICAL. When the System Access Priority status of a resource is changed, it is updated at all dispatch consoles in the systems that are monitoring that trunked resource. The System Access Priority Select feature can be used to change the system access priority status of a trunked resource to TACTICAL in order to give the resource a better chance of gaining communication access in a busy system. If, during a repeater busy condition, two call requests are queued with one as NORMAL and the other as TACTICAL priority, then the one with TACTICAL priority gains access to the system when the next repeater becomes available. Supported Types of Analog Conventional Base Stations A Motorola Solutions MCC 7500E dispatch console is capable of accessing and controlling the following types of analog conventional base stations. R1 T1R1 T2R2 p. 278 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-83

194 T4R4 T8R8 T12R12 T14R14 The above types of base stations are referred to as TnRn stations. A TnRn station has one n-frequency transmitter and one n-frequency receiver. The dispatch console can process audio received from the station and present it to the dispatch console user via speakers or headsets key the station s transmitter and provide it with audio to be transmitted over-the-air (except for R1 stations which don t have a transmitter) control various features on the stations such as frequency selection, PL selection, repeater on/off, etc. Voice Call Types on Radio Resources Conventional PTT Call The Conventional PTT Call feature allows a dispatch console user to initiate and receive normal PTT calls on conventional radio resources. A normal PTT call is not directed to any specific individual or talkgroup and does not carry any special importance. It is intended to be heard by all users listening to that radio resource. Trunking Talkgroup Call The Trunking Talkgroup Call feature allows a dispatch console user to initiate and receive talkgroup calls on trunked radio resources. A trunking talkgroup call is a method for communicating with a specific set of users on a trunked radio system. Users only hear the audio associated with talkgroups with which they are currently affiliated. This feature allows a user to speak with a specific group of users without disturbing other users. Trunking Announcement Group Call The Trunking Announcement Group Call feature allows a dispatch console user to initiate and receive announcement group calls on trunked radio resources. A trunking announcement group call is a method for communicating with multiple trunking talkgroups simultaneously. An announcement group is composed of multiple talkgroups that have been grouped together. The association of talkgroups to an announcement group is done by the trunking system s configuration subsystem. This feature allows a user to speak quickly and easily with multiple trunking talkgroups simultaneously. Trunking Emergency Call Trunking Emergency Calls are high-priority voice transmissions initiated by radios or dispatch consoles that allow them to communicate with each other in critical situations. Trunking emergency calls initiated by dispatch consoles reserve a voice channel for the duration of an emergency. A trunking emergency call is initiated by a radio when the radio transmits while it is in emergency mode. Trunking emergency calls are typically presented at a dispatch console using visual indications. Dispatch consoles are notified when another dispatch console starts a trunking emergency call Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 279

195 In ASTRO25 trunking systems, priority is given to allocating a voice channel to a trunking emergency call over a regular call regardless of whether the regular call is at either a tactical or normal priority level. Trunking emergency calls can be initiated from a dispatch console on ASTRO25 IP trunking resources only. When a trunking emergency call is started from a dispatch console, the call is assigned a voice channel for an indefinite period. This guarantees a path for voice communication for the duration of an emergency. The voice channel is released only when a dispatch console ends the call. A dispatch console user can take responsibility for an emergency by recognizing the trunking emergency call. All dispatch consoles are notified that the call has been recognized. Trunking emergency calls initiated by a dispatch console are automatically reported to all dispatch consoles as being recognized since a dispatch console user took an explicit action to initiate the trunking emergency call. When an emergency is over, a dispatch console can end the trunking emergency call. All dispatch consoles are notified that the call has been ended. When a dispatch console ends a trunking emergency call, the voice channel allocated for the call is released. Ending the trunking emergency call at the dispatch console has no effect on the state of the radio that initiated the call. Any radio units that initiated trunking emergency calls remain in emergency mode until the radio users explicitly return them to a normal mode of operation. If a radio that is in emergency mode transmits after a dispatch console user has ended the trunked emergency call, the trunked emergency call will be reestablished. The Trunking Emergency Call feature is used by radios and consoles for high priority voice communication. A dispatch console generally initiates a Trunking Emergency Call to guarantee a voice channel for the duration of an emergency. Received Emergency Call Indication The Received Emergency Call Indication feature allows a dispatch console user to be quickly informed that an emergency call has been received on a trunked resource. The indication is a visual indication on the user interface. The visual indication continues until the emergency call has been ended by a dispatch console. The Received Emergency Call Indication feature allows the dispatch console user to quickly identify on which resource an emergency call has occurred. Auto-Open of Quick List The Auto-Open of Quick List feature allows a dispatch console user to quickly access the controls necessary to handle a trunking emergency call. The Quick List contains controls for recognizing an emergency call, initiating an emergency call and ending an emergency call. When a resource with an unacknowledged emergency on the dispatch console s user interface is expanded by the dispatch console user the Auto-Open of Quick List feature automatically opens the quick list The Auto-Open of Quick List feature allows the dispatch console user to begin handling an emergency with a minimum of actions. p. 280 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-85

196 Emergency End (Knockdown) The Emergency End (Knockdown) feature allows a dispatch console user to terminate an emergency call. After an emergency call has been recognized and the situation has been addressed, the dispatch console user ends the emergency call by using the Emergency End feature. When the dispatch console user does this, the visual emergency indication on the dispatch console s user interface is removed and the dispatch console informs the trunking controller and all other dispatch consoles that the emergency has been terminated. Parallel dispatch consoles then clear their own emergency status indications for the resource if no other emergencies are active on it. Emergency Automatic Audio Level Control The Emergency Automatic Audio Level Control feature ensures that the audio associated with an emergency call is not missed due to its volume being too low. When an emergency call is received by a dispatch console, the volume of the received audio associated with the call is raised to its maximum level. When the emergency call is acknowledged by a dispatch console user, the volume is returned to its normal level. The Emergency Automatic Audio Level Control feature allows the dispatch console user to hear the emergency call audio while the emergency call audible alarm is active. Trunking Individual Call The Trunking Individual Call feature allows a dispatch console user to initiate and receive individual calls on trunked radio resources. A trunking individual call is a method for allowing a call to be placed to a specific user on the trunking system. A dedicated individual call resource on the dispatch console user interface allows the dispatch console user to initiate or answer an individual call. All types of individual calls are initiated from the dispatch console in the same way. When an individual call request is received by the target radio, the dispatch console user receives an indication that the target radio is ringing. At this point, the dispatch console is waiting for the radio user to answer the ring. Once the individual call is answered, the call is allowed to proceed. A dispatch console user may use an individual call to communicate privately with either a single radio user or a single MCC 7500E dispatch console user. If the target radio or dispatch console is not available when an individual call is attempted, the dispatch console user receives an indication that the call could not be completed. All inbound individual calls are announced to the dispatch console user. A ringing inbound call must be answered explicitly by the dispatch console user. At a dispatch console, individual calls can be ended by a request from the dispatch console or by the expiration of an audio activity timer. The audio activity timer expires when there has been no audio activity on an active individual call for an extended period. This time is specified via the configuration application at the network manager. If there is no audio activity on an active individual call for the specified amount of time, the individual call is automatically ended. When an individual call is ended by the radio user or the other dispatch console user, the console individual call resource automatically hangs up. Similarly, when an individual call is ended by the dispatch console user, the radio or other dispatch console automatically hangs up. This is known as the Cancel Service characteristic of individual call Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 281

197 The Trunking Individual Call feature is designed to allow a dispatch console to engage in private conversations with individual radio or dispatch console users. Once an individual call is established on a resource, the resource can be added to a patch group with another type of resource. Semi-Duplex or Full-Duplex Operation Depending on the type of radio unit and the type of trunking system, an individual call can be either semi-duplex or full-duplex. The console subsystem is capable of supporting both types of calls with no configuration changes or dispatch console user intervention required. When a dispatch console user is involved in either type of individual call, the dispatch console user is required to activate a PTT to talk. This is required to prevent unexpected results if a telephone resource is off-hook while an individual call is in process. A telephone resource does not require a PTT because it has hands-free full-duplex operation when the dispatch console user is using a headset. If the individual call also had hands-free full-duplex operation, the dispatch console would not be able to tell to which destination (telephone resource or individual call) the microphone audio should be sent. Therefore, a PTT is required to indicate to the dispatch console that the dispatch console user desires to speak on the individual call instead of the telephone resource. (In this context, the term telephone resource refers to two different types of telephone services. It refers to the external telephone that can be connected to a dispatch console so the dispatch console s headset can be used for both radio and telephone communications. It also refers to the console telephony interface, which will be added in a future release.) The dispatch console always allows receive audio to be presented to the dispatch console user, but in a semi-duplex call, the radio system does not provide the receive audio while the dispatch console user is transmitting. Advanced Signaling on Trunked Radio Resources Display Radio s Unit ID The Display Radio s Unit ID feature allows a dispatch console to display the unit ID associated with an inbound radio call. Unit IDs are unique numbers assigned to each radio and dispatch console in certain types of radio systems. A radio can send its unit ID when it makes a call. The dispatch console user interface can be configured to display the unit ID of the source radio on inbound calls. This configuration is done at the local administration application. The unit ID can appear in a Received Call Stack, the Three Line Display, the Resource Header and the Activity Log window. Note that if an alias for the unit ID is available, the dispatch console will display the alias instead of the unit ID. The unit ID of a parallel dispatch console is also displayed on the dispatch console when the parallel dispatch console transmits on radio resources which are common to both consoles or when the parallel dispatch console places a call to the dispatch console. If an inbound call is received on a radio resource that does not support the concept of unit IDs, no unit ID is displayed on the dispatch console even if it has been configured to display unit IDs. Send Console s Unit ID The Send Console s Unit ID feature allows a dispatch console to send its unit ID when it transmits on a radio resource. Unit IDs are unique numbers assigned to each radio and dispatch console in certain types of radio systems. The unit ID allows the radios to display the ID of the dispatch console that is the source of the transmission. p. 282 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-87

198 The dispatch console s unit ID is sent when the dispatch console user transmits on a radio resource and when the user initiates an individual call to another dispatch console. ID Conservation The ID Conservation feature prevents dispatch consoles from consuming an inordinate amount of unit IDs in a trunked radio system. The ID Conservation feature allows a dispatch console to use a single unit ID for all the trunking talkgroup resources and individual call resources that it controls. Emergency Alarm An Emergency Alarm is sent by radio users to alert dispatch console users of a critical situation needing immediate attention. When an Emergency Alarm is received by a dispatch console, an audible indication is sounded. A visual indication is also displayed to direct a dispatch console user s attention to the specific resource with the emergency alarm active on the dispatch console. Any dispatch console user can take responsibility for an emergency by Recognizing the Emergency Alarm. All dispatch consoles are notified that the Emergency Alarm has been recognized. The audible emergency indications are typically ended once all Emergency Alarms at a dispatch console are recognized. The audible emergency indications may also be ended by the dispatch console user without recognizing the Emergency Alarm. When an emergency is over, a dispatch console can end the Emergency Alarm. All dispatch consoles are notified that the Emergency Alarm has been ended. The emergency mode persists on the initiating radio unit until it is ended by the radio user explicitly. The Emergency Alarm feature is used by radios to alert dispatch consoles of an emergency without the use of voice communication. This is generally followed by a voice transmission. Received Emergency Alarm Indications The Received Emergency Alarm Indications feature allows a dispatch console user to be quickly informed that an emergency alarm has been received on a trunked resource. The indications are audible and visual in nature. The audible indication continues until either a dispatch console has recognized the emergency alarm or the dispatch console user mutes it. The visual indication continues until the emergency alarm has been ended by a dispatch console. The Received Emergency Alarm Indications feature allows the dispatch console user to be quickly alerted that an emergency alarm has been received and to identify quickly on which resource it occurred. Emergency Recognize The Emergency Recognize feature allows a dispatch console user to assume responsibility for an emergency call or emergency alarm. When a dispatch console user recognizes an emergency, all other dispatch consoles are notified that the emergency has been recognized. When an emergency has been recognized, the audible indications for that emergency are silenced at all dispatch consoles monitoring the emergency Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 283

199 The Emergency Recognize feature is often confused with the Acknowledge feature. Recognize is used when a dispatch console user takes a specific action to assume responsibility for an emergency. Acknowledge is used when a piece of equipment (trunking controller or dispatch console) automatically sends a message to a radio telling it that its emergency message was received. Mute Tones at Single Op The Mute Tones at Single Op feature allows a dispatch console user to mute the tones associated with an emergency alarm only at his/her dispatch console. This feature does not recognize the emergency alarm, so other dispatch consoles continue to generate the emergency tones. The Mute Tones at Single Op feature is used to silence the emergency alarm tones without recognizing the emergency. This would be used in a situation where one agency is monitoring a channel that belongs to another agency. If an emergency alarm comes in on the second agency s channel, the first agency could mute the tones at their dispatch consoles without having to wait for the second agency to recognize it. Emergency End (Knockdown) The Emergency End feature allows a dispatch console user to terminate an emergency alarm. All dispatch consoles are notified that the emergency alarm has been ended and which dispatch console ended it. Call Alert The Call Alert feature lets a dispatch console or radio leave a page at an unattended radio or dispatch console. Upon returning to the radio or dispatch console, the called user knows who called. Additionally, a Call Alert can be used to trigger an activity. For instance, a Call Alert may cause a vehicle s horn to sound and its lights to flash. Typically, the page appears at a radio as a series of beeps along with the unit ID of the sender. Traditionally, at a dispatch console, the received page is presented as a series of beeps along with a visual indication of who sent the Call Alert. When a Call Alert is sent to an individual radio or dispatch console, the receiving radio or dispatch console is expected to acknowledge it automatically. A sent Call Alert can be aborted by the initiator before an acknowledgment is received. If after a period an acknowledgment is not received, the Call Alert is automatically terminated and the sender is notified that it was not successful. The Call Alert feature provides the ability for a dispatch console or radio user to contact someone who is away from their radio or dispatch console and hence cannot hear a voice message. Call Alert eliminates the need to tie up airtime trying to reach an unattended radio. If a dispatch console receives a Call Alert, the identity of the caller can be displayed as a numeric Unit ID, or an alphanumeric alias for the calling radio. Secure Trunked Radio Communication Functionality Secure Capability in the Dispatch Console The Secure Capability in the Dispatch Console feature allows radio voice messages to be encrypted and decrypted in the dispatch console itself. This feature allows the radio voice messages to be encrypted the entire time they are being transported between the dispatch console and the radio. p. 284 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-89

200 The dispatch console is capable of supporting up to four different encryption algorithms simultaneously. This allows dispatch console users to talk and listen on radio resources that have different encryption algorithms without any manual intervention or delay. Trunked radio resources (talkgroups and private calls) can be configured with the ability to work in the secure mode. Secure-capable resources on a dispatch console may be configured so they always operate in secure mode or so the user can manually change between secure and non-secure modes. The Secure Capability in the Dispatch Console feature allows conversations between a dispatch console user and a radio user to remain encrypted during the entire journey between the two users. Advanced Encryption Standard (AES) Algorithm The AES Algorithm feature allows the dispatch console and archiving interface server to process radio voice messages using the AES encryption algorithm. AES is a United States government encryption/decryption standard defined in Federal Information Processing Standard 197 (FIPS-197). The dispatch console can encrypt and decrypt voice using the AES algorithm. Secure Transmit Mode Selection The Secure Transmit Mode Selection feature allows the dispatch console user to control the secure mode of transmissions on a trunked resource. The dispatch console user can choose whether his/her transmissions on a particular trunked resource are encrypted. This feature applies to trunked resources individually; that is, different trunked resources on a dispatch console are independently configured to have or not have this feature. This feature can be configured differently for the same trunked resource on different dispatch consoles; that is, a trunked resource may have this feature on one dispatch console but not on another dispatch console. When set to the secure mode, all transmissions on that trunked resource from that dispatch console are encrypted. When set to non-secure mode, no transmissions on that trunked resource from that dispatch console are encrypted. This feature only applies to the dispatch console on which it is located. Radios and other dispatch consoles can have their secure modes set differently. Receive Cross-Mode Indication The Receive Cross-Mode Indication feature is used to indicate when an inbound (to the dispatch console) radio call is in a different secure mode than the dispatch console s setting for outbound (from the dispatch console) transmissions on a trunked resource. This helps prevent dispatch console users from responding to an inbound call in the wrong mode. Clear Audio Alert The Clear Audio Alert feature provides visual and audible indications when a trunked radio call is in the clear mode. The dispatch console can be configured to provide the indications on dispatch console transmissions, on radio transmissions received at the dispatch console or both. This alerts the dispatch console user that a call is unencrypted. Multi-Select Cross-Mode Alert The Multi-Select Cross-Mode Alert feature is used to inform a dispatch console user that there are trunked resources with different secure modes in a multi-select group. This helps prevent dispatch console users from transmitting the same audio in both secure and non-secure modes Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 285

201 This feature does not prevent the dispatch console user from having trunked resources with different secure modes in a multi-select group; it merely informs the user that this is the case. Patch Cross-Mode Alert The Patch Cross-Mode Alert feature is used to inform a dispatch console user that there are trunked resources with different secure modes in a patch group. This helps prevent the transmission of encrypted audio in an unencrypted state in a patch. This feature does not prevent the dispatch console user from having trunked resources with different secure modes in a patch group; it merely informs the user that this is the case. Key Fail Indication The Key Fail Indication feature is used to indicate when the dispatch console is unable to decrypt or encrypt a trunked radio voice message due to a problem with an encryption key. This indication is provided on the Elite Dispatch GUI status bar. Reasons for a key failure include a missing key or no keys match the key used to encode the incoming voice message. Panic Key Zeroizing The Panic Key Zeroizing feature allows all the encryption keys in a dispatch console to be erased (zeroized) with the push of a button. The button is recessed in a panel to reduce the chance of accidentally pressing it. Erasing the keys on one dispatch console has no effect on the keys at other dispatch consoles. Keyset/Indexset Selection via GUI The Keyset/Indexset Selection via GUI feature allows the dispatch console user to manually select the Keyset/Indexset used by the dispatch console. This allows the dispatch console user to transmit to radios that are using a different keyset. (The dispatch console will automatically use the appropriate keyset to decrypt audio being received from a radio, so the Keyset/Indexset Selection feature does not really have an effect on received audio.) The control for doing this is incorporated into the dispatch console s GUI so no extra devices [such as a Key Variable Loader (KVL)] are required to change which Keyset/Indexset is being used. This feature does not apply to the archiving interface server since it does not have a GUI and it does not transmit encrypted audio. Key Management via KVL The Key Management via KVL feature provides the ability to manage all the keys for a dispatch console or archiving interface server using only a KVL (key variable loader). Crosspatch Functionality Standard Patch The Standard Patch feature allows a dispatch console user to set up a communication path between two or more resources that are normally unable to communicate with each other. These could be trunked resources and/or conventional resources. When a dispatch console detects call activity on one resource in a patch group, it automatically transmits that audio to all other resources in the patch group. p. 286 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-91

202 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. Patch Auto-Restore After Resource Interruption The Patch Auto-Restore After Resource Interruption feature allows the dispatch console to provide as much patch functionality as possible during and after service interruptions in the radio system. If a service interruption occurs on a resource that is in a patch group, the dispatch console keeps the patch active with the remaining members of the patch group. The interrupted resource is shown as being in a patch pending state for the duration of the interruption. If the interrupted resource is restored to service while the patch group is still active, the dispatch console attempts to add the resource back into the patch. If a service interruption occurs that affects all the resources in a patch group, the dispatch console keeps the patch active with no members in it. Resources are shown as being in a patch pending state for the duration of the interruption. If resources are restored to service while the patch group is still active, the dispatch console attempts to add the resources back into the patch. The word attempts is used in the previous paragraphs because there are conditions outside the control of the dispatch console, which may prevent it from adding a resource to a patch. Examples of these include the resource may not be available for use or another dispatch console placed it in a patch first Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 287

203 The Patch Auto-Restore After Resource Interruption feature allows the dispatch console to provide as much patch functionality as possible after service interruptions without human intervention. This is useful for patches that are desired to be active for long periods. The combination of the Patch Auto-Restore After Resource Interruption and the Patch Auto-Start features provides a highly resilient patch service that may be used for long-term patch applications. Permanent Patch The Permanent Patch feature has been replaced by a combination of the Standard Patch, the Patch Auto-Start and the Patch Auto-Restore After Resource Interruption features. Please refer to those features for information about what they do. Patch Transmit Patch Transmit is a console feature that allows a dispatch console to initiate a transmission on all resources contained within a patch group. Patch transmit is considered a low priority transmission; its priority is less than that of all other transmit functions. A dispatch console using a higher priority transmission can take control of a resource from another dispatch console using a lower priority transmission. Note that this does not mean the higher priority transmission becomes the audio source for the patch. It only becomes the audio source for the channel(s) upon which it is transmitting. A dispatch console can only patch transmit to one patch group at a time. Note that if a dispatch console user does any type of transmission on a member of a patch group, the dispatch console will automatically transmit on all the other members of the patch group as well. While this operation does not involve the patch transmit feature, it does provide similar results. The patch transmit feature allows a dispatch console user to send a voice transmission to all members of a patch group. This can be a convenient way for a dispatch console user to inform members of a patch group when a patch has been established between resources, or when the patch group is about to be dissolved. Patch Busy Indication The Patch Busy Indication feature provides a dispatch console user with an indication that a resource is a member of an active patch group on any dispatch console in the radio system. This is important because a resource can only be a member of one active patch group at a time. Patch Reserved Indication The Patch Reserved Indication feature provides a dispatch console user with an indication that a resource is a member of an active patch group on his/her dispatch console. This is important because a resource can only be a member of one active patch group at a time. Patch Pending Indication The Patch Pending Indication feature provides a dispatch console user with an indication that a resource the user is trying to place into a patch is not available. Some reasons a resource may not be available include: It is already a member of an active patch group on another dispatch console in the radio system. It may not be affiliated with the trunking system s controller. A hardware failure may be rendering it unavailable. p. 288 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-93

204 The dispatch console will continue to monitor the status of the resource and will attempt to include it in the patch if it becomes available. Patching Op Indication The Patching Op Indication feature allows the dispatch console user to see which dispatch console patched a resource. This is useful in control rooms with many dispatch consoles and a user wants to quickly find out which dispatch console is controlling a patch. Pausing the cursor on the Patch Busy Indication on a radio resource shows which dispatch console set up the patch group. Communication System Request Rejections Resource Reject The Resource Reject feature informs the dispatch console when a requested operation, such as General Transmit, Instant Transmit, Call Alert, etc., has been rejected by the radio system. This feature provides information regarding the reason the request has been rejected by the radio system for the affected resources. Resource Reject messages differ from error messages in that a reject comes from the radio system whereas an error is generated within the dispatch console. In certain situations, a single request might result in reject messages being received for multiple resources. For example, multiple rejects might be the result of resource regrouping done by a trunked radio system. Resource Rejects are directed to the dispatch console that attempted the rejected operation. Parallel dispatch consoles do not receive the rejects. Resource Rejects provide dispatch console information as to why the radio system is not allowing an attempted action to be performed. In many cases, the reject is because of a temporary condition within the system (e.g., all resources are busy, or the target radio is involved in another operation) which does not necessarily require corrective action. In other situations, a Resource Reject message informs the dispatch console of a system problem, indicating the need for a system administrator to correct the problem in the radio system. When an action is rejected, the Resource Reject feature provides a specific reason for why the request was denied. Announcement/Intercom Functionality Selective Op Intercom via Individual Call The Selective Op Intercom via Individual Call feature allows a dispatch console user to speak privately with another dispatch console user through the dispatch consoles. This feature is based on the Trunking Individual Call feature that allows a dispatch console user and a radio user to engage in a private conversation. The user interface and operation of the Selective Op Intercom via Individual Call feature are the same as for the Trunking Individual Call feature. Please refer to the description text for the Trunking Individual Call feature for more information. The Selective Op Intercom via Individual Call feature allows two dispatch console users to speak privately with each other through their dispatch consoles. It is useful for situations where two dispatch console users need to talk with each other, but are not close enough to talk face to face Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 289

205 Group Op Intercom via Talkgroup Call The Group Op Intercom via Talkgroup Call feature allows a group of dispatch console users to speak with each other through their dispatch consoles. This feature is based on the Trunking Talkgroup Call feature. A talkgroup containing only dispatch consoles as members can be created. Any dispatch console transmitting on this talkgroup would be heard by all the dispatch consoles monitoring that talkgroup. Multiple talkgroups can be created to create different intercom groupings. This does not require any additional hardware beyond what is required for the rest of the trunking system. The user interface and operation of the Group Op Intercom via Talkgroup Call feature are the same as for the Trunking Talkgroup Call feature. Please refer to the description text for that feature for more information. The dispatch console user groupings are created by assigning trunking talkgroup to the desired dispatch consoles. All dispatch consoles that share such a resource may talk with each other. A dispatch console may be part of multiple groups. The Group Op Intercom via Talkgroup Call feature allows a group of dispatch console users to speak with each other through their dispatch consoles. It is useful for situations where a specific group of dispatch console users need to talk with each other, but are not close enough to talk face to face. All Op Intercom via Talkgroup Call The All Op Intercom via Talkgroup Call feature is identical to the Group Op Intercom via Talkgroup Call feature. The only difference is the Trunking Talkgroup Call resource appears on all dispatch consoles. Thus, all dispatch consoles can participate in the discussion. The All Op Intercom via Talkgroup Call feature allows all dispatch console users to speak with each other through their dispatch consoles. It is useful for situations where all dispatch console users need to talk with each other, but are not close enough to talk face to face. System Maintenance and Supervisory Functions Primary/Secondary Supervisor Levels The Primary/Secondary Supervisor Levels feature provides a means for establishing a hierarchy of authority between the users of dispatch consoles. The Transmit Priority Levels feature to determine the priority level of each transmission in a console subsystem uses this hierarchy. There are three levels of dispatch consoles primary supervisor, secondary supervisor and nonsupervisor: A primary supervisor is the highest level and has transmit priority over all secondary supervisors and non-supervisors. A secondary supervisor is the second highest level and has transmit priority over all nonsupervisors. A non-supervisor console is the lowest level and has no transmit priority over any other console. The primary and secondary supervisor designations are associated with users, not with physical dispatch consoles. A console subsystem can have multiple dispatch consoles of each level. The Primary/Secondary Supervisor Levels feature allows supervisory personnel to have the transmit priority necessary to carry out their responsibilities in a console subsystem. p. 290 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-95

206 Multiple Primary Supervisors The Multiple Primary Supervisors feature allows multiple dispatch console users to be designated as primary supervisors in the same radio system. This feature is useful when multiple customers are sharing a radio system and each customer wishes to have their own primary supervisor. Console Disable The Console Disable feature allows a dispatch center supervisor to send a disable command from the radio system s network manager to a particular dispatch console. Once the target dispatch console receives the disable command, the dispatch console becomes inoperable. None of the console features or resources can be used and no call activity can be initiated or received on the disabled dispatch console. In addition, all the current activity on the dispatch console is ended. For example, if there is any kind of transmission active on the dispatch console, the transmission is aborted. The resources are removed from the patch group if resources are patched by this dispatch console. 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, if a dispatch console is located in a remote site and is not being supervised, the dispatch console can be disabled. Supervisor Takeover The Supervisor Takeover feature allows a supervisor in a dispatch room to control whether or not a non-mcc 7500E dispatch console (e.g., a deskset) can access an analog conventional base station that is controlled by an MCC 7500E dispatch console. A relay is used to physically disconnect the transmit wireline pair from the non-mcc 7500E dispatch console from the station. This feature can be used while the non-mcc 7500E 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-mcc 7500E 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-mcc 7500E 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 are 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 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 291

207 Trunking Talkgroup Resource A Trunking Talkgroup Resource is capable of having a single 16-character alias associated with it. The aliasing system is capable of providing an alias for each Trunking Talkgroup Resource in the radio system. The Alias feature allows dispatch console users to identify Trunking Talkgroup Resources by names rather than numbers. This allows dispatch console users to operate the dispatch console easily and efficiently. Trunking Announcement Group Resource A Trunking Announcement Group Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Trunking Announcement Group Resource in the radio system. The Alias feature allows dispatch console users to identify Trunking Announcement Group Resources by names rather than numbers. This allows dispatch console users to operate the dispatch console easily and efficiently. Trunking Individual Call Resource A Trunking Individual Call Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Trunking Individual Call Resource in the radio system. The Alias feature allows dispatch console users to identify Trunking Individual Call Resources by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Conventional Channel Resource A Conventional Channel Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Conventional Channel Resource in the radio system. The Alias feature allows dispatch console users to identify Conventional Channel Resources by names rather than numbers. This allows dispatch console users to operate the dispatch console easily and efficiently. Conventional Channel Frequency Selection Control A Conventional Channel Frequency Selection Control is capable of having multiple 16 character aliases associated with it. Each frequency can have a unique alias within the control. The aliasing system is capable of providing an alias for each Conventional Channel Frequency Selection Control in the radio system. The Alias feature allows dispatch console users to identify frequencies by names rather than numbers. This allows dispatch console users to operate the dispatch console easily and efficiently. Conventional Channel PL Selection Control A Conventional Channel PL Selection Control is capable of having multiple 16-character aliases associated with it. Each PL code can have a unique alias within the control. The aliasing system is capable of providing an alias for each Conventional Channel PL Selection Control in the radio system. p. 292 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-97

208 The Alias feature allows dispatch console users to identify PL codes by names rather than numbers. This allows dispatch console users to operate the dispatch console easily and efficiently. Unit ID A Unit ID is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Unit ID in the radio system. The Alias feature allows dispatch console users to identify Units by names rather than numbers. This allows dispatch console users to operate the dispatch consoles easily and efficiently. Aux I/O Resource An Aux I/O Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Aux I/O Resource in the radio system. The Alias feature allows dispatch console users to identify Aux I/O Resource by names rather than numbers. This allows dispatch console users to operate the dispatch consoles easily and efficiently. Security Management User Accounts and Passwords Radio system user accounts are used in radio systems to provide access to resources, simplify the use of certain features and assist in ensuring security. The radio system allows an administrative user to create accounts for the various users of the system and assign different capabilities and access rights to them. One such account is for the users of the console subsystem. A dispatch console requires that a valid radio system user account name and password be entered before it can be used on the radio system. The dispatch console validates the user account name and password with the radio system s network manager and allows the user to access only the resources for which the user has access rights. This also applies to third party applications that use the dispatch console s API. Note that these radio system user account names and passwords are in addition to any user account names and passwords required to log into the Windows operating system on the dispatch console PCs. Agency Partitioning The radio system provides users with the ability to create groups of users and assign system resource access rights to those groups. This allows users to control which users have access to which resources in the radio system. This is how agency partitioning is supported in the radio system. Agency partitioning allows radio systems, which are used by multiple agencies, to be configured in such a way that the users from each agency only have access to their agency s resources. This helps keep an agency s resources available for its users and it prevents unauthorized people from making any changes to the agency s resources. The console subsystem participates in this agency-partitioning scheme. Access rights given to user accounts manage the various parts of the console subsystem. A dispatch console checks with the network manager for the access rights assigned to the user and allows access to only the resources for which the user has access rights. This also applies to third party applications that use the dispatch console API Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 293

209 The radio system network manager checks the access rights assigned to the user wishing to configure the console subsystem and allows access to only the portions of the console subsystem for which the user has access rights. Network Security Enhancements The radio system s IP transport network is protected against viruses, hackers and other unauthorized activities by a set of enhancements that are applied to each product connected to the network. The dispatch consoles support these enhancements. Fault Management Hardware Element Monitoring The radio system s fault manager monitors and reports the status of all the hardware elements in the console subsystem. This allows the console subsystem to be fault managed from the same point at which the rest of the radio system is fault managed. The specific hardware elements that are monitored are the dispatch console and any networking equipment that supports the console elements. Each of these hardware elements monitors critical internal hardware sub-elements and reports their status. This allows a failure within a hardware element to be detected. The hardware elements in the console subsystem are also periodically polled to request their status. This allows a failure of an entire hardware element to be detected. Software Process Monitoring The console subsystem monitors and reports the status of all the critical software processes running on the various hardware elements that comprise the subsystem. Changes in the status of software processes on a device are recorded internally. Qualified technical personnel in troubleshooting problems with the console subsystem intend these internal records primarily for use. Status changes, which are useful for understanding the console subsystem s overall status, are also reported to the radio system s fault manager. If a failure of a software process is detected, self-healing actions may be initiated to correct the failed process. Refer to the Self-Healing Actions feature for more information. Network Link Integrity Monitoring The network elements, which are used by the console subsystem, are monitored in the same manner as the network elements for the rest of the radio system. Any failures in these links are reported to the radio system s fault manager. Automatic Discovery of Console Elements The console subsystem supports the automatic discovery of console elements by the radio system s fault manager. This saves the user from having to manually gather and enter the necessary data into the radio system fault manager. The radio system fault manager automatically discovers all network elements (both Motorola Solutions-manufactured elements and Motorola Solutions-supported third party elements) that are included in the system and adds them to the map of network elements in a topologically descriptive manner. Outputting of Monitoring Results (SNMP) The console subsystem supports the reporting of fault status to the radio system s network manager via the SNMP protocol. p. 294 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-99

210 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. This configuration application is used in conjunction with the Elite Admin application. The configuration application is used to define what is potentially available at each console subsystem element. The Elite Admin application is used to define exactly which resources are available to the dispatch console user and how they are presented to the dispatch console user. Automatic Distribution of Configuration Changes When a change is made to the configuration information for the console subsystem, the radio system s network manager automatically distributes the changed information to all the console subsystem elements that require it. As-Configured Documentation The configuration management system generates documentation that allows the user to verify the configuration that was entered and provide information necessary for installation of the console subsystem. The following information is contained in the documentation generated by the configuration management system: Console subsystem information - A listing of which dispatch consoles have been created in the console subsystem. Dispatch console information - A listing of the peripherals, peripheral port assignments, capabilities and audio destination assignments for each dispatch console. Conventional channel gateway information - A listing of the channels, channel capabilities, channel connection information and main/alternate designation for each conventional channel gateway. Trunked resource information - A listing of the type of and capabilities for each trunked resource controlled by the console subsystem. Conventional resource information - A listing of the type of and capabilities for each conventional resource in the console subsystem. Aux I/O information - A listing of the type of capabilities for each auxiliary input or output in the console subsystem Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 295

211 Date and Time Date and Time Synchronization The console subsystem synchronizes its time and date information with the radio system s time source via Network Time Protocol (NTP) on the radio system s IP network. This ensures that the time displays at the dispatch consoles and any time stamps on events in log files are accurate. Adjustments for 12/24-hour format, different time zones and Daylight Savings Time are made automatically if the operating system on the dispatch consoles and other console subsystem elements is configured to support them. Time Display The dispatch console provides the user with the ability to display the current time on the user interface. The time is synchronized with the radio system s time source. 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 made automatically if the operating system on the dispatch consoles is configured to support them ASTRO25 System Failure Mode Analysis Motorola Solutions ASTRO25 trunking networks have three modes of operation for increased reliability. The normal mode of operation is Wide Area Trunking. In the event of multiple component failures that lead to system disruption, the system is equipped to continue operation in two reduced feature operational modes: Site Trunking and Failsoft. Due to higher bandwidth demands of a distributed architecture approach, IP networks must be segmented. This results in multiple single points of failure, which could disable 1, 2, or even 3 channels (up to 60% of Columbia's channels). In contract, our Simulcast design eliminates any Grade of Service impacting events, maintaining 100% capacity in the event of a failure. The following pages include a detailed description of each of these operational modes. Please refer to the Narrative of Failure Analyses in Section for a comprehensive analysis of the possible infrastructure failure scenarios and the system redundancy for mitigating each scenario Wide Area Trunking Wide Area Trunking is the ASTRO25 system s normal mode of operation. Wide Area Trunking implies that the Fixed Network Equipment is operating properly. All Simulcast cells and ASTRO25 Repeater Sites are communicating with the Zone Core. Subscriber units automatically roam between the various network RF cells. Talkgroup calls occur in the appropriate RF cells if users are distributed throughout multiple cells. Data applications are properly assigned channels for communication between the subscriber units and the host application Site Trunking Site Trunking is the first failover mode of operation. Individual RF cells within a network are impacted by Site Trunking. In multiple RF cell systems, one RF cell can be in Site Trunking, while the rest of the system remains in Wide Area Trunking. Site Trunking implies that the Simulcast Prime Site Controller or the ASTRO25 Repeater Site has lost connectivity with the Zone Core. Talkgroup calls initiated in the RF cell that is in Site Trunking will only be broadcast in that RF cell. Dispatch p. 296 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-101

212 consoles use control stations or the operators use portable radios to communicate on a Site Trunking RF Cell. Console priority is not available in Site Trunking. Data applications are not available on a site in Site Trunking and will have to be reinitiated once the system reverts to Wide Area Trunking. Radios detect if a site is in Wide Area Trunking or site trunking. Radio models with a display will indicate to the user when the site is operating in site trunking. The radio alternately displays the selected talkgroup and Site Trunking. Depending on how the system and user equipment are programmed, subscriber units will try to roam to an RF cell that is in Wide Area Trunking Failsoft by Talkgroup Subsystem/Site Failsoft is the final fallback means of communication if a site no longer maintains Wide Area or Site Trunking operation. Multiple failures have to occur for the system to enter Failsoft. Failsoft impacts individual RF cells within a network. In multiple RF cell systems, one RF cell can be in Failsoft, while the rest of the system remains in Wide Area Trunking. The subsystem goes into Failsoft mode in any of these scenarios: The site controllers are not functioning properly When all control channels are disabled or malfunctioned When only one channel is enabled Failsoft operation provides communications in conventional mode via repeaters/base radios in order to maintain vital communications. In an IP multisite Simulcast subsystem in subsystem-wide Failsoft, received audio is routed to the comparator for voting and redistributed to all of the sites for Simulcast transmission. The subscriber s operation in Failsoft mode is determined by the subscriber s programming. A subscriber can be programmed to behave in the following manner: Failsoft by control channel operation - The subscriber first scans for alternate control channels outside the multisite subsystem, then scans the control channel frequencies for Failsoft data. Failsoft by working group - The subscriber looks for Failsoft data on a pre-programmed frequency after a scan for alternate control channels outside the multisite subsystem is unsuccessful. If the subscriber cannot decode Failsoft data on the pre-programmed frequency, the subscriber then scans the control channels in the Simulcast subsystem for Failsoft data. Dispatch Consoles use control stations or the operators use portable radios to communicate on a Site Trunking RF cell. Console priority is not available in Site Trunking. Data applications are not available on a site in Failsoft and will have to be reinitiated once the system reverts back to Wide Area Trunking Narrative of Failure Analyses Motorola Solutions has designed the system to be inherently fault-tolerant to ensure reliable communications for the end users. Redundant components and network component distribution ensure maximum system availability for the end users. Site and system component failures are detected by the unified event manager (UEM) at the master site and will be reported to the appropriate personnel. This section demonstrates the redundancy and self-healing features of Motorola Solutions system design by explaining required loss and recovery scenarios for the proposed system. The failure mode analysis contained here is comprehensive and represents Motorola Solutions proposed design. We have provided in response to this section a full failure analysis narrative and block diagrams for each major component failure possible for the proposed system, including the following scenarios: Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 297

213 Master Site Failure Scenarios Zone Controller failure at main master site core Network component failure at main master site core Entire main master site core or critical components of main master site Link failure between/dispatch/simulcast prime site and the master site Simulcast Prime Site Failure Scenarios Simulcast prime site controller Both simulcast prime site controllers at main prime site Comparator at prime site Single gateway (or site link) to master site Failure of both site gateways (or site links) to the master site Single Ethernet switch Prime site reference (GPS) Prime site main site access gateway to remote sites Simulcast Remote Site Failure Scenarios Simulcast remote site main gateway (or site link) Either simulcast remote site gateways or site links Simulcast remote site main Ethernet LAN switch Simulcast remote site main and redundant Ethernet LAN switches Simulcast remote site single control channel or voice channel Dispatch Site Failure Scenarios Dispatch operator position Ethernet switch at dispatch site Main site gateway or site link at dispatch site Failure of either site gateways or site links at dispatch site Conventional channel gateway at dispatch site Failure of Aux I/O server at dispatch site Master Site Failure Scenarios As shown in Figure 4-26, the proposed radio system includes a main master site and DSR master site. The Zone controllers provide the connectivity between the prime simulcast sites and the console dispatch sites. p. 298 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-103

214 Figure 4-27: Proposed Master Site Network Diagram Failure of Zone Controller at Main Master Site Core (as shown in Figure 4-27) Figure 4-28: Failure of Zone Controller at Main Master Site Core Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 299

215 Scenario: Result: Protection: Detection: Failure of Zone Controller Each master site core consists of a Zone Controller. If a failure of the active Zone Controller occurs, operations will switch over to the standby Zone Controller at the DSR site. As the switchover process takes place, the system will temporarily enter site trunking mode. Wide area trunking will be restored when the switchover process is complete (typically less than 30 seconds). Any and all calls generated after automatic switchover to the backup master will not observe any change of service. Once the primary master site is restored to operation, the remote sites will not switch back automatically unless there is a subsequent failure at the backup master site. This prevents unnecessary switching should the restoration of service be transient or intermittent. DSR Master Site Alarm on Network Management Terminal (UEM) Network Component Failure at Main Master Site Core (as shown in Figure 4-28) Figure 4-29: Failure of Network Component at Main Master Site Core p. 300 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-105

216 Scenario: Result: Protection: Detection: Failure of Core LAN Switch or Core Router or Gateway Router Motorola Solutions offers redundant master site system configuration, called Dynamic System Resiliency (DSR). In a system that implements DSR, there are two master sites, a main and backup. Both sites are live on the system. Failure of the key components at the active master site will result in the automatic switch-over of control to the backup master site. During a switch over, RF and dispatch sites will automatically switch over to the backup master site. As the switchover process takes place, the system will temporarily enter site trunking mode. Wide area trunking will be restored when the switchover process is complete (typically less than 30 seconds). Any and all calls generated after automatic switchover to the backup master will not observe any change of service. Once the primary master site is restored to operation, the remote sites will not switch back automatically unless there is a subsequent failure at the backup master site. This prevents unnecessary switching should the restoration of service be transient or intermittent. DSR Core Router, DSR Core LAN Switch, DSR Gateway Router, Redundant Links Alarm on Network Management Terminal (UEM) Failure of Master Site Critical Components (both Zone Controllers or Core LAN Switches or Core Routers or Gateway Routers- shown in Figure 4-29) Figure 4-30: Failure of Master Site Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 301

217 Scenario: Result: Protection: Detection: Failure of Entire Master Site Motorola Solutions offers redundant master site system configuration, called Dynamic System Resiliency (DSR). In a system that implements DSR, there are two master sites, a main and backup. Both sites are live on the system. Failure of the key components at the active master site will result in the automatic switch-over of control to the backup master site. During a switch over, RF and dispatch sites will automatically switch over to the backup master site. As the switchover process takes place, the system will temporarily enter site trunking mode. Wide area trunking will be restored when the switchover process is complete (typically less than 30 seconds). Any and all calls generated after automatic switchover to the backup master will not observe any change of service. Once the primary master site is restored to operation, the remote sites will not switch back automatically unless there is a subsequent failure at the backup master site. This prevents unnecessary switching should the restoration of service be transient or intermittent. DSR Master Site, Redundant Links Alarm on Network Management Terminal (UEM) Link Failure between Dispatch/Simulcast Prime Site and the Master Site (shown in Figure 4-30) Figure 4-31: Failure of Site Link to Main Master Site Scenario: Result: Protection: Detection: Failure of the site link from a Dispatch site or Simulcast Prime site to the master site If the Multicast/Simulcast Prime/Dispatch site loses communications with the zone controller at the master site due to site link failure, it will automatically try an alternate path to access that Zone controller. Redundant Site Links Alarm on Network Management Terminal (UEM) p. 302 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-107

218 Simulcast Prime Site Failure Scenarios (Geo-Redundant Prime) Motorola Solutions proposes to Columbia County a main simulcast subsystem with Geo-Redundant simulcast prime site redundancy. The proposed simulcast subsystem is comprised of a main simulcast prime site co-located with the main Core RF site, associated simulcast remote sites and a redundant prime site geographically located at different RF site. The County s Geo-Redundant simulcast subsystem is shown in Figure 4-31 below for reference. Figure 4-32: Proposed Geo-Redundant Simulcast Prime Site Network Diagram Simulcast Prime Site Controller (as shown in Figure 4-32) Figure 4-33: Geo-Redundant Main Prime Site: Simulcast Prime Site Controller Failure Scenario: Failure of the Simulcast Prime Site Controller at Prime Site Result: Motorola Solutions has provided redundant simulcast prime site controllers (GCP 8000) at the main simulcast prime site. Failure of the active controller will result in automatic switchover to the redundant controller. The entire system remains in the simulcast wide area trunking mode from the primary prime site. The failure is transparent to all voice system users. Dispatch console operation remains unaffected. Protection: Redundant Prime Simulcast Controllers, Spare Controller Modules Detection: Alarm on Network Management Terminal (UEM) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 303

219 Both Simulcast Prime Site Controllers (as shown in Figure 4-33) Figure 4-34: Geo-Redundant Main Prime Site: Both Simulcast Prime Site Controllers Failure Scenario: Result: Protection: Detection: Failure of Both Primary and Redundant Simulcast Prime Site Controllers In the unlikely event that both the active and the redundant main simulcast prime controllers fail at the main simulcast prime site, this will result in automatic switchover to the Geo redundant prime site controller. Subscriber radio units in the field affiliated to the simulcast site will go into fail-soft mode of operation. Subscriber units affiliated to the simulcast site and in fail-soft mode can communicate to each other on their designated channel frequency. They can communicate with the dispatch users, if the dispatch users have a backup control station affiliated to the simulcast site. Restoration to wide area trunking is typically less than 30 seconds. Geo Redundant Prime Simulcast Controller, Spare Controller Modules Alarm on Network Management Terminal (UEM) p. 304 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-109

220 Comparator at Prime Site (as shown in Figure 4-34) Figure 4-35: Geo-Redundant Main Prime Site: Comparator Failure Scenario: Result: Protection: Detection: Failure of Simulcast Comparator at main Simulcast Prime Site The system will recognize the failure of the comparator at the main prime site and activate the duplicate comparator on the Geo redundant prime site. The failure is transparent to all voice system users. Dispatch console operation remains unaffected. Duplicate comparators on the Geo redundant prime site Alarm on Network Management Terminal (UEM) Prime Site Failure of Single Gateway (or Site Link) to Master Site (as shown in Figure 4-35) Figure 4-36: Geo-Redundant Main Prime Site: Single Gateway Failure (or Site Link) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 305

221 Scenario: Result: Protection: Detection: Failure of Simulcast Prime Site Gateway or Site Link to the master site If the primary site gateway or site link to the master site fails, the redundant site gateway will take over. The switchover is automatic. The failure is transparent to all system users. The traffic is rerouted through the redundant site gateway. Redundant Simulcast Prime Site Gateway, Redundant Site Links Alarm on Network Management Terminal (UEM) Both Site Gateways (or Site Links) to the Master Site (as shown in Figure 4-36) Figure 4-37: Geo-Redundant Main Prime Site: Primary and Redundant Gateway (or both Site Links) Failure Scenario: Result: Protection: In the unlikely event that either both the prime site gateways (primary and redundant) or both the Site Links fail, this will result in the simulcast sub-system dropping into the Site Trunking mode. The entire system remains in the simulcast trunking mode from the primary prime site. The failure is transparent to all voice subscriber users except for the Site Trunking visual and/or audible alert. Dispatch console operation uses backup control stations. Geo Redundant Prime Simulcast Controller, Spare Gateway Alarm on Network Management Terminal (UEM) p. 306 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-111

222 Single Ethernet Switch (as shown in Figure 4-37) Figure 4-38: Geo-Redundant Main Prime Site: Ethernet LAN Switch Failure Scenario: Result: Protection: Detection: Failure of a main Simulcast Prime Site Ethernet LAN Switch The failure of the Ethernet LAN switch at the main simulcast prime site will result in the automatic switchover to the Geo redundant prime site. The system remains in the wide area mode and the failure is transparent to all users. Geo Redundant Prime Simulcast Controller, Spare Controller Modules Alarm on Network Management Terminal (UEM) Main Prime Site Reference (GPS) (as shown in Figure 4-38) Figure 4-39: Geo-Redundant Main Prime Site: Failure of Simulcast Prime Site Reference (GPS) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 307

223 Scenario: Result: Protection: Detection: Failure of main Simulcast Prime Site Reference (GPS) The primary site reference is designed with a rubidium and crystal Oscillator and redundant power supplies. If the rubidium oscillator fails then the crystal oscillator will take over and continue to provide a reference for the comparators and site controllers. If a power supply fails then the redundant power supply will take over. If the entire primary site reference fails, then the controllers and comparators will continue to run on the internal reference for up to four hours. If the primary site reference (TRAK) is down for over four hours then the system will switch to the Geo redundant prime site. Geo Redundant Prime Simulcast Controller, Spare Controller Modules Alarm on Network Management Terminal (UEM) Main Prime Site Main Site Access Gateway to Remote Sites (as shown in Figure 4-39) Figure 4-40: Geo-Redundant Main Prime Site: Failure of Main Site Access Gateway to Remote Sites Scenario: Result: Protection: Detection: Failure of Main Site Access Gateway to Remote Sites At the Simulcast Prime site if the main site access gateway to the remote simulcast sites fails, the redundant site access gateway will take over. The switchover is automatic. The failure is transparent to all system users. Redundant Simulcast Prime Site Gateway Alarm on Network Management Terminal (UEM) Simulcast Remote Site Failure Scenarios For illustration purposes, a LAN Switch is shown. The Switch is an internal part for the ESS Cabinet LAN system. p. 308 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-113

224 Simulcast Remote Site Main Gateway (or Site Link) (as shown in Figure 4-40) Figure 4-41: Failure of Simulcast Remote Site Main Gateway (or Site Link) Scenario: Result: Protection: Detection: Failure of Simulcast Remote Site Main Gateway or Site Link The simulcast subsystem employs redundant site gateways and redundant site links to connect the simulcast remote sites to the simulcast prime site. Failure of main site gateway/ site link at a simulcast remote site will result in automatic switchover to the redundant site gateway/site link. The entire system remains in the simulcast wide area trunking mode. The failure is transparent to all system users. Standby Simulcast Remote Site Gateway, Redundant Site Links Alarm on Network Management Terminal (UEM) Either Simulcast Remote Site Gateways or Site Links (as shown in Figure 4-41) Figure 4-42: Failures of Either Simulcast Remote Site Gateways (or Site Links) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 309

225 Scenario: Result: Protection: Detection: Failure of both Simulcast Remote Site Gateways (or Site Links) In the unlikely event that both simulcast remote site gateways or both the site links fail, the failed remote site will be removed from the simulcast cell. The remaining simulcast remote sites within that cell will remain unaffected. The coverage from the failed simulcast remote site will no longer be available, possibly reducing the coverage footprint. Network management alarms and software download capability will be lost for the failed simulcast remote site. All other simulcast remote sites within the cell will have network management alarming capability. Subscriber units on the field served by the failed simulcast remote site may experience a momentary loss of coverage, before they affiliate to another wide area RF site. If they are out of range of any RF coverage, the subscribers will lose access to the system. Spare Simulcast Remote Site Gateway Alarm on Network Management Terminal (UEM) Simulcast Remote Site Main Ethernet LAN Switch (as shown in Figure 4-42) Figure 4-43: Failure of Simulcast Remote Site Main Ethernet LAN Switch Scenario: Result: Protection: Detection: Failure of Simulcast Remote Site Main Ethernet LAN Switch Failure of the main simulcast remote site Ethernet LAN switch will result in automatic switchover to the redundant Ethernet switch. The entire system remains in the simulcast trunking mode. The failure is transparent to all system users. Redundant Simulcast Remote Site Ethernet switch Alarm on Network Management Terminal (UEM) p. 310 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-115

226 Simulcast Remote Site Main and Redundant Ethernet LAN Switches (as shown in Figure 4-43) Figure 4-44: Failure of Simulcast Remote Site Main and Redundant Ethernet LAN Switches Scenario: Result: Protection: Detection: Failure of Simulcast Remote Site Main and Redundant Ethernet LAN Switches In the unlikely event that both the main and redundant simulcast Ethernet LAN switches fail, the failed remote site will be removed from the simulcast cell. The remaining simulcast remote sites within that cell will remain unaffected. The coverage from that remote site will no longer be available, possibly reducing the coverage footprint. Network management alarms and software download capability will be lost for this remote site. All other remote simulcast sites within the cell will have network management alarming capability. Subscriber units on the field served by the failed simulcast remote site will experience a momentary loss of coverage, before they affiliate to another wide area RF site. If they are out of range of any RF coverage, the subscribers will lose access to the system. Spare Remote Site Ethernet LAN switch Alarm on Network Management Terminal (UEM) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 311

227 Simulcast Remote Site Single Control Channel or Voice Channel (as shown in Figure 4-44) Figure 4-45: Failure of Single Control Channel or Voice Channel Scenario: Result: Protection: Detection Failure of a Single Control Channel or Voice Channel Motorola Solutions trunking systems provide up to four possible control channels in a simulcast cell. If the currently active control channel fails, another channel automatically takes over and the failed control channel is automatically taken out of service. All other channels within the simulcast cell remain unaffected. The simulcast cell remains in the wide-area trunking mode. The failure is transparent to all system users. Dispatch console operation remains unaffected. In a trunking system, multiple channels inherently provide redundancy for simulcast remote sites. The failure of one voice channel will be transparent to all system users. The failure of a voice channel base station will result in the zone controller removing that channel from service, resulting in some reduced channel capacity. Any calls in progress on the failed channel will be lost and on the next push-to-talk, radio traffic will be restored on another channel. All other channels in the simulcast cell remain unaffected. The entire system remains in the wide area trunking mode. Dispatch console operation remains unaffected. Multiple potential control and voice channels Alarm on Network Management Terminal (UEM) p. 312 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-117

228 Dispatch Site Failure Scenarios Dispatch Operator Position (as shown in Figure 4-45) Figure 4-46: Failure of Single MCC7500E Console Position Scenario: Result: Protection: Detection: Failure of a Single Dispatch Operator Position The failure of a dispatch operator position would result in that particular dispatcher moving to another operator position or reverting to a fallback control station or portable radio. All other dispatch terminals operate normally and remain unaffected. The entire system remains in the wide area trunking mode. Multiple Consoles, Backup Control Stations Console User Detection, Console Diagnostics Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 313

229 Ethernet Switch at Dispatch Site (as shown in Figure 4-46) Figure 4-47: Failure of Ethernet LAN Switch at Dispatch Center Scenario: Result: Protection: Detection: Failure of a Dispatch Center Ethernet LAN Switch Each dispatch site is designed with at least two Ethernet LAN switches that connect the operator positions to the network. The console positions and other critical components at the dispatch sites are distributed equally amongst the Ethernet LAN switches at the site. The MCC7500E consoles connect to both switches. If an Ethernet switch fails, all MCC7500E consoles will continue to operate via the redundant LAN switch. Multiple console Positions, Multiple Ethernet LAN switches, Spare Ethernet LAN Switches, Backup Control Stations Console user detection, console diagnostics p. 314 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-119

230 Main Site Gateway or Site Link at Dispatch Site (as shown in Figure 4-47) Figure 4-48: Failure of Main Dispatch Gateway Scenario: Result: Protection: Detection Failure of Main Dispatch Site Gateway or Site Link The system employs redundant site gateways and redundant site links at dispatch sites. Failure of main site gateway/site link at a dispatch site will result in automatic switchover to the redundant site gateway/site link. The entire system remains in the wide trunking mode. The failure is transparent to all system users. The traffic is rerouted through the redundant site gateway-backup master site link and the interzone link to the main master site. Redundant Site Gateway, Spare Site Gateway, Redundant Site Links Alarm on Network Management Terminal (UEM) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 315

231 Failure of Either Site Gateways or Site Links at Dispatch Site (as shown in Figure 4-48) Figure 4-49: Failure of Main and Redundant Dispatch Site Gateways Scenario: Result: Protection: Detection Failure of both Dispatch Site Gateways or Site Links In the unlikely event that both Site Gateways and Site Links should fail, the dispatch site would lose wide area connectivity through the master sites. Trunking operations would continue via backup control stations connected to the console dispatch position. Conventional system communications would continue unaffected through conventional stations that are connected to the local console network LAN, as the conventional site controller takes over site operation. Spare Site Gateway, Backup Control Stations, Conventional Site Controller Alarm on Network Management Terminal (UEM) p. 316 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-121

232 Conventional Channel Gateway at Dispatch Site (as shown in Figure 4-49) Figure 4-50: Failure of Conventional Channel Gateway Scenario: Result: Protection: Detection Failure of Conventional Channel Gateway The failure of a conventional channel site gateway at a dispatch site causes the dispatch users the loss of the conventional resources connected to the failed gateway. The dispatchers may have to communicate with the subscribers served by the failed conventional channels using alternate conventional or trunked resources. Channels Distributed over Multiple CCGW, Spare Conventional Channel Site Gateway Console User Detection, Alarm on Network Management Terminal (UEM) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 317

233 Failure of Aux I/O server at Dispatch Site (as shown in Figure 4-50) Figure 4-51: Failure of Aux I/O Server Scenario: Result: Protection: Detection Failure of Aux I/O server The failure of an Aux I/O at a dispatch site causes the dispatch users to lose the ability to control the external devices connected to the Aux I/O server. Spare Aux I/O server Alarm on Network Management Terminal (UEM) p. 318 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-123

234 This page intentionally left blank Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 319

235 4.5 ASTRO25 FIXED NETWORK EQUIPMENT DESIGN The following sections describe the proposed ASTRO25 system components in detail Zone Core Columbia County, Florida The ASTRO25 master/dsr zone core is the main control point for the proposed communications system. The zone core contains the computing backbone for the system and all the components necessary for controlling voice calls and data messages within the proposed system. In addition, the zone core provides the hardware and software components used for network management and system configuration. The zone core for the County has been sized to provide for the current and future needs of its user base, with the capability to support up to 25,000 subscriber radios as required by the RFP. The system architecture is designed with inherent fault distribution, ensuring that a single point of failure will not cause the complete disruption of communications. The ASTRO25 architecture ensures that voice operation is maintained despite any single component failure anywhere on the network. In the case of a fault, the system can reroute the IP voice and data packets among the various redundant router configurations and notify the supervisor/network management terminal of the fault. Redundant Zone Controllers Redundant zone controllers will be geographically separated into the master and DSR sites. The zone controller is a software application that provides centralized control for call processing and mobility management functions in an ASTRO25 system. The zone controller application is responsible for processing calls, managing audio paths, controlling zone infrastructure and providing services to subscribers and dispatch consoles. The zone controller application resides on the HP DL380 dual virtual management servers and runs RedHat Linux in a VMware ESXi virtual machine. The dual virtual management servers at the master/dsr zone core contain the zone controllers and NM applications. Virtualization allows multiple virtual machines, with heterogeneous operating systems, to run in isolation, side-by-side on the same physical machine. Each virtual machine is allocated CPU, memory and storage resources used by the operating system and application associated with the virtual machine. Virtual machines are encapsulated into files, making it possible to rapidly save, copy and provision a virtual machine. Full systems (fully configured applications, operating systems, BIOS and virtual hardware) can be moved from one physical server to another, for high-availability maintenance and continuous workload consolidation. These two physical servers provide the processing for the redundant zone controllers, along with NM and reporting. These applications are distributed for reliability. The zone controller operates in a redundant configuration. The LAN switch is used to switch system resources between the zone controllers and provide high availability call management within the zone. While the zone controllers are powered and enabled at the same time, only one is actively participating in call processing tasks at any one time. The redundant zone controller configuration provides protection against a single point of hardware or software failure that results in the loss of wide area trunking until the zone controller is repaired or recovers automatically. The redundant zone controller remains in the standby state as long as the active zone controller does not report a malfunction that causes a switchover. p. 320 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-125

236 Zone Core LAN Switch Configuration The zone core equipment includes a set of Core LAN switches (Figure 4-51) that are the aggregate of all the Ethernet interfaces for all servers, clients and routers at the zone core. Additional LAN switches are used for remote site access aggregation and in other capacities within the proposed ASTRO25 system, including at the prime site, the dispatch centers and each of the remote RF sites. Figure 4-52: Core LAN switch 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. ASTRO25 System Licenses Many ASTRO25 system features are offered through a licensing structure giving the County the ability to purchase only those features that are needed. The proposed system is configured with sufficient licenses for up to 25,000 individual radio user IDs to accommodate for current and future expansion needs. The MCC 7500E console system includes licenses for 20 console positions. This will support the 9 proposed MCC 7500E consoles, the 9 MCC 7100 mobile laptop consoles, the MCC7100 Proxy server/maintenance console and the Archiving Interface Server. If Columbia County expands the dispatch console, or adds additional dispatch console locations later, the County may purchase additional licenses for dispatch console positions ASTRO25 Prime Site Design The Prime site acts as a control and digitized audio center for the simulcast subsystem. The proposed simulcast prime site will be geographically separated between the EOC and the CCSO sites, where it will be co-located with the DSR master site and a remote RF site at the CCSO site and with a remote RF site at the EOC site. The prime site links route IP packets containing control and audio information from the prime site to each simulcast remote site GCP 8000 Site Controller The GCP 8000 site controller is designed for use in ASTRO25 trunking systems. The GCP 8000 controller provides call processing and acts as a site link between the simulcast subsystem and the zone controller. The GCP 8000 is capable of supporting up to 36 voice paths and up to 30 simulcast sub-sites. The GCP 8000 controller communicates with interconnected ASTRO25 infrastructure elements, such as the GTR 8000 base radio subsystem and the GCM 8000 comparator, which are also designed to be P25 compliant. The GCP 8000 controller is implemented in a fully redundant configuration with two controllers. The redundant (standby) controller automatically takes over site link or site control operations when the active GCP 8000 controller has failed. Communications between the active and standby controllers are configured through an Ethernet link. Channel status information will be kept consistent between Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 321

237 the active and standby site controller to assure that accurate channel capability information will always be sent to the zone controller. In addition to the redundant controllers at the prime site, there will be a third controller at the redundant prime site, which will take over control operations automatically in the event of a failure of both controllers at the prime site Prime Site Routers The prime site router provides a WAN interface that carries all of the traffic between the active and backup prime site to the zone core including voice, control and network management traffic. The router provides direct IP packet network management connectivity for the remote sites to the zone core as well as: Traffic prioritization - The router applies the correct prioritization marking to the packets leaving the site. Fragmentation - The router fragments large IP packets as necessary. Dynamic Host Configuration Protocol (DHCP) service - This service allows the technician with a properly configured computer running on a Windows operating system to connect to the LAN at the site. Used with the NMS, the prime site router provides a proactively managed system and a means of receiving and reporting failure alarms, all of which increase router availability. Motorola Solutions has designed this system with redundant prime site routers, split between the prime and redundant prime sites GCM 8000 Channel Comparators The GCM 8000 comparator is a band-independent device that acts as a subsystem-wide signal collector, voter and distributor. The GCM 8000 comparator is designed for use in ASTRO25 IP simulcast trunking systems. With multiple base stations operating on the same frequency, it is possible for multiple RF sites to receive a single field unit transmission. The GCM 8000 compares the various voice traffic signals and interprets and selects the best audio samples and assimilates an enhanced audio signal for simulcast broadcasting. By simultaneously transmitting the enhanced audio signal from multiple sites within the system, both coverage and signal quality are improved. The geographic redundant prime site configuration, proposed for the County, consists of redundant comparators at the primary simulcast prime site and at the secondary simulcast prime site Prime Site Ethernet LAN Switches A LAN switch is required to connect GCM 8000 comparators and GCP 8000 controllers to the prime site router. Motorola Solutions has designed this system with redundant prime site Ethernet switches, split between the prime and redundant GEO prime sites TRAK 9100 Time and Frequency Standard The prime sites include a redundant GPS-based time and frequency standard that provides a frequency/timing device for synchronized simulcast transmissions. In addition, the GCM 8000 comparator will receive timing (1pps) information from the GPS. Each simulcast remote site will also utilize a GPS to provide the frequency/timing data needed to allow synchronization of simulcast p. 322 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-127

238 transmissions. Each TRAK has redundant power supplies and Rubidium oscillators clocked by dual GPS antenna systems Redundant Remote Site Routers Remote site routers provide an interface that routes all of the IP network traffic to and from the prime site for communication with the zone core. The site routers provide the following function for the network management packets: Layer 3 routing - This restricts local traffic from accessing the microwave system and forwards important voice and data information to the prime site. DHCP service - This service allows the technician with a properly configured computer running Windows to connect to the LAN at the site. Used with the system s NM, the remote site router provides a proactively managed system as well as a means of receiving and reporting failure alarms Ethernet LAN Switches The simulcast sub-site LAN switch performs two main functions at the simulcast remote site. The switch provides a 10BaseT LAN interface for the GTR expandable site subsystem and a 10BaseT port for the site router. The service technicians using CSS software use a switch port to gain access at the site to service the site and access the system s GUIs to maintain the system. DHCP service allows the technician with a properly configured computer running Windows to connect to the LAN at the site. The site router will assign the computer running Windows an IP address that will allow the computer access to the ASTRO25 network GTR8000 Expandable Site Subsystem (ESS) The P25 remote sites use GTR 8000 ESS (Expandable Site Subsystem) racks, a space-efficient, single-rack design that integrates up to six GTR 8000 base radios, power supply modules, redundant GPB 8000 Reference Distribution Modules, redundant Ethernet LAN switches, redundant site gateways, transmit combiner and receiver multi-couplers. A diagram of the GTR 8000 ESS is shown in Figure This platform was chosen to provide additional autonomy for the system. The GTR 8000 platform requires low power, minimized rack space and utilizes an IP-based transport layer, which allows increased backhaul flexibility. Subscriber audio is received and packetized by the stations. The internal GPB 8000 provides both LAN routing and GPS services for each station at the site. The packetized audio is routed via the GPB 8000 and the local redundant site routers to the Ethernet microwave backhaul network. The microwave routes the audio to the active prime site to be voted Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 323

239 Figure 4-53: Simulcast GTR 8000 ESS Layout The built-in six-channel transmitter combiner prepares the output signals from all the RF carriers in the GTR 8000 ESS for transmission on a single antenna. The cavity combiner has built-in singlestage circulator at each input. Each input to the combiner has a tuning and locking mechanism for each cavity to provide on-site frequency selection/tuning and to prevent unintentional detuning. Circulator loads are on the back of the combiner on a common heat sink. Since the system is five channels of 700 MHz repeaters required, the transmit output from each GTR 8000 ESS is combined with a standalone GTR base radio for the sites that require an 800 mutual aid repeater through a phasing harness and diplexer. Subscriber audio is received and packetized by the stations. The GPB 8000 included in the GTR 8000 provides both LAN routing and GPS services for each station at the site. The packetized audio is routed via the GPB 8000 and the local redundant site routers to the microwave backhaul network. The microwave routes the audio to the active prime site to be voted. The proposed IP simulcast subsystems do not require site controllers at the remote sites in order to operate under control of the GCP 8000 site controllers at the simulcast prime sites. Simulcast site controllers control the simulcast site over Ethernet IP links. This reduces equipment cost and eliminates a potential point of failure. In addition, each site uses redundant site gateways and p. 324 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-129

240 reference distribution modules for network transport, switching and GPS reference functions. All equipment has alarm outputs as required to deliver status information to the network management system IV&D System Design The ASTRO25, P25 trunking system supports Motorola Solutions integrated mobile data, Integrated Voice and Data (IV&D). Our ASTRO25 IV&D capability enhances the Project 25 system by adding packet data capability to subscriber units. This system enhancement will provide voice and data communications without the extra expense of installing and maintaining separate systems for voice and data RF Infrastructure and Subscriber Units ASTRO25 IV&D uses the same infrastructure components and subscriber units for Project 25 voice communications. This will allow the system to allocate resources to voice and data communications, depending on user demands GPRS Gateway Support Node The GPRS GGSN is a special purpose router that provides various services in support of trunked data operation. Among those are separation of IP address spaces between the trunked radio system network and external customer networks, DHCP address management and tunneling of radio system packets into and out of customer networks. The GGSN provides General Packet Radio Service for GSM cellular subscribers. The ASTRO25 system uses the device to provide connectivity between the trunked radio system network and other private or public networks. The proposed system requires only one GGSN (per system).the GGSN interfaces between the Motorola Solutions radio network and Customer Enterprise Networks (CEN). The GGSN tunnels data-grams from a CEN(s) to the appropriate PDG, which ultimately passes the datagram on to a specified subscriber unit operating on the closed Motorola Solutions radio network. A GGSN does the following: Isolates the Motorola Solutions radio network IP address plan from the IP plans of any CENs to which it enables a connection. It either sources or provides access to DHCP services. It can support VPN connections into external networks Packet Data Gateway (PDG) A Radio Network Gateway (RNG) and a Packet Data Router (PDR) make up a PDG. See the following sections for more details Packet Data Router 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 Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 325

241 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 MCC 7500E Dispatch Console To take full advantage of all the capabilities of the ASTRO25 trunked digital voice system and to support the wide variety of dispatch needs, Motorola Solutions offers the MCC 7500E IP console system. The MCC 7500E console subsystem tightly integrates to the ASTRO25 digital voice system. The MCC 7500E is our ASTRO25 IP console and the most advanced offering in Motorola Solutions line of radio dispatching products. Installation of the state-of-the-art MCC 7500E follows recognized industry standards of police and fire dispatch centers. The new console system will meet public safety dispatching needs for the County. The various hardware elements that which comprise the dispatch console are illustrated in Figure 4-53 and described in the following sections. Figure 4-54: MCC 7500E IP console system Workstation Computer The dispatch console uses a customized Motorola Solutions-certified PC running the Microsoft Windows 10 operating system. The PCs used in ASTRO25 systems have a small form factor Audio Interface Module The MCC 7500E console inherits the following capabilities from the MCC 7100 console. These are listed here because they are different than the capabilities of the current MCC 7500 console. It uses the same speakers, headset jacks, microphone, footswitch and audio interface module (AIM) as the MCC 7100 console. Both the analog versions and the USB versions of these devices are supported. p. 326 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-131

242 It is capable of being deployed outside of the ASTRO 25 system s radio network infrastructure (RNI). It supports the AES, DES-OFB and ADP encryption algorithms. It does not support the DES- XL, DVP-XL, DVI-XL, CFX-256 and Localized Encryption encryption algorithms. The AIM provides the connections for the following items: Speakers Headset jacks Microphone Footswitch Headset Desktop Gooseneck Microphone The dispatch console is capable of supporting a single desktop gooseneck microphone. The desktop microphone contains a microphone cartridge on a flexible shaft and two buttons in its base. One button controls the General Transmit feature and the other controls the Monitor feature Headset Jack A MCC 7500E dispatch console is capable of supporting up to two headset jacks. A headset jack allows a dispatch console user to use a headset while operating the dispatch console. The headset jacks ship from the factory configured for 6-wire headsets. When a headset is plugged into a headset jack, the selected receive radio call audio is typically removed from the speaker(s) and routed to the headset earpiece. The radio resource may be configured to output receive audio through the speaker and not to the headset earpiece when a headset is in use. If two headsets are connected to a dispatch console, the same radio audio appears in the earpieces of both of them. When an external telephone set connected to a dispatch console s external telephone port and is taken off hook while a headset is connected to a dispatch console, the selected radio audio is removed from the headset earpiece and routed to the appropriate speaker. The received telephone audio is routed to the earpiece of the headset connected to the first headset jack. The microphone of the headset connected to the first headset jack becomes live and its audio is routed to the external telephone set. This allows the dispatch console user who is using the headset connected to the first headset jack to talk and listen on the telephone set in a hands free full duplex mode. A headset connected to the second headset jack cannot may only be used with the radio channels on the dispatch console Dispatch Speaker Each speaker on a dispatch console contains unique audio; that is, an audio source cannot appear in multiple speakers at a single dispatch console. The speaker is designed for use near computer monitors or mounted on a computer monitor. It contains an amplifier, which provides a maximum of two watts of power Footswitch The footswitch allows a dispatch console user to access the General Transmit feature or Monitor feature without using his/her hands. This is useful in situations where the dispatcher's hands are not free for activating those features Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 327

243 Backup Operations and Failure Indications Columbia County, Florida In the event that a failure occurs in the connection between the MCC 7500E dispatch console and the radio system, backup operation will be on the proposed APX 7500 consolettes. The console positions will indicate a failure of this connection, by displaying a red X over the resources in the console positions. p. 328 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-133

244 This page intentionally left blank Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 329

245 4.6 ANALOG CONVENTIONAL EQUIPMENT DESIGN Columbia County, Florida The analog conventional radio designed to support mutual aid operations for Columbia County consist of the following major components: GTR 8000 Base Station/Repeater GGM8000 Conventional Channel Gateway (CCGW) This section of the system description contains descriptions of these components GTR 8000 The Motorola Solutions GTR 8000 Base Radio and GPW 8000 receiver are designed to meet Columbia County s current and future requirements for both analog and Project 25 solutions. The GTR 8000 Base/Repeater station and GPW 8000 receiver are designed to maximize channel up-time, simplify system migrations and enable smaller, more efficient site design while minimizing the cost of ownership to the customer. GTR 8000 stations and GPW 8000 receivers are designed so that upgrades, migrations and conversions can be completed with only software installations. Information Assurance/Network Security updates, migrations to new system releases and system migrations from analog to digital, conventional to trunking and from 25 khz Analog to 6.25 khz TDMA Digital can be completed with a software download. Bot the GTR 8000 and GPW 8000 are modular by design and are installed in the same chassis, which makes it easier to repurpose a station by changing modules rather than replacing the entire chassis. The GTR 8000 and GPW 8000 equipment chassis is shown in Figure Figure 4-55: G Series Equipment Motorola Solutions is the industry leader in simulcast system solutions with more mission critical systems fielded and operational than any other LMR vendor systems provider. The conventional GTR 8000 Base Radio hardware consists of four major Field Replacement Units (FRUs): the transceiver, the power amplifier, the power supply and the fan module. G-series site equipment products are very flexible and designed to support today's robust site designs. G-series site equipment products provide the flexibility to upgrade to future functionality through software downloads. The GTR 8000 Base Radio includes features such as: Compact and integrated hardware utilizing three rack unit chassis enables efficient use of site space. Software Defined Radio allows for upgrades to future functionality through software update. Modular software design coupled with the Software Download Manager simplifies future upgrades and routine servicing. p. 330 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-135

246 Functionally separate modules - Field Replacement Units (FRU) - are hot-swappable allowing servicing and replacement without system down-time while minimizing channel down-time. Designed for ease of service including significantly reduced alignment servicing Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 331

247 4.7 REGIONAL INTEROPERABILITY Columbia County, Florida Interoperability is a critical requirement for any public safety communications solution. Columbia County can utilize several key interoperability features in our ASTRO25 solution: P25 Phase 1 FDMA and Phase 2 TDMA interoperability Interoperability with the neighboring counties radio network Interoperability with non-trunking users via existing Conventional Analog infrastructure We understand Columbia County s need to interoperate with other agencies and have addressed that need in the proposed solution. The proposed system infrastructure includes the capability to support FDMA users and to support Phase 2 TDMA users. The ASTRO25 system supports the capability of interfacing conventional analog radio resources to the Zone Core with use of Conventional Gateways. Motorola Solutions has supplied Conventional Channel Gateways (CCGWs) at the radio sites to interface the proposed 800MHz mutual aid and Conventional systems to the P25 network. Motorola Solutions has also supplied CCGWs at the Columbia County PSAP to interface backup control stations, as well as additional existing conventional radio resources. This will allow dispatchers to communicate with those agencies not using the P25 trunked system, by selecting the proper resource on the console and will permit the ability to for Columbia County P25 users to interoperate with those agencies via a patch put in place by the dispatchers Levels of Interoperability SAFECOM, a United States Federal organization focused on defining and encouraging interoperability for radio communications systems, recognizes six levels of interoperability. These interoperability levels range from simple, basic solutions such as simply swapping radios, through fully integrated shared standards-based systems Interoperability with Surrounding Jurisdictions The County s RFP divides the surrounding jurisdictions and agencies into two categories: those agencies that the County requires interoperability solutions with and those agencies with which the County desires, but does not specifically require interoperability. Please see Table 4-11 for a detailed breakdown of each jurisdiction s system type, interoperability solution and resulting SAFECOM level of interoperability. Several of the surrounding counties and agencies detailed in RFP have the potential of communicating on a direct, radio-to-radio basis with Columbia County and vice versa, either through a system using the same frequency band or, in cases where the system uses a different frequency band, using a multiband radio. For example, if a user with a 700 MHz portable radio with trunked capability entered Columbia County, this user could communicate on the County s system directly with other radios, as long as their radio is both authorized and programmed into Columbia County s system. Similarly, users with Columbia County radios entering into these neighboring counties could also communicate by direct radio-to-radio communications on P25 Phase 1 or Phase 2 networks. With just Motorola Solutions proposed 700 MHz solution and radios, the County s users will have direct radio-to-radio over-the-air interoperability with local and neighboring jurisdictions such as Lowndes County, GA and Alachua County. Several of the neighboring jurisdictions maintain systems in VHF conventional systems. Direct radioto-radio interoperability and roaming on these systems is achieved using P25 multi-band radios, such as those in Motorola Solutions APX8000 series of mobiles and portables. If direct radio-to-radio p. 332 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-137

248 interoperability is not achievable with these non 700/800 trunked systems, inter-system communications are still available. Conventional base stations or control stations can be connected to the dispatch consoles that operate on these non 700/800 systems by using Conventional Channel Gateways (CCGW). These conventional stations can patch to Columbia County talk groups once they are connected to the dispatch console so that these users can communicate. Other technologies such as Digital Mobile Radio (DMR), IDAS or NXDN or MotoTRBO can also interface to the CCGWs at local 4-wire level. Table 4-11 details the specific interoperability solutions and interoperability levels provided for each of interoperability partners indicated in the County s RFP. We detail these methods of interoperability and assume the County s existing interoperability control stations will be used. Table 4-11: Interoperability Solutions for Columbia County Interoperability Partners Jurisdiction System Type Interoperability Solution Interagency within Columbia 700 MHz P25 P25 Radios County Lowndes County, GA 800 MHz P25 P25 Radios / ISSI Alachua County 800 MHz P25 P25 Radios / ISSI Suwannee County VHF Conventional Multi-band Radios / Control Stations Baker County SLERs & VHF Conventional 800 MHz Mutual Aid & Multiband Radios / Control Stations SLERs Agencies 800 MHz EDACs 800 MHz Mutual Aid Lake City, FL VHF Kenwood NXDN Swap Radios / Control Stations Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 333

249 4.8 SUBSCRIBERS Radio Equipment Requirements APX Series Radios Overview We are pleased to present Columbia County with our industry-leading flagship APX series of ruggedized public safety radios. The APX series incorporates many new features key to ensure the safety of the County s users, including further audio quality enhancements, ruggedization, intuitive displays and controls and features critical to ensuring the safety of first responders and citizens throughout the County. Motorola Solutions APX series radios are the next generation radio offering, extending a history of over 85 years of providing high-quality mission-critical devices to public safety organizations around the world. Many of Florida s first responders contributed input into the design and engineering of the APX series radios. Concept to finished product is completed in our Engineering Headquarters in Plantation, FL. We work very closely with local public safety organizations to improve radio communications. We have proposed radios that exceed the County s specifications. Public Safety radios are configured for P25 TDMA, GPS, IV&D, Bluetooth, AES Encryption, Multi-key, OTAP, OTAR, Link Layer Radio Authentication and include a three-year factory warranty. Local government radios are configured with P25 TDMA, GPS, IV&D, OTAP, Link Layer Radio Authentication and include a three-year factory warranty. Columbia County Radio Subscriber Department Matrix Public Safety Local Government Mobile Radios Portable Radios Mobile Radios Portable Radios APX4500 APX8500 APX6000 APX6000XE APX8000 APX1500 APX900 APX Portfolio Quality Differentiators APX radios take audio quality to the next level with advanced noise reduction algorithms and DSP audio processing in conjunction with an enhanced noise-cancelling microphones designed to achieve optimum audio intelligibility in the presence of background noise. Our radios provide significant industry-leading technology advantages for our public-safety customers; helping to ensure safer outcomes for our first-responders and in turn improved publicsafety response for Columbia County. APX radios offer the following feature advantages versus various competitor radios: APX Audio Design Advantages Adaptive Dual Mic Noise Cancelling Technology allows for noise cancellation regardless of radio positioning Adaptive Noise Reduction Algorithms that perform in Analog & Digital Operation Adjustable Audio Parameters to optimize performance in various noise environments p. 334 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-139

250 Significantly lower audio distortion for better intelligibility Automatic Gain Control for analog noise suppression: Non-AGC Portables may experience interoperability problems in mixed fleets due to fluctuating audio levels. APX Feature Advantages P25 Radio Authentication FIPS Level 3 Certified Encryption Module when used with AES encryption Demonstrated P25 Phase 2 TDMA operation Mission Critical Wireless Bluetooth technology enables fast, simple and secure encrypted pairing with any Bluetooth enabled APX APX features Superior Roaming, Fastest Site Switching and ability to specify Site Priority (most/least preferred) Integrated Voice & Data with Text Messaging capabilities in P25 Digital operation Integrated GPS in both portables and mobiles Man-Down automatic emergency notification in the event of user injury + GPS notification of user location upon Man-Down alarm Motorola Solutions OTAP advantages: Voice priority during OTAP: Voice communications take priority over data calls so that data transmissions are paused during voice communications and resume once the voice communication has ended. Additionally, the OTAP process does not inhibit voice transmissions. Presence Notification + Batch Programming Allows for Dynamic IP addresses are issued for each subscriber so that they do not have to be manually entered in order to remotely program a radio. User selected reboot following OTAP data sessions so that critical voice calls are not interrupted. Pause/resume data feature with differential write: Permits OTAP data package to pick up where it left off when interrupted by voice communications, additionally only changes to the radio s codeplug are transmitted to the radio competing solutions must start over when interrupted + must be write entire software package regardless of similarity to existing software. Data roaming: Users can roam and maintain data session P25 CAP certified on Motorola Solutions infrastructure and a wide variety of third party infrastructure Personnel Accountability applications with APX portables for fire-scene/swat team staff safety within buildings More Programmable Front Buttons, Side buttons Home & Data Buttons and Navigation Pad than competing radios Support of both Tactical + Trunking OTAR Customizable Channel Announcements RFID option APX Ergonomics Advantages Ergonomic spacing between controls Large, accessible emergency button Oversized ergonomic knobs for ease of use for users with gloves 3-Position Toggle and 2-Position Concentric Switches Top Display for easy viewing of channel/zone information, even when on the user s hip Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 335

251 Large Color LCD Display for Better Viewing and Enables Intelligent Lighting Radio Profiles/Intelligent Lighting Bar Shielded PTT button Universal PTT is textured with locater ridges, enabling quicker blind operation in high-stress situations Multiple keypad/display options in APX models to permit customizing to agency use cases Light weight Blind Operation/Operate by feel APX Ruggedization Advantages Gorilla Glass TM Lens Tempered glass for displays which provides a wider viewing angle, plus greater scratch and heavy impact resistance than competing radios, plus prevents distorted view with polarized lenses APX Endoskeleton Design Provides Improved Submersibility and Ruggedness for Internal Components MIL Spec Conformance with best-in-industry shock, submerged water and scratch resistance IP ratings up to IP 68 Enhanced (2M submersion for 4 Hours) Conformance to Motorola Solutions Internal 12M specifications which are even more stringent than MIL Spec Motorola Solutions Accelerated Life Tests APX RF Performance Advantages APX radios significantly outperform competing radios in key RF metrics ensuring superior talkin/talk-out capability. Our best-in-class RF specifications for better performance in challenging/fringe coverage include: Intermodulation Distortion/Rejection (Higher db better performance): APX hardware is optimized to reduce Intermodulation Distortion with a spec that is 2 times better than some competitors This dramatically increases the radios coverage performance in high RF traffic environments (Cities/Urban Centers) Sensitivity (Lower the μv better performance): Lowest possible signal strength that a radio can intelligibly detect in a given environment (the lower the (μv) number the better) Allows the radio to receive signals in difficult coverage areas such as inside buildings Selectivity/Adjacent Channel Rejection (Higher db better performance): Radio s ability to hear only the voice traffic from the desired channel and reject other signals that are very close to that frequency Specification helps considerably when operating near other transmitters, especially in urban environments with high RF traffic Audio Distortion (Lower the % distortion better performance): Measurement of the amount of audio distortion produced at a given output power level Less distortion equals clearer/crisper voice being heard from the radio especially at high audio volume FM Hum and Noise (Higher db better performance): Measurement of the radio noise floor of both Transmitter and Receiver Lower noise floor of the radio means greater the likelihood that a low-level audio signal will come through, such as when the talker is whispering. p. 336 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-141

252 APX Advanced Data Features Motorola Solutions offers a large number of advanced data features to enhance the usability of APX radios. The following graphic summarizes a handful of these data features. The Motorola Solutions APX Advanced Data solution set and features provide the following unique capabilities within the P25 radio industry: 200 Character free-form text messaging Send messages to text groups Choose from 150 pre-defined Quick-Access messages Store-and-forward message delivery System supports up to 20,000 active users Up to 50,000 outbound text messages per hour Integrated GPS Capability The entire APX family of portable and mobile radios provides County users the ability to locate and track each field unit from a central location. The integrated GPS receiver in the APX transmits the outdoor location of an individual or vehicle to map-based location software that will interface with the County s CAD system. POP25 Over the Air Programming (OTAP) APX radios have the ability to provide the County with the functional and cost benefits of Motorola Solutions Programming-Over Project 25 (POP25) over-the-air programming (OTAP) technology. POP25 functionality reduces the time, effort and costs needed to update radio functionality by allowing radios configuration to be accessed and updated over the air. Text Messaging Option Text messaging provides freeform and canned messaging between field users and dispatch operators. This enables selected field users to not only communicate with one another and with dispatch Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 337

253 operators via voice transmission, but also through discreet texts. Information (such as addresses, license plates and phone numbers) communicated out via text messaging results in fewer repeat voice communications improving efficiency. Motorola Solutions APX two way radios support Talk Group Text Messaging, a new messaging service that uses data packets transmitted in the hang time of normal radio communications to pass broadcast data to all radios on a talk group. This enables a broadcast text message to be sent from our MCC7500Es with instant messaging, eliminating delays with traditional sequential methods. This feature is only offered with Motorola Solutions APX radios and infrastructure. Outdoor Location Solution Option Motorola Solutions' Outdoor Location Solution is available on the proposed ASTRO25 Trunking Integrated Voice & Data (IV&D) System. It uses Global Positioning System (GPS) Satellites to provide the location of personnel and vehicles, which feed to a map-based location application to provide dispatch operators with an invaluable tool for managing and tracking personnel and resources. The ability to locate users in a mission critical situation dramatically increases user safety while improving resource allocation and responsiveness. Motorola Solutions APX two-way radios transmit their location information automatically when emergency is activated either by the user or via the Mandown feature. The APX radio can also be polled by the system or be programmed to send a location update based upon speed, siren or light activation, or crossing a Geo Fence boundary. ASTRO Outdoor Location Server: Intelligent Middleware (IMW) Option The available Intelligent Middleware (IMW) application acts as a gateway for the location, telemetry and presence information from the ASTRO radios and transfers data to back office applications. It simplifies the integration process for developers by receiving in disparate GPS protocols and translating them into a unified protocol out to the third party application. Additionally, it allows for intelligent routing of messages to the devices and thus lowers traffic over the network. ASTRO Presence Option The Presence functionality within IMW provides the presence and absence information of subscriber radios to any compatible data applications located in the Customer Enterprise Network (CEN). It interfaces with data applications and subscriber radios utilizing User Datagram Protocol/Internet Protocol (UDP/IP). This allows the dispatcher to know whether a subscriber unit is powered on or off or located somewhere within the radio network. Location on PTT APX radios are able to provide Location on PTT where radios can send location updates when making a PTT call. Typical cadence based GPS has a defined polling from anywhere from 30 seconds to 2 minutes based upon data network throughput. The delay in getting these updates can mean not knowing exactly where a user is an emergency. In contrast, Location on PTT provides immediate location updates each time the radio is PTT d, either during an emergency call or a routine voice communication, by using data capacity in the packets of the voice call. Location on PTT enables sending current location of APX Subscriber to the mapping application at every PTT press. p. 338 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-143

254 Allows location information to be sent from the transmitting radio to the system whilst the radio is transmitting on a trunked voice channel Applies to non-emergency and emergency dispatch calls A PTT will send last known location (with timestamp) for up to 30 minutes after GPS signal is lost; after that it sends no data This feature is only available when using an APX subscriber on an ASTRO25 system. APX Interoperability The APX family of portable and mobile radios are designed for today s Phase I and Phase II P25 trunking standards, digital and conventional analog standards and are backwards compatible with Motorola Solutions SMARTNET, SmartZone and SmartX systems. APX multi-band radios can operate on 700/800 MHz, VHF and UHF frequencies to enable instant interoperable communications for improved coordination, response and first responder safety. In mission critical situations, agencies from different jurisdictions often operate on different frequency bands requiring personnel to carry two radios in order to communicate with one another. With dual/all-band APX portable and mobile radios, the County s users and agencies can purchase one radio for instant communication over multiple frequency bands. This eliminates the need for field users to carry multiple radios and reduces the amount of maintenance and installation of equipment. APX Compliance to Standards Motorola Solutions is the industry leader in providing industry standard P25 interfaces to our products and features, which provide seamless communications to our public safety partners. Motorola Solutions recognizes the importance of P25 standards development and follows the P25 standard documents to ensure interoperability of our system and subscriber equipment with system and subscriber equipment of other P25 compliant manufacturers. Motorola Solutions believes that a rigorous and standardized approach to verifying interoperability, for which the P25 Compliance Assessment Program (CAP) was created, best serves the entire public safety community. Moreover, Motorola Solutions has been an active leader in P25 standards specifications and testing processes bringing our protocol and systems interoperability expertise to the P25 industry and community. Motorola Solutions ASTRO25 network and APX subscribers conform to all applicable P25 specifications as outlined in Motorola Solutions P25 Conformance documents and P25 CAP Summary Test Reports published on the DHS Science and Technology First Responder s website ( The results of the tests are documented in Motorola Solutions Project 25 Compliance Assessment Program Summary Test Reports published on the DHS Science and Technology First Responder s website ( Motorola Solutions APX Technology - Details APX Series Vocoder Audio Engineering Design Principles Our audio engineering design begins with Digital Signal Processor (DSP) technology, with added custom high-power loudspeakers and precise acoustic microphones to achieve outstanding noise cancelling, exceptional loudness and clarity and unparalleled intelligibility for mission critical communications. Our APX series vocoders use the new AMBE+2 Vocoder per the P25 Phase 2 standard Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 339

255 P25 vendors utilize the IMBE or the AMBE+2 vocoders from DVSI AMBE+2 is a new vocoder and is required for all new P25 Radios AMBE+2 Comes with Noise Suppression Algorithm IMBE and AMBE+2 are fully compatible APX Durability Durability is central to the design of Motorola Solutions radios For example, due to the way the battery slides into the frame of the radio instead of simply clipping onto the back, Motorola Solutions APX portable radios can survive larger drops and not lose power. In addition to standardized testing, Motorola Solutions has meticulously engineered these radios to survive the harshest of durability and environmental tests, including numerous drops onto concrete with the same radio, vibration, extreme temperature fluctuations, humidity, electric discharge, repeated button presses, screen impacts and more. Sequential tests are performed with the same radio having to go through and pass all tests before a passing grade is achieved. All this cumulates into a rugged radio that the County s first responders can rely on no matter the circumstances. Our public safety radios meet applicable Military Specifications 810, C, D, E, F and G. Using MacroBlend housing material, they are designed to survive severe shock and vibration and exposure to damaging environments such as temperature shock, salt fog, UV radiation, dust, blowing rain and electrostatic discharge (ESD). Our radios are tested and exposed to extreme conditions to simulate years of abuse. Verification that the radios still work after they are exposed to the environment is confirmed with functional and parametric testing. Our testing standards and methods include: Military Specification MIL-STD 810 C, D, E, F, G European IP specs Motorola Solutions internal 12M specifications Motorola Solutions Accelerated Life Tests Our internal 12M specifications are more stringent than industry-standard testing. For example, Military Specifications for a drop test calls for the unit to be dropped onto a plywood surface. Our drop tests utilize a steel landing surface, which increases the severity of the test. It is Motorola Solutions procedure that each test unit should be subjected to every environmental test, rather than using a different unit for each test. This ensures that our radios perform to specification regardless of the amount and type of abuse they receive. We go far beyond standard durability testing and perform a large suite of APX Accelerated Life Tests on each model subscriber radio. A subset of these tests include: Temperature Cycle (-30 to +60 C/3 Days) Temperature Shock (-40 to +85 C/2 Hours) Portable and Mobile Vibration 40G Crash Test for Mobile Mounting Electrostatic Discharge Solar Radiation (120F/Vehicle Dash/8 Hours) Portable Drop (4 Feet/Steel Plate/All Sides/64x) Steel Ball Drop (1 Meter) Water Immersion (2 Meters/2 Hours) p. 340 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-145

256 Salt Fog Dust Chamber (MS Limestone, 2 Hours) Driven Rain (60 Kmph) Truck Bed Packaging Vibration and Drop Test (Freeze/6 Sides/8 Corners) Motorola Solutions performs rigorous testing and subjects each model radio to unrealistically harsh conditions for one reason to ensure that the Columbia County s first responders can trust their radio to perform when they need it most APX Advanced Hardware Features Motorola Solutions offers a large number of standard and configurable hardware features to enhance the usability of APX radios for the County s users. Listed below are a few APX Hardware Features: GPS Location Integrated GPS receiver can transmit the outdoor location of an individual or vehicle to map-based location software. Motorola Solutions APX series radios feature GPS internal to the portable radio users do not depend on an external RSM for GPS to function. Enlarged Buttons Enlarged and ergonomic emergency button, PTT button, display and keypad controls. Increased spacing between controls increases ease of use for users. The optional XE series provides robustness and ergonomics with glove use. Color Display Resists scratches, wear and tear and tested for durability against cracks. Optimized to provide contrast without glare and provide increased viewing from angles. Radio Authentication Provides an extra, secure level of verification every time a radio registers onto a system Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 341

257 Mission Critical Wireless A unique Bluetooth solution provides an encrypted link to high performance accessories and applications to support different mission critical environments. Supports commercial off the shelf (COTS) and personal area network (PAN) devices. Our APX series radios include Bluetooth functionality for the County s users. No additional costs are required for the County s users to utilize Bluetooth functionality APX Advanced Software Features Motorola Solutions offers a large number of standard and configurable software features to enhance the usability of APX radios for Columbia County s users. A handful of these software features are summarized below. 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. Intelligent Lighting Motorola Solutions APX radios can offer a high resolution display that uses color and lighting to indicate radio mode, potential emergencies, or specific events. Intelligent lighting is a standard feature that enables users to see critical information at a glance, regardless of the amount of ambient lighting. Text Messaging Provides a freeform or canned messaging solution for efficient and discreet send/receive of messages to and from subscribers or dispatch operators. Unified Call List Consolidates all call lists underneath one unified list so you can easily access all information associated with a particular contact. p. 342 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-147

258 Voice Announcement Users can navigate through channels, talkgroups and zones in the radio while an audible, prerecorded voice file provides a description of the selected channel or zone. Voice Announcement is a standard feature on all model radios. P25 TDMA Capable More users can be added to the system without the needs for additional frequencies or infrastructure with twice the voice capacity. Multiband Operation Multiple frequency bands supported with best-in-class transceiver specifications and performance. Seamless Scan Seamless scanning of multiple protocols including FDMA and TDMA systems and multiple RF bands. Site-Selectable Alert Continuous tones sent to alert sites of evacuation of sites, vehicle stops, fire-hall alerting, or other pre-determined actions APX End-to-End Voice Encryption The Motorola Solutions APX family of radios utilize the Motorola Solutions Advanced Cryptographic Engine (MACE). The MACE has the capability to not only store the County s encryption keys but will also protect those keys from being accessed by unauthorized users through physical or electronic means. This capability allows the APX Family of Radios to meet Federal Information Processing Standard Publication (FIPS) encryption standards FIPS Level 3 and FIPS 197. The radios support multi-algorithm Project 25 and legacy encryption capabilities, including AES and DES / DES-XL / DES-OFB / DVP-XL / ADP for increased interoperability with other systems. The system s secure endpoints provide encryption and decryption services: consoles, logging interfaces and field radio units. Communications remains completely secure between the source and the destination. No decoding of information occurs at any other intermediate point along the communications path, ensuring a much higher level of security. Consoles and subscribers receive encryption keys and that is the only place the audio is decrypted Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 343

259 To increase the effectiveness of encryption, Columbia County s users have the ability to be able to update encryption keys while radios and their users can stay in the field. Motorola Solutions overthe-air rekeying (OTAR) feature offers the County s users the benefit of real-time, ongoing security for deployed APX subscribers APX End-to-End Data Encryption Option The optional Encrypted Integrated Data (EID) feature adds security to data sent between a radio and an agency data application (e.g. data server, wireless applications, GPS location updates, etc). In other words, any packet data flowing to or from a radio are ciphered and then deciphered in the radio and Customer Enterprise Network (CEN) premises. This solution ensures that agency data sent wirelessly is secure and immune to compromise throughout the entire route, secured using AES or other selected APX encryption algorithm from end to end APX Transmitter and Receiver Performance Motorola Solutions APX portables and mobiles offer industry-leading transmitter and receiver performance specifications. The result is simple increased coverage and better audio for end users. Paired with a Motorola Solutions trunked simulcast radio system, the County s users will have uncompromising coverage and audio performance from APX subscribers. APX Mobile Control-Head Interface Advantages Quick & easy to operate Siren Controls, Pursuit Knob, Light Switches and PA Button Mission critical display lens is resistant to high force impacts competing solutions using resistive touch-screens require a soft top layer which is much more vulnerable to wear and tear and can be easily damaged by sharp edges Large Programmable One Touch Consolidated Action Buttons Quick & Easy Brightness, Night Mode and Covert Mode controls Concave/Convex Integrated DEK Buttons enable easy Blind Operation Tri-color Backlighting (Green, Orange & Red) for Intelligent Lighting Superior IP 56 ratings for better water resistance than competing mobile control head interfaces p. 344 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-149

260 Motorola Solutions O5 Control Head provides 5 programmable soft key buttons and 5 scrollthrough menus enable up to 24 total programmable soft keys + 4-way navigation button Motorola Solutions O7 Control Head provides 4 programmable soft key buttons and 5 scrollthrough menus enable up to 24 total programmable soft keys + 4-way navigation button + DTMF keypad w/pre-configured Siren/Lights/PA/Gun Lock controls APX Variants: XE (Extreme Edition) Series Product Advantages The XE Mission Extreme feature addition to the APX radio line provides Fire Departments with the level of ruggedization and survivability needed in the especially harsh environments seen by Fire first responders. Motorola Solutions has included several key new innovative features to enhance personnel safety APX XE Portable Radios The APX XE series of radio solutions provides extreme rugged and ergonomic design with innovative features developed specifically for the fire market to enhance personnel safety in extreme environments Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 345

261 Fire-Centric Audio Enhancements New Extreme One Sided Audio Profile: A unique audio profile with noise reduction algorithms and filters specifically designed for the most challenging of noise environments Enhanced Dual Microphone noise-cancelling Adaptive and fast acting dual-sided design that allows effective noise reduction regardless of what microphone the user is talking into Loudest Audio Output with least distortion Large 1Watt Rated Speaker that delivers clarity 50% louder than typical P25 Radios Fire-Centric Ergonomic Enhancements Protective Bumper Ring Exaggerated Knobs and Controls PTT/Side Button design changes for Improved Gloved Operation: Larger Ridge/Increased Texture Larger programmable side buttons Rubber over mold for improved grip Redesigned speaker grill for improved water porting Larger emergency button Taller top display for larger fonts Video Demonstrations of APX XE Series Performance The following URL provides a video presentation showing the advantages of APX XE series radio equipment with compelling live demonstrations of APX audio performance: Solutionssolutions.com/video.aspx/Motorola Solutions-s-apx-xe-remote-speakermicrophone/ In an effort to deliver optimal intelligible audio in the presence of high background noise, the use of Best Practices as defined by the International Association of Fire Chiefs (IAFC) along with optimal Customer Programming Software (CPS) audio settings in the radio, have also shown to be very beneficial in delivering improved communications. The following URL provides additional best practices for Fire agency users with Motorola Solutions APX XE series radios, which were presented to the International Association of Fire Chiefs: Solutionssolutions.com/video.aspx/say-it-loud-and-clear/ APX Accessories Motorola Solutions not only invests in the R&D of our Radios, but Motorola Solutions compliments the radios with our investment and care in designing our accessory fleet. We develop and design with the intent to meet exceed the specific needs of both fire and law enforcement environments. Many Southern Florida first responders gave input to the conceptualization, design and creation of the accessories Remote Speaker Microphones (RSMs) Motorola Solutions APX RSMs and PSMs deliver audio that is clearer, easier to understand and up to 50% louder than XTS-series RSMs because they have the same speaker found in our APX portable radios for the best-in-class accessory audio available. p. 346 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-151

262 Some RSMs feature leading-edge IMPRES technology, which communicates with the APX radio to help suppress ambient noise, improve voice intelligibility and amplify loudness even in noisy situations and difficult weather. Columbia County s users can rely on Motorola Solutions RSMs to carry on a conversation clearly even with traffic rushing by or pumper trucks running. Shows Information Instantly Select from a variety of models, including RSMs with a display. These easy-read screens let users see zone and channel information at-a-glance. Since the display mirrors the one on top of the portable, it delivers the information users need, when they need it. Many of our RSMs/PSMs give users immediate access to radio controls from volume and channel selector to emergency and programmable buttons. Reduce Background Noise To reduce background noise in windy environments, we designed the Windporting feature on select RSMs/PSMs. Windporting dramatically reduces the noise caused by howling winds and harsh weather. In addition, it prevents water from clogging the microphone and distorting transmissions. In a domed stadium or an open-air event, noise-canceling acoustics on select RSM models negate background noise so your voice comes through loud and clear anytime you speak into the microphone. Noise-canceling RSM models have up to five microphones enabling best in class user transmission by mitigating the surrounding environmental audio. Whatever the work condition, there s a microphone made for each unique situation. Endures Adverse Conditions Many of our RSMs and PSMs meet and exceed tough specs IP57 submersibility ratings to withstand water immersion longer. Even if users drop them in a puddle or wear them in the rain, they will stay connected. Our rugged accessories take toughness further exceeding IP57 standards for submersibility and providing an optimal level of water protection. If you are on the fireground and a hose drenches your RSM, it will stand up. Display RSMs sport the first rugged, submersible audio jack so you can receive discreet communications with a separate earpiece accessory and not worry about water damaging your connection. APX XE Remote Speaker Microphone Firefighter safety is critical to us. Motorola Solutions has teamed up with first responders around the world to develop a rugged remote speaker microphone (RSM) that complements our APX XE radios and withstands the harshest conditions. The APX XE RSM is part of our complete portfolio of firespecific radios and accessories, with ultra-rugged features, advanced ergonomics and special innovations to improve responder safety. From exaggerated controls to exceptional noise suppression, it is made for the noisiest, nastiest days. The XE RSM is designed for easy use on the fireground. From exaggerated controls, you can operate with bulky gloves to an asymmetrical shape so you can find the controls you need without looking. Feel how the XE RSM fits comfortably in your hand and discover the difference extreme ergonomics make. The large emergency button that is easy to locate, but shielded so it s not accidentally activated. The prominent push-to-talk button that is easy to find and press with gloves on. The easily accessible, programmable buttons and a volume switch on the corner of the RSM that rocks up and down to distinguish it from other controls. The XE RSM is available in three different housing colours to meet your specific needs and includes a large metal D-ring that flips up or down so you can attach it any way you want on your turnout gear. A high visibility strobe light activates when the emergency button is pressed, this strobe has been Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 347

263 verified by firefighters in training conditions to be visible in smoke up to 10 feet. In addition, if the RSM is sprayed with a hose or dropped in a pool of water, you will see what rugged specs and a unique water-draining speaker design really mean. Noise Suppression at its Best The XE RSM is the first accessory with up to five microphones that locate the talker and cancel out background noise. It suppresses noise so effectively, you can be heard in the loudest environments over roaring fire, pumper trucks and wailing sirens. A large speaker delivers the loudest, clearest accessory audio available 50% louder and clearer than our existing XTS RSMs so transmissions are clear and intelligible, not distorted or garbled. Because the XE RSM leverages the exceptional noise suppression technology of our best-in-class APX radios, you can be heard and be clearly understood in all types of extremes. APX Extreme Performance (XP) RSM Designed with mission critical law enforcement users in mind, the APX XP RSM suppresses noise so effectively; you can be heard over traffic noise, crowds and sirens. Its unique dual-microphone design tracks the talker's voice so that you can keep your eye on what is in front of you while still talking on the microphone. A digital signal processor (DSP) algorithm helps suppress background noise so you can be heard clearly regardless of the noise around you. It includes a flexible 360-degree rotatable shoulder clip, designed specifically to fit comfortably on the Sheriff uniform epaulet. A D-ring provides an additional attachment option. This IMPRES RSM is the thinnest RSM in the APX portfolio and is designed specifically for tough mission critical use buttons are enlarged for easy access, yet recessed to avoid accidental activation. p. 348 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-153

264 Mission Critical Wireless - Bluetooth Accessories Motorola Solutions APX 4000, 6000 and 8000 portable radios ship standard with Bluetooth functionality enabled. The County s users can use COTS Off-The-Shelf Bluetooth accessories or Motorola Solutions Mission Critical Wireless accessories to meet their operational needs. Columbia County s users need wireless accessories that are remarkably fast, secure, robust and easy to use. Yet off-the-shelf Bluetooth products often lack the performance, security and comfort they require. That is why Motorola Solutions developed enhanced Bluetooth accessory solutions for APX portable radios. Our portfolio is the choice of first responders in the moments that matter most Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 349

265 Motorola Solutions Mission Critical Wireless Advantages Critical Voice on Demand With enhanced security, quick pairing and fast push-to-talk (PTT), our APX Mission Critical Wireless portfolio stands out in meeting these most critical criteria. When you use our accessories with Bluetooth-enabled APX radios, you can be sure every data transmission and every word gets through. Just Touch and Go Our accessories pair with just a touch and usually connect in less than 10 seconds even around other Bluetooth devices. Grab an earpiece or earbuds; place the PTT pod within an inch of any APX portable and securely pair. There is no need to enter codes or navigate through menus. Every Transmission is Secure While the APX radio is pairing, a Bluetooth ID and a strong 128-bit key are exchanged to encrypt the Bluetooth link IMPRES 2 Technology Batteries and Battery Chargers Motorola Solutions created our patented IMPRES 2 technology as an integral part of our two-way radio batteries and chargers. Users who rely on IMPRES 2 call it innovative and indispensable. We call IMPRES 2 the intelligent way to communicate offering enhanced performance and exceptional capabilities for your radio, your battery and its charger and your users. IMPRES Smart Energy System Our innovative IMPRES 2 battery charging and reconditioning system streamlines and automates battery maintenance. It draws on our exclusive technology that enables communication between battery and charger to help lengthen battery life and extend talk time. Automates Battery Maintenance Users want to be sure they can get the most out of every battery by maximizing its life. IMPRES 2 automates battery reconditioning, adapting the intervals to each battery s usage pattern. IMPRES 2 batteries and chargers have the capability to exchange data. This allows the IMPRES charger to evaluate the usage pattern of an IMPRES battery and determine the optimum reconditioning interval, thus optimizing battery life. Eliminates Overcharging IMPRES 2 batteries can be left in their IMPRES chargers for extended periods without heat damage from the charger. If radios are accidentally left in the charger overnight, over a weekend or longer p. 350 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-155

266 there should not be any worry about shortening the battery s life. Because the IMPRES 2 charger automatically monitors battery capacity, batteries are safely charged to the right capacity and always ready to go. Better Data for Better Decisions IMPRES 2 batteries store critical usage information. Each two-line IMPRES 2 charger display presents data at a glance, so users and administrators can make informed decisions about battery replacement. Data includes key information such as battery capacity, time remaining to complete charging and each battery s unique serial number. If you are operating a large fleet of batteries, IMPRES 2 Battery Data Reader is a valuable diagnostic tool to evaluate individual IMPRES 2 batteries. Furthermore, IMPRES 2 Battery Fleet Management collects and consolidates that data automatically, so you can identify, quickly and easily, when batteries need to replaced. Tested Tough and Proven Tough All Motorola Solutions IMPRES 2 batteries are Proven Tough. Time after time, in lab test after test for Drop, Vibration and ESD (Electrostatic Discharge) they withstand shocks, knocks, drops and shakes and outperform the leading brands. If your radio is banged on a ride, rattled by heavy equipment or shocked by static electricity, you can depend on IMPRES batteries to stay true and stand tough Mobile Radio and Control Station Equipment Please refer Section 9, Appendix for APX portable radio specification documents. ASTRO TWO-WAY MOBILES SELECT THE RIGHT PRODUCT TO ENSURE SAFETY AND RELIABILITY Features APX 8500 APX 7500 APX 6500 APX 4500 APX 1500 Control Heads Control Heads O2, O3, O5, O2, O3, O5, O2, O3, O5, O2 O2 O7 O7 O7 Max. # of Control Heads Rugged (IP Rating) IP54 IP54 IP54 IP56 IP54 EMG Button (Initiate EMG Call) Electronic Display (Alpha Numeric Indicators for System Status, CH/TG, User ID, Call Alert, Status) Control Integration with Light, Siren, Etc Protocols and Systems Supported APCO EIA/TIA Standards Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 351

267 MIL 810 Specification Multi-Band Capable Dynamic Dual Mode Capable (FDMA/TDMA) Analog Conventional P25 Phase I (FDMA) Conventional and Trunking P25 Phase II (TDMA) ASTRO TWO-WAY MOBILES Trunking SmartNet/SmartZone Analog and Digital Trunk 3600 and 9600 MDC-1200 Analog Signaling 3600 or 9600 Standard Channels Mounting Options Dash Mount Remote Mount Motorcycle Control Station Consolette Encryption Capability Encryption Capability (Optional) AES and DES AES and DES AES and DES AES Only Multi-key ADP POP 25 P25 OTAR Applications ADP only Mission Critical Wireless (Bluetooth) p. 352 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-157

268 ASTRO TWO-WAY MOBILES Wi-Fi Integrated Voice and Data Text Messaging Enhanced Data Integrated GPS - Outdoor Location Radio Authentication Voice Announcement Dual Radio Capability Priority Scan of TG or Channels Radio Management Electronic Software Programming Suite TX Time Out Timer RFP Electronic Specs (See Spec Sheets) Portable Radio Equipment Please refer Section 9, Appendix for APX portable radio specification documents. ASTRO TWO-WAY PORTABLES SELECT THE RIGHT PRODUCT TO ENSURE SAFETY AND RELIABILITY Features APX 8000 Supported Frequencies VHF ( ) APX 8000X E APX 7000 APX 7000X E APX 6000 APX 6000X E APX 4000 APX 3000 APX 1000 Power Level 6W UHFR1 ( ) Power Level 5W UHFR2 ( ) Power level 6W Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 353

269 700/800 MHz ( ) Power Level 3W 900 MHz ( , ) Power Level 2.5W Protocols and Systems Supported APCO EIA/TIA ASTRO TWO-WAY PORTABLES Standards Exceed MIL 810 Specifications Multi-Band Capable Dynamic Dual Mode (FDMA/ TDMA) Analog Conventional P25 Phase I (FDMA) Conventional and Trunking P25 Phase II (TDMA) Trunking Smart Net/Smart Zone Analog and Digital Trunking 3600 and or 9600 MDC-1200 Analog Signaling Standard Channels Encryption Capability Encryption Capability (Optional) AES and DES AES and DES AES and DES AES and DES AES and DES AES and DES AES ONLY AES and DES Multi-key ADP ADP ONLY SW only Radio Authentication POP 25 p. 354 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-159

270 P25 OTAR Environmental Rugged Std IP68, Delta T option Models 1.5, 2.5, 3.5 Colors Color Sleeves Applications Mission Critical Wireless (Bluetooth) Wi-Fi Black, Yellow, Green Sleeve s Only Red, Orange, Blue ASTRO TWO-WAY PORTABLES IS & Delta T Std 1.5, 2.5, 3.5 Black, Yellow, Green Std IP67, Delta T option IS & Delta T Std Std IP68, Delta T option 1.5, , , 2.5, 3.5 Black, Yellow, Green Sleeve s Only Red, Orange, Blue Black, Yellow, Green Black, Yellow, Green Sleeve s Only Red, Orange, Blue IS & Delta T Std 1.5, 2.5, 3.5 Black, Yellow, Green Std IP67, Delta T option Standa rd IP67 Standa rd IP54 2 and , 2 and 3 Black Black Black Reflecti ve Label Reflecti ve Label Text Messaging Mandown GPS Integrated Voice and Data Enhanced Data Voice Announcement Priority Scan of TG or Channels Radio Management Electronic Software Programming Suite TX Time Out Timer Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 355

271 ASTRO TWO-WAY PORTABLES RFP Electronic Specs (See Spec Sheets) p. 356 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-161

272 This page intentionally left blank Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 357

273 4.9 SYSTEM-LEVEL BLOCK DIAGRAMS Columbia County, Florida Block diagrams are not included in this section as they are referenced and reflected in Exhibit F. p. 358 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-163

274 This page intentionally left blank Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 359

275 4.10 ACCEPTANCE TESTING Coverage Methodology Hydra SM Overview Hydra is an innovative software tool developed by Motorola Solutions, Inc. to accurately predict coverage, model traffic (voice and data), analyze interference, plan channel re-use, and perform other design tasks for our diverse portfolio of radio networks. This description concentrates on Hydra coverage planning aspects Hydra Development Our Hydra coverage prediction tool was developed to provide accurate coverage simulations by applying proven models to detailed system and environmental data across large geographical areas. To create an accurate picture of the predicted radio coverage, many elements must be considered. Some of these elements, called system factors, are related to the system design parameters. System factors affecting coverage performance include frequency, distance, transmitter power, receiver sensitivity, antenna height, and antenna gain. Other factors, called environmental factors, vary according to the path taken by the radio signal and the environment surrounding the receiver. Environmental factors include terrain variations, obstructions, vegetation, buildings, ambient noise, and interference. All coverage prediction methods try to account for both types of factors and incorporate them into a computational model. In general, the currently accepted models, such as Okumura, Longley-Rice, and TIA provide excellent portrayals of radio coverage when used within their respective ranges of applicability. In the past, this level of analysis was adequate for the type of basic systems that were available. However, today s complex technologies, such as digital voice radios, packet data systems, or simulcast, require a much more in-depth analysis of the expected coverage performance to create a cost-effective design. This makes it necessary to select the appropriate coverage model, provide accurate representation of the environmental factors throughout the service area, and apply the coverage analysis method to every location within the service area. Recognizing these facts, we developed Hydra, a multi-purpose network design tool that includes a coverage analysis program. Taking advantage of the knowledge gained from our many years of practical experience and coverage testing, Hydra provides a superior means for analyzing system coverage. This program, unique to us, employs a technique of computing coverage on every tile in a service area rather than along a finite number of radials. Hydra computes layers of these tiles, with each layer containing the values of propagation model losses, coverage simulation results, or datasets. Layers can be displayed separately or in any combination as maps of the service area Hydra Detailed Description Inputs and Outputs Inputs to Hydra simulations include system architecture, equipment characteristics, service area boundaries, areas of various building losses, subscriber unit distribution density for traffic analysis, etc. p. 360 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-165

276 Hydra 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 coverage analyses can be limited to specified service area polygons (e.g., a county, a city, or a dispatch territory), so coverage reliability can be analyzed exclusively within the boundaries of your operating area. In addition to showing coverage reliability, Hydra maps can display terrain, land cover, roads and boundaries, signal strength and field strength, interference predictions, etc. Hydra provides closed-loop integration between predicting coverage and verifying coverage using Motorola Solutions Voyager SM coverage acceptance testing tool. Field survey measurements signal strength, Bit Error Rate (BER), and Message Success for data can be loaded into Hydra for analysis, display, and printing. Tile Method Hydra uniformly divides the entire geographical area to be analyzed into small, distinct areas called tiles. The resolution (size) of the tiles can be as fine as one arc-second (approximately 100 feet at U.S. latitudes). At each tile, Hydra models propagation from each site in the system. The tile method is of particular importance in the calculation of simulcast coverage and interference analysis. Radial methods determine performance only at the locations where radials from all sites cross, leaving many areas where coverage performance is not calculated. With the tile method, the information from every site and all datasets is available in every tile; this provides the most accurate results for multi-site analyses (simulcast, voting, interference, best server, etc.). Datasets For propagation prediction, Hydra uses two types of geophysical datasets: 1. Hypsographic (terrain elevations) to determine shadow loss and elevation 2. 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. Because of the massive amount of data involved, even the best datasets contain a certain amount of errors, caused by a number of factors that are difficult to completely overcome. Some examples follow: Source information - Older hypsographic and morphologic datasets were derived from existing map information, so any errors in the existing maps were carried over to the datasets. Newer datasets such as the U.S. National Land Cover Dataset (NLCD) are derived from satellite imagery, and are affected by digitization error. Dataset development process - Potential error sources include limitations in the digitizing algorithms, computer hardware problems, and judgment calls by the dataset developer. Dataset currency - Since the physical world is constantly changing, datasets can never be completely up-to-date. Over time, forests and shrub land are turned into farmland, hills are leveled, roads are built, communities are developed, and large buildings are constructed. Natural Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 361

277 phenomena such as earthquakes, volcanoes, fires, storms, etc., change both the topography and environmental factors. Hydra, like all terrain-based propagation tools, provides coverage predictions that are only as accurate as the available datasets permit. In the U.S., Motorola uses high-quality terrain and land cover data derived from USGS 30-meter DEM and NLCD sources. Hydra can use other datasets, including: Planimetric (mapping - Roads, water features, political boundaries, feature names, etc. U.S. radio site locations - Coordinates of existing radio sites, including FCC wireless licenses, FCC antenna site registry, and some commercial site providers U.S. frequencies - Potentially available channels in geographic areas, per FCC wireless licenses Propagation Model For each tile, Hydra predicts signal strength using an improved algorithm based on the industryaccepted Okumura model. 11 Coverage Reliability Hydra coverage maps indicate the probability (usually referred to as reliability) of the radio system providing a minimum acceptable criterion, such as a voice Delivered Audio Quality (DAQ) or a data Message Success Rate (MSR). Since system coverage can never be 100% reliable, there will always be particular times and locations where the signal strength or Bit Error Rate (BER) does not meet that needed to reach the performance criterion. These locations of unsatisfactory performance are often predictable in a coverage study. However, there are also areas of unsatisfactory coverage that cannot be predicted due to unknown circumstances such as unusual structures, tree density, ambient noise, atmospheric conditions, dataset errors, and interference from co-channel or adjacent channel units operating outside their normal service area. Because these conditions exist and signals fade due to these environmental and terrain factors, coverage must be described statistically in terms of a percentage of locations that exhibit the minimum acceptable criterion. Hydra predicts Area reliability, defined as the probability of achieving a specified performance criterion within a geographical area of interest. The area of interest is either the Covered Area (the painted area on a Hydra coverage map), or the entire Service Area. To provide radio systems with acceptably few communications failures throughout the Covered Area, Motorola designs coverage at high Area reliabilities. The performance criterion is usually DAQ for voice or MSR for data. It is also important to note that locations outside of a Hydra map coverage area may still provide useable communications, even though such locations do not achieve the minimum acceptable performance Hydra Capabilities Hydra provides detailed performance simulation of the following Motorola wireless network architectures: Voice coverage and traffic (Analog FM, ASTRO, SECURENET TM, etc.) ASTRO25 Integrated Voice & Data (IV&D) coverage and traffic 11 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 p. 362 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-167

278 Dimetra coverage and voice traffic High Performance Data (HPD) Long Term Evolution (LTE) data coverage If co-channel and/or adjacent-channel sites are known to exist, Hydra can model both Interfered and non-interfered coverage. Hydra Frequency Re-Use Planning analysis takes into account both co-channel and adjacent channel frequencies. Voice Systems Hydra coverage models use proven Okumura-based prediction methods and Monte Carlo simulation techniques to provide coverage reliability maps. Voice coverage models (Voice, Dimetra, ASTRO25) provide system-wide coverage maps, as well as subsystem maps (when applicable, e.g., for simulcast cells and receiver voting), and individual site maps. Simulcast Coverage Performance For a simulcast system, merely providing coverage maps of individual sites (separately or on the same map) does not accurately represent the total system performance, which depends upon differential delays and aggregate signal levels. Therefore, Motorola has developed the Hydra simulcast model, which uses the delay spread methodology to simulate aggregate signal strength and audio phase angle (delay) throughout the entire predicted coverage area. Analysis for the combined effect of signal strength and differential delays from the simulcast transmitters in the system is performed at all locations within the predicted coverage area. Hydra simulcast coverage maps will show any areas predicted to have coverage problems caused by out-of-phase signals and/or inadequate signal strengths. Hydra allows modeling with varied transmitter launch delays to predict optimized simulcast coverage within the evaluation area. Data Systems (ASTRO25 IV&D, HPD, and LTE) Wireless data network performance is highly dependent on RF coverage reliability, network protocol, and network traffic load. Hydra accurately predicts the coverage and traffic performance of Motorola data systems by modeling the automatic protocol retry mechanisms of data protocols. Hydra integrates RF coverage prediction, network protocol modeling, and traffic engineering into a single simulation, and utilizes Monte Carlo simulations as well as discrete event simulation techniques to provide a tool that accurately predicts wireless network system performance. Hydra uses the Okumura model for terrain-based propagation prediction, and adds the modeling of the protocol behavior (try-based coverage) via a detailed protocol simulation. Hydra models the relevant layers of the OSI protocol stack, from the physical layer of the air interface to the application layer of the host and subscriber entities. Using this modeling approach, Hydra can account for all the elements that impede network performance, from packet loss on the wireless link due to co-channel interference, to packet latencies in the fixed end equipment introduced by protocol behavior. Hydra s modeling architecture allows true end-to-end system modeling. Data Coverage Hydra s data coverage model, through multiple iterations, displays the area that meets the MSR performance criterion requested by the user. The system-wide maps show the composite coverage Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 363

279 from multiple sites, at the specified area reliability criterion and for the specified number of protocol tries. Data Traffic Summary Hydra integrates coverage prediction into the traffic simulation, so the terrain and subscriber distribution effects on packet collisions and interference are modeled in the simulation. Traffic simulation results provide performance statistics for the RF station, radio channel, controller, and application(s). Hydra allows predicting the performance of the actual network topology as designed by the engineer. 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. The RFP required coverage maps for both FDMA and TDMA for Portable with ½ Wave antenna at hip level. There are a total of twenty-six maps. Eight of the 16 maps are for the Modified County Service Area utilizing the required five existing antenna sites. There are eight additional maps for the full County Service Area utilizing the additional sixth antenna site Coverage Acceptance Test Plan (CATP) This Coverage Acceptance Test Plan (CATP) is designed to verify that the voice radio system implemented by Motorola Solutions meets or exceeds the service area reliability defined in Table 4-12 of this CATP. The CATP defines the coverage testing method and procedure, the coverage acceptance criterion, the test documentation and the responsibilities of both Motorola Solutions and the County. Coverage acceptance testing is based upon a coverage prediction that accurately represents the implemented infrastructure and parameters that are consistent with the contract agreements. If the implemented system varies from the design parameters, then a revised coverage map will be prepared and the guaranteed service area reliability will be adjusted accordingly. New test maps will reflect the measured losses and gains associated with the implemented infrastructure and subscribers. These will be used to define the test configuration. To verify that the radio coverage reliability is met, the County s service areas will be divided into equally sized test grids no larger than 0.5 miles x 0.5 miles. The size and quantity of grids required to achieve a 99% confidence level in the testing results, as determined in TSB 88, will be calculated prior to the actual test for each configuration. The number of test grids required to provide a statistically valid sampling of testing points may vary by the coverage configuration being tested, thus causing the size of each grid to be smaller. Table 4-12 shows the predicted service area reliabilities we will commit to based on the site configuration defined by the County. p. 364 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-169

280 Table 4-12: Predicted Service Area Reliability Based on 5 Sites within the Modified County Service Area Contractor Guaranteed Percentage of Service Area Reliability for Radio Coverage County Service Area Portable, 1/2 wave on hip at 3.3' AGL, body loss of 10.3dB Outdoors County Service Area Portable, 1/2 wave on hip at 3.3' AGL, body loss of 10.3 db in 6dB loss buildings County Service Area Mobile, 1/4 wave on the roof at 5.0' AGL Phase 1 FDMA % Phase 2 TDMA % Motorola Solutions notes that the service area reliability levels are achievable by the use of the RFP defined requirements to use the existing County owned tower sites and ensure the compliancy with Region 700 MHz contour requirements. The reliability levels presented in the above table are based on a design that is 100% compliant to the stipulations in the RFP. Table 4-13: Predicted Service Area Reliability Based on 6 Sites within the County Service Area Contractor Guaranteed Percentage of Service Area Reliability for Radio Coverage County Service Area Portable, 1/2 wave on hip at 3.3' AGL, body loss of 10.3dB Outdoors County Service Area Portable, 1/2 wave on hip at 3.3' AGL, body loss of 10.3 db in 6dB loss buildings County Service Area Mobile, 1/4 wave on the roof at 5.0' AGL Phase 1 FDMA % Phase 2 TDMA % It should also be noted that the RFP specified user device losses that exceed the field-tested losses that we would typically use to predict system coverage. Therefore, the numbers given above are conservative and are based on CATP test parameters defined in the RFP. When factors are taken into account such as our optimized APX device design, advanced acoustics and audio processing and the ability of the human ear to discern audio well below the CATP test criteria, it can be expected that the usable service area of the system would be markedly higher than suggested by the reliability figures tabulated above. The following text provides a detailed description of the CATP CATP Definitions Several definitions are needed to accurately describe the coverage test method. Coverage Area The coverage area is the geographical region in which communications will be provided that meets or exceeds the specified Channel Performance Criterion (CPC) at the specified reliability for the specified equipment configurations. These coverage areas are the jurisdictional boundaries of the County and Modified County for portable on street and for 6dB building loss coverage as defined in the RFP. In the event that the 6 th site currently identified as Forest is not yet built at the time of the scheduled CATP, the modified county service CATP will be completed. Once the Forest site is completed, the CATP will be repeated for the predicted coverage area that the Forest site will provide. This will Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 365

281 include all of the county area north of the modified county line and all of the county area 6 miles south of the modified county line. The results will be added to the original CATP. Channel Performance Criterion The CPC is the specified minimum design performance level in a faded channel. For this system, the CPC is a Delivered Audio Quality (DAQ) of DAQ 3.4 for portables and mobiles. DAQ definitions are provided in Table 4-14 {TSB 88.1 C, 5.4.2, Table 2}. Table 4-14: DAQ Definitions DAQ Faded Subjective Performance Description 1 Unusable, speech present but unreadable 2 Understandable with considerable effort Frequent repetition due to noise/distortion 3 Speech understandable with slight effort Occasional repetition required due to noise/distortion 3.4 Speech understandable with repetition only rarely required Some noise/distortion 4 Speech easily understood Occasional noise/distortion 4.5 Speech easily understood Infrequent noise/distortion 5 Speech easily understood Service Area Reliability The service area reliability, also defined as the CPC service area reliability, is the percentage of locations within the desired service area that meet or exceed the specified CPC. We have indicated the CPC service area reliability in Table 4-12 for the losses detailed in the RFP. Although the coverage maps do not guarantee coverage at a specific location, they do indicate the ability of the system to provide service and to overcome the expected losses of typical buildings located within the service area as defined by the RFP Equipment Configurations Coverage acceptance is based on two radio configurations for the field unit equipment or subscriber. Our coverage maps for this system indicate the coverage area for the following equipment configurations: Portable (3 watt): A. 119 dbm receiver sensitivity per the RFP B. Hip level (3.3 feet for transmit and receive) ½ wave flex antenna per the RFP C db of body loss per the RFP D. P25 Phase 1 FDMA and Phase 2 TDMA operation Mobile (25 watt) A. 119 dbm receiver sensitivity per the RFP B. Vehicle roof mount (5 feet for transmit and receive) ¼ wave antenna per the RFP C. Loss of 3 db when referenced to a half wave dipole per the RFP p. 366 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-171

282 D. P25 Phase 1 FDMA and Phase 2 TDMA operation Coverage acceptance is based on the five tower site coverage and six--tower site design using simulcast transmission and receiver voting In Building Coverage Our coverage maps for portable in building equipment configurations are predictions of coverage both outdoors and inside buildings throughout the service area. The in building coverage predictions are based on 6dB of building loss. Typical examples of building losses are provided in Table Building Type Light (6dB loss) Table 4-15: Typical Building Types Typical Building Description Standalone residential structures wooden and brick veneer Since building loss varies significantly depending on the construction of buildings, Motorola Solutions coverage maps do not predict coverage within any specific building. Rather, the in building coverage maps indicate the area within which this system is predicted to provide 95% covered area reliability of meeting or exceeding the CPC of DAQ 3.4 for the defined building loss. The building loss tests will be conducted outdoors with a fixed 6dB of simulated building loss introduced via attenuators, not within actual buildings. There is no requirement in the RFP to test or guarantee coverage within any specific critical buildings CATP Method The method used to test coverage is statistical sampling of the predicted coverage area to verify that the CPC is met or exceeded at the required reliability for each of the defined equipment configurations. It is impossible to verify every point within a coverage area, because there are infinite points; therefore, coverage reliability will be verified by sampling a statistically significant number of randomly selected locations, quasi uniformly distributed throughout the predicted coverage area. This CATP provides a method of tracking test tile location using Motorola Solutions Voyager SM hardware and software. A GPS receiver will provide location information indicating when a valid test tile is available for testing. The method follows TIA TSB 88.3 C 5.0, Performance Confirmation for statistical sampling. This CATP provides an objective, quantitative method of measurement using Voyager software in conjunction with an APX 6000 portable radio for location reference, BER measurements and recording of signal strength for informational purposes. The CATP also provides a subjective audio quality test by using actual equipment and simulating the required building loss with attenuators and then performing voice tests to determine the pass or fail status of the required DAQ 3.4 voice quality performance. Determine the Required Number of Test Tiles in the Coverage Area The requested service area will be divided into a tile pattern to produce at least the number of uniformly sized test locations (or tiles) required by the Estimate of Proportions formula {TSB 88.3 C, 5.2.1, equation 2}. The minimum number of test tiles required varies for different systems, from a hundred to many thousands, depending on the size of the service area, desired confidence in results, Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 367

283 type of coverage test and the predicted versus required reliability. Our Hydra Stratus SM coverage modeling tool calculates the required test tiles as described. Constraints on Test Tile Sizes The minimum tile size is 100 by 100 wavelengths; however, the minimum practical test tile size is typically about 400 by 400 meters (about 0.25 by 0.25 miles). The minimum practical tile size for any system is determined by the distance traveled at the speed of the test vehicle while sampling, GPS error margin and availability of road access within very small test tiles. A related consideration is the time, resources and cost involved in testing very large numbers of very small tiles. The maximum test tile size is 2 by 2 kilometers (1.25 by 1.25 miles). In some wide area systems, this constraint on maximum tile size may dictate a greater number of test tiles than the minimum number required by the Estimate of Proportions formula. Accessibility to Test Tiles Prior to testing (if possible) or during the test, Motorola Solutions and the County will determine whether any test tiles are inaccessible for the coverage test (due to lack of roads, restricted land, etc.). Inaccessible tiles will be eliminated from the acceptance test calculation; however, a minimum number of test locations must be accessed to provide a statistically valid test. This is important since all valid test tiles are part of the prediction and when tiles are removed from the proof of performance testing, the area reliability accuracy could be adversely affected. TSB 88.3 C provides consideration for inaccessible test locations called Estimated based on adjacent grids (single grids only). Single inaccessible test locations would be considered a pass if 5 of the 8 surrounding test tiles provide passing results, provided that the CATP test tiles are defined as follows: Only those test tiles where the majority of the tile falls within the boundaries of the CATP area under test. Those test tiles within the CATP boundaries that are actually tested. Inaccessible test tiles that are surrounded by not less than 5 contiguous test tiles which have been tested and show an actual passing result (untested test tiles are not counted). Any other untested test tiles that do not fit any of the criteria above (e.g., untested test tiles surrounded by other untested test tiles, or less than 5 passed test tiles, etc.) would be categorized as simply untested and will not be factored into the results as a CATP tile. Randomly Select a Test Location within Each Tile Using Voyager, the actual test location within each test tile is selected randomly by the test vehicle crossing into the tile at an arbitrary point, with an arbitrary speed and direction. This will be the cue for the objective sampling test to begin. After the sample is taken for both BER and SSI, the test team will initiate the subjective voice test to determine if the test point passes the audio quality DAQ test. Perform Measurements in Each Tile In each test tile, a series of 200 or more sequential SSI measurements (sub samples) will be made, along with approximately 17 or more sequential BER measurements. This test location measurement, containing a number of sub samples, constitutes the test sample for this location. The test sample will establish the local mean BER and median SSI within the test tile. The distance over which the sub samples are measured will be 40 wavelengths. A mean of multiple BER and median of multiple SSI sub samples is used rather than a single measurement to ensure that the measurement is not biased by taking a single sample that might be at a peak or null point on the radio wave. p. 368 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-173

284 Determine If Each Test Tile Passes or Fails the CPC Requirement For each test tile, the pass/fail criterion is the objective Bit Error Rate (BER) and the subjective TDMA round trip voice quality assessment that meets the specified CPC. The subjective TDMA round trip voice test and the objective outbound BER tests are separately evaluated. Failure of the voice test does not constitute failure of the tile for the BER test and vice versa. For this system, the CPC is DAQ 3.4 for portables and mobiles. To simulate a portable with the required losses of buildings, the indicated net attenuation in Table 4-16 is used with a portable test device and accounts for the differential height and gain of a ¼ wave magnetic mount antenna on the test vehicle s roof. Per the RFP requirement, 1.3 db will be used for a height adjustment and 3.0 db will be used for an antenna loss adjustment versus a ½ wave dipole reference antenna. In each test tile an outbound TDMA bit error rate and outbound FDMA bit error rate test will be performed, providing an objective method of verifying that the radio system provides the faded performance threshold (BER) for the specified CPC for each of the defined equipment configurations. In each test tile a TDMA voice test exchange will also be initiated using predetermined text typical of a common voice exchange between the fixed location and the portable location. The person conducting the test at the portable will be moving at a typical speed for the surrounding conditions. Subjective TDMA coverage acceptance testing will be performed in both the talk out and talk in direction to determine if test tile passes or fails. The FDMA BER, TDMA BER and TDMA round trip voice test are separately evaluated. Failure of a BER test does not constitute failure of the tile for the TDMA voice test and vice versa. Building Loss Outside (0 db) 6dB building Table 4-16: Attenuator Values Net Attenuation for Portable Antenna and Building Loss (db) 8.6 ( ) 14.6 ( ) Determine the Coverage Service Area Reliability for Acceptance After all accessible tiles in the coverage area have been tested; the service area reliability (percentage) will be determined by dividing the number of tiles that pass by the total number of tiles tested. The coverage test acceptance criterion for each equipment configuration is that the tested service area reliability must be equal to or greater than the guaranteed service area reliability as shown in Table The BER and subjective voice service area reliability will be calculated independently. For the voice test, if a test call in a tile fails, a single retry will be permitted and the user may move up to 5 feet and retry the test. All retries shall be counted and no more than 5% retries will be allowed. All retries shall be documented Responsibilities and Preparation This information will help set the expectations of the County and Motorola Solutions regarding requirements for equipment, personnel and time during the coverage test. The County will provide the following for the duration of the coverage test: Vehicles for the duration of the test: A minimum of two test teams would be recommended, dividing the county (or modified county) between north and south. Whichever team finishes first can then assist the other team with its areas. Two (2) County representatives for each test vehicle to be the customer representatives for each of the field test teams Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 369

285 Two (2) County representatives for the fixed location (likely the dispatch center) to be the customer representatives for the fixed end. Motorola Solutions will provide the following for the duration of the coverage test: At least one (1) Motorola Solutions representative to participate in testing and operate Voyager for each team (this assumes that the customer representative would drive the vehicle). At least two (2) calibrated Motorola Solutions Voyager coverage testing packages per team. Test radios for each field team (unless the teams mutually agree to use customer owned radios). Coverage acceptance testing will be performed within the borders of the County s service area or Modified County service area. Once we have determined the minimum number of test tiles required, Motorola Solutions and the County will plan the route for the test vehicles through the coverage test area, to ensure that at least the minimum required number of tiles is tested. If possible, any tiles not accessible to the test vehicles will be identified while planning the route. Motorola Solutions will check and/or calibrate the test radios (standard APX 6000 portables) used with the Voyager coverage testing package in the County s presence. We will conduct this test only once. If any portion of the test is determined to be unreliable because of proven equipment malfunctions or failures, we will repeat the portion of the test affected by the equipment malfunction or failure. The County will have the option to accept the coverage at any time prior to completion of the coverage test. Before starting the test, the County and Motorola Solutions will agree upon the period for Motorola Solutions submission of a report containing the coverage test results CATP Procedures Subjective Voice Quality Testing A subjective listening test will be performed for coverage acceptance testing to verify TDMA talk out and talk in DAQ performance of the system. The procedure for the subjective DAQ coverage test will be as follows: To perform a statistically valid subjective DAQ test, a large group of people is required to ensure high confidence in the results. However, obtaining a large group of people for a subjective listening test is usually impractical; therefore, several (3 to 7) people in a car or van must be used for the test. Since a group this small cannot provide statistically significant results, it is very important that the personnel participating in the subjective test be familiar with the sound of radio conversations. A fixed control point location will be established. Prior to testing, the County and Motorola Solutions will agree upon a procedure to allow each audio transmission to be evaluated. The test participants will be divided into teams, each consisting of personnel from the County and Motorola Solutions. Each team will have members that operate a portable unit inside the test vehicle and members that are stationed at the fixed control point location. An odd number of team members is required to avoid ties for the pass/fail consensus of the test team. As the field test team(s) drive through the coverage area, test locations within each tile will be selected randomly by Voyager that will be conducting the objective BER and informational SSI testing. The voice subjective test may begin after the sampling is complete. This is to prevent any degradation to the receiver sampling the SSI/BER and to meet the TSB 88 requirement of a randomly selected test point. p. 370 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-175

286 The field test unit will make a TDMA call and identify the test tile by the current x y tile or tile cell number location and repeat one of ten phonetically balanced phrases (approximately 8 seconds in length). The fixed location unit (console or control station) test team will then determine if the voice passes or fails the DAQ criteria as defined by Table The fixed location will then repeat 1 of the 10 phonetically balanced phrases (approximately 8 seconds in length) and the field team will in turn determine if the voice passes or fails the DAQ criteria. The tile pass/fail evaluations will be used to determine the service area reliability of the defined coverage areas in Table If any test point should fail, the test team will move five feet and perform another test in the same manner. Either passed test will render that test point a PASS. Based on the TSB 88C definition of DAQ 3.4, which allows for repetition, no more than 5% of the testing points may be deemed to have passed due to a successful retry. Coverage acceptance will be based on demonstrating that the percentage of the tile locations, meets DAQ 3.4 or better. The system coverage acceptance criterion will be the successful passing of each of the equipment configurations. Motorola Solutions reserves the right to review any test tiles that fail the subjective DAQ tests. If a coverage test, or a portion thereof, is suspected by Motorola Solutions to have failed due to external interference, those tiles suspected of being affected by an interferer may be re tested. If the tiles (or test points) re tested are confirmed to have failed due to interference, those tiles (or test points) will be excluded from all acceptance calculations and Motorola Solutions will work with the County to identify potential solutions to the interference issues. The definition of interference includes any internal (on site) and external (off site) sources of RF energy that negatively affect communications, which includes but is not limited to the following types of interference: external noise, co channel interference, adjacent channel interference, intermodulation, passive intermodulation (PIM), desensitization, spurious responses or RF ducting. Such interference sources are outside of Motorola Solutions control and are not the responsibility of Motorola Solutions. Critical Buildings Subjective Voice Quality Testing Critical building testing is outside the scope of this test plan. Objective BER and Informational Signal Strength Testing Motorola Solutions will conduct attenuated objective BER testing and informational SSI measurements for the service area reliabilities as shown in Table Both the subjective and objective testing as described would be evaluated independently of each other. A tile that tests below the target BER for the objective test point will not constitute a failure for the subjective testing. The procedure for the objective BER coverage test will be as follows: The Voyager package will be installed in a test vehicle. The County s personnel will drive the test vehicle over a route planned to cover the accessible tiles within the coverage test area. Motorola Solutions personnel will operate the Voyager package. During the coverage test, the laptop computer will display the vehicle s location on a map of the coverage test area overlaid with the test grid. Voyager will automatically initiate signal level and BER measurements when the GPS receiver indicates that a test tile has been entered. The computer will provide a visual indication that a measurement has been completed in a tile. Voyager will manage the coverage test data collection and will store for later analysis the mobile outbound reference signal level measured in each tested tile. Attenuation of the test receiver will be used to evaluate whether each tile passes or fails the required BER for each equipment configuration. The tile pass/fail evaluations will be used to determine the coverage area reliability Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 371

287 Coverage acceptance will be based on demonstrating that at least the guaranteed percentage of the tiles in the coverage test area for each equipment configuration are measured to provide a mean level BER for the corresponding CPC or DAQ or better at the test receiver input. The system coverage acceptance criterion will be the successful passing of each of the equipment configurations. The DAQ to BER relationships for Phase 2 will not be the same as for Phase 1 (LSM/C4FM and IMBE). The Project 25 Phase 2 TDMA standard defines a new over the air bit rate for voice transmission (12,000 bps versus 9,600 bps) and two new transmitter modulations (H CPM and H DQPSK). Industry guidelines for modeling Project 25 coverage are established in Technical Services Bulletin TSB 88. The mean level BER value for FDMA DAQ 3.4 is 2.0%. The mean level BER value for TDMA DAQ 3.4 is 2.4%. Motorola Solutions reserves the right to review any test tiles that fail both the objective BER and subjective DAQ tests, versus the signal strength samples taken for the same test tiles. If a coverage test, or a portion thereof, is suspected by Motorola Solutions to have failed due to external interference, those tiles suspected of being affected by an interferer may be re tested. If the test tiles re tested are confirmed to have failed due to interference, those test tiles will be excluded from all acceptance calculations and Motorola Solutions will work with the County to identify potential solutions to the interference issues. The definition of interference includes any internal (on site) and external (off site) sources of RF energy that negatively affect communications, which includes but is not limited to the following types of interference: external noise, co channel interference, adjacent channel interference, intermodulation, passive intermodulation (PIM), desensitization, spurious responses, or RF ducting. Such interference sources are outside of Motorola Solutions control and are not the responsibility of Motorola Solutions CATP Documentation and Coverage Acceptance During the coverage acceptance test, Voyager generates computer files that include the measured SSI and BER for each test tile. It also generates a comma separated values (.csv) file that documents these samples for each test point taken. A copy of this data will be provided to the County at any time during the test or as required. Motorola Solutions will also document the voice testing results. Motorola Solutions will process this data to determine whether the coverage test was passed for the equipment configurations and to produce a map that graphically displays the statistical coverage test results along with the analyzed numbers of the passes and failures. Motorola Solutions will submit to the County a report detailing the coverage test results. This report will include a document, which is to be signed by both the County and Motorola Solutions, indicating the test was performed in accordance with this CATP and the results of the test indicate the acceptance or non acceptance of the coverage portion of the system. The County will have the option to accept the coverage at any time prior to completion of the coverage test or documentation process. Should Motorola Solutions fail to meet the coverage requirements for both the BER objective test and the voice Subjective test as detaled in this CATP, Motorola Solutions will provide a solution to correct the deficiency and re-run the CATP in accordance with the RFP Section 11 at no additional cost to Columbia County. p. 372 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-177

288 Mobile/Portable Equipment Checklist Vehicle Make: Vehicle Type: Vehicle No.: Service Shop: Radio Serial No.: Radio Network ID: Date: Technician: Note: A failure of any preliminary check will cause rejection and the vehicle will be returned for correction before continuing the testing and installation. Battery Visual Pass Fail 1. Broken or Cracked Case 2. Broken or Cracked Cover 3. Acidic Odor 4. Excessive Corrosion on Battery Posts 5. Battery Posts Tight Wiring Visual Pass Fail 1. Wires Pinched or Damaged 2. Wires Running Over Hot or Moving Parts 3. Condition of Battery Ground 4. Condition of Battery to Hot Lead 5. Wires Run Through Firewall (grommet installed) Radio Check Pass Fail 1. Radio Mounted Securely 2. Antenna Type (unity, 3 dbqw, etc.) 3. Antenna Line Type and Length 4. Antenna Installed Correctly 5. Antenna Length Correct 6. Tx Power Forward 7. Tx Power Reverse (< 4% of Forward Power) 8. VSWR (< 1.5:1) 9. Tx Deviation 10. Tx Frequency 11. Rx Sensitivity 12. Effective Receiver Sensitivity Degradation (refer to the Systems Engineer for maximum allowable degradation) Radio Software Check Pass Fail 1. Verify the hardware revision and model/and serial numbers (include an archive file with the software release version and personality parameters) Comments: Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 373

289 4.11 SPARES LIST 1 Item DS ETX-1300-PS/48 DC Power Supply 1 DS Description ETX-1300 GIGABIT ETHERNET AGGREGATION SWITCH,RED AC,32 EMPTY SFP SLOTS SFP GIGE TWP COPPER, UP TO 100M, RJ-45 CONNECTOR (GIGE ONLY) 1 DS SFP SM 1310 NM LC CONNECTOR 1 T8126 FORTINET FIREWALL APPLIANCE 1 DLN GB HARD DRIVE 1 CLN ETHERNET SWITCH 1 CLN ETHERNET SWITCH 1 DLN6970 FRU: DL380 G9 HARD DRIVE 1 DLN6973 FRU: DL380 G9 FAN 1 DLN6971 FRU: DL380 G9 DVD DRIVE 1 DLN6878 DAS GB SAS HARD DRIVE 1 DLN6867 DAS POWER SUPPLY 1 DLN6978 FRU: DOTHILL 4524 RAID I/O CONTROLLER MODULE 1 DLN6972 FRU: DL380 G9 POWER SUPPLY 1 DSTRAK91061 FOUR PORT DDM 1 CLN ETHERNET SWITCH 1 DLN6455 CONFIGURATION/SERVICE SOFTWARE 1 SQM01SUM0205 GGM 8000 GATEWAY 1 CA01616AA ADD: AC POWER 1 B1912 MCC SERIES DESKTOP SPEAKER 1 B1914 MCC SERIES DESKTOP GOOSENECK MICROPHONE 1 B1913 MCC SERIES HEADSET JACK 1 TT3106 Z440 WORKSTATION WINDOWS 10 IOT ENT (NON RETURNABLE) 1 B1934 MCC 7500E VOICE PROCESSOR MODULE FRU 1 CA00147AF ADD: MCC 7500E SECURE OPERATION 1 CA00182AB ADD: AES ALGORITHM 1 DLN6966 FRU: GCP 8000/GCM 8000/GPB DLN6455 CONFIGURATION/SERVICE SOFTWARE 1 DLN6781 FRU: POWER SUPPLY 1 DLN6846 FRU: GTR ESS INTEGRATION KIT FOR EXT GGM 8000 GATEWAY 1 DLN6895 FRU: PA 7/800 MHz 1 DLN6885 FRU: XCVR 7/800 MHZ V2 1 DLN6898 FRU: FAN MODULE 1 DLN6634 FRU: 700/800 MHZ SITE LNA p. 374 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-179

290 1 DLN1306 FRU: 700/800 MHZ CABINET RMC MODULE 1 DLN6677 FRU: G-SERIES XHUB 1 M-EEH-06-LOW PLANNING MODEL ECLIPSE ETSI ODU 600, Lower 06 GHz Coupler Assy Eclipse, 6 GHz Equal 3 db, V and H Polarization (840ET06H1A) 1 EXX Intelligent Node Unit e/w Node Controller Card & Fan Card 1 EXS-002 Node Protection Card 1 EXR Modem - Radio Access Cards (RAC 60E) 1 EXD Gigabit Ethernet Switch Card (DAC GE3) 1 EXA-001 Auxiliary Card, Up to 6 Dry Contacts Gigabit Ethernet SFP, Electrical RJ BASE-T Fan Tray Kit, IRU 600 v3 1 M-W41-L6 WTM 4100, L6 GHz (Planning Model only) GIG ETH SFP, OPT MMF 850nm LC 1000BASE-SX, <550M (LM28- C3S-TC-N) CABLE, PWR 2 CORE BLUE/GREY, 2x16AWG, 100M UNTERM (FRHT ) CONN, TERMINAL BLOCK, RECEPTACLE, 6 PIN, DUAL ROW, 3.5MM PITCH, CABLE MOUNT ( ) Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 375

291 4.12 COVERAGE MAPS Columbia County, Florida Coverage maps are not included in this document as they are included and reflected in Exhibit F. MAP # System Configuration 1 5 Site P25 Phase II TDMA Simulcast 2 5 Site P25 Phase II TDMA Simulcast 3 5 Site P25 Phase II TDMA Simulcast 4 5 Site P25 Phase II TDMA Simulcast 5 5 Site P25 Phase I FDMA Simulcast 6 5 Site P25 Phase I FDMA Simulcast 7 5 Site P25 Phase I FDMA Simulcast) 8 5 Site P25 Phase I FDMA Simulcast 9 6 Site P25 Phase II TDMA Simulcast 10 6 Site P25 Phase II TDMA Simulcast 11 6 Site P25 Phase II TDMA Simulcast 12 6 Site P25 Phase II TDMA Simulcast 13 6 Site P25 Phase 1 FDMA Simulcast 14 6 Site P25 Phase 1 FDMA Subscriber Configuration APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM Subscriber Location Map Type Coverage Guarantee On-Street Talk-Out Guarantee On-Street 6dB Loss 6dB Loss On-Street On-Street 6dB Loss 6dB Loss On-Street On-Street 6dB Loss 6dB Loss On-Street On-Street Talk-In Talk-Out Talk-In Talk-Out Talk-In Talk-Out Talk-In Talk-Out Talk-In Talk-Out Talk-In Talk-Out Talk-In Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee p. 376 Motorola Solutions Confidential Restricted Technical Approach and Proposed Solution 4-181

292 MAP # System Configuration 15 6 Site P25 Phase 1 FDMA 16 6 Site P25 Phase 1 FDMA 17 5 Site P25 Phase II TDMA Simulcast 18 5 Site P25 Phase II TDMA Simulcast 19 5 Site P25 Phase I FDMA Simulcast 20 5 Site P25 Phase I FDMA Simulcast 21 6 Site P25 Phase II TDMA Simulcast 22 6 Site P25 Phase II TDMA Simulcast 23 6 Site P25 Phase I FDMA Simulcast 24 6 Site P25 Phase I FDMA Simulcast 25 EOC TIA Contour Map 26 Cumorah Hill TIA Contour Map 27 Lulu TIA Contour Map 28 CCSO TIA Contour Map 29 Deep Creek TIA Contour Map 30 Greenfield TIA Contour Map Subscriber Configuration APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-6000 Radio on-hip with 1/2-wave In Swivel Case with RSM APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna APX-4500 Mobile Radio with ¼ wave Antenna Subscriber Location Map Type Coverage Guarantee 6dB Loss Talk-Out Guarantee 6dB Loss Talk-In Guarantee On-Street On-Street On-Street On-Street On-Street On-Street On-Street On-Street Talk-Out Talk-In Talk-Out Talk-In Talk-Out Talk-In Talk-Out Talk-In N/A N/A 40 dbu Contour N/A N/A 40 dbu Contour N/A N/A 40 dbu Contour N/A N/A 40 dbu Contour N/A N/A 40 dbu Contour N/A N/A 40 dbu Contour Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Guarantee Information Information Information Information Information Information Technical Approach and Proposed Solution Motorola Solutions Confidential Restricted p. 377

293 PROPOSAL TO COLUMBIA COUNTY, FLORIDA SECTION 8 NEGOTIATED COST PROPOSAL APCO P25 700MHZ RADIO SYSTEM PROJECT NOVEMBER 8, 2017 RFP-2017-O The design, technical, pricing and other information ( Information ) furnished with this submission is proprietary and/or trade secret information of Motorola Solutions, Inc. ( Motorola Solutions ) and is submitted with the restriction that it is to be used for evaluation purposes only. To the fullest extent allowed by applicable law, the Information is not to be disclosed publicly or in any manner to anyone other than those required to evaluate the Information without the express written permission of Motorola Solutions. MOTOROLA SOLUTIONS, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Solutions Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners Motorola Solutions, Inc. All rights reserved. p. 378

294 p. 379

295 TABLE OF CONTENTS Section 8 Negotiated Cost Proposal Negotiated Summary Pricing Negotiated Subscriber Pricing Columbia County, Florida p. 380 Motorola Solutions Confidential Restricted Negotiated Cost Proposal i

296 p. 381

297 SECTION 8 NEGOTIATED COST PROPOSAL 8.1 NEGOTIATED SUMMARY PRICING Table 8-1: Pricing Summary and Proposed Total Cost This worksheet summarizes all of the previous pricing worksheets to derive a Original Response Total Project Cost. Contractors are encouraged to provide cost reduction measures in the form of Trade- In allowances and/or other cost reduction Incentives. 1.2 Master Core Control Point Equipment and Services $ 1,376, $ 1,376, (EOC Communications Room) Remove Quantity 2 ISSI Connections $ (170,000.00) 600 OTAP Licenses $ 10, GPS Licenses $ 20, Add Enhanced Geo Select Quantity 396 Radios $ 76, Geo-Redundant Master Core Control Point Equipment and Services (CCSO) 1.4 P25 Simulcast System Control Equipment and Services (EOC Communications Room) 1.5 P25 Geo-Redundant Simulcast System Control Equipment and Services (CCSO) 1.6 Commercial Carrier Talk Group Interface for Smartphones 1.7 Network Control and Management System Equipment and Services 1.8 EOC Dispatch Center Common Console Equipment and Services $ 412, $ 412, $ 270, $ 270, $ 216, $ 216, $ 36, $ 36, $ 43, $ 43, $ 115, $ 115, Removed AES $ (10,950.15) 1.9 EOC Dispatch Equipment (AES removed and ADP $0) $ 347, $ 347, Mobile Dispatch Equipment $ 224, $ 224, EOC Site System Maintenance Console Equipment and Services N/A N/A Electrical Upgrades $ 29, p. 382 Motorola Solutions Confidential Restricted Negotiated Cost Proposal 8-1

298 This worksheet summarizes all of the previous pricing worksheets to derive a Total Project Cost. Contractors are encouraged to provide cost reduction measures in the form of Trade- In allowances and/or other cost reduction Incentives. Original Response 1.12 Logging Recorder System and Integration and Services $ 132, $ 132, Removed from Scope $ (132,429.15) 1.13 EOC Tower Site Equipment and Services $ 361, $ 361, Antenna Line and Mutual Aid Base Station Installation $ 9, Deep Creek Tower Site Equipment and Services $ 431, $ 431, Relocation of Existing Digital Simulcast Paging $ 9, Antenna Line and Mutual Aid Base Station Installation $ 9, Cumorah Hill Tower Site Equipment and Services $ 435, $ 435, Lulu Hill Tower Site Equipment and Services $ 415, $ 415, CCSO Hill Tower Site Equipment and Services $ 366, $ 366, EOC Microwave Network Backhaul System $ 82, $ 82, Deep Creek Microwave Network Backhaul System $ 72, $ 72, Cumorah Hill Microwave Network Backhaul System $ 71, $ 71, Lulu Microwave Network Backhaul System $ 68, $ 68, CCSO Microwave Network Backhaul System $ 71, $ 71, Franklin Street Microwave Network Backhaul System $ 83, $ 83, Public Safety Mobile Radios $ 883, $ 883, See Equipment List for Feature and Model Changes $ (75,027.96) $ Public Safety Portable Radios $ 1,147, $ 1,147, See Equipment List for Feature and Model Changes $ 35, $ Local Government Mobile Radios $ 364, $ 364, See Equipment List for Feature and Model Changes $ (22,184.29) 1.29 Local Government Portable Radios $ 16, $ 16, See Equipment List for Feature and Model Changes $ (498.57) Desktop Control Stations (Quantity 21) $ 96, Recommended Spares for Infrastructure Equipment $ 76, $ 76, Training $ 135, $ 135, Customer Discretionary Equipment or Services $ 77, Negotiated Cost Proposal Motorola Solutions Confidential Restricted p. 383

299 This worksheet summarizes all of the previous pricing worksheets to derive a Total Project Cost. Contractors are encouraged to provide cost reduction measures in the form of Trade- In allowances and/or other cost reduction Incentives. Original Response Drop Ship Freight $ 5, $ 5, % Performance and Payment Bond $ 34, $ 34, Total Proposed System Turnkey Cost (Before Cost Adjustments) $ 8,264, $ 8,298, Optional Pricing Summary and Proposed Total Cost RFP Compliant Infrastructure Options Total to add Greenfield Site from Tower RFP $ 313, $ 313, Total to add Greenfield Site items 1.18 and 1.25 $ 350, $ 350, Total to Upgrade Microwave Network from outdoor radios to all indoor radios (Including Greenfield Site) $ 188, $ 188, System Purchase Discount $ (1,434,000.00) $ (1,434,000.00) Customer Loyalty Discount $ (1,365,629.00) $ (1,453,414.00) Subscriber Volume Discount $ (400,000.00) $ (400,000.00) Geo-Redundant Prime Control Point Discount $ (216,449.00) $ (216,449.00) Greenfield Site Discount $ (200,000.00) $ - Total Proposed System Turnkey Cost (After Cost Adjustments) $ 5,500, $ 5,646, Motorola Recommended Alternative Corrective and Preventative Maintenance 1.34a Motorola Recommended Alternative Corrective and Preventative Maintenance Year 2 through Year 15: - Factory depot equipment repair/replacement support for P25 system infrastructure and dispatch console equipment - Factory depot equipment repair/replacement support for microwave backhaul equipment - Telephone technical support for P25 system infrastructure, microwave backhaul system, and software/firmware support $ 999, $ - Year 5 System Technology Refresh Update $ 496, $ - Year 10 System Technology Refresh Update $ 627, $ - *Total Extended Maintenance and Technology Refresh $ 2,123, Total Cost of Ownership $ 7,623, * Extended Maintenance and Technology Refresh will be invoiced annually at $151, years 2 through 15. p. 384 Motorola Solutions Confidential Restricted Negotiated Cost Proposal 8-3

300 8.2 NEGOTIATED SUBSCRIBER PRICING 8-4 Negotiated Cost Proposal Motorola Solutions Confidential Restricted p. 385

301 p. 386 Motorola Solutions Confidential Restricted Negotiated Cost Proposal 8-5

302 8-6 Negotiated Cost Proposal Motorola Solutions Confidential Restricted p. 387

303 p. 388 Motorola Solutions Confidential Restricted Negotiated Cost Proposal 8-7

304 8-8 Negotiated Cost Proposal Motorola Solutions Confidential Restricted p. 389

305 p. 390 Motorola Solutions Confidential Restricted Negotiated Cost Proposal 8-9

306 8-10 Negotiated Cost Proposal Motorola Solutions Confidential Restricted p. 391