The URL can be used to link to this page

Browse Search

Home My WebLink About20131010.tiffRESOLUTION RE: APPROVE COMMUNICATIONS SYSTEM AGREEMENT AND AUTHORIZE CHAIR TO SIGN - MOTOROLA SOLUTIONS, INC. WHEREAS, the Board of County Commissioners of Weld County, Colorado, pursuant to Colorado statute and the Weld County Home Rule Charter, is vested with the authority of administering the affairs of Weld County, Colorado, and WHEREAS, the Board has been presented with a Communications System Agreement, among the County of Weld, State of Colorado, by and through the Board of County Commissioners of Weld County, on behalf of the Weld County Regional Communications Center, the Weld County E911 Authority Board and Motorola Solutions, Inc., with terms and conditions being as stated in said agreement, and WHEREAS, after review, the Board deems it advisable to approve said agreement, a copy of which is attached hereto and incorporated herein by reference. NOW, THEREFORE, BE IT RESOLVED by the Board of County Commissioners of Weld County, Colorado, that the Communications System Agreement among the County of Weld, State of Colorado, by and through the Board of County Commissioners of Weld County, on behalf of the Weld County Regional Communications Center, the Weld County E911 Authority Board and Motorola Solutions, Inc., be, and hereby is, approved. BE IT FURTHER RESOLVED by the Board that the Chair of the Board of County Commissioners is authorized to sign said agreement. The above and foregoing Resolution was, on motion duly made and seconded, adopted by the following vote on the 29th day of April, A.D., 2013. BOARD OF COUNTY COMMISSIONERS ATTEST:+ e'"^-°-°` Weld County Clerk to the Boar BY: Deputy Clerk : the Board WELD COU T , COLORADO gl-s Radem=cher, Pro-Tem Sean P. Conway APB'�`�-- y s tthrney Date of signature: MAY 1 4 2013 2- trti°3 VIA.tat Wallace, Mike Freeman CL mat witiArAte2 slap 2013-1010 CM0022 QMOTOROLA SOLUTIONS Motorola Solutions, Inc_ 7237 Church Ranch Blvd Suite 406 Westminster, CO 80021 April 23m. 2013 Mike Wallace Director of Public Safety Communications Weld County 1950 O Street Greeley, CO 80631 RE: Motorola MCC7500 Console, Master Site and S/W Upgrades Dear Mr. Wallace: Motorola Solutions, Inc. ("Motorola") is pleased to have the opportunity to provide Weld County with quality conununication equipment and services. The Motorola project team has taken great care to propose a solution to address your needs and provide unsurpassed value. Motorola's solution includes a combination of hardware. software, and services. Specifically, this solution provides the following: • 14 positions of MCC7500 IP based console in the new Prime Center. • M3 Master Site with ISSI.1 • S/W Upgrades for Weld County Consoles and RF Sites • Installation and Optimization Services This proposal includes this cover letter and is subject to: (i) the terms and conditions of the attached Communications System Agreement, together with its Exhibits; and, (ii) Motorola's proposal to Adams County Communication Center, Inc. for MCC7500s Console and S/W Upgrades. dated April 23rd, 2013 being accepted and a contract entered into between the parties. This proposal shall remain valid for a period of 60 days from the date of this cover letter. Motorola would be pleased to address any concerns the County may have regarding the proposal. Any questions can be directed to Lisa Mansuetti. Account Manager. at 720-441-9545. We thank you for the opportunity to furnish the County with our communications solutions and we hope to strengthen our relationship by implementing this project. Our goal is to provide you with the best products and services available in the communications industry. Sincerely, MOTOROLA SOLUTIONS, INC. Lany Mabry MSSSI Vice President & Director Sales SECTION 10 9 TERMS AND CONDITIONS Terms and Conditions are included on the pages that follow. • • Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. 0 Motorola Solutions Confidential Restricted Terms and Conditions 10-1 Communications System Agreement • • • Motorola Solutions, Inc. ("Motorola") and Weld County ("Customer") enter into this "Agreement," pursuant to which Customer will purchase and Motorola will sell the System, as described below. Motorola and Customer may be referred to individually as a "Party" and collectively as the "Parties." For good and valuable consideration, the Parties agree as follows: Section 1 EXHIBITS The exhibits listed below are incorporated into and made a part of this Agreement. In interpreting this Agreement and resolving any ambiguities, the main body of this Agreement takes precedence over the exhibits and any inconsistency between Exhibits A through E will be resolved in their listed order. Exhibit A Motorola "Software License Agreement" Exhibit B "Payment Schedule" Exhibit C "Technical and Implementation Documents" C-1 "System Description" dated April 24, 2013 C-2 "Equipment List" dated April 24, 2013 C-3 "Statement of Work" dated April 24, 2013 C-4 "Acceptance Test Plan" or "ATP" dated April 24, 2013 C-5 "Performance Schedule" dated April 24, 2013 Exhibit D Service Statement(s) of Work and "Service Terms and Conditions" (if applicable) Exhibit E "System Acceptance Certificate" Section 2 DEFINITIONS Capitalized terms used in this Agreement have the following meanings: 2.1. "Acceptance Tests" means those tests described in the Acceptance Test Plan 2.2. "Administrative User Credentials" means an account that has total access over the operating system, files, end user accounts and passwords at either the System level or box level. Customer's personnel with access to the Administrative User Credentials may be referred to as the Administrative User. 2.3. "Beneficial Use" means when Customer first uses the System or a Subsystem for operational purposes (excluding training or testing). 2.4. "Confidential Information" means any information that is disclosed in written, graphic, verbal, or machine -recognizable form, and is marked, designated, or identified at the time of disclosure as being confidential or its equivalent; or if the information is in verbal form, it is identified as confidential at the time of disclosure and is confirmed in writing within thirty (30) days of the disclosure. Confidential Information does not include any information that: is or becomes publicly known through no wrongful act of the receiving Party; is already known to the receiving Party without restriction when it is disclosed; is or becomes, rightfully and without breach of this Agreement, in the receiving Party's possession without any obligation restricting disclosure; is independently developed by the receiving Party without breach of this Agreement; or is explicitly approved for release by written authorization of the disclosing Party. 2.5. "Contract Price" means the price for the System, excluding applicable sales or similar taxes and freight charges. 2.6. "Effective Date" means that date upon which the last Party executes this Agreement. 2.7. "Equipment" means the equipment that Customer purchases from Motorola under this Agreement. Equipment that is part of the System is described in the Equipment List. Motorola.CSA.FINAL.3.7.11.revision.doc 1 Motorola Contract No. 110668 • • • 2.8. "Force Majeure" means an event, circumstance, or act of a third party that is beyond a Party's reasonable control (e.g., an act of God, an act of the public enemy, an act of a government entity, strikes or other labor disturbances, hurricanes, earthquakes, fires, floods, epidemics, embargoes, war, and riots). 2.9. "Infringement Claim" means a third party claim alleging that the Equipment manufactured by Motorola or the Motorola Software directly infringes a United States patent or copyright. 2.10. "Motorola Software" means Software that Motorola or its affiliated company owns. 2.11. "Non -Motorola Software" means Software that another party owns. 2.12. "Open Source Software" (also called "freeware" or "shareware") means software with either freely obtainable source code, license for modification, or permission for free distribution. 2.13. "Proprietary Rights" means the patents, patent applications, inventions, copyrights, trade secrets, trademarks, trade names, mask works, know-how, and other intellectual property rights in and to the Equipment and Software, including those created or produced by Motorola under this Agreement and any corrections, bug fixes, enhancements, updates or modifications to or derivative works from the Software whether made by Motorola or another party. 2.14. "Software" means the Motorola Software and Non -Motorola Software, in object code format that is furnished with the System or Equipment. 2.15. "Specifications" means the functionality and performance requirements that are described in the Technical and Implementation Documents. 2.16. "Subsystem" means a major part of the System that performs specific functions or operations. Subsystems are described in Exhibit C - Technical and Implementation Documents. 2.17. "System" means the Equipment, Software, and incidental hardware and materials that are combined together into an integrated system; the System is described in the Technical and Implementation Documents. 2.18. "System Acceptance" means the Acceptance Tests have been successfully completed. 2.19. "Warranty Period" means one (1) year from the date of System Acceptance or Beneficial Use, whichever occurs first. Section 3 SCOPE OF AGREEMENT AND TERM 3.1. SCOPE OF WORK. Motorola will provide, install and test the System, and perform its other contractual responsibilities, all in accordance with this Agreement. Customer will perform its contractual responsibilities in accordance with this Agreement. 3.2. CHANGE ORDERS. Either Party may request changes within the general scope of this Agreement. If a requested change causes an increase or decrease in the cost or time required to perform this Agreement, the Parties will agree to an equitable adjustment of the Contract Price, Performance Schedule, or both, and will reflect the adjustment in a change order. Neither Party is obligated to perform requested changes unless both Parties execute a written change order. 3.3. TERM. Unless terminated in accordance with other provisions of this Agreement or extended by mutual agreement of the Parties, the term of this Agreement begins on the Effective Date and continues until the date of Final Project Acceptance or expiration of the Warranty Period, whichever occurs last. 3.4. ADDITIONAL EQUIPMENT OR SOFTWARE. For three (3) years after the Effective Date, Customer may order additional Equipment or Software if it is then available. Each order must refer to this Agreement and must specify the pricing and delivery terms. Notwithstanding any additional or contrary Motorola.CSA.FINAL.3.7.11.revision.doc 2 Motorola Contract No. 110668 • • • terms in the order, the applicable provisions of this Agreement (except for pricing, delivery, passage of title and risk of loss to Equipment, warranty commencement, and payment terms) will govern the purchase and sale of the additional Equipment or Software. Title and risk of loss to additional Equipment will pass at shipment, warranty will commence upon delivery, and payment is due within twenty (20) days after the invoice date. Motorola will send Customer an invoice as the additional Equipment is shipped or Software is licensed. Alternatively, Customer may register with and place orders through Motorola Online ("MOL"), and this Agreement will be the "Underlying Agreement" for those MOL transactions rather than the MOL On -Line Terms and Conditions of Sale. MOL registration and other information may be found at https://businessonline.motorola.com and the MOL telephone number is (800) 814-0601. 3.5. MAINTENANCE SERVICE. During the Warranty Period, in addition to warranty services, Motorola will provide maintenance services for the Equipment and support for the Motorola Software pursuant to the Statement of Work set forth in Exhibit D. Those services and support are included in the Contract Price. If Customer wishes to purchase additional maintenance and support services for the Equipment during the Warranty Period, or any maintenance and support services for the Equipment either during the Warranty Period or after the Warranty Period, the description of and pricing for the services will be set forth in a separate document. If Customer wishes to purchase extended support for the Motorola Software after the Warranty Period, it may do so by ordering software subscription services. Unless otherwise agreed by the parties in writing, the terms and conditions applicable to those maintenance, support or software subscription services will be Motorola's standard Service Terms and Conditions, together with the appropriate statements of work. 3.6. MOTOROLA SOFTWARE. Any Motorola Software, including subsequent releases, is licensed to Customer solely in accordance with the Software License Agreement. Customer hereby accepts and agrees to abide by all of the terms and restrictions of the Software License Agreement. 3.7. NON -MOTOROLA SOFTWARE. Any Non -Motorola Software is licensed to Customer in accordance with the standard license, terms, and restrictions of the copyright owner on the Effective Date unless the copyright owner has granted to Motorola the right to sublicense the Non -Motorola Software pursuant to the Software License Agreement, in which case it applies and the copyright owner will have all of Licensor's rights and protections under the Software License Agreement. Motorola makes no representations or warranties of any kind regarding Non -Motorola Software. Non -Motorola Software may include Open Source Software. All Open Source Software is licensed to Customer in accordance with, and Customer agrees to abide by, the provisions of the standard license of the copyright owner and not the Software License Agreement. Upon request by Customer, Motorola will use commercially reasonable efforts to determine whether any Open Source Software will be provided under this Agreement; and if so, identify the Open Source Software and provide to Customer a copy of the applicable standard license (or specify where that license may be found); and provide to Customer a copy of the Open Source Software source code if it is publicly available without charge (although a distribution fee or a charge for related services may be applicable). 3.8. SUBSTITUTIONS. At no additional cost to Customer, Motorola may substitute any Equipment, Software, or services to be provided by Motorola, if the substitute meets or exceeds the Specifications and is of equivalent or better quality to the Customer. Any substitution will be reflected in a change order. 3.9. OPTIONAL EQUIPMENT OR SOFTWARE. This paragraph applies only if a "Priced Options" exhibit is shown in Section 1, or if the parties amend this Agreement to add a Priced Options exhibit. During the term of the option as stated in the Priced Options exhibit (or if no term is stated, then for one (1) year after the Effective Date), Customer has the right and option to purchase the equipment, software, and related services that are described in the Priced Options exhibit. Customer may exercise this option by giving written notice to Seller which must designate what equipment, software, and related services Customer is selecting (including quantities, if applicable). To the extent they apply, the terms and conditions of this Agreement will govern the transaction; however, the parties acknowledge that certain provisions must be agreed upon, and they agree to negotiate those in good faith promptly after Customer delivers the option exercise notice. Examples of provisions that may need to be negotiated are: specific lists of deliverables, statements of work, acceptance test plans, delivery and implementation schedules, Motorola.CSA.FINAL.3.7. 11.revision.doc 3 Motorola Contract No. 110668 • • • payment terms, maintenance and support provisions, additions to or modifications of the Software License Agreement, hosting terms, and modifications to the acceptance and warranty provisions. Section 4 PERFORMANCE SCHEDULE The Parties will perform their respective responsibilities in accordance with the Performance Schedule. By executing this Agreement, Customer authorizes Motorola to proceed with contract performance. Section 5 CONTRACT PRICE, PAYMENT AND INVOICING 5.1. CONTRACT PRICE. The Contract Price in U.S. dollars is $ 3,071,301 . If applicable, a pricing summary is included with the Payment Schedule. Motorola has priced the services, Software, and Equipment as an integrated system. A reduction in Software or Equipment quantities, or services, may affect the overall Contract Price, including discounts if applicable. 5.2. INVOICING AND PAYMENT. Motorola will submit invoices to Customer according to the Payment Schedule. Except for a payment that is due on the Effective Date, Customer will make payments to Motorola within 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. Overdue invoices will bear simple interest at the maximum allowable rate. For reference, the Federal Tax Identification Number for Motorola Solutions, Inc. is 36-1115800. 5.3. FREIGHT, TITLE, AND RISK OF LOSS. Motorola will pre -pay and add all freight charges to the invoices. Title to the Equipment will pass to Customer upon shipment. Title to Software will not pass to Customer at any time. Risk of loss will pass to Customer upon delivery of the Equipment to the Customer. Motorola will pack and ship all Equipment in accordance with good commercial practices. 5.4. INVOICING AND SHIPPING ADDRESSES. Invoices will be sent to the Customer at the following address: 1150 O Street Greeley, CO 80631 The address which is the ultimate destination where the Equipment will be delivered to Customer is: Same as above The Equipment will be shipped to the Customer at the following address (insert if this information is known): Wireless Advanced Communications 3901 East Service Road Evans, CO 80620 Customer may change this information by giving written notice to Motorola. Section 6 SITES AND SITE CONDITIONS 6.1. ACCESS TO SITES. In addition to its responsibilities described elsewhere in this Agreement, Customer will provide a designated project manager; all necessary construction and building permits, zoning variances, licenses, and any other approvals that are necessary to develop or use the sites and mounting locations; and access to the work sites or vehicles identified in the Technical and Implementation Documents as reasonably requested by Motorola so that it may perform its duties in accordance with the Performance Schedule and Statement of Work. If the Statement of Work so indicates, Motorola may assist Customer in the local building permit process. 6.2. SITE CONDITIONS. Customer will ensure that all work sites it provides will be safe, secure, and in compliance with all applicable industry and OSHA standards. To the extent applicable and unless the Statement of Work states to the contrary, Customer will ensure that these work sites have adequate: Motorola.CSA.FINAL.3.7.11.revision.doc 4 Motorola Contract No. 110668 • • physical space; air conditioning and other environmental conditions; adequate and appropriate electrical power outlets, distribution, equipment and connections; and adequate telephone or other communication lines (including modem access and adequate interfacing networking capabilities), all for the installation, use and maintenance of the System. Before installing the Equipment or Software at a work site, Motorola may inspect the work site and advise Customer of any apparent deficiencies or non -conformities with the requirements of this Section. This Agreement is predicated upon normal soil conditions as defined by the version of E.I.A. standard RS -222 in effect on the Effective Date. 6.3. SITE ISSUES. If a Party determines that the sites identified in the Technical and Implementation Documents are no longer available or desired, or if subsurface, structural, adverse environmental or latent conditions at any site differ from those indicated in the Technical and Implementation Documents, the Parties will promptly investigate the conditions and will select replacement sites or adjust the installation plans and specifications as necessary. If change in sites or adjustment to the installation plans and specifications causes a change in the cost or time to perform, the Parties will equitably amend the Contract Price, Performance Schedule, or both, by a change order. Section 7 TRAINING Any training to be provided by Motorola to Customer will be described in the Technical and Implementation Documents. Customer will notify Motorola immediately if a date change for a scheduled training program is required. If Motorola incurs additional costs because Customer reschedules a training program less than thirty (30) days before its scheduled start date, Motorola may recover these additional costs. Section 8 SYSTEM ACCEPTANCE 8.1. COMMENCEMENT OF ACCEPTANCE TESTING. Motorola will provide to Customer at least ten (10) days notice before the Acceptance Tests commence. System testing will occur only in accordance with the Acceptance Test Plan. 8.2. SYSTEM ACCEPTANCE. System Acceptance will occur upon successful completion of the Acceptance Tests. Upon System Acceptance, the Parties will memorialize this event by promptly executing a System Acceptance Certificate. If the Acceptance Test Plan includes separate tests for individual Subsystems or phases of the System, acceptance of the individual Subsystem or phase will occur upon the successful completion of the Acceptance Tests for the Subsystem or phase, and the Parties will promptly execute an acceptance certificate for the Subsystem or phase. If Customer believes the System has failed the completed Acceptance Tests, Customer will provide to Motorola a written notice that includes the specific details of the failure. If Customer does not provide to Motorola a failure notice within thirty (30) days after completion of the Acceptance Tests, System Acceptance will be deemed to have occurred as of the completion of the Acceptance Tests. Minor omissions or variances in the System that do not materially impair the operation of the System as a whole will not postpone System Acceptance or Subsystem acceptance, but will be corrected according to a mutually agreed schedule. 8.3. BENEFICIAL USE. Customer acknowledges that Motorola's ability to perform its implementation and testing responsibilities may be impeded if Customer begins using the System before System Acceptance. Therefore, Customer will not commence Beneficial Use before System Acceptance without Motorola's prior written authorization, which will not be unreasonably withheld. Motorola is not responsible for System performance deficiencies that occur during unauthorized Beneficial Use. Upon commencement of Beneficial Use, Customer assumes responsibility for the use and operation of the System. 8.4 FINAL PROJECT ACCEPTANCE. Final Project Acceptance will occur after System Acceptance when all deliverables and other work have been completed. When Final Project Acceptance occurs, the parties will promptly memorialize this final event by so indicating on the System Acceptance Certificate. Section 9 REPRESENTATIONS AND WARRANTIES Motorola.CSA. FINAL.3.7.11. revision.doc Motorola Contract No. 110668 5 • • 9.1. SYSTEM FUNCTIONALITY. Motorola represents that the System will perform in accordance with the Specifications in all material respects. Upon System Acceptance or Beneficial Use, whichever occurs first, this System functionality representation is fulfilled. Motorola is not responsible for System performance deficiencies that are caused by ancillary equipment not furnished by Motorola which is attached to or used in connection with the System or for reasons or parties beyond Motorola's control, such as natural causes; the construction of a building that adversely affects the microwave path reliability or radio frequency (RF) coverage; the addition of frequencies at System sites that cause RF interference or intermodulation; or Customer changes to load usage or configuration outside the Specifications. 9.2. EQUIPMENT WARRANTY. During the Warranty Period, Motorola warrants that the Equipment under normal use and service will be free from material defects in materials and workmanship. If System Acceptance is delayed beyond six (6) months after shipment of the Equipment by events or causes within Customer's control, this warranty expires eighteen (18) months after the shipment of the Equipment. 9.3. MOTOROLA SOFTWARE WARRANTY. Unless otherwise stated in the Software License Agreement, during the Warranty Period, Motorola warrants the Motorola Software in accordance with the terms of the Software License Agreement and the provisions of this Section 9 that are applicable to the Motorola Software. If System Acceptance is delayed beyond six (6) months after shipment of the Motorola Software by events or causes within Customer's control, this warranty expires eighteen (18) months after the shipment of the Motorola Software. TO THE EXTENT, IF ANY, THAT THERE IS A SEPARATE LICENSE AGREEMENT PACKAGED WITH, OR PROVIDED ELECTRONICALLY WITH, A PARTICULAR PRODUCT THAT BECOMES EFFECTIVE ON AN ACT OF ACCEPTANCE BY THE END USER, THEN THAT AGREEMENT SUPERCEDES THE ATTACHED SOFTWARE LICENSE AGREEMENT AS TO THE END USER OF EACH SUCH PRODUCT. 9.4. EXCLUSIONS TO EQUIPMENT AND MOTOROLA SOFTWARE WARRANTIES. These warranties do not apply to: (i) defects or damage resulting from: use of the Equipment or Motorola Software in other than its normal, customary, and authorized manner; accident, liquids, neglect, or acts of God; testing, maintenance, disassembly, repair, installation, alteration, modification, or adjustment not provided or authorized in writing by Motorola; Customer's failure to comply with all applicable industry and OSHA standards; (ii) breakage of or damage to antennas unless caused directly by defects in material or workmanship; (iii) Equipment that has had the serial number removed or made illegible; (iv) batteries (because they carry their own separate limited warranty) or consumables; (v) freight costs to ship Equipment to the repair depot; (vi) scratches or other cosmetic damage to Equipment surfaces that does not affect the operation of the Equipment; and (vii) normal or customary wear and tear. 9.5. WARRANTY CLAIMS. To assert a warranty claim, Customer must notify Motorola in writing of the claim before the expiration of the Warranty Period. Upon receipt of this notice, Motorola will investigate the warranty claim. If this investigation confirms a valid warranty claim, Motorola will (at its option and at no additional charge to Customer) repair the defective Equipment or Motorola Software, replace it with the same or equivalent product, or refund the price of the defective Equipment or Motorola Software. That action will be the full extent of Motorola's liability for the warranty claim. If this investigation indicates the warranty claim is not valid, then Motorola may invoice Customer for responding to the claim on a time and materials basis using Motorola's then current labor rates. Repaired or replaced product is warranted for the balance of the original applicable warranty period. All replaced products or parts will become the property of Motorola. 9.6. ORIGINAL END USER IS COVERED. These express limited warranties are extended by Motorola to the original user purchasing the System for commercial, industrial, or governmental use only, and are not assignable or transferable. 9.7. DISCLAIMER OF OTHER WARRANTIES. THESE WARRANTIES ARE THE COMPLETE WARRANTIES FOR THE EQUIPMENT AND MOTOROLA SOFTWARE PROVIDED UNDER THIS AGREEMENT AND ARE GIVEN IN LIEU OF ALL OTHER WARRANTIES. MOTOROLA DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Motorola.CSA.FINAL.3.7.11.revision.doc 6 Motorola Contract No. 110668 • • • Section 10 DELAYS 10.1. FORCE MAJEURE. Neither Party will be liable for its non-performance or delayed performance if caused by a Force Majeure. A Party that becomes aware of a Force Majeure that will significantly delay performance will notify the other Party promptly (but in no event later than fifteen days) after it discovers the Force Majeure. If a Force Majeure occurs, the Parties will execute a change order to extend the Performance Schedule for a time period that is reasonable under the circumstances. 10.2. PERFORMANCE SCHEDULE DELAYS CAUSED BY CUSTOMER. If Customer (including its other contractors) delays the Performance Schedule, it will make the promised payments according to the Payment Schedule as if no delay occurred; and the Parties will execute a change order to extend the Performance Schedule and, if requested, compensate Motorola for all reasonable charges incurred because of the delay. Delay charges may include costs incurred by Motorola or its subcontractors for additional freight, warehousing and handling of Equipment; extension of the warranties; travel; suspending and re -mobilizing the work; additional engineering, project management, and standby time calculated at then current rates; and preparing and implementing an alternative implementation plan. Section 11 DISPUTES The Parties will use the following procedure to address any dispute arising under this Agreement (a "Dispute"). 11.1. GOVERNING LAW. This Agreement will be governed by and construed in accordance with the laws of the State in which the System is installed. 11.2. NEGOTIATION. Either Party may initiate the Dispute resolution procedures by sending a notice of Dispute ("Notice of Dispute"). The Parties will attempt to resolve the Dispute promptly through good faith negotiations including 1) timely escalation of the Dispute to executives who have authority to settle the Dispute and who are at a higher level of management than the persons with direct responsibility for the matter and 2) direct communication between the executives. If the Dispute has not been resolved within ten (10) days from the Notice of Dispute, the Parties will proceed to mediation. 11.3 MEDIATION. The Parties will choose an independent mediator within thirty (30) days of a notice to mediate from either Party ("Notice of Mediation"). Neither Party may unreasonably withhold consent to the selection of a mediator. If the Parties are unable to agree upon a mediator, either Party may request that American Arbitration Association nominate a mediator. Each Party will bear its own costs of mediation, but the Parties will share the cost of the mediator equally. Each Party will participate in the mediation in good faith and will be represented at the mediation by a business executive with authority to settle the Dispute. 11.4. LITIGATION, VENUE and JURISDICTION. If a Dispute remains unresolved for sixty (60) days after receipt of the Notice of Mediation, either Party may then submit the Dispute to a court of competent jurisdiction in the state in which the System is installed. Each Party irrevocably agrees to submit to the exclusive jurisdiction of the courts in such state over any claim or matter arising under or in connection with this Agreement. 11.5. CONFIDENTIALITY. All communications pursuant to subsections 11.2 and 11.3 will be treated as compromise and settlement negotiations for purposes of applicable rules of evidence and any additional confidentiality protections provided by applicable law. The use of these Dispute resolution procedures will not be construed under the doctrines of laches, waiver or estoppel to affect adversely the rights of either Party. Section 12 DEFAULT AND TERMINATION 12.1 DEFAULT BY A PARTY. If either Party fails to perform a material obligation under this Agreement, the other Party may consider the non -performing Party to be in default (unless a Force Motorola.CSA.FINAL.3.7.11.revision.doc 7 Motorola Contract No. 110668 • • Majeure causes the failure) and may assert a default claim by giving the non -performing Party a written and detailed notice of default. Except for a default by Customer for failing to pay any amount when due under this Agreement which must be cured immediately, the defaulting Party will have thirty (30) days after receipt of the notice of default to either cure the default or, if the default is not curable within thirty (30) days, provide a written cure plan. The defaulting Party will begin implementing the cure plan immediately after receipt of notice by the other Party that it approves the plan. If Customer is the defaulting Party, Motorola may stop work on the project until it approves the Customer's cure plan. 12.2. FAILURE TO CURE. If a defaulting Party fails to cure the default as provided above in Section 12.1, unless otherwise agreed in writing, the non -defaulting Party may terminate any unfulfilled portion of this Agreement. In the event of termination for default, the defaulting Party will promptly return to the non - defaulting Party any of its Confidential Information. If Customer is the non -defaulting Party, terminates this Agreement as permitted by this Section, and completes the System through a third Party, Customer may as its exclusive remedy recover from Motorola reasonable costs incurred to complete the System to a capability not exceeding that specified in this Agreement less the unpaid portion of the Contract Price. Customer will mitigate damages and provide Motorola with detailed invoices substantiating the charges. Section 13 INDEMNIFICATION 13.1. GENERAL INDEMNITY BY MOTOROLA. Motorola will indemnify and hold Customer harmless from any and all liability, expense, judgment, suit, cause of action, or demand for personal injury, death, or direct damage to tangible property which may accrue against Customer to the extent it is caused by the negligence of Motorola, its subcontractors, or their employees or agents, while performing their duties under this Agreement, if Customer gives Motorola prompt, written notice of any the claim or suit. Customer will cooperate with Motorola in its defense or settlement of the claim or suit. This section sets forth the full extent of Motorola's general indemnification of Customer from liabilities that are in any way related to Motorola's performance under this Agreement. 13.2. GENERAL INDEMNITY BY CUSTOMER. (Deleted) 13.3. PATENT AND COPYRIGHT INFRINGEMENT. 13.3.1. Motorola will defend at its expense any suit brought against Customer to the extent it is based on a third -party claim alleging that the Equipment manufactured by Motorola or the Motorola Software ("Motorola Product") directly infringes a United States patent or copyright ("Infringement Claim"). Motorola's duties to defend and indemnify are conditioned upon: Customer promptly notifying Motorola in writing of the Infringement Claim; Motorola having sole control of the defense of the suit and all negotiations for its settlement or compromise; and Customer providing to Motorola cooperation and, if requested by Motorola, reasonable assistance in the defense of the Infringement Claim. In addition to Motorola's obligation to defend, and subject to the same conditions, Motorola will pay all damages finally awarded against Customer by a court of competent jurisdiction for an Infringement Claim or agreed to, in writing, by Motorola in settlement of an Infringement Claim. 13.3.2. If an Infringement Claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its option and expense: (a) procure for Customer the right to continue using the Motorola Product; (b) replace or modify the Motorola Product so that it becomes non -infringing while providing functionally equivalent performance; or (c) accept the return of the Motorola Product and grant Customer a credit for the Motorola Product, less a reasonable charge for depreciation. The depreciation amount will be calculated based upon generally accepted accounting standards. 13.3.3. Motorola will have no duty to defend or indemnify for any Infringement Claim that is based upon: (a) the combination of the Motorola Product with any software, apparatus or device not furnished by Motorola; (b) the use of ancillary equipment or software not furnished by Motorola and that is attached to or used in connection with the Motorola Product; (c) Motorola Product designed or manufactured in accordance with Customer's designs, specifications, guidelines or instructions, if the alleged infringement would not have occurred without such designs, specifications, guidelines or instructions; (d) a modification of the Motorola Product by a party other than Motorola; (e) use of the Motorola Product in a Motorola.CSA.FINAL.3.7.11.revision.doc 8 Motorola Contract No. 110668 • • manner for which the Motorola Product was not designed or that is inconsistent with the terms of this Agreement; or (f) the failure by Customer to install an enhancement release to the Motorola Software that is intended to correct the claimed infringement. In no event will Motorola's liability resulting from its indemnity obligation to Customer extend in any way to royalties payable on a per use basis or the Customer's revenues, or any royalty basis other than a reasonable royalty based upon revenue derived by Motorola from Customer from sales or license of the infringing Motorola Product. 13.3.4. This Section 13 provides Customer's sole and exclusive remedies and Motorola's entire liability in the event of an Infringement Claim. Customer has no right to recover and Motorola has no obligation to provide any other or further remedies, whether under another provision of this Agreement or any other legal theory or principle, in connection with an Infringement Claim. In addition, the rights and remedies provided in this Section 13 are subject to and limited by the restrictions set forth in Section 14. Section 14 LIMITATION OF LIABILITY Except for personal injury or death, Motorola's total liability, whether for breach of contract, warranty, negligence, strict liability in tort, indemnification, or otherwise, will be limited to the direct damages recoverable under law, but not to exceed the price of the Equipment, Software, or services with respect to which losses or damages are claimed. ALTHOUGH THE PARTIES ACKNOWLEDGE THE POSSIBILITY OF SUCH LOSSES OR DAMAGES, THEY AGREE THAT MOTOROLA WILL NOT BE LIABLE FOR ANY COMMERCIAL LOSS; INCONVENIENCE; LOSS OF USE, TIME, DATA, GOOD WILL, REVENUES, PROFITS OR SAVINGS; OR OTHER SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES IN ANY WAY RELATED TO OR ARISING FROM THIS AGREEMENT, THE SALE OR USE OF THE EQUIPMENT OR SOFTWARE, OR THE PERFORMANCE OF SERVICES BY MOTOROLA PURSUANT TO THIS AGREEMENT. This limitation of liability provision survives the expiration or termination of the Agreement and applies notwithstanding any contrary provision. No action for contract breach or otherwise relating to the transactions contemplated by this Agreement may be brought more than one (1) year after the accrual of the cause of action, except for money due upon an open account. Section 15 CONFIDENTIALITY AND PROPRIETARY RIGHTS 15.1. CONFIDENTIAL INFORMATION. During the term of this Agreement, the Parties may provide each other with Confidential Information. To the extent allowed by Colorado law, each Party will: maintain the confidentiality of the other Party's Confidential Information and not disclose it to any third party, except as authorized by the disclosing Party in writing or as required by a court of competent jurisdiction; restrict disclosure of the Confidential Information to its employees who have a "need to know" and not copy or reproduce the Confidential Information; take necessary and appropriate precautions to guard the confidentiality of the Confidential Information, including informing its employees who handle the Confidential Information that it is confidential and is not to be disclosed to others, but these precautions will be at least the same degree of care that the receiving Party applies to its own confidential information and will not be less than reasonable care; and use the Confidential Information only in furtherance of the performance of this Agreement. Confidential Information is and will at all times remain the property of the disclosing Party, and no grant of any proprietary rights in the Confidential Information is given or intended, including any express or implied license, other than the limited right of the recipient to use the Confidential Information in the manner and to the extent permitted by this Agreement. 15.2. PRESERVATION OF MOTOROLA'S PROPRIETARY RIGHTS. Motorola, the third party manufacturer of any Equipment, and the copyright owner of any Non -Motorola Software own and retain all of their respective Proprietary Rights in the Equipment and Software, and nothing in this Agreement is intended to restrict their Proprietary Rights. All intellectual property developed, originated, or prepared by Motorola in connection with providing to Customer the Equipment, Software, or related services remain vested exclusively in Motorola, and this Agreement does not grant to Customer any shared development rights of intellectual property. Except as explicitly provided in the Software License Agreement, Motorola does not grant to Customer, either directly or by implication, estoppel, or otherwise, any right, title or interest in Motorola's Proprietary Rights. Customer will not modify, disassemble, peel components, decompile, otherwise reverse engineer or attempt to reverse engineer, derive source code or create derivative works from, adapt, translate, merge with other software, reproduce, distribute, sublicense, sell Motorola.CSA.FINAL.3.7.11.revision.doc 9 Motorola Contract No. 110668 • • or export the Software, or permit or encourage any third party to do so. The preceding sentence does not apply to Open Source Software which is governed by the standard license of the copyright owner. Section 16 GENERAL 16.1. TAXES. The Contract Price does not include any excise, sales, lease, use, property, or other taxes, assessments or duties, all of which will be paid by Customer except as exempt by law. If Motorola is required to pay any of these taxes, Motorola will send an invoice to Customer and Customer will pay to Motorola the amount of the taxes (including any interest and penalties) within thirty (30) days after the date of the invoice. Customer will be solely responsible for reporting the Equipment for personal property tax purposes, and Motorola will be solely responsible for reporting taxes on its income or net worth. 16.2. ASSIGNABILITY AND SUBCONTRACTING. Except as provided herein, neither Party may assign this Agreement or any of its rights or obligations hereunder without the prior written consent of the other Party, which consent will not be unreasonably withheld. Any attempted assignment, delegation, or transfer without the necessary consent will be void. Notwithstanding the foregoing, Motorola may assign this Agreement to any of its affiliates or its right to receive payment without the prior consent of Customer. In addition, in the event Motorola separates one or more of its businesses (each a "Separated Business"), whether by way of a sale, establishment of a joint venture, spin-off or otherwise (each a "Separation Event"), Motorola may, without the prior written consent of the other Party and at no additional cost to Motorola, assign this Agreement such that it will continue to benefit the Separated Business and its affiliates (and Motorola and its affiliates, to the extent applicable) following the Separation Event. Motorola may subcontract any of the work, but subcontracting will not relieve Motorola of its duties under this Agreement. 16.3 WAIVER. Failure or delay by either Party to exercise a right or power under this Agreement will not be a waiver of the right or power. For a waiver of a right or power to be effective, it must be in a writing signed by the waiving Party. An effective waiver of a right or power will not be construed as either a future or continuing waiver of that same right or power, or the waiver of any other right or power. 16.4. SEVERABILITY. If a court of competent jurisdiction renders any part of this Agreement invalid or unenforceable, that part will be severed and the remainder of this Agreement will continue in full force and effect. 16.5. INDEPENDENT CONTRACTORS. Each Party will perform its duties under this Agreement as an independent contractor. The Parties and their personnel will not be considered to be employees or agents of the other Party. Nothing in this Agreement will be interpreted as granting either Party the right or authority to make commitments of any kind for the other. This Agreement will not constitute, create, or be interpreted as a joint venture, partnership or formal business organization of any kind. 16.6. HEADINGS AND SECTION REFERENCES. The section headings in this Agreement are inserted only for convenience and are not to be construed as part of this Agreement or as a limitation of the scope of the particular section to which the heading refers. This Agreement will be fairly interpreted in accordance with its terms and conditions and not for or against either Party. 16.7. ENTIRE AGREEMENT. This Agreement, including all Exhibits, constitutes the entire agreement of the Parties regarding the subject matter of the Agreement and supersedes all previous agreements, proposals, and understandings, whether written or oral, relating to this subject matter. This Agreement may be executed in multiple counterparts, each of which shall be an original and all of which shall constitute one and the same instrument. A facsimile copy or computer image, such as a PDF or tiff image, or a signature shall be treated as and shall have the same effect as an original signature. In addition, 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. 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. Motorola.CSA.FINAL.3.7.11.revision.doc 10 Motorola Contract No. 110668 • • • 16.8. NOTICES. Notices required under this Agreement to be given by one Party to the other must be in writing and either personally delivered or sent to the address shown below by certified mail, return receipt requested and postage prepaid (or by a recognized courier service, such as Federal Express, UPS, or DHL), or by facsimile with correct answerback received, or by personal service, and will be effective upon receipt: Motorola Solutions, Inc. Attn: Law Department 1301 E. Algonquin Road IL01-8'" fl Schaumburg, IL 60196 fax: 847-576-0721 Weld County Regional Communications Center Attn: Mike Wallace 1150 O Street Greeley, CO 80631 fax: (970) 304-6501 16.9. COMPLIANCE WITH APPLICABLE LAWS. Each Party will comply with all applicable federal, state, and local laws, regulations and rules concerning the performance of this Agreement or use of the System. Customer will obtain and comply with all Federal Communications Commission ("FCC") licenses and authorizations required for the installation, operation and use of the System before the scheduled installation of the Equipment. Although Motorola might assist Customer in the preparation of its FCC license applications, neither Motorola nor any of its employees is an agent or representative of Customer in FCC or other matters. 16.10. AUTHORITY TO EXECUTE AGREEMENT. Each Party represents that it has obtained all necessary approvals, consents and authorizations to enter into this Agreement and to perform its duties under this Agreement; the person executing this Agreement on its behalf has the authority to do so; upon execution and delivery of this Agreement by the Parties, it is a valid and binding contract, enforceable in accordance with its terms; and the execution, delivery, and performance of this Agreement does not violate any bylaw, charter, regulation, law or any other governing authority of the Party. 16.11. ADMINISTRATOR LEVEL ACCOUNT ACCESS. Motorola will provide Customer with Administrative User Credentials. Customer agrees to only grant Administrative User Credentials to those personnel with the training or experience to correctly use the access. Customer is responsible for protecting Administrative User Credentials from disclosure and maintaining Credential validity by, among other things, updating passwords when required. Customer may be asked to provide valid Administrative User Credentials when in contact with Motorola System support. Customer understands that changes made as the Administrative User can significantly impact the performance of the System. Customer agrees that it will be solely responsible for any negative impact on the System or its users by any such changes. System issues occurring as a result of changes made by an Administrative User may impact Motorola's ability to perform its obligations under the Agreement or its Maintenance and Support Agreement. In such cases, a revision to the appropriate provisions of the Agreement, including the Statement of Work, may be necessary. To the extent Motorola provides assistance to correct any issues caused by or arising out of the use of or failure to maintain Administrative User Credentials, Motorola will be entitled to bill Customer and Customer will pay Motorola on a time and materials basis for resolving the issue. 16.12. SURVIVAL OF TERMS. The following provisions will survive the expiration or termination of this Agreement for any reason: Section 3.6 (Motorola Software); Section 3.7 (Non -Motorola Software); if any payment obligations exist, Sections 5.1 and 5.2 (Contract Price and Invoicing and Payment); Subsection 9.7 (Disclaimer of Implied Warranties); Section 11 (Disputes); Section 14 (Limitation of Liability); and Section 15 (Confidentiality and Proprietary Rights); and all of the General provisions in Section 16. 16.13 FUNDING CONTINGENCY. No portion of this Agreement shall be deemed to create an obligation on the part of the Customer to expend funds not otherwise appropriated or budgeted for. Customer shall provide evidence of appropriated funds prior to the shipment of equipment or the performance of services associated with this agreement. Motorola shall also be entitled to receive just and equitable compensation for work in progress, work completed and materials accepted by the Customer. Motorola.CSA.FINAL.3.7.11.revision.doc 11 Motorola Contract No. 110668 • • • APR 2 9 2013 16.14 GOVERNMENTAL IMMUNITY. No portion of this Agreement shall be deemed to constitute a waiver of any immunities the Customer or its officers or employees may possess under federal or state constitutional, statutory or common law. The Parties hereby e into this Agreement as of the Effective Date. Motorola Solution (lr�c., 4 / \ / Customer: Weld County By: Name: Title: Date: By: sales Name: illiam F. Garcia Title:Ctha}r, Board of Weld County Commissioners Date: APR 2 9 2013 Weld County has requested and Weld County 911 Authority agrees that: Weld County will be invoiced for the Master Site at a price of $1,744,057 and Weld County 911 Authority will be invoiced for the MCC7500 and S/W upgrades at a price of $1,327,244. Such invoicing shall in no way effect Weld County's liabilities and obligations under this Agreement. Weld County - j Weld County 911 Authority 7 B Nome: Title: Date: APR 2 9 2013 Motorola.CSA.FINAL.3.7.11.revision.doc NAL.3.7.11. revision.doc Motorola Contract No. 110668 12 • • • Exhibit A SOFTWARE LICENSE AGREEMENT This Exhibit A Software License Agreement ("Agreement") is between Motorola Solutions, Inc., ("Motorola"), and Weld County ("Licensee"). For good and valuable consideration, the parties agree as follows: Section 1 DEFINITIONS 1.1 "Designated Products" means products provided by Motorola to Licensee with which or for which the Software and Documentation is licensed for use. 1.2 "Documentation" means product and software documentation that specifies technical and performance features and capabilities, and the user, operation and training manuals for the Software (including all physical or electronic media upon which such information is provided). 1.3 "Open Source Software" means software with either freely obtainable source code, license for modification, or permission for free distribution. 1.4 "Open Source Software License" means the terms or conditions under which the Open Source Software is licensed. 1.5 "Primary Agreement" means the agreement to which this exhibit is attached 1.6 "Security Vulnerability" means a flaw or weakness in system security procedures, design, implementation, or internal controls that could be exercised (accidentally triggered or intentionally exploited) and result in a security breach such that data is compromised, manipulated or stolen or the system damaged. 1.7 "Software" (i) means proprietary software in object code format, and adaptations, translations, de - compilations, disassemblies, emulations, or derivative works of such software; (ii) means any modifications, enhancements, new versions and new releases of the software provided by Motorola; and (iii) may contain one or more items of software owned by a third party supplier. The term "Software" does not include any third party software provided under separate license or third party software not licensable under the terms of this Agreement. Section 2 SCOPE Motorola and Licensee enter into this Agreement in connection with Motorola's delivery of certain proprietary Software or products containing embedded or pre -loaded proprietary Software, or both. This Agreement contains the terms and conditions of the license Motorola is providing to Licensee, and Licensee's use of the Software and Documentation. Section 3 GRANT OF LICENSE 3.1. Subject to the provisions of this Agreement and the payment of applicable license fees, Motorola grants to Licensee a personal, limited, non -transferable (except as permitted in Section 7) and non- exclusive license under Motorola's copyrights and Confidential Information (as defined in the Primary Agreement) embodied in the Software to use the Software, in object code form, and the Documentation solely in connection with Licensee's use of the Designated Products. This Agreement does not grant any rights to source code. 3.2. If the Software licensed under this Agreement contains or is derived from Open Source Software, the terms and conditions governing the use of such Open Source Software are in the Open Source Motorola.CSA.FINAL.3.7.11.revision.doc 13 Motorola Contract No. 110668 • • • Software Licenses of the copyright owner and not this Agreement. If there is a conflict between the terms and conditions of this Agreement and the terms and conditions of the Open Source Software Licenses governing Licensee's use of the Open Source Software, the terms and conditions of the license grant of the applicable Open Source Software Licenses will take precedence over the license grants in this Agreement. If requested by Licensee, Motorola will use commercially reasonable efforts to: (i) determine whether any Open Source Software is provided under this Agreement; (ii) identify the Open Source Software and provide Licensee a copy of the applicable Open Source Software License (or specify where that license may be found); and, (iii) provide Licensee a copy of the Open Source Software source code, without charge, if it is publicly available (although distribution fees may be applicable). Section 4 LIMITATIONS ON USE 4.1. Licensee may use the Software only for Licensee's internal business purposes and only in accordance with the Documentation. Any other use of the Software is strictly prohibited. Without limiting the general nature of these restrictions, Licensee will not make the Software available for use by third parties on a "time sharing," "application service provider," or "service bureau" basis or for any other similar commercial rental or sharing arrangement. 4.2. Licensee will not, and will not allow or enable any third party to: (i) reverse engineer, disassemble, peel components, decompile, reprogram or otherwise reduce the Software or any portion to a human perceptible form or otherwise attempt to recreate the source code; (H) modify, adapt, create derivative works of, or merge the Software; (iii) copy, reproduce, distribute, lend, or lease the Software or Documentation to any third party, grant any sublicense or other rights in the Software or Documentation to any third party, or take any action that would cause the Software or Documentation to be placed in the public domain; (iv) remove, or in any way alter or obscure, any copyright notice or other notice of Motorola's proprietary rights; (v) provide, copy, transmit, disclose, divulge or make the Software or Documentation available to, or permit the use of the Software by any third party or on any machine except as expressly authorized by this Agreement; or (vi) use, or permit the use of, the Software in a manner that would result in the production of a copy of the Software solely by activating a machine containing the Software. Licensee may make one copy of Software to be used solely for archival, back- up, or disaster recovery purposes; provided that Licensee may not operate that copy of the Software at the same time as the original Software is being operated. Licensee may make as many copies of the Documentation as it may reasonably require for the internal use of the Software. 4.3. Unless otherwise authorized by Motorola in writing, Licensee will not, and will not enable or allow any third party to: (i) install a licensed copy of the Software on more than one unit of a Designated Product; or (ii) copy onto or transfer Software installed in one unit of a Designated Product onto one other device. Licensee may temporarily transfer Software installed on a Designated Product to another device if the Designated Product is inoperable or malfunctioning, if Licensee provides written notice to Motorola of the temporary transfer and identifies the device on which the Software is transferred. Temporary transfer of the Software to another device must be discontinued when the original Designated Product is returned to operation and the Software must be removed from the other device. Licensee must provide prompt written notice to Motorola at the time temporary transfer is discontinued. 4.4. When using Motorola's Radio Service Software ("RSS"), Licensee must purchase a separate license for each location at which Licensee uses RSS. Licensee's use of RSS at a licensed location does not entitle Licensee to use or access RSS remotely. Licensee may make one copy of RSS for each licensed location. Licensee shall provide Motorola with a list of all locations at which Licensee uses or intends to use RSS upon Motorola's request. 4.5. Licensee will maintain, during the term of this Agreement and for a period of two years thereafter, accurate records relating to this license grant to verify compliance with this Agreement. Motorola or an independent third party ("Auditor") may inspect Licensee's premises, books and records, upon reasonable prior notice to Licensee, during Licensee's normal business hours and subject to Licensee's facility and security regulations. Motorola is responsible for the payment of all expenses and costs of the Auditor. Any information obtained by Motorola and the Auditor will be kept in strict confidence by Motorola and the Motorola.CSA.FINAL.3.7. 11.revision.doc 14 Motorola Contract No. 110668 • • • Auditor and used solely for the purpose of verifying Licensee's compliance with the terms of this Agreement. Section 5 OWNERSHIP AND TITLE Motorola, its licensors, and its suppliers retain all of their proprietary rights in any form in and to the Software and Documentation, including, but not limited to, all rights in patents, patent applications, inventions, copyrights, trademarks, trade secrets, trade names, and other proprietary rights in or relating to the Software and Documentation (including any corrections, bug fixes, enhancements, updates, modifications, adaptations, translations, de -compilations, disassemblies, emulations to or derivative works from the Software or Documentation, whether made by Motorola or another party, or any improvements that result from Motorola's processes or, provision of information services). No rights are granted to Licensee under this Agreement by implication, estoppel or otherwise, except for those rights which are expressly granted to Licensee in this Agreement. All intellectual property developed, originated, or prepared by Motorola in connection with providing the Software, Designated Products, Documentation or related services, remains vested exclusively in Motorola, and Licensee will not have any shared development or other intellectual property rights. Section 6 LIMITED WARRANTY; DISCLAIMER OF WARRANTY 6.1. The commencement date and the term of the Software warranty will be a period of ninety (90) days from Motorola's shipment of the Software (the "Warranty Period"). If Licensee is not in breach of any of its obligations under this Agreement, Motorola warrants that the unmodified Software, when used properly and in accordance with the Documentation and this Agreement, will be free from a reproducible defect that eliminates the functionality or successful operation of a feature critical to the primary functionality or successful operation of the Software. Whether a defect occurs will be determined by Motorola solely with reference to the Documentation. Motorola does not warrant that Licensee's use of the Software or the Designated Products will be uninterrupted, error -free, completely free of Security Vulnerabilities, or that the Software or the Designated Products will meet Licensee's particular requirements. Motorola makes no representations or warranties with respect to any third party software included in the Software. 6.2 Motorola's sole obligation to Licensee and Licensee's exclusive remedy under this warranty is to use reasonable efforts to remedy any material Software defect covered by this warranty. These efforts will involve either replacing the media or attempting to correct significant, demonstrable program or documentation errors or Security Vulnerabilities. If Motorola cannot correct the defect within a reasonable time, then at Motorola's option, Motorola will replace the defective Software with functionally -equivalent Software, license to Licensee substitute Software which will accomplish the same objective, or terminate the license and refund the Licensee's paid license fee. 6.3. Warranty claims are described in the Primary Agreement. 6.4. The express warranties set forth in this Section 6 are in lieu of, and Motorola disclaims, any and all other warranties (express or implied, oral or written) with respect to the Software or Documentation, including, without limitation, any and all implied warranties of condition, title, non -infringement, merchantability, or fitness for a particular purpose or use by Licensee (whether or not Motorola knows, has reason to know, has been advised, or is otherwise aware of any such purpose or use), whether arising by law, by reason of custom or usage of trade, or by course of dealing. In addition, Motorola disclaims any warranty to any person other than Licensee with respect to the Software or Documentation. Section 7 TRANSFERS Licensee will not transfer the Software or Documentation to any third party without Motorola's prior written consent. Motorola's consent may be withheld at its discretion and may be conditioned upon transferee paying all applicable license fees and agreeing to be bound by this Agreement. If the Designated Products are Motorola's radio products and Licensee transfers ownership of the Motorola radio products to a third party, Licensee may assign its right to use the Software (other than RSS and Motorola's Motorola.CSA.FINAL.3.7.11.revision.doc 15 Motorola Contract No. 110668 • • • FLASHport® software) which is embedded in or furnished for use with the radio products and the related Documentation; provided that Licensee transfers all copies of the Software and Documentation to the transferee, and Licensee and the transferee sign a transfer form to be provided by Motorola upon request, obligating the transferee to be bound by this Agreement. Section 8 TERM AND TERMINATION 8.1 Licensee's right to use the Software and Documentation will begin when the Primary Agreement is signed by both parties and will continue for the life of the Designated Products with which or for which the Software and Documentation have been provided by Motorola, unless Licensee breaches this Agreement, in which case this Agreement and Licensee's right to use the Software and Documentation may be terminated immediately upon notice by Motorola. 8.2 Within thirty (30) days after termination of this Agreement, Licensee must certify in writing to Motorola that all copies of the Software have been removed or deleted from the Designated Products and that all copies of the Software and Documentation have been returned to Motorola or destroyed by Licensee and are no longer in use by Licensee. 8.3 Licensee acknowledges that Motorola made a considerable investment of resources in the development, marketing, and distribution of the Software and Documentation and that Licensee's breach of this Agreement will result in irreparable harm to Motorola for which monetary damages would be inadequate. If Licensee breaches this Agreement, Motorola may terminate this Agreement and be entitled to all available remedies at law or in equity (including immediate injunctive relief and repossession of all non -embedded Software and associated Documentation unless Licensee is a Federal agency of the United States Government). Section 9 UNITED STATES GOVERNMENT LICENSING PROVISIONS This Section applies if Licensee is the United States Government or a United States Government agency. Licensee's use, duplication or disclosure of the Software and Documentation under Motorola's copyrights or trade secret rights is subject to the restrictions set forth in subparagraphs (c)(1) and (2) of the Commercial Computer Software -Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless they are being provided to the Department of Defense. If the Software and Documentation are being provided to the Department of Defense, Licensee's use, duplication, or disclosure of the Software and Documentation is subject to the restricted rights set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. The Software and Documentation may or may not include a Restricted Rights notice, or other notice referring to this Agreement. The provisions of this Agreement will continue to apply, but only to the extent that they are consistent with the rights provided to the Licensee under the provisions of the FAR or DFARS mentioned above, as applicable to the particular procuring agency and procurement transaction. Section 10 CONFIDENTIALITY Licensee acknowledges that the Software and Documentation contain Motorola's valuable proprietary and Confidential Information and are Motorola's trade secrets, and that the provisions in the Primary Agreement concerning Confidential Information apply. 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. Motorola.CSA.FINAL.3.7.11.revision.doc 16 Motorola Contract No. 110668 Section 13 GENERAL • • • 13.1. COPYRIGHT NOTICES. The existence of a copyright notice on the Software will not be construed as an admission or presumption of publication of the Software or public disclosure of any trade secrets associated with the Software. 13.2. COMPLIANCE WITH LAWS. Licensee acknowledges that the Software is subject to the laws and regulations of the United States and Licensee will comply with all applicable laws and regulations, including export laws and regulations of the United States. Licensee will not, without the prior authorization of Motorola and the appropriate governmental authority of the United States, in any form export or re-export, sell or resell, ship or reship, or divert, through direct or indirect means, any item or technical data or direct or indirect products sold or otherwise furnished to any person within any territory for which the United States Government or any of its agencies at the time of the action, requires an export license or other governmental approval. Violation of this provision is a material breach of this Agreement. 13.3. ASSIGNMENTS AND SUBCONTRACTING. Motorola may assign its rights or subcontract its obligations under this Agreement, or encumber or sell its rights in any Software, without prior notice to or consent of Licensee. 13.4. GOVERNING LAW. This Agreement is governed by the laws of the United States to the extent that they apply and otherwise by the internal substantive laws of the State to which the Software is shipped if Licensee is a sovereign government entity, or the internal substantive laws of the State of Illinois if Licensee is not a sovereign government entity. The terms of the U.N. Convention on Contracts for the International Sale of Goods do not apply. In the event that the Uniform Computer Information Transaction Act, any version of this Act, or a substantially similar law (collectively "UCITA") becomes applicable to a party's performance under this Agreement, UCITA does not govern any aspect of this Agreement or any license granted under this Agreement, or any of the parties' rights or obligations under this Agreement. The governing law will be that in effect prior to the applicability of UCITA. 13.5. THIRD PARTY BENEFICIARIES. This Agreement is entered into solely for the benefit of Motorola and Licensee. No third party has the right to make any claim or assert any right under this Agreement, and no third party is deemed a beneficiary of this Agreement. Notwithstanding the foregoing, any licensor or supplier of third party software included in the Software will be a direct and intended third party beneficiary of this Agreement. 13.6. SURVIVAL. Sections 4, 5, 6.3, 7, 8, 9, 10, 11 and 13 survive the termination of this Agreement. 13.7. ORDER OF PRECEDENCE. In the event of inconsistencies between this Exhibit and the Primary Agreement, the parties agree that this Exhibit prevails, only with respect to the specific subject matter of this Exhibit, and not the Primary Agreement or any other exhibit as it applies to any other subject matter. 13.8 SECURITY. Motorola uses reasonable means in the design and writing of its own Software and the acquisition of third party Software to limit Security Vulnerabilities. While no software can be guaranteed to be free from Security Vulnerabilities, if a Security Vulnerability is discovered, Motorola will take the steps set forth in Section 6 of this Agreement. Motorola.CSA.FINAL.3.7.11.revision.doc 17 Motorola Contract No. 110668 Exhibit B • • • Payment Schedule Except for a payment that is due on the Effective Date, Customer will make payments to Motorola within thirty (30) days after the date of each invoice. Customer will make payments when due in the form of a check, cashier's check, or wire transfer drawn on a U.S. financial institution and in accordance with the following: 25% of the contract price upon contract execution 50% of the contract price upon shipment 15% of the contract price upon installation 10% of the contract price upon Final Acceptance or start of Beneficial Use Motorola reserves the right to make partial shipments of equipment and to request payment upon shipment of such equipment. In addition, Motorola reserves the right to invoice for installations or civil work completed on a site -by -site basis, when applicable. Motorola.CSA.FINAL.3.7.11.revision.doc 18 Motorola Contract No. 110668 Exhibit C • Technical and Implementation Documents Motorola.CSA.FINAL.3.7.11.revision.doc 19 Motorola Contract No. 110668 Warranty D • Warranty and Maintenance Plan Motorola.CSA.FINAL.3.7.11.revision.doc 20 Motorola Contract No. 110668 • • • Exhibit E System Acceptance Certificate Customer Name: Project Name: This System Acceptance Certificate memorializes the occurrence of System Acceptance. Motorola and Customer acknowledge that: 1. The Acceptance Tests set forth in the Acceptance Test Plan have been successfully completed. 2. The System is accepted. Customer Representative: Motorola Representative: Signature: Signature: Print Name: Print Name: Title: Title: Date: Date: FINAL PROJECT ACCEPTANCE: Motorola has provided and Customer has received all deliverables, and Motorola has performed all other work required for Final Project Acceptance. Customer Representative: Motorola Representative: Signature: Signature: Print Name: Print Name: Title: Title: Date: Date: Motorola.CSA.FINAL.3.7.11.revision.doc 21 Motorola Contract No. 110668 WELD COUNTY APRIL 24, 2013 MASTER SITE, MCC7500 AND SOFTWARE UPGRADES MOTOROLA The design, technical, and cost information furnished with this proposal is proprietary information of Motorola Solutions, Inc. (Motorola). Such information is submitted with the restriction that it is to be used only for the evaluation of the proposal, and is not to be disclosed publicly or in any manner to anyone other than those required to evaluate the proposal, without the express written permission of Motorola Solutions, Inc. MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. SYMBOL is a trademark owned by Symbol Technologies, Inc., which is a wholly owned subsidiary of Motorola Solutions, Inc. All other trademarks are the property of their respective owners. © 2012 Motorola Solutions, Inc. All rights reserved. TABLE OF CONTENTS Section 1 System Description 1-1 1 1 SOLUTION OVERVIEW 1-1 1.1.1 ASTRO 25 Project 25 Infrastructure 1.1.2 MCC 7500 Dispatch Consoles 1.1.3 Weld County Configuration 1.1.4 Project 25 Equipment 1.1.4.1 Master Site Equipment 1.1.4.2 Zone Controller 1.1.4.3 Network Management 1.1.4.4 Zone -Level Server Applications 1.1.4.5 System -Level Server Application 1.1.4.6 Prime Site Equipment 1.1.4.7 Simulcast Remote Site Equipment 1.1.4.8 Standalone Trunked Repeater Site Equipment 1.1.5 System Coverage 1.1.6 ASTRO 25 Features and Functionality 1.1.6.1 Project 25 Standards Compliance 1.1.6.2 Security and Encryption 1.1.6.3 P25 Digital Modulation 1.1.6.4 Integrated Data 1.1.6.5 Interoperability Interfaces — ISSI and CSSI 1.1.6.6 System Access Functionality 1.1.6.7 User Talkgroup Functionality 1.1.6.8 Individual Call Functionality 1.1.7 System Reliability and Fault Tolerance 1.1.7.1 ASTRO 25 Master Site Designed Resilience 1.1.7.2 Redundancy and Failure Modes 1.2 DISPATCH CONSOLES 1-1 1-1 1-3 1-3 1-4 1-4 1-5 1-5 1-5 1-6 1-7 1-7 1-12 1-12 1-12 1-12 1-13 1-14 1-15 1-18 1-19 1-20 1-20 1-20 1-21 1-23 1.2.1 Console Key Capabilities and Functionality 1-24 1.2.1.1 Capabilities of the MCC 7500 Dispatch Console 1-25 1.2.1.2 Agency Partitioning 1-25 1.2.1.3 Dispatch Console Position Architecture 1-25 1.2.1.4 Console Operations 1-26 1.2.2 Additional Console Equipment 1-28 1.2.2.1 Analog Conventional Channel Gateway (CCGW) 1-28 1.2.2.2 Backup Consolettes 1-28 1.2.3 Logging Recorder Subsystem 1-29 1.2.3.1 Archiving Interface Server 1-29 1.2.3.2 MCC 7500 IP Logging Recorder 1-30 1.2.3.3 NICE Inform 1-30 Section 2 System Diagrams 2-1 Section 3 Equipment List 3-1 Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Table of Contents i Section 4 Statement of Work 4-1 4.1 Overview 4-1 4.2 Assumptions 4-1 4.3 Contract 4-3 4.3.1 Contract Award (Milestone) 4-3 4.3.2 Contract Administration 4-3 4.3.3 Project Kickoff 4-3 4.4 Contract Design Review 4-4 4.4.1 Review Contract Design 4-4 4.4.2 Design Approval (Milestone) 4-5 4.5 Order Processing 4-5 4.5.1 Process Equipment List 4-5 4.6 Manufacturing and Staging 4-6 4.6.1 Manufacture Motorola Fixed Network Equipment 4-6 4.6.2 Manufacture Non -Motorola Equipment 4-6 4.6.3 Ship to Staging (Milestone) 4-6 4.6.4 Stage System 4-6 4.6.5 Perform Staging Acceptance Test Procedures 4-7 4.6.6 Ship Equipment to Field 4-7 4.6.7 CCSi Ship Acceptance (Milestone) 4-7 4.7 Civil Work for the Customer -Provided Facilities 4-8 4.8 System Installation 4-9 4.8.1 Install Fixed Network Equipment 4-9 4.8.2 Fixed Network Equipment Installation Complete 4-10 4.8.3 Console Installation 4-10 4.8.4 Console Installation Complete 4-10 4.8.5 System Installation Acceptance (Milestone) 4-10 4.9 System Optimization 4-11 4.9.1 Optimize System FNE 4-11 4.9.2 Link Verification 4-11 4.9.3 Completion Criteria* 4-12 4.9.4 Optimization Complete 4-12 4.10 Training 4-12 4.10.1 Perform Training 4-12 4.10.2 Training Complete 4-12 4.11 Audit and Acceptance Testing 4-12 4.11.1 Perform R56 Installation Audit 4-12 4.11.2 Perform Equipment Testing 4-13 4.11.3 Perform Functional Testing 4-13 4.11.4 System Acceptance Test Procedures (Milestone) 4-13 4.12 Finalize 4-13 4.12.1 Cutover 4-13 4.12.2 Resolve Punchlist 4-14 4.12.3 Transition to Service/Project Transition Certificate 4-14 4.12.4 Finalize Documentation 4-15 4.12.5 Final Acceptance (Milestone) 4-15 Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. 0 Motorola Solutions Confidential Restricted Table of Contents ii 4.13 Project Administration 4-15 4.13.1 Project Status Meetings 4-15 4.13.2 Progress Milestone Submittal 4-16 4.13.3 Change Order Process 4-16 Section 5 Project Schedule 5-1 Section 6 Acceptance Test Plan 6-1 6.1 Acceptance Test Procedures 6-1 6.1.1 General Performance Criteria 6-1 6.1.2 System Functionality Tests 6-1 6.2 Sample Test Scripts 6-1 Section 7 Training Plan 7-1 7.1 Overview 7-1 7.2 Courses Proposed 7-1 Section 8 Warranty and Maintenance Plan 8-1 8.1 THE MOTOROLA SERVICE DELIVERY TEAM 8-1 8.2 Warranty Services 8-2 8.2.1 Dispatch Service 8-2 8.2.2 OnSite Infrastructure Response 8-2 8.2.3 Network Preventative Maintenance 8-2 8.2.4 Infrastructure Repair with Advanced Replacement 8-3 8.2.5 Technical Support Service 8-3 8.2.6 Network Monitoring Service 8-3 8.2.7 Security Update Service (SUS) 8-4 8.3 Post Warranty Services 8-4 8.4 Summary 8-4 Section 9 Pricing Summary 9-1 Section 10 Terms and Conditions 10-1 Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page_ 0 Motorola Solutions Confidential Restricted Table of Contents iii SECTION 1 SYSTEM DESCRIPTION 1.1 SOLUTION OVERVIEW Motorola Solutions, Inc. (Motorola) proposed design for Weld County is a Project 25 (P25) compliant, digital bunked communications system specifically designed to provide a regional P25 Standards Based system for Adams County, Weld County, and Thornton, with the ability to accommodate other future users. Motorola's proposed system leverages the existing Weld County equipment investment, and provides a state-of-the-art, mission critical, highly reliable system. The proposed design will provide an M3 Core (to be located at the ADCOM facility in Commerce City) which includes Console Subsystem Interface (CSSI) and the upgrade eight Weld County sites from 7.5 to 7.13. The proposal includes a new MCC 7500 dispatch center for the Weld County backup center and an upgrade to the existing MCC 7500 Dispatch Center located in Weld County. The new Master Site will become an interoperability network node utilising ISSI. The ISSI gateway has the ability to link to three other existing systems in the Denver Metro Area, assuming those systems also have an ISSI Gateway on their end. The proposed new master site and infrastructure upgrade will provide enhancements for North Metro area users. • Upgraded infrastructure capable of new features • Upgraded infrastructure capable of future TDMA and Dynamic Dual Mode • Upgraded infrastructure capable of expansion of sites and dispatch centers • End -to -End encryption from user to dispatcher. • Additional Integrated Voice and Data capability. Optional Integrated data applications will be available to enhance the management of the system, including Over the Air Rekeying (OTAR) and Over the Air Programming (OTAP), and the operation of the system (Outdoor Location and Text Messaging). 1.1.1 ASTRO 25 Project 25 Infrastructure Motorola has proposed a total solution that meets the voice and data subsystem requirements expressed by Weld County. The P25 Radio System will include an ASTRO 25 IP Master Site, one (1) simulcast subsystem with three (3) remote sites in Weld County, and upgrades to five (5) remote standalone sites. There is also one (1) Simulcast subsystem with four (4) remote sites and one standalone site in Adams County being proposed to ADCOM via separate proposal that will also be part of the overall P25 system. 1.1.2 MCC 7500 Dispatch Consoles The MCC 7500 Dispatch Console is Motorola's mission -critical high -tier radio dispatch console system. Fully integrated with the P25 system, the MCC 7500 Dispatch Console features an intuitive, easy -to -use Graphical User Interface (GUI) that runs under a Microsoft Windows operating system. MCC 7500's highly recognizable icons are designed to reduce user training time and allow dispatchers to manage information more productively. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-1 New Motorola MCC 7500 IP consoles will be located at the Weld County Backup Center located at 351 Avenue. The existing MCC 7500 Dispatch Center in Weld County will be upgraded and integrated with the new ASTRO 25 Master Site. PROJECT 25 INFRASTRUCTURE The proposed solution for Weld County is a new ASTRO 25 M3 IP Master Site, one trunked simulcast cell, and five standalone repeater sites. Each of the sites and cells will be re -configured and upgraded as appropriate to operate on the new ASTRO 25 IP Master Site. The simulcast cell and standalone repeater sites connect back to the ASTRO 25 IP Master Site via a combination of T1 and Ethernet Site Links. The IP Master Site is capable of providing all system administration and traffic control functions for the entire system As part of the configuration of the M3 Master Site, each subscriber unit will have to be reprogrammed to recognize the new System ID associated with the ASTRO 25 master site. The programming and configuration of subscribers is the responsibility of Weld County. 0 STREET 12 Channel Simulcast CIVIC CENTER 0( 0) 13 Channel Simulcast I HILLTOP 0) 13 Channel Simulcast NEW (TBD) 13 Channel Simulcast r / WATER TANK l(� 13 Channel Simulcast 8 0PS THORNTON DISPATCH 35TM AVE 12 Channel Simulcast GREELEY 0 05" WEST 12 Channel GREELEY 01Simulcast IP BACKHAUL NETWORK sins P25 MASTER SITE 10 OPS ADCOM DISPATCH SE WELD l(� �)� 6 Channel Standalone 14OPS WELD COUNTY DISPATCH TRI AREA ( 9 Channel Standalone HOYT 5 Channel Standalone NEW RAYMER 4 Channel Standalone GROVER 4 Channel Standalone NUNN 5 Channel Standalone whoa 14OPS WELD COUNTY ACKUP DISPATC Figure 1-1: High -Level Diagram of the Weld/ADCOM Proposed Project 25 Infrastructure. The Weld County system has been configured to accommodate a capacity of up to 7,000 users. The system can be easily configured to accommodate up to 128,000 users and 16,000 talk groups, as needed. The ASTRO 25 IP Master Site is software upgradeable to P25 Phase 2 operation, providing Weld County with the capability to further enhance operation by utilizing TDMA in the future. The Dynamic Dual Mode software option provides seamless interaction between FDMA and TDMA capable users on one channel. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-2 1.1.3 Weld County Configuration The current Weld County trunked system consists of a simulcast cell with three existing remote sites, and 12 channels. Five standalone repeater sites are located throughout the County. The existing 3 -site simulcast in Weld County is currently IP Simulcast. The sites will be software upgraded from 7.5 to 7.13. No hardware modifications are included. The five repeater sites in Weld County are New Raymer, Grover, Tri Area, Southeast Weld and Nunn. Each of these sites will also be software upgraded from 7.5 to 7.13. No hardware modifications are required. The Weld County Simulcast. Tri-Area site and SE Weld sites will be connected to the IP Master Site via Ethernet Links. The New Raymer, Grover, and Nunn sites will be connected to the IP Master Site via T1 links. 1.1.4 Project 25 Equipment The components provided for each site are listed below: • New ASTRO 25 M3 Zone Core Redundant Zone Controllers - Core Switching and Routing Center - Integrated Voice and Data Network Management Subsystem • 2 Network Management Terminals (one remote) • Security Partitioning • Dynamic Frequency Blocking • ATIA Data • Email Alarm Notification capability • CSSI for 10 operator positions • Network Management System Licenses • Two (2)- Unified Network Configuration Manager • Two (2)- User Configuration Manager • Two (2)- Unified Event Manager • Two (2)- Zone Watch • Two (2)- Radio Control Manager • Two (2)- Historical Reports • Two (2)- Dynamic Reports • Two (2)- Affiliation User Reports - 7,000 subscriber user licenses - Site licenses to accommodate the ADCOM simulcast cell (4 subsites), Hoyt, Weld County Simulcast (3 subsites), New Raymer, Grover, Tri Area, SE Weld and Nunn. Channel licenses for 22 Dynamic Dual Mode Channels (6 channels in the simulcast cell, and 2 channels each at Hoyt and Ladybird) — Spares • ISSI 8000 Network gateway with connections to 3 neighboring system — 30 simultaneous call capability • Optional Data Applications — Programming over P25 (POP25) — Advanced Messaging — Outdoor Location Solution Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-3 — Over the Air Rekeying • Weld County upgrades to 7.13 - Software upgrades to stations and controllers from 7.5 to 7.13 at the following sites: 3 site simulcast cell (12 channels), New Raymer (4 channels), Grover (4 channels), Tri Area (9 channels). Southeast Weld (6 channels). Nunn (5 channels) - Software upgrade to routers and switches at remote sites and dispatch location - Ethernet Modules for S2500 routers located at Tri Area, SE Weld and the Simulcast Prime Site The following sections describe elements of the proposed system: Master Site, simulcast prime site, simulcast remote site, and standalone repeater site. 1 1.4.1 Master Site Equipment At the heart of the proposed Weld County design is a P25 IP Core Master Site. The P25 Master Site provides connectivity between voice subsystems, along with optional P25 data capabilities such as OTAP and Rekeying of P25 subscribers. The IP Master Site is individually capable of managing the entire network. The P25 Master Site is the central call processing center, delivering mission critical voice and data communications and allowing users to roam throughout the network without the need to make a manual selection. Designed for maximum availability and dependability, the core is the central source of network services and control. It is a fully IP-based. flexible, modular network with advanced call processing capabilities designed to meet the mission critical needs of Weld County. The proposed P25 network will adapt and change to accommodate additional users, increased geographic coverage, enhanced data applications, and connectivity to other networks to ensure an efficient and cost-effective solution for the County. The Master Site serves as a central point for all system traffic in the P25 system, houses redundant zone controllers, and provides system management interfaces. 1 1.4.2 Zone Controller The Zone Controller is a redundant processor that provides trtuiked call processing for P25 system operation. The Zone Controller forms the heart of a wide area radio system by providing the central processor for the zone with the necessary hardware and software capabilities to provide call processing and mobility management. The Zone Controller is supplied in a redundant controller configuration, and provides the following: • System Availability - The Zone Controller allows software upgrades once loaded, providing enhanced system availability. • Intelligent Switchover - The redundant configuration provides automatic switchover to the standby controller if a loss of wide area communications is detected. Notification can be sent to the user if other components fail, allowing the user to manually switch to the standby controller if desired. • Cross Controller Compatibility - Capable of inning two different versions of software simultaneously, ensuring that upgrades are fully functional with one controller before upgrading the second controller. • Redundant Configuration - The redundant zone controller is a computer platform with redundant -processors that provides honking call processing for P25 wide area radio communication systems. The redundant zone controller is designed to detect failures by Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-4 automatically switching operation to the standby controller, minimi7ing interruption of call processing functionality. 1.1.4.3 Network Management The Network Management System (NMS) can be viewed as a set of software applications or tools used to manage the P25 wide area bunked radio system and its constituent components. The network management servers support fault, configuration, performance, and security management for the infrastructure. The system includes servers which maintain configuration and statistical data, collect fault management information, host Private Radio Network Management (PRNM) applications, and share information with other equipment in the system. 1.1.4.4 Zone -Level Server Applications • Air Traffic Router (ATR) • Zone Database Server (ZDS) • Zone Statistics Server (ZSS) • Unified Event Manager Server (UEM) 1.1.4.5 System -Level Server Application • User Configuration Server (UCS). PN Router IIIIIIIIIIII Network Management gaSS ZC2, ZDS, UEM, CSMS, UNC Core Routers G GSN Core LAN Switches Core Backhaul Switches Gateway Gateway Router 1 Router 2 ADCOM m DM Z Switch �■ Firewall ZC1, DC, ATR, Prov Mgr, ZSS, IVD PDG ADCOM C ADCOM SIMULCAST ` STANDALONE SUBSYSTEMS SITES WELD COUNTY SIMULCAST SUBSYSTEMS WELD COUNTY STANDALONE SITES Figure 1-2: High -Level Diagram of the Weld/ADCOM P25 Master Site. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-5 1.1.4.6 Prime Site Equipment The existing Weld County simulcast cell consists of a prime site and a number of simulcast remote sites. The prime site acts as a control and audio center for the simulcast cell. Audio from the user radios is received by the GTR 8000 simulcast receivers at the remote sites, packetized, and routed to the prime site. At the prime site, a GCM 8000 voting comparator votes the multiple audio streams from different site on a frame -by -frame basis. The resulting voted composite signal is better than any one site can provide. This "voted" audio at the prime site is again packetized and routed to two destinations. • First the audio is redistributed to each remote site in the simulcast cell. The remote sites simultaneously transmit the voted audio to the user radios operating in that cell. This allows all members of the call to receive this optimum audio. • Additionally the prime site also routes the voted audio to the Master Site. The Master Site distributes the audio to dispatch centers, simulcast cell/site that requires participation in the call. µWave Backhaul Layer 2 Microwave Links Primary Simulcast Prime Site Controller Comparators fnr CH 1 & 2 Comparators forCH3&4 TI Prime Site Gateway Site LAN Switch 1 Site LAN Switch 2 Comparators fnrCH5&R Comparators forCH7&8 T1 t t 44 µWave Backhaul Prime Site Gateway Site LAN Switch 4 Comparators fnr CH 9 & 10 Comparators for CH 11&12 Comparators for CH 13 PPS GPS Frequency GPS Reference — Antenna Remote Site Access Gateway Remote Site Access Gateway µWave µWave Backhaul Backhaul lu Mastei Sites Redundant Simulcast Prime Site Controller Layer 2 Microwave Links to Master Sites Figure 1-3: Weld/ADCOM Simulcast Prime Site. Weld County Master Site, MCC7500 and Software Upgrades T1 Time/Frequency Reference Cable April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-6 1.1.4.7 Simulcast Remote Site Equipment The GTR 8000 repeater is at the core of the ASTRO 25 remote site. The GTR 8000 platform requires low power, minimal rack space, and utilizes an off -the -shelf Ethernet -based transport layer. Subscriber audio is received and packetized by the stations. The packetized audio is routed via the local redundant site routers to the packet based microwave backhaul network. The microwave routes the audio via two independent paths: if the audio is simulcast, it routes to the prime site to be voted. If it is not simulcast, the audio routes directly to the Master Site. GPS Antenna r 11 µWave Backhaul Ethernet Rack -Integrated LAN Switch with internal GPS Tx Antenna Microwave Links to Master Sites Site Gateway t Rack -Integrated LAN Switch with internal GPS 1 1 11 µWave Backhaul Ethernet tat 11 In -Rack Rx Muilticoupler & Combiner Primary GTR 8000 ESS Rack 6 CH per 19" Rack GPS Antenna Rx Antenna Figure 1-4: Weld/ADCOM Simulcast Remote Site. LAN Ethernet Time/Frequency Reference Cable ESS - Expandable Site Subsystem 1.1.4.8 Standalone Trunked Repeater Site Equipment Additional coverage is provided by standalone trunked repeater sites. These sites house the same mucking equipment as the simulcast cell remote sites. However, unlike the simulcast remotes sites, which connect to a prime site, the standalone trunked repeater sites connect directly to the ASTRO 25 Master Site. Users will seamlessly roam between the simulcast cell and standalone repeater sites, with no user or dispatch intervention. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-7 MOSCAD µWave µWave Backhaul Backhaul Ethernet Tx Antenna i I Ra4k-Integrated LA _ Switch Site Gateway Ethernet In -Rack Rx Muilticoupler & Combiner Microwave Links to Prime Site Site Gateway Rack -Integrated LAN Switch 0 Primary GTR 8000 ESS Rack 6 CH per 19" Rack Rx Antenna Figure 1.5: Weld/ADCOM A25 GTR Standalone Remote Site. LAN Ethernet Time/Frequency Reference Cable Ethernet Backhaul ESS: Expandable Site Subsystem The following describes the components associated with the proposed simulcast prime and remote sites, and standalone repeater sites. GCP 8000 Site Controller The GCP 8000 Site Controller is the control interface between the transmitter/receiver subsystem at the site and the zone controller at the zone control location. The GCP 8000 Site Controller is comprised of redundant site controller modules: one site controller module is active, and the second module is standby, providing redundancy and eliminating a single point of failure. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-8 The GCP 8000 provides the following functions at both repeater and simulcast sites: • Manages the channels to maximize throughput and channel availability. • Call processing for individual sites. • Administers registration and context activation requests. • Deployed in two separate chassis to prevent single point failures. • Redundant site control. • Enables redundant site link routing for patch redundancy. Additionally, the GCP 8000 provides the following functions at each simulcast site: • IP simulcast capability, enabling true end -to -end IP connectivity in a simulcast configuration. • In the event the primacy site reference fails, the GCP 8000 provides a time and frequency reference signal to the base stations maximizing frequency stability and allowing for further site separation in a simulcast configuration. Figure 1-6: GCP 8000 Site Controller Front View with the Fan Removed GCM 8000 Comparator The GCM 8000 Comparator is typically located at the simulcast prime site. It ensures the broadcast of the best possible voice signal by combining the best parts of a single signal that has been received by multiple sites in a simulcast system. The comparator features a state-of-the-art digital voting methodology: Frame Diversity Reception. The comparator selects the data frame or signals with the lowest BER and forwards it. By using the best pieces of each input signal, the result is the best possible composite signal. The GCM 8000 provides the following functions: • Available in standalone configuration with one or two channels per chassis. • Occupies only three rack units of space for up to two channels. • Supports up to 15 simulcast sub -sites. • Supports IP simulcast operation only. • AUX Power is shared between chassis. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-9 Figure 1.7: GCM 8000 Comparator- Front Inside. GTR 8000 Base Station The GTR 8000 Base Station is typically located at ASTRO 25 repeater and simulcast remote sites. Its benefits include: • Software -definable station allows for flexibility in implementation for P25 Phase 2 TDMA, P25 Phase 1 FDMA, Trtmking, Conventional, Multi -site configuration or simulcast configuration as well as High Performance Data configuration. • A common hardware platform requires fewer Field Replaceable Units (FRU). • Innovative design allows for upgrades within systems via hardware and/or software to avoid total infrastructure replacement. • Modular, front access design and minimized cabling reduces install and service labor. Figure 1-8: GTR 8000 Base Station. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-10 GTR 8000 Expandable Site Subsystem (ESS) The GTR 8000 Expandable Site Subsystem has: • Includes up to six GTR 8000 base stations. • Extremely efficient use of site space. • Preconfigured which decreases field and system engineering work and allows for easier installation. 3.2.2.3.4 GGM 8000 - Site Gateway In the RF site subsystem, site gateways perform three functions: they convert Ethernet to the selected transport medium; they prioritize packets which are leaving the site; and they fragment large IP packets according to industry standards. There are three types of gateways used: • Prime to Zone Control Location Gateway — Routes network management traffic between the remote sites and the prime site LAN. • Prime to Remote Site Access Gateway — Connects remote sites to prime site LAN, carries remote site audio to the prime site, voted audio to the remote sites, and transmits network management data to the zone control location. • Remote Site Gateway — Handles all IP Network management traffic between the zone control location and the simulcast remote site or repeater site. 80 SC 88 8A MOTOROLA 78 IA L. n. 68 M Expansion Module 4,M • •••••••••••••••• ••• I I" A Ill illl �maronos.A SYSTEM •vane •la UM Ghat •LW • 9Mr. •t�l �arr4 0) Figure 1-9: GGM 8000 Site Gateway. HP 2620 LAN Switches The LAN switch at a site provides a LAN interface for site equipment and a LAN port for the site gateway. There are two types of LAN switches used in the subsystem: • Prime Site LAN Switch - Provides a LAN between the comparators, redundant site controllers, and prime site gateway. Each simulcast site controller is connected to a separate switch. Through the switch, the service technicians gain access to service the site, and also access the system's Graphical User Interface. • Remote Site LAN Switch - Distributes network management traffic to the base stations. Radio Frequency Distribution System (RFDS) The RFDS provides interconnect between the base stations and antennas, allowing for a completely contained and more compact installation footprint. Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-11 1.1.5 System Coverage Motorola has not performed any coverage studies associated with the Weld County/ADCOM regional system. Motorola cannot guarantee coverage for Weld County agencies will be the same after the split from CO DTR as it was with the sites attached to DTR. Additional sites may be required to provide coverage similar to today's for the agencies utilizing the proposed Master Site. Any additional sites that may be required by Weld County are not included in this proposal. 1.1.6 ASTRO 25 Features and Functionality 1.1.6.1 Project 25 Standards Compliance The proposed P25 system features P25 -compliant tr unking, as described in the TIA-102 standard. In order to achieve this compliance. Motorola optimizes custom solutions for mission -critical voice communications performance, more efficiently than solutions that use commercial -off -the -shelf network components. When public safety life or death decisions depend upon clear uninterrupted voice, Motorola has the correct IP solution. Table 1-1 below provides a list of P25 tnmked system features for release 7.13. 1.1.6.2 Security and Encryption Encryption assures that only authorized units in the system can listen to transmissions being made. Encrypted calls are protected end -to -end throughout the network. Starting at the subscriber unit, which encrypts/decrypts the call signal: calls are encrypted all the way through to the MCC 7500 dispatch operator position, which contains the encryption key in each dispatcher operator position. The Radio Network Infrastructure is secure and transparent to the user. Figure 1-10 is a pictorial representation of end -to -end voice encryption. AVFire Dispatch Algorithm A Algorithm B Figure 1-10: Proposed System provides End -to End Encryption. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-12 Project 25 Encryption Algorithms Motorola's P25 systems can be equipped with current P2.5 algorithms, and filly compliant with all Federal Inforrnation Processing Standards (FIPS), and support the following: • Advanced Encryption Standard (AES) - P25 Standard. • Data Encryption Standard (DES/DES-XL/DES-OFB) - P25 Standard. • Digital Voice Privacy — Extended Range (DVP-XL). • Digital Voice International — Extended Range (DVI-XL). No encryption has been included in the consoles for this proposal. 1 1.6.3 P25 Digital Modulation The proposed system is P25 FDMA. The Weld County equipment will require hardware and software at the RF sites in order to be TDMA capable. Motorola's proposed system design will provide Weld County users the option of implementing the system with Dynamic Dual Mode and TDMA support. The system is TDMA and FDMA capable from day one without need of additional hardware. A software option is required to operate in TDMA. Additionally, the Dynamic Dual Mode option allows seamless TDMA and FDMA operation. It is important to note that Motorola's P25 TDMA operation complements P25 FDMA operation on the P25 platform; it does not replace it. While the proposed system includes FDMA operation on all channels at all sites, the channels can be selectively configured with the appropriate software upgrade to operate as either TDMA-only FDMA-only, or both TDMA and FDMA as capacity requires. Talkgroups configured in TDMA mode will operate on the TDMA-configured channels: likewise, tlkgroups configured in FDMA mode will operate on the FDMA-configured channels. Talkgroups can also be configured to accommodate mixed fleet of both TDMA and FDMA users. With TDMA operation enabled, voice calling capacity is increased over FDMA alone without having to abandon FDMA operational stations and subscribers. Benefits of TDMA With the addition of P25 TDMA operation, the P25 system leverages 2:1 TDMA channel efficiency to double voice path capacity as compared to a P25 FDMA channel. This enhanced capacity improves the Grade of Service (GoS), leading to fewer busy calls and faster callbacks during busy situations relative to a standard P25 FDMA system. This improvement is due to the fact that TDMA provides double the talk path capacity in the same RF bandwidth allocation. Having this additional capacity improves the grade of service by reducing channel busies. Furthermore, call-backs are faster due to the greater availability of talk paths in the TDMA solution. P25 TDMA also provides 6.25e (6.25 kHz "equivalent") operation for satisfying certain future FCC spectral efficiency requirements. Dynamic Dual Mode Dynamic Dual Mode allows users to interoperate between P25 FDMA and P25 TDMA services in the same channel without any need for user intervention. 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. 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. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-13 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 ASTRO 25 systems with a mixed fleet of P25 FDMA and P25 TDMA radios. For example: • Radio users have seamless interoperability regardless of the operations mode. • Dispatch operators can automatically coordinate between P25 TDMA radio users and P2.5 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. Dynamic Dual Mode provides efficient system operation by dynamically switching between P25 FDMA mode and P25 TDMA mode for a given station based on the needs for the call assigned to the station. Any station can potentially be configured as FDMA only, TDMA only or Dynamic (FDMA/TDMA). Dynamic Dual Mode does not require a permanent sacrifice of TDMA efficiency on any channels to accommodate FDMA users; the system will automatically adjust to accommodate the load placed on the channels. 1 1.6.4 Integrated Data P25 compliant Integrated Data operation allows data traffic to seamlessly share the ASTRO 25 system with voice traffic. Voice is prioritized, allowing mission critical voice traffic to always take precedence over data transmissions. The Integrated Data service creates a data transport layer capable of supporting both industry standard IP and customer -developed applications, including: • Over the Air Programming (POP25) • Over the Air Rekeying (OTAR) • Text Messaging • Outdoor Location (GPS-Based) The ASTRO 25 proposed radio system includes IV&D functionality. Data applications have not been included in this proposal. Over the Air Rekeying (Priced as Optional) The OTAR feature allows new encryption keys to be remotely loaded into user radios over the air, via the IV&D transport layer. The OTAR option adds a Key Management Facility (KMF) Server and Client workstations for the purposes of managing and updating encryption keys. OTAR provides all the features of multikey (multiple keys) and would enable Weld County to distribute encryption keys over the air without physically touching the radio. OTAR is designed to work on the IV&D transport layer, configuring the system's encryption by distributing unique keys to designated users. OTAR eliminates the burden of manually rekeying radios on a regular basis, enabling key distribution and key management to be conducted securely over -the -air. Motorola's solution is fully P25 compliant and conforms to Federal Information Processing Standard Publication (FIPS 140-2) security guidelines for both hardware and software. The Key Management Facility (KMF), a centralized key manager, is the essential key management controller for the proposed P25 Over the Air Rekeying (OTAR) feature. Utilizing the KMF, key material information can easily be 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. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-14 Over the Air Programming (Priced as Optional) Motorola's over -the -air programming feature is called Programming Over P25 (POP25). POP25 provides the ability to remotely reprogram a properly -equipped Motorola radio operating within the coverage area of the P25 network. More specifically, a radio manager uses a traditional Customer Programming Software (CPS) solution attached to the system infrastructure to read and write a codeplug from a properly -equipped ASTRO 25 trumked radio via the ASTRO Common Air Interface (CAI). The technician can update any CPS based radio configuration information and send the updated codeplug back to the radio. This feature will enable Weld County to easily reprogram their radios to reflect network growth and changes. POP25 automates the programming process, sending updates quickly and transparently over the air using the ASTRO 25 IV&D network instead of requiring users to bring their radios in for manual reprogramming. Global Positioning System (Priced as Optional) The ASTRO 25 Outdoor Location Solution allows Weld County to track mobile and portable radios throughout the coverage area utilizing the Integrated Data functionality within the system. The Motorola Outdoor Location Solution (OLS) is a resource tracking tool that uses Global Positioning System (GPS) satellites to provide operators with the ability to locate and track outdoor personnel and assets in near real time. Weld County's dispatchers can utilize OLS to track the outdoor location of radio users in order to deploy nearby units for a faster response. Updates can be configured to be sent periodically based on time, distance, or can be customized on the fly to reflect the current situation. 1 1.6.5 Interoperability Interfaces — ISSI and CSSI Integration between radio systems and consoles can be accomplished using the P25 Inter RF Subsystem Interface, or P25 ISSI. ISSI provides for the interconnection between multiple P25 systems, allowing user devices to roam from their home networks onto neighboring agency networks, while still communicating with their home dispatchers and users. P25 ISSI provides wire line interoperability among different P25 compliant networks. It allows agencies to roam and communicate across larger coverage areas, greatly enhancing overall coordination and effectiveness of multi -agency operations. It enables users to utilize the entire coverage areas of existing connected networks, many of which span thousands of square miles. P25 ISSI provides this connection to other networks while maintaining complete system autonomy. Motorola's ISSI 8000 provides an interoperability solution built to the P25 ISSI standards. The ISSI 8000 solution is an interoperability solution that enables the Weld County ASTRO 25 system to connect to other P25 systems regardless of their RF bands, manufacturer type and release versions. ISSI 8000 is built to the 11A-102 suite of standards used for the design of P25 interoperable communication products. The ISSI 8000 provides more interoperability choices and allows Weld County more features such as automatic seamless roaming, PTT ID, and P25 TDMA support. ISSI 8000 supports a maximum of 24 connected systems, and over 100 simultaneous nuked calls. A user can operate with ISSI 8000 utilizing Manual Roaming or Automatic Roaming between the systems. For an ISSI connection to be made both systems desiring interoperability must be equipped with ISSI. Motorola cannot guarantee that other systems that Weld/ADCOM desires to have an ISSI connection with will be equipped with that interface. It is Weld/ADCOM's responsibility to negotiate any ISSI agreements with other desired agencies. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-15 The following table summarizes the P25 ISSI features offered by Motorola. Table 1-2: P25 ISSI Trunking Features offered by Motorola. v.10.0 p25 ISSI Trunking Features Offered by Motorola P25 ISSI Trunking Feature Name Offered by Motorola ISSI.1 ? Offered by Motorola ISSI 8000? TIA-102 Standards Document Voice & Mobility Features Voice Featues Broadcast Call No Yes TIA-1O2.BACA-A Announcement Group Call No Yes TIA-1O2.BACA-A _ Confirmed Group Voice Service No Yes TIA-1O2.BACA-A Unconfirmed Group Voice Service Yes Yes "°°e 1 TIA-102.BACA-A Emergency Group Call Yes Yes TIA-1O2.BACA-A Encrypted Voice (AES) Yes Yes TIA-1O2.BACA-A P25 Full -rate vocoder (FDMA) Yes Yes TIA-1O2.BACA-A P25 Half -rate vocoder (TDMA) No Yes Future SU and Group Mobility Management SU Registration No Yes TIA-102.BACA-A Transport of Authentication Credential No Yes TIA-1O2.BACA-A Secure SU registration (SU authentication) No Yes T1A-102.BACA-A SU Deregistration No Yes TIA-1O2.BACA-A Group Affiliation Yes Yes TIA-102.BACA-A Call Restriction No Yes TIA-1O2.BACA-A Roaming Inter-WACN (manual) Yes Yes TIA-1O2.BACA-A Inter-WACN (automatic) No Yes TIA-1O2.BACA-A Inter -System (manual) Yes Yes TIA-1O2.BACA-A Inter -System (automatic) No Yes TIA-102.BACA-A Intra-System (automatic) No Yes TIA-1O2.BACA-A RFSS Service Capability Polling Yes Yes TIA-1O2.BACA-A-2 Supplementary Services Features Transport of Talking Party Identity No Yes TIA-1O2.BACA-A Priority Call No Yes TIA-1O2.BACA-A Emergency Alarm No Yes TIA-1O2.BACD-B Emergency Alarm Cancellation No Yes TIA-1O2.BACD-B Group Emergency Cancellation No Yes TIA-1O2.BACD-B NOTES Note 1: Motorola's ISSI 8000 support unconfirmed group call only as a serving system For dispatch consoles that are not directly connected to the Weld County ASTRO 25 IP Master Site, Motorola offers a P25 Console Sub -System Interface (P25 CSSI). The CSSI 8000 Solution enables Weld County to connect 3rd party P25 CSSI capable consoles to an ASTRO 25 system. CSSI 8000 is built to the P25 CSSI standards and provides Weld County more choices on the type of dispatch consoles they can deploy. CSSI 8000 allows member agencies to keep their existing P25 capable consoles while upgrading their RF infrastructure to an ASTRO 25 system. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-16 Table 1-3: Project 25 CSSI Trunking Features Offered by Motorola. v.10.0 P25 CSSI Trunking Features Offered by Motorola P25 ISSI Trunking Feature Name Offered by Motorola CSSI 8000? TIA-102 Standards Document Voice & Mobility Features Voice Featues Broadcast Call Yes TIA-1O2.BACA-A Announcement Group Call Yes TIA-1O2.BACA-A Confirmed Group Voice Service Yes TIA-1O2.BACA-A Unconfirmed Group Voice Service Yes Note 1 TIA-1O2.BACA-A Emergency Group Call Yes TIA-1O2.BACA-A Individual Voice Call YesN°`e2 TIA-1O2.BACA-A A Encrypted Voice (AES) Yes TIA-1O2.BACA-A P25 Full -rate vocoder (FDMA) Yes TIA-1O2.BACA-A P25 Half -rate vocoder (TDMA) Yes Future SU and Group Mobility Management SU Registration Yes TIA-1O2.BACA-A Transport of Authentication Credential Yes TIA-1O2.BACA-A Secure SU registration (SU authentication) Yes TIA-1O2.BACA-A SU Deregistration Yes TIA-1O2.BACA-A Group Affiliation Yes TIA-1O2.BACA-A Call Restriction Yes TIA-1O2.BACA-A Roaming Inter-WACN (manual) Yes TIA-1O2.BACA-A Inter-WACN (automatic) Yes TIA-1O2.BACA-A Inter -System (manual) Yes TIA-1O2.BACA-A Inter -System (automatic) Yes TIA-1O2.BACA-A Intra-System (automatic) Yes TIA-1O2.BACA-A RFSS Service Capability Polling Yes TIA-1O2.BACA-A-2 Voice & Mobility CSSI Only Features Ability for Console Display of Transmission Source Type Yes TIA-1O2.BACA-A Ability for Console Takeover by Another Console Yes TIA-1O2.BACA-A Ability for Console to have knowledge of when it is receiving duplicate audio Yes TIA-1O2.BACA-A Ability for Console to mute its speakers to prevent audio feedback Yes TIA-1O2.BACA-A Console Priority (Dispatcher Audio Takeover) Yes TIA-1O2.BACA-A Parallel Console Audio Yes TIA-1O2.BACA-A Supplementary Services Features Transport of Talking Party Identity Yes TIA-1O2.BACA-A Priority Call Yes TIA-1O2.BACA-A Call Alert YesN0tC2 TIA-1O2.BACD-B Emergency Alarm Yes TIA-1O2.BACD-B Emergency Alarm Cancellation Yes TIA-1O2.BACD-B Group Emergency Cancellation Yes TIA-1O2.BACD-B NOTES Note 1: Motorola's CSSI 8000 supports unconfirmed group call only as a serving system Note 2: Motorola's CSSI 8000 can support Individual Voice Call and Call Alert to a single CSSI with the same WACN ID and System Id as the ASTRO 25 system Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted System Description 1-17 1 1.6.6 System Access Functionality To ensure system access, simplify radio operation, and limit operator involvement, the ASTRO 25 platform has many access features, as described below. Busy Queuing/Call Back The proposed system has been designed to maximize availability to the end user. In the unlikely event that all the channels are busy, a user depressing their Push -To -Talk (PTT) will be given a busy signal, and placed into a busy queue. When a channel becomes available, the system assigns the users to a channel via pre -assigned priority levels. Once a channel is assigned, the system notifies the user with a call back tone. This feature makes it unnecessary for the radio operator to waste valuable time rekeying their radio in an effort to gain channel access. Automatic Retry If a channel request is not received at the Zone Controller, the individual radio unit continues sending channel requests until the Controller acknowledges the request, or until a total of 16 automatic retries occur. This feature eliminates the need for the operator to continually key and de -key their radio, or to keep their radio keyed in an effort to gain system access. Recent User Priority To ensure uninterrupted communications, a recent radio user priority provides those users who have been recently assigned a voice channel priority over the other system users. Recent user priority ensures that a talkgroup engaged in a conversation receives priority system access for up to 10 seconds between transmissions. Misdirected Radio Protection To ensure that a radio from one talkgroup cannot accidentally be assigned to a voice channel being used by a different talkgroup, the system utilizes embedded signaling. If a unit from a different talkgroup is accidentally assigned the same channel, the radio will recognize that it has been assigned incorrectly, and will automatically revert to the control channel. Continuous Assignment Updating Once a talkgroup is assigned a voice channel, the control channel continues to transmit the channel assignment for as long as that talkgroup is using the channel. This ensures that a radio just coming into service will be sent to the appropriate voice channel to join the rest of its talkgroup. Talk Prohibit Tones In the event that a user attempts to perform an unauthorized function as defined by system permissions, a talk prohibit tone is given. Dynamic Network Access Code (DNAC) The dynamic network access code is used to reduce co -channel and co -site interference. The radio decodes the Network Access Code (NAC) associated with the control channel at a site and uses it for both transmit and receive on the ASTRO 25 voice channel at that particular site. NAC serves as the ASTRO 25 equivalent of connect tone. Each site can have one of the 16 unique NACs allowed within the system. Interference protection is provided from nearby systems as well as between sites in the customer system. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-18 1 1.6.7 User Talkgroup Functionality To enhance user functionality, the ASTRO 25 platform has many talkgroup features, as described below. These features are configurable by the System Administrator Emergency Alarm/Call Emergency alarm/call provides users the capability to inform dispatch personnel of a life -threatening situation. By pressing the radio's emergency alarm button, an audible and visible alarm and the user's ID are sent to the dispatcher, and optionally all talkgroup members. In emergencies, the dispatch center is notified immediately, regardless of whether the system is busy. If one or more voice channels are available, one of those channels will be assigned immediately to the emergency call when the user presses the PTT switch. The duration of the emergency call can be defined by the system administrator. In the event that the system is busy, two alternatives are provided for handling emergency traffic: • Top of the Queue —when an emergency is initiated and no channel is available, the emergency user is put at the top of the busy queue. As soon as the first user on any channel de -keys, the emergency caller is assigned that channel. The major advantage to this approach is that there is no contention for the channel. • Ruthless Preemption —when an emergency is initiated and no channel is available, the Zone Controller selects the channel assigned to the lowest priority user and assigns it to the emergency caller — a feature unique to Motorola thinking systems. Multiple Priority Levels The system provides 10 priority levels, allowing administrators to segment their users according to their communications needs. Priority 1 is always reserved for emergencies. Priorities 2 through 10 can be assigned by the System Manager on a per radio or talkgroup basis. These priorities are only applicable when the system is busy. Multi -Group Call Multi -group call is used to make a simultaneous call to multiple talkgroups, and allow all units to be configured for talk back capability. The System Manager can program this call to operate in one of two ways: • The requesting user waits for all requested talkgroups to finish all calls in progress. • The requested call immediately interrupts other conversations in progress without waiting for active users to de -key. Radio users who are transmitting on a voice channel will not hear the call until they de -key. Dispatch Console/Talkgroup Merge Talkgroup merge is a dispatch function that allows multiple talkgroups to operate together on one voice channel, improving channel efficiency. This is a standard feature of Motorola wire -line consoles. Non -Priority Scan Non -priority scan allows the radio user to scan between multiple systems, talkgroups, or conventional channels. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-19 Priority Monitor Priority monitor allows the radio user to scan talkgroups in their system, and mark up to two talkgroups in their scan list as Priority. A non -priority conversation will be interrupted by Priority 1 or Priority 2 talkgroup activity. 1.1.6.8 Individual Call Functionality To further enhance user functionality, the ASTRO 25 platform has individual call features in addition to user talkgroup features, as described below. These features are configurable by the system administrator. Call Alert Call Alert allows a dispatcher or radio user to selectively page an individual's radio. Call Alert signaling is conducted over the control channel and does not affect voice channel capacity. The Call Alert produces an audible and visual alert on the receiving radio. Indicators on the initiating radio acknowledge delivery of the Call Alert. If the receiving unit has a display, it will show and store the sending unit's ID. In -Call User Alert In -Call User Alert is a feature that builds upon Call Alert. When In -Call User Alert is enabled on the system, radios will be able to receive Call Alerts even when involved in voice and data services. Radio Talkgroup Muting Radio Talkgroup Muting is a feature that utilizes the Call Alert feature. Radio Talkgroup Muting allows the radio user to mute all voice traffic for the currently selected talkgroup. The radio can be automatically unmated by the console dispatcher or another radio user by sending the muted radio a Call Alert. With In -Call User Alert enabled, the Call Alert will reach the muted radio when it is on the voice channel or a data channel, as well as if it is idle on the control channel. Private Call Private Call allows a radio user or console dispatcher to selectively call and cany on a private conversation with another individual radio, as long as that unit is not already engaged in another Private Call. The calling unit will receive an acknowledgment of a successful Private Call. If the receiving radio has a display, it will show the calling party's unit ID. 1.1.7 System Reliability and Fault Tolerance The purpose of this section is to describe the multiple levels of redundancy inherent to the Weld County P25 Radio System. A significant and material attribute of the system is how it performs during various failure conditions and its ability to provide continued conummications. The system can withstand multiple failures and still provide full -featured communications. 1.1.7.1 ASTRO 25 Master Site Designed Resilience The master site's critical equipment is fully redundant; system level equipment that is essential for voice communications is redundant at both the component and box level. This includes redundant zone controllers, enterprise LAN switches, Core backhaul switches and other LAN/WAN components. Should one component or box fail, then a redundant component or box will immediately take over. This level of redundancy is also beneficial during system maintenance and upgrades since a Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-20 redundant component can be serviced without impacting the rest of the system. When servicing of that component is complete, it can be activated and the second component can be serviced. Master Site Enterprise LAN Switch Failure of one Enterprise LAN Switch on the Master site will result in automatic failover to the redundant switch. Users will have full operational functionality. Master Site Core Router (Backhaul LAN switch) In case of an active Core router (with Backhaul Ethernet switch) failure, back up router will immediately take over the control and no effect on system operation. Users will have full operational functionality. Master Site - Redundant Gateway Router or Zone Controllers or Core routers or Enterprise LAN switches (both boxes fail) In the unlikely event that the devices and their redundant backup units both fail, the simulcast cell will automatically switch over to Site Trunking. The ASTRO 25 Simulcast cell will continue to trunk in its respective coverage area; however, there will be no linking of calls directly to the dispatch console. Dispatch centers will utilize the backup consolettes provided to interface to the Simulcast Cell. When the failed components come back online, the system will return to Wide Area Trunking. Site Link Failure Simulcast cells (or A25 repeater sites) whose redundant site links fail (as a result of two failures) will enter site trunking mode. Site trunking mode continues simulcast operation and users within the cell to continue tnuiked operations. Dispatchers will connect to both types of sites through the radio consolettes. 1 1.7.2 Redundancy and Failure Modes The following is a description of the key redundancy schemes incorporated into the ASTRO 25 system which are included as a part of our system design and provide a foundation of how the system responds to various failure scenarios. The proposed system is inherently fault -tolerant and can sustain multiple box -level and system -level failures while still delivering high levels of operational functionality. Box -level redundancy allows multiple failures to occur with no noticeable impact on user operations. Additionally, the system provides two fallback modes of operation (site trunking and failsoft) which provide high levels of operational availability during major failure of multiple system elements. Equipment Redundancy The following sections detail the equipment redundancy available at each type of site, the impact of a failure of each component, and a description of the impact on the user. Trunked Base Station Failure The failure of a station at a simulcast remote site results in some reduced channel capacity. Communications will continue on the remaining channels with no user intervention required. All other channels in the simulcast cell remain unaffected. The entire system remains in the simulcast honking mode. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-21 Site Router (with Backhaul Switch) Failure If the active router (contains Ethernet backhaul switch) fails, the backup router will take over and provide the necessary site connectivity. Users will continue to function on the systems with no impact to their communication functionality. Trunked Prime Site LAN Switch Failure (1 of 4) One quarter of the tanked channels will be unavailable. Communications will continue on the remaining tanked resources. No user intervention will be required. Due to the reduced channels, there is less channel capacity for the cell and hence a lower grade of service. Trunkinq Remote Site LAN Switch Fails (1 of 2) The IP trunking simulcast remote site's dual LAN architecture assures no loss of capacity or functionality due to a switch failure. Full operational functionality will be available to all users. Simulcast Comparator Failure A comparator module failure will affect only one channel on the tanked simulcast cell system. The remaining channels will continue to provide full operational functionality. No user intervention is required to operate on the other available trunked channels. Simulcast Remote Site Failure Failure of one Simulcast Remote Site has no impact on the other simulcast sites. The coverage area will be reduced in the area of the failed site. Users will be able to utilize the remainder of the Simulcast cell to continue communications in that area. The user radios will automatically switch to these other sites and cells with no user intervention. A25 Site Failure Failure of the A25 repeater site has no impact on the simulcast cell. Users will be able to utilize the simulcast cell to continue communications in that area. The user radios will automatically switch to these other sites and cells with no user intervention. Failure Modes The following scenarios describe the infrequent situations where the control channel is not available to the user, either due to coverage limitations, or system failures. Site Trunkinq Site trunking (entire simulcast cell or a single multisite) is the first fallback mode of operation. This mode allows full feature rich tanking operations to continue in the case the simulcast cell or multisite is separated from the core. Dispatch consoles will remain in contact with the field units via consolettes that are integrated at the dispatch centers. Four Control Channels There is always more than one control channel available in the both for the simulcast cells and the standalone trunking sites. The proposed tanked system provides four possible control channels. If the currently active control channel fails, another channel will automatically take over as the control channel, and the failed channel will be automatically taken out of service. All other channels will remain unaffected. The ASTRO 25 simulcast cell or repeater site will remains in the wide -area trunking mode. This type of failure is transparent to all system users. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-22 Failsoft In the event that all four control channels are unavailable to operate due to a major failure, the simulcast cell/standalone site will go into the failsoft fallback mode of operation. Failsoft is a fallback means of commtmication if a site no longer maintains wide area or site thinking operation. Failsoft operation provides communications in conventional mode via repeaters/base radios in order to maintain vital communications. Failsoft operation will continue to provide wide -area simulcast coverage to the end user. The receive audio will be routed to the comparator for voting and redistributed to all of the sites for simulcast transmission. Dispatchers will also still be able to communicate to the user groups on the failsoft cell through fallback consolettes that are integrated at the dispatch centers. Failsoft impacts only the individual cells within the RF network. In systems with multiple RF cells, one cell can be in failsoft while the rest of the system remains in wide -area bunking. 1.2 DISPATCH CONSOLES Motorola is proposing the MCC 7500 IP console to provide the required features for the dispatch center for Weld County. • Weld County upgrades to 7.13 Software upgrade to routers and switches dispatch locations - Software upgrade for 14 MCC 7500 operator positions - Software upgrade for 1 MCC 7500 operator position located at UNC Software upgrades for 2 Archiving Interface Servers and NiceLog logging recorder. • • MCC 7500 Dispatch Center for Weld Backup Center - - 14 MCC 7500 Operator Positions. Each position will be equipped with AES, DES-OFB and ADP encryption and have a VPM, 2 speakers, footswitch, gooseneck microphone, two standard headset jacks and mouse. - — One of the Redundant NiceLog IP Logging Recorders and AIS will be moved from the Weld primary dispatch center to the backup center. — — Aux I/O capability for 48 inputs and 16 outputs — Redundant Gateways and LAN Switches - — 1 Conventional Site Controller — — 5 Conventional Channel Gateways (interface up to 20- 4 -wire tone remote resources) Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-23 NICE SYSTEM LOGGING ADCOM DISPATCH 10 OPS f • • • WELD COUNTY DISPATCH 14 OPS • • RF SITES (I) WELD COUNTY BACKUP DISPATCH 14 OPS r-SH Figure 1-12: Dispatch Configuration 1.2.1 Console Key Capabilities and Functionality Motorola's MCC 7500 Dispatch Console is Motorola's mission -critical high -tier radio dispatch IP console system. Fully integrated with the P25 system, the MCC 7500 Dispatch Console features an intuitive, easy -to -use Graphical User Interface (GUI) that runs under a Microsoft Windows operating system, on an industry -standard PC platform. MCC 7500's highly recognizable icons are designed to reduce user training time and allow dispatchers to manage information more productively. Designed for effective, flexible dispatch communications, the MCC 7500 Dispatch Console provides a range of valuable features: • Seamless integration with P25 trunking systems. • End -to -End Encryption — Encryption and decryption occurs in the dispatch consoles, allowing true end -to -end encryption in the radio system. • Centralized System Management — The MCC 7500 console system is configured and managed by the ASTRO 25 system's network management applications. This provides Weld County system administrators with a single point for configuring and managing the entire radio system, including the console portion. • User -Friendly — MCC 7500's environment features the familiar standards used by other Windows programs, worldwide. • Screen layout, menus and icons are easy to understand and quickly recognizable. • Each dispatcher's configuration can be customized via the Elite Admin application. • Elite Dispatch GUI uses a simple point -and -click response and the keyboard is not required for day-to-day operations. • Agency Partitioning — Allows multiple agencies to use a common system while maintaining control over their console resources. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-24 1.2.1.1 Capabilities of the MCC 7500 Dispatch Console As the most advanced dispatch console in Motorola's portfolio of mission -critical communications technologies, the MCC 7500's standard features offer Weld County state-of-the-art communications. The MCC 7500 solution operates on existing systems and equipment and provides console management and configuration functionality, dispatch operation, and communications security. The proposed system also offers Weld County the capability to maintain both audio and data recording of the calls made on the communications system. 1.2.1.2 Agency Partitioning With Agency Partitioning. Weld County agencies will gain the interoperability benefits of being on the Weld/ADCOM system while being able to leverage cost savings in the maintenance of a shared system, and still maintain control of their own console configurations, encryption keys, and channels. Agency partitioning functionality will enable County system administrators to control who has access to functionality for the console network as a whole. It controls access for 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. 1.2.1.3 Dispatch Console Position Architecture Motorola is proposing a. state-of-the-art, high -tier radio dispatch IP console system. The hardware involved includes client computers and standard networking equipment, all connected to the P25 Master Site via Ethernet switches and site routers through an IP network. Both tanked talkgroups and conventional radio channels can be accessed and controlled from one MCC 7500 IP Dispatch Console over the same network. This reduces overall transport costs and the need for duplicate fixed network equipment. The ASTRO 25 network enables the MCC 7500 to be up to five times more bandwidth -efficient than our competitors' solutions. In addition, bandwidth can be shared between calls, using less total bandwidth during system operation. There are three main components of a Motorola MCC 7500 system: • Dispatch console position • Radio channel interfaces • Archiving interface server Various combinations of these components are connected together and to the rest of the ASTRO 25 system via console site routers and switches on an IP network. Dispatch Console Position The dispatch console software consists of Motorola's Elite Dispatch graphical user interface (GUI). The dispatch console hardware is based on a commercially available personal computer. The console audio interfaces are handled with Motorola -provided hardware, VPM, and software, including: • A Motorola certified Personal Computer • A Voice Processor Module (VPM) • Desktop speakers (up to 8) • Headset jacks (up to 2) • A desktop microphone • A footswitch Each dispatch position has its own PC and its own VPM. Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-25 Console Graphical User Interface (GUI) The MCC 7.500's graphical user interface (GUI) optimises user efficiency. It makes maximum use of monitor space to provide the highest number of resources that a dispatch operator is able to easily view and control. Weld County can customize the MCC 7500's GUI by agency or by individual user to meet the dynamic needs and requirements. Tool Bars iandlg 1.tLl Motolvla MCC IOU tine VlspalLli o"pmabon Ed; Yen ® MOTOROLA reetztes ;tone Fddes .! ip *41(etaib 6:55:55 PM Resource—' Folders Radio Resource Auxiliary Inputs/Outputs Radio Resource Status Bar-+ Folder 1 IAuxio2 Folder2 I Folder 3 I Aux,o1 i ✓� AtndOB r P.Ised 3 I Patch 2 I Patch 3 Paten 1 I ktse► 1IM)sef 2 • a LiTG200049 L1PC_9_00001 LlIli 2 UUU49 Z1TG 2 00049 ©L1MG_v uu6 ©L1♦ C_y_WW© Radio 4— Resources I a' IZ1PC 900003 V 4 _ Patch & Multi -Select Folders • /2627013 PTT ID Palm 6:53:15 PM 6:53:00 PM !S: `c Sa'R}desc.caltJ.:kJ e: a_L al= L^e Sa'r?‘ cite'aUxt Figure 1-13: MCC 7500 Dispatch GUI. Radio Resources Activity Log Window Based on operator preference, the MCC 7500 GUI can be customized to show details of trumked and conventional channels on a per -channel basis. • 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 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. 1.2.1.4 Console Operations Radio Patch The standard MCC 7500 Dispatch GUI includes patch and multi -select features that can be accessed via a set of dedicated folders. The MCC 7500 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 MCC 7500 Administration application. There can be up to sixteen patch folders and three multi -select folders. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-26 Patch Folders Clicking on one of the patch folder tabs brings it into view. The patch group is opened by clicking on the left -most button on the folder. Once the patch group is open, the patch group is editable and resources 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 resources assigned to them. This is true even if the patch group is not open. The resources of the patch group are shown on the patch folder along with the status of each resource (patched or pending). The resources in the patch also show an indication that they are in a patch group. Some patch groups contain resources that were pre -assigned by the MCC 7500 Administration application. These patch groups become active as soon as the dispatch console begins using the configuration file that contains the pre -assigned patch groups. The dispatch console user can add/remove resources 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 resources of the patch group with a single button press. Figure 1-14 shows an example of a patch folder containing radio resources. Msel 3 I Patch 2 I Patch 3 Patch 1 Msel 9 I Msel 2 Z1 TG_2_00049 Z1 PC_9_00001 Figure 1-14: Patch Folder Indicating Radio Resources. Multi -Select Clicking on one of the multi -select folder tabs brings it into view. The multi -select group is opened by clicking the left -most button on the folder. Once the multi -select group is open, the multi -select becomes active and resources 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. Some multi -select groups contain resources pre -assigned by the MCC 7500 Administration application. The dispatch console user can add/remove resources 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 1-15 shows an example of a multi -select folder containing radio resources. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-27 Patch 1 Patch 21 Patch 3 Msel 1 J Msel 2 I Msel 3 Z1 CONV_01_00003 Z1 CONV 10 00053 Figure 1-15: Multi -Select Folder. Supervisor Mode The Supervisor Levels feature provides a means for establishing a hierarchy of authority between the users of dispatch consoles. This hierarchy is used by the Transmit Priority Levels feature to determine the priority level of each transmission in a console subsystem. There are different levels of dispatch consoles: primary supervisor, secondary supervisor, and non - supervisor. A primary supervisor is the highest level and has priority transmit over all secondary supervisors and non -supervisors. A secondary supervisor is the second highest level and has transmit priority over all non -supervisors. A non -supervisor console is the lowest level and has no transmit priority over any other console. 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. The Supervisor Levels feature allows supervisory personnel to have the transmit priority necessary to carry out their responsibilities in a console subsystem. Finally, console supervisors have the capability to disable and enable operator console functionality as necessary. 1.2.2 Additional Console Equipment 1.2.2.1 Analog Conventional Channel Gateway (CCGW) The physical interface to the analog conventional stations includes a GGM 8000 Gateway fitted with a conventional IP interface kit and is used to interface analog conventional stations to the radio system infrastructure. The portion of the router hardware and software that supports the conventional stations is called the Analog Conventional Channel Gateway (CCGW). The CCGW interfaces conventional analog channels into dispatch operations. The CCGW is a router that provides E&M and tone remote station control and supports the 4 -wire analog connections for conventional. Each CCGW in a system can support up to four channels. 1.2.2.2 Backup Consolettes No backup consolettes are provided. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-28 1.2.3 Logging Recorder Subsystem In an IP environment, there are no dedicated analog outputs for each radio channel or talkgroup to be recorded. Instead, the audio and associated call control information is sent across the IP: therefore, an IP based logging recorder provides a more robust solution over analog recorders requiring dedicated outputs for each recorder channel or talkgroup. The MCC 7500 logging recorder is tightly integrated with Motorola's proposed solution and certified with Motorola's ASTRO 25 trunked network. The logging solution resides on the radio system's IP network enabling the logging to provide more than just basic audio recording. Valuable data associated with each call including radio ID, Alias and talk group is captured. As part of this proposal, one of the existing redundant NiceLog IP Logging Recorders and MS will be moved from the Weld primary dispatch center to the backup center. NICE IP Logging Recorder AIS Workstation U IIIIIIIIIIIIII 1 NICE Playback Station Figure 1-16: MCC 7500 IP Logging Solution. • VPM Console Site Link WAN 1.2.3.1 Archiving Interface Server The Archiving Interface Server (MS) is the interface between the radio system and the logging recorder solution, and provides flexible, high -quality archiving services for audio and data associated with various types of calls and events associated with radio resources. The AIS is a server which allows an IP-based logging recorder to "log onto" the radio system and request talkgroup and conventional channel audio be directed to it for recording. The MS monitors identified resources passes call control information to the logging recorder, and redirects audio for those monitored channels to the logging recorder. Once configured by the logging recorder, the MS sends the audio and any information associated with the call (PTT ID, Alias, Type of Call, etc.) to the recorder. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-29 The MS is comprised of a computer and software and is required for each logging recorder used in a system. 1.2.3.2 MCC 7500 IP Logging Recorder The MCC 7500 IP Logging Recorder and Archiving Interface Server provide a mission critical IP- based digital logging solution for ASTRO 25 systems. The solution, a collaborative effort between Motorola and NICE Systems Inc, was designed to work with the MCC 7500 Dispatch Console and is a fully integrated and certified IP radio recording and replay solution for Motorola's ASTRO 25 network. It provides a reliable and robust solution for customer audio recording requirements. The seamless integration with Motorola's IP infrastructure coupled with the advanced solution application for scenario reconstruction and analysis, helps improve productivity and provides insight from citizen interactions for public safety agencies. The value and strength of the Motorola MCC 7500 IP logging recorder solution is its integration and certification with the Motorola ASTRO 25 network. The logging recorder resides on the radio system's IP network, enabling the logging solution to provide more than just audio recording. Valuable data associated with each call including radio ID and Alias is captured. In addition, tasks or events performed by the dispatcher such as emergency alarms and patches are presented as graphical icons in the Scenario ReplayTM application. The MCC 7500 IP logging solution is fully digital. Audio is recorded in its native vocoded format and the recorder stores it in the same form in which it was passed through the radio system. This eliminates degradation, allowing for optimal audio quality. The addition of secure capability to the dispatch console and the archiving interface server provides true end to end encryption, providing a high degree of security for public safety customers. Radio voice messages remain encrypted the entire time they are being transported between the dispatch console and the two-way radio. 1.2.3.3 NICE Inform The NICE Inform application provides simple control of advanced recording technology allowing users access to the information needed for analysis, investigation, or evidence. NICE Inform fuses different types of multimedia information into a common application and interface. It provides structure to un-structured multimedia, seamlessly combining the data for a complete. authentic, chronological audio/visual timeline and 360 -degree view. NICE Inform provides the ability to: • Monitor and verify communications and interactions. Live Monitoring enables emergency communication center supervisors to rapidly and pro -actively listen -in and instantly review any call. Inform Verify enables Control Centre call takers to instantly review their calls. • Capture telephony, radio and VoIP communications. Record and store all inputs in one place. • Search - simple yet extremely powerful search capabilities that reduce search times dramatically and minimise the use of valuable resources. Users can filter out and narrow down results to find the right transmissions with the minimum amount of effort. • Reconstruct real-time view. Provides an authentic, synchronized, incident reconstruction for investigative or training purposes. • Organizer: Information electronically. Organization of specific and relevant incident and event information by Incident Folder. Allowing instant and secure, web based access for authorized reviewers • Distribute on DVD or email. Flexible, rapid and secure information sharing. Use the NICE Inform Media. Player to encrypt, authenticate and externally review and replay incident Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted System Description 1-30 information of line. Promotes improved interoperability and inter -working between and within public safety organizations. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Description 1-31 SECTION 2 SYSTEM DIAGRAMS System Diagrams are included on the pages that follow. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted System Diagrams 2-1 E a) D O 2 a >. N (000 _ cv -C co _ o a' o a o c/) 2( Q) m .E O E w O I co C TO ^` E C L f— OU) a) a) rE ////F a) c-7, U O E O O `4 U) a 0 W Z O 0 Cl-D N N U) U X CC CI ow cn r H< a)p2UWoU/) QmO gn liow)NN N Core Backhaul Core Backhaul WAN Switch 2 WAN Switch 1 a) L co a) a MO W to Master Si U U U 0 in m o ts `- o o o aa) c cV o o ai u Er) ioa 2 .C ui > o c co o U C MCC 7500 MCC 7500 MCC 7500 MCC 7500 re: 2 0 0 0 i Site Controllers Base Radios Trunking Repeater Site SECTION 3 EQUIPMENT LIST Qty Model Description 7.13 MASTER SITE 1 SQM01 SUM0226 MASTER SITE CONFIGURATION 1 CA02093AA M3 SYSTEM (1-100) 1ST ZONE 1 CA01471AA ADD: WINDOWS SUPPLEMENTAL TRANS CONFIG 1 CA02113AA ASTRO 25 FDMA TRKG OPERATION 13 CA02106AA astro 25 fdma voice site 1 CA02117AA HA SYSTEM1ST ZONE 1 CA01724AB BACK UP & RECOVERY (BAR) 1 CA01722AB FIREWALL MGMT SERVICE 7 CA02105AA MCC7500/MCC7100 CONSOLE LIC 5 CA01316AA ADD: UNC ADDTL DEVICE LIC (QTY 10) 14 CA01208AA ENH: 500 RADIO USER LICENSES 6 ca02193aa ADD: ANTI-MALWARE DEF UPDATE LIC 2 Z13AG ENH: UNIFIED NETWORK CONFIGURATOR (UNC) 2 ZA00921AA PROVISIONING MANAGER 2 CA01224AB ENH: UNIFIED EVENT MANAGER (UEM) 1 ZA00921AB ENH: USER CONFIGURATION INTERFACE (UCI) 1 D999AL ENH: SECURITY PARTITIONING 1 CA01395AA ADD: 700/800 MIXED SITE OPERATION 1 Z619AF ENH: DYNAMIC FREQ BLOCKING 1 CA01453AA ADD: FLEXIBLE AIR TRAFFIC INFORMATION ACCESS 1 ZA00103AA ENH: TECHNICAL ASSISTANCE. TEN HOURS 2 D52AJ ENH: ZONEWATCH 2 DA00148AG ENH: ZONE HISTORICAL REPORTS 2 ZA00149AD ENH: DYNAMIC REPORTS 2 Z801AM ENH: RADIO CONTROL MANAGER 2 ZA00151AG ENH: AFFILIATION USER REPORTS 1 CA01455AA ADD: NORTHBOUND INTERFACE 1 ca02081aa ADD: TRUNKED INTEGRATED DATA 1 ca01725ab ADD: EVENT LOGGING 1 CA01238AA ENH: EMAIL ALARM NOTIFICATIONS 2 tt2565 NM Z420 HIGH TIER WIN7-IE9 64BIT 2 ASTRO 7.13 CLIENT APPLICATION SW T7787 2 DS019BLK 19" LCD. BLACK. NON -TOUCH 1 sqm01sum0205 GGM 8000 GATEWAY 1 CA01616AA ADD: AC POWER Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Equipment List 3-1 Qty Model �� Description 1 c1n1856 2620-24 ETHERNET SWITCH 1 tt2569 RSA AUTHENTICATION MANAGER 7.1 BASE ED. 25 USER LICENSES 1 tt05699 RSA ACE SERVER MAINTENANCE FOR 25 CLIENT ACCESS LICENSES 1 a DDN8653 RSA 5 YEAR HARD TOKEN SOLD ONLY IN MULTIPLES OF 5 1 . LX4000T 8 PORT TERMINAL SERVER, NO DIAL -UP MODEM INCLD. TT2022 6 WINDOWS SUPPLEMENTAL TRANS CONFIG T7449 1 DDN9590 SSG140 FIREWALL W/ 2 YEARS SUPPORT 1 • c1n1856 • 2620-24 ETHERNET SWITCH 1 • SQM01 SUM0205 'ADD: GGM 8000 GATEWAY 1 • CA01616AA • AC POWER 1 SQM01 SUM0205 GGM 8000 GATEWAY 1 CA01616AA ADD: AC POWER 1 sqm01sum0257 UNIFIED NETWORK SERVICES 1 ca02384aa ADD: UNIFIED NETWORK SERVICES SOFTWARE 1 I ca02354aa ADD: ASTRO NETWORK APPLICATION INTERFACE 1 ua00060aa ADD: 5001-10.000 DEVICES FOR PRESENCE 1 ca02362aa ADD: MCAFEE STANDALONE ANTI VIRUS SOFTWAARE 1 ca02358aa ADD: ASTRO NETWORK SERVER 1 ca02053aa ADD: Supplemental CD Transparent IA on Presence and/or Location 1 .dstrak91009e REMOTE SITE REDUNDANT MODULAR FREQUENCY TIMING SYSTEM AC 50 L1700 CABLE: 1,4" SUPERFLEX POLY JKT PER FOOT 4 .DDN9769 2114" TYPE N MALE CONNECTOR FOR FSJ1-50A CABLE 1 SQM01 SUM0227 ISGW SERVER USED FOR ISSI .' CSSI 1 71932 • ISG 1000 FIREWALL W 2 YR SUPPORT 3 ua00004aa ISSI MANUAL ROAMING 10 SIMULTANEOUS TALK GROUP CAPACITY LICENSE 1 SQM01 SUM0238• SRC7500 SWITCHING ROUTING CENTER (7.13 AND BEYOND) 1 ca02194aa ADD: HIGH TIER CORE LAN 96 PORTS 1 CA01345AA ADD: DUAL GATEWAY ROUTERS STANDARD 1 ca01355aa ADD: DUAL LINK 2 PAIRS CWR 1 ca01347aa ADD: QTY 2 PAIRS CORE ROUTERS CWR 1 I CA01360AA ADD: CORE BACKHAUL SWITCHES 1 ca01361aa ADD: GGSN 2 THN1012 RACK 7' OPEN 7 DSOP820B PDU, 120V HARDWIRE (8) 20A OUTLET PDU WITH TYPE 3 SAD PROTECTION 4 dsrmp615a SPD. TYPE 3. 120V RACK MOUNT. 15A PLUG-IN W' (6) 15A NEMA 5-15 OUTLETS 7 . DS1101378 RACK MT ADAPTER PLATE. 19 IN FOR DSOP820B. DSOP820B2 & DSNSOP820B 11 DSTSJ100BT SPD, RJ-48 CONNECTED FOR T1/E1. 10/100BT PROTECTS/PASSES ON ALL 8 PIN 11 DSTSJADP RACK MOUNT GROUND BAR. 19 IN FOR TSJ AND WPH SERIES DATA SPDS 1 DVN4046 MASTER SYSTEM KEY STARTER KIT 1 SQM01 SUM0227 • ISGW ? SERVER USED FOR ISSI / CSSI 1 TT1932 ISG 1000 FIREWALL W 2 YR SUPPORT Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Equipment List 3-2 Qty Model Description 1 SQM01 SUM0205 GGM 8000 GATEWAY 1 CA01616AA ADD: AC POWER 1 c1n1856 2620-24 ETHERNET SWITCH 1 CLN1838 FRU: 3500-48 ETHERNET SWITCH 1 c1n1856 2620-24 ETHERNET SWITCH 1 CLN1837A 620 REDUNDANTEXTERNAL POWER SUPPLY 1 CLN8489 48 PORT TERMINAL SERVER 1 ST6018 S6000 12 PORT T1'E1 II MODULE 1 CO-OP WAN ROUTER RELAY PANEL T7380 1 ST6011 S6000 4 -PORT FLEXWAN MODULE 1 ST6202 SRC 24 PORT T1/E1 EXP II 1 DKN6144A ASSY.CBL.3 FT.RELAY PNL,CWR.S6000 1 DDN9590 SSG140 FIREWALL W/ 2 YEARS SUPPORT 1 ddn1073 DL360 VIRTUAL SERVER - NO OS NON -RETURNABLE 1 d1n6742 460 WATT POWER SUPPLY 1 d1n6744 300 GB SAS HARD DISK DRIVE 1 dIn6745 DVD-RW SATA DRIVE (DL360) 1 d1n6822 FRE: DL380p G8 HC 300GB DISK 2 d1n6823 FRE: DL380 G8p LC 300GB DISK 1 d1n6864 FRU: DL380 G8p POWER SUPPLY 1 d1n6844 CPH 300 GB HARD DRIVE 1 dIn6866 DVD DRIVE 1 dIn6880 DAS - CHASSIS ONLY 1 dIn6878 DAS - 600 GB SAS HARD DRIVE 1 d1n6879 DAS - PROCESSOR MODULE 1 d1n6867 DAS POWER SUPPLY 1 ckn6952 SAS CABLE 1M Weld County RF site and Console Upgrade 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 15 CA00899AA ADD: MCC 7500 DISPATCH CONSOLE SOFTWARE REFRESH LICENSE 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 2 CA00900AA ADD: MCC 7500 AIS SOFTWARE REFRESH LICENSE 2 FVN5707 SDM3000 MCC7500 AUX 1O F'W FOR A7.7 2 72159 NICE UPGRADE SOFTWARE TO 7.7 SYSTEM RELEASE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 CA01246AA ADD: MCC 7500 CONV SITE UPGRADE 1 T6931 ASTRO 25 TRUNKING SOFTWARE 8 CA00276AA ADD: PSC 9600 SOFTWARE UPGRADE 1 T6693 SOFTWARE DOWNLOAD UPGRADE KIT 13 X418 ADD: ASTRO 25 SITE REPEATER UPG 13 X591AB ADD: ASTRO25 SITE REPEATER UPGRADE Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Equipment List 3-3 Qty Model Description 1 T7140 G -SERIES SOFTWARE UPGRADE 6 ca01116aa ADD: SITE REPEATER BR SW UPGRADE 1 T6957 700 MHZ SITE REPEATER SW MIGRATION 9 X870AA ENH: STR 3000 LATEST SHIPPING SOFTWARE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 ca02219ba SITE RPTR SC SW UPGRD ? IV&D 1 T7140 G -SERIES SOFTWARE UPGRADE 12 CA01116AA ADD: SITE REPEATER BR SW UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 CA01196AA ADD: IP BASED MULTISITE SITE CONTROLLER SOFTWARE UPGRADE 6 ca02206ba SIMUL REM SITE UPGRD LIC?IV&D 1 T7140 G -SERIES SOFTWARE UPGRADE 36 CA01195AA ADD: IP BASED MULTISITE BASE RADIO SOFTWARE UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 12 CA01197AA ADD: IP BASED MULTISITE OPERATION UPGRADE 1 tt2404 MICROSOFT WINDOWS 7 PRO 64 BIT MEDIA DISK 15 TT05654AA REQUIRED OPTION - MS WINDOWS PRO 7 CLIENT LICENSES (MIN 5) 2 REQUIRED OPTION - MS WINDOWS PRO 7 CLIENT LICENSES (MIN 5) TT05654AA 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 15 CA00899AA ADD: MCC 7500 DISPATCH CONSOLE SOFTWARE REFRESH LICENSE 15 DDN1243 IRR SOFTWARE UPGRADE TO V -45 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 2 CA00900AA ADD: MCC 7500 AIS SOFTWARE REFRESH LICENSE 2 FVN5889 SDM3000 MCC 7500 AUX 1O FAN FOR A7.11 1 T7140 G -SERIES SOFTWARE UPGRADE 2 CA01246AA ADD: MCC 7500 CONV SITE UPGRADE 1 T6931 ASTRO 25 TRUNKING SOFTWARE 8 CA00276AA ADD: PSC 9600 SOFTWARE UPGRADE 1 T6693 SOFTWARE DOWNLOAD UPGRADE KIT 13 X418 ADD: ASTRO 25 SITE REPEATER UPG 13 X591AB ADD: ASTRO25 SITE REPEATER UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 6 CA01116AA ADD: SITE REPEATER BR SW UPGRADE 1 T6957 700 MHZ SITE REPEATER SW MIGRATION 9 X870AA ENH: STR 3000 LATEST SHIPPING SOFTWARE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 ca02219ba ADD: SITE REPEATER SC SW UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 6 CA01116AA ADD: SITE REPEATER BR SW UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 CA01196AA ADD: IP BASED MULTISITE SITE CONTROLLER SOFTWARE UPGRADE Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Equipment List 3-4 Qty Model • Description 6 ca02206ba SIMUL REM SITE UPGRD LIC?IV&D 1 T7140 G -SERIES SOFTWARE UPGRADE 36 CA01195AA ADD: IP BASED MULTISITE BASE RADIO SOFTWARE UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 12 CA01197AA ADD: IP BASED MULTISITE OPERATION UPGRADE 1 DLN6455 CONFIGURATION/SERVICE SOFTWARE 2 WINDOWS SUPPLEMENTAL TRANS CONFIG T7449 2 ST5140A HP PROCURVE OS UPGRADE 2 ST5100 MNR ASTRa SMARTZONE SOFTWARE UPGRADE 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 15 CA00899AA ADD: MCC 7500 DISPATCH CONSOLE SOFTWARE REFRESH LICENSE 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 2 CA00900AA ADD: MCC 7500 AIS SOFTWARE REFRESH LICENSE 2 FVN5972 SDM3000 MCC7500 AUX 1O F'W FOR A7.13 1 t7140 G -SERIES SOFTWARE UPGRADE 2 ca01246aa ADD: MCC 7500 CONV SITE UPGRADE 1 T6931 ASTRO 25 TRUNKING SOFTWARE 8 CA00276AA ADD: PSC 9600 SOFTWARE UPGRADE 1 T6693 SOFTWARE DOWNLOAD UPGRADE KIT 13 X418 ADD: ASTRO 25 SITE REPEATER UPG 13 X591AB ADD: ASTRO25 SITE REPEATER UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 6 CA01116AA ADD: SITE REPEATER BR SW UPGRADE 1 T6957 700 MHZ SITE REPEATER SW MIGRATION 9 X870AA ENH: STR 3000 LATEST SHIPPING SOFTWARE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 ca02219ba SITE RPTR SC SW UPGRD ? IV&D 1 T7140 G -SERIES SOFTWARE UPGRADE 6 CA01116AA ADD: SITE REPEATER BR SW UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 2 CA01196AA ADD: IP BASED MULTISITE SITE CONTROLLER SOFTWARE UPGRADE 6 ca02206ba SIMUL REM SITE UPGRD LIC?IV&D 1 T7140 G -SERIES SOFTWARE UPGRADE 36 CA01195AA ADD: IP BASED MULTISITE BASE RADIO SOFTWARE UPGRADE 1 T7140 G -SERIES SOFTWARE UPGRADE 6 CA01197AA ADD: IP BASED MULTISITE OPERATION UPGRADE 1 DLN6455 CONFIGURATION/SERVICE SOFTWARE 2 WINDOWS SUPPLEMENTAL TRANS CONFIG T7449 17 MCAFEE WINDOWS AV CLIENT T7885 1 tt2543 NICE UPGRADE SOFTWARE TO 7.13 SYSTEM RELEASE 3 ST2511 S2500 FLEXWAN DAUGHTER BOARD Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restncted Equipment List 3-5 Qty Model; Description 2 dqwindows2008R1 WINDOWS SERVER 2008 R1 32 BIT O/S 1 tt2595 FULL INFORM UPGRADE FROM R3.2 TO R5.1 32 b1913 MCC SERIES HEADSET JACK WELD COUNTY BACKUP DISPATCH CENTER 1 SQM01 SUM0239 MASTER SITE CONFIG UPGRADE 1 CA00996AK NM/ZC LICENSE KEY 7.13 1 CA00997AK UCS LICENSE KEY 7.13 3 CA02105AA MCC7500rMCC7100 CONSOLE LIC 1 B1905 MCC 7500 ASTRO 25 SOFTWARE 14 B1933 MOTOROLA VOICE PROCESSOR MODULE 14 CA01642AA ADD: MCC 7500 BASIC CONSOLE FUNCTIONALITY SOFTWARE LICENSE 14 CA01643AA ADD: MCC 7500 / MCC 7100 TRUNKING OPERATION 14 CA00147AF ADD: MCC 7500 SECURE OPERATION 14 CA00143AC ADD: DES-OFB ALGORITHM 14 CA00182AB ADD: AES ALGORITHM 14 CA00245AA ADD: ADP ALGORITHM 14 CA00140AA ADD: AC LINE CORD. NORTH AMERICAN 14 DS019BLK 19" LCD. BLACK. NON -TOUCH 14 Z420 LOW TIER WORKSTATION WINDOWS 7 64BIT 72538 14 WINDOWS SUPPLEMENTAL TRANS CONFIG T7449 14 DSRMP615A SPD. TYPE 3. 120V RACK MOUNT. 15A PLUG-IN WI (6) 15A NEMA 5-15 OUTLETS 28 B1912 MCC SERIES DESKTOP SPEAKER 14 B1914 MCC SERIES DESKTOP GOOSENECK MICROPHONE 28 B1913 MCC SERIES HEADSET JACK 14 DSTWIN6328A PROVIDES ONE DUAL PEDAL FOOTSWITCH FOR USE WITH MOTOROLA MCC 7500 DISP 14 MCAFEE WINDOWS AV CLIENT T7885 14 DDN1245 DUAL IRR SW USB HASP WITH LICENSE (VERSION 45) 14 DDN1118 PCI EXPRESS SOUND BLASTER X-FI XTREME AUDIO 14 CDN6673 CREATIVE LABS INSPIRE A60 3 CLN1856 2620-24 ETHERNET SWITCH 2 SQM01 SUM0205 GGM 8000 GATEWAY 2 CA01616AA ADD: AC POWER 1 F4543 SITE MANAGER BASIC 1 VA00212 SDM3000 MCC 7500 AUX 1O FAN FOR A7.13 1 V266 ADD: 90VAC TO 260VAC PS TO SM 3 V592 AAD TERM BLCK & CONN WI 1 GCP 8000 SITE CONTROLLER T7038 1 CA00303AA ADD: QTY (1) SITE CONTROLLER 1 X153AW ADD: RACK MOUNT HARDWARE 1 CA01136AA ADD: MCC 7500 CONVEN SITE OPER Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Equipment List 3-6 Qty Model Description 5 SQM01 SUM0205 GGM 8000 GATEWAY 5 CA01616AA ADD: AC POWER 5 CA02141AA ADD: LOW DENSITY ENH CONV GATEWAY 3 DQPS1 D NICE PROFESSIONAL SERVICES 1 JUNIPER/FIREWALL GATEWAY T7376 1 CLN1856 2620-24 ETHERNET SWITCH 3 TRN7343 SEVEN AND A HALF FOOT RACK 3 DSOP820B PDU. 120V HARDWIRE (8) 20A OUTLET PDU WITH TYPE 3 SAD PROTECTION 3 DS1101378 RACK MT ADAPTER PLATE. 19 IN FOR DSOP820B, DSOP820B2 & DSNSOP820B 2 DSTSJ100BT SPD. RJ-48 CONNECTED FOR T11E1. 10/100BT PROTECTS'PASSES ON ALL 8 PIN 1 DSTSJADP RACK MOUNT GROUND BAR. 19 IN FOR TSJ AND WPH SERIES DATA SPDS 3 DSRMP615A SPD. TYPE 3. 120V RACK MOUNT. 15A PLUG-IN W' (6) 15A NEMA 5-15 OUTLETS 1 DDN8325 17" LCD DRAWER WKEYBOARD & MOUSE. KVM 16 PORTS. CABLES 2 DDN9748 19 INCH BLACK SHELF 1 B1912 MCC SERIES DESKTOP SPEAKER 1 B1914 MCC SERIES DESKTOP GOOSENECK MICROPHONE 1 B1913 MCC SERIES HEADSET JACK 1 SQM01 SUM0205 GGM 8000 GATEWAY 1 CA01616AA ADD: AC POWER 1 Z420 LOW TIER WORKSTATION WINDOWS 7 64BIT 72538 1 B1934 MCC 7500 VOICE PROCESSOR MODULE FRU 1 CA00147AF ADD: MCC 7500 SECURE OPERATION 1 CA00143AC ADD: DES-OFB ALGORITHM 1 CA00182AB ADD: AES ALGORITHM 1 CA00245AA ADD: ADP ALGORITHM 1 DS019BLK 19" LCD, BLACK. NON -TOUCH 1 CLN1856 2620-24 ETHERNET SWITCH Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Equipment List 3-7 SECTION 4 STATEMENT OF WORK 4.1 OVERVIEW This Statement of Work (SOW) describes the deliverables to be fiunished to Weld County. The tasks described herein will be performed by Motorola, its subcontractors. and Weld County to implement the solution described in the System Description. It describes the actual work involved in installation, identifies the installation standards to be followed, and clarifies the responsibilities for Motorola and Weld County during the project implementation. Specifically, this SOW provides: • A summary of the phases and tasks to be completed within the project lifecycle. • A list of the deliverables associated with the project. • A description of the responsibilities for both Motorola and Customer. • The qualifications and assumptions taken into consideration during the development of this project. This SOW provides the most current understanding of the work required by both parties to ensure a successful project implementation. In particular, Motorola has made assumptions of the sites to be used for the new system. Should any of the sites change, a revision to the SOW and associated pricing will be required. It is understood that this SOW is a working document, and that it will be revised as needed 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. Motorola Solutions, Inc. (Motorola) proposed design for Weld County) is a Project 25 (P25) compliant, digital trunked communications system specifically designed to provide a regional P25 Standards Based system for Weld County. Motorola's proposed system leverages the existing Weld County equipment investment, and provides a state-of-the-art, mission critical, highly reliable system. The proposed design will provide an M3 Core (to be located at ADCOM), and the upgrade eight Weld County sites from 7.5 to 7.13. The proposal includes a new MCC 7500 14 position backup dispatch center for Weld County. The new Master Site will become an interoperability network node utilizing ISSI links to three other existing systems in the Denver Metro Area. 4.2 ASSUMPTIONS Motorola has based the system design on information provided by Weld County and an analysis of their system requirements. All assumptions have been listed below for review. Should Motorola's assumptions be deemed incorrect or not agreeable to Weld County, a revised proposal with the necessary changes and adjusted costs may be required. Changes to the equipment or scope of the project after contract may require a change order • Weld County is responsible for negotiating with ADCOM to locate the M3 Core in the ADCOM facility in Commerce City. If the M3 Core is not installed at ADCOM in Commerce City, CO a Change Order will be required to locate it in an alternate location. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-1 • Weld County will supply all primary power, AC circuits and outlets, Unintemiptible Power Supplies, and ensure all facilities and buildings meet R56 including any Type 1 and Type 2 surge protection that may be required. • Weld County will provide connectivity between the M3 Core location and all RF/dispatch sites. This will include Ethernet connections between the M3 core site and the Weld Simulcast cell, SE Weld site, Tri-Area site, Weld primary and backup dispatch centers. Weld County will provide T1 connection to the New Raymer, Grover and Nunn RF sites. • All Ethernet and T1 links will be available and tested prior to cutover commencing. • All alarms being reported via MOSCAD on the CO DTR system are the responsibility of Weld County to report via other means. MOSCAD is not included in this proposal. Therefore, all alarms now being reported via MOSCAD on the DTR system will no longer be reported via the proposed ASTRO 25 system. • Weld County is responsible for all database entry for the proposed 7.13 M3 Core. This includes all sites, mobiles, portables and dispatch centers as they relate to Unit IDs and Talkgroup IDs. It is assumed this database entry will be completed prior to cutover. • Weld County is responsible for programming the new system into all Weld County and Greeley mobiles, portables and control stations. Weld County is also responsible for any subscriber upgrades that may be required. No subscriber software is included in this proposal. • Weld County is responsible for all radio programming templates required for subscriber radios. • Weld County to supply VPM hardware for the MCC 7500 console upgrade. • Weld County to supply a 2M LAN connection to each operator position and MS server for the upgrade from GPIOM to VPM during the MCC 7500 console upgrade. • Both Weld County MCC 7500 dispatch centers are R56 compliant and that ground bars exist below all existing dispatch operator positions. • Weld County to supply communications center and equipment room that have adequate space, cable trays and are R56 compliant for the location of the backup dispatch center. • Weld County to supply all primary power, backup power, AC circuits, Type 1 and 2 AC surge suppression for the backup communications center. • Weld County to supply all connectivity for the backup communications center. This includes between the center and the M3 Core and between the center and any RF resources the center is required to control. Motorola will program and provision the customer supplied microwave for T1 circuits to connect the dispatch center to the M3 core and the existing RF channels to the backup MCC console. • All Weld County existing conventional console resources are configured for 4W Tone operation and no desksets are attached to any conventional resources. • Data applications such as POP25, Outdoor Location Service, Text Messaging and Over the Air Rekeying require the mobile and portable radios to be equipped with Packet Data, RS232, POP25, Text Messaging, OTAR and encryption. It is the responsibility of Weld County to ensure the mobiles and portables have the appropriate software options. These options are not included in this proposal. • Weld County will provide all required liaison support with the agencies required to support the upgrades. • Weld County will notify local agencies of any disruption in service that may be required during the upgrade. • Weld County will coordinate with local agencies for timing of outages required by the upgrade and field any calls from local agencies during the upgrade. • It is assumed that all existing Weld RF site and the existing Weld County MCC7500 hardware is in good working condition and capable of being upgraded. • All work is to be performed during normal work hours, Monday through Friday 8:00 a.m. to 5:00 p.m. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-2 • Motorola is not responsible for interference caused or received by the Motorola provided equipment except for interference that is directly caused by the Motorola -provided transmitter(s) to the Motorola -provided receiver(s). Should Weld County's system experience interference, Motorola can be contracted to investigate the source and recommend solutions to mitigate the issue. 4.3 CONTRACT 4.3.1 Contract Award (Milestone) • Weld County and Motorola execute the contract and both parties receive all the necessary documentation. 4.3.2 Contract Administration Motorola 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 information system. • Schedule the project kickoff meeting with Weld County. Customer Responsibilities: • Assign a Project Manager, as the single point of contact responsible for Customer -signed approvals. • Assign other resources necessary to ensure completion of project tasks for which the Customer agencies are responsible. Completion Criteria: • Motorola internal processes are set up for project management. • Both Motorola and Weld County assign all required resources. • Project kickoff meeting is scheduled. 4.3.3 Project Kickoff Motorola 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 Weld County. • Review the resource and scheduling requirements with Weld County. • Review the Project Schedule with Weld County to address upcoming milestones and/or events. • Review the teams' interactions (Motorola and Weld County), meetings, reports, milestone acceptance, and the Agencies' participation in particular phases. Customer Responsibilities: • Weld County key project team participants attend the meeting. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-3 • Review Motorola and Agency responsibilities. Completion Criteria: • Project kickoff meeting completed. • Meeting notes identify the next action items. 4.4 CONTRACT DESIGN REVIEW 4.4.1 Review Contract Design Motorola Responsibilities: • Meet with the Weld County project team. • Review the operational requirements and the impact of those requirements on various equipment configurations. • Establish a defined baseline for the system design and identify any special product requirements and their impact on system implementation. • 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 Weld County for approval. These documents form the basis of the system, which Motorola will manufacture, assemble, stage, and install. • Prepare equipment layout plans for staging and field installations. • Provide acceptable performance specifications for microwave, fiber, or copper links. Establish demarcation point (supplied by the Motorola system engineer) to define the connection point between the Motorola -supplied equipment and the Agency -supplied link(s) and external interfaces. • Finalize site acquisition and development plan. - Conduct (updated) site evaluations to capture site details of the system design and to determine site readiness (when necessary). - Determine each site's ability to accommodate proposed equipment based upon physical capacity. - If applicable, test existing equipment with which Motorola equipment will interface. • Prepare Site Evaluation Report that summarizes findings of above -described site evaluations (when necessary). • Work with Weld County to identify radio interference between the new communication system and other existing radio systems. Restrictions: - Motorola assumes no liability or responsibility for inadequate frequency availability or frequency licensing issues. — Motorola is not responsible for issues outside of its immediate control. Such issues include, but are not restricted to, improper frequency coordination by others and non -compliant operation of other radios. - Motorola is not responsible for co -channel interference due to errors in frequency coordination by APCO or any other unlisted frequencies, or the improper design, installation, or operation of systems installed or operated by others If, for any reason, any of the proposed sites cannot be utilized due to reasons beyond Motorola's control, the costs associated with site changes or delays including, but not limited to, re -engineering, frequency re -licensing, site zoning, site permitting, schedule delays, site minimum Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-4 abnormalities, re -mobilization, etc., will be paid for by Weld County and documented through the change order process. Customer Responsibilities: • Weld County's key project team participants attend the meeting. • Make timely decisions, according to the Project Schedule. • Frequency Licensing and Interference: - As mandated by FCC, the Customer, as the licensee, has the ultimate responsibility for providing all required radio licensing or licensing modifications for the system prior to system staging. This responsibility includes paying for FCC licensing and frequency coordination fees. - Provide the FCC "call sign" station identifier for each site prior to system staging. 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. • A Change Order is executed in accordance with all material changes resulting from the Design Review to the contract. 4.4.2 Design Approval (Milestone) • Weld County executes a Design Approval milestone document. 4.5 ORDER PROCESSING 4.5.1 Process Equipment List Motorola Responsibilities: • Validate Equipment List by checking for valid model numbers, versions, compatible options to main equipment, and delivery data. • Enter order into Motorola's Customer Order Fulfillment (COF) system. • Create Ship Views, to confirm with the Agencies 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 if applicable. Customer Responsibilities: • Approve shipping location(s). Completion Criteria: • Verify that the Equipment List contains the correct model numbers, version, options, and delivery data. • Trial validation completed. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-5 • Bridge the equipment order to the manufacturing facility. 4.6 MANUFACTURING AND STAGING 4.6.1 Manufacture Motorola Fixed Network Equipment Motorola Responsibilities: • Manufacture the Fixed Network Equipment (FNE) necessary for the system based on equipment order. Customer Responsibilities: • None. Completion Criteria: • FNE shipped to either the field or the staging facility. 4.6.2 Manufacture Non -Motorola Equipment Motorola Responsibilities: • Procure non -Motorola equipment necessary for the system based on equipment order. Customer Responsibilities: • None. Completion Criteria: • Ship non -Motorola manufactured equipment to the field and/or the staging facility. 4.6.3 Ship to Staging (Milestone) • Ship all equipment needed for staging to Motorola's factory staging facility in Schaumburg, Illinois [Customer Center for Solutions Integration (CCSi)]. 4.6.4 Stage System Motorola Responsibilities: • Set up and rack the system equipment on a site -by -site basis, as it will be configured in the field at each of the transmitter/receiver sites. • 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 ("connectorization" of the subsystems). • 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 ming template tool. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-6 • 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. Customer 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. 4.6.5 Perform Staging Acceptance Test Procedures Motorola Responsibilities: • Test and validate system software and features. • Functional testing of standard system features. • Conduct site and system level testing. • Power -up site equipment and perform standardized functionality tests. • Perform system burn -in 24 hours a day during staging to isolate and capture any defects. Customer Responsibilities: • None Completion Criteria: • Factory Acceptance Testing complete. 4.6.6 Ship Equipment to Field Motorola Responsibilities: • Pack system for shipment to final destination. • Arrange for shipment to the field. Customer Responsibilities: • None. Completion Criteria: • Equipment ready for shipment to the field. 4.6.7 CCSi Ship Acceptance (Milestone) • All equipment shipped to the field. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-7 4.7 CIVIL WORK FOR THE CUSTOMER -PROVIDED FACILITIES Motorola Responsibilities: • Provide electrical requirements for each equipment rack to be installed in the Weld County - provided facilities. • Provide heat load for each equipment rack to be installed in the Weld County -provided facilities. • Terminate the Motorola provided equipment at the customer supplied AC outlets in all RF sites and dispatch centers. Customer Responsibilities: • If applicable and based on local jurisdictional authority, the Customer will be responsible for any installation or up -grades of the Critical Operation Power Systems in order to comply with NFPA 70, Article 708. • Secure site lease/ownership, zoning, permits, regulatory approvals, easements, power, and Telco connections. • Provide clear and stable access to the sites for transporting electronics and other materials. Sufficient site access must be available for trucks to deliver materials under their own power and for personnel to move materials to the facility without assistance from special equipment. • Design and construct facilities for housing communications equipment such as shelters, towers, generators, fuel tanks, fenced compounds, etc. • Supply adequately sized electrical service, backup power (UPS, generator, batteries, etc.) including the installation of conduit, circuit breakers, outlets, etc., at each equipment location. • Provide AC power to the demarcation point(s) indicated in the documentation. including the associated electrical service and wiring (conduit, circuit breakers, etc.). The customer shall supply a dedicated 20A, AC outlet — simplex with ground for each major piece of equipment within 6 feet of the location of the Motorola supplied equipment. • Provide adequate HVAC, grounding, lighting, cable routing, and surge protection (also, among existing and Motorola -provided equipment) based upon Motorola's Standards and Guidelines for Communication Sites (R56). Ceiling ( 9 feet) and cable tray heights (minimum 8 feet) in the equipment rooms in order to accommodate 7 -foot, 6 -inch equipment racks. • Provide floor space and desk space for the System equipment at the Customer -provided facilities. Each rack shall be provided a minimum of 24 -inch x 24 -inch footprint with 36 -inch clearance in the front and back. • Relocate existing equipment, if needed, to provide required space for the installation of Motorola - supplied equipment. • Bring grounding system up to Motorola's R56 standards and supply a single point system ground, of 5 ohms or less, to be used on all FNE supplied under the Contract. Supply grounding tie point within 10 feet from the Motorola -supplied equipment. • Provide all necessary wall or roof penetrations on existing buildings for antenna coax and microwave waveguide (if applicable) for main transmitter antennas, microwave radios, and control station Yagi antennas. • Provide obstruction -free area for the cable nm between the demarcation point and the communications equipment. • Resolve any environmental issues including, but not limited to, asbestos, structural integrity (rooftop, water tank, tower, etc.) of the site, and any other building risks. (Resolve environmental or hazardous material issues). • Arrange for space on the tower for installation of new antennas at the proposed heights. • Perform structural analysis of existing tower and rooftops as required to confirm that the structure is capable of supporting proposed and future antenna loads. • Supply all permits as contractually required. minimum Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-8 • Supply interior building cable trays, raceways, conduits, and wire supports. • Supply engineering and drafting as required for modifications to existing building drawings for site construction. • Pay for usage costs of power and generator fueling, both during the construction and installation effort, and on an ongoing basis. • Complete all customer deliverables in accordance within the approved project schedule. Completion Criteria: • All sites are ready for equipment installations in compliance with Motorola's R56 standards. 4.8 SYSTEM INSTALLATION 4.8.1 Install Fixed Network Equipment Motorola Responsibilities: • Motorola 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)/Transport Canada, and FCC standards and regulations/Industry Canada. • For installation of the fixed equipment at the various sites, Motorola will furnish all cables for power, audio, control, and radio transmission to connect the Motorola supplied equipment to the power panels or receptacles and the audio/control line connection point. • 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. • Will provide storage location for the Motorola -provided equipment. • Receive and inventory all equipment. • Bond the supplied equipment to the site ground system in accordance with Motorola's R56 standards. • Upgrade existing Weld County RF sites to 7.13 as detailed in the System Description section of this proposal. • Will not interface with the following network connections: • Will not interface to existing alarms that are currently being reported on the CO DTR MOSCAD system. • Will remove existing equipment. • Will relocate existing equipment to a location designated by Weld County. • Will not dispose of existing equipment. Customer Responsibilities: • Provide secure storage for the Motorola -provided equipment, at a location central to the sites. Motorola coordinates the receipt of the equipment with Weld County's designated contact, and inventory all equipment. • Provide access to the sites, as necessary. • Provide all required liaison support with the agencies required to support the upgrades. • Notify local agencies of any disruption in service that may be required during the upgrade. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Statement of Work 4-9 • Coordinate with local agencies for timing of outages required by the upgrade and field any calls from the local agencies during the upgrade. Completion Criteria: • Fixed Network Equipment installation completed and ready for optimization. 4.8.2 Fixed Network Equipment Installation Complete • All fixed network equipment installed and accepted by the Agency. 4.8.3 Console Installation Motorola Responsibilities: • Install the Weld County back up consoles as detailed in the System Description in the space provided by Weld County. • Connect the Weld County -supplied, previously -identified circuits into the console, to a demarcation point located within 25 feet of the console interface. • Terminate the audio outputs for the logged talkgroups onto a punchblock, and then terminate these outputs into the logging recorder. • Install a dedicated Local Area Network (LAN) at the Weld County back up dispatch centers to connect the proposed console positions. • Connect the appropriate equipment to the Weld -supplied ground systems in accordance with Motorola's R56 Site Installation standards. • Perform the console programming of the Weld County backup console, based on the programming of the existing Weld County MCC 7500 console. • For consoles not located at the master site, additional network link resources will be required, as identified in the network diagram provided by Motorola. • Upgrade the primary Weld County MCC 7500 console as detailed in the System Description. Customer Responsibilities: • Provide demarcation point located within 25 feet of the console interface. • Install a dedicated Local Area Network (LAN) at the Weld County primary dispatch center to connect the proposed upgraded VPM console positions. • Provide the VPM hardware at the Weld County primary dispatch center required for the upgrade of the MCC 7500. • Provide conventional resources that are configured for 4 Wire Tone operation. These conventional resources will not have desksets connected in parallel. • Provide all connectivity between the centers and the M3 master site. • Provide all connectivity between the dispatch centers and the existing conventional resources. Completion Criteria: • Console installation is complete. 4.8.4 Console Installation Complete • Console installation completed and accepted by Weld County. 4.8.5 System Installation Acceptance (Milestone) • All equipment installations are completed and accepted by Weld County. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Statement of Work 4-10 4.9 SYSTEM OPTIMIZATION 4.9.1 Optimize System FNE Motorola Responsibilities: • Motorola and its subcontractors optimize each subsystem that required optimization. Existing sites being upgraded from 7.5 to 7.13 do not require optimization • Verify that all equipment is operating properly and that all electrical and signal levels are set accurately at new RF sites. • Verify that all audio and data levels are at factory settings at new RF sites. • Check forward and reflected power for all radio equipment, after connection to the antenna systems, to verify that power is within tolerances at new RF sites. • Check audio and data levels to verify factory settings at new RF sites. • Verify communication interfaces between devices for proper operation at new RF sites. • Test features and functionality are in accordance with manufacturers' specifications and that they comply with the final configuration established during the CDR/system staging at new RF sites. • • Install and integrate the RF sites with the system, then optimize and activate the SmartZone controller. • Integrate the consoles and RF sites into the system to ensure proper operation. • Set up the Weld County backup consoles on the radio system to perform the dispatching operation. Customer Responsibilities: • Provide access/escort to the sites. Provide required radio ID and alias information to enable alias database setup for interface to console. • Input all database information into the system for the Weld County RF sites, dispatch consoles and all mobiles and portables that will operate on the system. • Define the logging recorder tracks by talkgroup for the Weld County backup consoles. • Dispatchers to use the existing conventional system icons for dispatching until cutover. Completion Criteria: • System FNE optimization is complete. 4.9.2 Link Verification Motorola Responsibilities: • Perform test to verify site link performance, prior to the interconnection of the Motorola -supplied equipment to the link equipment. It should be noted that 900 MHz, 2.4 GHz, and 5.2/5.4/5.8 Gil: bands are unlicensed. Therefore, Motorola has no control over signal emissions in these bands that may interfere with the desired signals. Although link surreys will identifi' possible existing interference sources, there is no guarantee that interference will not emerge after the sun•ev. Motorola can assist Weld Count' in assessing interference issues if they occur, however, the cost for the services and any additional equipment necessary to resolve the interference problem are beyond the scope of the generic link surrey and installation. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-11 Customer Responsibilities: • Make available the required links which meet the specifications supplied by Motorola at the CDR. 4.9.3 Completion Criteria: • Link verification successfully completed. 4.9.4 Optimization Complete • System optimization is completed. Motorola and Weld County agree that the equipment is ready for acceptance testing. 4.10 TRAINING 4.10.1 Perform Training Motorola Responsibilities: • Finalize training schedules purchased as part of this project with the Weld County Project Manager. • Conduct the training classes outlined in the Training Plan. Customer Responsibilities: • Attend training classes. • Comply with the prerequisites in the Training Plan. Completion Criteria: • All training classes completed. 4.10.2 Training Complete • All training classes completed. 4.11 AUDIT AND ACCEPTANCE TESTING 4.11.1 Perform R56 Installation Audit Motorola 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's Standards and Guidelines for Communication Sites (R56). Customer Responsibilities: • Provide access/escort to the sites. • Witness tests. (if desired) Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-12 Completion Criteria: • All R56 audits completed successfully. 4.11.2 Perform Equipment Testing Motorola Responsibilities: • Test individual components of the system to verify compliance to the equipment specifications. • Repeat any failed test(s) once Motorola (or the Agency) has completed the corrective action(s). • Prepare documentation of component tests to be delivered as part of the final documentation package. Customer Responsibilities: • Witness tests if desired. Completion Criteria: • Successful completion of equipment testing. 4.11.3 Perform Functional Testing Motorola Responsibilities: • Verify the operational functionality and features of the individual subsystems and the system supplied by Motorola, as contracted. • If any major task as contractually described fails, repeat that particular task after Motorola 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 Weld County for review. • Resolve any minor task failures before Final System Acceptance. Customer Responsibilities: • Witness the functional testing. Completion Criteria: • Successful completion of the functional testing. • Weld County approval of the functional testing. 4.11.4 System Acceptance Test Procedures (Milestone) • Weld County approves the completion of all the required tests. 4.12 FINALIZE 4.12.1 Cutover Motorola Responsibilities: • Motorola and the Agencies develop 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. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Statement of Work 4-13 • 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 dining the general operation of the system. Customer Responsibilities: • Attend cutover meetings and approve the cutover plan. • Notify the user groups) affected by the cutover (date and time). • Conduct a roll call of all users working dining 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 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. 4.12.2 Resolve Punchlist Motorola Responsibilities: • Work with the Agencies to resolve punchlist items, documented dining the Acceptance Testing phase, in order to meet all the criteria for final system acceptance. Customer Responsibilities: • Assist Motorola with resolution of identified punchlist items by providing support, such as access to the sites, equipment and system. and approval of the resolved punchlist item(s). Completion Criteria: • All punchlist items resolved and approved by Weld County. 4.12.3 Transition to Service/Project Transition Certificate Motorola 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. Customer Responsibilities: • Participate in the Transition Service/Project Transition Certificate (PTC) process. • Complete the attached NICE Remote Access Consent Form Customer Remote Access Consent Form Completion Criteria: • All service information has been delivered and approved by Weld County. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Statement of Work 4-14 4.12.4 Finalize Documentation Motorola Responsibilities: • Provide an electronic as -built system manual on a Compact Disc (CD). The documentation will include the following: — System -Level Diagram - Site Block Diagrams - Site Floor Plans Site Equipment Rack Configurations ATP Test Checklists - Functional Acceptance Test Plan Test Sheets and Results — Equipment Inventory List Console Programming Template Drawings are created utilizing AutoCAD 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. Customer Responsibilities: • Receive and approve all documentation provided by Motorola. Completion Criteria: • All required documentation is provided and approved by Weld County. 4.12.5 Final Acceptance (Milestone) • All deliverables completed, as contractually required. • Final System Acceptance received from Weld County. 4.13 PROJECT ADMINISTRATION 4.13.1 Project Status Meetings Motorola Responsibilities: • Motorola Project Manager, or designee, will attend all project status meetings with the Agencies, 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 concerns of either the Agencies or Motorola. Customer Responsibilities: • Attend meetings. • Respond to issues in a timely manner. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Statement of Work 4-15 Completion Criteria: • Completion of the meetings and submission of meeting minutes. 4.13.2 Progress Milestone Submittal Motorola Responsibilities: • Submit progress (non-payment) milestone completion certificate/doctimentation. Customer Responsibilities: • Approve milestone, which will signify confirmation of completion of the work associated with the scheduled task. Completion Criteria: • Weld County approval of the Milestone Completion doctunent(s). 4.13.3 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. Example - Change Order Form Microsoft Office Word 97 - 2003 Docu Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Statement of Work 4-16 SECTION 5 PROJECT SCHEDULE Project Schedule is included on the pages that follow. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Project Schedule 5-1 CHEDULE N 8 3 2 0 0 0 Task External Milestone ♦ Duration -only Critical Split Split , „ „ „ „ „ „ „ , , , „ Inactive Task ° Manual Summary Rollup i Progress il Milestone ® Inactive Task ( I Manual Summary Willi, Deadline Summary iffjl Inactive Milestone Start -only C Project Summary Inactive Summary V V Finish-onty 7 External Tasks Manual Task ` ,J Critical ?1 Program Manager: Neil Clatworthy Page 1 of 5 Tel: 303 9567529 i Q Q `° m O 3 2 M,Weld County M,Weld County m 75 a ca O a Motorola O O m t 15 �... 3 o c u O o IeMotora . 2 '1 i oo 0 o 0 o 0 0., JH4 O 00 O N 0 0 0 0 0 4. o co T 0 J 0 0 Q1 Qf M o o IA N T Resource Names 2 U Q2a co S Q be 2 U(� I I I ADCOM,Weld County ADCOM,Weld County co O O 2 m 2 ca O O 2 Motorola Motorola @ 2 m 0 0 2222222 m 0 0 m 0 0 CO 0 0 co 0 0 N co 0 0 N co 0 0 1 ^S V v 7FS-24d,5 W T r 13 N 24 N cV N AINN 88,72.80,79,81,82,8 3,84, 85 ADCOM / WELD PROPOSAL PROJ El Finish Predecessors 121d Tue 4/16/13 Tue 1011/13 10d Mon 5/6/13 Fri 5/17/13 Od Mon 5,6/13 Mon 5/6/13 10d Mon 5/6/13 Fri 5/17/13 3 Od Fri 5/17/13 Fri 5/17/134 Tue4/16/13 Tue4/16/13 4 V1 • Od Tue 4/16/1 3 Tue 4/18/137 Wed 4/17/13 Wed 4/24/13 Fn 4/19/13 8 I � Z % N r Tue 4/30/13 Tue 4/30/1815 r) T M T Wed 4/24/13 Tue 4/30/1313 pp N of T 10d Thu 5/16/13 Wed 529/13 22 28th Thu 5/16/13 Thu 6/20/13 23SS.22 5d' Fri 6/21/13 Thu 6/27/13 24.21 Od Thu 6/27/13 Thu 6/27/13 25 2d Fri 6/28/13 Mon 7/1/13 26 n N Tue 4/16/13 Tue 4/18/13 Od Tue 4/16/13 Tue 4/18/13 M T (h r Wed 4/17/13 Tue4130/15 Tue 4/30/13,, Wed 7/3/13 Wed 4/24/13 Wed 7/3/13 Wed 4(24113 Wed 5/15/13 £ l/S l/S PeM £ Ut7Z./t7 PIM M M N7 M T el T N Wed 5/1/13 Mon 613/13 Wed 4/17/13 M T M = V Wed 4117/13 Wed 4/24/13 O a I IA r IA in r r Task Name IComde e 1 Implementation Project - Phase 3 Executing Contract Contract Award Project Kick -Off Frequency Licensing Contract Design Review (Gate 9 & 8) Review Contract Design Design Approval (verbal) Issue Design Approval milestone document Order Processing (Gate 7 - Procurement & Build) Staged Equipment Process Staged Equipment list Staged Equipment Orders bridged in COF Non -Staged Equipment Process Non -Staged Equipment list Non -Staged Equipment Orders bridged in COF Manufacturing and Staging (Gate 7 -Procurement & Build) Staged Equipment Manufacture Motorola FNE Manufacture Non -Motorola Equipment Develop Programming Configurations Ship to Staging sucperedO apeaddrt Stage System Perform Staging ATP 0 U C a I I Ship Equipment to Field Receive and Inventory Equipment in Field Non -Staged Equipment Project ADCOM P25 - WELD CO -13Q Date: Tue 4/23/13 % t Fa p y O O SO & 2 g NN g g gg g g ggggggg g 0 r N CO if b 0 ti Co Of r. N 13 r 15 r r A 20 N N 23 24 I 25 N I 27 28 N CHEDULE Q •� 8 p� Q ® 'r 0 zi E COM Weld County Task External Milestone • Duration -only 4. Critical Split Split Inactive Task v Manual Summary Rollup a - . Progress ma Milestone • Inactive Task l ) Manual Summary Deadline Summary Vas. Inactive Milestone Start -only Project Summary IS. Inactive Summary V V Finish -only 7 External Tasks Manual Task F A Critical Program Manager: Neil Clatworthy Page 2 of 5 Tel: 303 9567529 U d }m 0 g ' 8 g . § §Ii O Q c8g t, T I o I i (Motorola 0 ft 2 C 2 $ 0 0 O O O Q\ O • it iiiOO IP q 2 G C O o O O O (Resource Names 10 z m Motorola Motorola Motorola I U ADCOM. Weld County Motorola Weld County ,ADCOM ADCOM.Weld County 2 0 888 Q 2 0 Q 2 0 Q 2 O Q ADCOM. Weld County i 1 ,, 33 72,81 ,82,83,84,85,88,80 Li LL o a 4 3 Y. ADCOM / WELD PROPOSAL PROJ El Finish Predecessors ID 5d Tue 5/28/13 Mon 6/3/13 31,30 Mon 6/3/13 32 Thu 6/20/13 72SS 2w LL U) 1 72S F -2w U) r _ A t r)r n 0d Thu 7/11/13 Thu 7/11/1377SS-2w Od Wed 7/24/13 Wed 724/1346FS+2w L Thu 7/11/13 Thu 7/11/1345 Thu 7/11/13 u h r r) !- ') r h aa a LL N) a r LL Stale Pala Mon 5/27/13 Mon 5/27/13 of r ai I Thu 5110113 Wed 9/4/13 Thu 6/20/13 Thu 6/20/13 lq 4 !9 A 8 5d Thu 5/16/13 Thu 5/23/13 Thu 6/20/13 Thu 6/27/13 Thu 6/27/13 Thu 6/27/13 Thu 7/11113 Wed 7/24/13 in n^ L C') l7 19d Wed 5/1/13 f7 co O Start st/lt/5 rn Cl a 4 l7 a 4 M a a = Mt_ or �; n Thu 6/27/13 Wed 7/3/13 el in N lo) 4 4 el 1 a 8 i I88 8 E 8 8o I' 8 8 88 l 8 8 8 8 Task Name Manufacture Motorola FNE (non -staged equipment) Manufacture Non -Motorola Equipment I Ship Equipment to Field Receive and Inventory Equipment in Field INSTALLATION (Gate 6 - Installation & Optimization) Customer Prerequisites Power and Connectivity All primary power, AC dreilts and outlets. UPS in place All connectivity between M3 Core and all RF and dispatch sites complete R66 -Audit and Upgrade Perform R-56 Audit Bring grounding system up to Motorola's R56 standards Ethernet and T1 links Required Ethernet and T1 links in place and tested Infrastructure for 4th Simulcast site Building in place Tower in place Antenna system in place Generator in place Hilltop temporary shelter and power Temporary shelter install completed Temporary power in place Database entry tor 7.13 M3 Core All database entry for ADCOM and Thornton into the proposed 7.13 M3 Core completed Templates and Programming Project ADCOM P25 - WELD CO -13Q Date: Tue 4/23/13 M 0 s 8 g g gg g ggg ggg gggggggggggg g f 31 �� 49 g 51 A t/ CHEDULE 8 _QQ f7i _ ADCOM,Weld County ,Weld County ,Weld County COM,Weld County c c 2 Id County Task External Milestone 0 Duration -only Critical Split Split . „ . . . . . . . . . . . . . . . . . Inactive Task Manual Summary Rollup Progress ip Milestone ® Inactive Task ( ) Manual Summary lis, Deadline Summary liPP40 Inactive Milestone Start -only C Project Summary „ Inactive Summary V V Finish -only 7 External Tasks Manual Task F A Critical Program Manager: Neil Clatworthy Page 3 of 5 Tel: 303 9567529 ?. -' W U U g (44 r -..1! —' 2 w U13 0 3 41 3 a o 0 o 0 ., o • • 4 — bi 2 t 0 0 0 O Resource Names ADCOM.Weld County ADCOM, Weld County ADCOM.Weld County ADCOM,Weld County ADCOM.Weld County L_ ADCOM,Weld County O 8 a Weld County g I 59SF-2w,58SF-2w ADCOM / WELD PROPOSAL PROJ El Finish Predecessors th co Fri 8!2!13 Fri 8/16/13 Fri 8/2/13 60SF-2w Fri 8/2/131808F -2W co FI 2 A ch • n Cl) CO 80SS-2w, 81 SS-2w,82S CI) Thu 6/20/13 Co) r r M I Thu 6/20/13 h r C') e� CO a r a aco a r u_ fl r C') e-„ C') M a0 Pi O M a f') O 3 a Thu 6/20/13 01 r C') co Fri 8116113 Fri 8/16/13 1 -_.CD /'7 C') 8 A 88 8 8 8 8 8 8 8 8 8 8 O JA 1 Task Name Upgrade Rados (If needed) Ensure Radios have Packet Data, RS232, POP25, Text Messaging, OTAR and encryption Radio Programming Radb programming templates produced Subscriber upgrades L completed (if needed) Programming of the new system into al mobiles, portables and control stations completed Configure existing conventional consde resources 4W Tone operation completed (no desksets are attached to any conventional resources) I I Structural analysis of existing tower and rooftops Structural analysis of existing tower and rooftops completed Local Area Network (LAN) (Thornton dispatch center) Local Area Network (LAN) at the Thornton dispatch center connected to the proposed upgraded VPM console positions VPM hardware for the MCC 7500 console upgrade VPM hardware for the MCC 7500 console upgrade avalable Project ADCOM P25 - WELD CO -13Q Date: Tue 4/23/13 W 0 �p Q T Q O O O O a 4 S S a N 59 3 CON to 3 Sm 2 CHEDULE \ J 2 / } // 2 k ]) o _ f a k s Motorola a 0 0 ■ a 2 0 ■ Motorola Motorola Motorola 2 e 0 ] 0 a LMotorola 0% Signed Installation Acceptance 1d Wed 9/4/13 Wed 9/4/1386,91 106 It 5" Task r777.7j External Milestone C Duration -only Critical Split Split Inactive Task Manual Summary Rollup r Progress il Milestone ♦ Inactive Task ( ) Manual Summary Deadline b Summary Ilpmmolp Inactive Milestone Start -only Project Summary V- V Inactive Summary V V Finish -only 7 External Tasks • Manual Task F ,J Critical Program Manager: Neil Clatworthy Page 4 of 5 Tel: 303 9567529 2■ C. ' r . . ..-:�- V N . ^ _ . 3 6 } z\4 $ €4 —1 0 &^ \K / K \ 6 \ F & - 21 Resource Names Weld County 86,95,77,74,76,75,73,38SS-... Motorola \ o 2 79 Motorola 2« o 22 4 ■ �F co o 78,79,45SS-2w,46SS-2w Motorola co 79 0 2 p 90,84FS+5d,96,86,89,85FS+... Motorola 86,68SS-2w,70SS-2w Motorola co # 0 2 ■ 2 $ $ $ S 86,68SS-2w,70SS-2w Motorola 86,68SS-2w,70SS-2w Motorola com p 0 I , % " $ $ $ m 86 Motorola 93 Motorola $ 15 22 4 24 et �a ■■ 1 15 p 0 II ■@ 2 m 0 9 0 ■ § I ADCOM / WELD PROPOSAL PROJ El Finish Predecessors .$ 2 A $ } 15d Thu 7/4/13 Wed 7/24/13 28,33 R % p / 72 Mon 8/19/13 77 Tue 9/311 328,79FS+54.33 Tue 913/1I79FS+5d,28,33 Tue 9/3/1379FS+5d.28,33 N \ § is - F 3d Fri 8/30/13 Tue 9/3/1 3 79FS+5d,28,33 Tue 9/3/13 79FS+5d,28,33 Od Tue 9/3/13 Tue 9/3/1384,72,85,83,79,80,82.8 Thu 7/4/13 Thu 8/29/13 10d Thu 7/4/13 Wed 7/11/13 28,33 Tue 8/27/1379 5d Fri 8/23/13 Thu 8/29/13 79 2 t k © I ces_Q 7 2 § I 2 § 12d Thu 7/25/13 Fri 8/9/13 in § Wed 8/14/13 2 j / .- B 4 Wed 9/4/13 Wed 914/13 n § C -O". I } _ a n _§ § 2 _ 7 ■ 12d Thu 7/25/13 Thu 7/25/13 r $ / 15d Thu 7/25/13 3d Thu 8/15/13 n / f 2 Od Thu 8/29/13 3d Fri 8/30/13 3d Fri 8/30/13 3d Fri 8/30/13 3d Fri 8/30/13 Duration 3 2 § § "4 Task Name 2nd LAN connection to each operator position and AIS server for the upgrade 2nd LAN connection to each operator position and AIS server for the upgrade from GPIOM to VPM available Install and Upgrade FNE Equipment Install FNE Master Site Install FNE Civic Center Prime Site Install FNE Civic Center Remote Site Install FNE Wllbp Remote Site Install FNE Water Tank Remote Site Install FNE 4th Site Remote Site Instal FNE Hoyt Remote Site Upgrade ADCOM Simulcast Cell Upgrade Weld Cty Grover Site Upgrade Weld Cty New Raymer Site Upgrade Wekl Cty SE Vlieki Sib Upgrade Weld Cty 7H Area Site Upgrade Weld Cty Nunn Site Upgrade Weld Cty Simulcast Cell I 3 / _ To Tri Z Console Installation (Gab 6 - Installation & Optimization) Instal ADCOM MCC Console Upgrade Thornton MCC Console Upgrade Weld MCC Console Console Installations Complels Installation Acceptance Project ADCOM P25 - WELD CO -13Q Date: Tue 4/23/13 0 #\ g g g g g K K g K K K g g K K K K gg gg gg gg 9 8 7 r. 2 73 74 N I 76 79 @ ■ g 2 $ 2 @ 87 2 @ 8 ■ 22 CHEDULE 8 — o co il IADCOM,Weld Counts U Is 3a 2 o 8 0 rola,ADCOM,W 00 co a 1DCOM and Well ` 2" O Motorola C 0% ADCOM,Weti Task External Milestone 0 Duration -only Critical Split Split . „ . . . . . . . . . . . . . . . „ Inactive Task Manual Summary Rollup Progress ip Milestone ® Inactive Task ( ) Manual Summary lis, Deadline Summary lifiFQ Inactive Milestone Start -only C Project Summary „ Inactive Summary V V Finish -only 7 External Tasks Manual Task F A Critical Program Manager: Neil Clatworthy Page 5 of 5 Tel: 303 9567529 as 0- 0 c� 0 0 c4o— 4 -f -4t e ` b o g43 St g o _ F eh N 4 — q 2 [` g .r 7 O g g 9 0 O e c 0 Resource Names OD O OD o al O ADCOM.Weld County tik 0 0 a TIJ O ADCOM,Weld County (13 T2 Motorola.ADCOM. Weld County al O CO O 0 ADCOM and Weld County IADCOM,Weld County Thu 7/25/13 Fri 82/1372 96 Fri 8/23/13 Thu 8/29/1379,47,95 97 0 88 r j 104,53SS-2w,60S S -2w e- 4 12 Sr r S8 r r r re 0 r 1-rr r r r ADCOM / WELD PROPOSAL PROJ El Thu 8129113, Thu 8/29/13 Thu 8/29/1398 Mon 5/6/13 Mon 9/23/13 Mon 5/6/13 Fri 5/17/13 3 32d1 Tue 7/23/13 Wed 9/4/13 3,99 5d Tue 9/17/13 Mon 9/23/13106 Tue 9/3/13 97 Tue 9/3/13 Tue 9/3/13103 8c1 Thu 9/5/13 Mon 9/16/13 93,104,100.48 Od Mon 9/16/13 Mon 9/16/13 106 Mon 9/16/13107 10d Tue 9/17/13 Mon 9/30/13 109 Mon 9/23/13109 Tue 10/1113111,110 Es O cV c+) S a r Finish Predecessors Mon 9/16/13 eh c� a C re r .—C a • eh a M L LA- Fri 8/30/13 .- 2 Thu 7/25113 11d Mon 9/16113 Od Mon 9/16/13 Sd Tue 9/17/13 a 55 S r a S ces 0 Duration N r A N 1 N 8 a Task Name System Optimization (Oats 6 - Installation & Optimization) Link Verification Optimize System FNE-ADCOM Simulcast Optimization Complete Training (Gate 5 - System Testing & Cutover) On -Line Training Perform Applicable Pre-Cutover Training Perform Applicable Post-Cutover Training Audit and Acceptance Testing (Gate 5 -System Testing & Cutover) IPerform System Testing SATP Acceptance Cutover (Gate 5 - System Testing & Cutover Cutover Complete Finalize (Gate 4 - Implementation Clow) I . gi I H C -o C itl Transition to Servios/PTC Final Acceptance Project ADCOM P25 - WELD CO -13Q Date: Tue 4/23/13 O sag gg gg gg gg gg g ggg g gggg Q a SS 68 S 8 6 S 8 I 104 8 8 O 8 3 0 r N � SECTION 6 ACCEPTANCE TEST PLAN 6.1 ACCEPTANCE TEST PROCEDURES During acceptance testing, Motorola will demonstrate the end -to -end functionality and performance of the ASTRO 25 7.13 system. At the conclusion of this acceptance testing, full documentation of the executed tests, test results, and signed acceptance certificates will be provided as components of the System Manual. 6.1.1 General Performance Criteria Acceptance Testing will be performed during the implementation phase and will consist of system functional testing. The Acceptance Tests will provide a means to ensure that the system is performing as designed before integrating users into the system. The Final System Functional Test will be performed upon the completion of the implementation. Tests are described below, and sample test scripts are provided, as applicable, in Section 21.2 of the response. In addition to the acceptance test types listed above, Motorola's standard approach to system testing for large projects includes installation quality audits after the system has been installed in the field. 6.1.2 System Functionality Tests The system ftmctional tests verify that each subsystem delivers the features and functions as defined in the ADCOM and Weld County contracts. These tests mainly represent user operations on the voice subsystem, and will be performed as part of the final system acceptance testing. The major subsystems will be tested utilizing test scripts to demonstrate their functionality as part of the Radio System. In addition, the system redundancy and reliability will be verified to ensure that the system users will have continuous communication. These tests will be performed prior to beneficial use of the system. Sample test scripts are provided below. The test scripts will be reviewed during the Detailed Design Process. Typical Voice Subsystem Tests The following are examples of Motorola's standard voice subsystem tests. Examples of tests to be conducted are: • Full Registration. • Group Voice Call. • Private Call. • Affiliation. • Announcement Group Call. • Emergency Alarm. • Emergency Group Call. • Emergency Unit -To -Unit Call. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Acceptance Test Plan 6-1 • Busy Queue. Dispatch Subsystem Tests The following are examples of Motorola's standard Dispatch functionality tests for the MCC 7500 Console Subsystem. • Console Priority. • Group Voice Call. • Multi -Select Operation. • Patch Operation. • Unit ID/Alias Display. • Emergency Alarm and Call. • Audio Logging. System Administration and Fault Management Subsystem Tests The following are examples of Motorola's System Administration Subsystem Tests. • Configuration Management. • Report Generation. • Radio Control Manager. • Link and Equipment Failures reported to Fault Management. • Diagnostics. System Reliability and Availability Tests System Reliability tests will confirm the redundancy of major system components, and the fallback modes of the system. This section describes each of these types of tests. The critical system components of the proposed design are built in a redundant configuration to minimize negative impact on user operations should one of these components fail. Redundancy tests will be conducted for the following: ASTRO 25 Master Site Components • Zone controllers. • Ethernet LAN switches. • Core routers. • System management servers. Trunked Simulcast Remote or Standalone Site Components • Control channels (base station). • Voice channel (base station). • Site controllers. • Site routers. Motorola's proposed system is also equipped with several fallback modes to ensure field users can still communicate in the event of multiple major failures on the system. Fallback modes • Site Tnmking. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Acceptance Test Plan 6-2 6.2 SAMPLE TEST SCRIPTS Wide Area Trunking - FDMA Only Sites Talkgroup Call 1. DESCRIPTION The Talkgroup is the primary level of organization for communications on a trunked radio system. Radios with Talkgroup call capability will be able to communicate with other members of the same Talkgroup. This provides the effect of a private channel down to the Talkgroup level. This test will demonstrate that a Talkgroup transmission initiated by a radio user will only be heard by system users, which have, the same Talkgroup selected. As with other types of calls. Talkgroup calls can take place from anywhere in the system. SETUP RADIO -1 - SITE 1 - TALKGROUP 1 RADIO -2 - SITE 2 - TALKGROUP 1 RADIO -3 - SITE 1 - TALKGROUP 2 RADIO -4 - SITE 2 - TALKGROUP 2 VERSION #1.040 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Step 4. Initiate a Wide Area Call with RADIO -1 in TALKGROUP 1. Observe that only RADIO -2 will be able to monitor and respond to the call. Initiate a Wide Area Call with RADIO -3 in TALKGROUP 2. Observe that only RADIO -4 will be able to monitor and respond the call. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-1 Wide Area Trunking - FDMA Only Sites Continuous Assignment Updating 1. DESCRIPTION When a talkgroup is assigned a voice channel, the site controller continues to transmit the channel assignment on the control channel for the duration of the talkgroup call. Radios coming into use on the system are automatically sent to voice channels with conversations in progress involving their selected talkgroups. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 RADIO -3 - TALKGROUP 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Turn OFF RADIO -1. Initiate a Talkgroup Call using RADIO -2 and verify RADIO -3 hears the audio. While the Talkgroup Call is in progress, turn ON RADIO -1. Step 4. Observe RADIO -1, which was just brought back into service, joins the Talkgroup Call already in progress. Step 5. End the talkgroup call. Step 6. Switch RADIO -1 to another talkgroup. Step 7. Initiate a Talkgroup Call from RADIO -2 to RADIO -3. Step 8. While the Talkgroup Call is in progress, set RADIO -1 back to TALKGROUP 1. Step 9. Observe that RADIO -1 joins the Talkgroup Call already in progress. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-2 Wide Area Trunking - FDMA Only Sites Multigroup Call in Wait Mode 1. DESCRIPTION This trunking feature allows an equipped radio user to transmit an announcement to several different talkgroups simultaneously. The multigroup (ATG) call can be flagged for Wait Mode in the Provisioning Manager (PM) database forcing all attached talkgroups to finish calls in progress before the trunked system will process the multigroup call. The system does not permit inactive, attached talkgroups to initiate Talkgroup Calls during the "wait" timeframe. As with other types of calls, multigroup calls can take place from anywhere in the system. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 RADIO -3 - RANDOM (Not part of MG) RADIO -4 - ATG 1 * TALKGROUP 1 and TALKGROUP 2 are members of ATG 1. * RANDOM is any talkgroup not a member of ATG 1. * Multigroups are set up through both the Provisioning Manager (PM) and the Subscriber Programming software. VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Step 4. Step 5. Verify ATG 1 is set for the Wait mode. Using RADIO -1, initiate a call on TALKGROUP 1. While RADIO -1 is keyed, attempt to initiate a multigroup call using RADIO -4 on ATG 1. Verify RADIO -4 receives a busy tone because one of the talkgroups attached to ATG 1 is involved in a Talkgroup Call. Key RADIO -2 and verify that a busy tone is received because the ATG 1 call is in queue. Dekey RADIO -1 and verify RADIO -4 receives a callback. Step 6. Key RADIO -4 and verify both RADIO -1 and RADIO -2 hear the multigroup call while RADIO -3 does not unmute. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-3 Wide Area Trunking - FDMA Only Sites Call Alert 1. DESCRIPTION Call Alert is a tone page that allows a user to selectively alert another radio unit. The initiating radio will receive notification from the trunked system as to whether or not the page was received by the target radio. Units receiving a Call Alert will sound an alert tone. As with other types of calls, Call Alerts can take place from anywhere in the system. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 RADIO -3 - TALKGROUP 3 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Step 4. Step 5. Step 6. Step 7. Step 8. Using RADIO -1, press the page button. Enter the unit ID of RADIO -2 with the keypad, or scroll to the location where this ID is stored Press the PTT to initiate the call alert. Verify that the RADIO -1 user receives audible indication that the Call Alert was sent. Verify that RADIO -2 user receives an audible indication of an incoming Call Alert was sent but RADIO -3 does not. Verify RADIO -1 gets an audible indication that the Call Alert was successfully received at the target radio. Turn off RADIO -2. Send a Call Alert from RADIO -1 to RADIO -2. Verify that the RADIO -1 user receives audible indication that the Call Alert was sent. Verify RADIO -1 receives a "No Acknowledgement" indication that the Call Alert was not received at the target radio. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-4 Wide Area Trunking - FDMA Only Sites Private Call 1. DESCRIPTION Private Call is a selective calling feature that allows a radio user to carry on one-to-one conversation that is only heard by the 2 parties involved. Subscriber units receiving a private call will sound an alert tone. As with other types of calls, Private Calls can take place from anywhere in the system. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 RADIO -3 - TALKGROUP 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Using RADIO -1, press the Private Call (Call) button. Step 2. Enter the unit ID of RADIO -2 with the keypad, or scroll to the location where this ID is stored. Step 3. Press the PTT to initiate the Private Call. Step 4. Step 5. Step 6. Step 7. Verify that RADIO -2 hears tones and the display indicates that a Private Call has been received, but RADIO -3 receives no indications. Answer the call at RADIO -2 by pressing the Private Call (Call) button. If RADIO -2 has a display, verify it shows the ID number or Alias of the calling unit. Press the PTT switch on RADIO -2 and respond to the Private Call. Note that if you do not press the Private Call button before pressing PTT, your audio will be heard by all members of the talkgroup, and not just by the radio initiating the Private Call. Verify that RADIO -2 can communicate with RADIO -1. Step 8. Verify that RADIO -3 does not monitor the Private Call. Step 9. End the Private Call by pressing the "home" key and return to normal talkgroup operation. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-5 Wide Area Trunking - FDMA Only Sites Audio Interrupt / Interrupt Never Mode 1. DESCRIPTION A radio PTT request may be received for a group already active and currently being sourced by another radio unit. The talkgroup can be flagged to either allow or disallow the new PTT. If allowed, the latest PTT request will be granted and become the source of the call. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 RADIO -3 - TALKGROUP 1 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Verify TALKGROUP l's template is set up as Audio Interrupt Never. Step 2. Using RADIO -1, initiate a call on TALKGROUP 1. Step 3. Verify both RADIO -2 and RADIO -3 monitor the audio. Step 4. Using RADIO -3. initiate a call on TALKGROUP 1. Step 5. Verify that RADIO -3 receives a reject and that RADIO -2 continues to listen to RADIO - 1. Step 6. Dekey both Radios. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-6 Wide Area Trunking - FDMA Only Sites Emergency Alarm and Call with Top of Queue 1. DESCRIPTION Users in life threatening situations can use the Emergency button on the radio to immediately send a signal to the dispatcher and be assigned the next available voice channel. An Emergency Call can be set to either Top of Queue or Ruthless Preemption operation. During an emergency call the Emergency ID will appear on the display of the subscribers. To demonstrate this, an Emergency Alarm and Call will be initiated from a subscriber which will be received by a subscriber on the same talkgroup, affiliated at any site of any zone in the system. NOTE: If the subscriber does not have the Display option, the Emergency ID will not be displayed. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - Any Site RADIO -3 - TALKGROUP 2 RADIO -3 - SITE - SITE 1 RADIO -4 - TALKGROUP 3 RADIO -4 - SITE - SITE 1 All radios and talkgroups should start with default priorities. Default is 10. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Verify the emergency type for TALKGROUP l's template is set up as Top of Queue. Step 2. Simulate a busy system by disabling all channels at SITE 1 with the exception of the control channel and one voice channel. Step 3. Press the PTT to initiate a call with RADIO -3 and hold the PTT switch until instructed to release. Step 4. Key RADIO -4 and verify the radio receives a busy tone. Release the PTT switch on RADIO -4. Step 5. Using RADIO -1 send an Emergency Call by depressing the emergency switch and then the PTT switch. Step 6. Observe that RADIO -1 cannot transmit due to the voice channel being busy. Step 7. Release the PTT switch on RADIO -3. Step 8. Step 9. Observe that RADIO -1 receives the call back before RADIO -4 and is able to proceed with the call. Also observe that the display on RADIO -2 denotes an emergency and the unit ID or alias of RADIO -1. Dekey RADIO -1 and end the Emergency Call by holding down the Emergency button on RADIO -1 until an alert tone sounds. Verify RADIO -1 returns to normal operation and that RADIO -4 receives a callback. Step 10. Return the system to normal operation by enabling all the channels at SITE 1. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-7 Wide Area Trunking - FDMA Only Sites Busy Queuing and Callback with Ten Talkgroup Priority Levels 1. DESCRIPTION If no voice channel resources are available, radios requesting channels for new conversations are placed in a queue. Users of the same priority will move through the queue in a FIFO (first in, first out) sequence: however, users of higher priority will be inserted ahead of lower priority users in queue. When a voice channel becomes available, the radio at the top of the busy queue gets a channel assignment and generates a callback tone. The callback tone alerts the user that a channel assignment was made and transmitting is now possible on the selected talkgroup. An Emergency Call has the highest priority at level 1. The highest assignable priority is 2 and 10 is the lowest. NOTE: All radios and talkgroups should start with default priorities. Default is 10. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 6 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 3 RADIO -3 - SITE - SITE 1 RADIO -4 - TALKGROUP 6 RADIO -4 - SITE - Any Site VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Simulate a busy system by disabling all channels at SITE 1 with the exception of the control channel and one voice channel. Step 2. Verify the priority level for TALKGROUP 6's template as priority 9. Step 3. Initiate a Talkgroup Call with RADIO -1. Keep this call in progress until instructed to end the call. Step 4. Key RADIO -3 and observe that the radio receives a busy. Step 5. Key RADIO -2 and observe that the radio receives a busy. Step 6. End the Talkgroup Call established in Step 3. Step 7. Observe RADIO -2 receives the first callback and can now make a call to RADIO -4 upon receipt of the callback indication. Step 8. End the call between RADIO -2 and RADIO - 4. Step 9. Observe RADIO -3 now receives a callback and can make a call upon receipt of the callback indication. Step 10. Return all the channels in the system to service. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-8 Site Trunking - FDMA Only Sites Site Trunking Indication 1. DESCRIPTION When a remote site loses its link or does not have a link to the Zone Controller, the affected site will enter "Site Trunking" mode of operation. Radios locked onto this site will be serviced locally within this site's coverage area. NOTE: If the subscriber does not have the Display option, the "Site Trunking" indication will not be displayed. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 2 RADIO -2 - SITE - SITE 1 Lock the subscribers to SITE 1 if more than one site exists on the system. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Place SITE 1 into the Site Trunking mode. Verify that RADIO -1 and RADIO -2 are displaying the "Site Trunking" indication. Return the site to Wide Area Trunking unless the next test requires Site Trunking. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-9 Site Trunking - FDMA Only Sites Talkgroup Call 1. DESCRIPTION When a site goes into Site Trunking, radios with Talkgroup Call capability will be able to communicate with other members of the same talkgroup at that same site. Members of the same talkgroup at other sites will not be able to monitor those conversations. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 1 RADIO -3 - SITE - SITE 2 RADIO -4 - TALKGROUP 1 RADIO -4 - SITE - SITE 2 Note: All Radios should be "Site Locked" VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Place SITE 1 into the Site Trunking mode. Initiate a Talkgroup Call with RADIO -1 on TALKGROUP 1 at SITE 1. Observe that only RADIO -2 will be able to monitor and respond to the call. Note that RADIO -3 and RADIO -4 are not able this monitor the call since the site is not in wide area operation. Step 4. Initiate a Talkgroup Call with RADIO -3 on TALKGROUP 1 at SITE 2. Step 5. Observe that only RADIO -4 will be able to monitor and respond to the call. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-10 Site Trunking - FDMA Only Sites Call Alert 1. DESCRIPTION Call Alert is a tone page that allows a user to selectively alert another radio unit. When a site is in Site Trunking, Radios at the site will only be able to Call Alert other radios at the same site. The initiating radio will receive notification from the trunked system as to whether or not the page was received by the target radio. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 2 RADIO -2 - SITE - SITE 1 Note: All Radios should be "Site Locked" VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Place SITE 1 into the Site Trunking mode. Using RADIO -1, press the page button. Enter the Unit ID of RADIO -2 with the keypad, or scroll to the location where this ID is stored. Step 4. Press the PTT to initiate the Call Alert. Step 5. Verify that RADIO -2 received the Call Alert. Step 6. Exit the Call Alert mode and return to normal talkgroup mode. Step 7. Return the site to Wide Area Trunking unless the next test requires Site Trunking. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-11 Site Trunking - FDMA Only Sites Private Call 1. DESCRIPTION Private Call is a selective calling feature that allows a dispatcher or radio user to carry on one-to-one conversation that is only heard by the 2 parties involved. When a site is in Site Trunking, Radios at the site will only be able to Private Call other radios at the same site. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 1 RADIO -3 - SITE - SITE 1 Note: All Radios should be "Site Locked" VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Place SITE 1 into the Site Trunking mode. Step 2. Using RADIO -1, press the Private Call button. Step 3. Enter the Unit ID of RADIO -2 with the keypad, or scroll to the location where this ID is stored. Step 4. Press the PTT to initiate the call. Step 5. Verify that at RADIO -2 only tones are heard and the display indicates that a call has been received. Step 6. Answer the call at RADIO -2 by pressing the Private Call button. Verify its display shows the ID number or alias of the calling unit. Step 7. Press the PTT switch on RADIO -2 and respond to the call. Note that if you do not press the Private Call button before pressing PTT, your audio will be heard by all members of the talkgroup, and not by the radio initiating the Private Call. Step 8. Verify only RADIO -1 hears the audio from RADIO -2. Step 9. End the Private Call. Return the site to Wide Area Trunking unless the next test requires Site Trunking. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-12 Site Trunking - FDMA Only Sites Continuous Assignment Updating 1. DESCRIPTION When a talkgroup is assigned a voice channel, the site controller continues to transmit the channel assignment on the control channel for the duration of the Talkgroup Call. Radios coming into use on the system are automatically sent to voice channels with conversations in progress involving their selected talkgroups. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 1 RADIO -3 - SITE - SITE 1 Note: All Radios should be "Site Locked" VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Place SITE 1 into the Site Trunking mode. Turn OFF RADIO -1. Initiate a Talkgroup Call using RADIO -2. Step 4. While the Talkgroup Call is in progress, turn on RADIO -1. Step 5. Observe that RADIO -1, which was just brought back into service, joins the Talkgroup Call already in progress. Step 6. Release the PTT of RADIO -2. Switch RADIO -1 to TALKGROUP 2. Step 7. Initiate a Talkgroup Call using RADIO -2. Step 8. While the Talkgroup Call is in progress, turn RADIO -1 back to TALKGROUP 1. Step 9. Observe that RADIO -1, which was just set back to TALKGROUP 1, joins the Talkgroup Call already in progress. Step 10. Return the site to Wide Area Trunking unless the next test requires Site Trunking. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-13 Site Trunking - FDMA Only Sites Busy Queuing and Callback 1. DESCRIPTION If no voice channel resources are available, radios requesting channels for new conversations are placed in the busy queue. Users of the same priority will move through the queue in a FIFO (first in, first out) sequence: however, users of higher priority will be inserted ahead of lower priority users in the queue. When a voice channel becomes available, the radio at the top of the busy queue gets a channel assignment and generates a callback tone. The callback alerts the user that a channel assignment was made and transmitting is now possible on the selected talkgroup. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 2 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 3 RADIO -3 - SITE - SITE 1 RADIO -4 - TALKGROUP 1 RADIO -4 - SITE - SITE 1 Note: All radios are "Site Locked." VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Simulate a busy system by disabling all channels at SITE 1 with the exception of the control channel and one voice channel. Initiate a Talkgroup Call with RADIO -1 and observe that RADIO -4 receives the call. Keep this call in progress until instructed to end the call. Step 3. Key RADIO -2 and observe that the radio receives a busy. Step 4. Key RADIO -3 and observe that the radio receives a busy. Step 5. End the Talkgroup Call established in Step 2. Step 6. Observe that RADIO -2 receives a callback prior to RADIO -3 receiving a callback. Step 7. Return the site to Wide Area Trunking unless the next test requires Site Trunking Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-14 Site Trunking - FDMA Only Sites Emergency Call and Alarm 1. DESCRIPTION Emergency Alarms and Calls can be initiated by subscribers when the registered site is in Site Trunking. With all subscribers registered on a Site Trunking site, a subscriber will initiate an Emergency Alarm by pressing the Emergency button. By pressing the PTT, an Emergency Call will be issued and the ID of the initiator will be displayed with an Emergency indication by the other subscribers on the same talkgroup. Note that for site trunking, Emergency Call operation is always Top of Queue. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 2 RADIO -3 - SITE - SITE 1 RADIO -4 - TALKGROUP 3 RADIO -4 - SITE - SITE 1 Note: All Radios should be "Site Locked" VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Place SITE 1 into the Site Trunking mode. Simulate a busy system by disabling all channels at SITE 1 with the exception of the control channel and one voice channel. Step 3. Press the PTT on RADIO -3 and hold the PTT switch until instructed to release. Step 4. Step 5. Step 6. Step 7. Step 8. Step 9. Step 10. Key RADIO -4 and observe that the radio receives a busy. Using RADIO -1, initiate an emergency alarm followed by an emergency call. Observe that RADIO -1 cannot transmit due to the voice channel being busy. Release the PTT switch on RADIO -3. Observe that RADIO -1 can now proceed with the call and RADIO -2 receives the call. Also observe that the display on RADIO -2 denotes an emergency and the ID or Alias of the unit sending the emergency. End the emergency call and verify that RADIO -4 gets a callback. Restore all channels to service and return the site to Wide Area Trunking unless the next test requires Site Trunking. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-15 MCC 7100/7500 Trunked Resources 2. TEST PTT Unit ID/Alias Display 1. DESCRIPTION Console operator positions contain various resources such as talkgroup, multigroup, Private Call which enables the dispatcher to communicate with the subscriber units. If activity occurs on one of these operator position resources, the unit ID or associated alias of the initiating radio appears at the console resource. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 CONSOLE -2 - TALKGROUP 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Select the resource for TALKGROUP 1 on CONSOLE -1. Step 2. Step 3. Initiate a call on TALKGROUP 1 from RADIO -2 and observe that the alias is seen at CONSOLE -1 in the resource window as well as in the Activity Log window. Initiate a call from RADIO -1 and observe that the alias of RADIO -1 is seen at CONSOLE -1 in the resource window as well as in the Activity Log window. Step 4. Modify RADIO -2's alias. Make sure to give enough time for the alias change to propagate to the Zone Controller. Step 5. Initiate a call from RADIO -2 and observe the new alias of RADIO -2 is seen at CONSOLE - 1 in the list in the resource window as well as in the Activity Log window. Step 6. Return RADIO -2's alias to its original state. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-16 MCC 7100/7500 Trunked Resources Instant Transmit 1. DESCRIPTION The instant transmit switch provides immediate operator access to a channel, independent of its select status (selected or unselected). It provides priority over other dispatcher transmit bars or optional footswitches. SETUP RADIO -1 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 (Selected), TALKGROUP 2 (Unselect mode) VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Using CONSOLE -1, press the Instant Transmit button on TALKGROUP 1. Step 2. Verify that the Transmit indicator is lit. Step 3. Verify RADIO -1 can monitor and respond to the call on TALKGROUP 1. Step 4. On RADIO -1 change to TALKGROUP 2. Step 5. Step 6. Using CONSOLE -1, press the Instant Transmit button on the TALKGROUP 2 radio resource. Verify RADIO -1 can monitor and respond to the call on TALKGROUP 2. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-17 MCC 7100/7500 Trunked Resources 2. TEST Talkgroup Selection and Call 1. DESCRIPTION The Talkgroup Call is the primary level of organization for communications on a trunked radio system. Dispatchers with Talkgroup Call capability will be able to communicate with other members of the same talkgroup. This provides the effect of an assigned channel down to the talkgroup level. When a Talkgroup Call is initiated from a subscriber unit, the call is indicated on each dispatch operator position that has a channel control resource associated with the unit's channel/talkgroup. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 RADIO -3 - TALKGROUP 1 RADIO -4 - TALKGROUP 2 CONSOLE -1 - TALKGROUP 1 CONSOLE -2 - TALKGROUP 2 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a wide area call from CONSOLE -1 on TALKGROUP 1. Step 2. Observe that RADIO -1 and RADIO -3 will be able to monitor the call. Dekey the console and have either radio respond to the call. Step 3. Observe that all consoles with TALKGROUP 1 can monitor both sides of the conversation. Step 4. Initiate a wide area call from CONSOLE -2 on TALKGROUP 2. Step 5. Observe that RADIO -2 and RADIO -4 will be able to monitor the call. Dekey the console and have either radio respond to the call. Step 6. Observe that all consoles with TALKGROUP 2 can monitor both sides of the conversation. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-18 MCC 7100/7500 Trunked Resources Emergency Alarm and Call Display Description 1. DESCRIPTION Users in life threatening situations can use the emergency button on the radio to send an audible alarm and a visual alarm signal to a console operator in order to request immediate system access to a voice channel for an emergency call. An emergency alarm begins after the radio user presses the radio's emergency button. Pressing the emergency button places the radio in "emergency mode". To begin an emergency call, the radio user must press the radio's PTT button while in "emergency mode." The assigned voice channel will be dedicated to the emergency caller's talkgroup for an extended period of time, equal to the Message Hang Time plus the Emergency Hang Time. As with other call types, emergency calls can operate across sites as well as within the same site. SETUP RADIO -1 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 CONSOLE -2 - TALKGROUP 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Step 4. Step 5. Initiate an Emergency Alarm from RADIO -1. Observe the Emergency from RADIO -1 is received at CONSOLE -1 for TALKGROUP 1. Acknowledge the Emergency at the operator position. Verify CONSOLE -2 receives notification that the call has been acknowledged. Initiate a call with RADIO -1 to initiate an Emergency call. Observe CONSOLE -1 and CONSOLE -2 can monitor RADIO -1 Step 6. Clear the Emergency from CONSOLE -1 on TALKGROUP 1. Step 7. End the Emergency Alarm from RADIO -1. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-19 MCC 7100/7500 Trunked Resources 2. TEST Multigroup Call 1. DESCRIPTION This trunking feature allows an equipped console operator position to transmit an announcement to several different talkgroups simultaneously. As with Talkgroup Calls, multigroup calls operate across sites as well as within the same site. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 RADIO -3 - RANDOM CONSOLE -1 - ATG 1 Note: TALKGROUP 1 and TALKGROUP 2 are members of ATG 1. RANDOM is any talkgroup not a member of ATG 1. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Using CONSOLE -1, select the ATG 1 resource. Step 2. Step 3. Step 4. Step 5. Step 6. Step 7. Initiate the Multigroup Call from CONSOLE - 1. Observe that RADIO -1 and RADIO -2 receive the Multigroup Call. Verify that RADIO -3 does not receive the Multigroup Call because it is not a member of ATG 1. Answer the Multigroup Call using RADIO -1 and observe CONSOLE -1 receives the response. Verify that if the call is answered within the repeater hang time, the console will receive the call on the ATG 1 resource tile, otherwise the console will receive the call on the TALKGROUP 1 tile. Verify that if the call is answered within the repeater hang time, RADIO -2 will monitor the call. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-20 MCC 7100/7500 Trunked Resources Multi -Select Operation 1. DESCRIPTION Multi -Select (Msel) allows the console operator to group a number of channels/talkgroups together such that when the general transmit bar is depressed, all of the multi -selected channels/talkgroups will transmit at the same time with the same information. Multi -Select is one way communication call. If a radio user responds to a Multi -Select call the talkgroup the user is affiliated to will be the only one to hear the call. There is no super -group formed, so radio communication is still at the single talkgroup level. Multi -Select is utilized to send an APB to several channels/talkgroups. A Multi -Select has a limit of twenty (20) trunking/conventional resources SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 CONSOLE -1 - TALKGROUP 1, TALKGROUP 2 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. From CONSOLE -1. create an Msel group with TALKGROUP 1 and TALKGROUP 2. Step 2. Step 3. Transmit on the Msel using the Msel instant transmit button. Verify that RADIO -1 and RADIO -2 hear the call. Step 4. Initiate a call with RADIO -1. Step 5. Verify the call is heard on CONSOLE -1 but not on RADIO -2. Step 6. Initiate a call with RADIO -2. Step 7. Verify the call is heard on CONSOLE -1 but not on RADIO -1. Step 8. On CONSOLE -1 dissolve the Msel. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-21 MCC 7100/7500 Trunked Resources 2. TEST Talkgroup Patch 1. DESCRIPTION Talkgroup Patch allows a dispatcher to merge several talkgroups together on one voice channel to participate in a single conversation. This can be used for situations involving two or more talkgroups that need to communicate with each other. Using the Patch feature, the console operator can talk and listen to all of the selected talkgroups grouped; in addition, the members of the individual talkgroups can also talk or listen to members of other talkgroups. Patched talkgroups can communicate with the console dispatcher and other members of different talkgroups because of the "supergroup" nature of the Patch feature. NOTE : If "secure" and "clear" resources are patched together, one repeater for each mode may be assigned per site. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 RADIO -3 - TALKGROUP 1 RADIO -4 - TALKGROUP 2 CONSOLE -1 - TALKGROUP 1 and TALKGROUP 2 Note: All 4 Radios must have the same home zone. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Using CONSOLE -1 create a patch between TALKGROUP 1 and TALKGROUP 2. Step 2. Initiate a patch call from CONSOLE -1. Step 3. Verify RADIO -1, RADIO -2, RADIO -3. and RADIO -4 can monitor the call. Step 4. Initiate several calls between the radios and verify successful communication. Step 5. Dissolve the patch created in step 1. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-22 MCC 7100/7500 Trunked Resources Alert Tones - Talkgroup 1. DESCRIPTION Pre -defined alert tones can be transmitted on the selected Radio Resource to subscribers which can alert members of a channel / talkgroup to a particular event or signify to radio users special instructions are to follow. The Console has the ability to send an Alert -Tone signal on selected conventional or talkgroup resources. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 VERSION #1.040 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Select TALKGROUP 1 on CONSOLE -1. Step 2. Select Alert Tone 1 and depress the Alert Tone button. Step 3. Verify that RADIO -1 and RADIO -2 hear Alert Tone 1. Step 4. Repeat Steps 2-3 for Alert Tone 2 and 3. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-23 MCC 7100/7500 Trunked Resources 2. TEST Call Alert 1. DESCRIPTION Call Alert Page allows a subscriber/dispatcher to selectively alert another radio unit. The initiating subscriber/console will receive notification as to whether or not the call alert was received. Units receiving a Call Alert will sound an alert tone and show a visual alert indication. The display will also show the individual ID of the initiating subscriber/console unit. SETUP RADIO -1 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Using CONSOLE -1, select the call alert button in the "Private Call" resource window. Step 2. Enter the ID of RADIO -1 and send the call alert to RADIO -1. Step 3. Verify that RADIO -1 receives the alert and that the ID of the console is shown. Step 4. Turn off RADIO -1. Step 5. Using CONSOLE -1, send the call alert to RADIO -1 again. Step 6. Verify that after trying to page RADIO -1, the console displays "Can not send call alert - target not found" in the summary/status list. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-24 MCC 7100/7500 Trunked Resources Console Initiated Private Call to Subscriber 1. DESCRIPTION Private Conversation is a selective calling feature which allows a dispatcher or radio user to carry on one-to-one conversation that is heard only by the two parties involved. Subscriber units receiving a private call will sound an alert tone. As with other call types, Private Calls operate across sites as well as within the same site. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Using CONSOLE -1, select the "PRIVATE - CALL" tile and click the Private Call function. Step 2. Select the unit to be Private Called, in this case RADIO -1. (or select the numeric keypad and enter the Unit ID to be Private Called.) Step 3. Click the Send button. Step 4. Answer the Private Call with RADIO -1 and respond to the console. Step 5. Verify RADIO -2 does not hear the private conversation. Step 6. After completing the Private Call, return to the normal talkgroup mode. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-25 MCC 7100/7500 Trunked Resources 2. TEST Console Priority 1. DESCRIPTION Console Operator Positions have ultimate control of transmitted audio on an assigned voice channel resource. The Console Position has the capability to take control of an assigned voice channel for a talkgroup call so that the operator's audio overrides any subscriber audio. Console priority is a feature that enables dispatchers to gain immediate access to an assigned voice channel so that a central point of audio control exists. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 CONSOLE -1 - TALKGROUP 1 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a Talkgroup call from RADIO -1 on TALKGROUP 1. Keep this call in progress until the test has completed. Step 2. Observe that RADIO -2 receives the call. Step 3. While the call is in progress, key up CONSOLE -1 on TALKGROUP 1. Step 4. Observe that RADIO -2 is now receiving audio from CONSOLE -1 on TALKGROUP 1. Step 5. De -key CONSOLE -1. Step 6. Verify RADIO -2 now receives RADIO -1 audio. Step 7. End the TALKGROUP 1 call from RADIO -1. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-26 MCC 7100/7500 Trunked Resources 2. TEST Activity Log 1. DESCRIPTION The Console activity log will show all traffic for the resource assigned to that console to include the time, radio alias, TG. PTT ID and Emergency Call. The dispatcher has the capability of selecting a logged call within in the "Activity Log Window" for instant transmit on the corresponding logged resource. This activity log can be logged to a text file for archival purposes. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 2 RADIO -3 - TALKGROUP 3 RADIO -4 - TALKGROUP 4 CONSOLE -1 - TALKGROUP 1, TALKGROUP 2, TALKGROUP 3, TALKGROUP 4 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. On CONSOLE -1 select the "Show Activity Log" button on the tool bar to open the Activity Log Window. Step 2. Initiate calls on RADIO -1. RADIO -2. RADIO - 3 and RADIO -4 to log call information and verify calls are displayed in the activity log window. Step 3. Step 4. Select a logged call in the Activity Log Window and verify that the Channel Control Window (CCW) at the top of the Activity log window changes to the corresponding resource. Verify the dispatcher is capable of responding via the instant transmit button. Open the text file created by the Activity Log and verify call traffic has been archived to the document file. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-27 Radio Control Manager (RCM) Features 2. TEST Radio Check 1. DESCRIPTION Radio Check is a Radio Control Manager (RCM) command used to verify that a radio is active in the trunking system. The Radio Check command causes the Zone Controller to poll for the radio requesting that the radio re -affiliate. When the radio re -affiliates, the RCM then has the knowledge that the radio is powered on and within system range. If the radio is involved in a conversation, whether group or interconnect, the RCM application displays a message to that effect. The information displayed by the RCM in response to the Radio Check command is: current talkgroup affiliation, the multigroup that the talkgroup is attached to (assuming the talkgroup belongs to a multigroup). and the site where the radio is affiliated. If the radio does not respond to the Radio Check command, a message to that effect displays. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Select the Command menu and then select the Radio Check item to open the Radio Check window. Step 2. Enter the ID or alias of RADIO -2 into the entry box and click the Apply button. Step 3. Observe the radio is polled and the current radio information is displayed on the RCM. Step 4. Turn off RADIO -1. Step 5. Enter the ID or alias of the RADIO -1 into the entry box and click the Apply button. Step 6. Observe that the RCM displays "Radio Not Found." Step 7. Depress and hold the PTT button of RADIO - 2 until instructed to release. Step 8. Enter the ID or alias of RADIO -2 into the entry box and click the Apply button. Observe that a busy for the radio is displayed on the RCM. Step 9. Release the PTT button on RADIO -2. Step 10. Observe the radio is polled and the current radio information is displayed on the RCM. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-28 Radio Control Manager (RCM) Features 2. TEST Radio Snapshot 1. DESCRIPTION Snapshot is a Radio Control Manager (RCM) command used to retrieve information about an individual radio. Information provided by the RCM application in response to the Snapshot command includes: the serial number of the radio, current talkgroup/multigroup and site affiliations; the Regroup, Inhibit, and Selector Lock state of the radio. Snapshot information is taken from the system databases. The Snapshot command does not initiate any communication with the target radio. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 RADIO -3 - TALKGROUP 2 RADIO -3 - SITE - SITE 3 * RADIO -1 and RADIO -3 must be programmed with Dynamic Regrouping capability. *Make sure Radio Users are configured with a "Radio Primary Talkgroup Assignment" in the UCM. VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Submit a Dynamic Regroup command for RADIO -1 and RADIO -3 to be regrouped to TALKGROUP 3. Step 2. At the RCM, initiate the Snapshot command for RADIO -1. Step 3. Verify that the RCM shows RADIO -1 affiliated to SITE 1 and that its current Regroup state is "Regroup." Step 4. At the RCM, revert the dynamic regrouping on RADIO -1 and RADIO -3. Step 5. Initiate the Snapshot command for RADIO - 1 Step 6. Verify RADIO -1 shows an affiliation to SITE 1 and that its current Regroup state is "Cancel Regroup." Step 7. At the RCM, inhibit RADIO -2 and then initiate the Snapshot command for RADIO -2. Step 8. Verify RADIO -2 shows an affiliation to SITE 2 and that its current Inhibit state is "Selective Inhibit." Step 9. At the RCM. revert RADIO -2 and then initiate the Snapshot command for RADIO -2. Step 10. Verify RADIO -2 shows an affiliation to SITE 2 and that its current Inhibit state is "Cancel Inhibit." Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-29 Radio Control Manager (RCM) Features 2. TEST Dynamic Regrouping 1. DESCRIPTION Dynamic Regrouping allows the Radio Control Manager (RCM) to assign individual radios operating in different talkgroups to a temporary talkgroup via the Regroup command. Network managers or supervisors can override individual radio talkgroup selections by steering regrouped subscribers to a new talkgroup containing users which need to communicate on a temporary basis. After receiving a Regroup command, a radio will ignore the current setting of the talkgroup selector and move to the target talkgroup specified in the Regroup command. Unless the supervisor issues a LOCK command. the radio user can deselect the target talkgroup by selecting another talkgroup using the radio selector. A unique location on the radio selector is reserved for the target talkgroup following a Regroup command. Dynamic Regrouping assignments can be initiated rapidly, but not instantaneously. Regrouping is best suited for planned activities or occasional changes from normal routines. It is not intended for immediate responses such as high speed chases or for a rapid deployment on a per incident basis. Regrouped radios receiving a second Regroup command will move to the new target talkgroup specified in the second command. When a regrouped radio receives a Regroup command, all information pertaining to the previous Regroup command is lost. A Cancel Regroup command or a Revert returns an individual radio to its normal operation. Note - RCM user must be attached to primary and target talkgroup. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 RADIO -3 - TALKGROUP 2 RADIO -3 - SITE - SITE 3 RADIO -4 - TALKGROUP 2 RADIO -4 - SITE - SITE 4 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. With the RCM open from the Commands menu item select the Radio Commands item to open the command window. Choose Regroup. Step 2. Enter TALKGROUP 3 in the target field. Step 3. Enter the IDs or aliases of RADIO -1, RADIO -2, RADIO -3 and RADIO -4. Step 4. Once all desired radio information is entered and appears in the command window click the Regroup button to initiate the command. Step 5. Observe all radios are regrouped and are able to communicate on TALKGROUP 3. Step 6. Step 7. Switch the Subscriber to the Dynamic Regroup channel to acknowledge the group request. Observe that the radios are able to select different talkgroups and are not locked onto the regrouped mode. Note- The Talkgroup selector knob has to be set to the dynamic regroup position before switching to any other talkgroup. Step 8. Observe that the Regroup task appears in the Command Monitor window. Step 9. Issue a Selector Lock command all four radios and verify their selectors have been locked. Step 10. Revert both commands and verify the radios have returned to normal operation. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-30 Radio Control Manager (RCM) Features 2. TEST Selective Radio Inhibit 1. DESCRIPTION The INHIBIT command issued by the Radio Control Manager (RCM) disables a radio, preventing it from transmitting or receiving any audio. All of the radio's functionality ceases while a radio is inhibited by the RCM. Once inhibited, the radio cannot be used to monitor voice channels or for any other radio user initiated activity. Note that an inhibited radio still monitors the control channel so that it can be re - enabled with the Cancel Inhibit command. Upon receiving the Cancel Inhibit command from the RCM, the radio returns to its normal operation. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. From the Radio Control Manager select the Commands menu and then select the Radio Commands item in the menu to open the Command Window. Step 2. Enter the IDs or aliases of RADIO -1. Step 3. Select "Selective Inhibit" from the command pull down menu. Step 4. Once all desired radio information is entered and appears in the command window click the submit button to initiate the command. Step 5. Observe RADIO -1 is inhibited and appears to be dead. Step 6. Observe that the Inhibit task appears in the Command Monitor window. Step 7. Cancel the Inhibit by selecting the task in the Command Monitor window and clicking the Revert button to submit the task. Step 8. Observe that the Cancel Inhibit task appears in the Command Monitor window and that RADIO -1 is returned to normal operation. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-31 Radio Control Manager (RCM) Features 2. TEST Emergency Alarm Display 1. DESCRIPTION The emergency call information that is displayed on the Radio Control Manager (RCM) includes the radio alias of the radio that initiated the Emergency Alarm. the talkgroup that the radio was affiliated to at the time the alarm was sent, and the time the alarm was received. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 One RCM which has TALKGROUP 1 attached is required. VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Open the Radio Control Manager (RCM) window(s) and verify that the Emergency Alarm window is visible. If it is not, go to the View menu and select it bringing it into the RCM viewable area. Step 2. Initiate an Emergency Alarm from RADIO -1. Step 3. Observe that the RCM receives the Emergency Alarm. Step 4. Step 5. Acknowledge the Emergency by selecting the Emergency in the window and clicking on the Respond button. Verify the window displays the radio alias, the talkgroup, and the time the alarm was received. Step 6. Again, select the displayed Emergency and click the Delete button to clear the emergency. Step 7. Reset the radio by holding the Emergency button until the radio clears. Step 8. Repeat Steps 1-7 using RADIO -2. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-32 Fault Management 2. TEST Unified Event Manager - Views 1. DESCRIPTION The Unified Event Manager (UEM) provides three different views. The purpose of this test is to demonstrate the views available from the UEM. SETUP NMclient01 - UEM session up and running. Step 1. The first view is the Active Alarms. In the navigation pane expand Fault Management and select Alarms. Step 2. Customize the Active Alarms display by selecting the Edit option from the menu bar, then select Search. Step 3. Perform a Managed Resource search for channels, site controllers and routers by entering "Starts with" and ch, sc, and z00 respectively in the search fields to perform the three separate searches. Step 4. For each of the three searches a filtered alarm view is displayed that contains alarms for the appropriate device in the search. VERSION #1.040 Step 5. Step 6. Step 7. The second view is the Physical Summary view. In the navigation pane, expand Zone Maps and select Physical Summary. The Physical Summary View provides an aggregated alarm severity status of the devices located at all subnets in the Zone. The third view is the Service Summary. In the navigation pane, under Zone Maps select Service Summary. The Service Summary View provides a quick summary of the service status of sites in a Zone. In the main UEM window is an Alarm Summary View pane. In the Alarm Summary View, select the format for the desired view, pie, tabular or bar. Pass Fail Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-33 Fault Management 2. TEST Station Power Amp Failure Reports to the Unified Event Manager (UEM) 1. DESCRIPTION This test will demonstrate that the Unified Event Manager (UEM) alarms view is able to capture information about various failures at the system and zone level. A station will be keyed while the output is unloaded to simulate a power amp failure. The failures will be monitored on the UEM. Note: For safety, either power down the station or TX Inhibit it before disconnecting or re -connecting the dummy load to prevent accidental keying of the station. Note: This test should be done on a site with more than 2 channels. Failsoft will occur if the test is done on a 2 channel site. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 2 RADIO -2 - SITE - SITE 1 NMclient01 - UEM session up and running. * All Radios should be "Site Locked" VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Verify that the power amp of the station to be tested has no active alarms against it. Step 2. Disconnect the dummy load/antenna from the station. Step 3. Make several talkgroup calls using RADIO -1 until the test station has been keyed. Step 4. Observe that an alarm indicating a Power Amp failure appears on the UEM alarms view. For SmartX sites you will need to look at event view to see cause of alarm. Step 5. Reconnect the dummy load/antenna disconnected in Step 3. Step 6. In approximately 5 minutes, observe the changes to the alarm on the UEM, indicating the module is restored to service. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-34 Fault Management 2. TEST Core Router Failure Reports to the Unified Event Manager 1. DESCRIPTION This test will demonstrate that the Unified Event Manager (UEM) alarms view is able to capture information about various failures at the system and zone level. A Core Router will be powered off to simulate a failure. The system health will be monitored on UEM. SETUP NMclient01 - UEM session up and running. VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Verify that the Core Router to be tested displays without failures (normal) on UEM. The core router is contained in the specific subnet that it is physically collocated with in the network. Step 2. Power down the Core Router. Step 3. Observe that an alarm indicating a Core Router failure appears on the UEM alarms view. Step 4. Restore power to the Core Router. Step 5. Observe the changes to the alarm in UEM. indicating the Core Router is Enabling. Step 6. Observe that alarm view updates in the UEM, indicating the Core Router has recovered and is Enabled. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-35 System Reliability Features 2. TEST Base Station Identification 1. DESCRIPTION This test will demonstrate that the repeater(s) programmed for Base Station Identification (BSI) operation at every site broadcasts the FCC BSI at predefined intervals (usually 30 minutes). To accomplish this, a service monitor will be set up to monitor the BSI channel of a random site and note that the Base Station Identification is heard. SETUP A service monitor will be required to perform this test. Note: A properly configured subscriber can be used to monitor the frequency for the BSI tones in place of a service monitor. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Choose one site to test for Base Station Identification (BSI). Step 2. Step 3. Setup the service monitor to receive the frequency of the BSI channel for the particular site. Monitor the service monitor until the Base Station Identification is broadcast. Verify that the BSI tones are heard on the monitored frequency. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-36 System Reliability Features 2. TEST Multiple Control Channels 1. DESCRIPTION A maximum of four channels are eligible for assignment as control channel at each site. In the event that the assigned control channel fails at any remote site, the Zone Controller automatically selects one of the other control capable channels as the active control channel for that site. A Control Channel Preference Level can be used to rank the control capable channels where 1 is the highest ranking and 4 the lowest. SETUP RADIO -1 - TALKGROUP 1 RADIO -2 - TALKGROUP 1 RADIO -3 - TALKGROUP 2 RADIO -4 - TALKGROUP 2 Note: All radios should be affiliated to the site under test. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a Talkgroup Call with RADIO -1 on TALKGROUP 1. Step 2. Observe that only RADIO -2 will be able to monitor and respond to the call. Step 3. Initiate a Talkgroup Call with RADIO -3 on TALKGROUP 2. Step 4. Observe that only RADIO -4 will be able to monitor and respond to the call. Step 5. Power off the control channel at the site under test. Step 6. Observe that the control channel rotates to the next available channel capable of acting as a control channel. Step 7. Initiate a Talkgroup Call with RADIO -1 on TALKGROUP 1. Step 8. Observe that only RADIO -2 will be able to monitor and respond to the call. Step 9. Initiate a Talkgroup Call with RADIO -3 on TALKGROUP 2. Step 10. Observe that only RADIO -4 will be able to monitor and respond to the call. Power up the channel previously powered off to return the system to normal operation. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-37 System Reliability Features 2. TEST Transmitter Power Failure Shutdown 1. DESCRIPTION The repeaters can detect a loss or decrease in transmitter output power of all trunked repeaters connected to it. Each trunked repeater contains an internal wattmeter element. Once the forward power has decreased past the threshold set, the repeater instructs the Zone Controller to take the channel out of service. If reflected power increases past the threshold set. the repeater will also instruct the Zone Controller to take the channel out of service. Once the station threshold has been exceeded and the station taken out of service a 5 minute timer will start. At the timer expiration a transmitter test will start to perform a self check on the station. This self check lasts for 20 seconds. If the station passes the self check it will be placed back into service. Note: This test should be done on a site with more than 2 channels. Failsoft will occur if the test is done on a 2 channel site. SETUP RADIO -1 - TALKGROUP 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Step 2. Step 3. Step 4. Step 5. Select a channel to disconnect the transmit antenna connection to the trunked repeater. (This will cause a high VSWR condition) Key RADIO -1 so that the selected channel is assigned, and verify that the channel disables due to an alarm condition. Verify that this alarm is reported at the Unified Event Manager (UEM). Wait 30 seconds after the failure then restore the transmit antenna connection to the trunked repeater. Using the station LEDs, verify that the time it takes from the corrected connection to the station being placed back in service is within 5 minutes. Verify the Unified Event Manager (UEM) also reports the station being back in service. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-38 System Reliability Features 2. TEST Redundant Site Controller Switching - Automatic Switchover 1. DESCRIPTION The Site Controller subsystem uses two Site Controllers in a redundant configuration. The backup Site Controller is made active either upon the loss of communication to the active Site Controller or upon a user initiated command from the Site Control Manager. This test will demonstrate that on the loss of the active site controller the standby controller will become active and carry on the site operations. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 RADIO -3 - TALKGROUP 1 RADIO -3 - SITE - SITE 1 All Radios should be "Site Locked". VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Verify both Site Controller are available and in the Normal state. Step 2. Power off the active Site Controller (or in the ESS configuration connect to the Active Site controller using CSS and perform a "reset") and verify the backup becomes the new active Site Controller (note events in the event viewer). Step 3. Key RADIO -1 and verify that RADIO -2 and RADIO -3 hear the audio. Step 4. End the call from RADIO -1. Step 5. Power up the Site Controller (if it was powered off). Verify the Site Controller returns to the normal state. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-39 System Reliability Features 2. TEST Redundant Zone Controller Switching/Automatic Switchover 1. DESCRIPTION In a non-DSR configuration the Zone Controller subsystem uses two Zone Controllers in a redundant configuration. The backup Zone Controller is made active either upon the loss of the active ZC or upon a user command from the Unified Network Configurator (UNC). In a DSR configuration there are 4 Zone Controllers in a redundant configuration Any one of the 4 could be active to keep the Zone Sites in Wide Area Trunking. If using the Dynamic Resilience Zone configuration the Unified Event Manager will report the Zone Controller switchover in both Unified Event Managers (UEM). SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 RADIO -3 - TALKGROUP 1 RADIO -3 - SITE - Site3 (Site3 should be in another Zone if applicable.) * The Zone Controllers should be sucessfully synchronized before performing this procedure. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Verify the state of the current Zone Controllers is Active or Standby in the Unified Network Configurator (UNC). (There will be 2 Zone Controllers in single Zone or 4 in the case of DSR zones.) Step 2. Reset the active Zone Controller via the Unified Event Manager (UEM) diagnostic. Step 3. Verify using UNC. UEM and ZoneWatch (if applicable) that the standby Zone Controller becomes active and brings all sites back wide. Wait for the Radios to settle out the site affiliations. Step 4. Key RADIO -1 and verify that RADIO -2 and RADIO -3 hear the audio. Step 5. End the call from RADIO -1. Step 6. Verify that Zone Controller that was reset comes back up to a "Standby" state. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-40 System Reliability Features 2. TEST Station Failure 1. DESCRIPTION When a base station repeater at one site fails due to hardware problems, the pending call is lost and the trunking controller removes the channel from service system wide. This failure can be created by powering down one base station repeater. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 VERSION #1.010 Step 1. Step 2. Step 3. Power down a voice repeater for any voice channel at SITE 1. Initiate calls using RADIO -1 to step through all available voice channels. Verify that the disabled channel is not used at SITE 1. Pass Fail Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-41 Audio IP Logging 2. TEST Logging Trunking Talkgroup Call 1. DESCRIPTION This test will demonstrate how the Archiving Interface Server (AIS) can be used to log trunking talkgroup call audio/events on a given talkgroup. The audio is archived in a vocoded format (IMBE for Trunking Talkgroup Calls). SETUP The AIS at MCC 7500 Console site affiliated to TALKGROUP 1. RADIO -1 - TALKGROUP 1 RADIO -1 - SITE 1 CONSOLE -1 - TALKGROUP 1 CONSOLE -1 - CONSOLE SITE 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a talkgroup call from RADIO -1 on TALKGROUP 1. Step 2. Observe that the call events/audio are being sent to the logging system by the AIS. Step 3. Using the playback station and logging recorder, verify the logged audio/events correspond to steps 1 and 2. Step 4. Initiate a talkgroup call from CONSOLE -1 on TALKGROUP 1. Step 5. Observe that the call events/audio are being sent to the logging system by the AIS. Step 6. Using the playback station and logging recorder, verify the audio/events logged correspond to steps 4 and 5. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-42 Audio IP Logging 2. TEST Logging Secure Trunking Talkgroup Call 1. DESCRIPTION This test will demonstrate the Archiving Interface Server (AIS) can be used to log trunking talkgroup call audio for call in a secure transmit mode on a given talkgroup. The audio is archived in a vocoded decrypted format (IMBE for Trunking Talkgroup Call) only when the logging system user requested coded audio to be logged. SETUP The AIS at MCC7500 Console site is affiliated to TALKGROUP 1 and has the appropriate secure keys loaded. RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 CONSOLE -1 - TALKGROUP 1 VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate PTT from RADIO -1 on TALKGROUP 1 in a secure transmit mode. Step 2. Step 3. Step 4. Observe that the call audio is being sent to the logging system by the playback application. If TALKGROUP 1 is marked to receive coded audio verify the coded audio can be played back via the application. Observe that the events for the TALKGROUP 1 call is logged even if the TALKGROUP 1 is not marked to receive coded audio. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-43 Audio IP Logging Logging Subsystem - Emergency Events and Calls -Emergency Alarm 1. DESCRIPTION This test will demonstrate that upon receiving notification from the Zone Controller of an Emergency Acknowledge/Recognize issued for a resource that the AIS is monitoring, the AIS will report the event to the Logging System. SETUP RADIO -1 TALKGROUP 1 CONSOLE -1 TALKGROUP 1 AIS, NICE play back station and record station connected to AIS via the site LAN switch. Configure an alias for RADIO -1 and RADIO -2 and allow adequate time for data propagation. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades 2. TEST Step 1. Step 2. Step 3. Step 4. Step 5. Start an emergency alarm from RADIO -1 Verify that a RADIO -1 displays a emergency indication and CONSOLE -1 gets the Emergency indication. Key up RADIO -1 on TALKGROUP 1. Verify that CONSOLE -1 receives audio on TALKGROUP 1. Playback recent TALKGROUP 1 call activities Verify that the logging system has recorded the emergency alarm call/events with correct Resource Alias, Individual Alias, Site ID and the zone ID. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-44 Audio IP Logging 2. TEST Logging Subsystem - Logging User Can Search Recorded Calls by Various Fields 1. DESCRIPTION This test will demonstrate that the Logging System will allow an authorized user to search recorded conversations and to play back the desired conversation. The supported search includes time and date search, resource search based on ID or alias (trunked talkgroup), type of call search, site search, zone search, and user search. Note: If using the Inform Application the search fields may be limited to 3 , Unit ID, Resource Alias and Individual ID. SETUP The NICE play back station connected to AIS via the site LAN switch. AIS with prerecorded audio / events in TALKGROUP 1 and TALKGROUP 2 is required. Assign aliases for TALKGROUP 1 (TALKGROUP 1_ALIAS) and TALKGROUP 2 (TALKGROUP 2_ALIAS). Playback station is configured with User Account UA. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Verify that TALKGROUP 1 and TALKGROUP 2 recorded audio / events can be replayed by logging in with UA user account. Step 2. Step 3. Step 4. Step 5. Step 6. Step 7. Search for a recorded call by 'time and date' field and play back the recorded call from the search results. Verify that accurate search results are produced and the recorded call is played back Search for a recorded call by 'Individual Alias' field and play back the recorded call from the search results Verify that accurate search results are produced and the recorded call is played back Search for a recorded call by 'Resource aliases' and play back the recorded call from the search results. Verify that accurate search results are produced and the recorded call is played back Step 8. Search for a recorded call by 'Site ID' field and play back the recorded call from the search results. Step 9. Verify that accurate search results are produced and the recorded call is played back. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-45 Report Generation Tests 2. TEST Historical Reports 1. DESCRIPTION Performance reports can be created automatically for dynamic statistical information about the air traffic activity on the system. These reports provide assistance with system management, resource planning, usage allocation, and monitoring. All reports are preformatted and summarize air traffic activity for a configured time span. Note: Depending on the time span selected smaller time intervals may not be available. SETUP No prior setup is required for this test. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. From the PC Application Launcher, select a zone. Step 2. From that zone's menu, choose Zone Historical Reports. Step 3. From the Historical Reports Player window that opens, select a report. Step 4. Using the left mouse button, click on the view button. Step 5. Observe a window opens allowing a user to enter report parameters. Step 6. Enter all desired data for the report and Generate Report. Step 7. Observe a window appears showing the requested report. Step 8. Close the report window. Step 9. Run the following reports during testing: Talkgroup at Zone Summary; User at Zone Summary; Site Summary. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-46 Report Generation Tests 2. TEST Unified Network Configurator (UNC) Reports - Device Inventory Report 1. DESCRIPTION The Unified Network Configurator (UNC) reports allow the user to generate data summaries to view information from the UNC database. Once the report is run, the results can be viewed, printed, and exported. This test will run a report that provides the data for a specific device. SETUP If the UNC is not open, double-click the UNC shortcut (UNC) on the desktop, and a VoyenceControl client session will launch. When prompted, use the Login dialog box to login to the UNC using the appropriate username and password. Note: The output format for the report will default to PDF. If a different output format for the report is desired it will need to be selected. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Step 2. Step 3. Step 4. From the UNC launch page menu bar select the Tools menu and choose Report Advisor. (If needed log in with appropriate user name and password.) From the Report Advisor screen, select the "Inventory Reports" header to expand the drop down menu. Select the desired report to run, in this case select "Devices by Model" and choose "Run Report". Leave the default field entries until the "Vendor Filter" field is reached. In this field select HP for the vendor. Then select the "Procurve Switch 2610-24" switch model for the "Model Filter" field. Enter a description for the report if so desired. Step 5. Verify the "Run now" button is selected and hit the Submit button. Step 6. Select the "Export Report" icon to save the report to the server. Select the file format for saving the report. For this test case, select PDF and hit Submit. (Not all formats will be viewable on the client. The appropriate application would be needed to view the saved file.) Step 7. Expand the "Downloads" tab on the left side of the screen to expand the selection. Verify the report that was saved in the previous step is listed. If it was saved as a PDF it should be available to view on the NM client. Step 8. View the generated report. (In some cases the user may need to temporarily allow pop ups on the browser) The report can be saved to the client by selecting "Save A Copy" icon and applying the appropriate information for filename and location. Step 9. Verify the generated report has appropriate information on the selected devices and that it can be saved to the client. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-47 System Management Tests 2. TEST ZoneWatch 1. DESCRIPTION ZoneWatch is an administration tool for monitoring radio traffic on a system. A system manager can use ZoneWatch to analyze traffic patterns for load distribution and troubleshoot radio and site problems. ZoneWatch is used to view current radio traffic activity for the system. This activity is displayed in graphical format, color -coded for easy identification of the type of activity occurring on the system. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 RADIO -3 - TALKGROUP 1 RADIO -3 - SITE - SITE 3 RADIO -4 - TALKGROUP 1 RADIO -4 - SITE - SITE 4 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Verify that ZoneWatch has been configured for the Grid and Multi Site Scroll windows to display system activity. Step 2. From the PC Application Launcher, select a zone folder. Step 3. From within that zone, select ZoneWatch. Step 4. Select the appropriate profile to be able to view the channel usage on the system. Step 5. Initiate several calls with the radios and observe that the appropriate channel usage information is displayed. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-48 System Management Tests 2. TEST Configuration Management - Access Permissions 1. DESCRIPTION In ASTRO releases the Radio System Infrastructure management is done in the Unified Network Configurator (UNC) application. The Unified Network Configurator Wizard (UNCW) also helps to configure the system by having a User interface into the system configuration. Configuration parameters such as Individual and Talkgroup Default Access Permission, and Site Access Denial Type can be manipulated from these applications. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 VERSION #1.030 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Delete the database record for RADIO -1 from the Provisioning Manager so that the system does not have any knowledge of RADIO -1. And distribute the configuration from the Provisioning Manager (i.e. invoke Distribute Configuration Changes operation). Step 2. Verify the "Individual Default Access Permission" flag is set to "NO". If changes are made. approve the job in Voyence, then Publish Infrastructure Data from the Unified Network Configuration Wizard (UNCW). Step 3. Step 4. Step 5. Step 6. Step 7. Step 8. Initiate a call from RADIO -1 on TALKGROUP 1. Verify that the Radio System rejects the RADIO -1 call request because RADIO -1 has not been defined in the Radio User database. Change the Individual Default Access Permission flag to YES. After approving the job in Voyence, Publish Infrastructure Data from the UNCW. Initiate a call from RADIO -1. Verify that the system permits the RADIO -1 call request because the system grants radio access using default settings. From the Provisioning Manager, configure the RADIO -1 records that was automatically created as a result of the radio's PTT. And distribute the configuration from the Provisioning Manager (i.e. invoke Distribute Configuration Changes operation). Reset the "Individual Default Access Permission" flag to NO. After approving the job in Voyence, Publish Infrastructure Data from the UNCW. Initiate a call from RADIO -1. Verify that the Radio System permits the RADIO -1 call request because RADIO -1 is now a valid user. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-49 System Management Tests 2. TEST Configuration Management - General Timeout Parameters 1. DESCRIPTION System and call timeout parameters such as Private Call Ring, Group Call Service Timeout, Private Call Hang Time, Emergency Call Hang time, Maximum Group Call Duration and Maximum Private Call Duration can also be manipulated from the Unified Network Configurator (UNC) Wizard. For this test the Private Call Duration will be limited to one minute. The call will change to transmission trunked after the one minute timer expires at which time the hang timers will come into play. Once the users have discontinued using the system for the Private Call long enough for the hang timers to expire the system will end the call. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 1 VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a TALKGROUP 1 call from RADIO -1. Verify that the Radio System permits the RADIO -1 call request. Step 2. In the manager, configure the "Maximum Private Call Duration" to 1 minute and apply. Step 3. Step 4. Initiate a Private Call from RADIO -1 to RADIO -2. Continue to converse back and forth using RADIO -1 and RADIO -2, Verify that after one minute elapses, the system will transmission trunk the Private Call because the maximum call duration has been exceeded. Once the hang time timer has expired the call will be terminated. Step 5. Reset the Private Call Maximum Call Duration setting to be 10 minutes (default). Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-50 System Management Tests 2. TEST Configuration Management - Subscriber Capabilities 1. DESCRIPTION The Provisioning Manager (PM) controls the parameters for all radio users and dispatchers on the system. Within the Subscriber section, the Radio User Configuration Window enables the network manager to tailor SmartZone subscribers' capabilities. Multigroup. Secure, Call Alert, Private Call, and Telephone Interconnect are some of the features that can be enabled or disabled. The features that could be unique to the particular user are configured directly in the Radio User Configuration Window. The features that could be configured the same for a group of users are placed into records called profiles. The network manager references the profile which contains the desired setup for these features from the Radio User Configuration Window. Note - A profile must already exist to be referenced through the Radio Configuration Window but can be modified later if needed. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 * Flag both radios to be capable of Call Alert, Private Call, and Dispatch Calls. * Set the "User Enabled" flag to YES for both RADIO -1 and RADIO -2. VERSION #1.010 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a Call Alert (PAGE) from RADIO -1 to RADIO -2. Verify that RADIO -2 receives the Call Alert. Step 2. Change the Call Alert Enabled flag to NO for RADIO -1 via the PM. Step 3. Initiate a Call Alert from RADIO -2 to RADIO - 1. Verify that RADIO -2 receives a reject when attempting to Call Alert RADIO -1. Step 4. Change the Call Alert Enabled flag back to YES for RADIO -1 via the PM. Step 5. Initiate a Call Alert from RADIO -2 to RADIO - 1. Verify that RADIO -1 now receives the Call Alert. Step 6. Initiate a Private Call (CALL) from RADIO -1 to RADIO -2. Verify that RADIO -2 receives the Private Call. Step 7. Change the Private Call Enabled flag to NO for RADIO -1 via the PM. Step 8. Initiate a Private Call from RADIO -2 to RADIO -1. Verify that RADIO -2 receives a reject when attempting to Private Call RADIO -1. Step 9. Change the Private Call Enabled flag back to YES for RADIO -1 via the PM. Step 10. Initiate a Private Call from RADIO -2 to RADIO -1. Verify that RADIO -1 now receives the Private Call. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-51 System Management Tests 2. TEST Configuration Management - Talkgroup Capabilities 1. DESCRIPTION The Provision Manager (PM) controls the parameters for all radio users and dispatchers on the system. Within the Subscriber section, the Talkgroup Configuration Window enables the network manager to tailor SmartZone Talkgroup Capabilities. Emergency, Secure and Priority Monitor are some of the features that can be enabled or disabled. The features that could be unique to the particular user are configured directly in the Talkgroup Configuration Window. The features that could be configured the same for a group of users are placed into records called profiles. The network manager references the profile which contains the desired setup for these features from the Talkgroup Configuration Window. NOTE: A profile must already exist to be referenced through the Talkgroup Configuration Window but can be modified later if needed. SETUP RADIO -1 - TALKGROUP 1 RADIO -1 - SITE - SITE 1 RADIO -2 - TALKGROUP 1 RADIO -2 - SITE - SITE 2 * Set the "Talkgroup Enabled" flag to YES for TALKGROUP 1 in the UCM. VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. Initiate a call from RADIO -1 on TALKGROUP 1. Verify that RADIO -2 hears the RADIO -1 audio. Step 2. Change the Talkgroup Enabled flag to NO for TALKGROUP 1 via the PM. Step 3. Initiate a call from RADIO -1 or RADIO -2 on TALKGROUP 1. Verify that neither radio can initiate a call because of the change in status of the Group Enabled Flag of TALKGROUP 1. Step 4. Initiate an Emergency call from RADIO -1. Verify that both the console (if present) and RADIO -2 can hear the transmission. Step 5. Dekey RADIO -1. Step 6. Change the Talkgroup Enabled flag back to YES for TALKGROUP 1 via the PM. Step 7. Initiate a call from RADIO -1 on TALKGROUP 1. Verify that both the console (if present) and RADIO -2 hear RADIO -1. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-52 System Management Tests 2. TEST Unified Event Manager - User Actions Create Audit Trails 1. DESCRIPTION One of the functions of the Unified Event Manager (UEM) that can be managed under Security Management is the User activity log, also called Audit Trails, containing: Operations invoked by the user. The name of the user who invoked the operation. Data and time of invocation. Target device/object on which the operation was invoked. The status of the operation. The category of invoked operation. This test will demonstrate that Unified Event Manager (UEM) user actions are logged by the system. These audit items log the history of activity for a period of up to 1 year. Note: The audit log is part of the UEM database. A database restore or reload of the UEM may affect the audit log history. SETUP NMclient 01 - UEM client session active. (Note: If the Authentication Audit Log has been cleared there will only be the event to clear the log.) VERSION #1.020 Weld County Master Site, MCC7500 and Software Upgrades Step 1. On a UEM client session, select Tools from the menu bar and then System Administration. The Administration Menu window opens up. Step 2. In the System Administration window, click on Audit Trails. Step 3. Verify the Authentication Audit Log is displayed. The following information is displayed for each entry: User Name, Operation, Audit Time, Severity, Category, and Audited Object. User actions recorded include: Login, Logout, Discovery, Synchronization, Device Deletion, Diagnostics, Telnet, and Manage/Unmanage. Pass Fail April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-53 Signoff Certificate By their signatures below, the following witnesses certify they have observed the system Acceptance Test Procedures. WITNESS: Please Print Name: Please Print Title: Motorola WITNESS: Please Print Name: Please Print Title: Signatures Date: Date: Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Acceptance Test Plan 6-2 SECTION 7 TRAINING PLAN 7.1 OVERVIEW Motorola Solutions Technical Training organization dedicates itself exclusively to offering the most comprehensive training available for Motorola Solutions advanced equipment to fully realize the equipment's potential. From sophisticated training needs analysis to ongoing training throughout the life cycle of your product or system, we can help ensure that your investment in training today is an investment for your future. Our training methodology includes knowledgeable instructors, well -designed courseware, lab activities, and system hardware and software that closely parallels your operating environment and that is integrated with proper system documentation. This methodology is based upon several key criteria: • Course design is driven by an analysis of learner needs and focuses on how-to rather than theory. • Learning objectives are based upon what learners need to accomplish on the job and focus on specific applications. • Hands-on lab opportunities using customer -specific job aids are incorporated into training to maximize the transfer of skills to the job and the retention/reuse of information. Motorola Solutions offers both train -the -trainer and end -user training. Students can attend training at one of our training centers or instructors can come to your site. In conjunction with or in addition to instructor -led training, we can provide self-study/e-leaming programs in which students follow a computer -based training module on CD-ROM or other media. 7.2 COURSES PROPOSED In the process of assessing your training needs, Motorola Solutions has identified the following course(s) that are necessary to achieve your training goals. Inserted within the matrix are course description files for your review or printing. While the standard courses are encouraged, the class outline may be tailored for your quotation. Thus, the outline(s) below may not exactly match your quoted class length and content. Course Bridging the Knowledge Gap for ASTRO 25 Technicians Course or Bridging the Knowledge Gap for ASTRO 25 System Administrator Course (Self -paced; On-line) Target Audience No. of Duration Location Date No. of Technicians and System Administrators Sessions (days) 1 6 -12 hours Self Paced Online Prior to remaining classes Attendees 4 Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Training Plan 7-1 Course Synopsis: This seven -module course is designed to bring Technicians from different technical backgrounds and experience levels to a common starting point for the ASTRO 25 curriculum. This course provides seven modules from the basic concepts of radio communication systems and computer networking features, through the evolution that led to the ASTRO 25 trunking system's architecture. This five -module course is designed to bring Administrators from different technical backgrounds and experience levels to a common starting point for the ASTRO 25 curriculum. This course provides seven modules from the basic concepts of radio communication systems and computer networking features, through the evolution that led to the ASTRO 25 trunking system's architecture. Note: Recommended prerequisite or experience for students without at least a Motorola SMARTNET trunking system background. Bridging the Knowledge Gap-TE Bridging the Knowledge Gap-SystE Course Target Audience No. of Sessions Duration (days) Location Date No. of Attendees ASTRO 25 IV&D System Networking System Administrators 1 5 Commerce City, CO Prior to remaining classes Up to 12 Course Synopsis: This course provides the technician with the necessary networking information required for understanding the Network Transport subsystem components installed in an ASTRO 25 IV&D communications system. The course includes familiarization with basic networking concepts and the networking components deployed throughout the system. Note: Important equipment requirements listed in the course description are needed for this class : iL 25 ASTRO System Netwo ASTRO 25 IV&D with M Core System Overview (Self -paced; On- line) Prerequisite #1 for Core Classes System Administrators 1 4 hours Self Paced Online Prerequisite 1 for Core Classes Up to 12 Course Synopsis: ASTRO25 IV&D Trunking with M Core System Overview self -paced course is the starting point of all ASTRO25 IV&D Trunking with M Core System. In order to take other classes, students are required to complete this course and obtain a passing score in the corresponding test. It presents a high level description of the system's call flow capabilities. components, features and benefits. ACS711200_Tr _M_Core_Ove - ll `� ASTRO 25 IV&D Introduction to Radio System Management Applications (Self -paced; On- line) Prerequisite #2 for Core Classes System Administrators 1 12 hours Self Paced Online Prerequisite 2 for Core Classes Up to 12 Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. © Motorola Solutions Confidential Restricted Training Plan 7-2 Course Synopsis: This virtual, interactive course provides a high-level overview of the Motorola Radio System Management applications through recorded demonstrations of common system tasks. ASTRO 25 I' Intro to Radio Course Target Audience No. of Sessions Duration (days) Location Date No. of Attendees ASTRO 25 IV&D Radio System Administrator System Administrators 1 5 Commerce City, CO Prior to managing the system Up to 12 Workshop 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 ACS711102_AS and personnel for optimal ASTRO 25 IV&D system use. 25_IV&D_Radio, ASTRO 25 IV&D with M Core Workshop Master Site Technicians 1 5 Commerce City, CO Prior to maintaining the system Up to 12 Course Synopsis: The ASTRO 25 IV&D with M Core course teaches advanced troubleshooting skills and best 14' 1 practices for the Trunked Large Systems. The course also focuses on gathering and analyzing system information to implement appropriate action(s) that return a system to full operational ACS711103_AS status. 25_IV&D_M_Co Course Specialized Feature Training ASTRO 25 IV&D ISSI.1 Network Gateway Overview Target Audience No. of Duration Sessions (days) System Administrators & Technicians 1 Location Date 4 hours Self Paced Online TBD Course Synopsis: The ASTR•4D25 IV&D ISSI.1 Network Gateway Overview is a self -study training course intended to provide a technical overview of the Inter -Sub -System Interface (ISSI) Network Gateway Interfaces between different ASTRO 25 Systems. No. of Attendees 4 ASTRO 25 IV&D I Network Gateway It is recommended that the students bring their lap top computers for all System Manager and Technician classes. Students will receive their manuals in CD-ROM format. Students will also receive hard copy participant guides. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Training Plan 7-3 SECTION 8 WARRANTY AND MAINTENANCE PLAN Motorola has over 75 years of experience supporting mission critical communications for public safety and public service agencies. Motorola's technical and service professionals use a structured approach to life cycle service delivery and provide comprehensive maintenance and support throughout the life of the system. The value of support is measured by system availability, which is optimi7ed through the use of proactive processes, such as preventive maintenance, fault monitoring and active response management. System availability is a function of having in place a support plan delivered by highly skilled support professionals, backed by proven processes, tools, and continuous training. 8.1 THE MOTOROLA SERVICE DELIVERY TEAM Customer Support Manager Your Motorola Customer Support Manager provides coordination of support resources to enhance the quality of service delivery and to ensure your satisfaction. The Customer Support Manager (CSM) is responsible to oversee the execution of the Warranty and Service Agreement and ensure that Motorola meets its response and restoration cycle time commitments. The CSM will supervise and manage the Motorola Authorized Servicer's functions. Motorola System Technologists The Motorola System Teclmologists (ST) are available to assist Motorola's Authorized Servicers when needed for network health and operations. Motorola System Support Center Located in Schaumburg, Illinois, the System Support Center (SSC) is a key component to the overall management and system maintenance. As detailed in this Customer Support Plan, the following services are provided by the System Support Center: • Network Monitoring • Dispatch Service • Infrastructure Repair with Advanced Replacement • Technical Support Motorola Local Service Provider Motorola's authorized service centers are staffed with trained and qualified technicians. They provide rapid response, repair, restoration, Weld County Master Site, MCC7500 and Software Upgrades Motorola has proven experience to deliver mission critical network support Extensive Experience — Motorola has over 70 years of experience supporting mission critical communications and the Public Safety community. Capacity to Respond — Motorola's network of local service centers, repair depots, system support center and parts support enable Motorola to provide quick and effective service delivery. Flexibility and Scalability — Motorola's Support Plans are customized to meet individual Customer needs. Skills and Process — Motorola uses a well - established, structured, and disciplined approach to provide service delivery. Motorola's team of well -trained and committed people understands the communications technology business. April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Warranty and Maintenance Plan 8-1 installations, removals, programming, and scheduled preventive maintenance tasks for site standards compliance and RF operability. Motorola's authorized service centers are assessed annually for technical and administrative competency. Motorola places great emphasis on ensuring that communications systems, such as the one proposed for Weld County, meet high standards for design, manufacture, and performance. To enhance the value of the communications system being acquired, Motorola offers customized warranty and post - warranty services as outlined in this section. 8.2 WARRANTY SERVICES Motorola will provide warranty services per our standard warranty terms and conditions as outlined within the Conumrucation Systems Agreement within this proposal. In addition to the Standard Commercial Warranty, the service products that comprise the Custom Warranty package are listed below along with a brief description. 8.2.1 Dispatch Service Motorola's Dispatch Service ensures that trained and qualified technicians are dispatched to diagnose and restore your communications network. Following proven response and restoration processes, the local authorized service center in your area is contacted and a qualified technician is sent to your site. An automated escalation and case management process is followed to ensure that technician site arrival and system restoration comply with contracted response and restore times. Once the issue has been resolved, the System Support Center verifies resolution and with your approval, closes the case. Activity records are also available to provide a comprehensive history of site performance, issues, and resolution. 8.2.2 OnSite Infrastructure Response Motorola OnSite Infrastructure Response provides local, trained and qualified technicians who arrive at your location to diagnose and restore your communications network. Following proven response and restore processes, Motorola Dispatch contacts the local authorized service center in your area and dispatches a qualified technician to your site. An automated escalation and case management process ensures that technician site arrival and system restoration comply with contracted response times. The field technician restores the system by performing first level troubleshooting on site. If the technician is unable to resolve the issue, the case is escalated to the System Support Center or product engineering teams as needed. 8.2.3 Network Preventative Maintenance Network Preventative Maintenance provides an operational test and alignment on your infrastructure or fixed network equipment to ensure that it meets original manufacturer's specifications. Trained technicians: • Physically inspect equipment • Remove dust and foreign substances • Clean filters • Measure, record, align and adjust equipment to meet original manufacturer's specifications This service is performed based on a schedule agreed upon between you and Motorola. Network Preventative Maintenance proactively detects issues that may result in system malfunctions and operational interruptions. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Warranty and Maintenance Plan 8-2 8.2.4 Infrastructure Repair with Advanced Replacement Infrastructure Repair with our Advanced Replacement upgrade supplements your spares inventory with Motorola's centralized inventory of critical equipment. In advance of Motorola repairing the malfunctioning unit, a replacement unit is sent to you within 24 hours to ensure a spare unit is available. Upon receipt of the malfunctioning unit, Motorola repairs the unit and replace it in our centralized inventory. 8.2.5 Technical Support Service Motorola Technical Support service provides an additional layer of support through centralized, telephone consultation for issues that require a high level of communications network expertise and troubleshooting capabilities. Technical Support is delivered by the System Support Center (SSC). The SSC is staffed with trained, skilled technologists specializing in the diagnosis and swift resolution of network performance issues. These technologists have access to a solutions database as well as in house test labs and development engineers. Technical Support cases are continuously monitored against stringent inbound call management and case management standards to ensure rapid and consistent issue resolution. Technical Support service translates into measurable, customer -specific metrics for assured network performance and system availability. 8.2.6 Network Monitoring Service Network Monitoring Service can help keep your network at optimum availability so it is ready to serve mission critical communications needs. By watching over the network continuously, Network Monitoring Service takes action whenever needed, and resolves network problems. We often intervene and correct the problem before you even know a problem exists. Network Monitoring Service provides improved productivity and enhanced network performance, which in turn helps to increase your technology Return -On -Investment. Using a combination of network monitoring software, automated alerts, and remote diagnostics inquiries, our System Support technologists actively monitor your network to maximize network uptime and overall preparedness... for the expected and unexpected. Upon receiving an alert, our team immediately performs a series of diagnostics to assess the problem. Often the situation can be resolved remotely, but when additional attention is required, local field technicians are dispatched immediately to your site to achieve restoration. Motorola's Network Monitoring service is a vital component of an intelligent communication support plan that keeps your business operating smoothly, your costs down, and assures maximum preparedness at all times. Specifically, Network Monitoring Service provides: • Improved network availability • Remote and timely resolution to minimize downtime • Cost efficiencies • Optimize time at site due to assessment and knowledge transfer before dispatch • Minimize unnecessary trips to site • Mitigate need for 24x7 operations monitoring center • Detailed Reports Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Warranty and Maintenance Plan 8-3 8.2.7 Security Update Service (SUS) Commercial security software updates are often designed without RF systems in mind and could cause inadvertent harm to your radio network, disrupting mission -critical communications and putting your first responders and citizens at risk. The Motorola Security Update Service assures that commercial anti -virus definitions, operating system software patches, and Intrusion Detection Sensor signature files are compatible with your ASTRO 25 network and do not interfere with network functionality. Our expert network security technologists analyze, perform testing, and validate the latest security software updates in a dedicated test lab and provide continuous monitoring of updates to provide you regular electronic updates upon completion of successful testing. SUS SUS Platinum Anti -virus Definition Update ✓ ✓ Minor Release (patch release) ✓ ✓ Information Assurance Remediation ✓ Major Release (system release) Hardware Refresh Implementation Services Regional Partner Invoicing available available • Anti -virus definitions and intrusion detection sensor updates for Motorola supplied equipment from applicable original equipment manufacturer • Minor releases may include commercial OS and application security updates, patches and service pack updates for Microsoft Windows and Server OS, Red Hat Linux, Sun Solaris and any Motorola software service packs that may be available • Recommendations for IA remediation may include, but is not limited to the following: provide security software updates; provide operating system security updates or patches; implement configuration changes: upgrade to a later ASTRO 25 System Release (upgrade expense not included), or recommending a compensating control • Regional partner invoicing provides ability to separate invoicing across multiple agencies 8.3 POST WARRANTY SERVICES As Motorola's continuing commitment to supporting your system, warranty services can be extended after the first year to provide maintenance and service support in future years. Any of the services that we identify can be customized in future years, and are available for purchase either in "System Support Services" packages or as individual service offerings. These system support services significantly benefit Weld County because the system can be effectively supported after the warranty period, thereby maximizing the operational capabilities and useful life of the system and protecting your investment in the system. 8A SUMMARY Whether it's a routine service call, or a disaster situation, Motorola understands its responsibility and takes pride in its commitment to deliver proven response service to the public safety community. Motorola has the capability to provide the technical, administrative, consultative, and maintenance repair services needed to support, enhance, and maintain the effectiveness of your communications network. Motorola's goal is to provide Weld County with the qualified resources, to maintain and improve system operation and availability, and to deliver world class service support. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page. ® Motorola Solutions Confidential Restricted Warranty and Maintenance Plan 8-4 Warranty and Post Warranty Service Overview Warranty Year Post Warranty Year Dispatch Service ✓ On Site Infrastructure Response _ Network Preventative Maintenance Infrastructure Repair with Advanced Replacement _ _ Technical Support Service _ _ Network Monitoring Service _ Security Update Service (SUS) _ _ The M3 Core Post Warranty pricing includes Infrastructure Repair with Advanced Replacement, Technical Support and Security Update Services. The new 14 position MCC 7500 Post Warranty pricing includes Dispatch, On Site Infrastructure Response, Network Preventative Maintenance, Infrastructure Repair with Advanced Replacement, Technical Support, Network Monitoring and Security Update Services. Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Warranty and Maintenance Plan 8-5 QMOTOROLA SOLUTIONS STATEMENT OF WORK ASTRO 25 SOFTWARE MAINTENANCE AGREEMENT (SMA) 1.0 Description of Service and Obligations 1.1 As major system releases become available, Motorola agrees to provide the system owner with the software required to execute up to one system infrastructure upgrade in a 12 month period for thew ASTRO 25 system. 1.2 Motorola agrees to provide minor software upgrades, known as "patch releases", which may include commercial Operating Software ("OS") and application software patches and service pack updates when and if available. Currently, the parties acknowledge that Motorola's service includes Microsoft Windows and Server OS, Red Hat Linux, Sun Solaris and any Motorola software service packs that may be available. Motorola agrees to provide only patch releases that have been analyzed, pre -tested. and certified in a dedicated ASTRO 25 test lab to ensure that they are compatible and do not interfere with the ASTRO 25 network functionality. Corresponding 3rd Party software and operating system patches will be released quarterly upon successful completion of the regular test cycle or at Motorola's discretion. Once a patch release has been validated as safe for deployment on the radio network, Motorola agrees to post it on a Motorola secure extranet site for the Customer to download and deploy. 1.2.1 The parties agree that minor software upgrades, and patch release coverage, which include commercial Operating Software ("OS") and application software patches and service pack updates, will terminate should the customers system release version become more than 5 system release versions form the current shipping release version. 1.3 The parties agree that ASTRO 25 system release upgrades are considered "major" upgrades if they include commercial OS and application software updates as well as Motorola system release software. System releases shall be pre -tested and certified in Motorola's Systems Integration Test lab. ASTRO 25 system releases shall improve the system functionality and operation from previous releases and may include some minor feature enhancements. At Motorola's option, system releases may also include significant new feature enhancements that Motorola may offer for purchase. 1.4 The parties agree that the ASTRO 25 system release upgrades include limited security updates issued by Microsoft, Solaris and Red Hat certified with each individual system release. 1.5 Motorola agrees that this Agreement entitle a Customer to past software versions for the purpose of downgrading product software to a compatible release version. 1.6 The parties agree that the ASTRO 25 SMA pricing is based on the system configuration outlined in Appendix A. The parties further agree that this configuration is to be reviewed annually on the contract renewal date. Any change in system configuration may require an ASTRO 25 Software Maintenance Agreement price adjustment. 1.7 The parties agree and acknowledge that the ASTRO 25 SMA applies only to system release upgrades within the ASTRO 25 7.x platforn. ASTRO 25 Software Maintenance Agreement SOW August 24. 2012 1 of QMOTOROLA SOLUTIONS 1.8 Motorola agrees that the following ASTRO 25 system release software for the following products are covered under this Agreement: base stations, site controllers, comparators. routers, LAN switches, servers, dispatch consoles, network management terminals, Network Fault Management (NFM) products, network security devices such as firewalls and intrusion detection sensors, and associated peripheral infrastructure software. 1.9 Product programming software such as Radio Service Software ("RSS"), Configuration Service Software ("CSS"), and Customer Programming Software ("CPS") are also covered under this Agreement. 1.10 The parties agree that the SMA makes available the subscriber radio software releases that are shipping from the factory during the SMA coverage period. The parties further agree that new subscriber radio options and features not previously purchased are excluded from SMA coverage. Additionally, subscriber software installation and reprogramming are excluded from the ASTRO 25 SMA coverage. 1.11 Motorola agrees to issue the SMA bulletin on an annual basis and post it in soft copy on a designated extranet site for Customer access. Standard and optional features for a given ASTRO 25 system release are listed in the SMA bulletin. 1.12 Coverage Continuity. 1.12.1 The parties acknowledge and agree that the ASTRO 25 SMA requires continuous coverage beginning within (90) days after the expiration of system warranty. Should the Customer delay purchase of an ASTRO 25 SMA beyond (90) days from system warranty expiration or elect to discontinue the ASTRO 25 SMA and later decide to reinstate coverage, additional payment(s) will be necessary to cover the period for which coverage was discontinued or delayed. The total of payments for lapses in coverage will not exceed 3 years in equivalent ASTRO 25 SMA coverage. 1.13 The Customer agrees that they shall: 1.13.1 Contact Motorola upon receiving a bulletin to engage the appropriate Motorola resources for a system release upgrade. 1.13.2 Purchase any hardware and labor needed to implement system release upgrades. 1.13.3 Purchase optional system release features or system expansions. 1.13.4 Purchase any additional hardware and software needed to implement any optional system release features or system expansions. 1.13.5 Provide or purchase labor to implement optional system release features or system expansions. 1.13.6 Cooperate with Motorola and perform all acts that are reasonable or necessary to enable Motorola to provide software upgrade services. ASTRO 25 Software Maintenance Agreement SOW August 24. 2012 2of6 QMOTOROLA SOLUTIONS 2.0 Exclusions and Limitations 2.1 The parties agree that Systems that have non-standard configurations that have not been certified by Motorola Systems Integration Testing are specifically excluded from the ASTRO 25 SMA unless otherwise agreed in writing by Motorola and included in this SOW. 2.2 The parties acknowledge and agree that the ASTRO 25 SMA does not cover the following products: • MCC5500 Dispatch Consoles • MIP5000 Dispatch Consoles • Plant/E911 Systems • MOTOBRIDGE Solutions • ARC 4000 Systems • Motorola Public Sector Applications Software (PSA) • Custom SW, CAD, Records Management Software • Data Radio Devices • Mobile computing devices such as Laptops • Non -Motorola two-way radio subscriber products • Genesis Products • Point-to-point products such as Microwave terminals and association multiplex equipment 2.3 The parties agree that hardware upgrades and/or replacements, as well as pre -planning, design and implementation services required to deploy an ASTRO 25 system release upgrade are not included within the coverage of the ASTRO 25 Software Maintenance Agreement. The parties further agree that implementation services and any hardware upgrades and/or replacements required to support the system release upgrade will be quoted separately for the specific system release upgrade requested by the customer. 2.4 The parties agree that the ASTRO 25 system releases include limited security updates issued by Microsoft, Solaris and Red Hat certified with each individual system release. 2.5 The parties agree that the ASTRO 25 SMA does not cover software support for virus attacks or other applications that are not part of the ASTRO 25 system, or unauthorized modifications or other misuse of the covered software. Motorola is not responsible for management of anti -virus or other security applications (such as Norton). Anti -virus and/or security application support may be covered under a separate agreement. 2.6 The parties agree that upgrades for equipment add ons or expansions during the teen of the contract are not included in the coverage of this SOW unless otherwise agreed to by Motorola. 3.0 Special provisions 3.1 Customer acknowledges that if its System has a Special Product Feature, additional engineering may be required to prevent an installed system release from overwriting the Special Product Feature. Upon request, Motorola will determine whether a Special Product Feature can be incorporated into a system release and whether additional engineering effort is required. If additional engineering is required Motorola will issue a change order for the change in scope and associated increase in the price for the ASTRO 25 Software Maintenance Agreement. ASTRO 25 Software Maintenance Agreement SOW August 24. 2012 3 of 6 QMOTOROLA SOLUTIONS 3.2 Customer may use the software (including any System Releases) only in accordance with the applicable Software License Agreement. The SMA Statement of Work is not intended to modify or terminate an existing Software License Agreement. The SMA or services rendered by Motorola does not alter Motorola's software intellectual property rights. 3.3 Customer acknowledges that Software Maintenance Agreement services do not include repair or replacement of hardware or software necessary due to defects that are not corrected by the system release, nor does it include repair or replacement of defects resulting from any nonstandard or improper use or conditions or from unauthorized installation of software. 3.4 The parties agree that ASTRO 25 SMA coverage and the parties' responsibilities described in this Statement of Work will automatically terminate if Motorola no longer supports the ASTRO 25 7.x software version in the Customer's system or discontinues the SMA program; in either case, Motorola will refund to Customer any prepaid fees for Software Maintenance services applicable to the terminated period. 3.5 Motorola may suspend or terminate the ASTRO 25 Software Maintenance Agreement if the following conditions apply: • Customer fails to pay Motorola any fees for the ASTRO 25 SMA when due • Customer breaches the Software License Agreement or other applicable agreement • Customer's rights to use the software under the Software License Agreement expire or are terminated • Customer replaces its Motorola System with a system from another manufacturer ASTRO 25 Software Maintenance Agreement SOW August 24. 2012 4of6 QMOTOROLA SOLUTIONS 4.0 WARRANTIES AND DISCLAIMER: Motorola warrants that its services will be free of defects in materials and workmanship for a period of ninety (90) days following completion of the service ("Warranty Period"). Your sole remedies are to require Motorola to re -perform the affected service or at Motorola's option to refluid, on a pro -rata basis, the service fees paid for the affected service. 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 this information is provided) are collectively referred to as "Documentation." During the applicable Warranty Period, Motorola warrants that the tested anti -virus definitions, intrusion detection sensor signatures, and operating system security updates/patches do not degrade or compromise System functionality, and that after incorporation of the recommended remediation action the System Software, when used properly and in accordance with the Documentation, 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 solely with reference to the Documentation. Motorola does not warrant that Customer's use of the software or products will be ilnintenupted or error -free or that the software or the products will meet Customer's particular requirements. MOTOROLA DISCLAIMS ALL OTHER WARRANTIES WITH RESPECT TO PRETESTED ANTI- VIRUS DEFINITIONS, DATABASE SECURITY UPDATES, OPERATING SYSTEM SOFTWARE PATCHES, AND INTRUSION DETECTION SENSOR SIGNATURE FILES, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON -INFRINGEMENT. FURTHER, MOTOROLA DISCLAIMS ANY WARRANTY CONCERNING THE NON -MOTOROLA SOFTWARE AND DOES NOT GUARANTEE THAT CUSTOMER'S SYSTEM WILL BE ERROR -FREE OR IMMUNE TO VIRUSES OR WORMS AS A RESULT OF THESE SERVICES. ASTRO 25 Software Maintenance Agreement SOW August 24. 2012 5of6 QMOTOROLA SOLUTIONS Appendix A - System Pricing Configuration This configuration is to be reviewed annually on the contract renewal date. Any change in system configuration may require an ASTRO 25 SMA price adjustment. Core Master Site Configuration 0 Zones in Operation (Including DSR and Dark Master Sites) 0 Zone Features: IV&D, OTAR, TDMA, Telephone Interconnect, CNI. HPD, ISSI CSMS, IA. POP25, Text Messaging, Outdoor Location, ... 0 RF System Voice RF Sites & RF Simulcast Sites 8 Repeaters/Stations (FDMA) 64 Repeaters/Stations (TDMA) 0 HPD RF Sites 0 HPD Stations 0 Dispatch Console System Dispatch Sites 2 Gold Elite Operator Positions 0 MCC 7500 Operator Positions (GPIOM) 15 MCC 7500 Operator Positions (VPM) 0 Conventional Channel Gateways (CCGW) 1 Conventional Site Controllers (GCP 8000 Controller) 2 Logging System Number of AIS Servers 2 Number of Voice Logging Recorder 1 Number of Logging Replay Clients 1 Network Management and MOSCAD NFM Network Management Clients 0 MOSCAD NFM Systems 0 MOSCAD NFM RTUs 0 MOSCAD NFM Clients 0 Fire Station Alerting (FSA) FSA Systems 0 FSA RTUs 0 FSA Clients 0 Fire Station Alerting (FSA) Voice Subscribers non-APX 0 Voice Subscribers APX 0 HPD Subscribers 0 ASTRO 25 Software Maintenance Agreement SOW August 24, 2012 6of6 SECTION 9 PRICING SUMMARY Motorola's pricing is based on the equipment list and services defined for the system designed for Weld County's 7.13 system. The Statement of Work (SOW) describes the work to be performed for the installation, optimization. and testing of the system and the equipment list provides the equipment necessary for this project. The pricing offered below is based upon implementation of all portions of the system at the same time. Implementation at a later date for any of the pieces listed below would require an increase in services associated with that piece. Description Pricing Weld County —Master Site M3 Core $1,442,465.00 ISSI Equipment $286,250.00 Weld M3 Core Integration Services $490,672.00 System Discount for bundled purchase with ADCOM and April 2013 contract <$472,046.00- Weld County Total $1,744,057.00 Weld County-MCC7500 and S/W Upgrades 14 Position MCC 7500 Console $899,633.00 MCC Console and RF Site Upgrades $606.875.00 Weld County Subtotal $1,506,508.00 System Discount for bundled purchase with ADCOM and April 2013 contract for Upgrade to existing MCCs and RF Sites <$129,264.00= Discount for April 2013 contract and Q2 2013 shipment of New MCC7500 <$50.000.00- Weld County Total $1,327,244.00 Weld County April 24, 2013 Master Site, MCC7500 and Software Upgrades Use or disclosure of this proposal is subject to the restrictions on the cover page_ © Motorola Solutions Confidential Restricted Pricing Summary 9-1 The optional warranty pricing below applies to the M3 Core. It includes Technical Support, Infrastructure Repair with Advanced Replacement and Security Update Service. Optional Extended Warranty Pricing 2nd Year Extended Warranty $84,382.00 3rd Year Extended Warranty $88,601.00 4th Year Extended Warranty $93,031.00 5th Year Extended Warranty $97,683.00 Extended Warranty Total $363,697.00 The optional warranty pricing below applies to the new 14 position MCC7500 console. It includes Dispatch, Technical Support, Infrastructure Repair with Advanced Replacement, Network Monitoring, Security Update Service, On Site Infrastructure Response Regular and Network Preventative Maintenance. Optional Extended Warranty Pricing 2nd Year Extended Warranty $29,244.00 3rd Year Extended Warranty $30,706.00 4th Year Extended Warranty $32,242.00 5th Year Extended Warranty $33,854.00 Extended Warranty Total $126,046.00 Warranty pricing has not been included for the existing Weld County equipment. That equipment was upgraded via software as part of this project. Any existing maintenance contract that may be in place would cover warranty for that equipment. Weld County Master Site, MCC7500 and Software Upgrades April 24, 2013 Use or disclosure of this proposal is subject to the restrictions on the cover page_ ® Motorola Solutions Confidential Restricted Pricing Summary 9-2 Hello