No preview available
Contract 2022-013ADocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 CONTRACT APPROVAL FORM TO: BRIAN BULTHUIS, CITY MANAGER DS THRU: FREDDY SUAREZ, PROCUREMENT SERVICES DIRECTOR FROM: RAMSEY JIMENEZ, SENIOR PROCUREMENT AGENT SUBJECT: BROWARD COUNTY CONTRACT FOR RADIOS WITH MOTOROLA SOLUTIONS DATE: FEBRUARY 14, 2022 THE PROCUREMENT SERVICES DIRECTOR RECOMMENDS THE FOLLOWING: APPROVE: Agreement between the City of Clermont and Motorola Solutions to provide radio system and services for the Sanitation Department. The agreement shall take effect on the date of execution by both parties and shall remain in effect until May 23, 2027, unless renewed or terminated as provided by the Broward County contractual agreement. Upon mutual agreement, the agreement may be renewed for two (2) additional five (5) year terms. 2. Why is this action necessary: In accordance with the City of Clermont Purchasing Policy, the City Manager is authorized to approve contracts under $50,000 that do not require a budget amendment. 3. ADDITIONAL INFORMATION: At the request of the Public Services Department Sanitation Division, the Procurement Services Department sought a contract with Broward County for radio system and services, contract number R1422515R1/P1. The estimated annual expenditures is less than $25,000 and it is included in the Environmental Services Department budget. The Procurement Services Department issued RFI 2212-001 to notify local vendors of the City's intent to utilize other governmental entities' contract. At the completion of the RFI the Procurement Services Department received no interest. The Broward County contract was fully competed, advertised, and complies with the City of Clermont Purchasing Policy. 4. FISCAL IMPACT: The fiscal impact of $25,000 is included in the current year approved budget. 5. EXHIBITS: Broward County Bid Tabulation Motorola Solutions Agreement DocuSigned by: Signature APPROVAL AUTHORITY Approved ® Disapproved ❑ Reason/Suggestion (If disapproved) City Manager Title 2/18/2022 Date DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 AGREEMENT NO.2022-013 FOR P25 SYSTEM AND SERVICES WITH MOTOROLA SOLUTIONS, INC. THIS AGREEMENT, is made and entered into this 18 day of February 2022, by and between the CITY OF CLERMONT, FLORIDA, a municipal corporation under the laws of the State of Florida whose address is: 685 W. Montrose Street, Clermont, Florida, (hereinafter referred to as "CITY"), and Motorola Solutions, Inc., whose address is: 500 West Monroe Street, 43rd Floor, Chicago, IL 6066, (hereinafter referred to as "CONTRACTOR"). WHEREAS, Broward County through the public procurement process awarded an Agreement for a turnkey radio system and services solution, Broward County Contract Number R1422515RI/Pl (the "Broward County Contract"); WHEREAS, CITY desires to utilize the above -referenced awarded bid, CONTRACTOR's response thereto and Agreement in accordance with CITY's procurement policy to buy certain Motorola products; and WHEREAS, CONTRACTOR desires to enter into a contract with CITY based on the terms and conditions of the Broward County Contract Number RI422515RI/P1; WITNESSETH: That the parties hereto, for the consideration hereinafter set forth,mutually agree as follows: ARTICLE I — SCOPE OF WORK The CONTRACTOR shall sell to the CITY, certain Motorola products described in the Broward County Contract —included herein by reference in Exhibit A- at the prices listed in its SOW A-4 Section 3.0 Pricing. Provided, however, that nothing herein shall require CITY to purchase or acquire any items or services from CONTRACTOR thatis not specified in the CITY's purchase order ARTICLE 2 —SUPPLEMENTAL TERMS AND CONDITIONS 2.1 The parties hereby acknowledge that the scope of the Broward County Contract was related to a turnkey solution and therefore agree that terms and conditions set in the Broward County Contract do not fully apply to the scope of this Agreement. Hence, applicable supplemental terms and conditions are included in this Agreement and are described in Exhibit B. 2.2 The parties specifically agree that: a) The following sections of the Broward County Contract do not apply and are thereby deleted in their entirety from this Agreement: Sections 3.6 to 3.10; Article 4; and Article 5; and b) This Agreement does not bind or obligateCITY to purchase any minimum quantity of product during the term hereof 2.3. The following is the order of precedence shall be applied when interpreting this Agreement: 1) This Agreement DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2) The Supplemental Terms and Conditions (Exhibit B) 3) An applicable Contractor Quote/Proposal or Statement of Work 4) City's Purchase Order or Notice to Proceed 5) The Broward County Contract These documents shall be read to be consistent and complementary. Any conflict among these documents shall be resolved by giving priority to these documents in the order listed above. Notwithstanding the foregoing, ordering documents (purchase orders/notice to proceed) may contain transaction -specific terms and each ordering document that is accepted by the CONTRACTOR shall become a part of this Agreement as to the products and services listed on the ordering document only. No other terms and conditions shall apply. ARTICLE 3 — TERM AND TERMINATION 3.1. This Agreement is to become effective upon execution by both parties, and shall remain in effect until May 23, 2027 unless terminated or renewed by Broward County. 3.2. Upon mutual Agreement of the parties, this Agreement may be renewed for two (2) additional five (5) year term. ARTICLE 4 — INTENTIONALLY OMITTED ARTICLE 5 — PAYMENTS In accordance with the provisions fully set forth in the Contract Documents, CONTRACTOR shall submit an invoice to CITY upon completion of the services and delivery of products to CITY as set forth in the supplemental documents. CITY shall makepayment to the CONTRACTOR for all accepted deliveries and undisputed product delivered and services provided, within thirty (30) calendar days of receipt of the invoice. ARTICLE 6 — DISPUTE RESOLUTION - MEDIATION 6.1. Any claim, dispute or other matter in question arising out of or related to this Agreement shall be subject to mediation as a condition precedent to voluntary arbitration or the institution of legal or equitable proceedings by either party. 6.2. The CITY and CONTRACTOR shall endeavor to resolve claims, disputes and other matters in question between them by mediation. 6.3 The parties shall share the mediator's fee and any filing fees equally. The mediation shall be held in Clermont, Lake County, Florida, unless another location is mutuallyagreed upon. Agreements reached in mediation shall be enforceable as settlement Agreements in any court having jurisdiction thereof. ARTICLE 7 — INSURANCE 2 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 7.1. Worker's Compensation Insurance — The CONTRACTOR shall take out and maintain during the life of this Agreement, Worker's Compensation Insurance for all its employees connected with the work of this Project and, in case any work is sublet, the CONTRACTOR shall require the subCONTRACTOR similarly to provide Worker's Compensation Insurance for all of the subCONTRACTOR employees unless such employees are covered by the protection afforded by the CONTRACTOR. Such insurance shall comply with the Florida Worker's Compensation Law. In case any class of employees engaged in hazardous work under this Agreement at the site of the Project is not protected under the Worker's Compensation statute, the CONTRACTOR shall provide Employer's Liability insurance with a limit of $1,000,000 each accident; $1,000,000 disease -each employee; $1,000,000 disease -policy limit . (a) CONTRACTOR's Commercial General Liability Insurance — The CONTRACTOR shall take out and maintain during the life of this Agreement, Commercial General Liability Insurance as shall protect it from claims for damage for personal injury, including accidental death, as well as claims for property damages which may arise from operations underthis Agreement whether such operations are by itself or by anyone directly employed by it, and the amount of such insurance shall be as follows: CONTRACTOR's Commercial General Liability, $3,000,000 per occurrence and ,$10,000,000 aggregate. Liability Coverages, Bodily Injury Occurrence, & Property Damage (b) Automobile Liability Coverages, $1,000,000 Each, Bodily Injury & Property Damage Occurrence, Combined Single Limit Insurance clause for both BODILY INJURY AND PROPERTY DAMAGE shallprovide coverage on an occurrence basis. ARTICLE 8 — NOTICES All notices shall be in writing and sent by United States mail, certified or registered, with return receipt requested and postage prepaid, or by nationally recognized overnight courierservice to the address of the party set forth below. Any such notice shall be deemed givenwhen received by the party to whom it is intended. CONTRACTOR: Motorola Solutions, Inc. Attn: Daniel Sanchez, Territory Vice President 500 West Monroe Street, 43rd Floor Chicago, IL 60661 OWNER: City of Clermont Attn: Brian Bulthuis, City Manager 685 W. Montrose Street Clermont, FL 34711 3 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ARTICLE 9 — MISCELLANEOUS 9.1. Attorneys' Fees — In the event a suit or action is instituted to enforce or interpret any provision of this Agreement, the prevailing party shall be entitled to recover such sum as the Court may adjudge reasonable as attorneys' fees at trial or on anyappeal, in addition to all other sums provided by law. 9.2. Waiver — The waiver by city of breach of any provision of this Agreement shall notbe construed or operate as a waiver of any subsequent breach of such provision or of such provision itself and shall in no way affect the enforcement of any other provisions of this Agreement. 9.3. Severability — If any provision of this Agreement or the application thereof to any person or circumstance is to any extent invalid or unenforceable, such provision, orpart thereof, shall be deleted or modified in such a manner as to make theAgreement valid and enforceable under applicable law, the remainder of this Agreement and the application of such a provision to other persons or circumstances shall be unaffected, and this Agreement shall be valid and enforceable to the fullest extent permitted by applicable law. 9.4. Amendment — Except for as otherwise provided herein, this Agreement may not be modified or amended except by an Agreement in writing signed by both parties. 9.5. Entire Agreement — This Agreement including the documents incorporated by reference contains the entire understanding of the parties hereto and supersedes allprior and contemporaneous Agreements between the parties with respect to the performance of services by CONTRACTOR. 9.6. Assi _ ng ment — Except in the event of merger, consolidation, or other change of control pursuant to the sale of all or substantially all of either party's assets, this Agreement is personal to the parties hereto and may not be assigned, in whole or in part, without the prior written consent of the other party. 9.7. Venue — The parties agree that the sole and exclusive venue for any cause of action arising out of this Agreement shall be Lake County, Florida. 9.8. Applicable Law — This Agreement and any amendments hereto are executed and delivered in the State of Florida and shall be governed, interpreted, construed and enforced in accordance with the laws of the State of Florida. 9.9. Public Records — Contractor expressly understands records associated with this project are public records and agrees to comply with Florida's Public Records law to: (a) Keep and maintain public records that ordinarily and necessarily would be required by the CITY in order to perform the services contemplated herein. (b) Provide the public with access to public records on the same terms and conditions that the CITY would provide the records and at a cost that does not exceed the cost provided in this Florida's Public Records law or as otherwise provided by law. (c) Ensure that public records that are exempt or confidential and exempt from public records disclosure requirements are not disclosed except as authorized by law. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 (d) Meet all requirements for retaining public records and transfer, at no cost, to the CITY all public records in possession of CONTRACTOR upon termination of the contract and destroy any duplicate public records that areexempt or confidential and exempt from public records disclosure requirements. CONTRACTOR shall use reasonable efforts to provide all records stored electronically to the CITY in a format that is compatible withthe information technology systems of the CITY. (e) IF CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE CONTRACTOR'S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THIS CONTRACT, CONTRACTOR SHALL CONTACT THE CITY'S CUSTODIAN OF PUBLIC RECORDS ATCITY CLERK'S OFFICE, (352) 241-7331. IN WITNESS WHEREOF, the parties hereto have executed this Agreement on this 18 day of February , 2022. CITY OF CLERMONT —DocuSigned by: 1%W& f °J�s ATTEST: —DocuSigned by: T4-� A DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola Solutions, Inc. DocuSigned by: B Y (Signature Print Name: Daniel sanchez Title: Territory vice President Date:2/14/2022 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Exhibit A Contract Broward County Contract Number R1422515R1/Pl Hereby added by reference DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Exhibit B Supplemental Terms and Conditions Master Customer Agreement This Master Customer Agreement (the "MCA") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and the entity set forth in the signature block below ("Customer"). Motorola and Customer will each be referred to herein as a "Party" and collectively as the "Parties". This Agreement (as defined below) is effective as of the date of the last signature (the "Effective Date"). 1. Agreement. 1.1. Scope; Agreement Documents. This MCA governs Customer's purchase of Products (as defined below) and Services (as defined below) from Motorola. Additional terms and conditions applicable to specific Products and Services are set forth in one or more addenda attached to this MCA (each an "Addendum", and collectively the "Addenda"). In addition, the Parties may agree upon solution descriptions, equipment lists, statements of work, schedules, technical specifications, and other ordering documents setting forth the Products and Services to be purchased by Customer and provided by Motorola and additional rights and obligations of the Parties (the "Ordering Documents"). To the extent required by applicable procurement law, a proposal submitted by Motorola in response to a competitive procurement process will be included within the meaning of the term Ordering Documents. This MCA, the Addenda, and any Ordering Documents collectively form the Parties' "Agreement". 1.2. Order of Precedence. Each Addendum will control with respect to conflicting terms in the MCA, but only as applicable to the Products and Services described in such Addendum. Each Ordering Document will control with respect to conflicting terms in the MCA or any Addenda, but only as applicable to the Products and Services described on such Ordering Document. 2. Products and Services. 2.1. Products. Motorola will (a) sell hardware provided by Motorola ("Equipment"), (b) license software which is either preinstalled on Equipment or installed on Customer -Provided Equipment (as defined below) and licensed to Customer by Motorola for a perpetual or other defined license term ("Licensed Software"), and (c) license cloud -based software as a service products and other software which is either preinstalled on Equipment or installed on Customer - Provided Equipment, but licensed to Customer by Motorola on a subscription basis ("Subscription Software") to Customer, to the extent each is set forth in an Ordering Document, for Customer's own use in accordance with this Agreement. The Equipment, Licensed Software, and Subscription Software shall collectively be referred to herein as "Products", or individually as a "Product". At any time during the Term (as defined below), Motorola may substitute any Products at no cost to Customer, if the substitute is substantially similar to the Products set forth in the applicable Ordering Documents. 2.2. Services. 2.2.1. Motorola will provide services related to purchased Products ("Services"), to the extent set forth in an Ordering Document. 2.2.2. Integration Services; Maintenance and Support Services. If specified in an Ordering Document, Motorola will provide, for the term of such Ordering Document, (a) design, deployment, and integration Services in order to design, install, set up, configure, and/or integrate the applicable Products at the applicable locations ("Sites"), agreed upon by the Parties ("Integration Services"), or (b) break/fix maintenance, technical support, or other Services (such as software DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 integration Services) ("Maintenance and Support Services"), each as further described in the applicable statement of work. Maintenance and Support Services and Integration Services will each be considered "Services", as defined above. 2.2.3. Service Ordering Documents. The Fees for Services will be set forth in an Ordering Document and any applicable project schedules. A Customer point of contact will be set forth in the applicable statement of work for the Services. For purposes of clarity, each statement of work will be incorporated into, and form an integral part of, the Agreement. 2.2.4. Service Completion. Unless otherwise specified in the applicable Ordering Document, Services described in an Ordering Document will be deemed complete upon Motorola's performance of all Services listed in such Ordering Document ("Service Completion Date"); provided, however, that Maintenance and Support Services may be offered on an ongoing basis during a given Ordering Document term, in which case such Maintenance and Support Services will conclude upon the expiration or termination of such Ordering Document. 2.3. Non -Preclusion. If, in connection with the Products and Services provided under this Agreement, Motorola makes recommendations, including a recommendation to purchase other products or services, nothing in this Agreement precludes Motorola from participating in a future competitive bidding process or otherwise offering or selling the recommended products or other services to Customer. Customer represents that this paragraph does not violate its procurement standards or other laws, regulations, or policies. 2.4. Customer Obligations. Customer will ensure that information Customer provides to Motorola in connection with receipt of Products and Services are accurate and complete in all material respects. Customer will make timely decisions and obtain any required management approvals that are reasonably necessary for Motorola to provide the Products and Services and perform its other duties under this Agreement. Unless the applicable Ordering Document states otherwise, Motorola may rely upon and is not required to evaluate, confirm, reject, modify, or provide advice concerning any assumptions or Customer information, decisions, or approvals described in this Section. If any assumptions in the Ordering Documents or information provided by Customer prove to be incorrect, or if Customer fails to perform any of its obligations under this Agreement, Motorola's ability to perform its obligations may be impacted and changes to the Agreement, including the scope, Fees, and performance schedule may be required. 2.5. Documentation. Products and Services may be delivered with documentation for the Equipment, software Products, or data that specifies technical and performance features, capabilities, users, or operation, including training manuals, and other deliverables, such as reports, specifications, designs, plans, drawings, analytics, or other information (collectively, "Documentation"). Documentation is and will be owned by Motorola, unless otherwise expressly agreed in an Addendum or Ordering Document that certain Documentation will be owned by Customer. Motorola hereby grants Customer a limited, royalty -free, worldwide, non-exclusive license to use the Documentation solely for its internal business purposes in connection with the Products and Services. 2.6. Motorola Tools and Equipment. As part of delivering the Products and Services, Motorola may provide certain tools, equipment, models, and other materials of its own. Such tools and equipment will remain the sole property of Motorola unless they are to be purchased by Customer as Products and are explicitly listed on an Ordering Document. The tools and equipment may be held by Customer for Motorola's use without charge and may be removed from Customer's premises by Motorola at any time without restriction. Customer will safeguard all tools and equipment while in Customer's custody or control, and be liable for any loss or damage. Upon the expiration or earlier termination of this Agreement, Customer, at its expense, will return to Motorola all tools and equipment in its possession or control. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.7. Authorized Users. Customer will ensure its employees and Authorized Users comply with the terms of this Agreement and will be liable for all acts and omissions of its employees and Authorized Users. Customer is responsible for the secure management of Authorized Users' names, passwords and login credentials for access to Products and Services. "Authorized Users" are Customer's employees, full-time contractors engaged for the purpose of supporting the Products and Services that are not competitors of Motorola, and the entities (if any) specified in an Ordering Document or otherwise approved by Motorola in writing (email from an authorized Motorola signatory accepted), which may include affiliates or other Customer agencies. 2.8. Export Control. Customer, its employees, and any other Authorized Users will not access or use the Products and Services in anyjurisdiction in which the provision of such Products and Services is prohibited under applicable laws or regulations (a "Prohibited Jurisdiction"), and Customer will not provide access to the Products and Services to any government, entity, or individual located in a Prohibited Jurisdiction. Customer represents and warrants that (a) it and its Authorized Users are not named on any U.S. government list of persons prohibited from receiving U.S. exports, or transacting with any U.S. person; (b) it and its Authorized Users are not a national of, or a company registered in, any Prohibited Jurisdiction; (c) Customer will not permit its Authorized Users to access or use the Products or Services in violation of any U.S. or other applicable export embargoes, prohibitions or restrictions; and (d) Customer and its Authorized Users will comply with all applicable laws regarding the transmission of technical data exported from the U.S. and the country in which Customer, its employees, and the Authorized Users are located. 2.9. Change Orders. Unless a different change control process is agreed upon in writing by the Parties, a Party may request changes to an Addendum or an Ordering Document by submitting a change order to the other Party (each, a "Change Order"). If a requested change in a Change Order causes an increase or decrease in the Products or Services, the Parties by means of the Change Order will make appropriate adjustments to the Fees, project schedule, or other matters. Change Orders are effective and binding on the Parties only upon execution of the Change Order by an authorized representative of both Parties. 3. Term and Termination. 3.1. Term. The term of this MCA ("Term") will commence on the Effective Date and continue until six (6) months after the later of (a) the termination, expiration, or discontinuance of services under the last Ordering Document in effect, or (b) the expiration of all applicable warranty periods, unless the MCA is earlier terminated as set forth herein. The applicable Addendum or Ordering Document will set forth the term for the Products and Services governed thereby. 3.2. Termination. Either Party may terminate the Agreement or the applicable Addendum or Ordering Document if the other Party breaches a material obligation under the Agreement and does not cure such breach within thirty (30) days after receipt of notice of the breach or fails to produce a cure plan within such period of time. Each Addendum and Ordering Document may be separately terminable as set forth therein. 3.3. Suspension of Services. Motorola may terminate or suspend any Products or Services under an Ordering Document if Motorola determines: (a) the related Product license has expired or has terminated for any reason; (b) the applicable Product is being used on a hardware platform, operating system, or version not approved by Motorola; (c) Customer fails to make any payments when due; or (d) Customer fails to comply with any of its other obligations or otherwise delays Motorola's ability to perform. 3.4. Effect of Termination or Expiration. Upon termination for any reason or expiration of this Agreement, an Addendum, or an Ordering Document, Customer and the Authorized Users will return or destroy (at Motorola's option) all Motorola Materials and Motorola's Confidential DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Information in their possession or control and, as applicable, provide proof of such destruction, except that Equipment purchased by Customer should not be returned. If Customer has any outstanding payment obligations under this Agreement, Motorola may accelerate and declare all such obligations of Customer immediately due and payable by Customer. Notwithstanding the reason for termination or expiration, Customer must pay Motorola for Products and Services already delivered. Customer has a duty to mitigate any damages under this Agreement, including in the event of default by Motorola and Customer's termination of this Agreement. 4. Payment and Invoicing. 4.1. Fees. Fees and charges applicable to the Products and Services (the "Fees") will be as set forth in the applicable Addendum or Ordering Document, and such Fees may be changed by Motorola at any time, except that Motorola will not change the Fees for Products and Services purchased by Customer during the term of an active Ordering Document or during a Subscription Term (as defined and further described in the applicable Addendum). Changes in the scope of Services described in an Ordering Document may require an adjustment to the Fees due under such Ordering Document. If a specific invoicing or payment schedule is set forth in the applicable Addendum or Ordering Document, such schedule will apply solely with respect to such Addendum or Ordering Document. Unless otherwise specified in the applicable Ordering Document, the Fees for any Services exclude expenses associated with unusual and costly Site access requirements (e.g., if Site access requires a helicopter or other equipment), and Customer will reimburse Motorola for these or other expenses incurred by Motorola in connection with the Services. 4.2. Taxes. The Fees do not include any excise, sales, lease, use, property, or other taxes, assessments, duties, or regulatory charges or contribution requirements (collectively, "Taxes"), all of which will be paid by Customer, except as exempt by law, unless otherwise specified in an Ordering Document. If Motorola is required to pay any Taxes, Customer will reimburse Motorola for such Taxes (including any interest and penalties) within thirty (30) days after Customer's receipt of an invoice therefore. Customer will be solely responsible for reporting the Products for personal property tax purposes, and Motorola will be solely responsible for reporting taxes on its income and net worth. 4.3. Invoicing. Motorola will invoice Customer at the frequency set forth in the applicable Addendum or Ordering Document, and Customer will pay all invoices within thirty (30) days of the invoice date or as otherwise specified in the applicable Addendum or Ordering Document. Late payments will be subject to interest charges at the maximum rate permitted by law, commencing upon the due date. Motorola may invoice electronically via email, and Customer agrees to receive invoices via email at the email address set forth in an Ordering Document. Customer acknowledges and agrees that a purchase order or other notice to proceed is not required for payment for Products or Services. 5. Sites; Customer -Provided Equipment; Non -Motorola Content. 5.1. Access to Sites. Customer will be responsible for providing all necessary permits, licenses, and other approvals necessary for the installation and use of the Products and the performance of the Services at each applicable Site, including for Motorola to perform its obligations hereunder, and for facilitating Motorola's access to the Sites. No waivers of liability will be imposed on Motorola or its subcontractors by Customer or others at Customer facilities or other Sites, but if and to the extent any such waivers are imposed, the Parties agree such waivers are void. 5.2. Site Conditions. Customer will ensure that (a) all Sites are safe and secure, (b) Site conditions meet all applicable industry and legal standards (including standards promulgated by OSHA or other governmental or regulatory bodies), (c) to the extent applicable, Sites have adequate physical space, air conditioning, and other environmental conditions, electrical power DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 outlets, distribution, equipment, connections, and telephone or other communication lines (including modem access and interfacing networking capabilities), and (d) Sites are suitable for the installation, use, and maintenance of the Products and Services. 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. 5.3. Site Issues. Motorola will have the right at any time to inspect the Sites and advise Customer of any deficiencies or non -conformities with the requirements of this Section 5 — Sites; Customer -Provided Equipment; Non -Motorola Content. If Motorola or Customer identifies any deficiencies or non -conformities, Customer will promptly remediate such issues or the Parties will select a replacement Site. If a Party determines that a Site identified in an Ordering Document is not acceptable or desired, the Parties will cooperate to investigate the conditions and select a replacement Site or otherwise adjust the installation plans and specifications as necessary. A change in Site or adjustment to the installation plans and specifications may cause a change in the Fees or performance schedule under the applicable Ordering Document. 5.4. Customer -Provided Equipment. Certain components, including equipment and software, not provided by Motorola may be required for use of the Products and Services ("Customer -Provided Equipment"). Customer will be responsible, at its sole cost and expense, for providing and maintaining the Customer -Provided Equipment in good working order. Customer represents and warrants that it has all rights in Customer -Provided Equipment to permit Motorola to access and use the applicable Customer -Provided Equipment to provide the Products and Services under this Agreement, and such access and use will not violate any laws or infringe any third -party rights (including intellectual property rights). Customer (and not Motorola) will be fully liable for Customer -Provided Equipment, and Customer will immediately notify Motorola of any Customer -Provided Equipment damage, loss, change, or theft that may impact Motorola's ability to provide the Products and Services under this Agreement, and Customer acknowledges that any such events may cause a change in the Fees or performance schedule under the applicable Ordering Document. 5.5. Non -Motorola Content. In certain instances, Customer may be permitted to access, use, or integrate Customer or third -party software, services, content, and data that is not provided by Motorola (collectively, "Non -Motorola Content") with or through the Products and Services. If Customer accesses, uses, or integrates any Non -Motorola Content with the Products or Services, Customer will first obtain all necessary rights and licenses to permit Customer's and its Authorized Users' use of the Non -Motorola Content in connection with the Products and Services. Customer will also obtain the necessary rights for Motorola to use such Non -Motorola Content in connection with providing the Products and Services, including the right for Motorola to access, store, and process such Non -Motorola Content (e.g., in connection with Subscription Software), and to otherwise enable interoperation with the Products and Services. Customer represents and warrants that it will obtain the foregoing rights and licenses prior to accessing, using, or integrating the applicable Non -Motorola Content with the Products and Services, and that Customer and its Authorized Users will comply with any terms and conditions applicable to such Non -Motorola Content. If any Non -Motorola Content require access to Customer Data (as defined below), Customer hereby authorizes Motorola to allow the provider of such Non -Motorola Content to access Customer Data, in connection with the interoperation of such Non -Motorola Content with the Products and Services. Customer acknowledges and agrees that Motorola is not responsible for, and makes no representations or warranties with respect to, the Non -Motorola Content (including any disclosure, modification, or deletion of Customer Data resulting from use of Non - Motorola Content or failure to properly interoperate with the Products and Services). If Customer receives notice that any Non -Motorola Content must be removed, modified, or disabled within the Products or Services, Customer will promptly do so. Motorola will have the right to disable or remove Non -Motorola Content if Motorola believes a violation of law, third -party rights, or Motorola's policies is likely to occur, or if such Non -Motorola Content poses or may pose a security or other risk or adverse impact to the Products or Services, Motorola, Motorola's systems, or any DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 third party (including other Motorola customers). Nothing in this Section will limit the exclusions set forth in Section 7.2 — Intellectual Property Infringement. 6. Representations and Warranties. 6.1. Mutual Representations and Warranties. Each Party represents and warrants to the other Party that (a) it has the right to enter into the Agreement and perform its obligations hereunder, and (b) the Agreement will be binding on such Party. 6.2. Motorola Warranties. Subject to the disclaimers and exclusions below, Motorola represents and warrants that (a) Services will be provided in a good and workmanlike manner and will conform in all material respects to the descriptions in the applicable Ordering Document; and (b) for a period of ninety (90) days commencing upon the Service Completion Date for one- time Services, the Services will be free of material defects in materials and workmanship. Other than as set forth in subsection (a) above, recurring Services are not warranted but rather will be subject to the requirements of the applicable Addendum or Ordering Document. Motorola provides other express warranties for Motorola -manufactured Equipment, Motorola -owned software Products, and certain Services. Such express warranties are included in the applicable Addendum or Ordering Document. Such representations and warranties will apply only to the applicable Product or Service that is the subject of such Addendum or Ordering Document. 6.3. Warranty Claims; Remedies. To assert a warranty claim, Customer must notify Motorola in writing of the claim prior to the expiration of any warranty period set forth in this MCA or the applicable Addendum or Ordering Document. Unless a different remedy is otherwise expressly set forth for a particular warranty under an Addendum, upon receipt of such claim, Motorola will investigate the claim and use commercially reasonable efforts to repair or replace any confirmed materially non -conforming Product or re -perform any non -conforming Service, at its option. Such remedies are Customer's sole and exclusive remedies for Motorola's breach of a warranty. Motorola's warranties are extended by Motorola to Customer only, and are not assignable or transferrable. 6.4. Pass -Through Warranties. Notwithstanding any provision of this Agreement to the contrary, Motorola will have no liability for third -party software or hardware provided by Motorola; provided, however, that to the extent offered by third -party providers of software or hardware and to the extent permitted by law, Motorola will pass through express warranties provided by such third parties. 6.5. WARRANTY DISCLAIMER. EXCEPT FOR THE EXPRESS AND PASS THROUGH WARRANTIES IN THIS AGREEMENT, PRODUCTS AND SERVICES PURCHASED HEREUNDER ARE PROVIDED "AS IS" AND WITH ALL FAULTS. WARRANTIES SET FORTH IN THE AGREEMENT ARE THE COMPLETE WARRANTIES FOR THE PRODUCTS AND SERVICES AND MOTOROLA DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND QUALITY. MOTOROLA DOES NOT REPRESENT OR WARRANT THAT USE OF THE PRODUCTS AND SERVICES WILL BE UNINTERRUPTED, ERROR -FREE, OR FREE OF SECURITY VULNERABILITIES, OR THAT THEY WILL MEET CUSTOMER'S PARTICULAR REQUIREMENTS. 7. Indemnification. 7.1. General Indemnity. Motorola will defend, indemnify, and hold Customer harmless from and against any and all damages, losses, liabilities, and expenses (including reasonable fees and expenses of attorneys) arising from any actual third -party claim, demand, action, or proceeding ("Claim") for personal injury, death, or direct damage to tangible property to the extent caused by Motorola's negligence, gross negligence or willful misconduct while performing its duties under DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 an Ordering Document or an Addendum, except to the extent the claim arises from Customer's negligence or willful misconduct. Motorola's duties under this Section 7.1 — General Indemnity are conditioned upon: (a) Customer promptly notifying Motorola in writing of the Claim; (b) Motorola having sole control of the defense of the suit and all negotiations for its settlement or compromise; and (c) Customer cooperating with Motorola and, if requested by Motorola, providing reasonable assistance in the defense of the Claim. 7.2. Intellectual Property Infringement. Motorola will defend Customer against any third - party claim alleging that a Motorola -developed or manufactured Product or Service (the "Infringing Product") directly infringes a United States patent or copyright ("Infringement Claim"), and 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. Motorola's duties under this Section 7.2 — Intellectual Property Infringement are conditioned upon: (a) Customer promptly notifying Motorola in writing of the Infringement Claim; (b) Motorola having sole control of the defense of the suit and all negotiations for its settlement or compromise; and (c) Customer cooperating with Motorola and, if requested by Motorola, providing reasonable assistance in the defense of the Infringement Claim. 7.2.1. 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 Infringing Product; (b) replace or modify the Infringing Product so that it becomes non -infringing; or (c) grant Customer (i) a pro -rated refund of any amounts pre -paid for the Infringing Product (if the Infringing Product is a software Product, i.e., Licensed Software or Subscription Software) or (ii) a credit for the Infringing Product, less a reasonable charge for depreciation (if the Infringing Product is Equipment, including Equipment with embedded software). 7.2.2. In addition to the other damages disclaimed under this Agreement, Motorola will have no duty to defend or indemnify Customer for any Infringement Claim that arises from or is based upon: (a) Customer Data, Customer -Provided Equipment, Non -Motorola Content, or third -party equipment, hardware, software, data, or other third -party materials; (b) the combination of the Product or Service with any products or materials not provided by Motorola; (c) a Product or Service designed, modified, or manufactured in accordance with Customer's designs, specifications, guidelines or instructions; (d) a modification of the Product or Service by a party other than Motorola; (e) use of the Product or Service in a manner for which the Product or Service was not designed or that is inconsistent with the terms of this Agreement; or (f) the failure by Customer to use or install an update to the Product or Service that is intended to correct the claimed infringement. In no event will Motorola's liability resulting from an Infringement Claim extend in any way to any payments due on a royalty basis, other than a reasonable royalty based upon revenue derived by Motorola from Customer from sales or license of the Infringing Product. 7.2.3. This Section 7.2 — Intellectual Property Infringement provides Customer's sole and exclusive remedies and Motorola's entire liability in the event of an Infringement Claim. For clarity, the rights and remedies provided in this Section are subject to, and limited by, the restrictions set forth in Section 8 — Limitation of Liability below. 7.3. Customer Indemnity. To the extent provided by law and without waiving any sovereign immunity it may enjoy, Customer will defend, indemnify, and hold Motorola and its subcontractors, subsidiaries and other affiliates harmless from and against any and all damages, losses, liabilities, and expenses (including reasonable fees and expenses of attorneys) arising from any actual or threatened third -party claim, demand, action, or proceeding arising from or related to (a) Customer -Provided Equipment, Customer Data, or Non -Motorola Content, including any claim, demand, action, or proceeding alleging that any such equipment, data, or materials (or the integration or use thereof with the Products and Services) infringes or misappropriates a third - party intellectual property or other right, violates applicable law, or breaches the Agreement; (b) Customer -Provided Equipment's failure to meet the minimum requirements set forth in the DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 applicable Documentation or match the applicable specifications provided to Motorola by Customer in connection with the Products or Services; (c) Customer's (or its service providers, agents, employees, or Authorized User's) negligence or willful misconduct; and (d) Customer's or its Authorized User's breach of this Agreement. This indemnity will not apply to the extent any such claim is caused by Motorola's use of Customer -Provided Equipment, Customer Data, or Non -Motorola Content in violation of the Agreement. Motorola will give Customer prompt, written notice of any claim subject to the foregoing indemnity. Motorola will, at its own expense, cooperate with Customer in its defense or settlement of the claim. 8. Limitation of Liability. 8.1. DISCLAIMER OF CONSEQUENTIAL DAMAGES. EXCEPT FOR PERSONAL INJURY OR DEATH, MOTOROLA, ITS AFFILIATES, AND ITS AND THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, SUBCONTRACTORS, AGENTS, SUCCESSORS, AND ASSIGNS (COLLECTIVELY, THE "MOTOROLA PARTIES") WILL NOT BE LIABLE IN CONNECTION WITH THIS AGREEMENT (WHETHER UNDER MOTOROLA'S INDEMNITY OBLIGATIONS, A CAUSE OF ACTION FOR BREACH OF CONTRACT, UNDER TORT THEORY, OR OTHERWISE) FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES OR DAMAGES FOR LOST PROFITS OR REVENUES, EVEN IF MOTOROLA HAS BEEN ADVISED BY CUSTOMER OR ANY THIRD PARTY OF THE POSSIBILITY OF SUCH DAMAGES OR LOSSES AND WHETHER OR NOT SUCH DAMAGES OR LOSSES ARE FORESEEABLE. 8.2. DIRECT DAMAGES. EXCEPT FOR PERSONAL INJURY OR DEATH, THE TOTAL AGGREGATE LIABILITY OF THE MOTOROLA PARTIES, WHETHER BASED ON A CLAIM IN CONTRACT OR IN TORT, LAW OR EQUITY, RELATING TO OR ARISING OUT OF THE AGREEMENT WILL NOT EXCEED THE FEES SET FORTH IN THE ORDERING DOCUMENT UNDER WHICH THE CLAIM AROSE. NOTWITHSTANDING THE FOREGOING, FOR ANY SUBSCRIPTION SOFTWARE OR FOR ANY RECURRING SERVICES, THE MOTOROLA PARTIES' TOTAL LIABILITY FOR ALL CLAIMS RELATED TO SUCH PRODUCT OR RECURRING SERVICES IN THE AGGREGATE WILL NOT EXCEED THE TOTAL FEES PAID FOR SUCH SUBSCRIPTION SOFTWARE OR RECURRING SERVICE, AS APPLICABLE, DURING THE CONSECUTIVE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT FROM WHICH THE FIRST CLAIM AROSE. 8.3. ADDITIONAL EXCLUSIONS. NOTWITHSTANDING ANY OTHER PROVISION OF THISAGREEMENT, MOTOROLAWILL HAVE NO LIABILITY FOR DAMAGESARISING OUT OF (A) CUSTOMER DATA, INCLUDING ITS TRANSMISSION TO MOTOROLA, OR ANY OTHER DATA AVAILABLE THROUGH THE PRODUCTS OR SERVICES; (B) CUSTOMER -PROVIDED EQUIPMENT, NON-MOTOROLA CONTENT, THE SITES, OR THIRD -PARTY EQUIPMENT, HARDWARE, SOFTWARE, DATA, OR OTHER THIRD -PARTY MATERIALS, OR THE COMBINATION OF PRODUCTS AND SERVICES WITH ANY OF THE FOREGOING; (C) LOSS OF DATA OR HACKING, RANSOMWARE, OR OTHER THIRD -PARTY ATTACKS OR DEMANDS; (D) MODIFICATION OF PRODUCTS OR SERVICES BY ANY PERSON OTHER THAN MOTOROLA; (E) RECOMMENDATIONS PROVIDED IN CONNECTION WITH OR BYTHE PRODUCTS AND SERVICES; (F) DATA RECOVERY SERVICES OR DATABASE MODIFICATIONS; OR (G) CUSTOMER'S OR ANY AUTHORIZED USER'S BREACH OF THIS AGREEMENT OR MISUSE OF THE PRODUCTS AND SERVICES. 8.4. Voluntary Remedies. Motorola is not obligated to remedy, repair, replace, or refund the purchase price for the disclaimed issues in Section 8.3 — Additional Exclusions above, but if Motorola agrees to provide Services to help resolve such issues, Customer will reimburse Motorola for its reasonable time and expenses, including by paying Motorola any Fees set forth in an Ordering Document for such Services, if applicable. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 8.5. Statute of Limitations. Customer may not bring any claims against a Motorola Party in connection with this Agreement or the Products and Services more than one (1) year after the date of accrual of the cause of action. 9. Confidentiality. 9.1. Confidential Information. "Confidential Information" means any and all non-public information provided by one Party ("Discloser") to the other ("Recipient") that is disclosed under this Agreement in oral, written, graphic, machine recognizable, or sample form, being clearly designated, labeled or marked as confidential or its equivalent or that a reasonable businessperson would consider non-public and confidential by its nature. With respect to Motorola, Confidential Information will also include Products and Services, and Documentation, as well as any other information relating to the Products and Services. The nature and existence of this Agreement are considered Confidential Information of the Parties. In order to be considered Confidential Information, information that is disclosed orally must be identified as confidential at the time of disclosure and confirmed by Discloser by submitting a written document to Recipient within thirty (30) days after such disclosure. The written document must contain a summary of the Confidential Information disclosed with enough specificity for identification purpose and must be labeled or marked as confidential or its equivalent. 9.2. Obligations of Confidentiality. During the Term and for a period of three (3) years from the expiration or termination of this Agreement, Recipient will (a) not disclose Confidential Information to any third party, except as expressly permitted in this Section 9 - Confidentiality; (b) restrict disclosure of Confidential Information to only those employees (including, employees of any wholly owned subsidiary, a parent company, any other wholly owned subsidiaries of the same parent company), agents or consultants who must access the Confidential Information for the purpose of, and who are bound by confidentiality terms substantially similar to those in, this Agreement; (c) not copy, reproduce, reverse engineer, de -compile or disassemble any Confidential Information; (d) use the same degree of care as for its own information of like importance, but at least use reasonable care, in safeguarding against disclosure of Confidential Information; (e) promptly notify Discloser upon discovery of any unauthorized use or disclosure of the Confidential Information and take reasonable steps to regain possession of the Confidential Information and prevent further unauthorized actions or other breach of this Agreement; and (f) only use the Confidential Information as needed to fulfill its obligations and secure its rights under this Agreement. 9.3. Exceptions. Recipient is not obligated to maintain as confidential any information that Recipient can demonstrate by documentation (a) is publicly available at the time of disclosure or becomes available to the public without breach of this Agreement; (b) is lawfully obtained from a third party without a duty of confidentiality to Discloser; (c) is otherwise lawfully known to Recipient prior to such disclosure without a duty of confidentiality to Discloser; or (d) is independently developed by Recipient without the use of, or reference to, any of Discloser's Confidential Information or any breach of this Agreement. Additionally, Recipient may disclose Confidential Information to the extent required by law, including a judicial or legislative order or proceeding. 9.4. Ownership of Confidential Information. All Confidential Information is and will remain the property of Discloser and will not be copied or reproduced without the express written permission of Discloser (including as permitted herein). Within ten (10) days of receipt of Discloser's written request, Recipient will return or destroy all Confidential Information to Discloser along with all copies and portions thereof, or certify in writing that all such Confidential Information has been destroyed. However, Recipient may retain (a) one (1) archival copy of the Confidential Information for use only in case of a dispute concerning this Agreement and (b) Confidential Information that has been automatically stored in accordance with Recipient's standard backup or recordkeeping procedures, provided, however that Recipient will remain subject to the obligations of this Agreement with respect to any Confidential Information retained subject to DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 clauses (a) or (b). No license, express or implied, in the Confidential Information is granted to the Recipient other than to use the Confidential Information in the manner and to the extent authorized by this Agreement. Discloser represents and warrants that it is authorized to disclose any Confidential Information it discloses pursuant to this Agreement. 10. Proprietary Rights; Data; Feedback. 10.1. Data Definitions. The following terms will have the stated meanings: "Customer Contact Data" means data Motorola collects from Customer, its Authorized Users, and their end users for business contact purposes, including marketing, advertising, licensing and sales purposes; "Service Use Data" means data generated by Customer's use of the Products and Services or by Motorola's support of the Products and Services, including personal information, product performance and error information, activity logs and date and time of use; "Customer Data" means data, information, and content, including images, text, videos, documents, audio, telemetry, location and structured data base records, provided by, through, or on behalf of Customer, its Authorized Users, and their end users through the use of the Products and Services. Customer Data does not include Customer Contact Data, Service Use Data, or information from publicly available sources or other Third -Party Data or Motorola Data; "Third -Party Data" means information obtained by Motorola from publicly available sources or its third party content providers and made available to Customer through the Products or Services; "Motorola Data" means data owned or licensed by Motorola; "Feedback" means comments or information, in oral or written form, given to Motorola by Customer or Authorized Users, including their end users, in connection with or relating to the Products or Services; and "Process" or "Processing" means any operation or set of operations which is performed on personal information or on sets of personal information, whether or not by automated means, such as collection, recording, copying, analyzing, caching, organization, structuring, storage, adaptation, or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. 10.2. Motorola Materials. Customer acknowledges that Motorola may use or provide Customer with access to software, tools, data, and other materials, including designs, utilities, models, methodologies, systems, and specifications, which Motorola has developed or licensed from third parties (including any corrections, bug fixes, enhancements, updates, modifications, adaptations, translations, de -compilations, disassemblies, or derivative works of the foregoing, whether made by Motorola or another party) (collectively, "Motorola Materials"). The Products and Services, Motorola Data, Third -Party Data, and Documentation, are considered Motorola Materials. Except when Motorola has expressly transferred title or other interest to Customer by way of an Addendum or Ordering Document, the Motorola Materials are the property of Motorola or its licensors, and Motorola or its licensors retain all right, title and interest in and to the Motorola Materials (including, all rights in patents, copyrights, trademarks, trade names, trade secrets, know-how, other intellectual property and proprietary rights, and all associated goodwill and moral rights). For clarity, this Agreement does not grant to Customer any shared development rights in or to any Motorola Materials or other intellectual property, and Customer agrees to execute any documents and take any other actions reasonably requested by Motorola to effectuate the foregoing. Motorola and its licensors reserve all rights not expressly granted to Customer, and no rights, other than those expressly granted herein, are granted to Customer by implication, estoppel or otherwise. Customer will not modify, disassemble, reverse engineer, derive source code or create derivative works from, merge with other software, distribute, sublicense, sell, or export the Products and Services or other Motorola Materials, or permit any third party to do so. 10.3. Ownership of Customer Data. Customer retains all right, title and interest, including intellectual property rights, if any, in and to Customer Data. Motorola acquires no rights to Customer Data except those rights granted under this Agreement including the right to Process and use the Customer Data as set forth in Section 10.4 — Processing Customer Data below and in other applicable Addenda. The Parties agree that with regard to the Processing of personal DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 information which may be part of Customer Data, Customer is the controller and Motorola is the processor, and may engage sub -processors pursuant to Section 10.4.3 — Sub -processors. 10.4. Processing Customer Data. 10.4.1. Motorola Use of Customer Data. To the extent permitted by law, Customer grants Motorola and its subcontractors a right to use Customer Data and a royalty -free, worldwide, non- exclusive license to use Customer Data (including to process, host, cache, store, reproduce, copy, modify, combine, analyze, create derivative works from such Customer Data and to communicate, transmit, and distribute such Customer Data to third parties engaged by Motorola) to (a) perform Services and provide Products under the Agreement, (b) analyze the Customer Data to operate, maintain, manage, and improve Motorola Products and Services, and (c) create new products and services. Customer agrees that this Agreement, along with the Documentation, are Customer's complete and final documented instructions to Motorola for the processing of Customer Data. Any additional or alternate instructions must be agreed to according to the Change Order process. Customer represents and warrants to Motorola that Customer's instructions, including appointment of Motorola as a processor or sub -processor, have been authorized by the relevant controller. 10.4.2. Collection, Creation, Use of Customer Data. Customer further represents and warrants that the Customer Data, Customer's collection, creation, and use of the Customer Data (including in connection with Motorola's Products and Services), and Motorola's use of such Customer Data in accordance with the Agreement, will comply with all laws and will not violate any applicable privacy notices or infringe any third -party rights (including intellectual property and privacy rights). It is Customer's responsibility to obtain all required consents, provided all necessary notices, and meet any other applicable legal requirements with respect to collection and use (including Motorola's use) of the Customer Data as described in the Agreement. 10.4.3. Sub -processors. Customer agrees that Motorola may engage sub -processors who in turn may engage additional sub -processors to Process personal data in accordance with this Agreement. When engaging sub -processors, Motorola will enter into agreements with the sub - processors to bind them to data processing obligations to the extent required by law. 10.5. Data Retention and Deletion. Except as expressly provided otherwise under the Agreement, Motorola will delete all Customer Data following termination or expiration of this MCA or the applicable Addendum or Ordering Document, with such deletion to occur no later than ninety (90) days following the applicable date of termination or expiration, unless otherwise required to comply with applicable law. Any requests for the exportation or download of Customer Data must be made by Customer to Motorola in writing before expiration or termination, subject to Section 13.9 — Notices. Motorola will have no obligation to retain such Customer Data beyond expiration or termination unless the Customer has purchased extended storage from Motorola through a mutually executed Ordering Document. 10.6. Service Use Data. Customer understands and agrees that Motorola may collect and use Service Use Data for its own purposes, including the uses described below. Motorola may use Service Use Data to (a) operate, maintain, manage, and improve existing and create new products and services, (b) test products and services, (c) to aggregate Service Use Data and combine it with that of other users, and (d) to use anonymized or aggregated data for marketing, research or other business purposes. Service Use Data may be disclosed to third parties. It is Customer's responsibility to notify Authorized Users of Motorola's collection and use of Service Use Data and to obtain any required consents, provide all necessary notices, and meet any other applicable legal requirements with respect to such collection and use, and Customer represents and warrants to Motorola that it has complied and will continue to comply with this Section. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 10.7. Third -Party Data and Motorola Data. Motorola Data and Third -Party Data may be available to Customer through the Products and Services. Customer and its Authorized Users may use Motorola Data and Third -Party Data as permitted by Motorola and the applicable Third - Party Data provider, as described in the applicable Addendum. Unless expressly permitted in the applicable Addendum, Customer will not, and will ensure its Authorized Users will not: (a) use the Motorola Data or Third -Party Data for any purpose other than Customer's internal business purposes; (b) disclose the data to third parties; (c) "white label" such data or otherwise misrepresent its source or ownership, or resell, distribute, sublicense, or commercially exploit the data in any manner; (d) use such data in violation of applicable laws; (e) remove, obscure, alter, or falsify any marks or proprietary rights notices indicating the source, origin, or ownership of the data; or (f) modify such data or combine it with Customer Data or other data or use the data to build databases. Additional restrictions may be set forth in the applicable Addendum. Any rights granted to Customer or Authorized Users with respect to Motorola Data or Third -Party Data will immediately terminate upon termination or expiration of the applicable Addendum, Ordering Document, or this MCA. Further, Motorola or the applicable Third -Party Data provider may suspend, change, or terminate Customer's or any Authorized User's access to Motorola Data or Third -Party Data if Motorola or such Third -Party Data provider believes Customer's or the Authorized User's use of the data violates the Agreement, applicable law or Motorola's agreement with the applicable Third -Party Data provider. Upon termination of Customer's rights to use any Motorola Data or Third -Party Data, Customer and all Authorized Users will immediately discontinue use of such data, delete all copies of such data, and certify such deletion to Motorola. Notwithstanding any provision of the Agreement to the contrary, Motorola will have no liability for Third -Party Data or Motorola Data available through the Products and Services. Motorola and its Third -Party Data providers reserve all rights in and to Motorola Data and Third -Party Data not expressly granted in an Addendum or Ordering Document. 10.8. Feedback. Any Feedback provided by Customer is entirely voluntary, and will not create any confidentiality obligation for Motorola, even if designated as confidential by Customer. Motorola may use, reproduce, license, and otherwise distribute and exploit the Feedback without any obligation or payment to Customer or Authorized Users and Customer represents and warrants that it has obtained all necessary rights and consents to grant Motorola the foregoing rights. 10.9. Improvements; Products and Services. The Parties agree that, notwithstanding any provision of this MCA or the Agreement to the contrary, all fixes, modifications and improvements to the Services or Products conceived of or made by or on behalf of Motorola that are based either in whole or in part on the Feedback, Customer Data, or Service Use Data (or otherwise) are the exclusive property of Motorola and all right, title and interest in and to such fixes, modifications or improvements will vest solely in Motorola. Customer agrees to execute any written documents necessary to assign any intellectual property or other rights it may have in such fixes, modifications or improvements to Motorola. 11. Force Majeure; Delays Caused by Customer. 11.1. Force Majeure. Except for Customer's payment obligations hereunder, neither Party will be responsible for nonperformance or delayed performance due to events outside of its reasonable control. If performance will be significantly delayed, the affected Party will provide notice to the other Party, and the Parties will agree (in writing) upon a reasonable extension to any applicable performance schedule. 11.2. Delays Caused by Customer. Motorola's performance of the Products and Services will be excused for delays caused by Customer or its Authorized Users or subcontractors, or by failure of any assumptions set forth in this Agreement (including in any Addendum or Ordering Document). In the event of a delay under this Section 11.2 — Delays Caused by Customer, (a) Customer will continue to pay the Fees as required hereunder, (b) the Parties will agree (in writing) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 upon a reasonable extension to any applicable performance schedule, and (c) Customer will compensate Motorola for its out-of-pocket costs incurred due to the delay (including those incurred by Motorola's affiliates, vendors, and subcontractors). 12. Disputes. The Parties will use the following procedure to resolve any disputes relating to or arising out of this Agreement (each, a "Dispute"): 12.1. Governing Law. All matters relating to or arising out of the Agreement are governed by the laws of the State of Illinois, unless Customer is the United States Government (or an agency thereof) or a Florida municipality, in which case all matters relating to or arising out of the Agreement will be governed by the laws of the State in which the Products and Services are provided. The terms of the U.N. Convention on Contracts for the International Sale of Goods and the Uniform Computer Information Transactions Act will not apply. 12.2. Negotiation; Mediation. Either Party may initiate dispute resolution procedures by sending a notice of Dispute ("Notice of Dispute") to the other Party. The Parties will attempt to resolve the Dispute promptly through good faith negotiations, including 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). If a Dispute is not resolved through negotiation, either Party may initiate mediation by sending a notice of mediation ("Notice of Mediation") to the other Party. The Parties will choose an independent mediator within thirty (30) days of such Notice of Mediation. Neither Party may unreasonably withhold consent to the selection of a mediator, but if the Parties are unable to agree upon a mediator, either Party may request that the 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. All in person meetings under this Section 12.2 — Negotiation; Mediation will take place in Chicago, Illinois, and all communication relating to the Dispute resolution will be maintained in strict confidence by the Parties. Notwithstanding the foregoing, any Dispute arising from or relating to Motorola's intellectual property rights will not be subject to negotiation or mediation in accordance with this Section, but instead will be decided by a court of competent jurisdiction, in accordance with Section 12.3 — Litigation, Venue, Jurisdiction below. 12.3. Litigation, Venue, Jurisdiction. If the Dispute has not been resolved by mediation within sixty (60) days from the Notice of Mediation, either Party may submit the Dispute exclusively to a court in Lake County, Florida, Illinois. Each Party expressly consents to the exclusive jurisdiction of such courts for resolution of any Dispute and to enforce the outcome of any mediation. 13. General. 13.1. Compliance with Laws. Each Party will comply with applicable laws in connection with the performance of its obligations under this Agreement, including that Customer will ensure its and its Authorized Users' use of the Products and Services complies with law (including privacy laws), and Customer will obtain any FCC and other licenses or authorizations (including licenses or authorizations required by foreign regulatory bodies) required for its and its Authorized Users' use of the Products and Services. Motorola may, at its discretion, cease providing or otherwise modify Products and Services (or any terms related thereto in an Addendum or Ordering Document), in order to comply with any changes in applicable law. 13.2. Audit; Monitoring. Motorola will have the right to monitor and audit use of the Products, which may also include access by Motorola to Customer Data and Service Use Data. Customer will provide notice of such monitoring to its Authorized Users and obtain any required consents, including individual end users, and will cooperate with Motorola in any monitoring or audit. Customer will maintain during the Term, and for two (2) years thereafter, accurate records relating DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 to any software licenses granted under this Agreement to verify compliance with this Agreement. Motorola or a third party ("Auditor") may inspect Customer's and, as applicable, Authorized Users' premises, books, and records. Motorola will pay expenses and costs of the Auditor, unless Customer is found to be in violation of the terms of the Agreement, in which case Customer will be responsible for such expenses and costs. 13.3. Assignment and Subcontracting. Neither Party may assign or otherwise transfer this Agreement without the prior written approval of the other Party. Motorola may assign or otherwise transfer this Agreement or any of its rights or obligations under this Agreement without consent (a) for financing purposes, (b) in connection with a merger, acquisition or sale of all or substantially all of its assets, (c) as part of a corporate reorganization, or (d) to a subsidiary corporation. Subject to the foregoing, this Agreement will be binding upon the Parties and their respective successors and assigns. 13.4. Waiver. A delay or omission by either Party to exercise any right under this Agreement will not be construed to be a waiver of such right. A waiver by either Party of any of the obligations to be performed by the other, or any breach thereof, will not be construed to be a waiver of any succeeding breach or of any other obligation. All waivers must be in writing and signed by the Party waiving its rights. 13.5. Severability. If any provision of the Agreement is found by a court of competent jurisdiction to be invalid, illegal, or otherwise unenforceable, such provision will be deemed to be modified to reflect as nearly as possible the original intentions of the Parties in accordance with applicable law. The remaining provisions of this Agreement will not be affected, and each such provision will be valid and enforceable to the full extent permitted by applicable law. 13.6. 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. 13.7. Third -Party Beneficiaries. The Agreement is entered into solely between, and may be enforced only by, the Parties. Each Party intends that the Agreement will not benefit, or create any right or cause of action in or on behalf of, any entity other than the Parties. Notwithstanding the foregoing, a licensor or supplier of third -party software included in the software Products will be a direct and intended third -party beneficiary of this Agreement. 13.8. Interpretation. The section headings in this Agreement are included only for convenience The words "including" and "include" will be deemed to be followed by the phrase "without limitation". This Agreement will be fairly interpreted in accordance with its terms and conditions and not for or against either Party. 13.9. 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 provided by the other Party by certified mail, return receipt requested and postage prepaid (or by a recognized courier service, such as FedEx, UPS, or DHL), and will be effective upon receipt. 13.10. Cumulative Remedies. Except as specifically stated in this Agreement, all remedies provided for in this Agreement will be cumulative and in addition to, and not in lieu of, any other remedies available to either Party at law, in equity, by contract, or otherwise. Except as specifically stated in this Agreement, the election by a Party of any remedy provided for in this Agreement or otherwise available to such Party will not preclude such Party from pursuing any other remedies available to such Party at law, in equity, by contract, or otherwise. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 13.11. Survival. The following provisions will survive the expiration or termination of this Agreement for any reason: Section 2.4 — Customer Obligations; Section 3.4 — Effect of Termination or Expiration; Section 4 — Payment and Invoicing; Section 6.5 — Warranty Disclaimer; Section 7.3 — Customer Indemnity; Section 8 — Limitation of Liability; Section 9 — Confidentiality; Section 10 — Proprietary Rights; Data; Feedback; Section 11 — Force Majeure; Delays Caused by Customer; Section 12 — Disputes; and Section 13 — General. 13.12. Entire Agreement. This Agreement, including all Addenda and Ordering Documents, constitutes the entire agreement of the Parties regarding the subject matter hereto, 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, and will have the same legal force and effect as if the Parties had executed it as a single document. The Parties may sign in writing or by electronic signature. An electronic signature, facsimile copy, or computer image of a signature, will be treated, and will have the same effect as an original signature, and will 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 or part of this Agreement, even if a representative of each Party signs such document. The Parties hereby enter into this MCA as of the Effective Date. Moto ;J4gJ Viola Solutions, Inc. w� S� By: v OA86CDB3BAA44E9... Name: Daniel Sanchez Title: Territory vice President Date: 2/14/2022 City,of CUFmant By: j°jVicu�S Name: Brian Bulthuis Title: City Manager Date:2/18/2022 Equipment Purchase and Software License Addendum This Equipment Purchase and Software License Addendum (this "EPSLA") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and the entity set forth in the MCA ("Customer"), and will be subject to, and governed by, the terms of the Master Customer Agreement entered into between the Parties (the "MCA"). Capitalized terms used in this EPSLA, but not defined herein, will have the meanings set forth in the MCA. 1. Addendum. This EPSLA governs Customer's purchase of Equipment and license of Licensed Software (and, if set forth in an Ordering Document, related Services) from Motorola, and will form part of the Parties' Agreement. 2. Delivery of Equipment and Licensed Software. 2.1. Delivery and Risk of Loss. Motorola will provide to Customer the Products (and, if applicable, related Services) set forth in an Ordering Document, in accordance with the terms of the Agreement. Motorola will, using commercially reasonable practices, pack the ordered Equipment and ship such Equipment to the Customer address set forth in the applicable Ordering Document or otherwise provided by Customer in writing, using a carrier selected by Motorola. Notwithstanding the foregoing, delivery of Equipment (and any incorporated Licensed Software) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 will occur, and title and risk of loss for the Equipment will pass to Customer, upon shipment by Motorola in accordance with Ex Works, Motorola's premises (Incoterms 2020). Customer will pay all shipping costs, taxes, and other charges applicable to the shipment and import or export of the Products and Services, as applicable, and Customer will be responsible for reporting the Products for personal property tax purposes. Delivery of Licensed Software for installation on Equipment or Customer -Provided Equipment will occur upon the earlier of (a) electronic delivery of the Licensed Software by Motorola, and (b) the date Motorola otherwise makes the Licensed Software available for download by Customer. If agreed upon in an Ordering Document, Motorola will also provide Services related to such Products. 2.2. Delays. Any shipping dates set forth in an Ordering Document are approximate, and while Motorola will make reasonable efforts to ship Products by any such estimated shipping date, Motorola will not be liable for any delay or related damages to Customer. Time for delivery will not be of the essence, and delays will not constitute grounds for cancellation, penalties, termination, or a refund. 2.3. Beta Services. If Motorola makes any beta version of a software application ("Beta Service") available to Customer, Customer may choose to use such Beta Service at its own discretion, provided, however, that Customer will use the Beta Service solely for purposes of Customer's evaluation of such Beta Service, and for no other purpose. Customer acknowledges and agrees that all Beta Services are offered "as -is" and without any representations or warranties or other commitments or protections from Motorola. Motorola will determine the duration of the evaluation period for any Beta Service, in its sole discretion, and Motorola may discontinue any Beta Service at any time. Customer acknowledges that Beta Services, by their nature, have not been fully tested and may contain defects or deficiencies. 3. Licensed Software License and Restrictions. 3.1. Licensed Software License. Subject to Customer's and its Authorized Users' compliance with the Agreement (including payment terms), Motorola hereby grants Customer and its Authorized Users a limited, non -transferable, non-sublicenseable, and non-exclusive license to use the Licensed Software identified in an Ordering Document, in object code form only, and the associated Documentation, solely in connection with the Equipment provided by Motorola or authorized Customer -Provided Equipment (as applicable, the "Designated Products") and solely for Customer's internal business purposes. Unless otherwise stated in an Addendum or the Ordering Document, the foregoing license grant will be limited to the number of licenses set forth in the applicable Ordering Document and will continue for the life of the applicable Designated Product. Except as otherwise permitted in an applicable Addendum or Ordering Document, Customer may install, access, and use Licensed Software only in Customer's owned or controlled facilities, including any authorized mobile sites; provided, however, that Authorized Users using authorized mobile or handheld devices may also log into and access the Licensed Software remotely from any location. 3.2. Subscription License Model. If the Parties mutually agree that any Licensed Software purchased under this EPSLA will be replaced with or upgraded to Subscription Software, then upon such time which the Parties execute the applicable Ordering Document, the licenses granted under this EPSLA will automatically terminate, and such Subscription Software will be governed by the terms of the applicable Addendum under this Agreement. 3.3. End User Licenses. Notwithstanding any provision to the contrary in the Agreement, certain Licensed Software is governed by a separate license, EULA, or other agreement, including terms governing third -party equipment or software, such as open source software, included in the Products and Services. Customer will comply, and ensure its Authorized Users comply, with any such additional terms applicable to third -party equipment or software. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.4. Customer Restrictions. Customers and Authorized Users will comply with the applicable Documentation in connection with their use of the Products. Customer will not and will not allow others, including the Authorized Users, to: (a) make the Licensed Software available for use by unauthorized third parties, including via a commercial rental or sharing arrangement; (b) reverse engineer, disassemble, or reprogram the Licensed Software or any portion thereof to a human -readable form; (c) modify, create derivative works of, or merge the Licensed Software with other software or equipment; (d) copy, reproduce, distribute, lend, lease, or transfer the Licensed Software or Documentation for or to any third party without the prior express written permission of Motorola; (e) take any action that would cause the Licensed Software or Documentation to be placed in the public domain; (f) use the Licensed Software to compete with Motorola; or (g) remove, alter, or obscure, any copyright or other notice. 3.5. Copies. Customer may make one (1) copy of the Licensed Software solely for archival, back-up, or disaster recovery purposes during the term of the applicable Licensed Software license. Customer may make as many copies of the Documentation reasonably required for the internal use of the Licensed Software during such Licensed Software's license term. Unless otherwise authorized by Motorola in writing, Customer will not, and will not enable or allow any third party to: (a) install a licensed copy of the Licensed Software on more than one (1) unit of a Designated Product; or (b) copy onto or transfer Licensed Software installed in a unit of a Designated Product onto another device. Customer may temporarily transfer Licensed Software installed on a Designated Product to another device if the Designated Product is inoperable or malfunctioning, if Customer provides written notice to Motorola of the temporary transfer and identifies the device on which the Licensed is transferred. Temporary transfer of the Licensed Software to another device must be discontinued when the original Designated Product is returned to operation and the Licensed Software must be removed from the other device. Customer must provide prompt written notice to Motorola at the time temporary transfer is discontinued. 3.6. Resale of Equipment. Equipment contains embedded Licensed Software. If Customer desires to sell its used Equipment to a third party, Customer must first receive prior written authorization from Motorola and obtain written acceptance of the applicable Licensed Software license terms, including the obligation to pay relevant license fees, from such third party. 4. Term. 4.1. Term. The term of this EPSLA (the "EPSLA Term") will commence upon either (a) the Effective Date of the MCA, if this EPSLA is attached to the MCA as of such Effective Date, or (b) the EPSLA Date set forth on the signature page below, if this EPSLA is executed after the MCA Effective Date, and will continue until the later of (i) three (3) years after the first order for Products is placed via an Ordering Document, or (ii) the expiration of all applicable warranty periods (as set forth in Section 6.1 — Motorola Warranties below) under this EPSLA, unless this EPSLA or the Agreement is earlier terminated in accordance with the terms of the Agreement. 4.2. Termination. Notwithstanding the termination provisions of the MCA, Motorola may terminate this EPSLA (and any Ordering Documents hereunder) immediately upon notice to Customer if Customer breaches Section 3 — Licensed Software License and Restrictions of this EPSLA, or any other provision related to Licensed Software license scope or restrictions set forth in an Ordering Document, EULA, or other applicable Addendum. For clarity, upon termination or expiration of the EPSLA Term, all Motorola obligations under this EPSLA (including with respect to Equipment and Licensed Software delivered hereunder) will terminate. If Customer desires to purchase additional Services in connection with such Equipment or Licensed Software, Customer may enter into a separate Addendum with Motorola, governing such Services. Customer acknowledges that Motorola made a considerable investment of resources in the development, marketing, and distribution of the Licensed Software and Documentation, and that Customer's breach of the Agreement will result in irreparable harm to Motorola for which monetary DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 damages would be inadequate. If Licensee breaches this Agreement, in addition to termination, Motorola will be entitled to all available remedies at law or in equity, including immediate injunctive relief and repossession of all non -embedded Licensed Software and associated Documentation. 4.3. Equipment as a Service. In the event that Customer purchases any Equipment at a price below the MSRP for such Equipment in connection Customer entering into a fixed- or minimum required -term agreement for Subscription Software, and Customer or Motorola terminates the Agreement, this EPSLA, or other applicable Addendum (such as the Addendum governing the purchase of such Subscription Software) prior to the expiration of such fixed- or minimum required -term, then Motorola will have the right to invoice Customer for, and Customer will pay, the amount of the discount to the MSRP for the Equipment or such other amount set forth in the applicable Addendum or Ordering Document. This Section will not limit any other remedies Motorola may have with respect to an early termination. 5. Payment. Customer will pay invoices for the Products and Services provided under this EPSLA in accordance with the invoice payment terms set forth in the MCA. Generally, invoices are issued after shipment of Equipment or upon Motorola's delivery of Licensed Software (in accordance with Section 2.1 — Delivery and Risk of Loss), as applicable, but if a specific invoicing or payment schedule is set forth in the applicable Ordering Document, EULA or other Addendum, such schedule will control with respect to the applicable Products and Services referenced therein. Motorola will have the right to suspend future deliveries of Products and Services if Customer fails to make any payments when due. 6. Representations and Warranties; Liability. 6.1. Motorola Warranties. Subject to the disclaimers and exclusions set forth in the MCA and this EPSLA, (a) for a period of one (1) year commencing upon the delivery of Motorola - manufactured Equipment under Section 2.1 — Delivery and Risk of Loss, Motorola represents and warrants that such Motorola -manufactured Equipment, under normal use, will be free from material defects in materials and workmanship; (b) to the extent permitted by the providers of third -party software or hardware included in the Products and Services, Motorola will pass through to Customer any warranties provided by such third parties, which warranties will apply for the period defined by the applicable third party; and (c) for a period of ninety (90) days commencing upon the delivery of Motorola -owned Licensed Software under Section 2.1 — Delivery and Risk of Loss, Motorola represents and warrants that such Licensed Software, when used in accordance with the Documentation and the Agreement, will be free from reproducible defects that prevent operation of features critical to the primary functionality or successful operation of the Motorola -developed Licensed Software (as determined by Motorola). The warranty set forth in subsection (c) will be referred to as the "Motorola Licensed Software Warranty". As Customer's sole and exclusive remedy for any breach of the Motorola Licensed Software Warranty, Motorola will use commercially reasonable efforts to remedy the material defect in the applicable Licensed Software; provided, however, that if Motorola does not remedy such material defect within a reasonable time, then at Motorola's sole option, Motorola will either replace the defective Licensed Software with functionally -equivalent software, provide substitute software to Customer, or terminate the applicable software license and refund any paid license fees to Customer on a pro-rata basis. For clarity, the Motorola Licensed Software Warranty applies only to the most current version of the Licensed Software issued by Motorola, and issuance of updated versions of any Licensed Software does not result in a renewal or extension of the Motorola Licensed Software Warranty beyond the ninety (90) day warranty period. 6.2. ADDITIONAL EXCLUSIONS. IN ADDITION TO THE EXCLUSIONS FROM DAMAGES SET FORTH IN THE MCA, AND NOTWITHSTANDING ANY PROVISION OF THE AGREEMENT TO THE CONTRARY, MOTOROLA WILL HAVE NO LIABILITY FOR (A) DEFECTS IN OR DAMAGE TO PRODUCTS RESULTING FROM USE OTHER THAN IN THE NORMAL AUTHORIZED MANNER, OR FROM ACCIDENT, LIQUIDS, OR NEGLECT; (B) TESTING, DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 MAINTENANCE, REPAIR, INSTALLATION, OR MODIFICATION BY PARTIES OTHER THAN MOTOROLA; (C) CUSTOMER'S OR ANY AUTHORIZED USER'S FAILURE TO COMPLY WITH INDUSTRY AND OSHA OR OTHER LEGAL STANDARDS; (D) DAMAGE TO RADIO ANTENNAS, UNLESS CAUSED BY DEFECTS IN MATERIAL OR WORKMANSHIP; (E) EQUIPMENT WITH NO SERIAL NUMBER; (F) BATTERIES OR CONSUMABLES; (G) FREIGHT COSTS FOR SHIPMENT TO REPAIR DEPOTS; (H) COSMETIC DAMAGE THAT DOES NOT AFFECT OPERATION; (1) NORMAL WEAR AND TEAR; (J) ISSUES OR OBSOLESCENCE OF LICENSED SOFTWARE DUE TO CHANGES IN CUSTOMER OR AUTHORIZED USER REQUIREMENTS, EQUIPMENT, OR SYSTEMS; (K) TRACKING AND LOCATION -BASED SERVICES; OR (L) BETA SERVICES. 6.3. Voluntary Remedies. Motorola is not obligated to remedy, repair, replace, or refund the purchase price for the disclaimed or excluded issues in the MCA or Section 6.2 — Additional Exclusions above, but if Motorola agrees to provide Services to help resolve such issues, Customer will reimburse Motorola for its reasonable time and expenses, including by paying Motorola any Fees set forth in an Ordering Document for such Services, if applicable. 7. Copyright Notices. The existence of a copyright notice on any Licensed Software will not be construed as an admission or presumption of publication of the Licensed Software or public disclosure of any trade secrets associated with the Licensed Software. 8. Survival. The following provisions will survive the expiration or termination of this EPSLA for any reason: Section 3 — Licensed Software License and Restrictions; Section 4 — Term; Section 5 — Payment; Section 6.2 — Additional Exclusions; Section 8 — Survival. DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ar BROWARD COUNTY P25 SYSTEM AND SERVICES MASTER AGREEMENT WITH MOTOROLA SOLUTIONS, INC. This P25 System and Services Master Agreement (the "Agreement") is made and entered into by and between Broward County, a political subdivision of the State of Florida ("County"), and Motorola Solutions, Inc., a Delaware corporation registered to transact business in the State of Florida ("Provider" or "Motorola Solutions"). A. County issued solicitation RFP R1422515R1/P1 to provide a turnkey replacement of various communication subsystems operated by the County's Office of Regional Communications and Technology and integral to the public safety communications of Broward County and its municipalities. The RFP sought a new 700 MHz, P25 Phase II system to replace the County's existing 800 MHz SmartNet System, a new IP-based microwave system to replace the existing Tadiran 6 GHz system and providing backward compatibility for legacy circuits, civil work to support upgrades to new and existing radio sites, and P25 Phase II -compliant subscriber radios and maintenance available for purchase by entities in the Broward County public safety network. B. County has met the requirements of Section 287.055, Florida Statutes, the Consultants' Competitive Negotiation Act, and County's Design -Build competitive procurement regulations, and has selected Provider and its Subcontractors to perform the services hereunder. For good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties hereto agree as follows: ARTICLE 1. DEFINITIONS 1.1 Authorized Third Party Users. All persons and entities that County authorizes to use the P25 System, which may include employees and contractors of Broward County, Broward Sheriff's Office, Broward School District, municipalities, law enforcement, fire rescue, emergency management, transportation, non -government aid or relief organizations, and federal agencies. 1.2 Board. The Board of County Commissioners of Broward County, Florida. 1.3 Business hours or business day. 7 a.m. to 7 p.m. Eastern Time during weekdays that are not County holidays and on which County has not otherwise declared its offices closed. 1.4 Change Order. A written document ordering a change in the Design Build Price or Design Build Time or a material change in the Design Build Work. 1.5 Contract Administrator. The Director of Office of Regional Communications and Technology or other person as designated in writing by the Director of the Office of Regional Communications and Technology for all or portions of this Agreement and the Services provided hereunder. P25 System and Services Agreement (R1422515R1/P1) Page 1 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.6 County Consultant. Mission Critical Partners, Inc. or any other entity designated by the Contract Administrator as employed by or under contract to County for the providing of consulting services in connection with the preparation of the Specifications and oversight of the performance of this Agreement. 1.7 DB-Firm. The Subcontractor providing the design -related and civil work required for the Project or as otherwise required under the Facilities and Infrastructure SOW. As of the Effective Date, the DB-Firm is Amec Foster Wheeler. 1.8 DB-Firm's Consultant (Engineer of Record). A registered engineer who is employed by or has contracted with DB-Firm to provide professional services for the design, permitting, and construction related professional services of the Project and who is licensed by the State of Florida to provide said professional services. The DB-Firm Consultant as of the Effective Date is Carrick Contracting Corporation. 1.9 Design Build Contract Documents. Collectively, this Agreement and its exhibits, attachments and forms, the RFP R1422515R1/P1 and Addenda, and Provider's responses thereto (as negotiated and accepted by County); the Specifications; design plans, specifications, and drawings which are to be developed, signed, and sealed by DB-Firm's Consultant; the record of the contract award by the Board of County Commissioners; the Performance Bond and Payment Bond; the Notice(s) to Proceed; the Purchase Order; and all agreed upon contract and design modifications issued after execution of this Agreement. 1.10 Design Build Price. The amount established in the Agreement as the total contract price for the Project, as may be amended by Change Order. 1.11 Design Build Time. The original time between commencement and completion for the Facilities and Infrastructure Work, in accordance with Exhibit A-2 and the Project Schedule set forth in Schedule 10, including any milestone dates, as may be amended by Change Order. 1.12 Design Build Work. The totality of the obligations, including design and construction and other services required by the Design Build Contract Documents, whether completed or partially completed, including all labor, materials, equipment, and services provided or to be provided by DB-Firm or Provider to fulfill the obligations hereunder for the Project. 1.13 Documentation. All manuals, user documentation, specifications, and other related materials pertaining to any portion of the P25 System and other hardware and software that Provider or its Subcontractor customarily furnishes to purchasers of such hardware or software. "Documentation" includes product and software documents that specify 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.14 Equipment. The hardware and other property being provided to County pursuant to this Agreement, including equipment with which or for which the Software and Documentation is licensed, and including any embedded software and firmware incorporated therein or customarily provided by Provider to purchasers of such equipment. 1.15 Field Order. A written order which orders minor changes or interpretations of the Contract Documents but which does not involve an increase in the Design Build Price or change P25 System and Services Agreement (R1422515R1/P1) Page 2 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 in the Design Build Time. 1.16 Final Completion. The date certified by DB-Firm's Consultant, and as finally determined by the Contract Administrator with concurrence by the County Consultant, upon which all conditions and requirements of any permits and regulatory agencies have been satisfied; any documents required by the Design Build Contract Documents have been received bythe Contract Administrator; any other documents required to be provided by DB-Firm have been received by County; and the Design Build Work defined herein has been fully completed for the applicable Sites in accordance with the terms and conditions of the Design Build Contract Documents. 1.17 Open Source Software. Open Source Software is software with either freely obtainable source code, license for modification, or permission for free distribution. 1.18 Open Source Software License. The terms or conditions under which the Open Source Software is licensed by its copyright owner. 1.19 P25 System. All of the Software, Equipment, and other property identified in any Statement of Work, inclusive with all Services, being provided to County pursuant to this Agreement. The P25 System is comprised of three component systems: (1) the "Radio System," which constitutes the Software, Equipment and Services as stated in Exhibit A-1; (2) the Project, which constitutes the Design Build Work for the Facilities and Infrastructure system as stated in Exhibit A-2; and (3) the "Microwave System," which constitutes the Software, Equipment and Services as stated in Exhibit A-3. 1.20 Project. The design -build services to design, build, and install the necessary antenna towers, improvements, buildings, and other work as described in SOW A-2 or the Design Build Contract Documents. 1.21 Purchasing Director. The Broward County Director of Purchasing as appointed by the Broward County Administrator. 1.22 Security Vulnerability. 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.23 Services. All required installation, integration, programming, configuration, customization, and enhancements of the P25 System or any component System thereof, together with necessary and appropriate consulting, training, and project management services, to meet County's ongoing needs in connection with the P25 System, as further specified in the Statements of Work that comprise Exhibit A. 1.24 Sites. The sites included in this Project as identified in Exhibit A-2 and as updated or amended by Change Order. 1.25 Software. All proprietary or third -party software or other intellectual property rights, including the Documentation for same, provided or licensed to County or third party users pursuant to this Agreement, including the computer programs (in machine readable object code form) provided pursuant to this Agreement or listed in Exhibit A and any subsequent updates, upgrades, releases, or enhancements thereto developed by Provider during the term of this P25 System and Services Agreement (R1422515R1/P1) Page 3 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Agreement. "Software" includes software in object code format, and adaptations, translations, de -compilations, disassemblies, emulations, or derivative works of such software, and any modifications and new versions of the software provided pursuant to this Agreement, as well as any embedded software in the Equipment. 1.26 Specifications. The performance criteria developed by County Consultant that specifies the performance -based criteria for the P25 System or Project, including the description of work, standard specifications to be followed, technical requirements, management plans, Project schedule requirements, meetings and documentation requirements, design and survey requirements, provisions for utilities and coordination, permitting, maintenance -of -traffic, geotechnical investigations, environmental considerations, and construction operations, applicable to the Project or P25 System, as expressed in the RFP document, and include all implied requirements necessary to complete the Services and Design Build Work. 1.27 Subcontractor. A firm, partnership, corporation, independent contractor (including 1099 individuals), or combination thereof providing services to County through Provider for all or any portion of the Services or Project or who furnishes skills or materials worked into a special design according to the plans and specifications for such Services, but not those who merely furnish equipment or materials required by the plans and specifications. DB-Firm is included within the definition of Subcontractor. 1.28 Substantial Completion. That date, as certified by DB-Firm's Consultant and as finally determined by the Contract Administrator in its sole discretion, with concurrence from the County Consultant, the Design Build Work, or a portion thereof, is at a level of completion in substantial compliance with the Design Build Contract Documents such that all conditions of permits and regulatory agencies have been satisfied and County or its designee can enjoy use and operate it in all respects for its intended purpose. 1.29 Support and Maintenance Services. The maintenance and support required to maintain optimal performance of the applicable System as described in the Documentation and Exhibit C, as well as the support and maintenance services required for County to achieve and maintain optimal performance of the System. 1.30 Surety. The surety company or individual which is bound by the performance bond and payment bond with and for Provider who is primarily liable, and which surety company or individual is responsible for Provider's satisfactory performance of the Services and other work under the Agreement and for the payment of all debts pertaining thereto in accordance with Section 255.05, Florida Statutes, as applicable and as may be amended from time to time. ARTICLE 2. EXHIBITS AND SCHEDULES The following exhibits and schedules are attached hereto and incorporated into this Agreement: Exhibit A Statements of Work Exhibit A-1 Radio System SOW Exhibit A-2 Facilities and Infrastructure SOW Exhibit A-3 Microwave System SOW P25 System and Services Agreement (R1422515R1/P1) Page 4 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Exhibit A-4 Subscriber Equipment and Subscriber Equipment Maintenance Exhibit A-5 Optional Services Exhibit B Payment Schedule Exhibit C Support and Maintenance Services Exhibit D Insurance Coverages Exhibit E Work Authorization Form Exhibit F Additional Terms and Conditions for Project Exhibit G Subcontractor Schedule and CBE Letters of Intent Schedule 1 Software Schedule Schedule 2 Equipment Schedule Schedule 3 Training Plans Schedule 4 Spares Schedule 5 Interfaces and Alarms Schedule 6 Quality Control Plan Schedule 7 Block Diagrams Schedule 8 Specifications Schedule 9 Path Calculations and Profiles Schedule 10 Project Schedule If there is a conflict or inconsistency between any provision contained in Articles 1 - 14 and any provision contained in any of the Exhibits or Schedules, the provision of Articles 1-14 shall prevail and be given effect unless expressly stated to the contrary. ARTICLE 3. SCOPE OF SERVICES & SOFTWARE LICENSE 3.1 Scope of Services. Provider, either directly or through an authorized Subcontractor, shall complete all Services required in this Agreement inclusive of the Exhibits. Unless stated otherwise in this Agreement, the work required of Provider includes all labor, materials and tasks, whether or not enumerated in the Agreement, that are such an inseparable part of the work expressly stated in the Agreement that exclusion thereof would render Provider's performance impractical, illogical, or unconscionable. The Services required under this Agreement is inclusive of the Services required for all three separate system components: the Radio System, the Project, and the Microwave System. Provider shall be responsible for scheduling and coordinating each of the components, with the approval of the Contract Administrator, to ensure timely, complete, and proper implementation of each of the component Systems as well as the P25 System as a whole. 3.1.1 Radio Services. Provider or its Subcontractor shall perform all work set forth in the Radio Services SOW (Exhibit A-1) for the installation and implementation of the Radio System. Provider shall provide all services as set forth in this Agreement for the Radio System, including all necessary, incidental, and related activities and services required by the Radio SOW. P25 System and Services Agreement (R1422515R1/P1) Page 5 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.1.2 DB-Firm Services. Provider shall perform, directly or through the DB-Firm or other Subcontractor, all work set forth in the Facilities and Infrastructure SOW (Exhibit A-2) for the design, build, and installation for the Project. For all Services relating to the Project or required pursuant to the Facilities and Infrastructure SOW (Exhibit A-2), Provider and its Subcontractors, including the DB-Firm, shall comply with the Additional Terms and Conditions for Project attached as Exhibit F hereto. Provider shall ensure that its DB-Firm shall provide all services as set forth in this Agreement for the Project, including all necessary, incidental, and related activities and services required by the Facilities and Infrastructure SOW and implicit in the completion of the Project. 3.1.2.1 Structural Integrity. Provider and its DB-Firm shall perform all Design Build Work so as not to harm the structural integrity of any existing structure or infrastructure within the Project or at the Sites, and so as to conform to the standards set forth in Exhibit A-2. Provider shall repair and restore to its original condition any area of damage caused by Provider or its Subcontractor's performance under this Agreement. County or the County Consultant may review the work performed by DB-Firm and to direct DB-Firm to take certain corrective action if, in the opinion of the Contract Administrator or the County Consultant, the structural integrity of any existing structure or infrastructure within the Project or at any Site is or will be harmed. 3.1.2.2 Title of Work. Title to Design Build Work accepted by County under this Agreement shall vest in County. Ownership of the equipment and materials presently existing at the Sites at the time of execution of this Agreement shall remain the property of County, even if it is replaced or its operation made unnecessary by the Design Build Work. Title to the Equipment and risk of loss will pass to County upon written acceptance by County. Title to Software will not pass to County at any time. 3.1.2.3 Drawings and Material Lists. Where applicable, shop drawings, prepared, signed and sealed by the DB-Firm's Consultant, and equipment lists shall be submitted, including manufacturer supplied descriptive and technical literature. Manufacturer supplied descriptive and technical material (catalog cut sheets and performance charts) for new major equipment items shall also be submitted with the drawing package. The submitted shop drawings shall contain complete wiring and piping schematics and routing and any other details required to demonstrate the units are maintainable and will function as required in the complete system. 3.1.2.4 Lands for Work. County shall provide, as may be indicated in the Design Build Contract Documents, the Sites upon which the Design Build Work is to be performed, including rights -of -way and easements for access thereto, and such other lands as are designated by County for the use of Provider or its Subcontractor. Provider or its Subcontractor shall provide, at no expense to County and without liability to County, any additional land and access thereto that may be required for temporary construction facilities, or for storage of materials. Provider shall furnish to County copies of written permission obtained from the owners of such land. 3.1.3 Microwave Services. Provider or its Subcontractor shall perform all work set forth in the Microwave SOW (Exhibit A-3) for the installation and implementation of the Microwave P25 System and Services Agreement (R1422515R1/P1) Page 6 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 System. Provider shall provide all services as set forth in this Agreement for the Microwave System, including all necessary, incidental, and related activities and services required by the Microwave SOW. 3.2 Level of Effort. The Statements of Work do not delineate every detail and minor work task required to be performed by the Provider or its Subcontractor to complete the P25 System or its components. If, during the course of the performance of the Services, Provider determines that work should be performed to complete the P25 System or any component thereof, which in Provider's or its Subcontractor's opinion is outside the level of effort originally anticipated, whether or not the Statement of Work identifies the work items, Provider shall notify the Contract Administrator in writing in a timely manner before proceeding with the work. If Provider or its Subcontractor proceeds with said work without notifying the Contract Administrator, said work shall be deemed to be within the original level of effort, whether or not specifically addressed in the Statement of Work. Notice to the Contract Administrator does not constitute authorization or approval by County to perform the work. Performance of work outside the originally anticipated level of effort without prior written County approval is at Provider's sole risk. 3.3 Key Personnel. County's selection of Provider to perform the Services hereunder was based, in part, on the Subcontractors and specific personnel included in Provider's response to the County's solicitation. Provider's Subcontractors as identified in its response to the County's solicitation or as identified in this Agreement (inclusive of the applicable Statements of Work) shall not be changed without the prior written consent of the Contract Administrator. In the event Provider alters its relationship with the DB-Firm or DB-Firm alters its relationship with DB- Firm's Consultant without the prior written consent of the Contract Administrator, such occurrence shall be deemed an event of default and County may, in its discretion, terminate this Agreement in whole or as to any Statement of Work for cause herein. If Provider is granted written consent by the Contract Administrator to change any Subcontractor or the DB-Firm's Consultant, any delay costs associated with such change shall be borne by Provider. 3.4 Support and Maintenance Services. For so long as requested by County, Provider shall provide Support and Maintenance Services for the P25 System at the rates set forth in the Payment Schedule to ensure the proper functioning and optimal performance of the P25 System as set forth in the Documentation pursuant to the terms of Exhibit C. For the first year following Final Acceptance, all Support and Maintenance Services for the P25 System are included at no additional cost. For subsequent years, Support and Maintenance Services for the applicable System shall be invoiced and paid in accordance with the Payment Schedule set forth in Exhibit B. County may elect to suspend, discontinue, or recommence Support and Maintenance Services for the P25 System or for any or all of the component Systems upon thirty (30) days' prior notice, with the applicable fees prorated for the applicable term, without reinstatement or other penalty. 3.5 License. Subject to County's compliance with the license terms of use set forth in this Agreement, Provider grants to County a perpetual, royalty -free, nonexclusive license, with no P25 System and Services Agreement (R1422515R1/P1) Page 7 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 geographical limitations, for the number of users set forth in this Agreement (including any applicable Work Authorization), to all Software included in the P25 System, including to any software embedded in or provided with the Equipment, for use solely for governmental or other noncommercial purposes, including on- and off -site access and use of the System by Authorized Third Party Users, including those persons or entities with which County may contract to operate the P25 System or components thereof and the offices of the County constitutional officers. 3.5.1 Authorized Users and Additional Licenses. Unless otherwise stated in Exhibit A (Statement of Work) or Schedule 1, County and any of its employees, agents, suppliers of services, or other Authorized Third Party Users shall have the right to concurrently operate and use the P25 System. If anything less than unlimited, concurrent use is expressly provided under this Agreement and additional licenses are required, County's Purchasing Director is authorized to execute a Work Authorization to purchase additional licenses for the fee specified in the Payment Schedule. 3.5.2 Additional Uses. County may, if required by reason of an emergency, disaster or operational need, or for testing of recovery resources, temporarily use the Software on recovery resources at no additional cost, including recovery resources that may not be owned by County. County may, at no additional cost, copy the Software for backup and archiving purposes for the purposes of support or maintenance by County or others hired by County to provide such support or maintenance. County may, at no additional cost, utilize a hosted environment, including without limitation through a third -party hosting provider, for all otherwise permitted uses of the Softwa re. 3.5.3 Prohibited Uses. Except as otherwise provided for in this Agreement or required under Florida law, County shall not adapt, create derivative works, distribute, lease, lend, reproduce, publish, or license the Software to the general public or to third parties other than Authorized Third Party Users. County shall not modify, reverse engineer, disassemble, or decompile the Software or any portion thereof, except (a) to the extent expressly authorized in Exhibit A, in which event such authorized actions shall be deemed within the license grant of Section 3.5, or (b) to the extent permitted under any applicable open source license. County may not export the Software without complying with all applicable state and federal export laws. County will not transfer the Software to any third party (other than Authorized Third Party Users) without Motorola's prior written consent. 3.5.4 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 County under this Agreement by implication, estoppel or otherwise, except P25 System and Services Agreement (R1422515R1/P1) Page 8 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 for those rights which are expressly granted to County in this Agreement. All intellectual property developed, originated, or prepared by Motorola in connection with providing the Software, Equipment, Documentation or related services, remains vested exclusively in Motorola, and County will not have any shared development or other intellectual property rights. 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. 3.6 Updates, Upgrades and Releases. For the duration of this Agreement, Provider shall promptly provide to County, with advance notice and at no additional cost, any and all updates (including error corrections, bug fixes, security updates, and patches), upgrades, or new releases to the Software (as well as any firmware included with the Equipment), including all that Provider has made available to other licensees of all or part of the Software licensed pursuant hereto. All such updates, upgrades, and new releases shall remain the sole property of Provider and shall be deemed to be included within the scope of the license granted under this Agreement. 3.7 Compatibility. For the full term of this Agreement, Provider will ensure the continued compatibility of the Software and P25 System with all major releases, updates, or upgrades of any third party software used by County for access or operation of the P25 System. In the event Provider is not be able to support any third party software update, upgrade or new release that is not backwards compatible with the Software or the P25 System (or any component thereof), Provider shall use all reasonable efforts to resolve such issues and to provide optimal functionality of the Software and P25 System in accordance with this Agreement. If Provider is unable to provide continued optimal functionality of the Software and P25 System in accordance with this Agreement due to any applicable third party software release, update or upgrade, County shall be entitled to terminate the Agreement upon written notice with no further obligation to Provider. 3.8 Software Enhancements or Modifications. If requested by County and agreed to by Provider in an appropriate Work Authorization, Provider shall incorporate certain features and enhancements into the licensed Software. Any such request shall be formalized into a Statement of Work that shall define in detail the services to be performed, the financial terms, and the proposed project staffing and schedule. Any such Statement of Work shall be incorporated into a Work Authorization, to the extent permitted by Section 3.9 below, or otherwise into a proposed amendment to this Agreement. 3.9 Change of Scope Procedures. Provider acknowledges that Contract Administrator has no authority to make changes that would increase, decrease, or otherwise modify the scope of services to be provided under this Agreement, except as expressly provided herein. Contract Administrator may, from time to time, make changes to the Services or Design Build Work, including, but not limited to, the character and quantity of the Services or Design Build Work, as may be considered necessary or desirable in his or her sole discretion to complete fully and acceptably the proposed System or Design Build Work in a satisfactory manner. Provided such changes do not increase the cost to County, such changes may be documented between the Parties by execution of a Field Order or other writing in accordance with this Agreement (with P25 System and Services Agreement (R1422515R1/P1) Page 9 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 any decrease in charges to County credited against the next invoice, credited against other purchases with all applicable discounts and pricing incentives applied, or applied as the Parties otherwise agree). Unless otherwise expressly stated herein, any changes that increase cost to County must be documented by joint execution of a Change Order, Work Authorization, or amendment. Change Orders may only be used for the Project; Work Authorizations must be used for additional Services relating to the remainder of the P25 System. 3.9.1 Additional Services, Software or Equipment. To the extent any goods or services under this Agreement, or the quantity thereof, are identified as optional for County or set forth in SOW A-5 (collectively, "Optional Services"), County may select the type, amount, and timing of such goods or services pursuant to a Work Authorization executed by Provider and County pursuant to this Section, and provided that no such selection, when combined with those goods or services required under the Agreement, would result in a payment obligation exceeding the applicable maximum amount stated in Section 5.1. Notwithstanding anything to the contrary in the Agreement, Work Authorizations for Optional Services pursuant to this Section shall be executed on behalf of the County as follows: the Contract Administrator may execute Work Authorizations for which the cumulative total cost to County is less than $30,000.00; the Purchasing Director may execute Work Authorizations for which the cumulative total cost to the County is within the not -to -exceed amounts set forth in Section 5.1 (which amounts are acknowledged to be in excess of Purchasing Director's delegated authority under the Procurement Code, but are expressly authorized by the Board under this Agreement); any other Work Authorizations shall require Board approval. Subsequent to the full execution of any Work Authorization, the Contract Administrator will issue a Notice to Proceed for those authorized Optional Services. Provider shall not commence work on any Work Authorization until after receipt of the applicable Notice to Proceed. 3.9.2 Field Orders. The Contract Administrator shall have the right to approve and issue Field Orders setting forth written interpretations of the intent of the Design Build Contract Documents and ordering minor changes in Work execution, providing the Field Order involves no change in the Design Build Price or Design Build Time. 3.9.3 Change Orders. Changes in the quantity or character of the Design Build Work within the scope of the Project which are not properly the subject of Field Orders, including all changes resulting in changes in the Design Build Price or the Design Build Time, shall be authorized only by Change Orders approved in advance and issued in accordance with the provisions of the Broward County Procurement Code. Provider or DB-Firm shall not start work on any changes requiring an increase in the Design Build Price or the Design Build Time until a Change Order setting forth the adjustments is approved by the County. Upon receipt of a Change Order, Provider or DB-Firm shall promptly proceed with the Design Build Work set forth within the document. 3.9.4 In the event satisfactory adjustment cannot be reached for any item requiring a change in the Design Build Price or Design Build Time, and a Change Order has not been issued, County reserves the right at its sole option to either (a) terminate the Agreement as it applies to P25 System and Services Agreement (R1422515R1/P1) Page 10 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 the items in question and make such arrangements as may be deemed necessary to complete the disputed Design Build Work; or (b) submit the matter in dispute to County Administrator as set forth in Section 14.29 hereof. During the pendency of the dispute, and upon receipt of a Change Order approved by County, Provider and DB-Firm shall promptly proceed with the change in the Work involved and advise the Contract Administrator in writing within seven (7) calendar days of Provider's agreement or disagreement with the method, if any, provided in the Change Order for determining the proposed adjustment in the Design Build Price or Design Build Time. 3.9.5 On approval of any change increasing the Design Build Price, Provider shall ensure that the performance bond and payment bond are increased so that each reflects the Design Build Price as increased. 3.9.6 Under circumstances determined necessary by County, Change Orders may be issued unilaterally by County. 3.10 Value of Change Order Work. 3.10.1 The value of any Work covered by a Change Order or of any claim for an increase or decrease in the Design Build Price shall be determined in one of the following ways: 3.10.1.1 Where the Work involved is covered by unit prices contained in the Contract Documents, by application of unit prices to the quantities of items involved, subject to the provisions of Section 3.10.7. 3.10.1.2 By mutual acceptance of a lump sum which Provider and County acknowledge contains a component for overhead and profit. 3.10.1.3 On the basis of the "cost of work," determined as provided in Sections 3.10.2 and 3.10.3, plus a fee for overhead and profit which is determined as provided in Section 3.10.4. If and to the extent Provider claims that any of the data or calculations included in the calculation of the modification to the Design Build Price (or any other pricing calculation under this Agreement) constitutes a trade secret under Florida law, including Florida Statutes Section 812.081, Provider shall provide the information to County for determination of price in accordance with, but shall also follow the procedures set forth in Section 9.2 as to the trade secret designation of the information. 3.10.2 The term "cost of work" means the sum of all direct costs necessarily incurred and paid by DB-Firm in the proper performance of the Design Build Work described in the Change Order. Except as otherwise may be agreed to in writing by County, such costs shall be in amounts no higher than those prevailing in the locality of the Project, shall include only the following items, and shall not include any of the costs itemized in Section 3.10.3: P25 System and Services Agreement (R1422515R1/P1) Page 11 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.10.2.1 Payroll costs for employees in the direct employ of DB-Firm in the performance of the Design Build Work described in the Change Order under schedules of job classifications agreed upon by County and DB-Firm. Payroll costs for employees not employed full time on the Design Build Work covered by the Change Order shall be apportioned on the basis of their time spent on the Design Build Work. Payroll costs shall include, but not be limited to, salaries and wages plus the cost of fringe benefits which shall include social security contributions, unemployment, excise and payroll taxes, workers' compensation, health and retirement benefits, bonuses, sick leave, vacation and holiday pay application thereto. Such employees shall include superintendents and foremen at the site. The expenses of performing the Design Build Work after regular working hours, on Sunday or legal holidays, shall be included in the above to the extent authorized by County. 3.10.2.2 Cost of all materials and equipment furnished and incorporated in the Work, including costs of transportation and storage thereof, and manufacturers' field services required in connection therewith. All cash discounts shall accrue to DB-Firm unless County deposits funds with DB-Firm with which to make payments, in which case the cash discounts shall accrue to County. All trade discounts, rebates and refunds, and all returns from sale of surplus materials and equipment shall accrue to County, and DB- Firm shall make provisions so that they may be obtained. Rentals of all construction equipment and machinery and the parts thereof whether rented from DB-Firm or others in accordance with rental agreements approved by County and the costs of transportation, loading, unloading, installation, dismantling and removal thereof, all in accordance with the terms of said agreements. The rental of any such equipment, machinery or parts shall cease when the use thereof is no longer necessary for the Work. 3.10.2.3 Payments made to DB-Firm or other Subcontractors for work performed by Subcontractors. If required by County, DB-Firm shall obtain competitive bids from Subcontractors acceptable to DB-Firm and shall deliver such bids to County who will then determine which bids will be accepted. If the Subcontract provides that the Subcontractor is to be paid on the basis of cost of the work plus a fee, the Subcontractor's cost of the work shall be determined in the same manner as DB-Firm's cost of the work. All Subcontractors shall be subject to the other provisions of the Design Build Contract Documents insofar as applicable. 3.10.2.4 Supplemental costs including the following: 3.10.2.4.1 The proportion of necessary transportation, travel and subsistence expenses of DB-Firm's employees incurred in discharge of duties connected with the Work except for local travel to and from the site of the Design Build Work. 3.10.2.4.2 Cost, including transportation and maintenance, of all materials, supplies, equipment, machinery, appliances, office and temporary facilities P25 System and Services Agreement (R1422515R1/P1) Page 12 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 at the site and hand tools not owned by the workers, which are consumed in the performance of the Work, less market value of such items used but not consumed which remains the property of Provider or DB-Firm. 3.10.2.4.3 Sales, use, or similar taxes related to the Design Build Work, and for which DB-Firm is liable, imposed by any governmental authority. 3.10.2.4.4 Deposits lost for causes other than Provider's or DB-Firm's negligence; royalty payments and fees for permits and licenses. 3.10.2.4.5 The cost of utilities, fuel and sanitary facilities at the site. 3.10.2.4.6 Receipted minor expenses such as telegrams, long distance telephone calls, telephone service at the site, expressage and similar petty cash items in connection with the Work. 3.10.2.4.7 Cost of premiums for additional bonds and insurance required because of changes in the Work. 3.10.3 The term "cost of the work" shall not include any of the following: 3.10.3.1 Payroll costs and other compensation of Provider's or DB-Firm's officers, executives, principals (of partnership and sole proprietorships), general managers, engineers, architects, schedulers, estimators, lawyers, auditors, accountants, purchasing and contracting agents, expediters, timekeepers, clerks and other personnel employed by Provider or DB-Firm whether at the site or in its principal or a branch office for general administration of the Design Build Work are considered administrative costs covered by Provider's or DB-Firm's overhead. 3.10.3.2 Expenses of DB-Firm's principal and branch offices other than DB- Firm's office at the site. 3.10.3.3 Any part of DB-Firm's capital expenses, including interest on DB- Firm's capital employed for the Work and charges against DB-Firm for delinquent payments. 3.10.3.4 Cost of premiums for all bonds and for all insurance whether or not Provider or DB-Firm is required by the Design Build Contract Documents to purchase and maintain the same, except for additional bonds and insurance required because of the changes in the Design Build Work. 3.10.3.5 Costs due to the negligence or neglect of Provider or DB-Firm, any other Subcontractors, or anyone directly or indirectly employed by any of them or for whose acts any of them may be liable, including but not limited to, the correction of P25 System and Services Agreement (R1422515R1/P1) Page 13 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 defective Work, disposal of materials or equipment wrongly supplied and making good any damage to property. 3.10.3.6 Other overhead or general expense costs of any kind. 3.10.4 DB-Firm's fee allowed to DB-Firm for overhead and profit shall be determined as follows: 3.10.4.1 A mutually acceptable fixed fee; or 3.10.4.2 A fee based on the following percentages of the various portions of the cost of the work: For costs incurred under Sections 3.10.2.1 and 3.10.2.2, DB-Firm's fee shall not exceed ten percent (10%); For costs incurred under Section 3.10.2.3, DB- Firm's fee shall not exceed seven and one half percent (7.5%); and if a subcontract is on the basis of cost of the work plus a fee, the maximum allowable to the Subcontractor as a fee for overhead and profit shall not exceed ten percent (10%); and no fee shall be payable on the basis of costs itemized under Section 3.10.2.4 (except Section 3.10.2.4.3) and Section 3.10.3. 3.10.5 The amount of credit to be credited to County for any change which results in a net decrease in cost will be the amount of the actual net decrease. When both additions and credits are involved in any one change, the combined overhead and profit shall be figured on the basis of the net increase, if any; however, neither Provider nor DB-Firm shall be entitled to claim lost profits for any Design Build Work not performed. 3.10.6 Each Change Order must state within the body of the Change Order whether it is based upon unit price, negotiated lump sum, or "cost of the work." Provider will submit in a form acceptable to the Contract Administrator an itemized cost breakdown together with the supporting data. Breakdown shall list the quantities and unit prices for materials, labor, equipment and other items of cost. Whenever a change involves DB-Firm and one or more Subcontractors and the change is an increase in the Design Build Price, overhead and profit percentage for DB-Firm and each Subcontractor shall be itemized separately. 3.10.7 Where the quantity of any item of the Design Build Work that is covered by a unit price is increased or decreased by more than twenty percent (20%) from the quantity of such Design Build Work indicated in the Design Build Contract Documents, an appropriate Change Order shall be issued to adjust the unit price, if warranted. 3.10.8 Whenever a change in the Design Build Work is to be based on mutual acceptance of a lump sum, whether the amount is an addition, credit, or no change -in -cost, Provider shall submit an initial cost estimate acceptable to Contract Administrator. 3.11 Contract Administrator Authority. Unless otherwise expressly stated herein or in the applicable Procurement Code, Code of County Ordinances, or County Code of Administrative P25 System and Services Agreement (R1422515R1/P1) Page 14 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Procedure, the Contract Administrator may act on behalf of County to exercise the authority and powers of County under this Agreement. ARTICLE 4. TERM, TIME OF PERFORMANCE, ACCEPTANCE AND LIQUIDATED DAMAGES 4.1 Term. The Agreement shall become effective on the date it is fully executed by the parties (the "Effective Date"). The initial term of the Agreement shall be for a period of ten (10) years from the date of Final Acceptance (the "Initial Term"). 4.2 Extensions. County shall have the option to renew this Agreement for two (2) additional five-year terms (each an "Extension Term") by sending notice thereof to Provider at least thirty (30) days prior to the expiration of the then -current term. The Purchasing Director is authorized to exercise this renewal option. In the event that unusual or exceptional circumstances, as determined in the sole discretion of the Purchasing Director, render the exercise of an extension not practicable or if no extension is available, and expiration of this Agreement would result in a gap in the provision of services necessary for the ongoing operations of the County, then this Agreement may be extended on the same terms and conditions by the Purchasing Director for period(s) not to exceed six (6) months in the aggregate. 4.3 Fiscal Year. The continuation of this Agreement beyond the end of any County fiscal year shall be subject to both the appropriation and the availability of funds, in accordance with Chapter 129, Florida Statutes. 4.4 Time for Performance. Time is of the essence for all performance required under this Agreement. Prior to the commencement of Services under any Statement of Work, County Contract Administrator will issue a Purchase Order for the "P25 System Initial Purchase Order Amount" per Exhibit B and a Notice to Proceed for the relevant Services (including, to the extent set forth in the applicable Statement of Work, Notices to Proceed for each phase or subpart). Unless otherwise specified in the applicable Notice to Proceed, the applicable work to be performed pursuant to any Notice to Proceed shall commence within ten (10) calendar days of the issuance date of the Notice to Proceed. 4.4.1. Project Schedule. Provider and its Subcontractors shall complete the Services for each System, including the P25 System as a whole, within the time periods specified in the Project Schedule (Schedule 10) for the applicable System, including any modifications thereto approved in writing by the Contract Administrator. 4.4.2. County Responsibilities. The Contract Administrator or County Consultant, as applicable, shall reviewthe itemized deliverables and documents and respond in writing with any comment within the time set forth on the approved Project Schedule. The Contract Administrator or County Consultant shall give prompt written notice to Provider whenever the Contract Administrator observes or otherwise becomes aware of any development that affects the scope or timing of Provider's or DB-Firm's services or any defect in the work of Provider or DB-Firm. The Contract Administrator has the authority to stop the progress of the Services or P25 System and Services Agreement (R1422515R1/P1) Page 15 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Work whenever, in the opinion of the Contract Administrator, such stoppage is necessary to insure proper execution of the Services or Work or in an emergency affecting public safety, life, the integrity of the Services or Work, or adjoining property. 4.4.3. Facilities and Infrastructure Phases. The Project is organized into phases as detailed in Exhibit A-2. All design related documents prepared by DB-Firm should be sufficiently complete and comprehensive that they can be reviewed and approved by the Contract Administrator and County Consultant with an initial submittal and a re -submittal, if necessary. If DB-Firm requires additional review by the Contract Administrator and County Consultant beyond the first re -submittal, County may charge Provider for the invoice cost from County Consultant (if any), which amounts shall be reimbursed to County within thirty (30) days of receipt of billing from County or credited against the next invoice, as elected by County Contract Administrator. 4.4.3.1. Notices to Proceed. Neither Provider nor DB-Firm will commence work on any Site or Phase unless and until County Contract Administrator issues a Notice to Proceed for that particular Site or Phase. Provider and DB-Firm must obtain and notify County of receipt of all required permits as a condition precedent to the issuance of a Notice to Proceed for any physical construction work on any Site. No physical construction work shall commence on the Project site(s) until the issuance of the appropriate Notice to Proceed. 4.4.3.2. Substantial Completion. When Provider and DB-Firm consider that the Work at any Site has reached Substantial Completion, Provider shall notify, in writing, the Contract Administrator that the Site is ready for inspection. The Contract Administrator and County Consultant shall inspect the Work at that Site within thirty (30) calendar days of notice by Provider. When the Contract Administrator and County Consultant, on the basis of such an inspection, determine that the Design Build Work at the Site is substantially complete, the Contract Administrator will then prepare a Certificate of Substantial Completion. The Certificate of Substantial Completion for each Site shall state the responsibilities of County and Provider for security, maintenance, utilities, damage to the work, and insurance. The Contract Administrator shall develop and DB-Firm shall review the list of all Work yet to be completed at that Site (the "Punch List") to satisfy the requirements of the Contract Documents for Final Completion and to make the work conform and acceptable per the terms of this Agreement. The failure to include on the Punch List any items of corrective work does not alter the responsibility of Provider to complete all of the Design Build Work in accordance with the Design Build Contract Documents. The Certificate of Substantial Completion for each Site shall be executed by the Contract Administrator, Provider, DB-Firm, and DB-Firm's Consultant indicating acceptance of the responsibilities assigned to each in the Certificate. 4.5 Preliminary and Final Acceptance of each System. 4.5.1. Preliminary Acceptance of each System. Within thirty (30) days following completion of installation and integration of each System, including the Radio System and the Microwave System, County shall conduct Preliminary Acceptance testing of the applicable System. P25 System and Services Agreement (R1422515R1/P1) Page 16 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4.5.2. Final Acceptance of the P25 System. Within thirty (30) days following Preliminary Acceptance of all of the component System, including the Radio System and the Microwave System, as well as upon the County Contract Administrator's determination that each of the Sites required for the P25 System have achieved at least Substantial Completion, County shall conduct Final Acceptance testing of the P25 System. 4.5.3. Test Criteria. Both Preliminary Acceptance Testing and Final Acceptance Testing shall test the applicable System, with the assistance of its Enterprise Technology Services ("ETS") to the extent applicable under Broward County Administrative Code Section 22.148, to determine whether the System: (i) properly functions with any applicable operating software; (ii) provides the capabilities stated in this Agreement, the Documentation, and the applicable Specifications; and (iii) meets the Acceptance Criteria (if any) stated in the applicable Statement of Work or as otherwise agreed upon by the parties in writing. In the event of a conflict between the Acceptance Criteria and the Documentation, the Acceptance Criteria shall prevail. 4.5.4. Test Procedures. The testing period shall commence on the first business day after Provider informs County in writing that it has completed the Services required to be performed prior to testing and that the applicable System is ready for testing, and shall continue for a period of up to thirty (30) days. Unless otherwise set forth in the applicable Statement of Work, County shall notify Provider in writing of its Preliminary Acceptance, Final Acceptance, or rejection of the System, or any part thereof, within fifteen (15) days after the end of the testing period, as same may be extended or reset. If County rejects the applicable System, or any part thereof, County shall provide notice identifying the criteria for Preliminary Acceptance or Final Acceptance that the System failed to meet. Following such notice, Provider shall have thirty (30) days to (a) modify, repair, or replace the System or any portion thereof, or (b) otherwise respond to County's notice. If Provider modifies, repairs, or replaces the System or portion thereof, the testing period shall re -commence consistent with the procedures set forth above. In the event Provider fails to remedy the reason(s) for County's rejection of the System, or any part thereof, within ninety (90) days after County's initial notice of rejection, County may elect, in writing, to either accept the applicable System as it then exists or to reject the System. If County elects to reject the System, all sums paid by County for the applicable System shall be reimbursed to County by Provider within 15 days after such election is made. If County elects to accept the System as it then exists (partial acceptance), Provider shall continue to use its best efforts to remedy the items identified in the applicable notice of rejection for an additional period of time as approved by Contract Administrator. If, despite such continuing best efforts, Provider fails to remedy the issue(s) identified by County within a reasonable time as determined by County, then County shall be entitled to deduct from future sums due under the Agreement the value of the rejected portion of the System as mutually determined by the parties. If the parties cannot agree upon such value, County shall obtain a quotation from a third party for the price to remedy the items identified in the notice of rejection (or, if remedy is not commercially reasonable, to replace and provide a System that passes Final Acceptance testing) and Provider shall refund that amount to County within 15 days of notice of such rejection. P25 System and Services Agreement (R1422515R1/P1) Page 17 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4.6 Final Completion of the Design Build Work. Upon receipt of written notice from Provider stating that all items on the Punch List have been completed or corrected for every Site, the Contract Administrator and County Consultant shall promptly inspect the Design Build Work. Successful resolution of the Punch List for all Sites is a condition precedent to Final Completion of the Design Build Work. 4.6.1. As to each Site. Upon receipt of written notice from DB-Firm and DB-Firm's Consultant that the Site is ready for final inspection and stating that the requirements of the Contract Documents have been performed, the Contract Administrator and County Consultant shall, within thirty (30) calendar days, make an inspection thereof. If the Contract Administrator, with concurrence from County Consultant, finds the Design Build Work acceptable for that Site, the requisite documents have been submitted, the requirements of the Design Build Contract Documents have been fully satisfied for that Site, and all conditions of the permits and regulatory agencies have been met, a Certificate of Final Completion shall be issued by the Contract Administrator for that Site for execution by Provider, DB-Firm and DB-Firm's Consultant. 4.6.2. As to the last Site. Upon receipt of written notice from DB-Firm and DB-Firm's Consultant that the Design Build Work at the final Site is ready for final inspection and acceptance, stating that the requirements of the Contract Documents have been performed, including successful completion of the Burn -in Period, the Contract Administrator and County Consultant shall, within thirty (30) calendar days, make an inspection thereof. If the Contract Administrator, with concurrence from County Consultant, finds the Design Build Work acceptable, the requisite documents have been submitted, the requirements of the Design Build Contract Documents have been fully satisfied, and all conditions of the permits and regulatory agencies have been met, a Certificate of Final Completion of the Design Build Work and a Final Certificate of Payment shall be issued by the Contract Administrator for execution by Provider, DB-Firm and DB-Firm's Consultant. 4.6.3. Warranties for each Site as required by the Design Build Contract Documents shall commence on the date of Final Completion of the Work (i.e., Final Completion of all Sites). 4.6.4. Before issuance of the Final Certificate for Payment, DB-Firm shall deliver to the Contract Administrator: a complete release of all claims arising out of this Agreement, or receipts in full in lieu thereof; an affidavit certifying that all suppliers and subcontractors have been paid in full and that all other indebtedness connected with the Work has been paid, or a consent of the surety to final payment; the final corrected as -built drawings; and the final bill of materials, if required, and invoice. The final payment package is to include the certification document titled "Final List of Non -Certified Subcontractors and Suppliers" Form, which must be signed and notarized by DB-Firm. A list of all non -certified sub -vendors used must be attached to this certified document. 4.6.5. If, after the Work has been substantially completed, Final Completion of the Work is materially delayed through no fault of Provider or the DB-Firm, and Contract Administrator so certifies, County shall, and without terminating this Agreement, make payment of the balance P25 System and Services Agreement (R1422515R1/P1) Page 18 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 due for that portion of the Work fully completed and accepted. Such payment shall be made under the terms and conditions governing final payment, except that it shall not constitute a waiver of claims. 4.6.6. The acceptance of final payment shall constitute a waiver of all claims by DB-Firm, except those previously made in strict accordance with the provisions hereof and identified by DB-Firm as unsettled at the time of the application for final payment. 4.7 Liquidated Damages. Liquidated damages are hereby fixed and agreed upon between the Parties as set below, recognizing the impossibility of precisely ascertaining the amount of damages that will be sustained by County as a consequence of such delay, and both Parties desiring to obviate any question of dispute concerning the amount of said damages and the cost and effect of the failure of Provider to complete each System, the inability to continue to operate and maintain each Site, and the failure to complete the P25 System on time. These amounts are not penalties but liquidated damages to County for its inability to obtain full beneficial use of the P25 System. For purposes of this paragraph, any delays caused by County prior to Final Acceptance or Final Completion shall extend the deadline for the affected System(s) by the same number of days as the delay caused by County. The liquidated damages stated herein are cumulative, unless waived by County Contract Administrator, and shall be continuing until remedied. The total liquidated damages charged to Provider under this Section 4.7 shall not exceed ten percent (10%) of the System Total as set forth on Exhibit B. 4.7.1. Damages for Failure to Achieve Substantial Completion. Upon failure of Provider to achieve Substantial Completion of any Site within the time periods specified in the applicable Project Schedule (plus approved extensions, if any), Provider shall pay to County liquidated damages in the amount of $250 for each calendar day after the time specified in the Project Schedule. 4.7.2. Operation and Maintenance of Sites During Construction. Upon failure of Provider to meet the operating and maintenance criteria set forth in Exhibit A-2 for any Site, Provider shall pay to County liquidated damages in the amount as stated in Exhibit A-2 (if none stated, then the amount of $100) for each occurrence or series of occurrences of operating or maintenance failure. 4.7.3. Damages for Failure to Achieve Milestones or Final Acceptance. If any System fails to achieve the milestones stated below, Provider shall pay to County liquidated damages in the amount of $2,500 for each calendar day by which the date of the achievement of the applicable milestone exceeds the applicable deadline. 4.7.3.1. Completion of FNE installation at all RF Sites: August 30, 2018 4.7.3.2. Commencement of 30 Day Operational Test: November 21, 2018 4.7.3.3. P25 System Final Acceptance: December 31, 2018 P25 System and Services Agreement (R1422515R1/P1) Page 19 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4.7.4. Deduction from Amounts Otherwise Due. County is authorized to deduct any liquidated damages due under this Agreement from monies due Provider for Services or other work under this Agreement or as much thereof as County may, in its sole option and discretion, deem just and reasonable. 4.8 Delivery. Provider shall deliver the Software and Equipment for each System within the time stated in the applicable Statement of Work. Transportation cost and risk, and the cost of delivery, assembly and installation, including any applicable taxes and all actions necessary to integrate the Equipment into County's existing system, shall be the responsibility of Provider, except to the extent (if any) expressly provided in the applicable Statement of Work. 4.9 Use of Completed Portions. County shall have the right at its sole option to take possession of and use any completed or partially completed portions of the Project. Such possession and use shall not be deemed an acceptance of any of the Work not completed in accordance with the Design Build Contract Documents. If such possession and use increases the cost of or delays the Work, DB-Firm shall be entitled to reasonable extra compensation or reasonable extension of time or both, as recommended by Consultant and approved by County. 4.9.1. In the event County takes possession of any completed or partially completed portions of the Project, the following shall occur: 4.9.1.1. County shall give notice to DB-Firm in writing at least thirty (30) calendar days prior to County's intended occupancy of a designated area. 4.9.1.2. DB-Firm shall complete to the point of Substantial Completion the designated area and request inspection and issuance of a Certificate of Substantial Completion from DB-Firm and DB-Firm's Consultant. 4.9.1.3. Upon issuance of a Certificate of Substantial Completion by DB-Firm and DB-Firm's Consultant, County will assume full responsibility for maintenance, utilities, subsequent damages of County and public, adjustment of insurance coverages and start of warranty for the occupied area. 4.9.1.4. DB-Firm shall complete all items noted on the Certificate of Substantial Completion within the time specified by DB-Firm's Consultant on the Certificate of Substantial Completion, as soon as possible and request final inspection and final acceptance of the portion of the Work occupied. Upon completion of final inspection and receipt of an application for final payment, DB-Firm's Consultant shall issue a Final Certificate of Payment relative to the occupied area. 4.9.2. If County finds it necessary to occupy or use a portion or portions of the Work prior to Substantial Completion thereof, such occupancy or use shall not commence prior to a time mutually agreed upon by County and DB-Firm and to which the insurance company or companies providing the property insurance have consented by endorsement to the policy or policies. Insurance on the unoccupied or unused portion or portions shall not be canceled or P25 System and Services Agreement (R1422515R1/P1) Page 20 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 lapsed on account of such partial occupancy or use. Consent of DB-Firm and of the insurance company or companies to such occupancy or use shall not be unreasonably withheld. 4.10 Notification and Claim of Chanee of Desien Build Time or Desien Build Price. 4.10.1. Any claim for a change in the Design Build Time or Design Build Price shall be made by written notice delivered by Provider to the Contract Administrator within five (5) calendar days of the commencement of the event giving rise to the claim or knowledge by Provider or DB- Firm of the claim and the notice shall state the general nature and cause of the claim. Thereafter, within twenty (20) calendar days of the termination of the event giving rise to the claim or knowledge of the claim, written notice of the extent of the claim with supporting information and documentation shall be submitted to the Contract Administrator (hereinafter "Claim Notice"). The Claim Notice shall include Provider's or DB-Firm's written notarized certification that the adjustment claimed is the entire adjustment to which Provider or DB-Firm has reason to believe it is entitled as a result of the occurrence of said event. If the Contract Administrator and Provider cannot resolve a claim for changes in the Design Build Time or Design Build Price as set forth in a proper Claim Notice within twenty (20) calendar days after receipt by the Contract Administrator, then Provider shall submit the claim to County Administrator within five (5) calendar days from the date of impasse in accordance with Section 14.29. IT IS EXPRESSLY AND SPECIFICALLY AGREED THAT ANY AND ALL CLAIMS FOR CHANGES TO THE DESIGN BUILD TIME OR DESIGN BUILD PRICE SHALL BE WAIVED IF NOT SUBMITTED IN STRICT ACCORDANCE WITH THE REQUIREMENTS OF THIS SECTION. 4.10.2. The Design Build Time will be extended in an amount equal to time lost on critical Work items due to delays beyond the control of and through no fault or negligence of Provider or DB-Firm if a claim is made therefore as provided in Section 4.10.1. Such delays shall include, but not be limited to, acts or neglect by any separate contractor employed by County, fires, floods, labor disputes, epidemics, abnormal weather conditions, or acts of God. 4.11 No Damages for Delay. No claim for damages or any claim, other than for an extension of time, shall be made or asserted against County by reason of any delays except as provided herein. Provider or DB-Firm shall not be entitled to an increase in the Design Build Price or payment or compensation of any kind from County for direct, indirect, consequential, impact or other costs, expenses or damages, including, but not limited to, costs of acceleration or inefficiency, arising because of delay, disruption, interference or hindrance from any cause whatsoever, whether such delay, disruption, interference or hindrance be reasonable or unreasonable, foreseeable or unforeseeable, or avoidable or unavoidable; provided, however, that this provision shall not preclude recovery of damages by Provider or DB-Firm for actual delays due solely to fraud, bad faith or active interference on the part of County. Otherwise, Provider and DB-Firm shall be entitled only to extensions of the Design Build Time as the sole and exclusive remedy for such resulting delay, in accordance with and to the extent specifically provided above. P25 System and Services Agreement (R1422515R1/P1) Page 21 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4.12 Excusable Delay: Compensable and Non-Compensable. 4.12.1. Excusable Delay: Delay which extends the completion of the Work and which is caused by circumstances beyond the control of Provider or its Subcontractors is Excusable Delay. Provider is entitled to a time extension of the Design Build Time for each day the Work is delayed due to Excusable Delay. Provider shall document its claim for any time extensions as provided in Section 4.10 hereof. Failure of Provider to comply with Section 4.10 as to any particular event of delay shall be deemed conclusively to constitute a waiver, abandonment or relinquishment of any and all claims resulting from that particular event of delay. 4.12.2. Compensable Excusable Delay. Excusable Delay is only compensable when (i) the delay extends the Design Build Time, (ii) is caused by circumstances beyond the control of Provider or its Subcontractors, and (iii) is caused solely by fraud, bad faith, or active interference on the part of County or its agents. In no event shall Provider or DB-Firm be compensated for interim delays which do not extend the Design Build Time. Provider and DB-Firm shall only be entitled to direct costs for Compensable Excusable Delay. Direct costs recoverable by Provider or DB-Firm shall be limited to the actual additional costs allowed pursuant to Section 4.10 herein. 4.12.3. Non-Compensable Excusable Delay. When Excusable Delay is (i) caused by circumstances beyond the control of Provider or its Subcontractors, and is also caused by circumstances beyond the control of County, or (ii) is caused jointly or concurrently by Provider or its subcontractors, suppliers, or vendors and by County, then Provider shall be entitled only to a time extension and no further compensation for the delay. ARTICLE 5. COMPENSATION 5.1 For the duration of the Agreement, County will pay Provider in accordance with the Payment Schedule (Exhibit B) up to the following maximum amount(s): Services/Goods Term Not -To -Exceed Amount P25 System Implementation From Effective Date to $30,400,000 (including Radio System, Final Acceptance Microwave System, and Facilities and Infrastructure System) Additional Training Initial Term (10 years) $200,000 Support and Maintenance Initial Term (10 years) $11,000,000 Services Optional renewal terms First 5 year renewal term $7,100,000 (includes $100,000.00 for additional training) Second 5-year renewal $8,300,000 term (includes $100,000.00 for additional training) P25 System and Services Agreement (R1422515R1/P1) Page 22 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Services/Goods Term Not -To -Exceed Amount Optional Services Duration of the $2,500,000 Agreement (inclusive of any renewals) TOTAL NOT TO EXCEED $59,500,000 Payment shall be made only for work actually performed and completed pursuant to this Agreement or as otherwise set forth in Exhibit B (Payment Schedule), which amount shall be accepted by Provider as full compensation for all such work. Provider acknowledges that the amounts set forth herein are the maximum amounts payable for the respective terms and constitute a limitation upon County's obligation to compensate Provider for its work under this Agreement. These maximum amounts, however, do not constitute a limitation of any sort upon Provider's obligation to perform all items of work required under this Agreement. Unless otherwise expressly stated in this Agreement, Provider shall not be reimbursed for any expenses it incurs under this Agreement. 5.2 Method of Billing and Payment 5.2.1 Invoices. Provider may submit invoices only for goods provided and services completed in accordance with the Payment Schedule set forth in Exhibit B. Unless otherwise indicated in Exhibit B, an original plus one copy of each invoice must be submitted within fifteen (15) days after the end of the month for which payment is sought, except that the final invoice must be submitted no later than sixty (60) days after all services are completed. Provider shall submit with each invoice a Certification of Payments to Subcontractors and Suppliers on the form provided by County, as may be modified in County's reasonable discretion. If applicable, the certification shall be accompanied by a copy of the notification sent to each subcontractor and supplier listed in item 2 of the certification form, explaining the good cause why payment has not been made. Unless otherwise stated in Exhibit B or the applicable Work Authorization, any Optional Services shall be invoiced in accordance with the existing invoicing schedule for any like goods or services provided under this Agreement, including (if applicable) invoiced pro rata for the initial invoice period. 5.2.2 Payments. County shall pay Provider within thirty (30) days of receipt of Provider's proper invoice, as required by the "Broward County Prompt Payment Ordinance" (Broward County Ordinance No. 89-49). Payment shall be made to Provider at the most recent address designated under the "Notices" provision of this Agreement. To be deemed proper, an invoice must comply with all requirements set forth in this Agreement and must be submitted pursuant to any instructions prescribed by the Contract Administrator. County shall have the right to withhold payment of the invoice based on Provider's failure to comply with any term, condition, or requirement of this Agreement. The parties hereto agree that any amounts so withheld shall not be subject to payment of any interest by County. 5.2.3 Unless a shorter period is required under applicable law or under the applicable contract, Provider shall pay its CBE subcontractors and suppliers within fifteen (15) days following P25 System and Services Agreement (R1422515R1/P1) Page 23 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 receipt of payment from County and shall pay all other subcontractors and suppliers within thirty (30) days following receipt of payment from County. 5.2.4 County may withhold, in whole or in part, payment to such extent as may be necessary to protect itself from loss on account of: 5.2.4.1 Defective work not remedied; 5.2.4.2 Claims filed or reasonable evidence indicating probable filing of claims by other parties against Provider, DB-Firm or County because of Provider's or DB-Firm's performance; 5.2.4.3 Failure of Provider or DB-Firm to make payments properly to Subcontractors, or for material or labor; 5.2.4.4 Damage to another subcontractor not remedied; 5.2.4.5 Liquidated damages; 5.2.4.6 County Consultant fees for engineering review of subsequent re - submittal of design related documents beyond the first re -submittal; or 5.2.4.7 Failure of Provider or DB-Firm to provide any and all documents required by the Design Build Contract Documents. When the above grounds are removed, resolved, or settled to the satisfaction of the Contract Administrator, payment shall be made in whole or in part. 5.3 Permits, Licenses and Impact Fees. Provider shall secure and pay for all permits, licenses, and approvals necessary to construct the Project. Except as otherwise provided by the Design Build Contract Documents, all trade permits, sub -permits, and licenses required by federal, state, or local laws, rules and regulations necessary for the prosecution of the Work undertaken by Provider or any Subcontractor pursuant to this Agreement shall be secured and paid for by Provider or the Subcontractor. It is Provider's responsibility to have and maintain appropriate Certificate(s) of Competency, valid for the Work to be performed and valid for the jurisdiction in which the Work is to be performed for all persons working on the Project for whom a Certificate of Competency is required. Impact fees levied by any municipality shall be paid by Provider. Provider shall be reimbursed only for the actual amount of the impact fee levied by the municipality as evidenced by an invoice or other acceptable documentation issued by the municipality. In no event shall reimbursement to Provider in include profit or overhead of any Subcontractor. 5.4 Travel. With respect to travel costs and travel -related expenses, Provider and its Subcontractors shall adhere to Section 112.061, Florida Statutes, except to the extent, if any, that P25 System and Services Agreement (R1422515R1/P1) Page 24 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Exhibit B expressly provides to the contrary. County shall not be liable for any such expenses that have not been approved in advance, in writing, by County. 5.5 Fixed Pricing. Prices set forth in Exhibit B shall remain firm and fixed for the term of the Agreement, including any option terms. However, Provider may offer incentive or volume discounts to County at any time. 5.6 Other Eligible Purchasers. Municipalities, other County agencies, the Broward Sheriff's Office, other special districts within Broward County, or any Authorized Third Party User (collectively, each an "Eligible Purchaser") may purchase Subscriber Equipment or Subscriber Equipment Maintenance as set forth on Exhibit A-4 under the terms of this Agreement (other than Sections 12.4 through 12.8 relating to CBEs) at the pricing set forth on Exhibit A-4, provided that said Eligible Purchaser is solely responsible for all payment and performance with respect to any such purchased Subscriber Equipment or Subscriber Equipment Maintenance. County shall not be responsible for any costs, liabilities, charges, or services relating to Subscriber Equipment or Subscriber Equipment Maintenance that may be elected or purchased by Eligible Purchasers. ARTICLE 6. WARRANTIES 6.1 Ownership and License Rights. Provider represents and warrants that except as to third - party software licensed under this Agreement, Provider it is the owner of all right, title, and interest in and to the Equipment and other property being sold or provided to County under this Agreement, that it has the right to sell and provide such Equipment and other property to County, and that such sale is free and clear of any lien or interest of any other person or entity. Provider further represents and warrants that it has the right to grant to County the rights and the licenses granted under this Agreement as to the Software (including as to third party software licensed under this Agreement) and System. Provider warrants that it has not knowingly granted rights or licenses to any other person or entity that would restrict rights and licenses granted hereunder, except as may be expressly stated herein. 6.2 System Warranty. Provider represents and warrants to County that for a period of one (1) year from the date of Final Acceptance, the System will perform substantially as described in the Documentation and the Statement of Work (Exhibit A), will be free from defects in workmanship and material, and will have all of the qualities and features and be capable of performing all of the functions described in the Documentation and Statement of Work. This warranty shall not cover any failure of the System resulting from (a) use of the System in other than the manner for which it was intended; or (b) modification of the System by County not authorized by Provider. 6.3 Warranty Regarding Viruses. Provider further represents, warrants, and agrees that the System and any software or firmware provided under this Agreement are free from currently - known viruses or malicious software (at the time the System and any subsequent version thereof is provided to County), and that Provider has and will continue, for the full term of this Agreement, to use commercially reasonable security measures to ensure the integrity of such P25 System and Services Agreement (R1422515R1/P1) Page 25 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 software and firmware from data leaks, hackers, denial of service attacks, and other unauthorized intrusions. 6.4 Intellectual Property Warranty. Provider represents and warrants that at the time of entering into this Agreement, no claims that allege that any part of the System or other property provided to County under this Agreement infringes or misappropriates any patent, copyright, mask copyright, or any trade secret or other intellectual or proprietary right of a third party have been adjudicated adversely to Provider, and that Provider is unaware of any such potential or pending claim that is reasonably expected to impact County's ability to use the Software or System provided under this Agreement. Provider also agrees, represents and warrants that the P25 System (and all components thereof) and Services to be provided pursuant to this Agreement will not infringe or misappropriate any patent, copyright, mask copyright or any trade secret or other intellectual or proprietary right of a third party. If any Equipment, Software, or portion of the P25 System is finally adjudged to infringe, or in Provider's opinion is likely to become the subject of such a Claim, Provider shall, at County's option, either: (i) procure for County the right to continue using the applicable portion of the System; (ii) modify or replace the System (in part or in whole) to make it noninfringing; or (iii) refund to County all fees paid for the applicable System and for Services relating to that System under this Agreement. Provider shall have no liability regarding any infringement claim caused by any County modification of the System not authorized by Provider or the Documentation. 6.5 Quality of Performance and Materials. Provider represents and warrants that all services provided under this Agreement will be performed by a person duly qualified and sufficiently experienced to perform such services and, where required, licensed by all appropriate governmental authorities in the applicable area(s). Provider agrees that all services under this Agreement shall be performed in a skillful and respectful manner, and that the quality of all such services shall meet or exceed prevailing industry and professional standards for such services. Provider represents and warrants that all materials, Equipment, and products furnished pursuant to this Agreement shall be of good quality and free from defective or inferior workmanship. Provider warrants to County that all materials and equipment under this Agreement will be new unless otherwise specified and that all of the Work will be of good quality, free from faults and defects, and in conformance with the applicable requirements under this Agreement. All Work not conforming to these requirements, including substitutions not properly approved and authorized, may be considered defective. If required by the Contract Administrator, Provider shall furnish satisfactory evidence as to the kind and quality of materials and equipment. Any items found not to be in conformance with the foregoing and with the Documentation or applicable specifications (if any) in this Agreement shall be replaced by Provider at no additional cost to County. If requested by County's Contract Administrator, Provider shall develop and utilize a quality assurance plan approved by County to ensure the appropriate quality of the work and materials provided under this Agreement. P25 System and Services Agreement (R1422515R1/P1) Page 26 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6.6 Remedy for Breach of Warranty. In the event of written notice from County of a breach of warranty, Provider shall, at no charge to County, promptly correct the warranty breach including, when required, by (a) correcting, updating or replacing the Software, Equipment or Services, or (b) repairing the affected Equipment, or (c) providing to County other measures that correct the breach. In addition, upon notice from County of any warranty breach or other error or defect in the P25 System, Provider will immediately provide to County any known reasonable methods of operating the System in a manner that eliminates the adverse effects of the error or defect. If Provider is unable to correct a material breach of this Article within a reasonable period of time not to exceed ten (10) business days, County shall be entitled to cancel the Agreement as to the applicable nonconforming Software, Equipment, or Services, and receive a full refund of all amounts paid to Provider for the nonconforming portion of the Systems) (including any other portion of the applicable System(s) for which functionality is adversely affected by the nonconformance and all amounts paid for Services relating thereto), and Provider shall arrange for the removal and return of the applicable Equipment at Provider's expense. In the event of replacement of any of the Software, Equipment or Services, the replacement Software, Equipment or Services will be warranted as provided above from the date of replacement. The remedies in this Section are in addition to any other rights and remedies County may have under this Agreement or applicable law. 6.7 Additional Rights as to Defective Work. In addition to the foregoing, the Contract Administrator shall have the authority to reject or disapprove Work which it finds to be defective. If required by the Contract Administrator, Provider shall promptly either correct all defective work or remove such defective work and replace it with non -defective work. Provider shall bear all direct, indirect, and consequential costs of such removal or corrections including cost of testing laboratories and personnel. Should Provider fail or refuse to remove or correct any defective work or to make any necessary repairs in accordance with the requirements of the Design Build Contract Documents within the time indicated in writing by the Contract Administrator, County shall have the authority to cause the defective work to be removed or corrected, or make such repairs as may be necessary at Provider's expense. Any expense incurred by County in making such removals, corrections, or repairs, shall be paid for out of any monies due or which may become due to Provider, or may be charged against the Performance Bond. In the event of failure of Provider to make all necessary repairs promptly and fully, County may declare Provider in default. If, within one (1) year after the date of Final Completion of the each Site, or such longer period of time as may be prescribed by the terms of any applicable special warranty required by the Contract Documents, or by any specific provision of the Design Build Contract Documents, any of the Work is found to be defective or not in accordance with the Design Build Contract Documents, Provider, after receipt of written notice from County, shall promptly correct such defective or nonconforming Work within the time specified by County, without cost to County to do so. Nothing contained herein shall be construed to establish a period of limitation with respect to any other obligation which Provider might have under the Design Build Contract Documents, including, but not limited to, any claim regarding latent defects. Failure to reject any defective P25 System and Services Agreement (R1422515R1/P1) Page 27 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 work or material shall not in any way prevent later rejection when such defect is discovered, or obligate County to Final Acceptance. ARTICLE 7. DELIVERY, DOCUMENTATION AND PERFORMANCE AND PAYMENT BOND 7.1 Software. Unless otherwise stated in Exhibit A, Provider shall, within seven (7) days after the Effective Date, make the Software available to County and, unless the Software is embedded in equipment, deliver to County a master copy of the Software licensed hereunder in object code form, suitable for reproduction in accordance with this Agreement, in electronic files unless otherwise requested by County. All County license keys, usernames, and passwords shall be authenticated by Provider and perform according to Exhibit A (Statement of Work). 7.2 Documentation. Provider shall deliver copies of the Documentation to County concurrently with delivery of the applicable Equipment and Software, and thereafter shall promptly provide any updated Documentation as it becomes available during the term of this Agreement. Provider represents and warrants that the Documentation is sufficiently comprehensive and of sufficient quality to enable a competent user to operate the applicable portions of the System efficiently and in accordance with Exhibit A. County has the right to copy and modify the Documentation as it deems necessary for its own internal use. 7.3 Performance and Payment Bond. Within fifteen (15) calendar days of the Effective Date of this Agreement, Provider shall furnish a Performance and Payment Bond containing all the provisions of the Performance Bond and Payment Bond Forms attached to this Agreement. 7.3.1 Each Bond shall be in the amount of one hundred percent (100%) of the total amount of the Agreement (excluding Optional Services and Support and Maintenance) guaranteeing to County the completion and performance of the Work covered in this Agreement as well as full payment of all suppliers, laborers, or subcontractors employed pursuant to this Project. Each Bond shall be with a surety company which is qualified pursuant to Section 7.5. Each bond shall be increased in the amount of any change to the total amount paid under the Agreement (excluding Optional Services and Support and Maintenance). 7.3.2 The value of each bond shall be reduced as the one (1) year warranty period expires for each Site, to correspond in value to one hundred percent (100%) of the Construction Cost of the remaining Sites, or an additional bond shall be conditioned that Provider will, upon notification by County, correct any defective or faulty work or materials which appear within one (1) year after Final Completion of each Site. 7.3.3 Pursuant to the requirements of Section 255.05(1)(a), Florida Statutes, Provider shall ensure that the bond(s) referenced above shall be recorded in the public records of Broward County and provide County with evidence of such recording. 7.4 Alternate form of Security: In lieu of a Performance and a Payment Bond, Provider may furnish alternate forms of security which may be in the form of cash, money order, certified P25 System and Services Agreement (R1422515R1/P1) Page 28 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 check, cashier's check, or unconditional letter of credit. Such alternate forms of security shall be subject to the approval of County and for same purpose and shall be subject to the same conditions as those applicable above and shall be held by County for one (1) year after Final Completion and acceptance of the last remaining Site. 7.5 Qualifications of Surety. Each bond must be executed by a surety company of recognized standing, authorized to do business in the State of Florida as surety, having a resident agent in the State of Florida, and having been in business with a record of successful continuous operation for at least five (5) years. The surety company shall hold a current certificate of authority as acceptable surety on federal bonds in accordance with United States Department of Treasury Circular 570, Current Revisions. If the amount of the Bond exceeds the underwriting limitation set forth in the circular, in order to qualify, the net retention of the surety company shall not exceed the underwriting limitation in the circular, and the excess risks must be protected by coinsurance, reinsurance, or other methods in accordance with Treasury Circular 297, revised September 1, 1978 (31 CFR Section 223.10, Section 223.111). Further, the surety company shall provide County with evidence satisfactory to County, that such excess risk has been protected in an acceptable manner. County will accept a surety bond from a company in accordance with the requirements set forth below, provided, however, that if any surety company appears on the watch list that is published quarterly by Intercom of the Office of the Florida Insurance Commissioner, County shall review and either accept or reject the surety company based on the financial information available to County. A surety company that is rejected by County may be substituted by Provider with a surety company acceptable to County, only if the Agreement price does not increase. The following sets forth, in general, the acceptable parameters for bonds: Amount of Bond Policy Holder's Ratings Financial Size Category 500,001 to 1,000,000 A, A- Class I 1,000,001 to 2,000,000 A ,A- Class 11 2,000,001 to 5,000,000 A Class III 5,000,001 to 10,000,000 A Class IV 10,000,001 to 25,000,000 A Class V 25,000,001 to 50,000,000 A Class VI 50,000,001 or more A Class VII ARTICLE 8. PROTECTION OF SOFTWARE AND PROPRIETARY RIGHTS 8.1 County Proprietary Rights. Provider acknowledges and agrees that County retains all rights, title and interest in and to all materials, data, documentation and copies thereof furnished by County to Provider hereunder, including all copyright and other proprietary rights therein, which Provider as well as its employees, agents, Subcontractors, and suppliers may use only in connection with the performance of Services or Support and Maintenance Services under this P25 System and Services Agreement (R1422515R1/P1) Page 29 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Agreement. Motorola, the third party manufacturer of any Equipment, and the copyright owner of any third -party Software own and retain all of their respective proprietary rights in the Equipment and Software. All intellectual property developed, originated, or prepared by Motorola in connection with providing the Equipment, Software, or Services under this Agreement remain vested exclusively in Motorola or the applicable third party manufacturer or licensor, and this Agreement does not grant County any shared development rights of intellectual property or source code. 8.2 Ownership. Except for custom work products, if any, County acknowledges that all copies of the Software (in any form) provided by Provider are the sole property of Provider or the applicable third -party licensor. County shall not have any right, title, or interest to any such Software or copies thereof except as expressly provided in this Agreement, and shall take all reasonable steps to secure and protect all Software consistent with maintenance of Provider's proprietary rights therein. 8.3 Custom Work Products. To the extent this Agreement (including in the Statement of Work, any subsequent Work Authorization, any amendment, or the procurement documents relating to this Agreement) expressly identifies any deliverables as custom work products that Provider is to develop and furnish, the parties agree that County shall own all rights, title, and interest in and to all such custom work products and that they shall be deemed to constitute "works made for hire" under the United States Copyright Act, 17 U.S.C. § 101. If, for any reason, any custom work product would not be considered a "work made for hire" under applicable law, Provider hereby exclusively and irrevocably sells, assigns, and transfers to County all of Provider's rights, title, and interest in and to such custom work product and in and to any copyright or copyright application(s) related thereto. Provider agrees that neither it nor its agents shall use or disclose any custom work product except for County's benefit as required in connection with Provider's performance under this Agreement, unless Provider has obtained County's prior written consent to such use or disclosure. "Custom work product" shall not include any software, copyrighted material, or other proprietary material developed by Provider or any third party prior to the Effective Date, but shall include any modification(s) thereof developed pursuant to this Agreement. To the full extent applicable, Provider shall provide County with the source code and object code for all custom work products upon Final Acceptance of the Software or System, or within thirty (30) calendar days after written request by the Contract Administrator, whichever occurs first. ARTICLE 9. CONFIDENTIAL INFORMATION, SECURITY AND ACCESS 9.1 Public Records Law. As a political subdivision of the State of Florida, County is subject to Florida's Public Records Law, Chapter 119 of the Florida Statutes. Notwithstanding anything else in this Agreement, any action taken by County in compliance with, or in a good faith attempt to comply with, the requirements of Chapter 119 shall not constitute a breach of this Agreement. 9.2 Provider Confidential Information. Provider represents that the Software contains proprietary products and trade secrets of Provider. Any other material submitted to County by P25 System and Services Agreement (R1422515R1/P1) Page 30 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Provider that Provider represents constitutes or contains trade secrets or is otherwise exempt from production under Florida public records laws (including Florida Statutes Chapter 119) must be segregated and conspicuously labeled "EXEMPT FROM PUBLIC RECORD PRODUCT — TRADE SECRET." Provider's Software and properly designated trade secret materials constitute "Provider Confidential Information." To the full extent permissible under applicable law, County agrees to treat Provider Confidential Information as confidential in accordance with this Section unless otherwise ordered by a court of competent jurisdiction. Provider must, simultaneous with the production of any Provider Confidential Information other than the Software, provide a sworn affidavit from a person with personal knowledge attesting that the Provider Confidential Information constitute trade secrets under Florida Statutes Section 812.081 and stating the factual basis for same. In the event that a third party submits a request to the County for Provider Confidential Information, the County shall refrain from disclosing the Provider Confidential Information, unless otherwise ordered by a court of competent jurisdiction or authorized in writing by the Provider. Provider shall indemnify and defend County and its employees and Authorized Third Party Users from any and all claims, causes of action, losses, fines, penalties, damages, judgments and liabilities of any kind, including attorneys' fees, litigation expenses, and court costs, relating to the non -disclosure of any Provider Confidential Information in response to a records request by a third party. 9.3 County Confidential Information. 9.3.1 All materials, data, transactions of all forms, financial information, documentation, inventions, designs, and methods that Provider obtains from County in connection with this Agreement, that are made or developed by Provider in the course of the performance of the Agreement, or in which County holds proprietary rights, constitute "County Confidential Information." 9.3.2 All County -provided employee information, financial information, and personally identifiable information for individuals or entities interacting with County (including, without limitation, social security numbers, birth dates, banking and financial information, and other information deemed exempt or confidential under state or federal law) also constitute County Confidential Information. 9.3.3 County Confidential Information may not, without the prior written consent of County, or as otherwise required by law, be used by Provider or its employees, agents, Subcontractors or suppliers for any purpose other than for the benefit of County pursuant to this Agreement. Neither Provider nor its employees, agents, Subcontractors or suppliers may sell, transfer, publish, disclose, display, license or otherwise make available to any other person or entity any County Confidential Information without the prior written consent of County. Provider shall not, under any circumstances, cause or allow any County Confidential Information to be accessed by, transmitted or stored to any location outside the continental United States, Alaska and Hawaii, without prior written authorization from the Contract Administrator. Provider shall ensure that all County Confidential Information stored, maintained or transmitted by Provider is encrypted using AES 256 or equivalent at all times, whether at rest or in motion. P25 System and Services Agreement (R1422515R1/P1) Page 31 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 9.3.4 Provider expressly agrees to be bound by and to defend, indemnify and hold harmless County and its officers and employees from the breach of any federal, state or local law by Provider or its employees, agents, Subcontractors or suppliers regarding the unlawful use or disclosure of County Confidential Information. 9.3.5 Upon expiration or termination of this Agreement, or as otherwise demanded by County, Provider shall immediately turn over to County all County Confidential Information, in any form, tangible or intangible, possessed by Provider or its employees, agents, Subcontractors or suppliers. 9.4 Maintenance of Confidential Information. Each party shall advise its employees, agents, Subcontractors, and suppliers who receive or otherwise have access to the other party's Confidential Information of their obligation to keep such information confidential, and shall promptly advise the other party in writing if it learns of any unauthorized use or disclosure of the other party's Confidential Information. In addition, the parties agree to cooperate fully and provide reasonable assistance to ensure the confidentiality of the other party's Confidential Information. 9.5 Security and Access. Provider will cooperate with County and provide any and all information that County may request in order to determine appropriate security and network access restrictions and verify Provider's compliance with County security standards. Any access by Provider to any aspect of the County's network must comply at all times with all applicable County access and security standards, as well as any other or additional restrictions or standards for which County provides written notice to Provider. If at any point in time County, in the sole discretion of its Chief Information Officer, determines that Provider's access to any aspect of the County's network presents an unacceptable security risk, County may immediately suspend or terminate Provider's access and, if the risk is not promptly resolved to the reasonable satisfaction of the County's Chief Information Officer, may terminate this Agreement or any applicable Work Authorization upon ten (10) business days' notice (including, without limitation, without restoring any access to the County network to Provider). 9.6 Data and Privacy. Provider shall comply with all applicable data and privacy laws and regulations, including without limitation the Florida Information Protection Act of 2014, Florida Statutes Section 501.171. Provider may not sell, market, publicize, distribute, or otherwise make available to any third party any personal identification information (as defined by Florida Statutes Section 817.568 or Section 817.5685) that Provider may receive or otherwise have access to in connection with this Agreement, unless expressly authorized in advance by County. If and to the extent requested by County, Provider shall ensure that all hard drives or other storage devices and media that contained County data have been wiped in accordance with the then -current best industry practices, including without limitation DOD 5220.22-M, and that an appropriate data wipe certification is provided to the satisfaction of the Contract Administrator. P25 System and Services Agreement (R1422515R1/P1) Page 32 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 9.7 Injunctive Relief. The parties represent and agree that neither damages nor any other legal remedy is adequate to remedy any breach of this Article, and that the injured party shall therefore be entitled to injunctive relief to restrain or remedy any breach or threatened breach. 9.8 Survival. The obligations under this Article 9 shall survive the termination of this Agreement or of any license granted under this Agreement. ARTICLE 10. INDEMNIFICATION AND LIMITATION OF LIABILITY 10.1 Indemnification. Provider shall be fully liable for the actions of its current and former officers, employees, subcontractors and other agents under this Agreement. Provider shall at all times hereafter indemnify, hold harmless and defend County and all of County's current and former officers and employees and Authorized Third Party Users (collectively, "Indemnified Party") from and against any and all lawsuits, causes of action, demands, claims, losses, fines, penalties, damages, judgments, liabilities and expenditures of any kind, including attorneys' fees, litigation expenses, and court costs (collectively, "Claim"), raised or asserted by any person or entity that is not a party to this Agreement, which Claim is caused or alleged to be caused, in whole or in part, by any intentional, reckless, or negligent act or omission of Provider or any current or former officer, employee, Subcontractor or other agent of Provider, arising from, relating to, or in connection with any obligation or performance under this Agreement. In the event any Claim is brought against an Indemnified Party, Provider shall, upon written notice from County, defend each Indemnified Party against each such Claim through counsel reasonably satisfactory to County (approval of which shall not be unreasonably withheld). The provisions and obligations of this Section shall survive the expiration or earlier termination of this Agreement. Motorola will have no duty to defend or indemnify for any Claim for intellectual property infringement that is based upon: (a) the combination of the Motorola Equipment with any software, apparatus or device not furnished or approved by Motorola or otherwise specified in the Documentation or Specifications as compatible; (b) use of the Motorola Equipment in a manner for which the Motorola Equipment was not designed or that is inconsistent with the terms of this Agreement; or (c) the failure by County to install an enhancement release to the Software that is intended to correct the claimed infringement for which notice was provided to County that installation was necessary to avoid infringement. In no event will Motorola's liability resulting from its indemnity obligation to County extend in any way to County's revenues derived from user fee royalties payable to the County on a per use basis to the County. In addition, Provider's duties to defend and indemnify are conditioned upon: County promptly notifying Provider in writing of the Claim; Provider having sole control of the defense of the suit and all negotiations for its settlement or compromise; and County providing to Provider cooperation and, if requested by Provider, reasonable assistance in the defense of the Claim. 10.2 Limitation of Liability. Neither Provider nor County shall be liable to the other party for any damages under this Agreement that exceed the largest of the following amounts: (a) $100,000; (b) twice the maximum compensation amount specified in Section 5.1; or (c) the amount of insurance Provider is required to provide under Article 11. Neither party shall be liable for the other party's special, indirect, punitive, or consequential damages (including damages P25 System and Services Agreement (R1422515R1/P1) Page 33 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 resulting from lost data or records other than costs incurred in the recovery thereof), even if the party has been advised that such damages are possible, or for the other party's lost profits, lost revenue, or lost institutional operating savings. These limitations of liability shall not apply to (i) any Claim resulting from Provider's actual or alleged disclosure of County Confidential Information or resulting from an actual or alleged data breach in violation of applicable law, (ii) any Claim resulting from an actual or alleged infringement of any interest in any intellectual property, or (iii) any indemnification obligation under this Agreement. 10.3 Third Party Pass Thru Rights. Provider shall extend to County all rights and benefits Provider has from any third party as to the Equipment or Software as to any warranty or infringement claim, including any and all indemnification and hold harmless rights, to the extent permitted under any applicable agreement with the third party equipment or software supplier or otherwise available to Provider. Provider shall at all times use all reasonable efforts to cooperate with County in the event of a third party claim involving any part of the P25 System. 11.1 Provider shall maintain at its sole expense, on a primary basis, at all times during the term of this Agreement (unless a different time period is stated herein), at least the minimum insurance coverage designated in Exhibit D in accordance with the terms and conditions stated in this Article. 11.2 Such policies shall be issued by companies authorized and licensed to transact business in the State of Florida, with a minimum AM Best financial rating of A-, unless otherwise approved in writing by County. If any deductible amounts are permitted in Exhibit D, Provider shall be responsible for the payment of all such deductible amounts. 11.3 Provider agrees to include County as an additional insured under Provider's commercial liability insurance policy and any excess liability insurance policy. The listed certificate holder on all required policies shall be "Broward County." 11.4 Coverage shall be provided on forms no more restrictive than the latest edition of the applicable forms filed by the Insurance Services Office. 11.5 Provider shall notify County in writing within thirty (30) days after Provider learns of any claim against Provider's professional liability insurance policy in which damages claimed plus defense costs incurred to date exceed $250,000. 11.6 Within fifteen (15) days of execution of this Agreement, Provider shall provide County with proof of insurance in the form of Certificate(s) of Insurance and applicable endorsements. Failure to timely provide acceptable proof of insurance, as determined by County, shall entitle County to terminate this Agreement without any liability to Provider. P25 System and Services Agreement (R1422515R1/P1) Page 34 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 11.7 Provider must provide County with at least thirty (30) days' written notice of expiration, cancellation, or restriction of any coverage required under this Article. Provider shall provide certified copies of any required policy to County upon County's request. 11.8 If Provider subcontracts any work under this Agreement, Provider shall require that each subcontractor names County as an additional insured under the subcontractor's general liability insurance policy and any excess liability insurance policy. ARTICLE 12. EEO and CBE COMPLIANCE 12.1 Nondiscrimination. Provider may not discriminate on the basis of race, color, sex, religion, national origin, disability, age, marital status, political affiliation, sexual orientation, pregnancy, or gender identity and expression in the performance of this Agreement, except that any project assisted by U.S. Department of Transportation funds shall comply with the nondiscrimination requirements in 49 C.F.R. Parts 23 and 26. Provider shall include substantially similar language in its contracts with any and all permitted subcontractors providing goods or services under this Agreement. 12.2 Failure by Provider to carry out any of the requirements of this Article shall constitute a material breach of this Agreement, which shall permit County to terminate this Agreement or to exercise any other remedy provided under this Agreement, Broward County Code of Ordinances, Broward County Administrative Code, or under other applicable law, all such remedies being cumulative. 12.3 Provider shall comply with all applicable requirements of the County's CBE Program as established by Broward County Business Opportunity Act of 2012, Section 1-81, Broward County Code of Ordinances (the "Act"), in performing this Agreement. Provider acknowledges that the Board, acting through the Office of Economic and Small Business Development ("OESBD"), may make minor administrative modifications to the CBE Program which shall become applicable to this Agreement if the administrative modifications are not unreasonable. Written notice of any such modification shall be provided to Provider and shall include a deadline for Provider to notify County if Provider concludes that the modification exceeds the authority of this Section of this Agreement. Failure of Provider to timely notify County of its conclusion that the modification exceeds such authority shall be deemed acceptance of the modification by Provider. 12.4 Provider will meet the following CBE participation goal by utilizing the CBE firms for the following percentage of Services under this Agreement: CBE participation goal 15% or as otherwise approved by OESBD Provider stipulates that each CBE firm utilized to meet the CBE participation goal must be certified by the OESBD. Provider shall inform County immediately when a CBE firm is not able to perform or if Provider believes the CBE firm should be replaced for any other reason, so that the P25 System and Services Agreement (R1422515R1/P1) Page 35 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 OESBD may review and verify the good faith efforts of Provider to substitute the CBE firm with another CBE firm. Whenever a CBE firm is terminated for any reason, including cause, Provider shall provide written notice to the OESBD and shall substitute another CBE firm in order to maintain the level of CBE participation required herein, unless otherwise provided herein or agreed in writing by the parties. Such substitution shall not be required in the event the termination results from County modifying the scope of services and there is no available CBE to perform the new scope of services, in which event Provider shall notify County and the OESBD may adjust the CBE participation goal by written notice to Provider. Provider may not terminate for convenience a CBE firm without County's prior written consent, which consent shall not be unreasonably withheld. County may add or increase the required participation of CBE firms under this Agreement in connection with any amendment, extension, modification, or change order to this Agreement that, by itself or aggregated with previous amendments, extensions, modifications, or change orders, increases the initial Agreement price by ten percent (10%) or more. To the extent Provider is subcontracting any work under this Agreement, Provider shall make a good faith effort to include CBE firms in work resulting from any such amendment, extension, modification, or change order and shall report such efforts, along with evidence thereof, to the OESBD. 12.5 In performing the Services, the Parties hereby incorporate the list of Provider's participating CBE firms, addresses, scope of work, and the percentage of work amounts identified on each Letter of Intent into this Agreement (Exhibit G). Promptly upon execution of this Agreement by County, Provider shall enter into a formal contract with the CBE firms listed in Exhibit G and, upon request, shall provide copies of the contracts to the Contract Administrator and OESBD. 12.6 Provider shall provide written monthly reports to the Contract Administrator attesting to Provider's compliance with the CBE participation goals stated in this Article. In addition, Provider shall allow County to engage in on -site reviews to monitor Provider's progress in achieving and maintaining its contractual and CBE program obligations. Such review and monitoring shall be by the Contract Administrator in conjunction with the OESBD, unless otherwise determined by the County Administrator. County shall have access, without limitation, to Provider's books and records, including payroll records, tax returns and records, and books of account, on five (5) business days' notice. 12.7 In the event of Provider's noncompliance with its CBE participation goal (including without limitation the unexcused reduction of a CBE firm's participation), the affected CBE firm shall have the right to exercise any remedies as may be available as between the CBE firm and Provider. 12.8 The Contract Administrator may, at its option, increase allowable retainage or withhold progress payments unless and until Provider demonstrates timely payments of sums due to all subcontractors and suppliers. The presence of a "pay when paid" provision in a Provider's contract with a CBE firm shall not preclude County or its representatives from inquiring into allegations of nonpayment. P25 System and Services Agreement (R1422515R1/P1) Page 36 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ARTICLE 13. TERMINATION 13.1 The termination rights of County in this Article 13 may be exercised as to any one or more Statements of Work or component Systems, as elected in the sole direction of County, provided that any right to terminate for cause arises only as to the Statement(s) of Work related to the breach at issue. 13.2 This Agreement may be terminated for cause based on any breach that is not cured within ten (10) days after written notice from the aggrieved party identifying the breach. This Agreement may also be terminated for convenience by the Board upon providing written notice to Provider of the termination date, which shall be not less than thirty (30) days after the date such written notice is provided. If County erroneously, improperly, or unjustifiably terminates for cause, such termination shall, to the full extent permissible under applicable law, be deemed a termination for convenience, which shall be effective thirty (30) days after such notice of termination for cause is provided. 13.3 County may terminate this Agreement if Provider is found to have submitted a false certification pursuant to Section 287.135, Florida Statutes, if Provider has been placed on the Scrutinized Companies with Activities in Sudan List or the Scrutinized Companies with Activities in the Iran Petroleum Energy Sector List, or if Provider has failed to promptly implement corrective action for audit deficiencies upon reasonable notice by County. Notwithstanding anything contained in this Agreement to the contrary, the rights and obligations of the parties under this paragraph shall be governed by Section 287.135, Florida Statutes, to the full extent applicable. 13.4 Provider represents that neither it nor any of its affiliates has been placed on the discriminatory vendor list, as defined by Section 287.134, Florida Statutes. County may terminate this Agreement effective immediately, without any further obligation to Provider, upon learning that such representation is false or if Provider or any of its affiliates is placed on the discriminatory vendor list. 13.5 Additionally, and notwithstanding anything to the contrary in this Agreement, County may terminate this Agreement without any further liability to Provider upon the decertification of Provider as a Certified Business Entity ("CBE") by County's Office of Economic and Small Business Development ("OESBD"), if Provider's status as a CBE was a factor in the award of the Agreement and such status was misrepresented by Provider. However, such termination shall not be effective until expiration of any timely -filed review or appeal of the decertification decision. 13.6 Notice of termination shall be provided in accordance with the "Notices" section of this Agreement. P25 System and Services Agreement (R1422515R1/P1) Page 37 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 13.7 In the event this Agreement is terminated for convenience, Provider shall be paid for any goods and services properly provided through the termination date specified in the written notice of termination. Provider acknowledges that it has received good, valuable and sufficient consideration from County, the receipt and adequacy of which are hereby acknowledged by Provider, for County's right to terminate this Agreement for convenience, and Provider hereby waives, to the full extent permissible under applicable law, any and all rights to challenge the adequacy of such consideration or the validity of County's right to terminate for convenience. 13.8 In case of termination of this Agreement in whole or in part before Final Completion for any reason whatsoever, Provider, if notified to do so by County, shall promptly remove any part or all of the equipment and supplies of Provider or its Subcontractor from the property of County, failing which County shall have the right to remove such equipment and supplies at the expense of Provider. ARTICLE 14. MISCELLANEOUS 14.1 Rights in Documents and Work. Any and all reports, photographs, surveys, and other data and documents provided or created in connection with this Agreement shall be and remain the property of County and, if a copyright is claimed, Provider hereby grants to County a nonexclusive perpetual license to use the copyrighted item(s), to prepare derivative works, and to make and distribute copies to the public. In the event of termination or expiration of this Agreement, any reports, photographs, surveys, and other data and documents prepared by Provider, whether finished or unfinished, shall become the property of County and shall be delivered by Provider to the Contract Administrator within seven (7) days of termination or expiration of this Agreement by either party. 14.2 Audit Right and Retention of Records. County shall have the right to audit the books, records, and accounts of Provider and its subcontractors that are related to this Agreement. Provider and its subcontractors shall keep such books, records, and accounts as may be necessary in order to record complete and correct entries related to the Agreement and performance thereunder. All books, records, and accounts of Provider and its subcontractors shall be kept in written form, or in a form capable of conversion into written form within a reasonable time, and upon request to do so, Provider or its subcontractor, as applicable, shall make same available at no cost to County in written form. Provider and its subcontractors shall preserve and make available, at reasonable times within Broward County for examination and audit by County, all financial records, supporting documents, statistical records, and any other documents pertinent to this Agreement for a minimum period of three (3) years after expiration or termination of this Agreement or until resolution of any audit findings, whichever is longer. County audits and inspections pursuant to this Section may be performed by any County representative (including any outside representative engaged by County). County reserves the right to conduct such audit or review at Provider's place of business, if deemed appropriate by County, with seventy-two (72) hours' advance notice. P25 System and Services Agreement (R1422515R1/P1) Page 38 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Any incomplete or incorrect entry in such books, records, and accounts shall be a basis for County's disallowance and recovery of any payment upon such entry. If an audit or inspection in accordance with this Section discloses overpricing or overcharges to County of any nature by Provider in excess of five percent (5%) of the total contract billings reviewed by County, the reasonable actual cost of the County's audit shall be reimbursed to the County by Provider in addition to making adjustments for the overcharges. Any adjustments and/or payments due as a result of such audit or inspection shall be made within thirty (30) days from presentation of County's findings to Provider. Provider shall ensure that the requirements of this Section are included in all agreements with its subcontractor(s). 14.3 Public Records. To the extent Provider is acting on behalf of the County as stated in Section 119.0701, Florida Statutes, Provider shall: a. Keep and maintain public records required were County performing the services under this Agreement; b. Upon request from the County, provide County with a copy of the requested records or allow the records to be inspected or copied within a reasonable time and at a cost that does not exceed that provided in Chapter 119, Florida Statutes, or as otherwise provided by law; c. Ensure that public records that are exempt or that are confidential and exempt from public record requirements are not disclosed except as authorized by law for the duration of the Agreement and following completion of the Agreement if the records are not transferred to the County; and d. Upon completion of the Agreement, transfer to County, at no cost, all public records in possession of Provider upon termination of this Agreement or keep and maintain public records required were the County performing the service. If Provider transfers the records to the County, Provider shall destroy any duplicate public records that are exempt or confidential and exempt. If the Provider keeps and maintains public records upon completion of the Agreement, Provider shall meet all applicable requirements for retaining public records. All records stored electronically must be provided to County upon request in a format that is compatible with the information technology systems of County. The failure of Provider to comply with the provisions of this Section shall constitute a material breach of this Agreement entitling the County to exercise any remedy provided in this Agreement or under applicable law. P25 System and Services Agreement (R1422515R1/P1) Page 39 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A request for public records regarding this Agreement must be made directly to the County, who will be responsible for responding to any such public records requests. Provider will provide any requested records to County to enable County to respond to the public records request. IF THE PROVIDER HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE PROVIDER'S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THIS CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT (954) 357-8570, bbayag@broward.org, 115 S. ANDREWS AVE., SUITE 325, FORT LAUDERDALE, FLORIDA 33301. 14.4 Truth -In -Negotiation Representation. Provider's compensation under this Agreement is based upon representations supplied to County by Provider, and Provider certifies that that wage rates and other factual unit costs supporting the compensation are accurate, complete, and current at the time of contracting. The original price under this Agreement and any additions thereto will be adjusted to exclude any significant sums by which County determines the price was increased due to inaccurate, incomplete, or noncurrent wage rates and other factual unit costs. County shall be entitled to recover any and all other damages available under law or equity it incurs to the extent any such representation is untrue. 14.5 Public Entity Crime Act. Provider represents that it is familiar with the requirements and prohibitions under the Public Entity Crime Act, Section 287.133, Florida Statutes, and represents that its entry into this Agreement will not violate that Act. In addition to the foregoing, Provider further represents that there has been no determination that it committed a "public entity crime" as defined by Section 287.133, Florida Statutes, and that it has not been formally charged with committing an act defined as a "public entity crime" regardless of the amount of money involved or whether Provider has been placed on the convicted vendor list. Notwithstanding any provision in this Agreement to the contrary, if any representation stated in this paragraph is false, County shall have the right to immediately terminate this Agreement and recover all sums paid to Provider under this Agreement. 14.6 Independent Contractor. Provider is an independent contractor under this Agreement. Provider shall not have the right to bind County to any obligation not expressly undertaken by County under this Agreement. 14.7 Third Party Beneficiaries. The parties acknowledge that there are no third party beneficiaries under this Agreement. 14.8 Notices. In order for a notice to a party to be effective under this Agreement, notice must be sent via U.S. first-class mail with a contemporaneous copy via e-mail to the addresses listed below and shall be effective upon mailing. The addresses for notice shall remain as set forth herein unless and until changed by providing notice of such change. P25 System and Services Agreement (R1422515R1/P1) Page 40 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 NOTICE TO COUNTY: Broward County Office of Regional Communications and Technology Attn: Brett Bayag 115 S. Andrews Ave., Suite 325 Ft. Lauderdale, Florida 33301 Email address: bbayag@broward.org NOTICE TO PROVIDER: Motorola Solutions, Inc. Attn: Judy Jean-Pierre, Sr. Counsel 500 West Monroe Street, 43rd Floor Chicago, IL 60661 Email address: Judy.Jean-Pierre@motorolasolutions.com 14.9 Assignment and Subcontractors. Except for subcontracting approved by County at the time of its execution of this Agreement or any written amendment hereto, neither this Agreement nor any right or interest herein may be assigned, transferred, subcontracted, or encumbered by Provider without the prior written consent of County. If Provider violates this provision, County shall have the right to immediately terminate this Agreement. Notwithstanding the foregoing, solely to the extent of its rights and obligations as the licensor of the Software, Motorola may assign its rights or subcontract its obligations as licensor, or encumber or sell its rights in any Software, without prior notice to or consent of County; any such assignment, subcontract, transfer, encumbrance or sale shall have no effect upon and shall not relieve Motorola from any obligation(s) under this Agreement. Provider shall utilize the Subcontractors identified in the proposal that were a material part of the selection of Provider to provide the services for this Project. Provider shall obtain written approval of Contract Administrator prior to changing or modifying the list of Subcontractors submitted by Provider. Where Provider's failure to use a Subcontractor results in Provider's noncompliance with CBE participation goals, such failure shall entitle the affected CBE firm to damages available under this Agreement and local and state law. The list of Subcontractors is provided on Exhibit G, Schedule of Subcontractors, attached hereto and made a part hereof. Each Subcontractor must possess certificates of competency and licenses as may be required by law. Provider shall have a continuing obligation to notify County of any change in Subcontractors. Provider shall not employ any Subcontractor against whom County may have a reasonable objection. Provider shall not be required to employ any Subcontractor against whom Provider has a reasonable objection. Provider shall be fully responsible for all acts and omissions of its Subcontractors and of persons directly or indirectly employed by its Subcontractors and of persons for whose acts any of them may be liable to the same extent that Provider is responsible for the acts and omissions of persons directly employed by it. Nothing in the Design Build Contract Documents shall create any contractual relationship between any Subcontractor and County or any obligation on the part of County to pay or to seethe payment of any monies due any Subcontractor. County may furnish P25 System and Services Agreement (R1422515R1/P1) Page 41 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 to any Subcontractor evidence of amounts paid to Provider on account of specific work performed. Provider shall bind in writing each and every Subcontractor to the applicable terms and conditions of the Design Build Contract Documents for the benefit of County, provided that this provision shall not, in and of itself, impose the insurance requirements set forth in Article 11 on Provider's Subcontractors. 14.10 Conflicts. Provider agrees that neither it nor its employees will have or hold any continuing or frequently recurring employment or contractual relationship that is substantially antagonistic or incompatible with Provider's loyal and conscientious exercise of the judgment and care required to perform under this Agreement. Provider further agrees that none of its officers or employees shall, during the term of this Agreement, serve as an expert witness against County in any legal or administrative proceeding in which he, she, or Provider is not a party, unless compelled by court process. Further, such persons shall not give sworn testimony or issue a report or writing, as an expression of his or her expert opinion, which is adverse or prejudicial to the interests of County in connection with any such pending or threatened legal or administrative proceeding unless compelled by court process. The limitations of this Section shall not preclude Provider or any person from in any way representing themselves, including giving expert testimony in support thereof, in any administrative or legal proceeding. Provider agrees that each of its contracts with subcontractors performing under this Agreement shall contain substantively identical language to ensure that each subcontractor and its officers and employees meet the obligations contained in this paragraph. 14.11 Waiver of Breach. The failure of either party to enforce any provision of this Agreement shall not be deemed a waiver of such provision or modification of this Agreement. A waiver of any breach under this Agreement shall not be deemed a waiver of any subsequent breach. 14.12 Compliance with Laws. Provider shall comply with all applicable federal, state, and local laws, codes, ordinances, rules, and regulations in performing under this Agreement. Provider shall ensure that its Subcontractors conform to and obey all applicable laws, regulations, or ordinances with regard to labor employed, hours of work, and Subcontractor's general operations. Provider's Subcontractor shall perform the required Services under this Agreement in such a way so as not to close any thoroughfare, nor interfere in any way with traffic on railway, highways, or water, without the written consent of the proper authorities. 14.13 Severability. In the event any part of this Agreement is found to be unenforceable by any court of competent jurisdiction, that part shall be deemed severed from this Agreement and the balance of this Agreement shall remain in full force and effect. 14.14 Joint Preparation. This Agreement has been jointly prepared by the parties hereto, and shall not be construed more strictly against either party. P25 System and Services Agreement (R1422515R1/P1) Page 42 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 14.15 Headings and Interpretation. The headings contained in this Agreement are for reference purposes only and shall not in any way affect the meaning or interpretation of this Agreement. All personal pronouns used in this Agreement shall include the other gender, and the singular shall include the plural, and vice versa, unless the context otherwise requires. Terms such as "herein," "hereof," "hereunder," and "hereinafter," refer to this Agreement as a whole and not to any particular sentence, paragraph, or section where they appear, unless the context otherwise requires. 14.16 Governing Law, Venue and Waiver of Jury Trial. This Agreement shall be interpreted and construed in accordance with, and governed by, the laws of the state of Florida. The parties agree that the exclusive venue for any lawsuit arising from, related to, or in connection with this Agreement shall be in the state courts of the Seventeenth Judicial Circuit in and for Broward County, Florida. If any claim arising from, related to, or in connection with this Agreement must be litigated in federal court, the parties agree that the exclusive venue for any such lawsuit shall be in the United States District Court or United States Bankruptcy Court for the Southern District of Florida. BY ENTERING INTO THIS AGREEMENT, PROVIDER AND COUNTY HEREBY EXPRESSLY WAIVE ANY AND ALL RIGHTS EITHER PARTY MAY HAVE TO A TRIAL BY JURY OF ANY CAUSE OF ACTION OR CLAIM ARISING FROM, RELATED TO, OR IN CONNECTION WITH THIS AGREEMENT. 14.17 Amendments. No modification or amendment to this Agreement shall be effective unless it is in writing and executed by authorized representatives of each party. Without limiting the foregoing, the terms of this Agreement shall prevail over and against any additional or contrary terms and conditions in any format or medium whatsoever including, without limitation, shrinkwrap, click -through, or terms and conditions associated with any upgrade, update, release, patch, or other modification of the System or Software, unless expressly agreed to in writing by an amendment hereto executed by authorized representatives of each party. 14.18 Prior Agreements. This Agreement represents the final and complete understanding of the parties regarding the subject matter hereof and supersedes all prior and contemporaneous negotiations and discussions regarding that subject matter. There is no commitment, agreement, or understanding concerning the subject matter of this Agreement that is not contained in this written document. 14.19 HIPAA Compliance. It is understood by the parties that County personnel or their agents have access to protected health information (hereinafter known as "PHI") that is subject to the requirements of 45 C.F.R. § 160, 162, and 164 and related statutory and regulatory provisions. In the event Provider is considered by County to be a covered entity or business associate or otherwise required to comply with the Health Insurance Portability and Accountability Act of 1996 ("HIPAA") or the Health Information Technology for Economic and Clinical Health Act ("HITECH"), Provider shall fully protect individually identifiable health information as required by HIPAA and HITECH. If requested by County, Provider shall execute a Business Associate Agreement in the form set forth at www.broward.org/Purchasing/Pages/StandardTerms.aspx. Where required, Provider shall handle and secure such PHI in compliance with HIPAA, HITECH and its related regulations and, if required by HIPAA, HITECH, or other laws, shall include in its P25 System and Services Agreement (R1422515R1/P1) Page 43 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 "Notice of Privacy Practices" notice of Provider's and County's uses of a client's PHI. The requirement to comply with this provision, HIPAA and HITECH shall survive the expiration or termination of this Agreement. County hereby authorizes the County Administrator to sign Business Associate Agreements if required under this Agreement. 14.20 Payable Interest 14.20.1 Payment of Interest. County shall not be liable to pay any interest to Provider for any reason, whether as prejudgment interest or for any other purpose, and in furtherance thereof Provider waives, rejects, disclaims and surrenders any and all entitlement it has or may have to receive interest in connection with a dispute or claim arising from, related to, or in connection with this Agreement. This paragraph shall not apply to any claim interest, including for post -judgment interest, if such application would be contrary to applicable law. 14.20.2 Rate of Interest. If, for whatever reason, the preceding subsection is determined to be invalid or unenforceable by a court of competent jurisdiction, the annual rate of interest payable by County under this Agreement, whether as prejudgment interest or for any other purpose, shall be, to the full extent permissible under applicable law, 0.25% (one quarter of one percent) simple interest (uncompounded). 14.21 Incorporation by Reference. Any and all Recital clauses stated above are true and correct and are incorporated herein by reference. 14.22 Representation of Authority. Each individual executing this Agreement on behalf of a party hereto represents and warrants that he or she is, on the date of execution, duly authorized by all necessary and appropriate action to execute this Agreement on behalf of such party and does so with full legal authority. Provider represents that it is an entity authorized to transact business in the State of Florida. 14.23 Domestic Partnership Requirement. Unless this Agreement is exempt from the provisions of Section 16%-157 of the Broward County Code of Ordinances, which requires County contractors to provide benefits to domestic partners of their employees, Provider agrees to fully comply with Section 16%-157 during the entire term of the Agreement. If Provider fails to fully comply with that section, such failure shall constitute a material breach which shall allow County to exercise any remedy available under this Agreement, under applicable law, or under section 16%-157. For that purpose, the contract language referenced in Section 16%-157 is incorporated herein as though fully set forth in this paragraph. 14.24 Drug -Free Workplace. It is a requirement of County that it enter into contracts only with firms that certify the establishment of a drug -free workplace in accordance with Chapter 21.31(a)(2) of the Broward County Procurement Code. Execution of this Agreement by Provider shall serve as Provider's required certification that it has or will establish a drug -free workplace in accordance with Section 287.087, Florida Statutes, and Chapter 21.31(a)(2) of the Broward P25 System and Services Agreement (R1422515R1/P1) Page 44 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 County Procurement Code, and that it will maintain such drug -free workplace for the full term of this Agreement. 14.25 Contingency Fee. Provider represents that it has not paid or agreed to pay any person or entity, other than a bona fide employee working solely for Provider, any fee, commission, percentage, gift, or other consideration contingent upon or resulting from the award or making of this Agreement. If County learns that this representation is false, County shall have the right to terminate this Agreement without any further liability to Provider. Alternatively, if such representation is false, County, at its sole discretion, may deduct from the compensation due Provider under this Agreement the full amount of such fee, commission, percentage, gift, or consideration. 14.26 Living Wage Requirement. If Provider is a "covered employer" within the meaning of the Broward County Living Wage Ordinance, Broward County Code sections 26-100 — 26-105, Provider agrees to and shall pay to all of its employees providing "covered services," as defined therein, a living wage as required by such ordinance, and Provider shall fully comply with the requirements of such ordinance. Provider shall be responsible for and shall ensure that all of its subcontractors that qualify as "covered employers" fully comply with the requirements of such ordinance. 14.27 Force Maieure. If the performance of this Agreement, or any obligation hereunder, is prevented by reason of hurricane, earthquake, or other casualty caused by nature, or by labor strike, war, or by a law, order, proclamation, regulation, or ordinance of any governmental agency, the party so affected, upon giving prompt notice to the other party, shall be excused from such performance to the extent of such prevention, provided that the party so affected shall first have taken reasonable steps to avoid and remove such cause of nonperformance and shall continue to take reasonable steps to avoid and remove such cause, and shall promptly notify the other party in writing and resume performance hereunder whenever and to the full extent such causes are removed. However, if such nonperformance exceeds sixty (60) days, the party that is not prevented from performance by the force majeure event shall have the right to immediately terminate this Agreement upon written notice to the party so affected. This Section shall not supersede or prevent the exercise of any right the parties may otherwise have to terminate this Agreement. 14.28 County Logo. Provider shall not use County's name, logo, or otherwise refer to this Agreement in any marketing or publicity materials without the prior written consent of County. 14.29 Resolution of Disputes. During the pendency of any dispute and after a determination thereof, Provider and its Subcontractor shall act in good faith to mitigate any potential damages including utilization of construction schedule changes and alternate means of construction. Provider shall carry on the Services and Work and adhere to the progress schedule during all disputes or disagreements with the County, including disputes or disagreements concerning a request for a Change Order or a request for a change in the Design Build Price or Design Build Time. No work or Services shall be delayed or postponed pending resolution of any disputes or P25 System and Services Agreement (R1422515R1/P1) Page 45 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 disagreements except as Provider and County may otherwise agree in writing. Suspension of Work or Services by Provider during any dispute or disagreement with County shall entitle County to terminate the Agreement for cause. In the event a dispute cannot be resolved amicably between the Contract Administrator and Provider, Parties shall promptly escalate the dispute to the County Administrator, whose resolution will be determinative on behalf of County. If Provider objects to the resolution by the County Administrator, or the County Administrator does not resolve within sixty (60) days of submission and the dispute remains outstanding, upon written demand by either party, the Parties shall participate in voluntary, nonbinding mediation. Neither party shall commence litigation prior to completion or impasse of mediation, which shall be conducted within sixty (60) day of demand by either party. The mediator shall be mutually agreed upon by the Parties and expenses shared by the Parties. Should any objection not be resolved in mediation, the Parties retain all their legal rights and remedies provided under the laws of the State of Florida. A PARTY SPECIFICALLY WAIVES ALL OF ITS RIGHTS, INCLUDING, BUT NOT LIMITED TO, CLAIMS FOR DESIGN BUILD TIME AND DESIGN BUILD PRICE ADJUSTMENTS PROVIDED IN THE DESIGN BUILD CONTRACT DOCUMENTS, INCLUDING ITS RIGHTS AND REMEDIES UNDER STATE LAW, IF SAID PARTY FAILS TO COMPLY IN STRICT ACCORDANCE WITH THE REQUIREMENTS OF THIS ARTICLE. 14.30 Counterparts. This Agreement may be executed in multiple originals, and may be executed in counterparts, each of which shall be deemed to be an original, but all of which, taken together, shall constitute one and the same agreement. (The remainder of this page is intentionally left blank.) P25 System and Services Agreement (R1422515R1/131) Page 46 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 IN WITNESS WHEREOF, the Parties hereto have made and executed this Agreement: BROWARD COUNTY through its BOARD OF COUNTY COMMISSIONERS, signing by and through its Mayor or Vice -Mayor, authorized to execute same by Board action on the 3011 day of _ J 2017, and MOTOROLA SOLUTIONS, INC., signing by and through its Vice Pres , identkouly authorized to execute same. ATTE award County Administra Ex-officio Clerk of the Broward County Board of County Commissioners Insurance requirements approved by Broward County Risk Management Division: By: Name: 4iyA ,z fG� z.4'Eti Title: 9/a/c RDH 2017-05-01 Motorola P25 Agreement 05/01/17 #17-099.03 COUNTY BROWARD COUNTY, b throu its Board of Cou By: (:Qa �'�ay of 2017 Approved as to form by Joni Armstrong Coffey Broward County Attorney Governmental Center, Suite 423 115 South Andrews Avenue Fort Lauderdale, Florida 33301 Telephone: (954) 357-7600 Telecop' .y . 54 357-764 By: Rene D. Harrod (Date) Assistant County Attorney `,r,`��1�IN1�I Nltllf,`ff .� 4 CREATEDz 0 :M oCT ist a•• E =p .;, �. 1915 s N1t1i P25 System and Services Agreement (R1422515R1/Pl) Page 47 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 WITNESSES: Signature Print Name of Witness Bove Signature Print Name of Witness above PROVIDER MOTOROLA SOLUTIONS, INC. By: mc'rz�- Authorized Signor C/ 4 f e J t E, M. s�la I ��►Z V i Cr 'I'/2 �3Sro3 k� T Print Name and Title / day of AA ILLL ATTEST: Assist nt Secretary or other person authorized to attest (CORPORATE SEAL OR NOTARY) P25 System and Services Agreement (R1422515R1/P1) Page 48 of 48 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 EXHIBIT A — STATEMENT OF WORK All references to Exhibit A shall be deemed to be inclusive of this Introduction, as well as Exhibits A- 1, A-2, A-3, A-4, and A-5. Provider and County agree that Provider shall provide the following work under this Agreement: The System will provide a turnkey replacement of various communications subsystems operated by the County. The Provider shall provide equipment and services that includes all of the following: • A new 700 megahertz (MHz), Project 25 (1325) Phase II system to replace the County's existing 800 MHz Motorola SmartZone System • A new Internet Protocol (IP)-based microwave system to replace the County's existing Tadiran 6 GHz system, with all microwave links operating in the licensed 6 GHz frequency band, and with backward compatibility for legacy circuits to support the County's existing radio infrastructure during the transition period. • A new dispatch console system for the County's three regional dispatch centers • A new 800 MHz, P25 Phase II simulcast, 4-site 6-channel backup system • A new 700 MHz, P25 conventional, 4-site interoperability system • A new 800 MHz, analog conventional, 4-site simulcast interoperability system • A new communications trailer with appropriately sized towing vehicle • Civil work to support upgrades to new and existing radio sites to support the aforementioned communications subsystems. • Configured consoles to interface with Fort Lauderdale talkgroups without the use of a control station interface through the Inter-RF Sub System Interface (ISSI), to support the dispatching for the City of Fort Lauderdale • P25 Phase II -compliant subscriber radios as may be ordered by the County or Authorized Third Party Users. Dispatching in Broward County is handled at three public safety answering point (PSAP) locations: • Sunrise (Central Dispatch) —10440 W. Oakland Park Blvd., Sunrise, FL 33351 • Pembroke Pines (South Dispatch) — 6057 S.W. 1981" Terrace, Fort Lauderdale, FL 33311 • Coconut Creek (North Dispatch) — 4800 W. Copans Rd., Coconut Creek, FL 33063 1. Services General Description A. The project includes several turnkey components, as follows: 1. Replacement of the existing system with a new P25 Phase I and Phase II 700/800 MHz radio system, including dispatch consoles. (SOW A-1) P25 System and Services Agreement (R1422515R1/131) Page 1 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Replacement or upgrade of existing dispatch consoles including supervisor and spare positions. (SOW A-1) 3. Upgrade existing and design and build new towers, shelters, and other facilities where required in connection with new and upgraded site deployments (SOW A-2) 4. Replacement of the existing microwave network with anew IP-based microwave network providing "five nines" (99.999 percent) link reliability and multiprotocol label switching (MPLS) routing. (SOW A-3) 5. Provision of subscriber equipment and maintenance to Authorized Third Party User agencies (SOW A-4) B. The trunked radio system shall comply with the latest applicable P25 suite of standards adopted as Telecommunications Industry Association (TIA) and/or American National Standards Institute (ANSI) documents at the time of Final Acceptance. C. The system shall provide a standalone 700/800 MHz, P25 DMM Phase I and Phase II trunked, simulcast system providing communications within the County. The system shall include a system expansion with additional radio site(s) to enhance the coverage needs of Broward County. D. The Provider shall provide backup solutions, including a live 4-site 700/800 P25 Phase II, 7-channel fixed simulcast backup network supporting both voice and data; a 4-site, 2- channel conventional overlay (separate channels at each site); and a mobile communications trailer supporting two onboard conventional repeaters and a gateway system. The Provider's System shall comply with the specifications set forth in the SOWs to the Agreement (which incorporate the specifications provided in the RFP), unless expressly otherwise approved in writing by the County. The RFP specifications reflect user operational requirements, system requirements, infrastructure requirements, and system support requirements for the County. The RFP specifications document addresses (but is not limited to): • Coverage requirements • Daily operational communications requirements of first responders • Significant system components • Minimum and maximum performance specifications for the system and for the subscriber units, based on defined user needs, national standards, and industry best practices P25 System and Services Agreement (R1422515R1/P1) Page 2 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Hardware specifications • County -owned tower sites • County raw -land sites • Antennas, lines, grounding, and associated accessory items • Connectivity with the Broward County microwave network • Interoperability subsystem F. The System shall leverage the County's existing sites, meet the daily coverage and capacity needs, support transparent roaming and interoperability within the region, enhance interoperability within Broward County, and provide reserve capacity for use during major manmade or natural disasters and emergencies. 2. Proiect Team Motorola Solutions' Project Team will provide expertise in the following areas to support the scope required by the Agreement: project management, engineering, systems technologist, training, and service support. Provider will ensure that the persons responsible for Provider's performance of the Services under this Agreement and, to the extent applicable, expressly identified in any Statement of Work (collectively "Key Personnel") are appropriately trained and experienced and have adequate time and resources to perform in accordance with the terms of this Agreement. To the extent Provider seeks or is required to make any change to the composition of the Key Personnel, County's prior written consent is required, and Provider will provide County with thirty (30) days' advance notice (or as much advance notice as is possible if thirty (30) days' notice is not possible) regarding any such requested changes and the management plan associated with such changes. County shall not be responsible for any additional costs associated with a change in Key Personnel. Key Personnel: Motorola's Key Personnel include the following (Figure 0-1): P25 System and Services Agreement (R1422515R1/P1) Page 3 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 JORGE TIM MATTHEWS VASCONCELOS RENATO CORAZZA DAN KIMPE BEN QEMBY III KEN PASSELA Principal Design Lead Engineer- Service Support Customer Service Service Installation System Engineer Project Manager Manager Manager Technologist Implementation Figure 0-1: Motorola Solutions' Project Team for Broward County Each Provider team member, with their specialized skills, relevant experience and customer focused goals will ensure the network will be implemented on time, as specified by the County's requirements and meeting and exceeding the County's performance expectations. Provider will dedicate the proper resources to implementation of this project. Provider guarantees that all aspects of this project will have the appropriate resources. Unless otherwise agreed by the Parties, Provider's lead Project Manager is Buster Lerner and Lead Engineer -Project Implementation is Jorge Vasconcelos, both of whom will be exclusively dedicated to the performance of the Services for Broward County. 2.1 Project Staffing A. Project staffing shall be managed by the Provider based on workload and the level of effort throughout the implementation/installation process; however, the positions identified below shall be staffed throughout the duration of the project and shall not be changed without prior approval of the County. B. Provider's Project Manager: 1. Provider's Project Manager shall be the primary point of contact (POC) between the County and the Vendor. 2. Provider's Project Manager shall: bear full responsibility for supervising and coordinating the installation and deployment of the communications system; be responsible for development and acceptance of the PMP; manage the execution of the project against that plan; and oversee the day-to-day project activities, deliverables, and milestones completion. 3. Provider's Project Manager shall be responsible for coordination of the weekly status meetings. P25 System and Services Agreement (R1422515R1/131) Page 4 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. Provider's Project Engineer: 1. Provider's Project Engineer shall have the primary responsibility for managing the system design and ensuring that the system is installed in accordance with the approved system design. 2. Provider's Project Engineer shall ensure the development of block diagrams, system - level diagrams, and rack diagrams to assist the installation team in completing the system installation. 3. The Provider's Project Engineer also shall supervise the development and execution of the System Acceptance Test Plan (SATP) and the Coverage Acceptance Test Plan (CATP), and guide the County Project Team through the processes and procedures necessary to prove that the system performs as specified in the contract. No test plan will be executed until approved by the County. D. Provider's DB-Firm: Carrick Contracting Corporation DB-Firm's Consultant (Engineer of Record): Amec Foster Wheeler Environment & Infrastructure, Inc. As the systems integrator, Motorola Solutions provides the resources and project management necessary to complete the tasks required for implementation of the project. The Motorola Solutions System Integration (SI) organization is dynamic, utilizing both internal and external resources. Table 0-1 below provides a description of the roles responsibilities for the project team. Table 0-1: Project Team Roles and Responsibilities Lead Project Manager: Buster Lerner The Project Manager's primary responsibility and authority is to manage and administer the project to completion as defined within the Agreement. This individual will be County's single point of contact for all items related to the Agreement and official communications between the Manage and refine the SOW, project schedule, implementation plan, and change orders. Allocate available resources, personnel, funding, and material to ensure that the system is implemented according to the Agreement. Conduct an inventory of received equipment to ensure proper delivery. Inspect the physical condition of Motorola Solutions - supplied hardware. P25 System and Services Agreement (R1422515R1/P1) Page 5 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola • • .Responsibilities County's PM and Motorola . Ensure that Motorola Solutions -provided equipment Solutions. specifications are met. . Verify that all site preparation is complete prior to the installation of the equipment. Supervise field installation and implementation teams, ensuring all on -site installation, integration, and optimization tasks are performed within contract requirements. Ensure quality workmanship by all Motorola Solutions personnel, vendors, and subcontractors. Prepare for and conduct regular progress meetings and provide progress reports as required. Obtain County sign -off and acceptance upon completion of training, installation, and acceptance testing. . Escalate resolution of any issues encountered during system implementation. Manage the project to County's satisfaction. . Ensure successful transition to the warranty and maintenance phase. Engineering: Jorge Vasconcelos . Analyze County needs. The Motorola Solutions' . Design P25 system. Engineering team primary . Develop site design parameters. responsibilities is to ensure the Develop system documentation. technical integrity of County's system design. . Develop the proposed Acceptance Test Plan (ATP). Assist in the development of the proposed system cutover plan. Provide continuous technical support even after project acceptance. P25 System and Services Agreement (R1422515R1/P1) Page 6 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola • • .Responsibilities Systems Technologist: David Bache Provider's most advanced field technical resource ready to support County's project. . Participate in all equipment programming and configuration development. . Oversee the integration and optimization of all system hardware and software. . Participate in the ATP. Assist in the development and execution of the system cut -over plan. . Provide continuous technical support even after project acceptance. Training Consultant: Sherri Martin - Participate in the CDR to re -assess County's needs and The Training Consultant will expectations (e.g. validate student numbers, monitor develop and will manage training technology or courseware updates, etc.). deliverables through system . Participate in project status meetings to stay abreast acceptance. This individual will be of the project implementation plan and ensure the the single point of contact for training plan stays in sync. training -related matters working . Facilitate student registrations in online courseware. closely with Motorola Solutions' Conduct a Training Kickoff meeting with County's core Project Manager to ensure deliverables are in accordance with team to discuss the courses, target audiences, field the implementation plan. labs, possible training locations, and tentative training dates. Manage the collection of data needed for the instructors to prepare and/or tailor end -user materials to County's system and features. Discuss the tentative training plan/ dates with you to obtain confirmation 60-90 days prior to training. . Order training materials for end -user level courses. . Monitor course evaluations and obtain County's feedback on how training is progressing. Continue to serve as point of contact even after system acceptance for questions about training or continuing education on Motorola Solutions products. P25 System and Services Agreement (R1422515R1/P1) Page 7 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola • • .Responsibilities Account Manager: Kim Camps The Account Manager serves as the liaison responsible for addressing County's needs that arise from day- to -day operations as well as issues that arise from system implementation. . Assist in the configuration and pricing of equipment quotes. - Order, process, and manage equipment orders. . Perform a consultative role in applying Motorola Solutions' equipment solutions. Customer Support Manager: Dan - Oversee the execution of Broward County's support Kimpe contract (maintenance or warranty) by serving in the Dedicated Broward Customer role of the advocate for Broward County. Support Manager (CSM) . During the warranty phase, act as a point of contact coordinates support resources to for issue resolution and escalation, monitoring of help ensure optimal quality of Motorola Solutions' contractual performance and service (maintenance) delivery. providing review and analysis of process metrics. Field Services Organization (FSO): - Installation of RF equipment. Don Leuthke . Support Services for both Warranty and Post FSO is staffed with trained and Warranty. qualified technicians to provide . Available 24x7 On -Call Support. rapid response, repair, restoration, . On -Site Troubleshooting. installations, removals, programming, and scheduled . Customer Required Response Times. preventive maintenance tasks for - Preventative Maintenance. site standards compliance and RF . Third -Party Vendor Management. operability. - Hardware Repair Logistics coordination. . Access to Product Engineers and Designers. 2.2 Subcontractors During Project Delivery During project delivery, Motorola is authorized to utilize subcontractors as stated expressly herein or in the Agreement; any other subcontracting requires prior written approval by County Contract Administrator. Motorola is solely responsible for the Services, including the performance of its subcontractors in providing any of the Services. Motorola will coordinate core team members for effective coordination and communications and will manage subcontractor scope, performance, quality, and schedule according to the same core project management principles applied to the Motorola Solutions organization. P25 System and Services Agreement (R1422515R1/P1) Page 8 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola Solutions' Project Manager will coordinate the activities of Motorola Solutions' subcontractors to assure cost-effective performance and resolution of technical interface issues during design as opposed to during integration activities. Motorola Solutions' Project Manager will be the single authority for subcontract actions and reporting and will have the full responsibility for quality performance, schedules, and cost control. Each subcontractor will assign a lead manager who will be responsible for its company's performance. These managers will report directly to Motorola Solutions' Project Manager on scheduling and implementation issues and to the System Engineer on specific technical assignments. All subcontractors will submit as -needed progress reports to Motorola Solutions describing progress, level of effort, and anticipated problems which will be integrated into the project's tracking system. The subcontractors' weekly progress reports will serve as Motorola Solutions' primary mechanism for ensuring that they remain on track to deliver their promised results. Provider shall utilize the following subcontractors (Table 0-2): Table 0-2: Motorola Solutions' Subcontractors Subcontract•.Iroward County Project Aviat Turnkey Microwave Solution V-Comm MPE/IM Studies Carrick Contracting Corporation Engineering Services Bohren's Moving and Storage Storage and Delivery VPI Systems Logging Solution Kirms Communications Tower work Certified CBE Busines ARM Electrical Services, Inc. Provide and install DC Power Systems. Weezer Electric Provide electrical work such as: permits, installation, modifications for new and existing sites and UPS work. Lambert Brothers, Inc. Provided site construction services such as: permits, concrete, shelters and fencing installations. Mejia Telecommunications Provide services relating to towers and antenna and line systems. 3. Security/Access/Licensing Provider will cooperate with County and provide any and all information that County may request in order to determine appropriate security and network access restrictions and verify P25 System and Services Agreement (R1422515R1/P1) Page 9 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Provider compliance with County security standards. 3.1 AS Security Provider shall comply with all security requirements of the Criminal Justice Information Services (CJIS) Security Policy CJISD-ITS-COV-08140-5.2, Version 5/2 dated 08/09/2013 or later. 3.2 Licensing Provider or its subcontractor shall possess all required licensing, including state certified general contractor or state certified electrical contractor, Broward County general building contractor class "A" or master electrical contractor, and licensed engineer certified under Florida Statutes Section 471.023. 3.3 ID Badges Provider and subcontractor personnel servicing and requiring unescorted access to General Facilities must have a County issued contractor ID badge (contractor ID badge) which will be the responsibility of the contractor to obtain. Depending upon the request, the badge may carry electronic access privileges. The badge must be visible and worn at all times together with the contractor's company/business contractor ID badge. Similar to employee security/ID badges, requests for contractor ID badges are initially approved by the requesting agency director or designee and then submitted to Facilities Management Division (FMD) Security for final approval. Many Broward County government facilities will have areas designated as critical to security and public safety, pursuant to Broward County Ordinance 2003-08 Sections 26-121 and 26- 122, as may be amended. The issuance of a ID badge for unescorted access to facilities critical to security and public safety may entail a comprehensive statewide and national background check. Unescorted access to certain facilities occupied by the Broward Sheriff's Office (BSO) and the State Attorney's Office will require a national fingerprint -based records check per the Criminal Justice Information System (CJIS) policy. A Provider employee found to have a criminal record consisting of felony conviction(s) shall be disqualified from access to the State Attorney's Offices and certain BSO facilities. A Provider employee with a record of misdemeanor offense(s) may be granted access if the System Security Officer (CSO), Terminal Access Coordinator (TAC), and FDLE determines that the nature of the offense(s) do not warrant disqualification. Applicants shall also be disqualified on the basis of confirmations that arrest warrants are outstanding for such applicants. The issuance of an ID badge for unescorted access to General Facilities requires a "Level 1" FDLE background check, which can be conducted by the Florida Department of Law Enforcement (FDLE). This "Level 1" FDLE background check is the Provider's responsibility, including any associated cost. FDLE background checks can be done by Provider by phone at (850) 410-8109 or online at https://web.fdle.state.fl.us/search/app/default P25 System and Services Agreement (R1422515R1/131) Page 10 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Upon completion of the background check, Provider must attach a copy of the results to the Provider's application for an ID badge. The Project Manager or designee utilizing the service of the contractor will be the "Sponsor" and will either provide the contractor with a Provider ID Badge Request Form or assist the contractor in completing an on-line application for the County issued contractor ID badge. Requests for an ID badge requiring an FDLE background check may require lengthy processing and review by the Broward Sheriff's Office (BSO). Provider and subcontractors must therefore submit the request to Broward County Security at least two (2) weeks prior to the start of service by the contractor. When identification badges are ready, Broward County Security will contact the contractor to arrange pick up. Upon pick up, the applicant must present a valid Florida identification and must be accompanied by his or her supervisor. Broward County Security will then supply contractor ID badge valid for the anticipated period within which the work will be performed. The validity period must be clearly stated on the Contractor ID Badge Request Form; however, the period of validity will not exceed one (1) year. Background checks will be required for renewal of contractor ID badge. At the termination of the contract and separation of employee services, Provider is responsible for the collection and return of all contractor ID badge to the Project Manager and/or to Broward County Security. 3.4 Compliance Compliance with the County's security requirements is part of the overall contract performance evaluation. Final payment will, in part, be contingent on the return of all Provider ID badges issued to Provider personnel. 4. Project Schedule The Project Schedule (as referenced in Section 4.4.1 of the Agreement) is set forth in Schedule 10 and identifies key milestones necessary for project implementation and necessary to meet the proposed project schedule. Motorola Solutions will leverage its significant experience in large-scale project management to ensure successful and timely project implementation in keeping with the Project Schedule. Any changes to the Project Schedule must be approved by both parties in writing. Motorola Solutions will work collaboratively with the County to ensure the deliverables and responsibilities of both parties are met. P25 System and Services Agreement (R1422515R1/P1) Page 11 of 11 Exhibit A (Introduction) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Exhibit A-1 Radio System SOW The 700 MHz communications System as set forth in this SOW A-1 and being provided by Motorola will provide an Association of Public -Safety Communications Officials, International (APCO) P25 interoperable radio communications system to support mission -critical communications within the County. The County presently operates a 10-site Motorola Type II SmartZone, public safety -grade, two-way radio system that provides communications to first responders countywide. The system operates in the 800 MHz band and uses simulcast and trunking technology, as well as microwave connectivity, to provide a mix of analog and digital voice communications. The existing system has reached the end of its support period and will be replaced by Provider as part of this Agreement. In addition to the primary P25 system, the Provider will provide backup capabilities to include a 4-site P25 Phase II simulcast system supporting both voice and data, a conventional overlay, and a mobile communications platform. 1.1 Software. Provider will provide the Software itemized in Schedule 1. 1.2 Equipment: Provider will provide the Equipment itemized in Schedule 2, which Provider represents will provide the desired functionality as stated in the specifications. 1.3 Standards and Guidelines A. Provider shall comply with the following standards, rules, regulations, and industry guidelines: 1. American National Standards Institute (ANSI) 2. National Electrical Manufacturers Association (NEMA) 3. Electronics Industry Association (EIA) 4. Telecommunications Industry Association (TIA) 5. Telecommunications Distribution Methods Manual (TDMM) 6. National Electrical Code' (NEC) 7. Institute of Electrical and Electronics Engineers (IEEE) 8. Federal Communications Commission (FCC) 9. Underwriters Laboratories, Inc. (UL) 10. American Society of Testing Materials (ASTM) 11. National Fire Protection Association (NFPA) 1221 (latest revision) B. Provider shall comply with industry best practices for system installation, grounding, bonding, and transient voltage surge suppression (TVSS), as outlined in the Motorola R56% Standards and Guidelines for Communication Sites (latest revision). P25 System and Services Agreement (R1422515R1/P1) Page 1 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. If the requirements of this SOW conflict with any of the aforementioned standards, rules, regulations, and industry guidelines, then the more stringent of the two shall become applicable. D. Provider shall identify, coordinate and obtain all necessary applications, licenses, permits, or other approvals necessary to comply with all applicable codes, permitting or licensing requirements, and other government or regulatory requirements. Provider shall promptly notify the County of any issues that do or are likely to arise, and shall develop an appropriate action plan to resolve. Provider shall be solely responsible for all costs and fees. 1.4 Project Management Plan and Project Schedule A. Motorola shall provide and maintain a current Project Management Plan (PMP) that includes a detailed Work Breakdown Structure (WBS), project scope, deliverables, schedule, quality assurance/quality control (QA/QC) processes, and risk management sections. B. The PMP shall describe how the Provider will monitor and control the installation and deployment of the System, and mitigate risks in order to ensure that the System meets the design specifications and is delivered on time. C. Motorola shall schedule and conduct regular status meetings between the County Project Team and Motorola Project Team. The Provider shall provide a schedule for these meetings subject to the approval of the County. D. Motorola will provide and maintain the Project Schedule, which will detail tasks, milestones, start and end dates, task predecessors, and task owners based on an approved WBS in Microsoft Project format. The schedule shall represent tasks associated with completing work on all items identified in the WBS. Motorola will update the Project Schedule at least weekly, including with the actual dates as tasks are completed. E. The Project Schedule maybe modified only with the written approval of the County Contract Administrator. Motorola will provide the County will ongoing visibility to the Project Schedule with the ability for the County to make informed decisions regarding any requested changes during the project. F. Motorola shall review the Project Schedule and provide an updated progress schedule periodically to County for review and approval, and the Project Schedule shall be provided as an agenda item for all County/Providerweekly status meetings. P25 System and Services Agreement (R1422515R1/P1) Page 2 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 G. The Project Schedule shall, at a minimum, identify the schedule and applicable deadlines for the following: 1. Site surveys 2. Detailed design review 3. Required site modification 4. Required shelter modification 5. Equipment manufacturing 6. Factory acceptance test 7. Equipment delivery 8. System installation 9. System configuration 10. System optimization 11. Acceptance testing 12. Coverage testing 13. User training 14. Fleet map development 15. System cutover 16. System documentation development and delivery 17. System and equipment warranty The Project Schedule identifies key milestones necessary for project implementation and necessary to meet the proposed project schedule. Motorola Solutions will leverage its significant experience in large-scale project management to ensure successful and timely project implementation in keeping with the Project Schedule. Any changes to the Project Schedule must be approved by both parties in writing. 1.4.1 Project Punch List A. The Provider shall establish and maintain a punch list, as mutually agreed to with the County, for site facilities, equipment, and acceptance tests. B. The punch list shall be maintained in real time and published weekly. The punch list shall include the following at a minimum: 1. Sequential punch -list item numbers 2. Date identified 3. Item description 4. The party responsible for resolution 5. Expected resolution date 6. Resolution date 7. Details about how each punch -list item was resolved and tested 8. Notes about the item P25 System and Services Agreement (R1422515R1/P1) Page 3 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. If responsibility for resolving an item is transferred to another person or group, a new entry shall be added to the punch list and the original entry shall be appropriately noted. D. The Provider shall be responsible for reviewing each punch -list item and advising the County of any changes. The status of punch -list items shall be updated during each weekly status meeting. 1.4.2 Project Meetings A. A project kickoff meeting shall be scheduled prior to the beginning of the project. B. Weekly project status meetings shall be scheduled following contract award and the initial kickoff meeting. C. The Provider shall be responsible for scheduling the meetings as well as preparing meeting agendas and minutes. Meeting agenda items shall include, at a minimum, the following items: 1. Schedule review 2. Status of deliverables 3. Risk items 4. Changes 5. Plans for the next period 6. Action -item assignments 7. Punch -list review 1.4.3 Quality Control Plan It is Motorola Solutions' policy to produce and provide products and services of the highest quality that meet or exceed the needs of Motorola Solutions' customers. Motorola Solutions will perform all work consistent with high quality commercial practices and in accordance with Motorola Solutions' quality standards for fixed equipment installations and all applicable manufacturer installation and maintenance manuals. Motorola Solutions will comply with all applicable standards such as Electronics Industries Association (EIA) and FCC standards and regulations in effect at the time of contract execution. Motorola Solutions will utilize the ISO 9001 Quality Management System as the quality management system standard to control its Services and all equipment and work relating to the System. Since Motorola Solutions' QMS is an end -to -end quality management system, the entire span of the project is monitored continuously for adherence to quality deliverables. Quality is assured through vigilance in active management techniques. This section outlines the Quality Control Plan (QCP) steps P25 System and Services Agreement (R1422515R1/P1) Page 4 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 and procedures that will be used by Motorola Solutions in the implementation of the project from proposal through final acceptance. The QCP utilized by Motorola and which will be utilized for the System installation and Services under this Agreement is set forth on Schedule 6. 1.4.4 Risk Identification and Management Motorola Solutions will utilize risk management processes during the project so that any impacts to the project's overall cost and schedule are eliminated or minimized. Motorola Solutions will utilize a risk management process that is a collaborative approach with focused County involvement and participation. Motorola Solutions will identify potential risks to the project at the outset, and work closely with County to develop mitigation strategies to eliminate or minimize the impact of the risks on the project. In addition, Motorola Solutions project managers and system engineers will continue to refine the Project Schedule and system design respectively throughout project execution in order to develop cost reduction and schedule improvement plans that will be presented to County for approval and mutual agreement to implement. Risk management consists of not only identifying negative impacts to the project but also potential positive impacts which would benefit Broward County. Risk management looks for positive changes that would reduce cost and/or improve the schedule. Motorola's risk management processes will be designed and applied to achieve the following objectives: 1. Identifying potential risks that may occur during the project. 2. Mitigating the adverse events. 3. Identifying opportunities to improve the cost and/or schedule of the project. 4. Meeting project commitments and minimize any variances. During implementation of the project, Motorola Solutions will perform periodic review meetings that in addition to tracking action items on the project will monitor the status of each risk item. These reviews will analyze each risk, identify any new risks that may impact the project, assess the impact of those risks, and assign action items to develop risk mitigation plans. This review will also determine the effectiveness of any mitigation plans that have been triggered by a risk event occurring. Effective Change Management during Project Delivery Once the project design review is completed and the design is approved by Broward County, Motorola Solutions will maintain effective change management in compliance with County's policies and procedures during the project to capture the impact of any proposed changes to the requirements during implementation. 1.4.5 Project Communications Plan Motorola will provide a Communication Plan that will define and formalize key meetings, their frequency, and required attendees. This will provide Broward County with meaningful and focused meetings that accomplish the goals and objectives set prior to each meeting. Motorola Solutions' Communication Plan will identify the key stakeholders and project team members on the project. Tools will be used to store project information such as site audits and other site P25 System and Services Agreement (R1422515R1/P1) Page 5 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 development information. Broward County can quickly view the status of each individual site and the progress with respect to the schedule. Site documentation will be readily available for use by Broward County and the project team. Broward County's representatives will be supplied access to project documents such as schedules, status reports, risk logs, requirements documents, and change requests. Version control will ensure that the most current documentation and all past versions are available for review. Status reports (provided periodically as the parties agree, and upon request by County) will highlight any potential issues and identify the action being taken to mitigate them. Action items will be assigned to individuals and completion dates will be tracked to ensure the items are completed. Status Reports will also be used to provide Broward County an accurate assessment of the progress of the project and give visibility to the resource requirements to complete the near term tasks. Action item lists will be maintained and updated on a weekly basis to identify and quickly resolve identified items. Motorola Solutions team members and subcontractors will work together to enhance team and customer communications and provide a complete project record of all communications. 1.5 CAD PremierOne GPS Location Integration This feature, called ASTRO 25 Responder Location Integration, provides the following core features of ASTRO which are integrated with PremierOne CAD: The Responder Location Feature allows PremierOne to obtain the location of subscriber radios via the ASTRO 25 infrastructure. This capability allows dispatchers and supervisors to monitor the location of personnel who are using ASTRO subscribers. The location update rate is configured on a per Unit Status basis allowing specific location cadences for statuses such as Emergency, In -Route, etc. Location services are enabled on a per subscriber basis allowing agencies to limit its use to portable radios or other specific groups. 1.5.1 ASTRO Subscriber Requirements The Responder Location feature requires APX portable or mobile subscribers equipped with a GPS receiver, the current subscriber firmware version, and the Enhanced Data option. XTL/XTS subscribers do not support Enhanced Data and are not recommended for use with Responder Location. The XTL/XTS radios can send location data by the addition of a GPS Remote Speaker Mic for portables and additional external GPS receiver added to the mobiles but must use an IV&D channel set up at the sites. Sites can have both IV&D channels and Enhanced Data channels. Obviously the reporting rate will be significantly different and therefore impact the resources of the system. At a minimum, the non -Motorola subscriber would need to support the P25 Data over trunking SNDCP protocol to support the following features: • GPS • Text Messaging • Over the Air Programming (OTAP) —Also known as POP25 for Mot Subs P25 System and Services Agreement (R1422515R1/P1) Page 6 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Over the Air Rekeying (OTAR) Motorola's ASTRO Subscribers are designed to operate on the P25 SNDCP standard. The solutions are implemented, tested and certified for optimum performance with the various components operating on Motorola systems, such as the Presence Notifier, Text Messaging Service, and GPS server. While many vendors offer features that use the P25 SNDCP standard, the implementation of these features differ between the radios, the servers on the system, and applications —this means compatibility issues can exist with non -Motorola P25 subscribers. The ability to do OTAR and GPS would also depend upon the capabilities of the non -Motorola subscriber and how the manufacturer has implemented the P25 OTAR and GPS Standards. Even if the manufacturer claims compatibility, OTAR and GPS are not tested in the P25 Compliance Assessment Testing Program, meaning the applications may not be stable to a mission critical standard. IV&D features are not part of the P25 CAP Testing Program. Many other features are in the P25 Standard (such as OTAR and GPS) and should theoretically work across vendor platforms; however there are no interoperability tests defined for these features. Motorola tests every feature offered between its Subscribers and Infrastructure to a Mission Critical level of stability. In the event agencies within Broward County elect to purchase non -Motorola subscribers and wish to implement OTAR, GPS, or other P25-standard features, Motorola will fully participate with other vendors to troubleshoot and validate proper performance on the Broward County system. 1.5.2 ASTRO Infrastructure Requirements When deploying an ASTRO 25 infrastructure with Intelligent Middleware (IMW), the location functionality described with the PremierOne CAD can be enabled as part of that effort. ASTRO systems must be properly equipped and licensed to support data operation. The minimum requirements are ASTRO 7.14 infrastructure (or later) with Enhanced Data, IMW 5.x, and a GGSN and a Packet Data Gateway for each zone. Motorola is supplying all of the equipment, software, and options necessary to support the PremierOne GPS location integration. The System solution will utilize the ASTRO infrastructure. Options for the System include IMW and Enhanced Data. A capacity study must be performed to determine the system's ability to accommodate Responder Location features. 1.5.3 ASTRO System Capacity ASTRO communication systems utilize narrowband channels to support voice and data communications. The capacity of ASTRO systems, that is, the volume of voice and data traffic they can support, varies with the number of channels in the system and the system architecture (multi -site, simulcast). The ASTRO infrastructure provides two types of packet data bearer service between data enabled subscribers and host applications: P25 System and Services Agreement (R1422515R1/P1) Page 7 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Integrated Voice & Data (IV&D) is a P25 compliant data service that is integrated with trunked voice services. Trunked data allows data transmission inbound from a data enabled trunked subscriber through the ASTRO Infrastructure to a host application in a connected Customer Enterprise Network. Enhanced Data is a data solution based on Phase 2 voice signaling but uses the full channel for data. It allows data transmission inbound only, and is primarily used for periodic location update messages. Enhanced Data offers a 12 fold improvement in inbound location reporting capacity over Trunked IV&D. Its use is limited to Motorola APX subscribers. The Automatic Responder location (ARL) features can utilize an ASTRO system for data transport. The location reporting parameters configured in PremierOne have a dramatic impact on feature performance and on ASTRO data utilization. It's critical to take the ASTRO system's configuration and capacity into account when configuring these application features. The table below provides general guidelines for the channel utilization of Enhanced Data channels supporting ASTRO location data only. PremierOne CAD control signaling and other data applications such as, OTAP, OTAR, and Radio Management also require data capacity and will increase data channel utilization. ASTRO Data Solution Capacity Guidelines (Location updates only) IV&D Enhanced Data 150 Users per channel at 30 second location cadence (w/ Header Compression) 300 Users per channel at 60 second location cadence 1 channel for IMW Registration per 500 Users Motorola will perform a detailed capacity analysis prior to finalizing the PremierOne Responder Location feature configurations. Motorola's Hydra coverage analysis tool allows the system engineer to assess both the system's RF coverage and its voice and data utilization. All potential data sources will be analyzed including Radio Management, OTAP, OTAR and PremierOne. The analysis process will accurately determine the volume of Responder Location data that the ASTRO system can support. 1.5.4 ASTRO Location Accuracy There are a number of factors that impact the accuracy of ASTRO location updates. Some are a fundamental aspect of the Global Positioning System design such as the need to "see" satellites. Others are a result of the ASTRO system implementation and configuration settings. These settings can be adjusted for a specific implementation, but always involve a trade-off between competing system characteristics. 1.5.5 GPS Signal Availability The ASTRO subscriber's GPS antenna must be able to receive GPS signals from five or more satellites to accurately derive a location. Operation in buildings, tunnels, urban canyons, or densely forested areas can reduce GPS location accuracy or prevent the subscriber from determining its location altogether. P25 System and Services Agreement (R1422515R1/P1) Page 8 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.5.6 Temporary Signal Loss ASTRO subscribers cache their last known location. In the event that an ASTRO subscriber loses GPS fix, it will send its last known location in response to a location query or scheduled location update. The subscriber will send its last known location for up to 100 seconds after losing GPS fix. The accuracy of the location updates sent during temporary signal loss is a function of the subscriber speed. 1.5.7 GPS Acquisition Time When ASTRO subscribers are powered on they require a finite amount of time to accurately establish their location. This is referred to as Time To First Fix (TTFF). In the Cold Start scenario a subscriber is turned on after a prolonged period of time and does not have an accurate estimate of its position or time. TTFF in this case is <60 seconds 95% of the time. In a Warm Start scenario the subscriber is turned on and has an accurate location and time estimate. TTFF in this case is <10 seconds 95% of the time. This can result in a delay between subscriber power up and the first accurate location update. For example, if an officer turns on a portable radio when exiting the vehicle the Responder Location CAD feature may not receive an accurate location update for over a minute. 1.5.8 GPS Sleep Cycle APX subscribers use a sleep cycle to conserve battery life when GPS signal lock cannot be achieved. When the GPS receiver enters sleep cycle it powers down for 90 seconds then wakes and searches for GPS signal lock for 180 seconds. If it is able to achieve GPS signal lock it will remain awake, otherwise it will return to sleep for another 90 seconds. This behavior can result in a delay between the time when a subscriber moves into a location with GPS signal (e.g. goes outside) and its first location update. 1.5.9 Voice Priority ASTRO IV&D subscribers give priority to voice transmissions. If a user is talking on their radio or receiving a transmission from another user, their radio cannot originate or receive data traffic. This voice preference results in data packets being queued within the radio for transmission when the radio is not participating in a voice service. Packets are discarded if they are older than the 12 second queue dwell timer. This can cause a variable arrival rate of location update reports at PremierOne. 1.5.10 Open Mic on Emergency ASTRO subscribers can be configured to transmit audio after the Emergency Button is pressed. This will prevent the subscriber from transmitting location updates until the radio de -keys. 1.5.11 ASTRO Data Capacity Analysis (CapAnal-1) The objective of this activity is to ensure the Customer's ASTRO communication system is properly equipped, configured, and has the capacity to support ASTRO data dependent PremierOne CAD features such as ARL and AMS. The results of the capacity analysis provide guidance for provisioning ARL and AMS features. A Motorola System Engineer will conduct the assessment of the existing ASTRO P25 System and Services Agreement (R1422515R1/P1) Page 9 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 system. If an ASTRO system is in deployment then the analysis will be performed on the proposed ASTRO system design. Motorola will: 1. Collect and review as -built information about the ASTRO system from the Motorola ASTRO deployment team, system Manager, or Customer. 2. Document any deficiencies in the ASTRO system such as licenses, product versions, firmware versions, and system components that are required for PremierOne / ASTRO integration 3. Collect 30 days of ATIA data from the production ASTRO system 4. Analyze the ATIA data to determine the busy -hour voice load model 5. Collect PremierOne CAD provisioning parameters and usage statistics 6. Document the desired operation of ARL features including estimates of anticipated use 7. Analyze collected data and define a data load model based on the desired features and target configuration 8. Perform a voice and data capacity analysis using the Hydra ASTRO modeling tool. Multiple scenarios will be considered in an effort to optimize the use of available RF channels to provide PremierOne functionality while maintaining the required voice Grade of Service (GoS) 9. Prepare ASTRO Capacity Analysis Report that describes any required ASTRO system changes and the maximum recommended provisioning parameters for ARL features. 10. Present and discuss the Capacity Analysis Report with Customer and finalize the PremierOne ARL provisioning parameters. 11. Provision the PremierOne CAD with the agreed parameters. County will: 1. Provide access to the ASTRO Master Site for collection of ATIA and configuration data. 2. Provide information about the current subscriber types, quantities, and expected use. 3. Provide information about any other current or planned users on the ASTRO system 4. Review and discuss the Capacity Analysis report with Motorola. 1.5.12 PremierOne CAD Integration Scope of Work Motorola Solutions will perform the following services associated with the PremierOne CAD Integration: Provide all associated hardware, software, and licenses required to provide Broward County the above -stated functionality. 2. Provide engineering, project management, installation, and any other services required to fully deploy the above -stated functionality 3. Provide the solution in a manner which does not include any single points of failure, including backhaul connections and hardware redundancy, where appropriate 4. Provide connectivity between the primary and DSR master site IMW servers with the primary and disaster recovery (DR) CAD servers 5. Provide any configuration updates to the CAD or radio systems required to support this feature P25 System and Services Agreement (R1422515R1/P1) Page 10 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. Complete a data capacity study to optimize GPS polling rates 7. Install and configure interface 8. Provide CAD provisioning support 9. Provide training for County dispatch personnel regarding the use of this capability 10. Provide any integration services required with the County's Public Safety Internet (PSI) network, or any other required external network 11. Provide any required firewalls to interface between the radio network and any external networks 12. Develop an acceptance test to validate proper performance of the CAD integration, and successfully execute the test 1.6 Radio Management Motorola Solutions' Radio Management is a solution that comprehensively manages radio configuration and subscriber radios. Key Radio Management Features include: 1. Easily Searchable Radio Inventory Database. 2. Centralized Radio Configuration and Codeplug Management. 3. Automated Radio Updates of Codeplugs, Firmware, and Software Flash Versions. 4. Batch Programing of Motorola Solutions APX Radios over an ASTRO25 P25 System. 5. No Missed Calls with OTAP due to Voice Priority with Motorola Solutions' Infrastructure. Radio management enriches each agency's management of radio inventory, reduces initial programming time, optimizes routine programming maintenance and aids in software updates on a regular basis. The control, ease of use and efficiency Radio Management provides compliments the APX radio subscriber fleet and offers a dynamic and well organized fleet management solution. Using Radio Management (RM), APX Radios are assigned a codeplug template that can be unique or shared among a large group of radio users. Changes to these templates can then be performed via RM either individually or scheduled as part of a batch job by a radio technician. Regardless if the radio is being programmed as part of a large batch or an individual change, Radio Manager will track if the radios has been successfully programmed, providing a clear view of the entire radio fleet and codeplug history for each radio. Radio Management can also be used to manage the Software Flash Versions, or enabled feature sets, as well the firmware of each APX Subscriber. These updates can be performed on an individual or group basis using the RM server to manage the process. Radio Management is agnostic to how the APX radio is connected to the RM system and is able to use multiple methods to communicate with the subscriber. Regardless to how the APX radio is updated the RM server will provide a report to the radio technician of current programming status of each radio. P25 System and Services Agreement (R1422515R1/P1) Page 11 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 1.6-1: Radio Management Usability Methods -Methods Computer and Program Cable , Bluetooth ,f Wi-Fi ASTRO 25 OTAP Motorola Solutions APX subscribers on an ASTRO 25 system are also able to have their firmware updated over -the -air via the Over the Air Software Update process. The OTA Software update can send new firmware to every APX subscriber on the system in a broadcast fashion. This is done by using the voice channel to send small packets of data to the APX radios at the same time over the voice channel. This allows all of the APX radios in the fleet to compile the new firmware over a period of days and then allow the radio users to accept the new firmware when it is fully downloaded. The OTA software process runs in the background of the APX radio's operation and does not affect its' voice or data communications. This enables users to stay in the field, reducing costs and time and is exclusive to Motorola Solutions. Solution Architecture: IP Network, Network Server, Administrator Workstation(s), RM Licenses for each radio ALIAS BROADCASTS • Radio manager updates radio PTT 10 aliases in ProvisiDning Manager (PM) { NewPTTio aliipsis f madcastadand updated in all radios in thelalk9roup �pas�anwe• CORE s � x ■ SgL Pr�,illohl^tl IkllYyiFi� ■ aJup, I IP Figure 1.6-1: APX Alias Updates By using Radio Management, OTAP, OTA Software, and Alias Update, the APX radio fleet can be kept up to date with the latest software and features with minimal downtime, allowing First Responders to focus on the task at hand and not their radios. The Radio Management feature for the Astro 25 system proposed includes the following: • Radio Management Online Licenses Delivery P25 System and Services Agreement (R1422515R1/P1) Page 12 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • ADD: Radio Management Licenses Online For 10,000 Subscribers • Windows Desktop Workstation • Rack Mount Windows Database Server For Large Size Fleets • Rack Mount Windows Job Processor Server • Tech Global Evolution Series 19 inch Non Touch • Windows Laptops 1.6.1 Radio Management Scope of Work Motorola will provide the following services associated with the deployment of Radio Management: 1. Provide all associated hardware, software, and licenses required to provide Broward County the above - stated functionality. 2. Provide the solution in a manner which does not include any single points of failure, including backhaul connections and hardware redundancy, where appropriate 3. Provide engineering, project management, installation, and any other services required to fully deploy the above -stated functionality 4. Stage the equipment along with the complete system at CCSI and demonstrate the Radio Management functionality by selecting the appropriate RM Factory ATPs mutually agreed to by Broward County and Motorola. This should be done during the Contract Design Review prior to the staging event. 5. Provide installation of all servers, clients and programming laptops in the field 6. Provide any required interfacing with external networks, including but not limited to the County's PSI, leased circuits, the internet, any municipal networks (Motorola is not responsible for leased backhaul costs). 7. Provide any required firewalls to interface between the radio network and any external networks 8. Develop and load the subscriber initial templates for those subscribers that will be managed by RM. This requires a manual read of each subscriber radio that will be configured with Radio Management, from the Radio Management terminal. The labor for this effort is not included, and will be billed separately at the subscriber programmed rates defined in this contract. 9. Provide training for Broward County personnel that will use the RM feature, including system management and user training. 1.7 Over the Air Rekeying (OTAR) This feature provides the Astro 25 system the ability to change encryption keys over the air to subscribers that have the OTAR-Multikey feature. This feature requires IV&D and Presence Notifier (PN) licenses for each subscriber. All system -level licenses are being provided by Motorola. The PIN licenses also serve for other options such as OTAP and Location and only need to be purchased once. The KMF consists of three major elements: • A Client/Server software application • A Windows Computer Network • A KMF CRYPTR P25 System and Services Agreement (R1422515R1/P1) Page 13 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The KMF CRYPTR is a device that performs encryption and decryption for all security critical key management messages. Encryption Modules equipped with AES are APCO Project 25 and FIPS 140-2 compliant. KMF Redundancy allows for automatic database back up and automatic switch over from the main to the standby server in a system. Redundant servers can be co -located, or at a remote site while on the same subnet, to enhance failure recovery. The Redundant OTAR feature for the Astro 25 system proposed includes the following: • KEY Management Facility • KMF Server And Client Software • More Than 1000 Radio Users • 64 Agency Partitioning • KMF Redundancy Software • KMF DL380 G9 Server With Windows Server 2012 Embedded • USB Modem By Multitech - Required For KVL-KMF Communication Remotely • KMF CRYPTR • Basic Software Option • AES 256 Encryption Kit • Line Cord, North America • Rack Mount Kit For Cryptr II • Tech Global Evolution Series 19inch Non Touch • Computer, Z440 Workstation Windows 10 1.7.1 Over the Air Rekeying Scope of Work Motorola will provide the following services associated with the deployment of Over the Air Rekeying: 1. Provide all associated hardware, software, and licenses required to provide Broward County the above -stated functionality for the system infrastructure. Subscribers will require the addition of the OTAR/Multi-Key option and IV&D. APX subscribers shipped after 1/1/2016 has IV&D included. 2. Provide the solution in a manner which does not include any single points of failure, including backhaul connections and hardware redundancy, where appropriate 3. Provide engineering, project management, installation, and any other services required to fully deploy the above -stated functionality 4. Provide any required interfacing with external networks, including but not limited to the County's PSI, leased circuits, the internet, any municipal networks 5. Install primary and backup geographically redundant KMF servers 6. Install terminals for access to KMF servers 7. Stage the equipment along with the complete system at CCSI and demonstrate the OTAR functionality by selecting the appropriate OTAR Factory ATPs mutually agreed to by Broward P25 System and Services Agreement (R1422515131/P1) Page 14 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 County and Motorola. This should be done during the Contract Design Review prior to the staging event. 8. Perform the same ATPs after system installation and optimization using fielded Broward County OTAR capable radios. 9. Provide training for Broward County personnel that will use have access to and use the OTAR feature. 1.8 Over the Air Programming (OTAP) IV&D on the proposed ASTRO 25 digital trunked radio network provides a capability to reprogram or "reconfigure" radios units over -the -air. In addition to minimizing administrative costs and logistics issues, POP25 allows the County to respond faster to changing conditions, reprogramming your entire fleet in hours or days, instead of the weeks or even months required for a manual update. This feature, known as Programming Over Project 25 (POP25) will enable the 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. The OTAP feature for the Astro 25 system proposed includes the following: • Unified Network Services • Unified Network Services Software • Astro Network Application Interface • Mcafee Standalone Anti Virus Software • High Capacity/Geo Redundant Server • 10,001-20,000 Device Licenses For Presence • SQL SVR STD2014 EMB The Presence licenses are common for OTAR, OTAP and GPS location so these only need to be purchased once that covers all three features. Over the Air Programming Steps i a IV86 rlaNlmk �mnkiysp�. p� 0 Current radio ponfiguratipn read aver the air & reaiew$d i& Sand rbaw or updata.d configuration information & acicnmlo4arnant @ User is notifi@d and accepts changes Over -the -Air Programming steps P25 System and Services Agreement (R1422515R1/P1) Page 15 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.8.1 Over -the -Air Programming Steps Users can make, receive, and continue calls during the entire process. POP25 handles all of the same configuration parameters that can be programmed manually via Motorola CPS, including changing or adding: 1. Radio ID. 2. Talkgroups. 3. Mode names. 4. Scanning features. 5. "Rekeying" for software based Advanced Digital Privacy (ADP) encryption. 6. Call lists. 7. Conventional channels. Built-in security mechanisms prevent unauthorized users from "eavesdropping" during the re- programming process. POP25 supports read, write, and clone operations. It reads the entire memory codeplug from a radio. Once the codeplug is read, it can either write the codeplug to same or different radios or can save the codeplug. In order to reduce the write -time, POP25 writes only those parts of the codeplug that have changed using a process called differential write. In addition, using locally -stored archived codeplugs or templates, POP25 can change codeplug parameters locally and then write the codeplug over the air to a radio. Another important feature supported by POP25 is batch programming. Batch programming allows multiple radios to be reprogrammed at once without the need for the network manager or technician to individually poll and program each radio individually. This also allows programming of units to be set up and scheduled for a later time. 1.8.2 Additional Information Depending on circumstances and codeplug size, the approximate time is 2-4 minutes to read and 2-4 minutes to reprogram the entire content of a radio/codeplug. The codeplug must be read over the air and then modified. Only the parameters to be change are sent back over the air. In addition to the size of the codeplug, the timeframe required for reprogramming depends on the type of modifications, number of talkgroups or channels affected, and number of modifications. Changing fewer parameters in the radio lends to a shorter reprogram time. Batch programming enables 16 radios to be set up for programming at once. This POP25 programming feature is accomplished in a serial fashion; POP25 can be set up for the user to accept or decline a program. If the program is declined, it can be pushed automatically to the radio at the next "turn -on". POP25 can also be scheduled to send out the programming over the air at a specified time so it does not need to be attended. P25 System and Services Agreement (R1422515R1/P1) Page 16 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.8.3 Programming Over P25 Motorola's feature called POP25 allows radios to be remotely configured from your network by sending a sequence of commands over -the -air via the IV&D transport layer. POP25 enables reconfiguration of talk groups, personalities, and channels without physically touching the radio. Benefits and features of POP25 Feature of Our Our Solution to Broward County Radio is fully available for voice calls during the POP25 I Voice priority always. reprogramming. If a call is initiated or received during the No need to switch to a conventional reprogramming, the POP25 application will pause, channel to make a voice call. allowing the call to proceed. Once the call is complete, No need to manually restart the POP25 reprogramming will resume without any user programming after the call and/or lose involvement. track of who got programmed. The POP25 feature can be configured to allow the user to User control of POP25 reprogramming is accept, delay, or reject the new radio configuration available if desired. based on their current situation. This prevents the radio from being reset without the involvement of the user. The duration of the reprogramming is based on the size Reprogramming to be performed as of the radio codeplug, enabling smaller codeplugs to be quickly as possible. downloaded more efficiently. Typical download time is approximately 2 minutes. The POP25 feature can only be enabled/disabled by using Security the Customer Programming Software, and Advanced System Key. This prevents users from inadvertently disabling the feature. The radio user is free to roam from site to site while the Mobility download is taking place. POP25 can reduce the total amount of time spent per radio unit update by up to 85%, allowing users and equipment to remain operational in the field. Assuming one reprogramming event every other year over the average lifetime of a radio (10 years), the total coordination and programming time can be reduced from 3.5 hours to only 30 minutes. Motorola uniquely provides voice priority over data that is configurable. Other substantial benefits include: 1. No loss of communications while reprogramming occurs. 2. Programming resumes automatically after interruption. 3. Quicker network optimization. 4. Eliminates time spent tracking assets for reprogramming. P25 System and Services Agreement (R1422515R1/P1) Page 17 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Over -the -Air Programming utilizes the same CPS that is used every day to program radio units. POP 25 supports all read, write, and clone operations. Codeplug templates can be changed locally, and then sent over the air to the radio. Most of the editable CPS parameters can be changed via over -the -air programming, including radio personalities, talkgroups, channels, and sites. The only exception is Channel Announcement (audible indication of channel on the radio), which is not available for modification over the air. 1.8.4 Voice Priority Users retain full use of the radio during configuration data transfer. Radio voice calls take priority over data transfers, ensuring that Over -the -Air Programming will not interfere with the user's ability to communicate. Voice conversations will not be interrupted during the data transfers. While data is being transferred to the radio, the radio user can continue normal operation without any loss of productivity. Once the download is complete, the radio user receives a visual status in the display and an audio tone. The user takes action by accepting the changes immediately or delaying the update until a more convenient time. 1.8.5 User Interaction Radio codeplugs sent by the programmer will be automatically received by radio users. No interaction is required during the download process. During this process, the LED light on the radio will blink, and the data icon will appear on the display (if applicable). Following the data transmission, an audible notification will alert the user that they can accept, delay, or reject the update to the codeplug. If the user has a non -display model of radio, the radio will require a power cycle to accept the codeplug changes. The programmer can remove the "reject" option from the radio user, allowing the radio user to only accept the codeplug, or delay until a later time. The radio will continue to beep until an action is taken, notifying the user of the action required. If no action is taken and the radio is powered down, the radio will accept the codeplug upon power up. The CPS user (programmer) will receive an acknowledgement that the download to the radio unit was successful. The programmer does not receive the choice of the user to accept, delay, or reject. If the radio is turned off during the codeplug transmission, the programmer will receive notification that the download was unsuccessful. The CPS will timeout in 180 seconds if the transmission had started, and was interrupted by the power cycle. If the radio is not currently in the coverage area, or not powered on, the Presence Notifier will indicate that the IP address is invalid and the radio is not found. Should a radio user need to make a voice call during a codeplug download, the radio will leave the data channel upon PTT and move to a voice channel. The radio will remain on the voice channel for the duration of the voice conversation. While on the voice channel, no data is transmitted. The codeplug download will resume following voice traffic, if the voice conversation is less than 180 seconds. However, if the voice conversation is longer than 180 seconds, the codeplug write will cancel automatically and the programmer will need to reinitiate the download. P25 System and Services Agreement (R1422515R1/P1) Page 18 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.8.6 Coverage Over the Air Programming allows an authorized person to wirelessly access and update a data enabled ASTRO 25 mobile and portable radio wherever they are located in the coverage footprint of an Integrated Voice and Data system. There is complete system -wide mobility within coverage of the IV&D system. The Presence Notifier tracks the radios within the network by IP address. This allows the system to know whether the radio is turned on or off. The CPS interfaces with the Presence Notifier to recognize when the radio is on and within coverage area of the system. 1.8.7 Timing The time it takes to read or write a radio is dependent upon the size of the codeplug and the utilization level of the IV&D pipe. Typically, on a system where the data pipe is not heavily active, a 50K codeplug takes around 2 minutes. It is important to note that during the read and write process, voice activity can take priority so codeplug changes do not interfere with mission critical situations. (The voice priority can be configured using the network management configuration applications) 1.8.8 Over the Air Programming Scope of Work Motorola will provide the following services associated with the deployment of Over the Air Programming: 1. Provide all associated hardware, software, and licenses required to provide Broward County the above -stated functionality for the system infrastructure. Subscribers will require the addition of the OTAP option and IV&D. APX subscribers shipped after 1/1/2016 have IV&D included. 2. Provide the solution in a manner which does not include any single points of failure, including backhaul connections and hardware redundancy, where appropriate 3. Provide engineering, project management, installation, and any other services required to fully deploy the above -stated functionality 4. Provide any required interfacing with external networks, including but not limited to the County's PSI, leased circuits, the internet, any municipal networks 5. Stage the equipment along with the complete system at CCSI and demonstrate the OTAP functionality by selecting the appropriate OTAP Factory ATPs mutually agreed to by Broward County and Motorola. This should be done during the Contract Design Review prior to the staging event. 6. Perform the same ATPs after system installation and optimization using fielded Broward County OTAP capable radios. 7. Provide training for Broward County personnel that will use have access to and use the OTAP feature. P25 System and Services Agreement (R1422515R1/P1) Page 19 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.9 Automatic Resource Location (ARL) 1.9.1 ASTRO 25 OUTDOOR LOCATION Dispatchers need to be able to quickly identify the location of outdoor personnel whether they are in a life threatening situations or exercising their daily schedules. The ASTRO 25 Outdoor Location Solution is a resource tracking solution that uses Global Positioning System (GPS) satellites to provide operators with the ability to accurately locate and track outdoor personnel and assets, on demand, and in real- time. The ASTRO 25 Outdoor Location Solution does not contain a mapping application. This would be provided within the CAD applications. In this case, it would be part of a Premier 1 CAD system. 1.9.2 ASTRO 25 INTELLEGENT MIDDLEWARE (IMW) PRESENCE Presence within an ASTRO 25 network is used for monitoring the availability and absence of subscriber units with Automatic Registration Service (ARS) capabilities within an ASTRO 25 radio network. Presence is also required for Over the Air Programming or POP25. If POP25 was already purchased, then the presence does not have to be purchased with the location option. The Presence service within IMW is responsible for monitoring the presence of AIRS capable subscriber units and reporting their state. One of its primary purposes is to provide the IP address of subscriber units, thus avoiding the need to provision the subscriber units with the IP address of the various applications servers. The GPS Location feature for the Astro 25 system that shall be provided includes the following: • Unified Network Services * • Unified Network Services Software • Astro Network Application Interface • Mcafee Standalone Anti Virus Software • High Capacity/Geo Redundant Server * • 10,001-20,000 Device Licenses For Presence • SQL SVR STD2014 EMB * • 10,001-20,000 Device Licenses For Location • Integration for P1 CAD mapping * These are not required if POP25 was already added �'�� ��Z�l_�li[�1►I�1►ll��y;dl��>i1�:1 The Location on PTT feature enables ASTRO 25 trunked radio systems to continuously track the location of individual radio users while they are involved in voice calls. With each transmission, the APX radio with Location on PTT will send its Global Positioning System (GPS) location to the dispatch mapping application. ASTRO 25 Location on PTT provides timely, accurate location information when needed most — during emergencies and critical incidents. GPS location data is sent with each PTT or P25 System and Services Agreement (R1422515R1/P1) Page 20 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 "hot mic" activation, following an emergency button press or man -down situation. This allows dispatchers to effectively coordinate back-up and support services during an emergency situation. Additionally, Location on PTT increases location accuracy even during times when the radio system is heavily congested with voice traffic. Every time a first responder presses the PTT button, their location is updated, helping dispatchers make quick decisions based on current location data. With Location on PTT, radios will no longer be required to complete a call and connect to a data channel in order for a location update to be sent to dispatch. An APX radio in a group call or emergency call sends its current GPS location over the voice channel during each transmission. Location data is embedded directly in the voice stream and sent continuously with no impact to voice quality or performance. Radios with Location on PTT can be configured to send their location after each PTT during group calls and during emergency calls. Location on PTT can be sent over the voice channel, in addition to cadence, distance or manual updates already being sent over the data channel. Once location data is received by the Packet Data Gateway (PDG) at the ASTRO 25 Master Site, it is then forwarded on to the mapping application via Intelligent Middleware (IMW). Dispatch can then use the mapping application to view the location of any APX radio, in near real-time, for faster emergency responses. 1.9.4 ASTRO 25 ENHANCED DATA ASTRO 25 voice systems have been building to portable grade coverage specifications for several years. The ASTRO 25 system provides all of the components and the wide -area system coverage necessary to perform a mobile and portable GPS reporting function. Motorola understands the customer's needs to poll for location data more frequently. Constant tracking of the locations of all field personnel has been a need for the Public Safety sector for a long time. Enhanced Data on ASTRO 25 Integrated data will provide the following benefits: • Provide outdoor location data for all of the users with a faster polling rate. • Increased AVL and telemetry capacity as compared to Classic P25 Integrated Data. • Ability to have dedicated, data only, Enhanced Data channels. • Ability to prioritize data over non Emergency voice calls on Enhanced Data channels. • ASTRO Enhanced Data is an optional proprietary feature for the 7.14 release and beyond. Since the Broward County release is 7.17, this feature is available today. The Enhanced Data feature for the Astro 25 system includes the following: • Trunked Enhanced Data • 10,000 Enhanced Trunked Data User Licenses • Simulcast Remote Site Licenses IV&D+ENH Data 1.9.5 Automatic Resource Location Scope of Work Motorola will provide the following services associated with the deployment of Automatic Resource Location: P25 System and Services Agreement (R1422515R1/P1) Page 21 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. Provide all associated hardware, software, and licenses required to provide Broward County the above -stated functionality for the system infrastructure. Subscribers will require the addition of the GPS, IV&D and Enhanced Data options. APX subscribers shipped after 1/1/2016 have GPS and IV&D included. 2. Provide the solution in a manner which does not include any single points of failure, including backhaul connections and hardware redundancy, where appropriate 3. Provide engineering, project management, installation, and any other services required to fully deploy the above -stated functionality 4. Provide any required interfacing with external networks, including but not limited to the County's PSI, leased circuits, the internet, any municipal networks 5. Provide any required firewalls to interface between the radio network and any external networks 6. Stage the equipment along with the complete system at CCSI. Since only the IMW servers will be staged with the system that hosts the Location application, testing will be limited. The function of context activation can be demonstrated which shows that an IP assignment has been activated for a subscriber. 7. The integration will be completed and tested with PremierOne CAD in the field and in alignment with the scope and services defined in Section 1.5. 8. Provide system manager training for Broward County personnel that will be responsible for managing the ARL components of the radio system P25 System and Services Agreement (R1422515R1/P1) Page 22 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Phase Overview and Detailed Implementation Process The step-by-step implementation plan for the project is identified in Figure 1 below. Note: not all Phases are sequential, including without limitation that Installation, Civil Work, Subscriber Installation, and Training may occur at any time during the project as approved by the County or the applicable Authorized Third Party User. • Contract award • Review Gantract * Site acquisition • Process Manufacture She development • Contract design • Site zoning equipment list M❑t❑role FIVE She Development edministratign + Design approval • Site Acquisition • Trial validntipn Manufacture Complete • Proiect kicknft and Zoning • Order hrld god MatoroJa subscriher Site Flevelnpment Complete Manufacture non- Acceptance Motorola equipment • Develop fleet map • Develop templates Ship to staging • Stage system Perform staging ATP • Install Fixed Optimize • Perform • Pelforni R-56 • Frogram and • Cutover Occurs during equipment system FIVE training Audit install mobiles • gesolve punch the entire • Install Console Link • Training • Perform • Program and list project • Equipment verification cornpleta EquipmantIasting dis6ribute • Transition implementation irl-w' $lion Cvmpiete Perform portables sgrviCejPT Project status complete P optimization P Funct�ooaIiesting • Subscribers Finalize • Installation Perform complete documentatiDn meets meetings Progress Acceptarce Coverage tasting • Final system milestpne • SATP a cceptance acceptance submittals Figure 1- Motorola Solutions' Systems Integration Approach 2.1 Phase Overview This project will include the following major Phases: 1. Contract/Project Kickoff. 2. Design Review. 3. Order Processing/Manufacturing. 4. Fleet Mapping. 5. Staging and Shipment. P25 System and Services Agreement (R1422515R1/P1) Page 23 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. System Installation. 7. Optimization. 8. Training. 9. Cutover. 10. Preliminary Acceptance Testing. 11. Final Acceptance. The Work Breakdown Structure (Figure 2) identifies the specific tasks, responsibilities, and deliverables that comprise each phase: 1MWJ1JN I JUL I A 611iS P I OCT I NOVI DELI IJAN 1 FEB IMARI APR I MAY I J N I JUL I A0G I SEP I OCT I NOVI DECI Contract Site Surveys = Contract Design Review Order Processing Fleet Mapping Manufacturing and Staging r Factory System Acceptance Test (FATP) Construction Phase Microwave Installation FIVE Installation Subscriber Installation — — — — — — — — — — Dispatch Center Equipment Installation (68 Op Positions) = System Optimization Acceptance Testing & Cutover - S Training 30 Day Operational Test IMIiIli Finalize and Resolve Punchlist 1 Figure 2 - Preliminary Project Schedule Phase 1: Contract/Project Kickoff Final Acceptance 1 The project will begin with a Project Kickoff meeting, which will include key Broward County and Motorola Solutions project participants. The objectives of the kickoff meeting include finalization of the P25 System and Services Agreement (R1422515R1/P1) Page 24 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 communication plan that contains the contact information for both entities. The meeting will also provide a preliminary Project Schedule review, and align expectations regarding the overall PMP. This will be a joint meeting in order for all the participants to provide their concerns and perspective on the project implementation. Phase 2: Design Review The Design Review phase sets the direction of the project on the road to success, from the start of implementation all the way through to final acceptance. At the review meetings, the County and Motorola Solutions will work together to confirm the accuracy of every detail of the design. During the design review, Motorola Solutions and Broward County will review the proposed solution, including the preliminary design and statement of work, which reflects Broward County's requirements as defined in the RFP. Also during the design review, Broward County and Motorola Solutions will optimize the proposed phased implementation approach to save time and cost while meeting the needs and requirements of Broward County. Motorola Solutions will provide guidance and cost-effective solutions that anticipate not only the current needs and requirements but also allow for enhancements to meet Broward County's future needs. Throughout this interactive process, Broward County (including, to the extent involvement is approved by the County, its member agencies and other stakeholders) will be afforded opportunities for participative involvement in cost savings, risk mitigation, and the change management process. The design review shall be conducted in two subphases, as defined below: Phase 2A: Preliminary Design (45 Days After Notice to Proceed (NTP)) The Provider shall submit the Preliminary Design package in their native editable format and Portable Document Format (PDF) within 45 days after the applicable Notice to Proceed for SOW A-1 is issued. The Preliminary Design Package shall include the following: A. QA/QC plan B. Detailed Project Schedule (in Microsoft Project) C. System -level and block diagrams (in Visio format) D. Patching schedules and termination details for all cabling necessary for a complete record of the installation E. Radio and microwave channel plans F. Equipment room overview drawings G. Equipment rack/cabinet elevation drawings H. Tower profile drawings indicating antenna -mounting locations Detailed lists of materials for each site J. 30-day Operational Test Plan (OTP) K. Coverage Acceptance Test Plan (CATP) P25 System and Services Agreement (R1422515R1/P1) Page 25 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 L. Updates to Acceptance Test Plans to cover OTAR, OTAP, Radio Management, and Automatic Resource Location Phase 2B: Final Design (90 Days After NTP) Provider shall submit the Final Design package 90 days after the Notice to Proceed for SOW A-1 is issued. The Final Design Package shall include the following: A. Any updates to previously submitted design information B. Cutover plan C. System operation and maintenance manuals for all equipment D. Factory test data E. Site installation drawings F. Structural analyses and results G. A detailed Staging Acceptance Test Plan outlining a comprehensive series of tests that will demonstrate proof of performance and readiness for shipment Phase 3: Order Processing/Manufacturing Upon finalization of the system design at the design review and written approval of the Final Design by County Contract Administrator, Motorola Solutions will place factory orders for the System Equipment. Motorola Solutions will place factory orders for all Motorola Solutions -manufactured equipment as well as all third -party equipment. Motorola Solutions will also manufacture Motorola Solutions equipment and track third -party equipment suppliers. Phase 4: Fleet Mapping As the system is being installed, the County and Motorola Solutions will develop the plan for controlling radio communications within and across the County's groups, otherwise known as "fleetmapping." Motorola Solutions will be responsible for installation of mobile subscribers per SOW A-4. Motorola Solutions will have a two touch process when programming the subscribers. The second touch will remove the legacy system code plugs. Phase 5: Staging and Shipment The System Equipment will be staged at Motorola Solutions' Customer Center for Solutions Integration (CCSi), an ISO 9000 certified process. Provider will conduct a comprehensive staging acceptance test plan during Staging to confirm proper system operation in a factory environment. Provider will label and inventory the Equipment at CCSi in an efficient and consistent manner in compliance with the County's inventory procedures or as otherwise instructed by the County Contract Administrator. For all shipments of System Equipment, Provider shall submit a bill of materials/packing list with two copies for each shipment of equipment. The packing list shall include the following information at a minimum for each component per site (tower, dispatch location, etc.) included in the packaging: P25 System and Services Agreement (R1422515R1/P1) Page 26 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. Manufacturer 2. Model 3. Serial number 4. Unique identification of the package containing the item All items shipped by Provider or its suppliers will include the above information in both Excel and barcode format. Phase 6: System Installation Following factory staging and associated testing, the equipment will be shipped to the Motorola Solutions storage facility, prior to installation. As the equipment arrives on -site, Motorola Solutions personnel will perform site audits to ensure that each site is ready for equipment installation. After the equipment is installed, Motorola personnel will conduct equipment measurements to ensure that all appropriate levels have been set, and that the equipment is functioning according to the system design and manufacturer's specifications. Motorola Solutions local installation teams will install per Motorola quality standards (R56) and Motorola Solutions' team will inspect the equipment at Broward County sites as they are installed and commissioned. Phase 7: ODtimization Once all equipment is in place and fully installed, Motorola Solutions will configure, optimize and program all system equipment and subsystems as agreed upon during design review. During this phase, the System Technologist will perform installed component level testing on the RF equipment. A County representative will witness these tests at the time each site is optimized for operation within the system. Note that this optimization could occur outside of the 8:00 a.m. to 5:00 p.m. workday depending on schedule, if determined appropriate by the County Contract Administrator. Motorola Solutions System Technologists will be on site for this phase and will prepare the system for acceptance testing. Phase 8: Training Motorola Solutions will provide training timed appropriately for Broward County to ensure comfort with the system. The training plan will be finalized during Design Review and will be agreed upon between Motorola Solutions and Broward County. Motorola Solutions will also have engineers and technicians working with Broward County to answer any questions regarding the new system. The detailed training plan for Broward County is stated in Schedule 3. Phase 9: Cutover Planning The new system cutover plan will be finalized during Design Review. Motorola Solutions will work with Broward County to ensure smooth cutover for the County. Details of the cutover are set forth in Section 1.8.1 and following. P25 System and Services Agreement (R1422515R1/P1) Page 27 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Phase 10: Preliminary Acceptance Testin Preliminary Acceptance will include Coverage Testing, 30-Day Operational Test, and preliminary Acceptance Testing. Any punchlist items identified during the acceptance testing process will be resolved by Motorola before resubmitting for testing. Acceptance testing shall follow the procedures set forth in the Agreement. Phase 11: Final Acceptance Upon completion and preliminary acceptance of the Services provided by Provider pursuant to SOW A- 1, A-2, and A-3, the System will be subjected to Final Acceptance testing which shall govern, upon successful completion of all final acceptance test criteria, County's written issuance of notice of Final Acceptance. 2.2 Detailed Phase Description and Work Breakdown The following sections define in detail the expected project phases for the planning, design, manufacture, installation, optimization, and testing of equipment proposed. Each phase of the project defined in this Implementation Plan includes a responsibility matrix. These matrices define the responsibilities of both Motorola Solutions and Broward County and detail the tasks and deliverables for each phase. Each phase also includes completion criteria. Phase 1: Proiect Initiation and Kickoff Meeting Motorola Solutions' project management team will initiate a project kickoff meeting that includes key Broward County and Motorola Solutions project participants. The objectives of the kickoff meeting include the following: 9. Introduction of Motorola Solutions and the County's Project Managers as the single points of contact with authority to make routine project decisions. 10. Introduction of ASTRO 25 project team participants. 11. Review of the roles of the project participants to identify communication flow and decision -making authority between participants. 12. Review of the overall project scope and objectives. 13. Review of the resource and scheduling requirements. 14. Review Project Management Plan and processes. During the Project Initiation phase, Motorola Solutions will work with the County to review and finalize the following project processes and procedures: 15. Detailed Project Schedule. 16. Risk Management Plan. 17. Change Control (Change Management) Plan. 18. Issues Document and Action Item Log. Responsibilities and deliverables for Motorola Solutions and the County during the Design Review phase are defined in the following table: P25 System and Services Agreement (R1422515R1/P1) Page 28 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Phase 1 Responsibility Matrix ResponsibilityDeliverable Documented Project Personnel Initiate the project with a Kickoff Motorola Solutions and Broward Names, Responsibilities, Meeting. County Contacts, and Project Review Procedures Begin creating Risk Management Motorola Solutions Initial Risk Management Plan Plan. Define format of the Issues and Motorola Solutions Initial Issues and Action Item Log Action Item Log. Review change control procedures with County Project Motorola Solutions Initial Change Control Plan Manager. Work with Motorola Solutions personnel in finalizing and Broward County Approved Initial Change Control approving the Change Control Plan Plan. Develop a communication plan to address the types of communications that will be established such as the weekly status meetings and status reports. Weekly status meetings Motorola Solutions Communications Plan will be face to face. The communication plan will also indicate the appropriate points of contact for different types of communication. Existing system documentation. Motorola Solutions County's Existing System Documentation Updated Quality Control Plan Motorola Solutions Updated Quality Control Plan Completion Criteria This task will be considered complete when the project kickoff session has been held with Motorola Solutions and the County representatives in attendance, and when project scope, schedules, procedures, roles, and responsibilities have been documented and agreed upon. Phase 2: Detailed Design Development and Review After the Project Initiation and Kickoff Meeting, Motorola Solutions will meet with the County's project team to achieve written agreement on the contract system design, identify any special system or P25 System and Services Agreement (R1422515R1/P1) Page 29 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 product requirements and their impact on system design or implementation, and refine the system implementation plan and plan documentation. Motorola Solutions' proposed comprehensive system design will serve as the baseline design for the Design Review. During the Design Review phase, Motorola Solutions and the County will work together to finalize the system design. The County and Motorola Solutions will review and finalize the design through analysis of the system functionality, interface requirements, and end -user requirements, as mutually agreed upon by Motorola Solutions and the County. Document List Motorola Solutions will develop baseline versions of the following documents in cooperation with the County. 19. Project Schedule. 20. Statement of Work. 21. System Description. 22. Design of the P25 System. 23. System Block Diagrams. 24. Site Equipment Information: — Power Consumption Data. — Site Heat Output Data. 25. Civil Site Audits (Substantial Completion Acceptance Criteria, per SOW A-2) 26. Testing Plans: — Staging ATP — Coverage ATP — Field ATP — 30-Day Operational Test — System ATP — Final ATP (inclusive of Radio System, Microwave System, and Facilities and Infrastructure Services) 27. Training Plan. 28. Transition/Migration Plan. 29. Antenna system drawings Some of the documents will be high level in their initial form, and require further development through the course of the project implementation. All documents will be finalized prior to commencement of Final Acceptance testing. During Detailed Design Development and Review, Motorola Solutions and the County will have the general responsibilities shown in the following table: P25 System and Services Agreement (R1422515R1/P1) Page 30 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Phase 2 Responsibility Matrix Task ResponsibilityEM AK Deliverable Review baseline design with the County. Motorola Solutions and the County will participate in a Motorola Solutions and Broward Preliminary Design Package series of meetings where the County submitted to County Preliminary Design will be developed and reviewed. Update the Preliminary Design to the Final Design based on the design feedback from the Motorola Solutions County, Motorola Solutions will present the design documents listed above. Final Design incorporating Final Design Package submitted County's feedback will be Motorola Solutions to County for review; Final developed by Motorola Design finalized and approved by both Parties Completion Criteria This activity is complete when all the Final Design has been approved in writing by the County Contract Administrator and all associated documentation (Preliminary Design Package and Final Design Package) has been delivered to the County, reviewed by the County, and approved by the County. After written approval of the Final Design by County, Motorola Solutions will schedule all factory orders for shipment to meet the approved project schedule. Specific design activities are described in the following sections. Some detailed design development activities will encompass the review and finalization of multiple documents. The following sections provide more specific detail with respect to Design documentation. A. Project Schedule The objective of this task is to further develop the Project Schedule contained in the proposal and incorporate any updates from the Pre -Contract Infrastructure Design. The Project Schedule will be based upon the requirements identified in the Detailed Design Review and will take into account the project objectives, plans, schedules, approvals, priorities and inter- dependencies among tasks. These tasks will be established through a change order process and mutually agreed upon between the parties at the end of the Design Review. The resulting document defines the specific project tasks to be completed. P25 System and Services Agreement (R1422515R1/P1) Page 31 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Responsibilities and deliverables for Motorola Solutions and the County during the Project Schedule phase are defined in the table below. Project Schedule Responsibility Matrix ResponsibilityTask & Review with the County personnel the identified implementation tasks, priorities, inter -dependencies and other requirements needed to establish the Project Schedule. The Project Schedule will identify Motorola Solutions Project Schedule Review key project milestones, in addition to tasks that will require interruption of existing communications in order to move the new system into live operations. Review the Project Schedule with the County personnel and make changes and/or Motorola Solutions Project Schedule Completion corrections that are mutually agreed upon through the change order process. Review the Project Schedule and identify in writing any specific Broward County Project Schedule Approval deficiencies found within 10 business days of receipt. Completion Criteria This task will be considered complete upon mutual agreement of the parties to implement in accordance with the Project Schedule that has been developed within the Preliminary Design review. B. Finalize Space, Power, and HVAC Requirements Motorola Solutions will work with the County to finalize space, power, and HVAC requirements for the sites based on the agreed upon Final Design. Prior to the finalization of space, power, and HVAC requirements, Motorola Solutions will have completed the overall system configuration and architecture design jointly agreed upon by the County and Motorola Solutions. Motorola will provide a comprehensive report (including floor layout and rack drawings, as well as power consumption and heat output specifications) report identifying all applicable space, power and HVAC requirements at each applicable location required for the System. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below P25 System and Services Agreement (R1422515R1/P1) Page 32 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Finalize Space, Power and HVAC Requirements Responsibility Matrix Completion Criteria This task is considered complete upon the County receiving the detailed report of all applicable space, power, and HVAC requirements. C. Transition/Migration Plan The implementation will require a detailed transition plan for a smooth transition of subscriber radio users and dispatch console operators from the existing radio system to the P25 radio system. During the Contract Design, a high-level transition plan will be developed as the implementation proceeds, further detail will be incorporated into the transition plan. Responsibilities and deliverables for Motorola Solutions and the County during the development of the initial Cutover/Migration Plan are defined in the table below. The final transition plan will be developed during Preliminary and Final Design review. Transition/Migration Plan Responsibility Matrix ResponsibilityTask County will provide existing system, dispatch, vehicles, and Existing System, Dispatch, user information that must be Broward County Vehicle, and User Information taken into account in developing the detailed Cutover Plan. An initial Cutover/Migration Plan will be mutually agreed upon, which identifies when and how Motorola Solutions and Broward specific agencies will migrate County Initial Cutover/Migration Plan from operations on the existing system to operation on the new system. Completion Criteria This task will be considered complete when the high-level cutover plan is mutually agreed upon by the County and Motorola Solutions. P25 System and Services Agreement (R1422515R1/131) Page 33 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 D. Acceptance Test Plan Procedures Motorola Solutions will update the proposed Staging ATP, Coverage ATP, Field ATP, 30-day operational test, and System ATP as part of detailed design development and review with the County to ensure that the appropriate testing is included, leading to the completion of the ATP documents. The ATP documents will identify the overall test structure for the project, including a list of the tests to be performed. Further development of the ATP document will be required over the course of the project, including development and agreement on test methodology. The ATP includes the acceptance criteria to ensure the equipment operates in accordance with the contract. The County reserves the right to request additional tests within the ATP to validate the performance of any equipment provided. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below. Phase 2 Responsibility Matrix Task Responsibility Deliverable Work with the County to develop the initial ATP document. Review the overall approach to Motorola Solutions Initial ATP Document Complete testing including hardware, software, and final system acceptance criteria. Review and approve updates to Broward County Approval of updated ATP the ATP documents. Documents Completion Criteria This task is considered complete upon the County's acceptance and approval of the updated ATP documents. Phase 3: Order Processing and Manufacturing Motorola Solutions will process orders for equipment and begin equipment manufacturing. Motorola Solutions will place factory orders for the Equipment necessary for the Equipment. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below. Order Processing and Manufacturing Responsibility Matrix Task Responsibility Factory orders placed for all Motorola Solutions Orders for Motorola Solutions - Motorola Solutions manufactured Equipment manufactured equipment. Order placed for any third -party Motorola Solutions Third -party Equipment Orders equipment. P25 System and Services Agreement (R1422515R1/P1) Page 34 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Completion Criteria This phase is considered complete when all equipment orders have been placed. Phase 4: Fleetmap Development Motorola Solutions assumes that the fleetmap to be used for the new P25 system will be similar to County's existing fleetmap, however Motorola will assist the County with fleetmap development regardless of the extent to wish changes will be made to the existing fleetmap. The fleetmap organizational structures of the existing system and the new ASTRO 25 system will be similar, allowing for a streamlined transition. For existing radios that will be swapped out to operate on the ASTRO 25 system, the user interface can be configured to be similar to existing configuration, or group names and switch positions can be modified as necessary. Motorola will develop transitional templates for new radio template development with input from the County. Motorola Solutions will work with the County to identify the differences and create the fleetmap for the new P25 system. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below. Fleetmap Responsibility Matrix Responsibility Consult with partners (agencies) to confirm that the fleetmap Broward County User Information/Data remains the same. Develop new subscriber and Templates Creation and console templates. Motorola Solutions submission to County for review and approval Translate/develop fleetmap for Conceptual Fleetmap and the new P25 system. Create Associated Device Configuration templates for new subscriber Motorola Solutions Templates and submission to radios and new dispatch County for review and approval consoles. Test the fleetmap for radios and Motorola Solutions and Broward Fleetmap Tested and Approved consoles. County Completion Criteria This task will be considered complete when Motorola Solutions has delivered applicable training and the required templates and the same have been reviewed and approved in writing by Broward County, and the fleetmap is tested and approved by both Motorola and County. P25 System and Services Agreement (R1422515R1/P1) Page 35 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A. Frequency Planning Motorola Solutions and the County will work together to finalize the frequency plan for the system. Motorola Solutions will evaluate frequency compatibility based on available spectrum identified by the County. Motorola Solutions will recommend a frequency plan for the new system. Motorola Solutions will assist in the preparation of the application per County's RFP. Responsibilities and deliverables for Motorola Solutions and the County during the Frequency Planning phase are defined in the table below. Frequency Planning Responsibility Matrix ResponsibilityTask Request from FCC for Broward County Agreement on the Frequency assignment of frequencies. List Motorola Solutions will evaluate each site within the coverage design for its compatibility with the available frequencies. Motorola Solutions will Motorola Solutions Recommended Frequency Plan recommend a frequency plan. (Frequency assignments are required in advance of the manufacture of equipment). Motorola Solutions will evaluate the assigned frequencies per site and adjust the RF filtering Motorola Solutions Revised RF Filtering Design system design to accommodate these frequencies. Motorola Solutions will execute a computer -based intermodulation analysis, and identify probable interference conditions. This will be factored Intermodulation Analysis and into frequency planning. Any Motorola Solutions other County Frequency probable interference concern Recommendations that cannot be addressed through the planning process will be shared with the County, along with a recommendation for remediation. Approval of the frequency plan. Broward County LMR Frequency Plan Approval Complete FCC frequency license Broward County License Applications Complete applications for LMR system. P25 System and Services Agreement (R1422515R1/P1) Page 36 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Completion Criteria This task is considered complete when the frequency plan is finalized and approved in writing by Broward County and the FCC microwave license applications have been approved and licenses granted Phase 5: Staging and Shipment Motorola Solutions will provide factory staging for the System at Motorola Solutions' CCSi in Elgin, Illinois. Motorola Solutions will stage equipment in a single phase to facilitate a more efficient, faster staging activity, and to enable a shipping plan that will send parts of the system (RF sites, dispatch communications sites and microwave) to a single storage location. This approach will reduce the inefficiency of multiple handlings of equipment after shipping, and have a material effect on the installation process by making equipment available to installers closer to where it will be installed. Motorola Solutions will assemble the system hardware at CCSi, including the Master Sites, RF simulcast cell, and Dispatch Communications Centers. Physical setup, racking, and location of hardware will comply with the County's approved equipment layout plans. Cables will be cut and labeled with information to clarify interconnection for field installation and to fit the room layout plan specifications. All provided inter -rack and inter -equipment cables will have connectors attached and tested. After assembling the equipment, Motorola Solutions' staging team will power it up, load software, set levels, program, configure, and optimize the equipment. System parameters will be set according to inputs from Motorola Solutions' design team. System software and system features will be tested and validated. All system levels will be set according to specifications to verify proper end -to -end connectivity. These settings will be recorded and documented to provide baseline information to the field integration team. The system will be exercised while in factory staging, allowing for testing and at least two week burn -in of components and boards for proper operation as a complete system prior to shipping to the County. Once the system or subsystem has been assembled, optimized, and integrated as a complete working unit, the system will be tested according to the Factory Acceptance Test procedures. County may, in its sole discretion, attend (through County representatives and/or Authorized Third Party User representatives) and witness Factory testing. Once staging is completed, Motorola will carefully pack and ship the equipment in the racked configuration to a storage facility. P25 System and Services Agreement (R1422515R1/P1) Page 37 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A. Factory Acceptance Testing Motorola Solutions will coordinate with the Broward County for County representatives to visit CCSi and participate in a system demonstration and factory acceptance testing. This visit will provide the County with the opportunity to see the equipment assembled and working as an integrated system and to test in a hands-on manner, the functionality and features of the communication system that can be enabled in the factory environment. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below Factory ATP Responsibility Matrix AIIIIIIIIIIIIIIIIih ResponsibilityTask Motorola Solutions integrates the equipment for initial staging at CCSi and performs pre -testing Motorola Solutions System Staging to ensure the system provides the Contracted functionality and features. County may elect to send Factory Acceptance Testing personnel to CCSi to witness the Broward County Witnesses Factory Acceptance Testing. Motorola Solutions will perform testing in accordance with the Factory Acceptance Test Plan to Motorola Solutions Factory Acceptance Testing verify the functionality of the communications system. Motorola Solutions integrates the equipment for initial staging at CCSi and performs pre -testing Motorola Solutions System Staging to ensure the system provides the Contracted functionality and features. Staged equipment is shipped to a Motorola Solutions Storage facility inside Broward County Motorola Solutions Staged System Shipped for installation by Motorola Solutions. Completion Criteria This Factory Acceptance Testing will be considered complete when the County signs a certificate of acceptance of the Factory Acceptance Test and Motorola provides written notification that all staged equipment has been shipped to and received by the storage facility in Broward County. P25 System and Services Agreement (R1422515R1/P1) Page 38 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Phase 6: Installation A. Fixed Network Equipment Installation Motorola Solutions will be responsible for the availability and readiness of all sites, according to the agreed upon Project Schedule. Motorola Solutions will provide warehouse space following staging. Motorola Solutions will be responsible for delivery of equipment to the sites. Installation of the Fixed Network Equipment (FNE) will consist of installing the radio communications infrastructure and computer equipment at the master sites, dispatch communications sites, and RF sites. During equipment installation, any required changes will be noted and assembled with the final as -built documentation of the system. The as -built documents will be provided at the end of the project along with the applicable standard Maintenance and Operations manuals. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below. FNE Installation Responsibility Matrix Site Requirements including, as a minimum power, space, Site Requirements environmental details and network termination Motorola Solutions information provided to the County. Document Confirm that existing sites are ready for equipment installations per the Site Requirements, including: - Adequate installation space. - Cable trays/raceways. - Demarcation points for RF, power, grounding, control, Motorola Solutions Site Readiness and networking within five cable meters of the equipment. Sites will be ready according to the project schedule for equipment installation. P25 System and Services Agreement (131422515R1/P1) Page 39 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 General Installation Responsibilities: - Motorola Solutions will install the new system equipment that is provided by Motorola Solutions. - Motorola Solutions will ground and bond the site equipment to the building or shelter ground system, in accordance with the site installation standards. - Motorola Solutions will furnish all cables for power, audio and control, to connect the supplied equipment to the power panels or receptacles and the audio/control line connection point. Motorola Solutions Equipment Installations - All cabling will be cut to length, properly connected and terminated per Motorola Solutions standards and clearly labeled at both ends. - Motorola Solutions will remove and dispose of any debris that is a result of the project activities from the site. - All cabling, port assignments, and punch block connections will be recorded into the final system as - built documentation. Motorola Solutions will install Master Site Equipment in Radio System accordance with the Design Review Scope of Services and Motorola Solutions Installation Audit Equipment Lists. Motorola Solutions will install ASTRO 25 Trunked Simulcast Site equipment and remote RF site equipment Motorola Solutions Radio System in accordance with the Design Review Scope of Services Installation Audit and Equipment Lists. Motorola Solutions will install dispatch equipment in Radio System accordance with the Design Review Scope of Services and Motorola Solutions Installation Audit Equipment Lists. Motorola Solutions will remove any decommissioned Removal of equipment and antenna systems from sites that are being Motorola Solutions Decommissioned used for the new system. Equipment County will conduct inspection and check out of FNE on a Signed Installation site -by -site, system -by -system basis. Broward County Acceptance Documents P25 System and Services Agreement (R1422515R1/P1) Page 40 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Completion Criteria The installation of each FNE subsystem must be completed for this phase of the project to be considered complete. This task will be considered complete when the County reviews FNE installations with Motorola Solutions and approves by signing the installation check sheets. The following sections describe the major system components to be installed at each County location. B. ASTRO 25 FNE Installation ASTRO 25 FNE Installation The matrix below shows all site locations and the corresponding equipment (microwave and radio), including rack quantities and DC Power, according to the RFP design specifications. Site Name #Racks Main Astro 25 CORE 3 Coconut Creek 3 Markham Park 3 Playa 3 Davie 3 Point Of America 3 Miramar 3 Channel2 3 Deerfield 3 Tamarac 3 West Lake Park 3 BC Station 106 2 West Hollywood 3 Pompano Bch ClubN 3 Parkland 3 EOC 0 EMS 0 Sunrise Disp 0 Coconut Creek Disp 0 Pembroke Pines 0 # Racks # Racks If Racks # Racks # Racks # Racks # Racks # Racks # Racks # Racks Total — Rack Space Backup Astro 25 800 MAAnanlog Main Master DSR Master Main Prime GEO Prime Backup Prime 800 MA Prime MCC7500 Network Microwave Racks DC Power 0 0 2 0 2 0 0 0 0 1 8 7 2 1 0 0 0 0 0 0 0 1 7 7 0 0 0 0 0 0 0 0 0 1 4 6 0 0 0 0 0 0 0 0 0 1 4 4 2 1 0 0 0 0 0 0 0 1 7 5 0 0 0 0 0 0 0 0 0 1 4 4 0 0 0 0 0 0 0 0 0 1 4 6 2 1 0 0 0 0 0 0 0 1 7 6 0 0 0 0 0 0 0 0 0 1 4 4 0 0 0 0 0 0 0 0 0 1 4 4 0 0 0 0 0 0 0 0 0 1 4 4 0 0 0 0 0 0 0 0 0 1 3 4 0 0 0 0 0 2 0 0 0 1 6 6 0 0 0 0 0 0 0 0 0 1 4 4 0 0 0 0 0 0 0 0 0 1 4 4 0 0 0 2 0 0 0 0 0 1 3 3 2 1 0 0 0 0 2 1 0 1 7 5 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 1 0 1 0 Matrix for FNE & Microwave Equipment Install at each site. Phase 7: Systems Integration and Optimization DC Power Weight (lbs) 20,880 20,880 11,760 8,520 12,912 8,520 17,040 17,040 8,520 8,520 8,520 5,880 11,760 8,520 8,520 3,816 11,760 0 0 0 During this phase of the project, Motorola Solutions will configure, optimize, and program infrastructure equipment. Motorola Solutions will provide field integration of Motorola Solutions - provided equipment. Motorola Solutions will verify that all equipment is operating properly and that all levels are properly set, once installation in the field is complete. Motorola Solutions will optimize each site or node individually. 30. All audio and data levels will be verified. 31. All communication interfaces between devices will be verified for proper operation. 32. All features and functionality will be tested by Motorola Solutions to ensure that they are functioning according to the manufacturer's specifications and per the final configuration established during detailed design, and incorporating any subsequent contract changes. P25 System and Services Agreement (R1422515R1/P1) Page 41 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola Solutions will provide MPE/IM analysis based on two-way radio frequencies used in the System and used at the site. Motorola Solutions will not be responsible for any MPE issues caused by another system or source outside of the System; however, Motorola Solutions will work with the County to determine resolutions. Motorola Solutions will conduct an intermodulation analysis based on two-way radio frequencies used in the System plus other frequencies used at the site, list of which will be provided by the County. Motorola Solutions will not be responsible for any intermodulation issues caused by another system or source outside of the System; however, Motorola Solutions will work with the County to determine resolutions. Motorola Solutions will maintain a punch list of items that require resolution. The County will be responsible for interfacing with its partners to ensure access and cooperation in association with dispatch communications integration and optimization. Motorola Solutions will pre -test the system to ensure readiness for Field Acceptance Testing. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below. Phase 7 Responsibility Matrix ResponsibilityTask Provide all required liaison support with the partners for cooperation and access during Broward County Broward County Provide Liaison field integration and with its Partners optimization according to the Project Schedule. Integrate and optimize the hardware (Schedule 2), software Motorola Solutions Integration and Optimization of (Schedule 1), and interfaces the System (Schedule 5) Maintain and manage punch list of items that need resolution; Motorola Solutions Punch list Resolution resolve all punch list items to satisfaction of County. Pre -test the sites and overall Motorola Solutions Dry -run Field Testing system to ensure readiness. Motorola Solutions to notify the Notification of System Test County that the system is ready Motorola Solutions Readiness for Field ATP and for testing Coverage ATP Completion Criteria This task will be considered complete when the system is ready for Coverage ATP and Field ATP acceptance testing. P25 System and Services Agreement (R1422515R1/P1) Page 42 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Phase 8: Traini The Training Plan will provide the County personnel with a core set of technical and operational training as set forth in Schedule 3. Three categories of training will be provided (to operators, system technicians, and system managers) to equip each group with the system and equipment related skills that they require to perform their roles. Training is available in several scenarios, depending on the course, including online training, and instructor -led training (delivered on -site in Broward County). Motorola Solutions will provide training set forth herein, but additional classes may be available based on decisions made during design review A. The Provider shall provide: 1. Operator training: a. Provider shall provide complete and comprehensive operational training that covers the features, operation and special care associated with the equipment supplied. Operator training shall include the following categories: i) Dispatch console operation - The Provider will be responsible for providing a local training facility at the Provider's expense with a minimum of 20 dispatch positions. The training shall be conducted on a 24/7 basis to account for all Broward County dispatch shifts. There shall be a ratio of one student per dispatch console position. ii) Subscriber radio operation 2. Technical/system management training: a. Provider shall provide complete and comprehensive technical training in the theory, maintenance and repair of each type of equipment and system provided for the project. This training shall include, at a minimum, system theory, troubleshooting, repair and servicing techniques as applicable to the selected system. Technical training shall include the following categories: i) Infrastructure maintenance and troubleshooting ii) Subscriber unit maintenance and troubleshooting 3. Provider shall provide complete and comprehensive technical training for County technical staff charged with managing the system. This training shall include, but is not limited to: planning and setting up the system and network; building and implementing system and network profiles and configurations; performing database -management functions; P25 System and Services Agreement (R1422515R1/P1) Page 43 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 monitoring and managing the system's performance; and writing and printing system reports. System management training shall include the following categories: a. NMS operation and control b. Fleet mapping and radio programming c. Microwave network management d. Inter-RF Subsystem Interface (ISSI) operation and control B. Provider shall fully describe all proposed training programs detailing how Respondent intends to provide training. The training description shall include the following: 1. A list of all subjects with a description of each a. "Fingertip roaming" needs to be presented and defined 2. Class material to be provided by Respondent 3. Number of classes 4. Class duration 5. Need for recurring training 6. Class size 7. Class cost C. Provider shall coordinate with the County regarding the number of attendees and schedule. D. Classes shall be scheduled as near to system cutover as possible. Provider shall work with the County to develop the schedule. E. Provider shall train County employees or designated individuals. In some cases, a train -the - trainer approach will be used to train other users. F. Provider shall provide all instructional materials, including printed manuals, audio, video, interactive self -paced personal computer programs, and complete equipment operating instructions for all technical and operational training classes. Actual and/or exact model and series of equipment being delivered shall be made available for hands-on use and operation during training. All instructional materials shall be subject to the approval of the County and shall become property of the County. P25 System and Services Agreement (R1422515R1/131) Page 44 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Overview Through the training provided by Motorola Solutions, Broward County personnel will gain in-depth understanding of the power of County's new system through education and proficient daily use. The training is complemented by detailed documentation and available continuing education programs. Provider will collaborate with Broward County to develop a final customized training plan that fits County's needs. Motorola training will deliver a combination of online training and field based instructor —led training in classrooms at Broward County locations using operational equipment. Motorola Solutions will employ knowledgeable and experienced instructors to deliver well —designed courseware and integrated lab activities. Motorola instructors will be experienced and knowledgeable as to both the System and the practical aspects of Broward County manager, technician and end user job functions. Each instructor will have proven ability to communicate with a novice as well as expert personnel. The Training Plan set forth in Schedule 3 contains the detailed training program, which may be modified upon approval of the County Contract Administrator. Completion Criteria This task will be considered complete when the training has been delivered as described in the Training Plan. Phase 9: Cutover Plannin Motorola shall work with Broward County to develop a comprehensive cutover plan to migrate users from the old system to the new system. Motorola shall develop a detailed agency -by -agency schedule and step-by-step instructions to ensure a smooth migration and minimize risks to service interruption. The planning shall include how communications and interoperability will be maintained across both the old and new systems, including both console access and shared talkgroups to both the old and new systems. The plan shall include mitigation strategies should problems occur during the cutover process, such as failures on the new system or an inability of users to communicate across both the old and new systems. Completion Criteria This task will be considered complete when the cutover plan has been delivered as described. P25 System and Services Agreement (R1422515R1/P1) Page 45 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Phase 10: Preliminary Acceptance Testing Preliminary acceptance testing is composed of coverage testing and 30-day operational testing, as well as preliminary acceptance testing criteria. Testing will be performed when the system optimization is complete. Field acceptance tests verify the contracted system functionality and demonstrate RF coverage. Motorola Solutions will submit the detailed test plans, developed from the baseline initial ATP, for approval 30 days prior to the beginning testing. County will review and provide feedback, which Motorola will incorporate in revised proposed detailed test plans. That process will continue until County approves in writing the detailed test plans. Motorola Solutions will provide notice of the commencement of testing to the County at least 10 days in advance. Testing will occur in accordance with the agreed to test plans. Completion Criteria Upon successful completion of functional testing, the County's representatives participating in and observing the tests will sign off on this portion of the ATP. Coverage Testing will commence once the system has been optimized. Once successfully completed, coverage test results will be consolidated into a report and reviewed with the County. This task will be considered complete upon the County's written approval of successful completion of all functional testing and the successful passage of the coverage testing. If a punch list of material unresolved issues is created as a result of any acceptance testing, Motorola will remedy the issue and resubmit for testing in accordance with the testing procedures of the Agreement. A. System Functional Testing Description System functional acceptance tests will be performed when the system optimization is complete. The functional acceptance tests verify the functionality tested at factory testing. These tests will verify the entire system in operation, including radio system roaming and subscriber affiliation. If the System does not successfully pass all aspects of the functional acceptance test, the failed items will be documented and remedied by Motorola and resubmitted to County for retesting in accordance with the procedures set forth in the Agreement. Upon successful completion of the functional testing, the County will acknowledge testing completion by signing the Functional Test Completion Certificate. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below. P25 System and Services Agreement (R1422515R1/P1) Page 46 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 System Functional Testing Responsibility Matrix ResponsibilityDeliverable Motorola Solutions will perform functional ATPs for the system. Execution of Functional During each test, test results will Motorola Solutions Acceptance Testing be recorded for review and approval of the test. Upon successful completion of each Acceptance Test, the County and Motorola Solutions Motorola Solutions and Broward Written Approval of Successful will sign an acceptance County Functional Acceptance Testing certificate, documenting acceptance. B. Coverage Testing Coverage acceptance tests will be performed when the RF site and control equipment installations and optimization are complete. The coverage tests verify the coverage delivered by the system. A detailed CATP document is included in Section 2.10.5.1 Coverage Acceptance Test Plan. Responsibilities and deliverables for Motorola Solutions and the County are defined in the table below (unless otherwise approved by the County Contact Administrator). Coverage Testing Responsibility Matrix Task Motorola Solutions will perform Coverage Testing for the System. During each testing, test results will be recorded for review. .. Motorola Solutions Deliverable Execution of Coverage Testing Motorola to provide vehicles and drivers for Coverage Testing, assuming three test teams for a Motorola Solutions Provide Coverage Test period of approximately two weeks. Vehicles (County to provide the boats for water grids.) Motorola Solutions will consolidate coverage test results and submit a report to the County, summarizing Motorola Solutions Coverage Test Report coverage performance in the tested area. P25 System and Services Agreement (R1422515R1/P1) Page 47 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Task Responsibility Deliverable Upon completion of the coverage testing, and submission of the Written Agreement of Coverage Test Report, the County Motorola Solutions and Successful Completion of and Motorola Solutions will sign a Broward County certificate documenting agreement Coverage Testing of completion of coverage testing. Completion Criteria This task will be considered complete upon the County's acceptance and sign -off of the functional test, and agreement of the successful completion of coverage testing. C. System Acceptance System Acceptance will be based only on the approved ATPs as set forth herein. Motorola Solutions will provide checklists for each test. If deficiencies are found during the testing, both the deficiency and the action plan will be agreed upon and documented. By signing and approving the functional testing certificate and agreement to the completion of the coverage test, the system will be deemed to have passed the applicable acceptance test(s). Acceptance testing is a cooperative effort and will be conducted by Motorola Solutions and witnessed and approved by the County. D. 30 Day Operational Test and System Acceptance Motorola Solutions will perform a 30-calendar-day operational test of the system to ensure that all hardware and software defects have been corrected prior to final acceptance. The fully integrated operation of the system, including all individual subsystems, will be demonstrated during these tests. The tests will be designed to demonstrate the reliability, long-term stability and maintainability of the systems. A failure of any component of the system during this test will cause the test to restart after the repair is completed. The County will provide written acceptance of the Radio System within five working days after the successful completion and approval of all of the following: 33. Final design submittals. 34. Staging ATP. 35. System installation. 36. Final inspection and punch -list resolution. 37. As -built documentation. 38. Field ATP, including Coverage ATP. 39. 30-day operational test completion. 40. Training. Implementation Preliminary Acceptance Milestone Upon successful completion of all items stated above, the County will grant Preliminary Acceptance of the Radio System. If and to the extent the County allows partial or conditional Preliminary Acceptance, all outstanding, deficiencies that the Parties agree to defer in order to permit a conditional or partial P25 System and Services Agreement (R1422515R1/P1) Page 48 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Preliminary Acceptance shall be reconciled and remedied by Motorola Solutions within the time agreed upon by the Parties and in no event later than the commencement of the maintenance phase. System and Final Acceptance Tests The County will grant System Final Acceptance within 30 business days after successful completion of the following: 1. Satisfactory resolution of all deficiencies contained in the punchlist at system acceptance. 2. Resolution of deficiencies identified subsequent to system acceptance. 3. Delivery of all required implementation documentation. 4. Completion of initial training. 5. Preliminary Acceptance of the Radio System, Microwave System, and Facilities and Infrastructure Services. Implementation Final Acceptance Milestone The County will grant written System Final Acceptance. P25 System and Services Agreement (R1422515R1/P1) Page 49 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.10 Radio Communications System Requirements 1.10.1 Overview A. Motorola shall provide a complete P25 700/800 MHz digital radio communications systems as described below. Primary Trunked System: P25 Mixed Mode, Phase I and Phase II —The system shall utilize the radio sites detailed in this SOW. The system must seamlessly integrate all sites such that end users can roam freely throughout the service area without interruption of service or the need to manually select sites. The system must utilize the latest system platform available at the time of system acceptance. If a newer platform is available at the time of acceptance than what was originally proposed, Motorola shall upgrade the system to the current system release. The system must meet the coverage and capacity requirements defined in this SOW. The system must be expandable to allow for additional capacity and features. The system must be configured to support P25-compliant data on voice channels running at 9,600 bits per second. Trunked Backup System: P25 Mixed Mode, Phase I and Phase II —The system must utilize the radio sites detailed in this SOW. The system must seamlessly integrate all sites such that end users can roam freely throughout the service area without interruption of service or the need to manually select sites. The system must utilize the latest system platform. The system must meet the coverage and capacity needs of Broward County. The system must be expandable to allow for additional capacity and features. 700 MHz Conventional Backup System: P25 Phase I Conventional —The system must utilize the four mandatory radio sites detailed in this SOW. The system must operate on FCC -allocated 700 MHz interoperability channels, with each site providing two standalone conventional repeaters. 800 MHz Conventional simulcast interoperability system: Wideband Analog — The system must utilize the four mandatory radio sites detailed in this SOW. The system must operate on the three designated FCC -allocated 800 MHz NPSPAC interoperability channels. Interference Locator: The System will include functionality to provide visualization on the UNC GUI of the location of non -authorized transmitters (or RF interference carriers) in a simulcast system ("Interference Locator"). Interference Locator utilizes existing GTR and Comparator system equipment at RF sites to quickly and easily track the location of non -authorized transmitters. Included within the functionality provided by Interference Locator is the UNC System License UA00521AA and a UA00467AA license for each Simulcast RF Sub -Site (i.e., 14 sub -sites for Broward County). These systems shall provide portable and mobile radio coverage throughout the County as required in the RFP and described in this SOW. Motorola's solution will remedy the major in -building and on - street portable coverage deficiencies currently experienced by many of the agencies on the current systems and will provide reliable communications through redundant master and prime simulcast sites controlling a coverage network that meets the RFP's required simulcast and site selection requirements. The System will enable users to communicate seamlessly with one another, and P25 System and Services Agreement (R1422515R1/P1) Page 50 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 leverage the features of ASTRO 25 technology to interoperate with other P25 and conventional systems in the area. Preliminary System block diagrams are included as Schedule 7. 1.10.1.1 RFP Compliant Designs Motorola Solutions has engineered a single simulcast cell design that represents operational ease and will support a maximum of 36 talkpaths. Having one simulcast cell means that the same capacity is available across the entire service area, eliminating "operational seams", which negatively impact user operations. Motorola's solution will provide a single 11 site, 19 channel, 700 MHz simulcast P25 Phase 2 TDMA digital trunked radio system. In addition to the simulcast network that provides coverage for the populated areas of the County and off shore, a P25 6 channel Phase 2 ASTRO Site Repeater will provide the required coverage in the Everglades area of the County. This system will utilize the 700 MHz channels, which will be provided by Broward County. The design could however use 800 MHz channels or even a combination of 700/800 depending on the grouping of the available channels. The System will provide the ability to support both P25 Phase 2 TDMA users and users that are only capable of P25 Phase 1 FDMA operation. To preserve wide area Trunking communications, even in the event of the failure of major hardware components, the radio system includes a hardware redundant Zone Core site and Dynamic System Resiliency (DSR). Each Zone Core site has been configured to provide redundancy to key equipment components, such as Zone Controllers, Core LAN switches and Core Gateways, in order to eliminate single points of failure that could result in a loss of wide area Trunking operation to the radio system. To preserve simulcast radio system operation, even in the event of the failure of major hardware components, the radio system also includes GEO Redundant Simulcast Prime sites. Both Cores and GEO Redundant Simulcast Prime sites will be implemented at separate locations in order to provide a distributed architecture between two sites on the radio network. This will prevent the loss of both the Zone Core and the Simulcast Prime site in the event of a catastrophic event that causes the complete destruction of a single location. Each remote RF site consists of Base Radios, IP networking, antenna networks, and is controlled by the Simulcast Primes and Core sites. The sites are synchronized by a Global Positioning System (GPS) redundant time and frequency reference that has a backup Rubidium reference in order to keep the network timing synchronized. The multi -site architecture of the simulcast cell provides an inherent level of site redundancy. The loss of a single remote RF site will result only in a reduction of the coverage footprint, while maintaining the same system capacity throughout the system. The System also includes three MCC 7500 IP-based radio dispatch console sites as required by the RFP. A 24 position MCC 7500 dispatch console site will be located at the Broward County Sunrise central dispatch center. A 23 position MCC 7500 dispatch console site will be located at both the Coconut Creek North Dispatch center. A 21 position MCC 7500 dispatch console site will be located at both the Pembroke Pines Dispatch center. To allow for the capability to configure system parameters, monitor system activity, generate system reports, and to monitor all critical systems and site status alarms, Network Fault Management (NFM) equipment will be installed at each site. In addition three Network Management (NM) client workstations will be installed at TBD locations. P25 System and Services Agreement (R1422515R1/P1) Page 51 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Site connectivity will be provided by a combination of licensed 6 GHz and 11 GHz digital microwave which will provide a Layer 3 MPLS transport for all dispatch and radio infrastructure sites including the Broward County EOC. To preserve connectivity between the remote RF sites and Prime sites and between the Prime sites and the Zone Core sites, the microwave network has been configured in two rings between all sites. A failure to any one path between sites will result in a redirection of the links to the opposite direction of the ring. This will eliminate single points of failure, which could result in a loss of connectivity between the remote RF and the Control sites. A system topology diagram is included in this proposal. The primary system will utilize the mandatory existing site infrastructure, such as towers, radio communications shelters and generators but will include new site infrastructure equipment as described in detail in the following sections. Also included in the System provided by Motorola is a 700 MHz simulcast P25 Phase 2 TDMA 7 channel 4 site backup system with 2 conventional 700 MHz repeater channels at the 4 sites. In addition, a 3 channel 4 site 800 MHz analog conventional simulcast is also co -located at the 4 backup sites. Motorola Solutions will provide a Mobile Communications Trailer and properly sized vehicle with all of the required control stations, repeaters and GUI control interface. 1.10.1.2 Redundancy and Survivability A. The radio communications system shall support mission -critical operations; therefore, a high degree of redundancy and survivability is required. A network topology utilizing fault tolerance shall be incorporated to the greatest extent possible through a distributed and/or redundant architecture. B. Provider's System will be fully redundancy including for all system elements in which failure would result in a major failure of the system; single points of failure are not acceptable. Such redundant elements include, but are not limited to, the following: 1. System controllers and fixed site equipment 2. Simulcast controllers and voting equipment 3. Backhaul network 4. Power systems 5. Network Management System 6. Dispatch console position 7. ISSI gateway C. The trunked system shall include several modes of degraded operation, known as failure modes. The system shall be capable of automatic activation of failure modes in the event of a system failure. Additionally, the system shall switch to a failure mode gracefully. Failure modes shall include the following scenarios, at a minimum: P25 System and Services Agreement (R1422515R1/P1) Page 52 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. Loss of single site 2. Loss of multiple sites 3. Loss of system controller 4. Loss of simulcast controller 5. Loss of a frequency channel due to interference, including interference appearing on a control channel 6. Loss of multiple channels due to wideband interference 7. Loss of a repeater station due to an equipment failure 8. Loss of a dispatch console position 9. Loss of an ISSI gateway D. The trunked system must include geographically redundant components to allow continued wide -area operation and dispatch console connectivity in the event any location becomes inoperable or isolated from the network. Motorola shall provide geographically separated system controllers, simulcast controllers, and voting equipment. E. Motorola will provide both a geographically separated redundant master site and prime simulcast site. Geographic redundancy of both the master sites and simulcast prime sites combined with component -level redundancy at the master site and prime sites eliminate any single point of failure in the system. These multiple layers of redundancy ensure that users will continue to communicate and maintain full -featured functionality in the event of major or multiple failures. The redundant master and simulcast prime sites are configured in a hot - standby configuration with automatic switch -over capability, enabling automatic protection against a full loss of the primary master or prime sites, as well as less severe equipment or component failures. 1.10.2 System Technology The System will provide an integrated network that includes P25 TDMA voice infrastructure, dispatch consoles, conventional channel gateways for interoperability and encryption capabilities. It includes the following features and benefits for the County agencies: Extensive Coverage throughout the Broward County Service Area The new P25 system coverage will provide exceptional coverage throughout the Broward County area and provides public safety users a highly reliable and trustworthy system. The simulcast designs use 11 RF sites as well as a single standalone repeater site, to provide compliant 95% reliable portable coverage throughout the three defined portable service areas that include a 25 db building loss service area, a 20 db loss service area and an outside service area that is primarily the Everglades within P25 System and Services Agreement (R1422515R1/P1) Page 53 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Broward County. This coverage design also includes 95% mobile coverage for a minimum of 10 miles offshore. Backup system Coverage for the Broward County Service Area The trunked backup system will provide 95 percent coverage for a portable radio operating outdoors, with 95 percent reliability, for those portions of the county identified in the RFP. System County and Expandability Now and For the Future The system leverages the prior antenna sites purchased Broward County by expanding the system with the singular focus of meeting Broward County's current requirement to support the existing users with the ability to support future growth. The ASTRO 25 platform being provided is highly scalable and enables Broward to expand the system to support additional radio users, dispatch sites, dispatch consoles and RF sites that may be added in the future. Provider will include 75 licenses for dispatch console operator positions. The System will b able to support up to 500 operator positions with the addition of console user licenses. The System includes three dispatch center locations, and can support up to 55 separate dispatch console locations. Increased System Functionality and Security Enhanced programming, security, roaming, and interoperability capabilities will be provide by Motorola using both P25 standard functionality and Motorola Solutions data and value-added capabilities: 1. Communications with other agencies is assured, with shared encryption, enhanced roaming and system wide access to dispatchers using the proposed MCC 7500 consoles. 2. Users will be able to roam seamlessly throughout the simulcast system coverage area and into the Everglades providing simplified operation without the need to manually switch between different areas of the system. 3. Interoperability through the ISS18000 with automatic roaming will be provided for four (4) other systems (Motorola Host Master Site, Miami -Dade, Palm Beach, Collier) with 10 simultaneous talkgroups. 4. Dispatch centers will have increased integration with the system radios resources through the use of Motorola MCC 7500 dispatch technology. The MCC 7500 integrates directly into the system's core, providing access to all authorized resources system wide. The MCC 7500 dispatch console utilizes the same Gold Elite console Graphical User Interface (GUI) used today by the County thus allowing for an easy transition for dispatch users. Mission Critical Reliability Provided by Geographic and Equipment Redundancy The System will provide geographic redundancy of both the master sites and simulcast prime sites combined with component -level redundancy at the master site, prime sites, RF sites, and dispatch sites, eliminating any single point of failure in the system. These multiple layers of redundancy will ensure that users will continue to communicate and maintain full -featured functionality in the event of major or multiple failures. Provider will configure the redundant master and simulcast prime sites in a hot -standby configuration with automatic switch -over capability, enabling automatic protection against a full loss of the primary master or prime sites, as well as less severe equipment or component failures. P25 System and Services Agreement (R1422515R1/P1) Page 54 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Technology and Support for the Long -Term Provider's System is built on the ASTRO 25 platform, and the System will use technology that has already been deployed in over 500 Project 25 systems, for customers whose first responders rely on mission -critical communications during both day-to-day activities and during critical events. The System's ASTRO 25 technology is modular and scalable, enabling the incremental addition of new features and functionality throughout the system's lifetime. 1.10.2.1 Dispatch Consoles and Logging To minimize the impact that the dispatch operators experience during a system migration, Motorola Solutions will utilize the familiar Gold Elite GUI interface as part of the System's robust, public safety dispatch solution, the MCC 7500. Motorola will provide a robust logging recorder solution that will provide the County with a fully Internet Protocol (IP), based system that meets and exceeds the needs of the County today and in the future. The solution being provided by Motorola will allow the County to take advantage of the latest in public safety grade logging solutions. 1.10.3 Interoperability/ P25 Statement of Requirements (SOR) 1.10.3.1 Interoperability Features of System The System will be interoperable with other P25 radio systems as well as with non-P25 systems. In addition, it supports full, seamless communications between P25 Phase 1 and P25 Phase 2 radios, dynamically switching between FDMA and TDMA modulations as necessary. The Equipment and other infrastructure being provided has been proven to support radios from other vendors, with combined fleets in operation on many of the hundreds of ASTRO 25 systems servicing public safety agencies. A. Interoperability with Project 25 Radio Systems The System will accommodate additional users and system growth through a modularly expandable design that will scale as the County's needs change. It supports interoperability with other Project 25 systems in the region. The County's System will be able to interconnect with these systems either through an ISSI gateway or directly without the need for an ISSI connection when connecting to one of the many Motorola Solutions P25 systems in the South Florida area. The subscriber units being provided are P25 Phase 1 and Phase 2 compliant units. All of the radios will have the ability to operate on foreign P25 Phase 1 or Phase 2 systems. The radios also will be able to operate in analog and digital conventional modem, which will allow users to operate on outside agencies conventional systems or through radio to radio talk around mode. 1.10.3.2 System Features Tested for Compliance with Project 25 Standards The table below lists the P25 features of the System that Motorola will provide: P25 System and Services Agreement (R1422515R1/P1) Page 55 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 P25 Trunked System Feature Matrix The following table is a list of P25 trunking features available on an ASTRO 25 trunking system. Features available on your system will vary dependent on the options purchased. P25 TRUNKED SYSTEM FEATURE MATRIX Last Updated: April 28, 2015 RELEASE 7.15 TIA-102 STANDARD FDMA TDMA TIA STANDARDS DOCUMENTS PUBLISHED P25 TRUNKED CAI CAI FEATURES • PROJECT 25 COMMON VOICE CALLS Group Voice Call Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 / TIA-102.13CAE Individual Voice Call Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 / TIA-102.BCAE Availability Check on Called Party Yes Yes TIA-102.AABD-B / TIA-102.AABC-D / TIA- 102.AABF-D/ TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.13CAE Broadcast Voice Call Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- 13;13-1 / TIA-102.13CAE Announcement Group Call Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 / TIA-102.13CAE Emergency Group Voice Call Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 / TIA-102.BCAE Emergency Call Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 / TIA-102.BCAE Pre -Programmed Emergency Group Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- Call 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.BCAE Group Regrouping (part of P25 Yes Yes TS6102-B/ TIA-102.AABD-B / TIA-102.AABC-D / Dynamic Regrouping) TIA-102.AABF-D / TIA-102.AABH MOBILITY MANAGEMENT Roaming Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- P25 System and Services Agreement (R1422515R1/P1) Page 56 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Intra-System Roaming (Automatic) Yes Yes TS13102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 Inter -System Roaming (Manual) Yes Yes TS6102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 Registration Yes Yes TS6102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- 13;13-1 Restricting service access only to Yes Yes TS13102-B/ TIA-102.AABD-B / TIA-102.AABC-D / valid SU TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 De -registration Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 Group Affiliation Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Call Restriction Yes' Yes' TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Call Routing Yes Yes TSB102-B Wide Area Call Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 Location Registration Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 WUID Validity Timer Yes Yes TIA-102.AABD-A;A-1 / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B/TIA-102.AABB- B/TIA-102.BBAC;-1 KEY MANAGEMENT KFD Based Key Management Manual Rekeying Features Yes Yes TIA-102.AACD-A / TIA-102.BBAC;-1 Keyload Yes Yes TIA-102.AACD-A / TIA-102.BBAC;-1 Key Erase Yes Yes TIA-102.AACD-A / TIA-102.BBAC;-1 Erase all Keys Yes Yes TIA-102.AACD-A / TIA-102.BBAC;-1 View Key Info Yes Yes TIA-102.AACD-A / TIA-102.BBAC;-1 KMF Based Key Management Unique Key Encryption Key (UKEK) Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Individual Radio Set Identifier (Ind Yes N/Az TIA-102.AACD-A / TIA-102.AACA-A RSI) P25 System and Services Agreement (R1422515R1/P1) Page 57 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Key Management Facility Radio Set Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Identifier (KMF RSI) Message Number Period (MNP) Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Keyload Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A View Individual RSI Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Load Individual RSI Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A View KMF RSI Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Load KMF RSI Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A View MNP Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Load MNP Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A View Keyset Info Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A Activate Keyset Yes N/A' TIA-102.AACD-A / TIA-102.AACA-A SECURITY SERVICES Encryption Yes Yes TSB102-B / TIA-102.AAAB-A/TIA-102.AAAD-A / TIA-102.AACD-A / TIA-102.AACA-A/ TIA- 102. BBAC;-1 DES-OFB Encryption of Voice Yes Yes TSB102-B / TIA-102.AAAD-A / TIA-102.BBAC;-1 AES Encryption of Voice Yes Yes TIA-102.AAAD-A / TIA-102.BBAC;-1 AES Encryption of Packet Data Yes Yes TIA-102.AAAD-A / TIA-102.BBAC;-1 Multiple Encryption Algorithms Yes Yes TIA-102.AACA-A / TIA-102.BBAC;-1 Multiple Encryption Keys Yes Yes TIA-102.AAAD-A / TIA-102.BBAC;-1 SUPPLEMENTARY SERVICES Priority Call Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.13CAE Preemptive Priority Call Yes' Yes' TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.BCAE Dispatcher Audio Takeover Yes Yes TSB102-BAGA / TIA-102.BBAC;-1 / TIA- 102. BCAE Emergency Alarm Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D/ TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Silent Emergency Yes Yes TSB102-B Radio Unit Monitoring Yes' Yes$ TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Talking Party Identification Yes Yes TSB102-B Call Alerting Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Radio Check Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 P25 System and Services Agreement (R1422515R1/P1) Page 58 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Radio Inhibit Yes Yes TS6102-B/ TIA-102.AABD-B /TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- B;B-1 Radio Uninhibit Yes Yes TS6102-B/ TIA-102.AABD-B /TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- 13;13-1 Alert Tones Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 SU Status Update Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / TIA-102.AABF-D / TIA-102.AABA-B / TIA- 102.AABB-B / TIA-102.BBAC;-1 / TIA-102.CABC- 13;13-1 Dynamic Regrouping (part of P25 Yes Yes TSB102-B/ TIA-102.AABD-B / TIA-102.AABC-D / Dynamic Regrouping) TIA-102.AABF-D / TIA-102.AABH SYSTEM SERVICES Network Status Broadcast Message Yes Yes TIA-102.AABD-B / TIA-102.BBAC;-1 System Status Broadcast Message Yes Yes TIA-102.AABD-B / TIA-102.BBAC;-1 Channel Identifier Update Broadcast Yes Yes TIA-102.AABD-B / TIA-102.BBAC;-1 Message Adjacent Status Broadcast Message Yes Yes TIA-102.AABD-B / TIA-102.BBAC;-1 Backup Control Channel Broadcast Yes Yes TIA-102.AABD-B / TIA-102.BBAC;-1 Message MISCELLANEOUS Electronic Serial Number Yes Yes TSB102-B Queuing Yes Yes TIA-102.AABD-B / TIA-102.AABC-D/ TIA- 102.AABF-D / TIA-102.AABA-B / TIA-102.AABB- B / TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 Message Trunking Yes Yes TIA-102.AABD-B / TIA-102.AABC-D/ TIA- 102.AABF-D / TIA-102.AABA-B / TIA-102.AABB- B / TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 Transmission Trunking Yes Yes TIA-102.AABD-B / TIA-102.AABC-D / TIA- 102.AABF-D / TIA-102.AABA-B / TIA-102.AABB- B / TIA-102.BBAC;-1 / TIA-102.CABC-B;B-1 Network Access Code Yes Yes TIA-102.AABD / TIA-102.BBAC;-1 Extended hunt sequence Yes Yes TIA-102.AABD / TIA-102.BBAC;-1 PHYSICAL LAYER P25 Phase 1 FDMA P25 Phase 1 FDMA CAI Yes N/A TSB102-B / TIA-102.BAAA-A/TIA-102.BAAC- C/TIA-102.13AAB-B Enhanced Full Rate Vocoder Yes N/A TIA-102.13ABA / TS13-102.13ABE / TIA-102.13ABB / TIA-102.BABC / TSB-102.BABD /TIA- 102. BAAB-B Frequency Division Multiple Access Yes N/A TSB102-B / TIA-102.13AAA-A /TIA-102.BAAB-B (FDMA) 9.6 kbps Gross Bit Rate Yes N/A TSB102-B / TIA-102.BAAA-A/TIA-102.BAAB-B P25 System and Services Agreement (R1422515R1/P1) Page 59 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C4FM and CQPSK Modulation Yes N/A TSB102-B / TIA-102.13AAA-A / TIA-102.13AAC-C / TIA-102.CAAA-D / TIA-102.CAAB-D / TIA- 102. BAAB-B 12.5 KHz Channel Bandwidth Yes Yes TIA-102.CAAA-D / TIA-102.CAAB-D / TIA- 102. BAAB-B P25 Phase 2 TDMA P25 Phase 2 TDMA CAI N/A Yes TIA-102.BBAB / TIA-102.BCAD / TIA-102.BCAE Enhanced Half Rate Vocoder N/A Yes9 TIA-102.13ABA-1 / TSB-102.13ABE / TIA- 102.13ABB / TIA-102.13ABC / TS13-102.13ABD / TSB-102.BABF / TIA-102.BABG / TIA-102.BCAD / TIA-102.BCAE Time Division Multiple Access (TDMA) N/A Yes TIA-102.1313AB / TIA-102.CCAB-A / TIA- 102.13CAD / TIA-102.13CAD 12 kbps Gross Bit Rate N/A Yes TIA-102.1313AB / TIA-102.CCAB-A HCPM and HDQPSK Modulation N/A Yes TIA-102.1313AB / TIA-102.CCAB-A 12.5 KHz Channel Bandwidth Yes Yes TIA-102.1313AB / TIA-102.CCAB-A DATA SERVICES Packet Switched Confirmed Delivery Data Yes N/A10 TSB102-B / TIA-102.BAEB-B Packet Switched Unconfirmed Delivery Data Yes N/A10 TSB102-B / TIA-102.13AEB-13 Packet Switched Data Network Access Yes N/A10 TSB102-B / TIA-102.13AEB-13 TCP/UDP Port Number Assignments Yes N/A10 TIA-102.13AJD Data Configuration - Radio to FNE Yes N/A10 TIA-102.13AEA-13 / TIA-102.13AEB-13 / TIA- 102.13AEE-13 Packet Data Registration Yes N/A10 TIA-102.13AAD-A / TIA-102.13AEB-13 SU Registration Yes N/A10 TIA-102.13AAD-A / TIA-102.13AEB-13 SU Deregistration Yes N/A10 TIA-102.13AAD-A / TIA-102.13AEB-13 SU Location Tracking Yes N/A10 TIA-102.13AAD-A / TIA-102.13AEB-13 Mobile Data Interface (A) Yes N/A10 TSB102-B / TIA-102.13AEB-13 Link Layer and Physical Layer Protocols Yes N/A10 TIA-102.13AEA-13 / TIA-102.13AEB-13 SNDCP (Subnetwork Dependent Convergence Protocol) Yes N/A10 TIA-102.13AEB-13 Fixed Host Data Interface (Ed) Yes N/A10 TSB102-B / TIA-102.13AEB-13 Ethernet (802.3) Yes N/A10 TIA-102.13AEB-13 Internet Protocol Suite Yes N/A10 TIA-102.13AEB-B Notes: 1 Motorola Network Management provides the capability to provision the services available to both subscriber radios and talkgroups. 2 The P25 KMF utilizes the Phase 1 FDMA data channel. There is no P25 Phase 2 TDMA data channel. 3 Traffic Encryption is made up of two parts; Voice Traffic Encryption and Encrypted Integrated Data. Voice Traffic Encryption is defined by the P25 standard and Motorola offers. Today there is no published P25 standard for Encrypted Integrated Data however Motorola started offering this feature in the 7.8 release. 4 Today the Project 25 standard defines Chronological Integrity for OTAR, which Motorola offers. 5 Today the Project 25 standard defines Message Integrity for OTAR, which Motorola offers. The Project 25 standard will also support Message Integrity in the future Packet Data Security standard. Currently, Motorola supports Message Integrity for Encrypted Integrated Data. 6 Zerorize and No Service procedures can be used in Key Compromise situation. P25 System and Services Agreement (R1422515R1/P1) Page 60 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 7 Motorola understands this feature to mean Emergency Priority will Pre-empt a Non -Emergency Call. 8 Motorola supports remote unit monitor for talkgroup calls however it will not support the U2U version of remote unit monitor. 9 The APX subscriber uses the P25 enhanced vocoder. The XTS/XTL subscriber product portfolio uses the P25 baseline vocoder with added background noise reduction capability. 10 The P25 Phase 1 FDMA data channel is used for P25 Packet Data Delivery. There is no P25 Phase 2 TDMA data channel. This matrix includes Motorola ASTRO 25 System Release 7.15 System Infrastructure Capabilities. Allfeatures and capabilities listed above are included in the most up to date and the current shipping version being provided to County under this Agreement, Release 7.17. The System and the radios are designed to the Project 25 TIA-102 standard documents. Motorola Solutions fully supports and participates in the P25 Compliance Assessment Program (CAP) facilitated by the Department of Homeland Security DHS). 1.10.3.3 CAP Testing All Equipment and infrastructure being provided as part of the System has passed P25 Compliance Assessment Program testing. Motorola will provide the Declaration of Compliance (SDoCs) for the ASTRO trunking network and G-Series repeater equipment, as well as all the radios and radio upgrades These SDoCs confirm testing with Motorola, Harris, Tait, EF Johnson, and Kenwood radios, as well as other P25 subscriber manufacturers. Summary Test Report (STR) An STIR is issued by the manufacturer and outlines the individual tests conducted and the associated test results for a given product. Key information found on an STIR includes: 5. Product description information. 6. Other devices the product is tested with. 7. Individual tests conducted on the product. 8. Pass criteria for performance tests. 9. Test results for a given test (Pass, Fail, etc.). Supplier's Declaration of Compliance (SDoC) An SDoC is issued by the manufacturer and is a companion document to the STIR. The SDoC references the applicable STIR and includes a declaration that a product passed a given test suites. Key information found on an SDoC includes: 10. Product description information. 11. Other devices the product is tested with. 12. The test suites a product passed with any exceptions. 13. A declaration from the manufacturer including a signature from an authorized representative. P25 System and Services Agreement (R1422515R1/P1) Page 61 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.10.4 System Configuration 1.10.4.1 System Architecture Motorola Solutions' design for the Broward County is a P25 Phase 1/Phase 2 700MHz, digital trunked communications system designed specifically to meet the County's needs and comply with the RFP's requirements. Motorola Solutions' ASTRO 25 trunked design will provide wide -area, high County voice communications to all user agencies. The figure below illustrates the proposed P25 radio system topology, including the overall system design, the geographically -redundant master and prime sites, simulcast cell, standalone repeater site, and dispatch console sites. RF Remote Main Cft t}� Geo- Ct� )}� Redundant Prime Site Simulcast rime Site P25 AS Sites Core Core Routers Routers Primary Zone Controller ® Core LAN Core LAN Network Switches Gateway Gateway Switches Management Redundant Zane Routers Routers. Client Controller MAIN MASTER SITE — CURE Exit Exit Deters Inter zunq Link Proposed P25 Radio System Topology MCC 75DO insole Site PrimaryZane ABEEEMM Controller Network Redundant Zone Management Controller Client ASR MASTER SITE — EOC The architecture is IP-based, comprised of advanced network of computer servers and workstations, high speed local area networks (LAN), wide area networks (WAN), sophisticated databases, management software and radio frequency (RF) equipment. Connectivity will be provided by the dual loop new MPLS-based microwave system. 1.10.4.2 Reliability and Redundancy Features of System Motorola Solutions' solution provides the County with a mission critical reliable and redundant system. The system includes multiple levels of redundancy and is designed to withstand multiple failures and still provide full -featured trunked communications. Motorola Solutions' P25 system has no single point of failure that can disable P25 voice services within the network, or that would take more than 25% of the system channel Broward County out of service. P25 System and Services Agreement (R1422515R1/P1) Page 62 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A. Control Site Redundancy The master network controllers at both sites will have the same system components and will both be live on the system, with the primary Master Network Controller (master site) actively processing traffic and the second in a mirrored configuration, immediately ready to take over processing without requiring re -affiliation of radios or consoles. B. Master Site Switchover The system managers have the ability to manually switch between the active master site and the backup master site using the configuration tool. This manual switchover will result in the system going into site trunking mode for a period of up to two minutes before the previous backup master site becomes the active master. Failure of the key components at the active master site will result in the automatic switch -over of control to the backup master site. During the switch over period between the master sites, the system temporarily enters into site trunking mode. (This usually lasts for less than 30 seconds, is typically only a few seconds, and many users may not even be aware a switch has occurred.) In the seconds during switchover, when the system is in site trunking mode, the subscriber units and dispatch consoles in the field will have a visual and audible indication that the system is in site trunking, and that they do not have wide area communication with other users in the system, except those affiliated to the same RF site. Also during this period, the subscriber units will remain affiliated to their original RF site. Once the backup master site takes over control and the system is back in wide - area operation, the subscriber units go back to normal wide -area operation. No deaffiliation or reaffiliation takes place during this period. During the period when the entire system is in site trunking mode, the dispatch users will have a visual and audible indication of not having wide area access to trunked resources on the system. C. Prime Site Switchover The proposed Geo-Prime site system is designed in redundancy with a number of different configurations. The Primary Prime site is equipped with two controllers while the backup prime (geo-prime) is equipped with a single controller. The failure of one of the prime site controllers at the primary prime site will result in the redundant controller taking over. Only in the event that both the primary prime site controllers failure will the backup prime controllers become active. Both the primary prime site and backup -prime site have equal number of comparators. Failure of the comparator at the prime site will result in the corresponding comparator at the backup -prime site becoming active. This occurs even if all the other equipment at the primary prime site is still active. The transition to the backup comparator is transparent to users. Switching from the backup -prime to the primary prime site is only done at the command of an authorized user to avoid the system automatically switching prime sites unnecessarily. Further failure scenarios are found in the failure scenario section below. P25 System and Services Agreement (R1422515R1/P1) Page 63 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 D. System Failsoft In the unlikely circumstances that the system suffers additional failures, the site then may go into Failsoft mode. Subscriber radios currently affiliated with the Failsoft site will be affected differently depending on how they are programmed or configured. The Failure analysis below describes the behaviors of subscribers during the site Failsoft operation. Dealing with a site entering into Failsoft or one recovering from Failsoft requires special consideration to ensure that the control channel is not overloaded due to subscriber radios trying to affiliate. Upon site failure or recovery, the system protects itself from conditions that might entail numerous radios registering simultaneously and potentially overloading the system using Random Hold -off Timers; Failure Random Hold -off Timer (FRHOT) and Recovery Random Hold -off Timer (RRHOT). Any site that has failed or is recovering will result in the system issuing a Random Hold -off Timer at affected site's adjacent sites. This value is configurable from 1 to 60 minutes. Upon a site failure, those radios that are not programmed to remain at the failed site will seek out the best available wide -area site. Upon finding this wide -area site, the radios will attempt to register however not before receiving the FRHOT value that has been issued by the system. The FRHOT value is used to spread out registration requests over a longer time period. Using this value, the proposed APX P25 radio unit calculates a random time that determines when that radio unit attempts to register at the new site. Since each radio unit comes up with a slightly different time, the registration requests are spread out and the sites' inbound control channels do not become overloaded. While this is a critical feature to prevent site overload from registration requests, this feature is not part of the P25 standard and may not be available in non -Motorola radios. Talkgroup conversations that involve radios currently holding off registration due to the FRHOT feature will still be available to those radios. Should the radio user need to participate in a talkgroup call, the pressing of the PTT button will force an immediate registration request to the controller at which time the affiliation and registration will be treated immediately as a normal request. When a site recovers from a failure scenario and provides a radio subscriber substantially higher level of coverage than the current site to which it is affiliated, the radio unit will try to register with this recovered site. To ensure the recovered site does not get overloaded with registration requests on the control channel, the system issues aRRHOT value which is issued by the system. This feature works similar to the FRHOT described above as each radio unit calculates a random time that determines when that radio unit attempts to register at the recovered site. A complete and detailed failure mode analysis of the effects of component failures for each element of the system, diagrams showing component failures within the system and narratives describing the resiliency of the network during specific component failures are provided in the following sections in response to the RFP 2.3.1(Failure Mode Analysis). Long -Term Outages The System is designed with multiple levels of redundancy to ensure users are minimally impacted by failure conditions. While every step has been made to ensure the system remains operational at all times, there are functions that can impact the systems operations that are outside the design constraints of the Motorola Solutions System. P25 System and Services Agreement (R1422515R1/P1) Page 64 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The primary cause of long-term outages is backhaul transport. However to try to minimize this potential from occurring, Motorola Solutions has included redundant routers to provide for path diversity for the transport system. While Motorola Solutions develops very robust equipment, equipment at times fails. To minimize system outages, or Broward County reductions due to failed equipment, Motorola Solutions will provide the spare equipment identified in the equipment list that will help to ensure the system continues to operate when equipment failures occur. There is no single component contained within the proposed ASTRO system that will cause long-term outage. Motorola Solutions has provided a failure analysis to explore failure of the major components within the system. 1.10.4.3 Narrative of Failure Analyses [See Appendix] 1.10.5 System Expansion A. The systems shall be expandable by adding additional hardware and/or software to increase coverage, capacity, or features. Provider shall provide equipment such that the system can be easily expanded by a minimum factor of 10 percent. B. The trunked system shall be expandable to meet the minimum capacities listed below through the addition of hardware. All software licenses shall be included consistent with the terms of this Agreement. Replacement of the system and site control equipment to meet this requirement shall not be acceptable. 1. Interconnected system and site control equipment (if using a centralized architecture) — 3 2. Total simultaneous talk paths— 36 3. Simulcast cells — 5 4. Sites per simulcast cell — 30 5. Unit IDs—250,000 6. Affiliated users—15,000 7. Talkgroups — 1,000 8. Dispatch positions - 100 1.10.5.1 Broward County and Expansion Features of System The system is designed with expandability and future migration in mind. ASTRO 25 is an IP-based, standards -based, scalable technology. Motorola Solutions' experience in designing and implementing solutions to specifically address customers' needs makes Motorola Solutions uniquely suited to meet P25 System and Services Agreement (R1422515R1/P1) Page 65 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 and exceed the County's current communications requirements, as well as providing a system that will grow as the needs of the County grows. Master Site and System Expansion Capabilities Motorola Solutions' solution is modular and scalable, with controllers that can accommodate drastic expansion in RF sites, channels, console positions, and subscribers as the needs of the County changes over time. The expansion capabilities provided in the table below show that the solution will meet the County's needs now and in the future. The System facilitates future expansion by allowing system elements to be added over time as needed, including the addition of radio sites, channels, dispatch sites and consoles. P25 System and Services Agreement (R1422515R1/P1) Page 66 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ASTRO 25 System Reserve Broward Platform System Broward County Zones 7E 1 6 Individual IDs 250,000 E E 150,000 (Note 1) 100,000 UNS License for GPS and Text 100,000 E 0 100,000 UNS License for Location 100,000 E 0 100,000 Key Management (OTAR) Licenses 64,000 E 0 64,000 Talkgroups 16,000 s 16,000 - Zone Level Broward County Broward County is PER ZONE Broward County Increases by Adding Zones Channels per Zone (Trunking + 1000 E L 43 (Note 1) 957 Conventional) Simulcast Subsystems 64 s 3 61 ASTR025 Repeater Sites (ASR) 150 E 4(Note 1) 146 (Including Simulcast Subsystems) Maximum Dispatch Sites 100 E 5 (Note 2) 95 Maximum Dispatch Operator 500 E E 90 (Note 2) 410 Positions Zone Historical Reports Application Licenses 10sE 3 7 Dynamic Reports Application Licenses 5sE 3 2 Zone Watch Application Licenses 10 s E 3 7 Affiliation Display Application Licenses 5 s E 3 2 UNC Application Licenses 7 s E 2 5 UEM Application Licenses 16 s E 3 13 RCM Application Licenses 32 s E 3 29 Historical Reports Application Licenses 10 s E 3 7 Subsystem Broward County Broward County is PER Subsystem Broward County Increases by Adding Subsystems P25 System and Services Agreement (R1422515R1/P1) Page 67 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Single Simulcast Subsystems Sub -sites per Simulcast Sub- 14 — Main Simulcast 18 32 s systems 4 — Backup Simulcast 28 36—TDMA s 36 — Main Simulcast cell - 12 —Backup Simulcast 24 Talkpaths per Simulcast Subsite 29—FDMA s 18 — Main Simulcast cells 11 6 — Backup Simulcast 23 ASTRO 25 Repeater Sites (ASR) Talkpaths per ASR site 36-TDMA s 10 — BC Station 106 26 MCC Dispatch 24 — Sunrise 26 Maximum Dispatch Operators per 500 E L 23 —Pembroke Pines 27 Dispatch Site 21— Coconut Creek 29 24 — Sunrise 16 Conventional Legacy Channels via 40 s 24 — Pembroke Pines 16 CCGW per Dispatch Site 24 —Coconut Creek 16 11— Sunrise(Note 2) 60 Analog Conventional Channels per 71 s 11— Pembroke Pines(Note 2) 60 Console Operator Position 11— Coconut Creek(Note 2) 60 Affiliated Talkgroup IDs per Console Operator Position 160 s 160 - Simultaneous Audio Sessions per Console Operator Position 60 s 60 - Note 1: The system is capable of 250,000 IDs once the hardware is expanded to multi -zone; the 250,000 unit ID licenses are included. The ASTRO 25 System proposed is a 14-site, 19 channel simulcast system and one ASTRO Repeater site with six channels. Also proposed is a 4 site, 7 channel backup simulcast trunked system and 8 conventional 700 MHz repeaters that are included in the system count as well as a 4 site 3 channel analog 800 MHz simulcast MA system. Note 2: The ASTRO 25 System proposed has a dispatch console system at Sunrise, Coconut Creek and Pembroke Pines which has been included in the dispatch site and operator counts. The 11 conventional channels are 3 for 800 MA and 8 for the standalone conventional 700 repeaters. Note 3: The aforementioned site licenses and dispatch licenses are not site -specific and can be utilized by the County at any site or dispatch location (subject to availability of hardware at the site or location). Note 4: As indicated above, the subscript "S" indicates a system maximum capacity (e.g., a functional capacity limitation); the subscript "E" indicates the maximum capacity of the equipment as designed, and additional hardware may be necessary to increase capacity, and the subscript "L" indicates a P25 System and Services Agreement (R1422515R1/P1) Page 68 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 license capacity (i.e., the maximum number of licenses permitted under the current license scope and software, and additional licenses may be required to increase capacity). 1.10.5.2 Radio Channel/Site Expansion Capabilities System Capabilities The table above highlights the capabilities of the system that will utilize a small portion of the system's Broward County, ensuring the system is able to grow with the County over the next 15 to 20 years. In developing the design of the system, special attention was paid to ensure the system was not close to its limits so that future growth could be achieved without immediate restrictions. An example of such design is with the number of sites that can be supported by a Simulcast system, 32. The System will utilize 11 sites allowing for the growth of 21 additional sites to be added to the main simulcast cell. It is important to note that in selecting to add sites to a simulcast cell, factors such as site separation are important as sites that are too far apart can have adverse impact to the system's performance while sites that are too close may not contribute to the system's overall coverage. Motorola Solutions is willing to work with the County to ensure any future expansion is reviewed thoroughly and the best solution is developed. In addition to being able to add sub -sites to the proposed simulcast sites, the system also has the ability to add additional simulcast cells or ASTRO Repeater sites to provide the best solution for the County. The system is capable of supporting 64 simulcast cells while only three cells are being proposed. Channel and site expansions are therefore important capabilities that the County must have to ensure growth can be easily accommodated. The following will address the impacts of both for future system expansion. Channel Expansion per Site, per Channel The main single simulcast sub -system is equipped with 36 TDMA talkpaths. This is the maximum for a single simulcast sub -system and is the most talkpaths offered by any manufacturer. Additional talkpaths would be accomplished by expanding into another simulcast sub -system. The System uses both standalone GTR8000 Base Radios with expandable transmitter combiners and racks designed to achieve economy of scale by accommodating more than six channels per rack for the main simulcast system and GTR 8000 Expandable Site Subsystem (ESS) 6 channels per rack for the backup system which then allows the effective utilization of certain infrastructure equipment including the Frequency Standards, RF antenna systems, Tower Top Amplifiers and Receiver Multi -couplers. The ESS configuration allow for two ESS racks to share a RX antenna system and to share a TX antenna system. The main simulcast single sub -system will have 19 channels (36 TDMA or 18 FDMA talkpaths). Separate GTR8000 Base Radios were chosen to minimize the number of racks required which is a total of three per remote site. Included along with the radios are two 12-channel transmitter combiners to accommodate the 19 channels and have one additional port for expansion. P25 System and Services Agreement (R1422515R1/P1) Page 69 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Since the ESS racks are able to accommodate six channels, these were chosen for the backup simulcast system and to provide transmitter ports and receiver ports for the two 700 MHz conventional repeaters at each of the four sites designated that are common with the backup system sites. The Backup sites are proposed with seven channels to provide the 12 TDMA talkpaths as required. Since two ESS racks are able to accommodate 12 channels, there are three expansion channels available for the backup system sites, which also meets the RFP 10% expansion requirement. The proposed TTA receiver multi -coupler is capable of supporting up to 32 receiver ports and used only for the main simulcast receivers. Channel expansion for the Backup simulcast sub system beyond three channels will require an additional ESS rack to be added which will provide an additional six channels. To provide additional autonomy for the Backup simulcast sub system, a separate receive antenna system, TTA and receive multi -coupler with 16 receiver ports is provided however for every three ESS racks (18 stations) only one of the MCU ports needs to be utilized. This separate receive antenna system will also be used for the three channel 800 analog Mutual Aid simulcast system receivers. The Backup Simulcast system will operate on either the 700 MHz band or the 800 MHz band. The Backup Simulcast will have a separate transmit antenna that will carry the seven trunked channels and either the two 700 MHz conventional repeaters or the three 800 MHz mutual aid repeaters. The 800 MHz MA or 700 MHz conventional stations not sharing a combiner with the Backup Simulcast system will utilize a standalone 4-channel combiner. The three channel 800 MA simulcast system required by the RFP is designed with GTR8000 Base Radios and expandable transmitter combiners and will use the same receive antenna system as the Backup simulcast system. The 800 MA channels will have a dedicated 4 channel transmitter combiner and transmit antenna. This also meets the 10% expansion capabilities required. Any expansion of existing systems is dependent on the existing and any new frequency pair having sufficient channel spacing to achieve full performance of the combiner system. The standard standalone transmitter combiners and ESS transmitter combiners are designed to accommodate channel spacing of 150 kHz or greater to achieve best performance. Channel Expansion Process for Main & Backup Simulcast Cell Prime Sites The system includes simulcast cells with the corresponding simulcast sub -sites and channels at each site. The main and backup simulcast prime sites have comparators corresponding to each channel. Expansion of a channel requires an additional GCM8000 comparator module. Each comparator shelf holds two channels thus, if there is an existing shelf with a single channel, a comparator module will only be required to add one additional channel in addition to the software. If two channels are to be added, then an additional comparator shelf with power supply will be required. All GCM8000 comparator power supplies are bussed together so that if any shelf power supply goes down, the shelf and comparator modules will continue to function. Channel Expansion Process for Standalone 700 MHz Repeater Sites The system includes two standalone 700 MHz repeaters at each of four sites. At each of the four sites, the two channels are housed in one GTR 8000 ESS Backup rack, which includes the necessary combiner, multi -coupler, and power supply modules. Each site has one TX antenna and one RX P25 System and Services Agreement (R1422515R1/P1) Page 70 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 antenna for the Backup system and the two conventional repeaters. In the proposed design, adding an additional channel to the two proposed up to three require a new radio and license; expanding beyond three channels will necessitate a new rack, combiner, Receiver Multi -Coupler (RMC), radio, and license. The above channel expansion will be contingent on a number of items, including the frequency pair being added to the system, space, and electrical requirements. Site Expansion As noted earlier, the system is designed to utilize a small portion of the system's capability. The expansion of the system can occur in several ways: Simulcast Cell Addition As the needs of the County change, it's important that the system is able to accommodate these changes. The system is currently proposed with three simulcast cells for the single simulcast and four simulcast cells with the dual simulcast system. Therefore the County, in the future, can add either 61 (or 59) additional simulcast cells to the system. The location of these cells will be based on the needs of the additional RF coverage that is deemed necessary. In some instances it may be appropriate to utilize a small simulcast cell while in other situations larger cells. The flexibility of the system permits the system to develop as the desires of the County change. Simulcast coverage is typically beneficial for the ability to reuse frequencies while covering a large geographical area. This allows the County to focus coverage where it is needed the most. Simulcast Sub -site Addition The Main simulcast system is designed to accommodate 11 Simulcast sub -sites. That allows for 21 additional sub -sites to be added to the simulcast cell. The addition of the simulcast sub -site must consider several factors including site separation to ensure the additional sites do not have a negative impact on the remainder of the sub -site's performance. The Backup simulcast system is designed with 4 sub -sites. That allows for 28 additional sub -sites to be added to the cell. ASTRO Repeater Site Addition The ASTRO P25 system allows for 150 ASTRO Repeater sites (ASR) (minus Simulcast cells). The System has one ASR site, thus future expansion capabilities of 149 ASR sites is significant. P25 System and Services Agreement (R1422515R1/P1) Page 71 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Grade of Service (GoS) — Trunked System The required Grade of Service — GoS from the RFP is defined as "1% with 90% of the units that are placed in queue receiving a channel grant within two seconds. Motorola shall provide a single cell design with 36 talkpaths, delivering a 1% GoS for 3361 active users with Transmission Trunking and users making an average of five calls per unit per hour with a four second call duration. Motorola shall validate that the 36-talkpath single cell design will accommodate the system load provided by the current system loading and usage patterns during the busy hour, plus projected future growth. Motorola shall consider the impact of the loss of two-talkpaths due to a repeater failure. 1.10.6 Site Selection The radio coverage across the County's service area will be provided by a total of 15 RF remote sites: 14 simulcast remote sites, and one standalone ASR site. Motorola Solutions has designed the system with the eight mandatory sites required by the RFP plus four additional sites that provide the service area reliabilities that are required by the RFP. The site selection process has several steps that are followed to come up with sites that are optimum for meeting the wide area coverage required. First, the existing sites are taken into consideration by modeling the coverage for the required building losses and service area reliabilities. By doing this first, it determines where the additional coverage is required and if these existing locations are good locations for the overall wider area coverage. Next, additional sites are modeled by using the potential new sites listed within the RFP Appendix B- Addendum 2. Once these type sites are gathered for the deficient areas of coverage, they are entered into the Hydra coverage modeling tool. The Hydra modeling can then begin and determine which sites are the best locations to provide the additional coverage to meet the requirements of the RFP. The precise site locations shall be confirmed by the Parties during the design phase and confirmed in the Final Design. Any modification to the site locations shall have no effect upon scope and shall not increase price or cost to County, unless confirmed in an appropriate amendment executed by the Parties. The Parties shall work cooperatively to achieve the final site locations and incorporate same into the Final Design in accordance with the agreed Project Schedule, scope and price. The P25 700 MHz TDMA trunked system design consist of an ASTRO 25 simulcast cell. The remote simulcast sites contain the following RF equipment plus the ASR (i.e., multi -cast repeater site) as further detailed in SOW A-2: 1. CORE Tower— Main system one 19 channel simulcast prime site with co -located sub -site and main master site. 2. EMS Tower— Backup system 7 channel simulcast Prime Site, co -located sub -site and 800 Mutual Aid 3 channel prime site with co -located simulcast remote sub -site. 3. EOC Tower — DSR (backup) master site 4. Coconut Creek Tower — Main system one 19 channel simulcast sub -site, Backup system 7 channel simulcast sub -site and 800 Mutual Aid 3 channel simulcast remote sub -site. 5. Davie Tower — Main system one 19 channel simulcast sub -sites, Backup system 7 channel simulcast sub -site and 800 Mutual Aid 3 channel simulcast remote sub -site. P25 System and Services Agreement (R1422515R1/P1) Page 72 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. Channel 2 New Tower —Main system one 19 channel simulcast sub -sites, Backup system 7 channel simulcast sub -site and 800 Mutual Aid 3 channel simulcast remote sub -site. 7. Markham Park Tower— Main system one 19 channel simulcast sub -site. 8. Playa Del Mar Building— Main system one 19 channel simulcast sub -site. 9. Point of America Building — Main system one 19 channel simulcast sub -site. 10. Miramar Tower — Main system one 19 channel simulcast sub -site. 11. Deerfield — 300' self-supporting tower; Main system one 19 channel simulcast sub -site. 12. Tamarac —300' self-supporting tower; Main system one 19 channel simulcast sub -site. 13. West Lake Park — 300' self-supporting tower; Main system one 19 channel simulcast sub -site. 14. BC Station 106 New Tower (Everglades) — 300' self-supporting tower; ASR 6 channel repeater site. 15. Parkland: 300' self-supporting tower; Main system one 19 channel simulcast sub -site. 16. Pompano Beach: Rooftop -based Main system one 19 channel simulcast sub -site. 17. West Hollywood: 300' self-supporting tower; Main system one 19 channel simulcast sub -site and GEO Redundant 19 channel backup prime site. A map showing the geographic location of the simulcast sites and the single ASR site in the system is provided in the figure below. P25 System and Services Agreement (R1422515R1/P1) Page 73 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.10.7 Coverage A. The radio systems shall be designed to serve within the geographical boundaries of the county. B. Coverage design, implementation, and testing for the system shall adhere to the TIA Telecommunications Systems Bulletin (TSB) #88-D or latest version, Wireless Communications Systems Performance in Noise -Limited Situations. C. Channel Performance Criteria (CPC): P25 System and Services Agreement (R1422515R1/P1) Page 74 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 RF coverage is defined as the digital Bit Error Rate (BER) that provides an audio signal that delivers a minimum Delivered Audio Quality (DAQ) score of 3.4, for both outbound (talk -out) and inbound (talk -in) communications. 1. TIA defines DAQ 3.4 as "speech understandable with repetition only rarely required," which is the minimum acceptable level for public safety communications. 2. Provider shall provide sample audio files, in .wav or .mp3 formats, demonstrating the audio quality associated with DAQ levels of 3.0, 3.4, and 4.0. D. The radio system must provide coverage as described below: 1. The primary system shall provide 95 percent coverage for a portable radio inside a building with 25 decibels (dB) of attenuation, with 95 percent reliability, for those portions of the county east of 1-95. 2. The primary system shall provide 95 percent coverage for a portable radio inside a building with 20 dB of attenuation, with 95 percent reliability, for those portions of the county west of 1-95, east of U.S. 27 and south of 595; and west of 1-95, east of the Sawgrass Expressway and north of 595. 3. The primary system shall provide 95 percent coverage for a portable radio operating outdoors, with 95 percent reliability, for the portion of the county west of U.S. 27 and south of 595, and west of the Sawgrass Expressway for the area north of 595. 4. The primary system shall provide 95 percent coverage for a mobile radio operating on a boat, with 95 percent reliability, for those portions of the county in the ocean extending 10 miles eastward from the coast. 5. The trunked backup system shall provide 95 percent coverage for a portable radio operating outdoors, with 95 percent reliability, for those portions of the county east of U.S. 27 and south of 595, and east of the Sawgrass Expressway and north of 595. 6. A map of the various coverage areas has been included in Appendix C. Boundary files to be utilized for each of these areas have been included as a supplement to the solicitation. A. Provider shall utilize the following assumptions for subscriber radio performance in order to meet stated coverage requirements: P25 System and Services Agreement (R1422515R1/P1) Page 75 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. Vehicle -mounted mobile radios — Standard dash- or trunk -mount, with % wavelength whip antenna mounted on the trunk with an output power of 10 watts 2. Boat -mounted mobile radios —Standard dash -mount, with % wavelength whip antenna mounted on a boat mast, assumed at 5 feet above sea level 3. Portable radios — Standard portable radio outdoors or indoors: a. Talk -out to a portable radio on hip with a swivel belt clip b. Talk -in from a portable radio at hip using a remote speaker microphone c. % wavelength flexible whip antenna d. Hip level shall be assumed as a height above ground at 3.3 feet e. Appropriate level of in -building attenuation for both talk -out and talk -in based on coverage requirement The P25 700/800 MHz TDMA simulcast trunked system coverage will meet the requirements of the RFP. The System will deploy 11 trunked simulcast sites operating in primarily TDMA mode with full interoperability access by subscribers operating on FDMA. The coverage predictions and guarantee of coverage will provide 95% Service Area Reliability for portable radios worn on the hip with Remote Speaker Microphones operating outside on the roads and streets within Broward County at Delivered Audio Quality (DAQ) 3.4. In addition, the guarantee also provides 95% Service Area Reliability for portable radios worn on the hip with Remote Speaker Microphones operating within the five defined service areas detailed in the RFP for the following minimal acceptable db loss: 1.10.7.1 Coverage Maps All coverage maps provided by Motorola under this SOW A-1 shall comply with the following: A. Provider shall submit both talk -out and talk -in system composite coverage maps for all proposed design configurations. Updated maps shall be provider for updated site configurations until a final site configuration is available. The maps shall be clearly labeled and shall show link budget calculations for each of the following: 1. Mobile radios — Standard dash- or trunk -mount, with antenna mounted on the trunk 2. Portable radios — Standard portable radio outdoors: a. Talk -out to a portable radio on hip with a swivel belt clip b. Talk -in from a portable radio at hip level with a swivel belt clip 3. Portable radios — Standard portable radio indoors: P25 System and Services Agreement (R1422515R1/P1) Page 76 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 a. Talk -out to a portable radio on hip with a swivel belt clip, with 20 dB of building loss b. Talk -in from a portable radio at hip with swivel belt clip, with 20 dB of building loss c. Talk -out to a portable radio on hip with swivel belt clip, with 25 dB of building loss d. Talk -in from a portable radio at hip with swivel belt clip with 25 dB of building loss B. Coverage shall be depicted using a light transparent color or cross -hatching for those areas that meet or exceed the minimum coverage reliability threshold. C. All maps must clearly delineate the difference between areas with coverage predicted to be equal to or greater than DAQ 3.4 and areas that do not meet this coverage requirement. Vendors shall include the effects of simulcast interference in all coverage maps (if applicable). D. Coverage maps shall be provided in two formats: 1. 11-inch x 17-inch, full -color, hardcopy 2. softcopy format printable to 11-inch x 17-inch full color. E. Coverage maps must include sufficient detail to allow another party to duplicate the predicted coverage utilizing propagation software. F. Coverage maps shall display coverage extending beyond the county borders. G. Coverage maps shall consider any anticipated degradation resulting from simulcast interference. H. All maps shall include a background layer suitable for County reference (e.g., topographic map, roads, rivers, etc.). Link budgets shall be provided that clearly define the following minimum information for both the radio and paging systems, related to each map and each site: 1. Base station/repeater RF power output 2. Antenna Height (radiation center) 3. Antenna mounting azimuth 4. Antenna gain/transmission line size 5. Antenna down tilt (if applicable) 6. Transmit effective radiated power (ERP) 7. Receiver sensitivity 8. Combiner loss/multicoupling gain/tower-top amplifier (TTA) gain/noise 9. Net TTA amplification gain P25 System and Services Agreement (R1422515R1/P1) Page 77 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 10. Mobile and portable antenna height for talk -out and talk -in 11. Mobile and portable RF output power 12. Mobile and portable gain or loss factors 13. Mobile and portable ERP. 14. Configuration of field units (e.g., talk -out to a portable inside 10 dB -loss buildings) 15. Simulcast timing parameters (if applicable) A. Thirty -meter U.S. Geological Survey (USGS), North American Datum (NAD)-83 terrain elevation data shall be used for coverage simulations. Alternatively, 3-arc-second data may be used where 30-meter data is not available. B. Antenna pattern files shall be provided in the EDX or PLANET formats. The system will comply with the Coverage Maps listed in the table below. Coverage Maps .. # 1A Description APX Mobile- Sedan Antenna 1/4 Wave -0 Configuration On Trunk Lid Location Outside on Street 1B APX Mobile- Sedan 1/4 Wave On Trunk Lid Outside on Street 2A APX Portable 1/2 Wave Flex RSM Swivel Clip Outside on Street 2B APX Portable 1/2 Wave Flex RSM Swivel Clip Outside on Street 3A APX Portable 1/2 Wave Flex RSM Swivel Clip 20 db Loss Service Area 3B APX Portable 1/2 Wave Flex RSM Swivel Clip 20 db Loss Service Area 4A APX Portable 1/2 Wave Flex RSM Swivel Clip 25 db Loss Service Area 4B APX Portable 1/2 Wave Flex RSM Swivel Clip 25 db Loss Service Area 5A APX Portable 1/2 Wave Flex RSM Swivel Clip Outside Backup Service Area 5B APX Portable 1/2 Wave Flex RSM Swivel Clip Outside Backup Service Area 6A APX Mobile- Boat 1/4 Wave 5' mast w/ Grd Plain Off Shore Service Area 6B APX Mobile- Boat 1/4 Wave 5' mast w/ Grd Plain Off Shore Service Area 1.10.7.2 Map Criteria The tables below detail the map criteria used to generate the coverage maps. (Coverage is calculated for the Tamarac site based up a 180' monopole, rather than the design requirement of a 300' self-supporting tower. Channel 2 is calculated based upon the existing structure, rather than the design requirement of a 300' self-supporting tower. These deviations are by agreement for purposes of coverage analysis.) P25 System and Services Agreement (R1422515R1/P1) Page 78 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Q z (D on n n n n n n n n r n n n n ii Q CD N N N N N N N N N N N N N N N N N . N 6 QN \ \ \ \ \ \ c-I \ e-I \ \ c-I \ \ ei a-i \ ci \ ci a-i \ e-I H N N N N N N N N N N N N N N N N N N F O Z T a C C C C C C C C C C C C C C C (V o 0 0 0 0 0 0 0 0 0 0 0 0 0} o > z z z z z z z z z z z z z z z O In a) V m V Ln ;T m Ln CT c Y m V m Ln W E C C lD Ol lD Ol LO O1 01 lO ci l0 ci O1 lD O1 Id:O1 -7 0 - v LO v W V W W v M a Cn W a W W LO x N N N N N N N N N N N N N N N N N � ei ci ci c-I c-I c-I c-I e-I c-I ei ci a-i a --I ci a-i e-I Y Y I]A Ln LnL!1 Ln Ln Ln Q Q 0 r, 0 r, 0 0 0 0 0 r, 0� c-I O F O O O O O O Y O M O M Ln M M O O O O M O M Ln Ln Q N V N V c-I V V N N N N-tt N V H O x (D -O rl r-I H e-I e-I c-I e-I e-I e-I c-I r-I r-I a --I r-I rl e-I Q GA 'O Ln 'O O 'C O 'C 'C 'C 'C O '� 0 'O 'C v E- E- E n 0 E E E E- E- E E oC O H O N O N O O O O N O `-I O O L L • V Ln 0 V 0 m 0 Ln 0 m O Ln O 0 0 0 0 = O r-I M 0 LD 0 H 0 W 0 lD (U w x m�-Zt N m N m m m H m N m m m VI L 75 3 v 0 O r Ln O 0 o 0 0 0 Ln o 0 0 a E 2 o -az J _ N x E 0 rn O� Oi rn m m m m m m rn rn rn rn Ln Oi U o v v v v v T v v v v v v v It Itv v Y m rn N v m v m ao m m rn v ao rn ci rn D_ (p H N w N ci N N O l0 O N N Ln N C' ?: LU .--. N M N l\O H l\O M i\-I N M M H N ID H n N N N N N N M -i r-I n N l\O N O N t\O E F ,x m m N 0 m 0 m r-I m v m V1 �--I M 4 M Ln In Ln m Ln Ln Ln Ln Ln Ln m Ln Ln N Ln Ln CD J \ \ \ \00\ \ \ \ \00\ -- \ \ \ x ci rl e-I ^ t-i ^ ei t•-I e-I e-I r-I rl ei c-I C-I c-I c-I c-I c-I a --I t-i e-I e-I e-I C to Q Q H N O N O N O O ci N c-I O -1 O ci O �_ O Ln O Ln O O Ln Ln Ln Ln O O Ln Ln Q ci N c I N c-I N N O O H O N O N �--I c-I x (,'J rl r-I r-I r-I 'I r-I e-I e I i--I rl ci Q 'c Ln 'c 0 'c O 'c 'c c c O 'c 0 'c 'E E- E- E r- 0 E E E E r, E- E E x O ci O N O N 0 0 0 0 `4 0-1 0 0 i+ Y cu t `a) O O m M O O O O O m m m 0 to m O 0 m Y w N w m I, m m N W N LO N w N w N w N Ln H m N LD N w N w N H m w m X O H N U v y 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 O O O O O O O O O O O O O O O O O d \ N E ci \ 0 r-I \ 0 r-I \ 0 r-I \ 0 r-I \ 0 r-I \ 0 r-I \ 0 r-I \ 0 \ 0 0 r-I \ 0 r-I \ 0 ci \ 0 c-I \ 0 -1 \ 0 \ c-I 0 c I \ 0 O � <6 Ln LnLnLnLnLnLn In In Ln Ln In Ln Ln Ln Ln m z � 7 � O1 E v m V v y l> o z (1)a E N E i N -° V a)m y C > O -O p 7 f0 Y w O E v J m 2 C- W O N Y C m N m_ m v E ^ E O Ln Lccn O u O u 2 a t0 o O 2C c L V O1 O rp H : O D- �i m o_ U Co G w ci LrI -1 LO N N IZT c-I Ln -r- N X d LU DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 O • • • ++ ' m ' . .. L • • F O . • • O ' 0 U ' m c 4) T ' C H Q m X O OL C Sto a •°1 • � C Q O }w 9 -0'� • • M "r7 y Cf u w m H O 'a • • - Q Q ` j LL N O... M E OJ Cf 'a �= -0 • r Q C LL a�i H C O 'y X LA 0 t— O m V L a-+ X O Xr0+ O .• H Q fC f0 a 3 - uj E- V • L m O '^ d E - - L 1 • 1 1 ^' L "CL N r-I d r-I Li) c-I Ul N N c-I Ln = N X d LU DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.10.7.3 Coverage Model Hydras' Overview Hydra is an innovative software tool developed by Motorola Solutions to accurately predict coverage, model traffic (voice and data), analyze interference, plan channel re -use, and perform other design tasks for radio networks. This description concentrates on Hydra coverage planning aspects. Our solution presents typical Hydra coverage analysis for Broward County. A. Hydra Development Motorola Solutions' Hydra coverage prediction tool was developed to provide accurate coverage simulations by applying proven models to detailed system and environmental data across large geographical areas. To create an accurate picture of the predicted radio coverage, many elements must be considered. Some of these elements, called system factors, are related to the system design parameters. System factors affecting coverage performance include frequency, distance, transmitter power, receiver sensitivity, antenna height, and antenna gain. Other factors, called environmental factors, vary according to the path taken by the radio signal and the environment surrounding the receiver. Environmental factors include terrain variations, obstructions, vegetation, buildings, ambient noise, and interference. All coverage prediction methods try to account for both types of factors and incorporate them into a computational model. In general, the currently accepted models, such as Okumura, Longley-Rice, and TIA provide excellent portrayals of radio coverage when used within their respective ranges of applicability. In the past, this level of analysis was adequate for the type of basic systems that were available. However, today's complex technologies, such as digital voice radios, packet data systems, or simulcast, require a much more in-depth analysis of the expected coverage performance to create a cost- effective design. This makes it necessary to select the appropriate coverage model, provide accurate representation of the environmental factors throughout the service area, and apply the coverage analysis method to every location within the service area. Recognizing these facts, Motorola Solutions has developed Hydra, a multi -purpose network design tool that includes a coverage analysis program. Taking advantage of the knowledge gained from Motorola Solutions' many years of practical experience and coverage testing, Hydra provides a superior means for analyzing system coverage. This program, unique to Motorola, employs a technique of computing coverage on every tile in a service area rather than along a finite number of radials. Hydra computes "layers" of these tiles, with each layer containing the values of propagation model losses, coverage simulation results, or datasets. Layers can be displayed separately or in any combination as maps of the service area. P25 System and Services Agreement (R1422515R1/P1) Page 81 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.10.8 Site Equipment Overview The Provider shall provide all site equipment, which shall be new, of high quality, and designed to provide high reliability to support mission -critical communications. The site equipment, or RF infrastructure, consists of the following components: A. System and site control equipment B. Simulcast equipment C. Receiver voting D. Transmitters E. Receivers F. Combiners/multicouplers/TTAs G. Antenna systems H. Alarm remote terminal units I. GPS frequency standard All remote site equipment shall be configured to operate utilizing a -48 VDC power plant. All equipment located at dispatch facilities shall be configured to operate on the existing 120 VAC power systems. The system is made up of various site equipment components that include System Controllers within the Master Sites, Simulcast Controllers and Voting comparators at the Prime Sites, Base Station Radios at the simulcast Remote sub -sites and Dispatch consoles at console dispatch sites. 1.10.8.1 System and Site Control Equipment A. The system and site control equipment shall be capable of controlling all voice and data channels in the System. The control equipment may use a distributed or centralized architecture. B. The control equipment shall fully support APCO P25 functional requirements, features, and performance objectives, including the CAI and the ISSI. C. Provider shall provide a P25 ISSI for Broward County to connect to the adjacent four systems operated by neighboring agencies (Motorola Host Master Site, Miami -Dade, Palm Beach, Collier). The ISSI connections shall allow automatic system -to -system talkgroup roaming on up to 10 simultaneous talk paths per connected system. D. Provider shall provide a P25 CSSI to enable Broward County to connect to P25-compliant console systems operated by nine neighboring agencies. The CSSI connection shall allow direct P25 System and Services Agreement (R1422515R1/P1) Page 82 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 talkgroup access at the Broward County public safety answering points (PSAPs) without requiring a conventional interface. At the heart of the Broward County Radio System Infrastructure design is the Master Site. The Project 25 Master Site provides connectivity between voice subsystems that includes the simulcast prime sites, ASTRO Site Repeater sites and console dispatch sites. The Project 25 Master Network Switch 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 Broward County. The Project 25 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 Broward County. The Master Site serves as a central point for all system traffic in the Project 25 system, houses redundant zone controllers, and provides system management interfaces. Because the Master Site is so critical for wide area operation, the system has a second Master Site at an alternate location. This provides the highest level of redundancy known as Dynamic System Resilience. If the main Master Site have a catastrophic event that completely disables the main Master site, the backup Master Site takes over control of the system. The Master Site equipment is basically an IP network made up of redundant servers, LAN switches and Core routers. 1.10.8.2 Zone Core The ASTRO 25 master zone core is the main control point for the communications system. The zone core contains the computing backbone for the system and all the components necessary for controlling voice calls and data messages within the system. In addition, the zone core provides the hardware and software components used for network management and system configuration. The zone core for the County has been sized to provide for the current and future needs of its user base, with the capability to support up to 150,000 radios on a single zone and 250,000 radios on a dual zone. Per the RFP requirements, 250,000 unit ID licenses are included in the System pricing. The system architecture is designed with inherent fault distribution, ensuring that a single point of failure will not cause the complete disruption of communications. The ASTRO 25 architecture ensures that voice operation is maintained despite any single component failure anywhere on the network. In the case of a fault, the system can reroute the IP voice and data packets among the various redundant router configurations, and notify the supervisor/network management terminal of the fault. Redundant Zone Controllers The system offers redundant zone controllers. The zone controller is a software application that provides centralized control for call processing and mobility management functions in an ASTRO 25 system. The zone controller application is responsible for processing calls, managing audio paths, controlling zone infrastructure, and providing services to subscribers and dispatch consoles. The zone controller application resides on the HP DL380 dual virtual management servers (VMS01 and VMS02) and runs ReclHat Linux in a VMware ESM virtual machine. P25 System and Services Agreement (R1422515R1/P1) Page 83 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The dual virtual management servers at the zone core contain the zone controllers and NM applications. Virtualization allows multiple virtual machines, with heterogeneous operating systems, to run in isolation, side -by -side on the same physical machine. Each virtual machine is allocated CPU, memory and storage resources used by the operating system and application associated with the virtual machine. Virtual machines are encapsulated into files, making it possible to rapidly save, copy, and provision a virtual machine. Full systems (fully configured applications, operating systems, BIOS, and virtual hardware) can be moved from one physical server to another, for high -availability maintenance and continuous workload consolidation. These two physical servers (VMS01, VMS02) provide the processing for the redundant zone controllers, along with NM and reporting. These applications are distributed for reliability. The zone controller operates in a redundant configuration. The LAN switch is used to switch system resources between the zone controllers and provide high availability call management within the zone. While the zone controllers are powered and enabled at the same time, only one is actively participating in call processing tasks at any one time. The redundant zone controller configuration provides protection against a single point of hardware or software failure that results in the loss of wide area trunking until the zone controller is repaired or recovers automatically. The redundant zone controller remains in the standby state as long as the active zone controller does not report a malfunction that causes a switchover. 1.10.8.3 Zone Core LAN Switch Configuration The zone core equipment includes a set of Core LAN switches that are the aggregate of all the Ethernet interfaces for all servers, clients, and routers at the zone core. Additional LAN switches are used for remote site access aggregation and in other capacities within the ASTRO 25 system, including at the prime site, the dispatch centers, and each of the remote RF sites. Core LAN switch Core Routers The core routers perform the routing control of audio, data, and network management traffic in and out of the zone, replicating packets while achieving the fast access levels required by real-time voice systems. To increase availability, two core routers are used. The zone core audio, data, control, and network management equipment interfaces to the remote RF sites via the remote site aggregation LAN switches, through the core router. P25 System and Services Agreement (R1422515R1/P1) Page 84 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.10.9 ASTRO 25 Prime Simulcast and Voting Site Design The prime site acts as a control and digitized audio center for the simulcast subsystem. The prime site will be co -located with the zone core at the main dispatch site. The site links route IP packets containing control and audio information from the prime site to each simulcast remote site. 1.10.9.1 GCP 8000 Controller The GCP 8000 controller is designed for use in ASTRO 25 trunking systems. The GCP 8000 controller provides call processing and acts as a site link between the simulcast subsystem and the zone controller. The GCP 8000 is capable of supporting up to 36 voice paths and up to 30 simulcast sub -sites. The GCP 8000 controller communicates with interconnected ASTRO 25 infrastructure elements, such as the GTR 8000 base radio subsystem and the GCM 8000 comparator, which are also designed to be P25 compliant. The GCP 8000 controller will be implemented in a fully redundant configuration with two controllers. The redundant (standby) controller automatically takes over site link or site control operations when the active GCP 8000 controller has failed. Communications between the active and standby controllers are configured through an Ethernet link. Channel status information will be kept consistent between the active and standby site controller to assure that accurate channel capability information will always be sent to the zone controller. In addition to the redundant controllers at the prime site, there will be a third controller at the redundant prime site, which will take over control operations automatically in the event of a failure of both controllers at the prime site. 1.10.9.2 Prime Site Routers The prime site router provides a WAN interface that carries all of the traffic between the active and backup prime site to the zone core including voice, control, and network management traffic. The router provides direct IP packet network management connectivity for the remote sites to the zone core as well as: 18. Traffic prioritization —the router applies the correct prioritization marking to the packets leaving the site. 19. Fragmentation —the router fragments large IP packets as necessary. 20. Dynamic Host Configuration Protocol (DHCP) service —this service allows the technician with a properly configured computer running on a Windows operating system to connect to the LAN at the site. Used with the NMS, the prime site router provides a proactively managed system and a means of receiving and reporting failure alarms, all of which increase router availability. Motorola Solutions has designed this system with redundant prime site routers, split between the prime and redundant prime sites. 1.10.9.3 GCM 8000 Channel Comparators The GCM 8000 comparator is a band -independent device that acts as a subsystem -wide signal collector, voter, and distributor. The GCM 8000 comparator is designed for use in ASTRO 25 IP P25 System and Services Agreement (R1422515R1/P1) Page 85 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 simulcast trunking systems. With multiple base stations operating on the same frequency, it is possible for multiple RF sites to receive a single field unit transmission. The GCM 8000 compares the various voice traffic signals and interprets and selects the best audio samples and assimilates an enhanced audio signal for simulcast broadcasting. By simultaneously transmitting the enhanced audio signals from multiple sites within the system, both coverage and signal quality are improved. The geographic redundant prime site configuration for the County consists of redundant comparators at the primary simulcast prime site and at the secondary simulcast prime site. 1.10.9.4 Redundant Prime Site Ethernet LAN Switches A pair of interconnected LAN switches is required to connect GCM 8000 comparators and GCP 8000 controllers to the prime site router. Two switches are used at the site to increase availability, and they are interconnected via Gigabit Ethernet trunks. Each of the two prime site controllers is connected to its own switch. Therefore, if one switch should fail at least one controller will have connectivity. Motorola Solutions has designed this system with redundant prime site Ethernet switches, split between the prime and redundant prime sites. 1.10.9.5 TRAK 9100 Time and Frequency Standard The prime and remote sites include a redundant GPS-based time and frequency standard that provides a frequency/timing device for synchronized simulcast transmissions. In addition, the GCM 8000 comparator will receive timing information from the GPS. Each simulcast remote site will also utilize a GPS to provide the frequency/timing data needed to allow synchronization of simulcast transmissions. Each TRAK has redundant power supplies and Rubidium oscillators clocked by dual GPS antenna systems. 1.10.9.6 Redundant Remote Site Routers Remote site routers provide an interface that routes all of the IP network traffic to and from the prime site for communication with the zone core. The site routers provide the following function for the network management packets: 21. Layer 3 routing —This restricts local traffic from accessing the microwave system and forwards important voice and data information to the prime site. 22. DHCP service —This service allows the technician with a properly configured computer running Windows to connect to the LAN at the site. Used with the system's NM, the remote site router provides a proactively managed system as well as a means of receiving and reporting failure alarms. 1.10.9.7 Ethernet LAN Switches The simulcast sub -site LAN switch performs two main functions at the simulcast remote site. The switch provides a 10BaseT LAN interface for the GTR expandable site subsystem and a 10BaseT port for the site router. P25 System and Services Agreement (R1422515R1/P1) Page 86 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The service technicians using CSS software use a switch port to gain access at the site to service the site and access the system's GUIs to maintain the system. DHCP service allows the technician with a properly configured computer running Windows to connect to the LAN at the site. The site router will assign the computer running Windows an IP address that will allow the computer access to the ASTRO 25 network. 1.10.9.8 Base Station Equipment A. General 1. Base station equipment shall be solid state in design and function with standard site conditions for temperature, altitude, and humidity. 2. Equipment shall have alarm contact interfaces to provide status to a separate alarm system. 3. The units shall be as compact as possible, with mounting configurations for standard relay racks or cabinets. B. Base station equipment shall comply with Part 90 of the FCC Rules and Regulations, as well as appropriate EIA and similar agency standards, and be an FCC -type accepted for use in the 700/800 MHz frequency band. C. Prior to implementation, the Provider shall perform the following studies at each site: 1. Intermodulation analysis — Provider shall consider equipment from all tenants located at the proposed site, per FCC license information. 2. Maximum Permissible Exposure (MPE) study (per latest revision of the FCC Office of Engineering and Technology [OET] Bulletin 65) — Providershall consider equipment from all tenants located at the proposed site, per FCC license information. a. Provider shall gather the site data needed for these studies D. The Provider shall resolve all issues predicted during the intermodulation analysis and MPE studies. If an intermodulation problem is identified within 12 months after Final Acceptance, the Provider shall resolve the issue without degrading system coverage or performance, at no cost to the County. E. Base station equipment must dynamically support either Phase I or Phase II talkgroups based on the talkgroup type that is selected. Static assignment of Phase I or Phase II operation is not permitted. P25 System and Services Agreement (R1422515R1/P1) Page 87 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A. GTR8000 Site Repeater/Base Radio The GTR 8000 base radio consists of a transceiver module, power amplifier module, fan module, and power supply. The transceiver module includes the functionality for the exciter, receiver, and station control. The base radio software, configuration, and network management, as well as inbound/outbound traffic handling, are performed through this transceiver module. On -board serial and Ethernet ports are located on this module for local servicing via CSS. The power amplifier module amplifies the low-level modulated RF signal from the transceiver module and delivers the amplified signal on the path to the transmit antenna. The power supply module supports the transceiver and power amplifier modules, and can also provide auxiliary power to a connected site controller or Receive Multicoupler/Low Noise Amplifier (RMC/LNA). 1.10.9.9 Antenna Systems A. Provider shall provide all antenna system equipment necessary for a complete design. B. Antennas shall meet the following requirements: 1. 7/16-mm DIN connector 2. Passive intermodulation (PIM) rated 3. Voltage standing wave ratio (VSWR) of 1.5:1 4. Return loss of 14 dB 5. 6-foot sidearm mount 6. Compliant with TIA-222 Rev G and Florida Building Code requirements C. Antennas shall be appropriate to provide the required coverage and meet applicable FCC rules and regulations. D. Transmission line type and length shall be constructed of copper and appropriate to provide the required coverage. E. Transmission lines must be equipped with the following accessories: 1. Hanger kits (no snap -on kits permitted) 2. Hoist grip 3. Ground kits 4. Radio frequency (RF) surge suppression 5. Connectors installed per manufacturer specifications P25 System and Services Agreement (R1422515R1/P1) Page 88 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 F. Transmit combiner/receiver multicoupler: Provider shall include sufficient capacity for a 10- percent growth in the number of connected transmit and receive stations. G. Provider shall include detailed specification sheets for all proposed equipment, including, but not limited to antennas, receiver multicouplers, transmitter combiners, and TTAs (if applicable). H. TTAs shall be accompanied by a test line for troubleshooting purposes. I. Antenna systems shall be designed with sufficient redundancy so that a failure to any one component in the transmission system will not disable the entire site. J. A spare 700/800 MHz antenna shall be mounted at each location with an appropriately sized feedline to temporarily replace a failed transmit or receive antenna. K. Transmit antennas shall be equipped with an Advanced Power Meter (APM) to provide VSWR alarming. Motorola Solutions' design utilizes the primary, backup and mutual aid simulcast systems using antennas from three manufactures that include Sinclair, RFI, dbSpectra and RFS. These antennas will meet the requirements as indicated the table below: P25 System and Services Agreement (R1422515R1/P1) Page 89 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 EN i LL N LL i LL N LL i LL N LL q N LL 0 -1 I cr-I i LL r1 - N m rl N m rl N m N m ^ O -I H O -I H rl N U rL Ln LL 2 N U Ln LL 2 V U Ln LL 2 N N U U u Ln LL 2 Ln Ln Ln Ln U U H H H a M a1 C a1 C 2 a1 C a1 C M a1 C a1 C co Z 00 U1 O Z O Z M 00 O Z O Z 00 w O Z O Z 00 N 00 N M N LL 0 lD l0 Q N J a1 C a1 C LML N a1 C a1 C ML L N a1 C a1 C co Z Liu co O Z O Z r1 O Z O Z r1 LU O Z O Z cn L O O O W O L 00 O L W O L W O L W O L W O L W O L W O 00 O M M M M � 00rq M � 00rj E M 00 00 00 00 00 00 00 00 00 00 00 00 D ri D r-I D r-I r-I D D D w m w 0o w 00 0o w L0 �0 M U- Q M U- Q M U- Q Q M LL M LL M LL N rl N rl N rl N rl N rl N rl N rl N rl N rl N rl W r W r- 0= W r- W r" W r" W r" m m m m D D w 0p l0 0p l0 0p 0p l0 w l0 M LL a M LL a M LL a a M LL M LL M LL N r-I N rl N r-I N rl N r-I N r1 N r1 N r-I N r-I N r-I W W r, CL W r, Lu n W r, W r, m cono no 0 00 i U- rl N a a O a a O H a a Z oo Z Z W00 Z Z Z Z N N U U U u a M� U- Q a a U- a a r I ^ �, a a Z w COZ Z U LNL Z Z 00~ Z Z N N = U N U CNI N Q L.L N Q L.L N Q LL LL i Q J Cj rl 0_ C,4rl 0_ rl N rl N ^ O H O H N U Ln LL = LLU In >m U N L L = LLU Ln m > U N L L = LLU Ln m �: LLU Ln m �: 00 U 00 U U N L L = > Ln > V) Ln Ln U U T-I' N LL p ' N LL J i N LL Q i N LL i N LL Q i N LL J i N LL J rl rl N LL Q r1 J rq a) r-I N rl J 01 r-I N rl J r-jrl N rl N CL ~ ~ r-I J U N L L = W co 3 U LL _ W m U In LL _ W m 3 W co 3 W u u U LL Ln Ln Ln N Ln Ln V N U U 7 Y �O V L C� C N ai a1 U a1 Y Y �, 'T L a1 c i U U U fu D_ a O d a U O H c-I !Z c-I cc Ln r-I Ln N N IZI- c-I Ln = N X d W DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 I LL p I r-I LL p LL r-I N J N r-I N J N N r-I Q O H COO H m U LNL z rL 00 U LU V) 00 U LU V) Ln = H r-I O a1 a1 a1 a1 aJ C C C C C M co O O O O O 00 Z Z Z Z Z Uu 00 N tD a, a, a, a, a, LML C C C C C N O O O O O r-I Z Z Z Z Z LU r- Ln L1 00 Op L1 00 Op L1 00 Op LL 00 Op ' M ' Q M M M � M � t= 00 r I O Z 00 00 00 00 D �.D m D t.0 -1 00 w M M LL Q LML Q N Q N c-I N r-I N r-I N r-I r-I LU Z r- 0C LU OC Ln Ln Q J m Ln J m w m w m M N LL Q N r-I .� N r-I N .� cN-I L U z x cc LULU r- N N Q J m Q J m 00 Q Q Q Q Q Z Z Z Z Z O 00 V V LL a a a a a en U Z Z Z Z Z U LL Ln = c-I i LL c-1 i LL c-I c-I N J N c-I c-I N J N � C Q O x 00 c-I 00 F- c-I LU co O Z LU V) LU Ln V)O V)Z c-I c-I i N LL C J c-I c-I � N LL J i N LL I, r-I N ^ r-IN r-I Q z 00~ w co 00~ w m U= NN NLn V V cu a1 O C O J 4-1 (0 � Q 3 tv to In LU a D_ oo Z > 2 o m 0 LU 11 cc Ln r-I Ln N N IZI- c-I Ln = N X d LU DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Additional information about the site coordinates, tower heights, Antenna Site Registry, and antenna model information is included as Evaluation Criteria Attachments Section 2.4. All of the antenna models used will meet the RFP requirements and the TIA-222 Rev G Florida Building Code. The BLR12A-B1 does not have a PIM rating since it is a receive antenna and is only banded for 700/800 receive thus it is not PIM rated. All models use the 7/16-mm DIN connector. Antenna models to manufacturer are as follows: 1. SC-412 & SE-4192 — Sinclair. 2. DS7E12F36 — dbSpectra. 3. CC807 — RFI. 4. BLR12 — RFS. All transmission lines are LDF copper. 1 %" is used on all transmit lines except at Playa Del Mar and Point of America where 7/8" copper is used. All receive main lines will use 7/8" copper. All TTA test port lines will use %" copper. All transmission line attachment, grounding and termination will meet the RFP requirements for antenna mounting (6' side arms, Stainless attachment hardware, hoist grips, RF TVSS, etc.). Motorola Solutions R56 quality standards require that all transmission line meet these requirements. 1.10.9.10 Backup and Interoperability Systems 7 Channel 700 Trunked TDMA Backup Simulcast System A. Provider shall provide a P25 trunked backup system that includes the following elements: 1. Operates in the P25 mode with dynamic use of either P25 Phase I and P25 Phase II talkgroups at the base station level. Dynamic talkgroups are not required. 2. Utilizes the 4 radio sites identified in Appendix B. 3. Utilizes a total of 7 frequencies, providing 12 concurrent Phase II talk paths, or 6 concurrent Phase I talk paths. 4. Houses simulcast control equipment at the EMS radio site, which will not be utilized within the design of the primary trunked system. 5. Provides the greatest level of autonomy possible from the primary trunked system to provide a high likelihood that the system will remain functional in the event of a failure of the primary trunked system. P25 System and Services Agreement (R1422515R1/P1) Page 92 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. Includes the capability to support P25 data applications at a baud rate of 9,600 bits per second per channel, while providing priority to voice traffic. Motorola Solutions shall provide a 7 channel P25 TDMA simulcast system that will provide the 12 talkpaths required by the RFP. The 7 channel Backup Trunked TDMA Simulcast System prime site will be located at the EMS tower per the RFP requirements. This prime site will be configured as a standard prime site with redundant GCP8000 simulcast controllers, GGM8000 site and sub -site routers, site LAN and backhaul switches along with the same GCM8000 voting comparators as is used in the main system. The prime site will also have a dedicated TRAK frequency standard as is required at all trunked prime sites. The P25 Backup Trunked simulcast remote sites use GTR 8000 ESS (Expandable Site Subsystem) racks, a space -efficient, single -rack design that integrates up to six GTR 8000 base radios, power supply modules, redundant GPB 8000 Reference Distribution Modules, redundant Ethernet LAN switches, redundant site gateways, transmit combiner, and receiver multi -couplers. A diagram of the GTR 8000 ESS is shown in the table below. This platform was chosen to provide additional autonomy for the Backup System. The GTR 8000 platform requires low power, minimized rack space, and utilizes an IP-based transport layer, which allows increased backhaul flexibility. Subscriber audio is received and packetized by the stations. The internal GPB 8000 provides both LAN routing and GPS services for each station at the site thus the system is not dependent on the main system TRAK GPS. The packetized audio is routed via the GPB 8000 and the local redundant site routers to the MPLS/microwave backhaul network. The microwave routes the audio to the active prime site to be voted. P25 System and Services Agreement (R1422515R1/P1) Page 93 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Microwave Backhaul to Regional Control Locations US Receiver Microwave Backhaul to Regional Control Locations yWave uWave Backhaul Backhaul r t r r r t r r r r I r r r � LAN Switc I r r � Rack - Integrated Redundant Site Gateways BPS Receiver I I I I I I Tx I I RX Antenna Antenna In -Rack Rx r Muilticoupler I & Combiner - 0 0 900 I 0 000 I I I 0000©o 700 MHz GTR 8000 ESS for Simulcast --------------- Simulcast GTR 8000 ESS Layout The built-in six -channel transmitter combiner prepares the output signals from all the RF carriers in the GTR 8000 ESS for transmission on a single antenna. The cavity combiner has built-in single -stage circulator at each input. Each input to the combiner has a tuning and locking mechanism for each cavity to provide on -site frequency selection/tuning and to prevent unintentional detuning. Circulator loads are on the back of the combiner on a common heat sink. Since the Backup System is 7 channels and includes two conventional 700 MHz repeaters required by the RFP, the transmit output from each GTR 8000 ESS is combined with a second GTR 8000 ESS through a phasing harness. If the backup system is implemented in the 800 MHz band, the system shall share a combiner with the 800 MHz MA repeaters. Subscriber audio is received and packetized by the stations. The GPB 8000 included in the GTR 8000 provides both LAN routing and GPS services for each station at the site. The packetized audio is routed via the GPB 8000 and the local redundant site routers to the microwave backhaul network. The microwave routes the audio to the active prime site to be voted. The IP simulcast subsystems do not require site controllers at the remote sites in order to operate under control of the GCP 8000 site controllers at the simulcast prime sites. Simulcast site controllers P25 System and Services Agreement (R1422515R1/P1) Page 94 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 control the simulcast site over 10013aseT Ethernet IP links. This reduces equipment cost and eliminates a potential point of failure. In addition, each site uses redundant site gateways and reference distribution modules for network transport, switching, and GPS reference functions. All equipment is provided with alarm outputs as required to deliver status information to the network management system. 3 Channel 800 Mutual Aid Simulcast System B. Provider shall provide a P25 conventional backup system that includes the following elements: 1. Operates in the P25 conventional mode. 2. Utilizes 2 standalone (non -simulcast) conventional 700 MHz repeaters at each of the 4 radio sites identified in Appendix B. 3. Provides no wide -area dependencies for each individual repeater. C. Vendors shall propose a wideband analog conventional simulcast repeater system to replace the County's current National Public Safety Planning Advisory Committee (NPSPAC) repeaters, which include the following: 1. 8TAC92 2. 8TAC93 3. 8TAC94 4. Each channel shall be configured in a 4-site conventional simulcast configuration with stations located at the EMS, Coconut Creek, Channel 2, and Davie tower sites. 5. Voting equipment shall be located at the EMS location. 6. These stations must be configured to operate in the receive -only default mode, with the ability to remotely turn on transmit capability from any of the three PSAPs. Motorola Solutions has provided a design for a three channel 800 Mutual Aid system to replace the existing system required by the RFP. The system is a 3 channel by 4 site analog simulcast using the required NPSPAC MA channels detailed in the RFP. The Prime Site would be located at the EMS site along with a simulcast remote. The prime site would be connected to the Master Sites by the microwave network transport that would provide connectivity to all dispatch locations. A Conventional P25 System and Services Agreement (R1422515R1/P1) Page 95 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Channel Gateway (CCGW) at the prime site provides the IP connectivity to each of the three conventional channels. The prime simulcast control and voting uses the MLC8000 Voting Gateway Unit (VGU) for each channel. The three channels are configured using three GTR8000 Base Radios at each site with an MLC8000 Audio Gateway Unit (AGU). The GTR Base Radios require a 5 MHz frequency reference and the VGU/AGU require a 1pps/5MHz composite for synchronization of the simulcast. The existing site TRAK frequency standard will supply the required 5 MHz for each GTR station and 1PPS/5MHz composite for the MLC8000 VGU and AGU by the addition of a TRAK expansion shelf with additional Digital Distribution Modules (DDM) at the four Backup sites. The 800 MA system will have a transmitter combiner, Advanced Power Monitoring (APM) unit and transmit antenna. It will also have a TTA, 16 port receive multi -coupler and receive antenna that will be shared with the Backup Trunked System. 1.10.9.11 Mobile Communications Trailer and F-350 Truck The mobile communications trailer shall include the following components: 1. Appropriately sized vehicle for towing the proposed trailer 2. Graphical user interface (GUI) -based gateway system supporting up to 4 patches and 12 ports for locally interfaced control station radios. 3. Total of 10 rack -mounted control station radios broken down as follows: a. 8 x 700/800 MHz P25 Phase II capable b. 1 x UHF narrowband analog capable c. 1 x VHF narrowband analog capable d. 2 x UHF MOTOTRBO capable 4. Control station antennas must be omnidirectional and provide a minimum of unity gain. 5. Control station combiners are permitted to reduce the number of control station antennas. 6. Two 700 MHz repeaters operating in the P25 conventional mode: a. Antenna minimum gain of 6 dBd and omnidirectional b. Stations equipped with duplexers to share a single antenna for transmit/receive c. Repeaters shall be single frequency and locally controlled 7. Extendable automatic (not manual) mast with pre -mounted antennas that can be raised to 75 feet P25 System and Services Agreement (R1422515R1/P1) Page 96 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 8. Onboard 15 kw diesel generator to support continuous operation of equipment for three days between fuel refills 9. Automatic transfer switch 10. Single onboard HVAC to support proper environmental control of equipment 11. The ability to bypass onboard antennas in order to connect to pre -mounted antennas on an adjacent tower site. 12. Workspace for one technician 13. Steel storage cabinet 14. Hydraulic braking system 15. Motorola will provide training for the communications trailer onsite at Broward County. Motorola Solutions shall provide a properly sized F-350 truck and the S8 Hybrid mobile shelter communication tower system. This integrated mobile communications trailer includes a robust hot dip galvanized trailer frame chassis, designed to operate in multiple surfaces, including unimproved roads. The trailer is equipped with hydraulic brakes per the RFP specifications and with (2) 8000lbs torsion axles, giving the ability of independent suspension and max ride stability. The trailer chassis also contains four outriggers designed to increase the foot print of the tower deployment and prevent any overturn momentum. All 8000lbs jacks, a total of nine, are in place to facilitate the easy operation and leveling of the mobile shelter tower. An 8x8 foot shelter, climatized and R18 Insulated is capable of supporting up to three full communication racks, and many other accessories. An 85 foot unguyed (no guy wires needed) is also part of this turnkey system. This tower is designed following the TIA-222G regulations and is capable of operating in winds up to 80mph, with a large payload installed. The system is also equipped with: 1. Full size spare tire. 2. Hydraulics brakes. 3. Complete Motorola Solutions R-56 grounding and bonding system. 4. 15KW super quiet diesel Kubota generator, special design for mobile trailer tower units. 5. 100gallon fuel tank, providing over 96 hours (4 days) of operation at full load. 6. Auto transfer switch to provide power uninterrupted power operation between grid power and generator power. P25 System and Services Agreement (R1422515R1/P1) Page 97 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Other accessories include: 1. Storage tool box and storage cabinet. 2. Two roof mounts. 3. HVAC system, a total of 30000 BTUs. 4. Roxtec 1/0 Ports. 5. Coax reels. 6. Protect dri-dek flooring. 7. Cable trays. 8. Shore power cords. 9. Work lights for night operation. 10. Obstruction lights in accordance with FAA regulations. It is estimated that shipping weight of the system to be approximately 10500lbs. with a tongue weight set to be 9-12% of the overall weight, making this the lighter shelter trailer with an 85 foot unguyed tower available in the market, different of any steel or articulated tower system. The Aluma Tower SBhybrid can be towed by an F-350 truck model with no difficulty. The equipment installed within the shelter of the mobile communications trailer will consist of two P25 conventional repeaters, twelve control station radios and a Graphical User Interface (GUI) based control system for the radios. The two P25 conventional repeaters will operate in the 700 MHz band and each will interface to a single antenna on the trailer tower through a duplexer. Eight of the control station radios will operate in the 700/800 MHz bands and will be capable of P25 Phase 2 TDMA operation. These eight control stations will interface with an antenna pair on the trailer tower through a control station combiner. Three of the control station radios will operate in the UHF band, with one being capable of analog operation and the other two being capable of MOTOTRBO. These three control stations will interface to an antenna pair on the trailer tower through a control station combiner. The remaining control station will operate in the VHF band in analog mode and will interface to a single antenna on the trailer tower. Control of the radios will be provided by a Motobridge Radio Gateway Unit. A laptop will be included in the trailer, which will provide the GUI interface into the Motobridge gateway for radio control. The radio equipment will be installed in three racks within the shelter of the trailer, which will leave working space within the trailer for a single technician. Specification sheets for the mobile communications trailer and F-350 truck are as set forth in the Specifications (Schedule 8). 1.10.9.12 Data Capabilities A. Both the primary and backup systems shall be configured to support an integrated P25- compliant data stream on any voice channel, providing a desired data rate of 9,600 bits per second per channel. B. Voice must take priority over data in all circumstances. C. Examples of data applications that should be capable of utilizing the data stream include, but not limited to, the following: P25 System and Services Agreement (R1422515R1/P1) Page 98 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. GPS subscriber radio location 2. Over -the -air programming (OTAP) 3. Over -the -air rekeying (OTAR) 4. Fire station alerting signaling 5. Text messaging D. Data capabilities must support up to 1,000 concurrent subscribers E. The system must support GPS functionality from subscriber units that do not match the system manufacturer. F. The system must support data applications operating on a P25 data stream that do not match the system manufacturer. G. In the event third -party applications running on the system's P25-compliant data stream do not operate properly, Provider must cooperate with the third -party application vendor and the County to submit to laboratory testing with the provider of the third -party application, in order to validate and achieve proper performance and optimize usage on the Broward County system. Both the main primary system and the backup system have IV&D included for all voice channels to support any future applications required by the RFP. P25 features such as OTAR and GPS should work across vender platforms; however there is no interoperability tests defined for these features. Motorola Solutions will work with any other Yd party GPS venders that adhere to the P25 standard data stream and cooperate with the third -party application vendor and the County to submit to laboratory testing with the provider of the third -party application, in order to validate and achieve proper performance and optimize usage on the Broward County system. P25 System and Services Agreement (R1422515R1/P1) Page 99 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.11 Dispatch Console 1.11.1 General Requirements and Features A. Provider shall provide pricing for replacement of all existing Gold Elite consoles with state-of- the-art, IP-controlled consoles. B. Provide shall provide ISSI-compliant consoles with licensing for connection to console systems operated by nine (9) neighboring agencies. C. A list of existing console systems and operator positions is provided in Table 1 below. Table 1: Broward County Public Safety Answering Points (PSAPs) -mum .- Site Address of ..- L ir jkositij Sunrise 10440 West Oakland (Central Park Terrace, Sunrise, Motorola Gold Elite 24 Yes Dispatch) FL 33351 6057 S.W. 198th Pembroke Pines (South Terrace, Motorola Gold Elite 23 Yes Fort Lauderdale, Dispatch) FL 33311 Coconut 4800 W. Copans, Creek (North Coconut Creek, Motorola Gold Elite 21 Yes Dispatch) FL 33063 D. The dispatch console is a critical link for public safety personnel. It is here that the dispatch operator must relay critical information from the public to public safety personnel in the field. At times, the dispatcher may be in stressful conditions with lives at risk. It is imperative that the dispatch console be laid out in a manner that results in the operation of such consoles being second nature to the dispatching personnel. The dispatching console shall provide the operator with as much information as necessary without the screen being cluttered, and shall be easily navigated to perform necessary functions. Features of the console shall include, but not be limited to: 1. Dispatch console equipment (operator positions) shall be designed to be placed on existing furniture and provide operators with an ergonomic design that permits ease of operation over extended periods, typically 8-12 hours for each operator. P25 System and Services Agreement (R1422515R1/P1) Page 100 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Console positions shall be able to acoustically cross -mute channels in order to eliminate acoustic feedback between operators. 3. The screen display shall be designed so that all dispatching functions shall be operable from one display. 4. The screen display shall be very flexible, enabling authorized personnel to determine which functions are available at each operator position. 5. New features and screen configurations shall be supported through software programming and not reconfiguration of hardware. 6. Capability to program, store, retrieve, and edit multiple custom operator screens and configurations for each operator position should be provided. 7. Operator screen configurations and alias database should be stored locally or on a centrally located server. 8. The dispatch console shall display an alias name on screen when a unit with a radio ID stored in the alias database is transmitting. 9. Operator positions shall have the ability to decrypt and encrypt secure voice communications. Channels shall have a distinctive icon if encryption is being used for that channel. All consoles shall be configured to provide end -to -end Advanced Encryption Standard (AES) encryption to personnel in the field. 10. Upon activation of an emergency alarm by field units, dispatch positions shall provide an audible alert, display calling unit ID, and provide a visual alert of an emergency activation. 11. Operators shall have the ability to utilize a headset, foot pedal, and stationary gooseneck - type microphone for transmitting audio. 12. The capability to converse on the telephone utilizing the same operator headset that is used for radio conversations shall be provided. 13. Instant recall shall be provided allowing the operator to review and verify his or her recent traffic. Playback shall be available at the operator position. P25 System and Services Agreement (R1422515R1/P1) Page 101 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 14. Ability to display a loss of wide -area trunking notification if the system is experiencing a loss of connectivity. 15. The console system shall support an auxiliary input/output port for the control of analog logic sources. E. The dispatch console system must seamlessly integrate with the City of Fort Lauderdale's Motorola P25 system currently being deployed. The system is served by the Motorola hosted master site located at Motorola's facility in Plantation, Florida. The interface may be accomplished through CSSI or other means that satisfy all identified requirements. 1.11.2 Trunked Radio System Requirements A. Dispatch consoles shall be compatible with the proposed P25 trunked radio system. Dispatch consoles shall directly interface with single- and multi -site trunked system controllers, and shall allow interoperability between trunked and non-trunked channels in the system. B. Dispatch consoles shall be able to monitor and transmit on all proposed trunked systems. Backward compatibility with the existing trunked system for ease of cutover is desired, but not required. C. Dispatch consoles shall be equipped with an instant transmit switch for each talkgroup displayed. D. In a trunked system with radio IDs, the push -to -talk (PTT) ID of the unit calling shall appear in addition to a call indicator. After the call is completed, the unit's PTT ID shall remain displayed until another call is received. E. To aid dispatchers in a busy system, a list of the last 15 radio IDs should be available in a recent call list. F. In order to enhance dispatcher effectiveness in a PTT ID system, the various display modes available shall interact as follows: 1. An operator shall be capable of setting up (and subsequently knocking down) an emergency call from the dispatch console position. 2. An option shall be provided to allow private communication between a dispatch console operator and a radio user. Once the operator is involved in a private call on a specific P25 System and Services Agreement (R1422515R1/P1) Page 102 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 resource, the operator shall not receive audio from another radio attempting to call on that same resource. 3. An option shall be provided that assigns priority to associated talkgroups. The dispatcher shall have the choice between normal preset priority and tactical priority, with tactical being the second -highest priority for a talkgroup in a system. G. In the cases of multi-talkgroup transmit or talkgroup patch, the use of more than one trunked repeater should not be allowed; the talkgroups should be merged onto a single repeater in order to conserve repeaters. H. It shall be possible to temporarily mute unselected talkgroups. The unselected audio will un- mute automatically after a programmable preset time. Mute shall be 20 dB minimum. Dispatch consoles shall have the capability to patch together two or more talkgroups so that users may communicate directly. J. If the dispatcher attempts to make a call on a trunked radio system connected to the dispatch consoles and all trunked channels are busy, visual and audible alerts will be initiated at the dispatch consoles. 1.11.3 Conventional Radio System Requirements A. Dispatch equipment shall include an instant transmit switch for each conventional repeater channel and/or base station. B. The console system shall support a minimum of 24 conventional resources interfaced to the radio backhaul network through conventional gateways at each of the three PSAPs (72 conventional resources total). The conventional resources need to be available to the consoles in the event of a loss of wide -area trunking. C. On conventional resources capable of operating on multiple frequencies/modes, a control/indicator shall be provided to select the desired transmit frequency/mode (select channel). The select -channel function shall cause the associated channel to switch frequencies/modes. Once a channel has been selected, the operator shall be able to transmit on this channel by pressing the footswitch or transmit button. D. The conventional gateways shall support the following interfaces: 1. Analog Interfaces P25 System and Services Agreement (R1422515R1/P1) Page 103 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 a. 2-wire input/output b. 4-wire c. VOX and Carrier Operated Relay d. PTT Relay Output e. Line Operated Busy Light (LOBL) Detectors f. Analog Logging Output g. Secure/Clear Call Input 2. Conventional Channel Types a. R1 b. T1R1 c. T2R2 d. T4R4 e. T8R8 f. T12R12 g. T14R14 h. T16R16 i. M DC1200 j. P25 Conventional 3. Control Types a. E&M Control b. Tone Remote Control (TRC) c. Digital Control via IP link E. A transmit audio level meter shall be provided that indicates the level of transmitted voice. This meter also shall indicate the level of receive audio present on the selected channel. F. Operator positions shall have the ability to independently set each channel's volume level. Minimum audio levels shall be capable of being set to avoid missed calls. G. A control/indicator shall be provided to allow the operator to mute or unmute audio from unselected channels. Selected audio and unselected audio shall be audible from separate speakers. H. A control/indicator shall be provided that enables the operator to select multiple channels, which in turn gives the dispatcher the ability to broadcast to several channels at once. P25 System and Services Agreement (R1422515R1/P1) Page 104 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 I. Operators shall have the ability to patch two or more conventional repeaters and/or base stations together so that users may communicate directly. Operator positions shall be equipped such that a minimum of eight simultaneous patches shall be available. 1.11.4 Paging Requirements A. Consoles shall support current signaling methods as well the proposed alphanumeric paging format. Additional features shall be described. B. The console shall support the following paging formats: 1. Quick Call 1 2. Quick Call II 3. Dual -tone Multi -frequency (DTMF) 4. MDC-1200 selective call 5. Trunking call alert 6. POCSAG 512/1200/2400 bits C. Preprogrammed pages and groups shall be created and modified using the console alias database program. D. A manual page feature shall be provided. E. A visible indication shall be given when each page ends. F. A list of standard pages shall be created to enable the operator to select or stack pages to be sent to multiple recipients. G. An instant page feature shall allow operators to send multiple pages with the single press of a button. H. Consoles shall be capable of transmitting at least three distinctive alert tones indicating to field units the priority or type of dispatch to follow. 1.11.5 Operator Position Equipment A. All equipment supplied for use by the dispatch operators shall be capable of withstanding the 24 hours a day, 7 days a week (24 x 7) environment of today's PSAPs. B. All equipment supplied for use by the dispatch operators shall be integrated into the Viking USA furniture at the dispatch locations. P25 System and Services Agreement (R1422515R1/P1) Page 105 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. Operator position display monitors will be, at a minimum, 22-inch liquid crystal display (LCD) or light -emitting diode (LED) touchscreens, with resolution of 1920 x 1080 or better. D. Keyboards shall be a standard 101-key keyboard. E. Operator functions shall be executed by positioning a screen pointer (cursor) over the appropriate icon and pressing the mouse button, or by touching the monitor screen. F. A high -quality gooseneck microphone shall be provided for each operator position. G. Minimum of 2 speakers per position. H. Minimum of 2 headset jacks per position shall be provided that enable the operator to hear select audio via a headset and allow the operator to respond via a microphone attached to the headset. The headset plug inserted into the jack shall automatically disconnect the console's microphone and mute the select speakers. I. Optional pricing for wireless headsets shall be provided by Providers (Pricing provided in Price Workbook) J. A heavy-duty footswitch shall be provided to allow the operator to key the selected channel hands -free. K. Console units running on personal computers (PCs) shall be capable of providing a GUI using the Microsoft® Windows 7 operating system, be capable of local -area network (LAN) client -server architecture for network access, and be capable of supporting multiple Microsoft® Windows 7- compliant applications. L. PCs supplied shall be based on present state-of-the-art PC technology. 1.11.6 Common Electronics Equipment A. The common electronics equipment shall contain all equipment necessary to route audio and control signals between the dispatch operator positions and the proposed P25 trunked system. B. The common electronics equipment shall be capable of controlling the proposed P25 trunked system. P25 System and Services Agreement (R1422515R1/P1) Page 106 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. The common electronics equipment shall be capable of controlling the channels required or otherwise proposed by Provider. D. The common electronics equipment shall not have a single point of failure. Redundant cards and power supplies shall be used when feasible. E. The common electronics equipment shall be connected to the radio system directly; RF control stations shall not be used as primary connection to the radio system or the Fort Lauderdale system. F. The common electronics equipment shall be capable of receiving alarm information from distant communications sites and displaying this information on the dispatch screen. G. The common electronics equipment shall allow for a remote dispatch position. This remote dispatch position shall be connected via a LAN/WAN connection. H. The common electronics equipment shall include redundant components so that an equipment failure does not impact service to the connected dispatch consoles. 1.11.7 Console System Technology Motorola Solutions' dispatch console solution for the Broward County consists of 68 MCC 7500 dispatch console operator positions. The MCC7500 series consoles offer IP-based seamless connectivity between the County's dispatch operators and field personnel, as well as interoperability with existing trunked and conventional systems. The MCC 7500 meets the latest applicable standards of the FCC, EIA, NEC, IEEE, APCO Project 1613, and APCO Project 25. Flexible, Scalable Design The MCC 7500 will both provide the County with scalable, flexible, system architecture, sophisticated network management and security, and an easy migration to future capabilities. Their advanced feature set, ease of operation, and customizability will improve the safety of the County and County's first responders and decrease dispatch operator workload, while maintaining strict voice communications security. P25 System and Services Agreement (R1422515R1/P1) Page 107 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Tight Integration with the Radio System The consoles are directly integrated with the ASTRO 25 technology that provides the foundation of the radio solution. Operator positions connect directly to the radio system's IP transport network. Audio processing, encryption, and switching intelligence for dispatch are performed within each operator position, without additional centralized electronics. The console is capable of maintaining audio and data recording of the calls made on the communications system. Designed for Mission Critical Use An additional benefit of the MCC series console for the County is that it shares an operational likeness and user interface with the CENTRACOM Gold Elite consoles already in use by the County and County. This will reduce the need to formally train dispatch operators prior to transition from their current console to the new console. Motorola Solutions has had many successful migrations from Gold Elite to MCC 7500 consoles with little or no formal training. All console equipment is designed and built to withstand the high demands of a 24/7 dispatch environment and requires desktop and mounting space similar to a personal computer. The MCC 7500 console solution meets the County's need for a large-scale urbanized Public Safety/Mission Critical dispatch network. The system is highly configurable and customizable to ensure the maximum benefits are achieved for each dispatch agency. The software required to configure the system is provided within this proposal and can be configured in the field. 1.11.7.1 Dispatch System Reliability and Redundancy Motorola Solutions has designed to system to meet a stringent requirement at Broward County's dispatch centers. Each dispatch center includes dual site links to the ASTRO 25 master network sites in order to maintain a high level of redundancy. In the event of primary link failure, the secondary link shall seamlessly take over backhaul control with no impact to dispatch operations. If both site links fail, the affected dispatch center shall revert to fallback operations via wireless connectivity to the ASTRO 25 system. The Broward County dispatch centers are outfitted with a Conventional Site Controller (CSC) and Enhance Conventional Channel Gateways (ECCGWs) to facilitate this wireless fall back operation. The ECCGWs can interface back-up control stations to the dispatch center Radio Network Interface (RNI). This allows for the backup and interoperable control stations to be available as a resource to the MCC 7500 dispatch consoles. Dispatch operators are provided a visual notification on resources that are impacted by the site link failure allowing operators to quickly utilize other resources to continue communication. The setup of the dispatch position for fallback operations is customizable to meet the needs of each dispatch center. 1.11.8 Trunked Radio Dispatch System Requirements 1.11.8.1 MCC 7500 System Description The MCC 7500 console features an intuitive, GUI that operates under the Microsoft Windows platform and follows the same standards as other Windows programs around the world. The screen layout is simple and uses valuable space efficiently. Key information and critical functions are clearly identified P25 System and Services Agreement (R1422515R1/131) Page 108 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 with easy to understand icons. Dispatchers can quickly recognize these icons instead of reading text, hence maximizing their productivity. Many tasks can be completed more quickly and easily than ever before with the MCC 7500 consoles. Channels or talkgroups are displayed in on -screen "folders" for prioritization. Flashing red indicators easily identify incoming emergencies. Dispatchers can see information about who is calling, such as the time and call type. Trunked callers can be identified by real names versus numerical IDs. 1.11.8.2 Architecture Overview The MCC 7500 dispatch console is Motorola Solutions' IP high -tier radio dispatch console system designed for use in ASTRO 25 trunking systems. Some of the more important features of the MCC 7500 console include: 1. Seamless integration with ASTRO 25 trunking systems: — Supports the IP protocols of the trunking system's transport network; no circuit - switched network to packet -switched network conversion equipment is necessary. — Encryption and decryption is performed within the dispatch consoles, which allows true end -to -end encryption in the radio system. — Participation in the radio system's agency partitioning functionality. — Configuration of the console subsystem via the radio system's centralized configuration subsystem (NM) so the user has a single point to configure the radio system. The configuration subsystem may be accessed from multiple remote locations so users can still have convenient access while enjoying the benefits of centralized configuration. — Management of the console subsystem via the radio system's centralized network management subsystem so the customer has a single point for managing faults, accounting, performance, and security of the radio system. The network management subsystem may be accessed from multiple remote locations so customers can still have convenient access while enjoying the benefits of centralized management. 2. Centralized and/or distributed logging of conventional and trunked radio audio associated radio call information and certain radio system events. 3. Higher capacities in numerous areas. 4. The console system shall include a site trunking notification on each console position. The notification shall be provided through a mobile radio at each dispatch center interfaced through a console auxiliary input-output port. 1.11.8.3 Connection of MCC 7500 to IP Network Motorola Solutions MCC 7500 console equipment connects directly to the trunking system's IP transport network. It uses the IP packet protocols for passing call control data and call audio through the system. P25 System and Services Agreement (R1422515R1/P1) Page 109 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Elite Dispatch GUI The MCC 7500 dispatch console uses the Elite Dispatch GUI for displaying information to and accepting commands from the dispatch console user. The Elite Dispatch GUI is efficient, easy to use and intuitive, having been refined and proven through years of use in public safety dispatch centers around the world. The Elite Dispatch GUI in use today by the County is the same as the GUI and therefore will require minimal training for operators. An example of the Elite Dispatch GUI is shown in the figure below. Configuration Edit Vier Features Phone Folders Help /_Ll MOTOAOLA Tool Bars Resource Fddtl r1 Folders Radio ps Resource Auxiliary. T-1— _., Inputs/Outputs . ✓t 1�, ✓o Radio { ' ' II Resource Freg1 IPL Selecr2 -1 Status Bar M Mee! 3 1 Patch 2 I Patch,? Patch 1 1 V1 ( i I M11se 2 Z1TG 2 00041 Z1Pc 9 00001 Elite Dispatch GUI Radio Resources —Patch & Multi -Select Folders — Radio Resources Activity Log Window The Elite Dispatch GUI is based on Microsoft Windows GUI programming standards and contains many controls, displays, and features, which are familiar to anyone who has used Windows -based applications. These features are described in detail in the following sections. This GUI interface is the same as that currently in use by the County's Fire and Police Dispatchers thus making the transition to the new system very simple. Pull Down Menus The Elite Dispatch GUI provides the following pull down menus on a menu bar across the top of the dispatch window: 1. Configuration —Provides access to the configuration files used by the Elite Dispatch GUI. Also allows the dispatch application to be exited. 2. Edit —Allows various aspects of how audio, resources, and features are presented to the user on the Elite Dispatch GUI to be edited. Changes made using this menu are not permanent and are lost when the dispatch application is exited. 3. View —Allows the dispatch console user to control whether or not the Activity Log and Auxiliary 1/0 Windows are shown. P25 System and Services Agreement (R1422515R1/P1) Page 110 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4. Folders —Allows the dispatch console user to switch between folders, add folders, and change the folder tab width. Changes made using this menu are not permanent and are lost when the dispatch application is exited. 5. Help —Provides access to detailed online help for using the Elite Dispatch GUI. The user may customize which menus are displayed and what they contain via the Elite Admin application. Toolbars Up to two toolbars may be present across the top of the dispatch window and may be used to provide quick access to frequently used features. The following are examples of the items that may be placed in the toolbars: 1. Clock. 2. General Transmit Button. 3. Monitor Button. 4. All Mute Button. Many other items may be placed in the toolbars. The Elite Admin application is used to define how many tool bars are displayed and what they contain. Status Line A status bar is provided across the bottom of the dispatch window for viewing the status of the dispatch console as well as various error messages. The most current status or error message is displayed in the status line until cleared by the dispatch console user. The dispatch console user may scroll through the last 10 statuses/error messages to view them and may clear them by using the Features menu on the menu bar. Resource Folders The Elite Dispatch GUI provides up to twenty resource folders for organizing the various resources (radio resources, auxiliary input/output resources, etc) which are assigned to the dispatch console. These folders may be given descriptive names to simplify the organization of the resources. The resources on a folder are displayed when the dispatch console user clicks on the folder tab. Resources on folders that are hidden behind the one being displayed continue to operate in a normal manner. Radio resource audio on a hidden folder appears in the appropriate speakers/headsets along with a visual call indication on the folder tab. If an emergency alarm or call is received on a radio resource that is located on a hidden folder, a visual emergency indication is displayed on the folder tab. A resource may be placed on more than one folder at the same time. This allows customers to create folders for special situations without having to move resources back and forth between folders. The Elite Admin application is used to configure how many folders appear on the Elite Dispatch GUI and which resources appear on each folder. It is also used to put descriptive names on the folder tabs. During dispatch operations the dispatch console user may, if so configured by the Elite Admin application, be able to add, remove, or move resources on the folders. If this is done, these changes are not saved if the user logs off or changes configuration files for the dispatch application. P25 System and Services Agreement (R1422515R1/131) Page 111 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Up to 36 compressed radio resources may be viewed on one folder when the program is run in the standard 800 x 600 resolution and there is no patch or multi -select folders. If patch and multi -select folders are used and are set to the minimum height, then 31 compressed resources may be viewed. To figure the number of auxiliary input/output resources that could also be viewed, use the rule of thumb that two auxiliary resources can fit in the same space as one radio resource. In other words, instead of 10 radio resources, 20 auxiliary resources could fit in the same space. If the program is run in 1024 x 768 resolution, there is room for even more radio and auxiliary resources per folder. Radio Resources Voice communication paths in the radio system are represented as radio resources on the Elite Dispatch GUI. Radio resources are also referred to as "tiles" on the Elite Dispatch GUI. These radio resources are used by the dispatch console user to communicate on and control the radio system. The following radio resources are supported: 1. Trunked Talkgroups. 2. Trunked Announcement Groups. 3. Trunked Private Calls. 4. Analog Conventional Channels. Indicators and Controls A radio resource contains indicators and controls that allow the dispatch console user to monitor and control various aspects of the radio channel. Examples of the indicators and controls that may appear on a radio resource include: 1. Instant Transmit Button. 2. Transmit Active/Transmit Busy Indications. 3. Patch Active/Patch Busy Indications. 4. Received Call Indication. 5. Received Call Stack. 6. Individual Volume Control. The types of indicators and controls that appear on the radio resource depend on the type of radio channel it represents and how it has been configured in the Elite Admin application. The radio resource may be configured to always show the indicators and controls or to allow the dispatch console user to hide them when not in use to save space on the screen. Compressed, Larger Compressed, and Expanded Resources The figure below shows a radio resource that allows the dispatch console user to hide the indicators and controls. This is also called a "compressed" resource. Notice the small arrow button that allows the resource to be opened and closed to show the controls and indicators. P25 System and Services Agreement (R1422515R1/131) Page 112 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Flap Closed Flap Open Compressed radio resource The figure below shows a radio resource that always shows some of the indicators and controls, but allows the dispatch console to hide some of the others. This is also called a "larger compressed" resource. Flap Open Z1 C0HV 1 a aaa5 UNJ Larger compressed radio resource The figure below shows a radio resource that always shows the indicators and controls. This is also called an "expanded" resource. Notice there is no arrow button on the resource. Expanded radio resource Full parallel status for radio resources is reflected across all the dispatch consoles that have these radio resources assigned on them. That is, any activity or change on a radio resource appears on all dispatch consoles that have that resource assigned on them. P25 System and Services Agreement (R1422515R1/P1) Page 113 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Received Call Stack The received call stack provides the dispatch console user with a visual record of the most recent inbound calls on radio resources. This allows the dispatch console user to keep track of calls during busy traffic periods. Outbound calls on radio resources from dispatch consoles (both the dispatch console containing the received call stack or parallel dispatch consoles) are not shown in the received call stack. The calls are displayed in list format on a radio resource with the most recent calls at the top of the list. The number of calls displayed in the list is configurable as is the type of information displayed. The types of information that can be displayed are unit ID, unit ID alias, site ID, zone ID and, type of call and time. If an alias is available for a piece of information it is displayed, otherwise the raw information is displayed. The figure below shows a radio resource containing a received call stack. I�I Received 01 Call Stack Received call stack on a radio resource The received call stack provides a quick way for a dispatch console user to respond to calls in the stack. Various types of mouse clicks on calls in the stack provide the dispatch console user with different ways to reply to the call. The received call stack is configurable on a per -resource per -console basis, so a resource on one dispatch console can have it while the same resource on another dispatch console does not have it. The received call stack has a fixed memory of 25 calls, but the number of calls that are displayed is configurable via the Elite Admin application. The number displayed may be set anywhere from three to 24 calls in increments of three. Regardless of how many calls are actually displayed, the dispatch console user can always scroll through all 25 calls in the stack's memory. Stack display size is configured on a per radio resource per dispatch console basis. That is, each resource on a dispatch console may have different sized stack displays and the same resource on different dispatch consoles may have different sized stack displays. The dispatch console user can delete individual calls from the received call stack. All of the calls listed in a received call stack can also be deleted with a single action. Auxiliary Input and Output Resources Control relays and input buffers are represented as auxiliary input and output resources on the Elite Dispatch GUI. These auxiliary input and output resources are used by the dispatch console user to monitor the state of input buffers and monitor/control the state of control relays. P25 System and Services Agreement (R1422515R1/131) Page 114 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The auxiliary input and output resources are represented by various graphical icons that change their appearance based on the state of the resource. The particular icon that is associated with an input or output is configured by the Elite Admin application. Examples of some of the icons that may be used are shown in the figure below. Auxio2 % Icon for Input Buffer (shown in Active State) Auxio2 D Icon for Control Relay (shown in Active State) quxio2 Icon for Control Relay (shown in Inactive State) Auxiliary 1/0 resource icons Auxiliary input and output resources may be grouped together so that they can be moved or assigned/de-assigned as a group. This is useful for situations where the auxiliary input output resources are being used to interface to comparators or other devices that require multiple control relays or input buffers. Auxiliary output resources may be protected by a "safety switch" to help prevent unintended activation or deactivation. In order to activate or deactivate an auxiliary output that is protected by a safety switch, the dispatch console user must first press the safety switch and then press the auxiliary output. Latched auxiliary input resources may also be protected by a "safety switch" to help prevent unintended clearing of an active input. In order to clear a latched auxiliary input that is protected by a safety switch, the dispatch console user must first press the safety switch and then clear the auxiliary input. Full parallel status for auxiliary inputs and outputs is reflected across all the dispatch consoles that have the auxiliary inputs and output resources assigned on them. That is, if an auxiliary input or output changes state, the change of state is reflected on all the other dispatch consoles that have that auxiliary input or output assigned on them. Auxiliary input and output resources may also be placed on a separate auxiliary input and output window that is capable of being hidden when not needed. A button on one of the tool bars is used to open and hide the window. This allows the dispatch console user too easily and quickly access auxiliary input and output resources that are infrequently used without permanently consuming space on the screen. Patch and Multi -Select Folders The patch and multi -select features are accessed via a set of dedicated folders on the Elite Dispatch GUI. These folders are smaller than the resource folders and may be placed on the screen to suit the P25 System and Services Agreement (R1422515R1/P1) Page 115 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 dispatch console user's preferences. The placement is done in the Elite Admin application. There can be up to sixteen patch folders and three multi -select folders. Patch Folders Clicking on one of the patch folder tabs brings it into view. The patch group is then opened by clicking on the left -most button on the folder. Once the patch group is open, the patch group is editable and members may be added or removed from the patch group by clicking on the desired radio resources. Note that patch groups are active whenever there are members assigned to them. This is true even if the patch group is not open. The members of the patch group are shown on the patch folder along with the status of each member (patched or pending). The resources in the patch also show an indication that they are in a patch group. Some patch groups contain members that were pre -assigned by the Elite Admin application. These patch groups become active as soon as possible after the dispatch console begins using the configuration file that contains the pre -assigned patch groups. The dispatch console user can add/remove members from the pre -assigned patch group, but these additions/removals are lost when the dispatch console either re -loads the configuration file or changes to a different configuration file. A patch transmit button is provided on the patch folder to allow the dispatch console user to easily transmit on all members of the patch group with a single button press. The figure below shows an example of a patch folder containing some radio resources. MseI 3 I Parch 21 Patch 3 Patch 1 1 Msel 9 I Msel2 F1TG_2_000M F1 pc_9_00001 Patch folder Multi -Select Folder Clicking on one of the multi -select folder tabs brings it into view. The multi -select group is then opened by clicking on the left -most button on the folder. Once the multi -select group is open, the multi -select becomes active and members can be added or removed from the group by clicking on the desired radio resources. Closing the multi -select folder (by clicking on the left -most button a second time) deactivates the multi -select group. P25 System and Services Agreement (R1422515R1/P1) Page 116 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Note that this operation is different from that of the patch folders. A dispatch console can only have one multi -select group active at a time, but it can have multiple patch groups simultaneously active. The members of the multi -select group are shown on the multi -select folder. Some multi -select groups contain members that were pre -assigned by the Elite Admin application. The dispatch console user can add/remove members from the pre -assigned multi -select group, but these additions/removals are lost when the dispatch console either re -loads the configuration file or changes to a different configuration file. The figure below shows an example of a multi -select folder containing some radio resources. Patch 1 Patch 2 Patch 3 Msel1 A4sel2 "sel3 I1 Z1CONV_01_00003 Z1CONV 10 00053 Multi -select folder Activity Log Window The activity log window can be used by the dispatch console user as a point of reference for all calls coming into the dispatch console. The activity log shows call information associated with all incoming radio calls such as the name of the radio resource and the time of the call. Incoming calls from all radio resources assigned to the dispatch console are displayed in the activity log. The figure below is an example of an activity log window. Activity Log I� Resource � Tile List of Calls P 9 3 Emera Call 7:52:51 PM TG 2 00049 1 PTT ID 7:50:42 PM Activity log window Up to 1,000 calls can be held in the activity log. The most recent call is on the top of the list and the oldest at the bottom. Once the list is filled, the oldest calls are discarded as new calls come in. The dispatch console user may resize the activity log to show various numbers of calls. For example, when P25 System and Services Agreement (R1422515R1/P1) Page 117 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 there is light activity, the dispatch console user may choose to show only a few calls. During busy hours, the dispatch console user may view more calls by simply dragging the lower right hand corner of the activity log (making it longer) to see additional calls. Dispatch console users may respond to incoming calls simply by clicking on a call in the list. When this is done, the entry appears highlighted and the name of the radio resource appears on the activity log resource tile at the top of the activity log. The dispatch console user can then press the instant transmit button on the activity log resource tile to communicate with that radio resource. The information displayed by the activity log can be customized to suit the dispatch console user's needs. The activity log can be configured to show combinations of Resource Name, Unit ID or Alias, Status Number or Alias, Receiving Site ID, Receiving Zone ID and Time. This configuration is done via the Elite Admin application and, if so configured, via the dispatch console user interface. There are two levels of control over whether or not the activity log is displayed on a dispatch console. The first level is via the Elite Admin application, which controls whether or not a dispatch console has the capability of displaying the activity log. The second level is via the dispatch console user interface where the dispatch console user can choose to view or not view the activity log. Note that if the dispatch console has not been given the capability of displaying the activity log, then the dispatch console user cannot see the activity log at all. The number of lines that are initially displayed by the activity log is configurable via the Elite Admin application or the dispatch console user interface. The number of lines that are displayed may also be changed in real-time by changing the size of the activity log window using standard Microsoft Windows resizing techniques. The user can scroll through all the entries in the activity log even if they cannot all be displayed at once. The information listed in the activity log can be stored in a text file on the dispatch console's hard disk. The size of the text file can be specified to be between 1 MB and 20 MB. When the file fills up, new data overwrites old data beginning with the oldest data. All data associated with a call is logged to the file, regardless of what portion of the data is actually shown in the activity log window. Help The dispatch console is designed to allow the dispatch console user to quickly access information on how to use its features. This help is available right on the dispatch console graphical user interface. There are three types of help available to the dispatch console user: On Line, Micro, and Tool Tips. Online Help Online Help provides detailed information on how to use the dispatch console. The user accesses Online Help via the Help menu on the menu bar. The user can search for topics or keywords to quickly find the desired information or the user can use a table of contents to find the information. The information is displayed in a pop-up window on the dispatch user interface. Online Help allows new dispatch console users to shorten their learning curve and more experienced dispatch console users to quickly remember how to operate seldom -used features. P25 System and Services Agreement (R1422515R1/P1) Page 118 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Micro Help Micro Help provides information about the state of controls or indicators in a resource tile. When the cursor is placed over a control or indicator on a resource tile, a description of the control or indicator's state is given across the bottom of the resource tile. The figure below illustrates Micro Help text on a radio resource. The text across the bottom of the resource describes the icon to which the cursor is pointing. Micro Help Text Micro Help Text The text displayed by the Micro Help feature may be edited via the Elite Admin application. Micro Help allows a dispatch console user to view the status of a control or indicator textually instead of graphically. Tool Tips Help Tool Tips Help provides information about tool bar buttons and menu bar menus to the dispatch console user. When the cursor is placed over a toolbar button, the button's name appears in a small pop-up window next to the cursor and a short explanation of the button appears in the status bar at the bottom of the dispatch user interface window. When the cursor is moved across a menu item in a menu, a description of the menu item appears in the status bar at the bottom of the dispatch user interface window. The text displayed by the Tool Tips feature may be edited via the Elite Admin application. Tool Tips allow a dispatch console user to see a short explanation of the button or menu item of interest quickly. Elite Admin Application The manner in which resources and audio are presented to the dispatch console user on the MCC 7500 dispatch console is managed by the Elite Admin application. The look and feel of the Elite Dispatch GUI, as well as how received audio is routed on the dispatch console, can be optimized to meet customers' needs. The following sections describe how configurations for the Elite Dispatch GUI are managed and what can be configured on the dispatch console via the Elite Admin application. P25 System and Services Agreement (R1422515R1/P1) Page 119 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Managing Dispatch Screens When it first starts running, the Elite Dispatch GUI application reads a configuration file that tells it what should appear on the GUI and how received audio should be routed on the dispatch console. These configuration files are created by properly trained personnel using the Elite Admin application. They are often called "ELT" files because their file names have an ".elt" suffix. Multiple ELT files may be created to address different situations. For example, different ELT files can be created for different shifts in a dispatch center if the scope of dispatching changes significantly between shifts. Alternatively, different configuration files can be created for individual dispatch console users to meet their personal preferences. A dispatch console user may switch between ELT files during normal operations, but cannot access any resources while the original file is being closed and the new file is being opened. The ELT files may be stored locally on the dispatch console computer, on a different dispatch console computer, or in a central location. The choice on where to store the files depends on many factors such as: 1. Accessibility to the files —Do all dispatch console users need to access all the ELT files? If multiple agencies share a dispatch center, do they want to be able to access each other's files? 2. Ease of managing the files —Are the dispatch consoles located in one physical location or are they geographically separated? Is one person managing the files or are multiple people managing them? 3. The topology of the radio system's IP network —Are there servers (such as Domain Controllers) located at the dispatch console location that can be used to store the files? If the files are stored on a server, do the dispatch consoles have to retrieve them across WAN links? By default, when the Elite Dispatch GUI application starts up it asks the dispatch console user to specify which ELT file it should use. If this is not the customer's preferred mode of operation, the dispatch console can be configured so that it automatically opens a particular ELT file. Admin Capabilities The Elite Admin application allows a properly trained user to do the following: 1. Create new configurations. 2. Modify existing configurations. 3. Save configurations. 4. Determine how many toolbars are present. 5. Determine items that should go on the toolbar(s) and where on the toolbar(s) they should go. 6. Determine the number of resource folders. 7. Determine the number of patch/multi-select folders. 8. Name the resource folders and patch/multi-select folders. 9. Determine the location of patch/multi-select folders. P25 System and Services Agreement (R1422515R1/P1) Page 120 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 10. Determine the height of patch/multi-select folders (e.g., taller if there are many members in the groups). 11. Create pre -assigned patch/multi-select/primary groups. 12. Determine if dispatch console users have the ability to assign and de -assign resources. 13. Determine if the activity log is shown initially and where on the screen it is shown (dispatch console users may still hide or show the activity log). 14. Assign/unassign radio and auxiliary input/output resources to various folders. 15. Determine location of radio and auxiliary input/output resources in the folders (dispatch console users may temporarily change the locations by dragging and dropping the resources). 16. Determine where features are placed on each radio resource. 17. Modify the icons used for resource features. 18. Add a safety switch on radio resources. 19. Determine the size of each radio resource (compressed, larger compressed, or expanded). 20. Determine whether selected radio audio stays in a speaker or moves to a headset when headsets are used (this is done on a per -resource, per -console basis). 21. Determine border color for each radio resource. 22. Determine audio routing of resources to speakers. 23. Determine icons used for auxiliary input and outputs. 24. Determine if auxiliary inputs and outputs appear in a separate window. 25. Set initial volume level of each radio resource. 26. Determine if auxiliary outputs are safety switch protected. 27. Determine border color for each auxiliary input and output. 28. Modify Tool Tips and Micro Help text. Auxiliary Inputs and Outputs The MCC 7500 supports the ability to control or monitor Auxiliary inputs and outputs (Aux I/Os) that allow customers to control external devices via relay closures and sense the state of external devices via input buffers from the dispatch console. These Aux I/Os are referred to as Public Aux I/Os. Public Aux I/Os are accessible by more than one dispatch console. A change in state of the Aux 1/0 is reflected across all of the dispatch consoles that have it assigned on their user interfaces. These Aux I/Os are typically physically located in a common location that is shared by all the dispatch consoles. The MCC 7500 dispatch console supports Public Aux I/Os by accessing and controlling RTUs and displaying the status of the RTUs' inputs and outputs on its user interface. A separate window to display the inputs and outputs is not required on the dispatch console. Graphical icons provided by the dispatch console GUI are used to represent both the function and state of relay outputs. For example, an icon consisting of a light bulb may be used to represent a relay output that is controlling lighting of some type. The dispatch console user would click on the button associated with the icon to change the state of the relay output and the icon would change between a lighted bulb and an unlighted bulb to reflect the state of the lighting. Graphical icons are also used to provide a visual indication of both the function and state of external inputs. For example, an icon consisting of a door may be used to represent an external input that is P25 System and Services Agreement (R1422515R1/P1) Page 121 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 connected to a door position sensor. The door can be shown in the open state when the sensor says the door is open and it can be shown in the closed state when the sensor says it is closed. Multiple dispatch consoles may monitor and control the same relay output and/or external inputs. In this case, state changes are indicated across all dispatch consoles simultaneously. Individual relay outputs can be configured so that they require a safety switch to be pressed before they respond to any commands from the dispatch console user. A relay output on one dispatch console can be protected by a safety switch while the same relay output on a different dispatch console is not. The resetting of latched inputs may also be protected by using the safety switch. Supported Aux 1/0 Configurations The following Aux 1/0 configurations are supported: 1. Momentary Input —this is an input where the user interface always shows the true state of the input. If the input is active, it is shown as active. If it is not active, it is shown as not active. 2. Latched Input —this is an input where the user interface does not necessarily show the true state of the input. When the input goes active, the user interface shows the state as active. The display will continue to show the state as active even if the input changes to the inactive state. A dispatch console user must manually reset the display to return it to the inactive state. Note that a dispatch console user cannot clear the display until the input itself is in the inactive state. 3. Momentary Output —this output relay is activated when the dispatch console user presses the button on the user interface and deactivated when the dispatch console user releases the button. 4. Latched Output —this output relay changes state only when the dispatch console user presses the button. The release of the button has no effect on the state of the relay. One press activates the relay; the next press deactivates the relay. 5. Interlocked Latched Output —this latched output relay is part of a group of latched output relays. Only one of the relays in the group may be active at a time. Pressing the button for a relay automatically deactivates the previously active relay. Pressing the same button twice does not deactivate that relay. There is always one and only one relay active in the group at all times. Interlocked relays work in a "break before make" fashion; that is, the previously active relay is deactivated before the new relay is activated. Aux 1/0 Hardware The SDM 3000 RTU is used to support most dispatch console Aux 1/0 needs. The SDM 3000 RTU is rack mountable in a standard 19-inch rack and is one rack unit high. The SDM 3000 RTU is capable of supporting up to 16 outputs and 48 inputs. Expansion chassis can be added to increase the number of inputs and outputs. The output relays are capable of switching 1A @ 24VDC or 1A @ 24VAC. Input buffers are capable of sensing a dry closure through 1000 feet or less (round trip) of 24 AWG wire. P25 System and Services Agreement (R1422515R1/P1) Page 122 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The RTUs can be physically located at console sites or trunking RF sites. The dispatch consoles and RTUs communicate with each other across the radio system's IP transport network. This allows much greater flexibility in putting Aux I/Os where they are needed compared to CENTRACOM Gold Series, which required all the Aux I/Os to be located in the CEB. The RTU provides single pole Form A relay outputs. Double pole, Form B, or Form C relays must be implemented using external relays that are controlled by the RTU relays. 1.11.8.4 Feature Descriptions High-level descriptions for all the features supported by the MCC 7500 dispatch console are given in this section. Centralized System Management The MCC 7500 console system is configured and managed by the trunking system's configuration manager, fault manager, and performance reporting applications. This provides the customer with a single point for configuring and managing the entire radio system, including the console portion. The MCC 7500 console system is able to control certain conventional resources in addition to the trunking system. The trunking system's configuration manager, fault manager, and performance reporting applications also configure and manage the parts of the system interfacing to the conventional resources. End to End Encryption The addition of secure capability to the dispatch console allows true end -to -end encryption in the radio system. This provides the highest degree of security possible to those customers who wish to take advantage of this feature. The dispatch consoles support multiple encryption algorithms and multiple secure keys to allow them to access and control talkgroups from different agencies, if necessary. Gaining Access to Resources in the Communication System Resource Assignment Resource Assignment is a feature that allows a dispatch console user to choose which radio resources are monitored and controlled by the dispatch console. Resources must be assigned before they can be monitored and controlled. Once the assignment is made, the dispatch console starts receiving audio and status updates for the resource. The resource assignment feature works in conjunction with the security group feature of the radio system's network manager. The security group feature determines which radio resources a given dispatch console user has the right to access. Those radio resources are then eligible to be assigned on a dispatch console via the resource assignment feature. Resource Assignment allows the flexibility to change which resources are monitored and controlled at a dispatch console. This can be useful, for example, on shift changes. It does not force one shift to deal with resources that are only used by a different shift. P25 System and Services Agreement (R1422515R1/P1) Page 123 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Resources can be unassigned when they are no longer needed at a dispatch console. Once resources are unassigned, the dispatch console stops receiving audio and status updates for the resource. Aux 1/0 Assignment Aux 1/0 Assignment is a feature that allows a dispatch console user to choose which Aux I/Os are monitored and controlled by the dispatch console. Aux I/Os must be assigned before they can be monitored and controlled. Once an Aux 1/0 assignment is made, the dispatch console starts receiving status updates for the Aux 1/0. Aux 1/0 Assignment allows the flexibility to change which Aux I/Os are assigned at a dispatch console. This can be useful, for example, on shift changes. It does not force one shift to deal with Aux I/Os that are only used by a different shift. Aux I/Os can be unassigned when they are no longer needed at a dispatch console. Once Aux I/Os are unassigned, the dispatch console stops receiving status updates for the Aux 1/0. Resource Status The Resource Status feature informs a dispatch console user of the operational condition of radio resources and Aux I/Os. This gives the dispatch console user greater control by knowing which resources are available and which are not available. Operational failures of the resources and Aux I/Os can be displayed to the dispatch console user so the lack of operational ability is known. Configuration of Audio Presentation for Resources Audio Destination Assignment A dispatch console supports multiple speakers and can be configured so that the audio associated with different resources is routed to different speakers at the dispatch console. Audio Destination Assignment is a console feature that allows a dispatch console user to choose which audio destinations (speakers) are to be used for a given resource. Audio for a resource is generally directed to one of two destinations, depending upon the resource's current select status. Selected resources have their audio sent to the speaker designated as the select audio destination for that resource. When a resource is not selected, its audio is sent to the speaker designated as the unselect audio destination for that resource. In most cases, a single speaker is designated as the select audio destination for all resources monitored by that console. In this case, whichever resource is currently selected has its audio presented in that speaker. On some console installations, it may be desirable to route audio for a resource to a particular destination regardless of that resource's select status. This is accomplished by setting a resource's select audio destination to be the same as its unselect audio destination. Speakers configured in this way are often referred to as "dedicated" or "monitor" speakers. Basic Audio (Talk/Listen) Functions Single -Select The Single -Select feature allows only one radio resource to be selected at a time. When a resource is single -selected, the previously selected resource becomes deselected. P25 System and Services Agreement (R1422515R1/P1) Page 124 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The Single -Select feature is active when there are no Multi -Select groups open. When a Multi -Select group is closed without opening another Multi -Select group, the Single -Select feature becomes active, and the resource that had been selected prior to opening a Multi -Select group is once again selected. Single -Selecting a resource routes the inbound audio on the resource to the designated speaker allowing that audio to be easily distinguishable from the other audio at the dispatch console. It automatically raises the resource's individual volume level to full so inbound audio on that resource can be heard clearly. It also designates that resource as the one to be used by console features such as General Transmit, Monitor, and Page PTT. The main advantage of the Single -Select feature over the Multi -Select feature is that the previously selected resource is deselected when another resource is selected. This saves having to deselect one resource before selecting another. M111tl-SPIPrt The Multi -Select feature allows a dispatch console to define groups of selected radio resources. When a Multi -Select group is opened, all of the resources in the group are simultaneously selected. A dispatch console can support multiple Multi -Select groups, each of which supports multiple, potentially overlapping, resources If a Multi -Select group is opened while another Multi -Select group is open, the first group is closed and all of its resources deselected before the second group is opened. If a Multi -Select group is opened while no other Multi -Select group is open, the Single Selected resource is first deselected. When a Multi -Select group is closed without opening another Multi -Select group, the Single Select feature becomes active and the resource that had been selected prior to opening the Multi -Select group is once again selected. Resources can be added or removed from a Multi -Select group while it is open or while it is closed. Multi -Selecting a group of resources routes the inbound audio on the resources to the resources' select audio destinations, allowing that audio to be easily distinguishable from the other audio at the dispatch console. It automatically raises the resources' individual volume level to full, so inbound audio on the resources can be heard clearly. It also designates those resources as the ones to be used by console features such as General Transmit, Monitor, and Page PTT. The Multi -Select feature has two advantages over the Single Select feature. It allows multiple resources to be selected simultaneously. It also allows groups of resources to be defined and stored so that multiple resources can be conveniently selected and deselected. The resources of Multi -Select groups can also easily be simultaneously transmitted on without having to open the Multi -Select group by using the All Points Bulletin (APB) Transmit feature. Inbound Call Indication The Inbound Call Indication feature is used to indicate audio activity on a radio resource. If the resource is selected on the dispatch console, the indication flashes when inbound audio is detected. If it is not selected on the dispatch console, the indication does not flash. The indication is not affected by the select status of the resource on any other dispatch console. P25 System and Services Agreement (R1422515R1/P1) Page 125 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 It is also used to associate audio being heard from the dispatch console's speakers with a resource. The Inbound Call Indication can have different sources depending on the type of resource on which it appears. For trunked resources, the source is the trunking controller. For some conventional resources, the source can be an input that detects an external dry closure. This is called a Carrier Operated Relay (COR) Input. For some conventional resources, the source is audio activity on the receive path from the station. This is called VOX detection. Individual Resource Volume Control The Individual Resource Volume Control feature allows the dispatch console user to change the level at which each resource is mixed into a speaker. (It is common to have the audio from many resources routed to the same speaker, especially when these resources are unselected.) The Individual Resource Volume Control feature can be used at individual dispatch consoles to lower the volume level of less important resources and raise the volume level of resources as they become important. The initial volume level is set when the resource is assigned. The volume level for a resource is automatically raised to the full volume level when the resource is selected. If the volume level is adjusted while a resource is selected, it remains at the new volume level even after the resource is deselected. If the resource's volume level is not adjusted while the resource is selected, deselecting the resource restores its volume level to its volume level in effect prior to being selected. All Mute The All Mute feature is used to mute all of the audio on resources that are not currently selected at a dispatch console. When the All Mute feature is activated, all audio on resources that are not selected is muted until the All Mute feature is deactivated or a certain amount of time elapses, typically 30 seconds. The amount of time the All Mute feature stays active and the amount of attenuation it applies to the audio are programmable through the radio system's configuration application. If a resource's individual volume setting is such that it is lower than the All Mute feature's attenuated level, the resource's volume setting will not be changed by the All Mute feature. That is, the dispatch console will not increase the resource's volume setting above the level set by the dispatch console user. The All Mute feature is used when the dispatch console user does not want to be disturbed by the audio from the unselect resources. Using the All Mute feature is better than turning down the volume of the Unselect speaker because the volume is restored automatically when the All Mute feature is deactivated. Acoustic Cross Mute The Acoustic Cross Mute feature is used to prevent acoustic feedback from occurring when dispatch consoles are physically located near each other. Dispatch consoles that are monitoring the same radio resource can normally hear each other's outbound audio transmissions. This is called parallel operator audio. If two dispatch consoles are physically close to each other and the parallel operator audio appears in a speaker, the potential exists for a feedback condition between the speaker on the non - transmitting dispatch console and the microphone on the transmitting dispatch console. P25 System and Services Agreement (R1422515R1/P1) Page 126 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The Acoustic Cross Mute feature provides the means to specify groups of dispatch consoles, which mute parallel operator audio on all radio resources that they have in common. High Speed Mute The High Speed Mute feature allows an external device to provide a dry contact closure to the dispatch console subsystem that, when activated, mutes the receive audio of a conventional radio resource at all dispatch consoles monitoring that resource. The audio received remains muted as long as the closure is present, and un-mutes when it is removed. The High Speed Mute feature provides the customer with the means to control what audio appears at the dispatch consoles for a given conventional radio resource. General Transmit General Transmit is a feature that initiates a voice transmission on the currently selected resources. General Transmit is one of the most convenient methods for transmitting since it can be initiated with the footswitch, the headset transmit button, the microphone transmit button, or the General Transmit API functions. General Transmit is a medium -priority transmission. Please refer to the Transmit Priority Levels feature on the following page for more information on transmit priorities. It is important to note that a dispatch console can transfer control of an active General Transmit freely between the General Transmit API functions, the headset transmit button, the microphone transmit button and the footswitch while not losing the transmission. This can be used to free up a dispatch console user's hands for other activities such as writing notes. The General Transmit feature provides easy access to transmitting on the selected resources. Instant Transmit Instant Transmit is a feature that allows a dispatch console user to initiate a transmission on a specific resource regardless of its select state. It is the most direct method of transmitting on a resource. Instant Transmit is a high -priority transmission. Please refer to the Transmit Priority Levels feature below for more information on transmit priorities. It is important to note that the dispatch console user can Instant Transmit even when the dispatch console user is currently performing a General Transmit or APB Transmit. In this case, microphone audio will be sent to both the selected resource(s) and the one upon which is being instantly transmitted. The Instant Transmit feature gives the dispatch console user an additional level of control that is not available with the General Transmit feature. It gives a dispatch console user the ability to transmit quickly on a resource that is not selected. It allows a dispatch console user to monitor the audio from the selected resources in the headset, and simultaneously transmit to another resource. It also allows a dispatch console user to take over a lower -priority transmit from a parallel dispatch console. P25 System and Services Agreement (R1422515R1/P1) Page 127 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Instant Transmit Safety Switch Instant Transmit Safety Switch is a feature that requires a dispatch console user to press a "safety switch" before initiating an instant transmit on a specific resource (regardless of whether it is selected or not). This helps ensure the dispatcher does not accidentally instant transmit on a particular radio channel. All Points Bulletin Transmit APB Transmit is a feature that initiates a voice transmission on the resources of a Multi -Select group. An APB Transmit control on a dispatch console must have one and only one Multi -Select group associated with it. APB Transmit is a high -priority transmission. Please refer to the Transmit Priority Levels feature below for more information on transmit priorities. The APB Transmit feature allows transmission to all resources in its associated Multi -Select group even when the group is closed. The APB Transmit feature provides easy access for transmitting to a pre -selected group of resources. APB Transmit is commonly used to make an announcement to many radio users. It also allows a dispatch console user to take over a lower priority transmit from a parallel dispatch console. Transmit Priority Levels The Transmit Priority Levels feature is a hierarchy of transmit privileges for different types of transmissions on the same dispatch console or between dispatch consoles. It provides an orderly and consistent method for allowing higher priority transmissions to take over resources from lower priority transmissions. The priority levels from highest to lowest are: 6. Primary supervisor console instant transmit or APB transmit. 7. Secondary supervisor console instant transmit or APB transmit. 8. Non -supervisor console instant transmit or APB transmit. 9. General transmit on any type of console (single- or multi -select). 10. Patch transmit on any type of console. 11. Console Transmits While Receiving Audio. The Console Transmits While Receiving Audio feature allows a dispatch console to receive audio from other radio resources while transmitting on a particular radio resource. This allows a dispatch console user to hear audio from other resources while transmitting. Note that this is different from full duplex audio on a single radio resource. Resource Transmit Status —Transmitting The Resource Transmit Status —Transmitting feature is used on a per dispatch console basis to indicate when a dispatch console is transmitting on a resource. A visual indication is provided on the user interface to indicate it is transmitting. P25 System and Services Agreement (R1422515R1/P1) Page 128 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Each dispatch console uses the Resource Transmit Status —Transmitting feature to display its own transmit status. It is not used to display the status of parallel dispatch consoles. Refer to the Resource Transmit Status —Parallel MCC 7500 Op Busy feature for more information about parallel dispatch console status. Resource Transmit Status —Parallel MCC 7500 Op Busy The Resource Transmit Status —Parallel MCC 7500 Op Busy feature is used to indicate when a parallel Motorola Solutions MCC 7500 dispatch console is transmitting on a resource. A visual indication is provided on the non -transmitting dispatch consoles to indicate a parallel dispatch console is transmitting. This feature, in conjunction with the Resource Transmit Status —Parallel Non -MCC 7500 Op Busy feature, provides the means for a dispatch console user to know if a particular resource is available for use. The dispatch console user can see the alias of the parallel MCC 7500 dispatch console that is transmitting on either trunked or conventional resources. Each dispatch console uses the Resource Transmit Status —Parallel MCC 7500 Op Busy feature to display the parallel console transmit status of each resource to which it has been assigned. Resource Transmit Status—Trunking Busy/Callback The Resource Transmit Status—Trunking Busy/Callback feature is used to indicate when a trunking resource is not available for a dispatch console user to use and to alert the user when it becomes available. Audible indications are provided on the dispatch console to indicate a trunking resource is not available and when it becomes available. This feature allows the dispatch console user to know when a trunked resource is available again without having to try to transmit on it continuously. Trunked Base Station/Repeater Control The Repeat Control feature (also known as Repeat Enable) allows a dispatch console user to enable and disable the ability of radio users in a talkgroup to hear the transmissions of other radio users in that talkgroup. When the feature is enabled on a talkgroup, transmit audio from a radio is made available to all of the radios monitoring the talkgroup. If the feature is disabled on a talkgroup, transmit audio from a radio is not made available to other radio users monitoring the talkgroup. In either case, the radio's transmit audio is routed to the dispatch consoles. When repeat control is enabled or disabled, all dispatch consoles with this resource assigned are updated with the current status of the feature. This feature can be controlled from any dispatch console. P25 System and Services Agreement (R1422515R1/P1) Page 129 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 System Access Priority Select (Normal/Tactical) The System Access Priority Select feature allows a dispatch console user to select the relative system access priority of a trunked resource within the resource's communication system. Currently, there are only two possible priorities: NORMAL priority and TACTICAL priority. Call requests from a trunked resource with TACTICAL priority have priority over call requests from a trunked resource with NORMAL priority in obtaining a repeater for communications. Only emergency calls have a higher priority than TACTICAL. When the System Access Priority status of a resource is changed, it is updated at all dispatch consoles in the systems that are monitoring that trunked resource. The System Access Priority Select feature can be used to change the system access priority status of a trunked resource to TACTICAL in order to give the resource a better chance of gaining communication access in a busy system. If, during a repeater busy condition, two call requests are queued with one as NORMAL and the other as TACTICAL priority, then the one with TACTICAL priority gains access to the system when the next repeater becomes available. Voice Call Types on Radio Resources Conventional PTT Call The Conventional PTT Call feature allows a dispatch console user to initiate and receive normal PTT calls on conventional radio resources. A normal PTT call is not directed to any specific individual or talkgroup and does not carry any special importance. It is intended to be heard by all users listening to that radio resource. Trunking Talkgroup Call The Trunking Talkgroup Call feature allows a dispatch console user to initiate and receive talkgroup calls on trunked radio resources. A trunking talkgroup call is a method for communicating with a specific set of users on a trunked radio system. Users only hear the audio associated with talkgroups with which they are currently affiliated. This feature allows a user to speak with a specific group of users without disturbing other users. Trunking Announcement Group Call The Trunking Announcement Group Call feature allows a dispatch console user to initiate and receive announcement group calls on trunked radio resources. A trunking announcement group call is a method for communicating with multiple trunking talkgroups simultaneously. An announcement group is composed of multiple talkgroups that have been grouped together. The association of talkgroups to an announcement group is done by the trunking system's configuration subsystem. This feature allows a user to speak quickly and easily with multiple trunking talkgroups simultaneously. Trunking Emergency Call Trunking Emergency Calls are high -priority voice transmissions initiated by radios or dispatch consoles that allow them to communicate with each other in critical situations. Trunking emergency calls initiated by dispatch consoles reserve a voice channel for the duration of an emergency. P25 System and Services Agreement (R1422515R1/P1) Page 130 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A trunking emergency call is initiated by a radio when the radio transmits while it is in emergency mode. Trunking emergency calls are typically presented at a dispatch console using visual indications. Dispatch consoles are notified when another dispatch console starts a trunking emergency call. In ASTRO 25 trunking systems, priority is given to allocating a voice channel to a trunking emergency call over a regular call regardless of whether the regular call is at either a tactical or normal priority level. Trunking emergency calls can be initiated from a dispatch console on ASTRO 25 IP trunking resources only. When a trunking emergency call is started from a dispatch console, the call is assigned a voice channel for an indefinite period. This guarantees a path for voice communication for the duration of an emergency. The voice channel is released only when a dispatch console ends the call. A dispatch console user can take responsibility for an emergency by recognizing the trunking emergency call. All dispatch consoles are notified that the call has been recognized. Trunking emergency calls initiated by a dispatch console are automatically reported to all dispatch consoles as being "recognized" since a dispatch console user took an explicit action to initiate the trunking emergency call. When an emergency is over, a dispatch console can end the trunking emergency call. All dispatch consoles are notified that the call has been ended. When a dispatch console ends a trunking emergency call, the voice channel allocated for the call is released. Ending the trunking emergency call at the dispatch console has no effect on the state of the radio that initiated the call. Any radio units that initiated trunking emergency calls remain in emergency mode until the radio users explicitly return them to a normal mode of operation. If a radio that is in emergency mode transmits after a dispatch console user has ended the trunked emergency call, the trunked emergency call will be reestablished. The Trunking Emergency Call feature is used by radios and consoles for high priority voice communication. A dispatch console generally initiates a Trunking Emergency Call to guarantee a voice channel for the duration of an emergency. Received Emergency Call Indication The Received Emergency Call Indication feature allows a dispatch console user to be quickly informed that an emergency call has been received on a trunked resource. The indication is a visual indication on the user interface. The visual indication continues until the emergency call has been ended by a dispatch console. The Received Emergency Call Indication feature allows the dispatch console user to quickly identify on which resource an emergency call has occurred. Auto -Open of Quick List The Auto -Open of Quick List feature allows a dispatch console user to quickly access the controls necessary to handle a trunking emergency call. The Quick List contains controls for recognizing an emergency call, initiating an emergency call, and ending an emergency call. P25 System and Services Agreement (R1422515R1/P1) Page 131 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The Auto -Open of Quick List feature automatically opens the quick list when a resource with an unacknowledged emergency on the dispatch console's user interface is expanded by the dispatch console user. The Auto -Open of Quick List feature allows the dispatch console user to begin handling an emergency with a minimum of actions. Emergency End (Knockdown) The Emergency End (Knockdown) feature allows a dispatch console user to terminate an emergency call. After an emergency call has been recognized and the situation has been addressed, the dispatch console user ends the emergency call by using the Emergency End feature. When the dispatch console user does this, the visual emergency indication on the dispatch console's user interface is removed, and the dispatch console informs the trunking controller and all other dispatch consoles that the emergency has been terminated. Parallel dispatch consoles then clear their own emergency status indications for the resource if no other emergencies are active on it. Emergencv Automatic Audio Level Control The Emergency Automatic Audio Level Control feature ensures that the audio associated with an emergency call is not missed due to its volume being too low. When an emergency call is received by a dispatch console, the volume of the received audio associated with the call is raised to its maximum level. When the emergency call is acknowledged by a dispatch console user, the volume is returned to its normal level. The Emergency Automatic Audio Level Control feature allows the dispatch console user to hear the emergency call audio while the emergency call audible alarm is active. Trunking Individual Call The Trunking Individual Call feature allows a dispatch console user to initiate and receive individual calls on trunked radio resources. A trunking individual call is a method for allowing a call to be placed to a specific user on the trunking system. A dedicated individual call resource on the dispatch console user interface allows the dispatch console user to initiate or answer an individual call. All types of individual calls are initiated from the dispatch console in the same way. When an individual call request is received by the target radio, the dispatch console user receives an indication that the target radio is ringing. At this point, the dispatch console is waiting for the radio user to "answer" the ring. Once the individual call is answered, the call is allowed to proceed. A dispatch console user may use an individual call to communicate privately with either a single radio user or a single MCC 7500 dispatch console user. If the target radio or dispatch console is not available when an individual call is attempted, the dispatch console user receives an indication that the call could not be completed. All inbound individual calls are announced to the dispatch console user. A ringing inbound call must be answered explicitly by the dispatch console user. P25 System and Services Agreement (R1422515R1/P1) Page 132 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 At a dispatch console, individual calls can be ended by a request from the dispatch console or by the expiration of an audio activity timer. The audio activity timer expires when there has been no audio activity on an active individual call for an extended period. This time is specified via the configuration application at the network manager. If there is no audio activity on an active individual call for the specified amount of time, the individual call is automatically ended. When an individual call is ended by the radio user or the other dispatch console user, the console individual call resource automatically hangs up. Similarly, when an individual call is ended by the dispatch console user, the radio or other dispatch console automatically hangs up. This is known as the Cancel Service characteristic of individual call. The Trunking Individual Call feature is designed to allow a dispatch console to engage in private conversations with individual radio or dispatch console users. Once an individual call is established on a resource, the resource can be added to a patch group with another type of resource. Semi -Duplex or Full -Duplex Operation Depending on the type of radio unit and the type of trunking system, an individual call can be either semi -duplex or full -duplex. The console subsystem is capable of supporting both types of calls with no configuration changes or dispatch console user intervention required. When a dispatch console user is involved in either type of individual call, the dispatch console user is required to activate a PTT to talk. This is required to prevent unexpected results if a telephone resource is off -hook while an individual call is in process. A telephone resource does not require a PTT because it has hands -free full -duplex operation when the dispatch console user is using a headset. If the individual call also had hands -free full -duplex operation, the dispatch console would not be able to tell to which destination (telephone resource or individual call) the microphone audio should be sent. Therefore, a PTT is required to indicate to the dispatch console that the dispatch console user desires to speak on the individual call instead of the telephone resource. (In this context, the term "telephone resource" refers to two different types of telephone services. It refers to the external telephone that can be connected to a dispatch console so the dispatch console's headset can be used for both radio and telephone communications. It also refers to the console telephony interface, which will be added in a future release). The dispatch console always allows receive audio to be presented to the dispatch console user, but in a semi -duplex call, the radio system does not provide the receive audio while the dispatch console user is transmitting. Advanced Signaling on Trunked Radio Resources Display Radio's Unit ID The Display Radio's Unit ID feature allows a dispatch console to display the unit ID associated with an inbound radio call. Unit IDs are unique numbers assigned to each radio and dispatch console in certain types of radio systems. A radio can send its unit ID when it makes a call. The dispatch console user interface can be configured to display the unit ID of the source radio on inbound calls. This configuration is done at the local administration application. The unit ID can appear in a Received Call Stack, the Three Line Display, the Resource Header, and the Activity Log window. P25 System and Services Agreement (R1422515R1/P1) Page 133 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Note that if an alias for the unit ID is available, the dispatch console will display the alias instead of the unit ID. The unit ID of a parallel dispatch console is also displayed on the dispatch console when the parallel dispatch console transmits on radio resources which are common to both consoles or when the parallel dispatch console places a call to the dispatch console. If an inbound call is received on a radio resource that does not support the concept of unit IDs, no unit ID is displayed on the dispatch console even if it has been configured to display unit IDs. Send Console's Unit ID The Send Console's Unit ID feature allows a dispatch console to send its unit ID when it transmits on a radio resource. Unit IDs are unique numbers assigned to each radio and dispatch console in certain types of radio systems. The unit ID allows the radios to display the ID of the dispatch console that is the source of the transmission. The dispatch console's unit ID is sent when the dispatch console user transmits on a radio resource and when the user initiates an individual call to another dispatch console. ID Conservation The ID Conservation feature prevents dispatch consoles from consuming an inordinate amount of unit IDs in a trunked radio system. The ID Conservation feature allows a dispatch console to use a single unit ID for all the trunking talkgroup resources and individual call resources that it controls. Emergency Alarm An Emergency Alarm is sent by radio users to alert dispatch console users of a critical situation needing immediate attention. When an Emergency Alarm is received by a dispatch console, an audible indication is sounded. A visual indication is also displayed to direct a dispatch console user's attention to the specific resource with the emergency alarm active on the dispatch console. Any dispatch console user can take responsibility for an emergency by Recognizing the Emergency Alarm. All dispatch consoles are notified that the Emergency Alarm has been recognized. The audible emergency indications are typically ended once all Emergency Alarms at a dispatch console are recognized. The audible emergency indications may also be ended by the dispatch console user without recognizing the Emergency Alarm. When an emergency is over, a dispatch console can end the Emergency Alarm. All dispatch consoles are notified that the Emergency Alarm has been ended. The emergency mode persists on the initiating radio unit until it is ended by the radio user explicitly. The Emergency Alarm feature is used by radios to alert dispatch consoles of an emergency without the use of voice communication. This is generally followed by a voice transmission. P25 System and Services Agreement (R1422515R1/P1) Page 134 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Received Emergency Alarm Indications The Received Emergency Alarm Indications feature allows a dispatch console user to be quickly informed that an emergency alarm has been received on a trunked resource. The indications are audible and visual in nature. The audible indication continues until either a dispatch console has recognized the emergency alarm or the dispatch console user mutes it. The visual indication continues until the emergency alarm has been ended by a dispatch console. The Received Emergency Alarm Indications feature allows the dispatch console user to be quickly alerted that an emergency alarm has been received and to identify quickly on which resource it occurred. Emergency Recognize The Emergency Recognize feature allows a dispatch console user to assume responsibility for an emergency call or emergency alarm. When a dispatch console user recognizes an emergency, all other dispatch consoles are notified that the emergency has been recognized. When an emergency has been recognized, the audible indications for that emergency are silenced at all dispatch consoles monitoring the emergency. The Emergency Recognize feature is often confused with the Acknowledge feature. Recognize is used when a dispatch console user takes a specific action to assume responsibility for an emergency. Acknowledge is used when a piece of equipment (trunking controller or dispatch console) automatically sends a message to a radio telling it that its emergency message was received. Mute Tones at Single Op The Mute Tones at Single Op feature allows a dispatch console user to mute the tones associated with an emergency alarm only at his/her dispatch console. This feature does not recognize the emergency alarm, so other dispatch consoles continue to generate the emergency tones. The Mute Tones at Single Op feature is used to silence the emergency alarm tones without recognizing the emergency. This would be used in a situation where one agency is monitoring a channel that belongs to another agency. If an emergency alarm comes in on the second agency's channel, the first agency could mute the tones at their dispatch consoles without having to wait for the second agency to recognize it. Emergency End (Knockdown) The Emergency End feature allows a dispatch console user to terminate an emergency alarm. All dispatch consoles are notified that the emergency alarm has been ended and which dispatch console ended it. P25 System and Services Agreement (R1422515R1/P1) Page 135 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Call Alert The Call Alert feature lets a dispatch console or radio leave a "page" at an unattended radio or dispatch console. Upon returning to the radio or dispatch console, the called user knows who called. Additionally, a Call Alert can be used to trigger an activity. For instance, a Call Alert may cause a vehicle's horn to sound and its lights to flash. Typically, the "page" appears at a radio as a series of beeps along with the unit ID of the sender. Traditionally, at a dispatch console, the received "page" is presented as a series of beeps along with a visual indication of who sent the Call Alert. When a Call Alert is sent to an individual radio or dispatch console, the receiving radio or dispatch console is expected to acknowledge it automatically. A sent Call Alert can be aborted by the initiator before an acknowledgment is received. If after a period an acknowledgment is not received, the Call Alert is automatically terminated and the sender is notified that it was not successful. The Call Alert feature provides the ability for a dispatch console or radio user to contact someone who is away from their radio or dispatch console, and hence cannot hear a voice message. Call Alert eliminates the need to tie up airtime trying to reach an unattended radio. If a dispatch console receives a Call Alert, the identity of the caller can be displayed as a numeric Unit ID, or an alphanumeric alias for the calling radio. Secure Trunked Radio Communication Functionality Secure Capability in the Dispatch Console The Secure Capability in the Dispatch Console feature allows radio voice messages to be encrypted and decrypted in the dispatch console itself. This feature allows the radio voice messages to be encrypted the entire time they are being transported between the dispatch console and the radio. The dispatch console is capable of supporting up to four different encryption algorithms simultaneously. This allows dispatch console users to talk and listen on radio resources that have different encryption algorithms without any manual intervention or delay. Trunked radio resources (talkgroups and private calls) can be configured with the ability to work in the secure mode. Secure -capable resources on a dispatch console may be configured so they always operate in secure mode or so the user can manually change between secure and non -secure modes. The Secure Capability in the Dispatch Console feature allows conversations between a dispatch console user and a radio user to remain encrypted during the entire journey between the two users. Advanced Encryption Standard (AES) Algorithm The AES Algorithm feature allows the dispatch console and archiving interface server to process radio voice messages using the AES encryption algorithm. AES is a United States government encryption/decryption standard defined in Federal Information Processing Standard 197 (FIPS-197). The dispatch console can encrypt and decrypt voice using the AES algorithm. P25 System and Services Agreement (R1422515R1/P1) Page 136 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Secure Transmit Mode Selection The Secure Transmit Mode Selection feature allows the dispatch console user to control the secure mode of transmissions on a trunked resource. The dispatch console user can choose whether his/her transmissions on a particular trunked resource are encrypted. This feature applies to trunked resources individually; that is, different trunked resources on a dispatch console are independently configured to have or not have this feature. This feature can be configured differently for the same trunked resource on different dispatch consoles; that is, a trunked resource may have this feature on one dispatch console but not on another dispatch console. When set to the secure mode, all transmissions on that trunked resource from that dispatch console are encrypted. When set to non -secure mode, no transmissions on that trunked resource from that dispatch console are encrypted. This feature only applies to the dispatch console on which it is located. Radios and other dispatch consoles can have their secure modes set differently. Receive Cross -Mode Indication The Receive Cross -Mode Indication feature is used to indicate when an inbound (to the dispatch console) radio call is in a different secure mode than the dispatch console's setting for outbound (from the dispatch console) transmissions on a trunked resource. This helps prevent dispatch console users from responding to an inbound call in the wrong mode. Clear Audio Alert The Clear Audio Alert feature provides visual and audible indications when a trunked radio call is in the clear mode. The dispatch console can be configured to provide the indications on dispatch console transmissions, on radio transmissions received at the dispatch console or both. This alerts the dispatch console user that a call is unencrypted. Multi -Select Cross -Mode Alert The Multi -Select Cross -Mode Alert feature is used to inform a dispatch console user that there are trunked resources with different secure modes in a multi -select group. This helps prevent dispatch console users from transmitting the same audio in both secure and non -secure modes. This feature does not prevent the dispatch console user from having trunked resources with different secure modes in a multi -select group; it merely informs the user that this is the case. Patch Cross -Mode Alert The Patch Cross -Mode Alert feature is used to inform a dispatch console user that there are trunked resources with different secure modes in a patch group. This helps prevent the transmission of encrypted audio in an unencrypted state in a patch. This feature does not prevent the dispatch console user from having trunked resources with different secure modes in a patch group; it merely informs the user that this is the case. P25 System and Services Agreement (R1422515R1/P1) Page 137 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Fail Indication The Key Fail Indication feature is used to indicate when the dispatch console is unable to decrypt or encrypt a trunked radio voice message due to a problem with an encryption key. This indication is provided on the Elite Dispatch GUI status bar. Reasons for a key failure include a missing key or no keys match the key used to encode the incoming voice message. Panic Key Zeroizing The Panic Key Zeroizing feature allows all the encryption keys in a dispatch console to be erased (zeroized) with the push of a button. The button is recessed in a panel to reduce the chance of accidentally pressing it. Erasing the keys on one dispatch console has no effect on the keys at other dispatch consoles. Keyset/Indexset Selection via GUI The Keyset/Indexset Selection via GUI feature allows the dispatch console user to manually select the Keyset/Indexset used by the dispatch console. This allows the dispatch console user to transmit to radios that are using a different keyset. (The dispatch console will automatically use the appropriate keyset to decrypt audio being received from a radio, so the Keyset/Indexset Selection feature does not really have an effect on received audio.) The control for doing this is incorporated into the dispatch console's GUI so no extra devices [such as a Key Variable Loader (KVL)] are required to change which Keyset/Indexset is being used. This feature does not apply to the archiving interface server since it does not have a GUI and it does not transmit encrypted audio. Key Management via KVL The Key Management via KVL feature provides the ability to manage all the keys for a dispatch console or archiving interface server using only a KVL (key variable loader). Crosspatch Functionality Standard Patch The Standard Patch feature allows a dispatch console user to set up a communication path between two or more resources that are normally unable to communicate with each other. These could be trunked resources and/or conventional resources. When a dispatch console detects call activity on one resource in a patch group, it automatically transmits that audio to all other resources in the patch group. Resources are patched by being included in a console patch group. A dispatch console supports z maximum of 16 patch groups. A resource can be a member of only one patch group in the entire console system at a time. The Standard Patch feature can be used to allow radios within the same or different radio systems to communicate even though they use different resources in that system. For example, it can allow members of different talkgroups in a trunking system to communicate or it can allow conventional P25 System and Services Agreement (R1422515R1/131) Page 138 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 radio users to be able to communicate with other conventional radio user and/or with trunked radio users. Patch Auto -Start The Patch Auto -Start feature allows a dispatch console to automatically start up pre -determined patches after a power cycle or reboot on the dispatch console computer. If a dispatch console experiences an operating system reboot or an interruption in its AC power, this feature causes the dispatch console to automatically start the dispatch application, log into the dispatch console, and start up patches for all the patch groups that have been configured to use the Patch Auto -Start feature. Patch groups that are configured to use this feature need to be pre -configured with the radio resources that are members of the patch group. A dispatch console user may add/delete members to/from the patch group during real-time operation, but if a reboot or power cycle occurs, only the pre -configured members are included when the patch is restored. If a dispatch console user manually logs out of the dispatch application, this feature does not try to automatically restart it. It waits until the operating system is rebooted or the power is cycled off and on. The combination of the Patch Auto -Start and the Patch Auto -Restore After Resource Interruption features provides a highly resilient patch service that may be used for long-term patch applications. Patch Auto -Restore After Resource Interruption The Patch Auto -Restore After Resource Interruption feature allows the dispatch console to provide as much patch functionality as possible during and after service interruptions in the radio system. If a service interruption occurs on a resource that is in a patch group, the dispatch console keeps the patch active with the remaining members of the patch group. The interrupted resource is shown as being in a patch pending state for the duration of the interruption. If the interrupted resource is restored to service while the patch group is still active, the dispatch console attempts to add the resource back into the patch. If a service interruption occurs that affects all the resources in a patch group, the dispatch console keeps the patch active with no members in it. Resources are shown as being in a patch pending state for the duration of the interruption. If resources are restored to service while the patch group is still active, the dispatch console attempts to add the resources back into the patch. The word "attempts" is used in the previous paragraphs because there are conditions outside the control of the dispatch console, which may prevent it from adding a resource to a patch. Examples of these include the resource may not be available for use or another dispatch console placed it in a patch first. The Patch Auto -Restore After Resource Interruption feature allows the dispatch console to provide as much patch functionality as possible after service interruptions without human intervention. This is useful for patches that are desired to be active for long periods. P25 System and Services Agreement (R1422515R1/P1) Page 139 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The combination of the Patch Auto -Restore After Resource Interruption and the Patch Auto -Start features provides a highly resilient patch service that may be used for long-term patch applications. Permanent Patch The Permanent Patch feature has been replaced by a combination of the Standard Patch, the Patch Auto -Start and the Patch Auto -Restore After Resource Interruption features. Please refer to those features for information about what they do. Patch Transmit Patch Transmit is a console feature that allows a dispatch console to initiate a transmission on all resources contained within a patch group. Patch transmit is considered a low priority transmission; its priority is less than that of all other transmit functions. A dispatch console using a higher priority transmission can take control of a resource from another dispatch console using a lower priority transmission. Note that this does not mean the higher priority transmission becomes the audio source for the patch. It only becomes the audio source for the channel(s) upon which it is transmitting. A dispatch console can only patch transmit to one patch group at a time. Note that if a dispatch console user does any type of transmission on a member of a patch group, the dispatch console will automatically transmit on all the other members of the patch group as well. While this operation does not involve the patch transmit feature, it does provide similar results. The patch transmit feature allows a dispatch console user to send a voice transmission to all members of a patch group. This can be a convenient way for a dispatch console user to inform members of a patch group when a patch has been established between resources, or when the patch group is about to be dissolved. Patch Busy Indication The Patch Busy Indication feature provides a dispatch console user with an indication that a resource is a member of an active patch group on any dispatch console in the radio system. This is important because a resource can only be a member of one active patch group at a time. Patch Reserved Indication The Patch Reserved Indication feature provides a dispatch console user with an indication that a resource is a member of an active patch group on his/her dispatch console. This is important because a resource can only be a member of one active patch group at a time. Patch Pending Indication The Patch Pending Indication feature provides a dispatch console user with an indication that a resource the user is trying to place into a patch is not available. Some reasons a resource may not be available include: 1. It is already a member of an active patch group on another dispatch console in the radio system. 2. It may not be affiliated with the trunking system's controller. P25 System and Services Agreement (R1422515R1/P1) Page 140 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3. A hardware failure may be rendering it unavailable. The dispatch console will continue to monitor the status of the resource and will attempt to include it in the patch if it becomes available. Patching Op Indication The Patching Op Indication feature allows the dispatch console user to see which dispatch console patched a resource. This is useful in control rooms with many dispatch consoles and a user wants to quickly find out which dispatch console is controlling a patch. Pausing the cursor on the Patch Busy Indication on a radio resource shows which dispatch console set up the patch group. Communication System Request Rejections Resource Reject The Resource Reject feature informs the dispatch console when a requested operation, such as General Transmit, Instant Transmit, Call Alert, etc., has been rejected by the radio system. This feature provides information regarding the reason the request has been rejected by the radio system for the affected resources. Resource Reject messages differ from error messages in that a reject comes from the radio system whereas an error is generated within the dispatch console. In certain situations, a single request might result in reject messages being received for multiple resources. For example, multiple rejects might be the result of resource regrouping done by a trunked radio system. Resource Rejects are directed to the dispatch console that attempted the rejected operation. Parallel dispatch consoles do not receive the rejects. Resource Rejects provide dispatch console information as to why the radio system is not allowing an attempted action to be performed. In many cases, the reject is because of a temporary condition within the system (e.g., all resources are busy, or the target radio is involved in another operation) which does not necessarily require corrective action. In other situations, a Resource Reject message informs the dispatch console of a system problem, indicating the need for a "system administrator" to correct the problem in the radio system. When an action is rejected, the Resource Reject feature provides a specific reason for why the request was denied. Announcement/Intercom Functionality Selective Op Intercom via Individual Call The Selective Op Intercom via Individual Call feature allows a dispatch console user to speak privately with another dispatch console user through the dispatch consoles. This feature is based on the Trunking Individual Call feature that allows a dispatch console user and a radio user to engage in a private conversation. P25 System and Services Agreement (R1422515R1/P1) Page 141 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The user interface and operation of the Selective Op Intercom via Individual Call feature are the same as for the Trunking Individual Call feature. Please refer to the description text for the Trunking Individual Call feature for more information. The Selective Op Intercom via Individual Call feature allows two dispatch console users to speak privately with each other through their dispatch consoles. It is useful for situations where two dispatch console users need to talk with each other, but are not close enough to talk face to face. Group Op Intercom via Talkgroup Call The Group Op Intercom via Talkgroup Call feature allows a group of dispatch console users to speak with each other through their dispatch consoles. This feature is based on the Trunking Talkgroup Call feature. A talkgroup containing only dispatch consoles as members can be created. Any dispatch console transmitting on this talkgroup would be heard by all the dispatch consoles monitoring that talkgroup. Multiple talkgroups can be created to create different intercom groupings. This does not require any additional hardware beyond what is required for the rest of the trunking system. The user interface and operation of the Group Op Intercom via Talkgroup Call feature are the same as for the Trunking Talkgroup Call feature. Please refer to the description text for that feature for more information. The dispatch console user groupings are created by assigning trunking talkgroup to the desired dispatch consoles. All dispatch consoles that share such a resource may talk with each other. A dispatch console may be part of multiple groups. The Group Op Intercom via Talkgroup Call feature allows a group of dispatch console users to speak with each other through their dispatch consoles. It is useful for situations where a specific group of dispatch console users need to talk with each other, but are not close enough to talk face to face. All Op Intercom via Talkgroup Call The All Op Intercom via Talkgroup Call feature is identical to the Group Op Intercom via Talkgroup Call feature. The only difference is the Trunking Talkgroup Call resource appears on all dispatch consoles. Thus, all dispatch consoles can participate in the discussion. The All Op Intercom via Talkgroup Call feature allows all dispatch console users to speak with each other through their dispatch consoles. It is useful for situations where all dispatch console users need to talk with each other, but are not close enough to talk face to face. System Maintenance and Supervisory Functions Primary/Secondary Supervisor Levels The Primary/Secondary Supervisor Levels feature provides a means for establishing a hierarchy of authority between the users of dispatch consoles. This hierarchy is used by the Transmit Priority Levels feature to determine the priority level of each transmission in a console subsystem. There are three levels of dispatch consoles —primary supervisor, secondary supervisor, and non - supervisor: P25 System and Services Agreement (R1422515R1/131) Page 142 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. A primary supervisor is the highest level and has transmit priority over all secondary supervisors and non -supervisors. 2. A secondary supervisor is the second highest level and has transmit priority over all non - supervisors. 3. A non -supervisor console is the lowest level and has no transmit priority over any other console. The primary and secondary supervisor designations are associated with users, not with physical dispatch consoles. A console subsystem can have multiple dispatch consoles of each level. The Primary/Secondary Supervisor Levels feature allows supervisory personnel to have the transmit priority necessary to carry out their responsibilities in a console subsystem. Multiple Primary Supervisors The Multiple Primary Supervisors feature allows multiple dispatch console users to be designated as primary supervisors in the same radio system. Refer to the description text for the Primary/Secondary Supervisor Levels feature for more information about primary supervisors. This feature is useful when multiple customers are sharing a radio system and each customer wishes to have their own primary supervisor. Console Disable The Console Disable feature allows a dispatch center supervisor to send a disable command from the radio system's network manager to a particular dispatch console. Once the target dispatch console receives the disable command, the dispatch console becomes inoperable. None of the console features or resources can be used, and no call activity can be initiated or received on the disabled dispatch console. In addition, all the current activity on the dispatch console is ended. For example, if there is any kind of transmission active on the dispatch console, the transmission is aborted. If resources are patched by this dispatch console, the resources are removed from the patch group. A dispatch center supervisor can send an enable command from the radio system's network manager to a previously disabled dispatch console in order to make it operable. The Console Disable feature can be used to disable a dispatch console that is not being used in order to prevent unauthorized personnel from misusing it. For example, if a dispatch console is located in a remote site and is not being supervised, the dispatch console can be disabled. Supervisor Takeover The Supervisor Takeover feature allows a supervisor in a dispatch room to control whether or not a non -MCC 7500 dispatch console (e.g., a deskset) can access an analog conventional base station that is controlled by an MCC 7500 dispatch console. A relay is used to physically disconnect the transmit wireline pair from the non -MCC 7500 dispatch console from the station. This feature can be used while the non -MCC 7500 dispatch console is actively transmitting on the channel. This has the effect of immediately de -keying the transmitter. The feature may be configured so the parallel non -MCC 7500 dispatch console is still able to hear any audio being received by the base station from radios. P25 System and Services Agreement (R1422515R1/P1) Page 143 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 This feature allows a supervisor to prevent unauthorized individuals from using parallel non -MCC 7500 dispatch consoles to transmit on conventional stations. Aliasing In a console dispatch environment, it is desirable for users to have the ability to use familiar names in place of various numbers that are used in radio systems. Names can be recognized quickly and are easier to remember than numbers. An alias is an alphanumeric text string that is associated with some element of a console subsystem (e.g., a conventional channel, a talkgroup, a user, a "button" on a user interface, etc.). Typically, aliases are defined by users during the configuration of the console subsystem and do not change very often. Aliases are used in the configuration, operation, and management of the console subsystem. Trunking Talkgroup Resource A Trunking Talkgroup Resource is capable of having a single 16-character alias associated with it. The aliasing system is capable of providing an alias for each Trunking Talkgroup Resource in the radio system. The Alias feature allows dispatch console users to identify Trunking Talkgroup Resources by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Trunking Announcement Group Resource A Trunking Announcement Group Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Trunking Announcement Group Resource in the radio system. The Alias feature allows dispatch console users to identify Trunking Announcement Group Resources by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Trunking Individual Call Resource A Trunking Individual Call Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Trunking Individual Call Resource in the radio system. The Alias feature allows dispatch console users to identify Trunking Individual Call Resources by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Conventional Channel Resource A Conventional Channel Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Conventional Channel Resource in the radio system. P25 System and Services Agreement (R1422515R1/P1) Page 144 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The Alias feature allows dispatch console users to identify Conventional Channel Resources by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Conventional Channel Frequency Selection Control A Conventional Channel Frequency Selection Control is capable of having multiple 16 character aliases associated with it. Each frequency can have a unique alias within the control. The aliasing system is capable of providing an alias for each Conventional Channel Frequency Selection Control in the radio system. The Alias feature allows dispatch console users to identify frequencies by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Conventional Channel PL Selection Control A Conventional Channel PL Selection Control is capable of having multiple 16-character aliases associated with it. Each PL code can have a unique alias within the control. The aliasing system is capable of providing an alias for each Conventional Channel PL Selection Control in the radio system. The Alias feature allows dispatch console users to identify PL codes by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch console. Unit ID A Unit ID is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Unit ID in the radio system. The Alias feature allows dispatch console users to identify Units by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch consoles. Aux 1/0 Resource An Aux 1/0 Resource is capable of having a 16-character alias associated with it. The aliasing system is capable of providing an alias for each Aux 1/0 Resource in the radio system. The Alias feature allows dispatch console users to identify Aux 1/0 Resource by names rather than numbers. This allows dispatch console users to easily and efficiently operate the dispatch consoles. Security Management User Accounts and Passwords Radio system user accounts are used in radio systems to provide access to resources, simplify the use of certain features, and assist in ensuring security. The radio system allows an administrative user to create accounts for the various users of the system and assign different capabilities and access rights to them. One such account is for the users of the console subsystem. P25 System and Services Agreement (R1422515R1/P1) Page 145 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 A dispatch console requires that a valid radio system user account name and password be entered before it can be used on the radio system. The dispatch console validates the user account name and password with the radio system's network manager and allows the user to access only the resources for which the user has access rights. This also applies to third party applications that use the dispatch console's API. Note that these radio system user account names and passwords are in addition to any user account names and passwords required to log into the Windows operating system on the dispatch console PCs. Agency Partitioning The radio system provides users with the ability to create groups of users and assign system resource access rights to those groups. This allows users to control which users have access to which resources in the radio system. This is how agency partitioning is supported in the radio system. Agency partitioning allows radio systems, which are used by multiple agencies, to be configured in such a way that the users from each agency only have access to their agency's resources. This helps keep an agency's resources available for its users, and it prevents unauthorized people from making any changes to the agency's resources. The console subsystem participates in this agency -partitioning scheme. Access to the various parts of the console subsystem is managed by the access rights given to user accounts. A dispatch console checks with the network manager for the access rights assigned to the user and allows access to only the resources for which the user has access rights. This also applies to third party applications that use the dispatch console API. The radio system network manager checks the access rights assigned to the user wishing to configure the console subsystem and allows access to only the portions of the console subsystem for which the user has access rights. Network Securitv Enhancements The radio system's IP transport network is protected against viruses, hackers and other unauthorized activities by a set of enhancements that are applied to each product connected to the network. The dispatch consoles support these enhancements. Fault Management Hardware Element Monitoring The radio system's fault manager monitors and reports the status of all the hardware elements in the console subsystem. This allows the console subsystem to be fault managed from the same point at which the rest of the radio system is fault managed. The specific hardware elements that are monitored are the dispatch console and any networking equipment that supports the console elements. Each of these hardware elements monitors critical internal hardware sub -elements and reports their status. This allows a failure within a hardware element to be detected. The hardware elements in the console subsystem are also periodically polled to request their status. This allows a failure of an entire hardware element to be detected. P25 System and Services Agreement (R1422515R1/P1) Page 146 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Software Process Monitorin The console subsystem monitors and reports the status of all the critical software processes running on the various hardware elements that comprise the subsystem. Changes in the status of software processes on a device are recorded internally. These internal records are primarily intended for use by qualified technical personnel in troubleshooting problems with the console subsystem. Status changes, which are useful for understanding the console subsystem's overall status, are also reported to the radio system's fault manager. If a failure of a software process is detected, self -healing actions may be initiated to correct the failed process. Refer to the Self -Healing Actions feature for more information. Network Link Integrity Monitoring The network elements, which are used by the console subsystem, are monitored in the same manner as the network elements for the rest of the radio system. Any failures in these links are reported to the radio system's fault manager. Automatic Discovery of Console Elements The console subsystem supports the automatic discovery of console elements by the radio system's fault manager. This saves the user from having to manually gather and enter the necessary data into the radio system fault manager. The radio system fault manager automatically discovers all network elements (both Motorola - manufactured elements and Motorola -supported third party elements) that are included in the system and adds them to the map of network elements in a topologically descriptive manner. Outputting of Monitoring Results (SNMP) The console subsystem supports the reporting of fault status to the radio system's network manager via the SNMP protocol. Self -Healing Actions The console subsystem automatically takes certain actions to try to remedy failures detected by its fault management routines. These actions are intended to provide as much functionality to the user as possible. These actions include restarting failed software processes, resetting internal hardware or reloading software into internal hardware. Configuration Management Configuration Application The console subsystem is configured by an application residing on the radio system's network manager. This configuration application is used to configure all console subsystem elements in the radio system. Using the configuration application, the user defines what hardware is present at each element and the capabilities of each element. This configuration application is used in conjunction with the Elite Admin application. P25 System and Services Agreement (R1422515R1/P1) Page 147 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The configuration application is used to define what is potentially available at each console subsystem element. The Elite Admin application is used to define exactly which resources are available to the dispatch console user and how they are presented to the dispatch console user. Automatic Distribution of Configuration Cha When a change is made to the configuration information for the console subsystem, the radio system's network manager automatically distributes the changed information to all the console subsystem elements that require it. As -Configured Documentation The configuration management system generates documentation that allows the user to verify the configuration that was entered and provide information necessary for installation of the console subsystem. The following information is contained in the documentation generated by the configuration management system: 1. Console subsystem information —A listing of which dispatch consoles have been created in the console subsystem. 2. Dispatch console information —A listing of the peripherals, peripheral port assignments, capabilities and audio destination assignments for each dispatch console. 3. Conventional channel gateway information —A listing of the channels, channel capabilities, channel connection information, and main/alternate designation for each conventional channel gateway. 4. Trunked resource information —A listing of the type of and capabilities for each trunked resource controlled by the console subsystem. 5. Conventional resource information —A listing of the type of and capabilities for each conventional resource in the console subsystem. 6. Aux 1/0 information —A listing of the type of capabilities for each auxiliary input or output in the console subsystem. Date and Time Date and Time Synchronization The console subsystem synchronizes its time and date information with the radio system's time source via Network Time Protocol (NTP) on the radio system's IP network. This ensures that the time displays at the dispatch consoles and any time stamps on events in log files are accurate. Adjustments for 12/24 hour format, different time zones, and Daylight Savings Time are automatically made if the operating system on the dispatch consoles and other console subsystem elements is configured to support them. Time Display The dispatch console provides the user with the ability to display the current time on the user interface. The time is synchronized with the radio system's time source. P25 System and Services Agreement (R1422515R1/P1) Page 148 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The time displayed on the user interface is the PC clock time. Adjustments for 12/24 hour format, different time zones, and Daylight Savings Time are automatically made if the operating system on the dispatch consoles is configured to support them. 1.11.9 Conventional Radio Dispatch System Requirements 1.11.9.1 Dispatch System Interface with Conventional Systems The MCC 7500 console was designed with the explicit goal of maintaining all the features of the Gold Elite console, which has been tried and tested over 15 years. This includes a robust interface to conventional channels, supporting 4-wire and 2-wire interfaces with MDC signaling for analog channels, and ACIM/V.24/IP interfaces for digital channels using Consolettes or GTR 8000 conventional radios. Additionally, the interfaces for the system will allow immediate communications without garbled audio due to re -digitizing the incoming voice. This means that digital conventional users will be able to talk clearly with both the County dispatchers and to users on the Broward trunking system. Conventional Base Station Interfaces The MCC 7500 is capable of accessing and controlling the County's analog and digital conventional base stations through the use of conventional channel gateways (CCGW). This capability lowers the County's cost of ownership in two -ways: 1. It uses the same transport network, reducing the requirements for dedicated backhaul. 2. It reduces the hardware requirements for interoperability, lowering fixed network equipment costs. The dispatch console processes audio received from the station, and controls various features on the stations, such as frequency selection, private line selection, and repeater on/off. Using the high density version of the Enhanced GGM 8000-based CCGW, up to 16 conventional channels can be connected to the analog and V.24ports. These 16 channels can be a mixture of analog, MDC 1200, ACIM link, digital, or mixed mode operation. High/Low Density Enhanced Conventional Channel Interface (HD/LD-ECCGW) Today, Conventional channels are much more integrated into ASTRO 25 trunking systems than in previous radio systems. The zone controller manages conventional channels in a manner similar to how it manages trunked talkgroups. The physical interface to the analog conventional stations also changes from previous radio systems. GGM 8000 Gateways are fitted with 4-wire/V.24 interface cards, which are connected to the conventional resources. This connection allows the conventional audio to use the same transport network as the trunked audio. The portion of the router hardware and software that support the conventional stations is called the Enhanced Conventional Channel Gateway (ECCGW). Up to sixteen conventional resources may be connected a High Density ECCGW. Up to eight conventional resources may be connected to the Low Density ECCGW. If the number of stations at a site exceeds the Broward County of the gateway, additional ECCGWs can be added to support those conventional stations. The Conventional Site Controller allows dispatch console users continued access and control to local conventional channels if connectivity to the radio system's controller is lost. This mode of operation is P25 System and Services Agreement (R1422515R1/P1) Page 149 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 often called "fallback operation." The conventional site controller, ECCGWs and dispatch consoles must all be on the same console site LAN to take advantage of fallback operation. ECCGWs located at RF sites or other console sites cannot be accessed by the dispatch consoles located at the console site when in fallback operation mode. Only one conventional site controller is required per console site. This single conventional site controller is capable of supporting the full set of dispatch consoles and ECCGWs that can be placed in a console site. All dispatch consoles and ECCGWs continuously monitor their connections to the radio system's controller. If they detect that the connections have failed, they check their configuration data to see if a conventional site controller is present in their console site. If a conventional site controller does exist, they will automatically switch over to it. During the switchover, the dispatch consoles entering fallback operation will lose any calls in progress on non -local conventional channels and all trunking resources. Calls on local conventional channels will be re-established after the switchover finishes. When a dispatch console is in fallback operation, it will display a visual indication on the dispatch GUI on every non -local conventional channel and every trunked resource indicating the channel or resource is not available for use. The local conventional channels are shown as being fully available for use. An indication is also given in the status bar at the bottom of the dispatch GUI that the dispatch console is in fallback operation. While in fallback operation, the dispatch consoles and ECCGWs continuously check to see if connectivity to the radio system's controller has been restored. When they detect that connectivity has been restored, they will automatically switch out of fallback operation and into normal operation. Conventional Channel Gateway Conventional channels are much more integrated into the trunking systems than in previous radio — console configurations. The zone controller manages conventional channels in a manner similar to how it manages trunked talkgroups. The physical interface to the analog conventional stations also changes from previous radio systems. RF site routers are fitted with 4-wire interface cards, which are connected to the analog stations. Doing this provides two key benefits: 1. It allows the conventional audio to use the same transport network as the trunked audio. 2. It reduces the number of individual interface devices in the radio system. The portion of the router hardware and software that support the conventional stations is called the CCGW. To interface to analog conventional stations, the routers must be able to vocode and de vocode the conventional audio, key the station, detect when the station sends audio to the router and detect when a parallel deskset console transmits on the station. This capability has been added to the routers used in Motorola Solutions' trunking systems. P25 System and Services Agreement (R1422515R1/P1) Page 150 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola Solutions shall provide CCGWs that match the existing configuration for conventional resources and additional ports to support connections for up to 72 conventional resources Physical Interface to Station The MCC 7500 conventional channel gateway provides eight ports (per router) to which analog conventional base stations may be connected. Each port contains the following inputs and outputs. 1. 600 Ohm, balanced analog audio input —Used to accept radio audio from the base station. 2. 600 Ohm, balanced analog audio output —Used to send console transmit audio to the base station. 3. Input buffer —Used to detect Carrier Operated Relay (COR) closure in the base station. 4. 1 Amp, 24 VDC relay output —Used for relay keying of the base station. 5. Each port is manifested as an RJ45 connector on the router. Supported Configurations The MCC 7500 conventional channel gateway supports the following types of analog conventional base stations: 1. R1. 2. T1R1. 3. T1R1 with Paging. 4. T2R2. 5. T4R4. 6. T8R8. 7. T12R12. 8. T14R14. The dispatch console can process audio received from the station and present it to the dispatch console user via speakers or headsets key the station's transmitter and provide it with audio to be transmitted over -the -air (except for R1 stations which don't have a transmitter) control various features on the stations such as frequency selection, PL selection, repeater on/off, etc. 1.11.10 Paging 1.11.10.1 Integrated Paging System The MCC7500 console provides all of the paging formats detailed in the RFP with one exception - POCSAG. POCSAG paging format is primarily used to page Alpha -Numeric digital pagers and is usually associated with a large paging terminal. The MCC7500 console could be used with an external paging encoder that generates the POCSAG and connected to the console's external paging port to a conventional paging base station. P25 System and Services Agreement (R1422515R1/P1) Page 151 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The following analog tone paging formats are supported by the integrated paging encoder. 1. Quick Call I. 2. Quick Call II B—Tone and Voice. 3. Quick Call II C—Tone Only. 4. Quick Call II D—Battery Saver. 5. Quick Call II E—Competitive. 6. DTMF (a.k.a. Touch Code). 7. KNOX (only applies to standard KNOX box tones) 8. Single Tone 0.5. 9. Single Tone 1.5. 10. Motorola 5/6 Tone. 11. Digital Dial 1 (1500 Hz). 12. Digital Dial 2 (2805 Hz). 13. Digital Dial 3 (1500/2805 Hz). As shown in the figure below the following system paging formats are supported by the integrated paging encoder. 1. Trunked Call Alert. 2. MDC 1200 Call Alert. 3. ASTRO 25 Conventional Call Alert. Normal Size Quick Page Buttons 2x Size Quick Page Buttons Figure: Quick Page Buttons 1.11.11 Voice Logger Output Logging recorder outputs shall be provided for each talkgroup used for primary dispatch and select tactical talkgroups, as well as selected receive audio and the operator's transmit audio for each dispatch position. The interface shall support recording the maximum number of proposed P25 System and Services Agreement (R1422515R1/P1) Page 152 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 simultaneous talk paths-11 talk paths for Fort Lauderdale —and audio from up to 72 conventional resources interfaced to the system from conventional gateways. Audio from the 68 console positions spread between the three PSAPs shall be interfaced to each logging recorder locally through a punch block. The outputs from the console equipment shall be capable of being connected to the agency's current VPI recording equipment, and shall terminate to a wall -mounted punch block. The County requires a logging recorder link that will support a direct connection without requiring a conventional interface. Provider must include any required Application Program Interface (API) associated with completing the connection. Provider shall identify within its proposal all VPI requirements necessary to complete the interface. The logging recorder interface must include sufficient redundancy to permit continued recording in the event of a failure to any one component. Motorola shall be responsible for all cabling associated with the logging recorder integration. The redundancy shall include parallel recording at Central Dispatch and North Dispatch. 1.11.11.1 Dispatch System Interface with Logging Recorder The Archiving Interface Server (AIS) provides an interface between the dispatch consoles and the logging recorder system. This allows calls on the radio system to be recorded together with information associated with the calls. The AIS is comprised of a personal computer and Voice Processing Module (VPM). There is a one-to-one relationship between an AIS and IP logging recorder, such that each IP logging recorder in a system requires its own AIS. The design includes the required number of AISs located at the Broward County Sunrise, Coconut Creek and Pembroke Pines dispatch equipment rooms. There are two AIS/VPM interfaces at Sunrise and Coconut Creek and a single AIS/VPM at Pembroke Pines. Since there is a co -located master site at both Sunrise and Coconut Creek, both AIS/VPMs will be connected directly to the master site LANs and interfaced to VPI via the master site Firewall and border router. The AIS/VPM at Pembroke will interface to VPI using a control center firewall. Motorola Solutions has worked with VPI and identified all of their requirements that will provide the necessary hardware and software costs for the interface to the VPI logging recorder. Motorola Solutions shall provide the turnkey integration of the proposed radio system with the County's existing VPI logging recorder, including all associated hardware, software, cabling, application programming interfaces (API), and all associated services. The integration shall permit the recording of all system talkgroup audio and console position audio from all three dispatch centers. Broward County Console AIS Each AIS is designed to accommodate 120 simultaneous clear conversations and 256 resources. Encrypted conversations or those on conventional resources will impact the number of simultaneous conversations that can be recorded. P25 System and Services Agreement (R1422515R1/P1) Page 153 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Date and Time Synchronization The console sub -system synchronizes its time and date information with the radio system's time source via Network Time Protocol (NTP) on the radio system's IP network. This ensures that the time displays at the dispatch positions and any time stamps on events in log files are accurate. Adjustments for 12/24 hour format, different time zones and Daylight Savings Time are automatically made if the operating system on the dispatch positions and other console sub -system elements is configured to support them. 1.11.11.2 Operator Position Equipment The MCC 7500 console equipment connects directly to the trunking system's IP transport network. It uses IP packet protocols for passing call control data and call audio through the system. Proposed Equipment Description The MCC 7500 dispatch console is based on a Motorola -certified personal computer tailored with Motorola -provided hardware and software. The recommended Motorola Solutions hardware includes the following equipment at each of the operator positions: 1. One Motorola -certified personal computer, including keyboard, mouse, and 22-inch LCD monitor. 2. One voice processor module (VPM). 3. Two desktop speakers. 4. Two headset jacks. 5. One gooseneck microphone. 6. One dual pedal footswitch. The hardware elements that comprise the dispatch console are described in the following paragraphs. Voice Processor Module The VPM is designed so it can be mounted in furniture, placed on top of a writing surface, or mounted in an EIA 19-inch rack. It is also capable of supporting monitors weighing up to 80 pounds (36 kg) standing on top of it. The VPM has connectors for the following devices: 1. One desktop microphone. 2. Two headset jacks. 3. Eight desktop speakers (four speakers max supported in the initial releases). 4. One local logging recorder. 5. One radio instant recall recorder. One telephone instant recall recorder (not supported in initial releases). One external telephone set. One external paging encoder (for analog resources only). 9. One footswitch. 10. One generic transmit audio input. P25 System and Services Agreement (R1422515R1/P1) Page 154 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Front view VPM_honl DSP_ENET2-1 rTilEi Pont Headset i - Headset 2� KVL Porter I I I Ground Key Erase Button J J L PQ_ENET1 TifE1 Port 1 VPM rears Rear view VPM views The connections for the above items use RJ45 connectors except for the headset jack connectors, which are D1315. The audio inputs and outputs are 600 Ohm, balanced and transformer coupled, except for the microphone, which is 2000 Ohm, balanced, and does not use a transformer. They accept or provide audio levels appropriate for the devices being connected. Some of the connectors listed above may be used to provide audio inputs and outputs for connecting other types of dispatch consoles to the Motorola Solutions radio system in conjunction with the MCC 7500 dispatch API. The VPM uses an external power supply (similar to the power supplies used with laptop computers) which must be connected to an AC power source. The VPM connects to the console site LAN switch and communicates with the dispatch console PC via Ethernet. While there is no direct physical connection between the VPM and the PC, there is a one-to- one relationship between the VPM and the PC. Each dispatch position has its own PC and its own VPM. The VPM provides all the audio processing services and encryption/decryption services for the VPM- based dispatch console. These include: 1. Vocoding Services —It is capable of supporting AMBE and IMBE (for ASTRO 25), and G.728 (for analog resources) vocoder algorithms. 2. Audio Processing Services —It is capable of supporting audio level adjustments, summing, and filtering. It is capable of supporting multiple simultaneous streams of audio. 3. Encryption and Decryption Services (Optional) —It is capable of supporting multiple simultaneous encryption/decryption sessions using multiple algorithms and multiple secure keys. The PC uses a Microsoft Windows operating system. Motorola -provided software provides call processing services and an enhanced version of the Gold EliteT' GUI. The VPM-based dispatch console provides a suite of available APIs that may be used by third parties to interface CAD systems, non -Motorola dispatch consoles, or other devices with the Motorola Solutions radio system. P25 System and Services Agreement (R1422515R1/P1) Page 155 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Personal Computer The dispatch console uses a tailored Motorola -certified HP Z400 mid -tier workstation running Windows operating system. The PCs used in ASTRO 25 systems have a mini tower form factor. The PCs are configured at Motorola Solutions so that the hardware and application software are installed and tested and are operating properly. Desk Microphone The dispatch console is capable of supporting a single desk microphone. The desk microphone contains a microphone cartridge on a flexible shaft and two buttons in its base. One button controls the General Transmit feature and the other controls the Monitor feature. The desk microphone may be fastened or left free so the dispatch console user can pick it up during its use. The 18-inch long flexible neck allows the base to be placed behind a keyboard or writing area and still be able to position the microphone cartridge within a few inches of the user's mouth. If a desk microphone is connected to a dispatch console while no headsets are connected, the desk microphone is active whenever any transmit function is active. If a desk microphone is connected to a dispatch console while one or two headsets are connected, then the desk microphone is only active during a transmit function if its transmit button is pressed. This prevents the desk microphone from picking up unwanted background sound while the dispatch console user is using a headset to transmit. Headset Jack A dispatch console is capable of supporting up to two headset jacks. A headset jack allows a dispatch console user to use a headset while operating the dispatch console. The headset jack supports headsets which use either PJ7 (6-wire) or PJ327 (4-wire) long frame connectors (6-wire headsets have a PTT button while 4-wire headsets do not have a PTT button). The headset jack contains two volume controls; one for adjusting the level of received radio audio and one for adjusting the level of received telephone audio. A small dimple is molded into the headset jack housing near the telephone volume control so the dispatch console user can tell them apart without having to look at them. If an external telephone set connected to a dispatch console's telephone/headset port is taken off hook while a headset is connected to a dispatch console, the selected radio audio is removed from the headset earpiece and routed to the appropriate speaker(s). The received telephone audio is routed to the earpiece of both headset jacks. Both microphones of the headsets go live and their audio is routed to the external telephone set. This allows the dispatch console users to talk and listen on the telephone set in a hands -free full duplex mode. Proposed dispatch system can support only following wired headsets: 1. SupraPlus monaural (single -ear headband style). 2. SupraPlus monaural (single -ear headband style) with noise -canceling microphone. 3. SupraPlus binaural (dual -ear headband style). P25 System and Services Agreement (R1422515R1/P1) Page 156 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4. SupraPlus binaural (dual -ear headband style) with noise -canceling microphone. Desktop Speakers Proposed dispatch console is capable of supporting multiple speakers through which audio is presented to a dispatch console user. Each speaker on a dispatch console contains unique audio; that is, an audio source cannot appear in multiple speakers at a single dispatch console. The speaker is a self-contained unit which may be placed on a desktop, mounted in a rack/furniture, mounted on a wall, or mounted on a computer monitor. It contains an amplifier which provides two watts of power maximum. Power for the speaker is obtained from the VPM via its interconnect cable. A mounting bracket is included with the speaker. The speaker is designed for use near computer monitors. The speaker provides the user with a continuous volume control knob. This serves as a master volume control for all the audio which appears in the speaker. When the user adjusts this volume control, all the audio in the speaker is increased or decreased by the same amount. Audio for a resource is generally directed to one of two destinations, depending upon the resource's current select status. Selected resources have their audio sent to the speaker designated as the select audio destination for that resource. When a resource is not selected its audio is sent to the speaker designated as the unselect audio destination for that resource. In most cases a single speaker is designated as the select audio destination for all resources monitored by that console. In this case, whichever resource is currently selected has its audio presented in that speaker. The Individual Resource Volume Control feature allows the dispatch console user to change the level at which each resource is mixed into a speaker. (It is common to have the audio from many resources routed to the same speaker, especially when these resources are unselected.) The Individual Resource Volume Control feature can be used at individual dispatch consoles to lower the volume level of less important resources and raise the volume level of resources as they become important. In the console system, Individual volume controls are also available for each resource as shown in the figure below. P25 System and Services Agreement (R1422515R1/P1) Page 157 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Ta ' [ 6:55:55 PM Tool Bars Resource F° l 1 'm"x l F.140,3 1 AfaN 31 PuscA R I PsrM 3IVA + I + Radio Resources _ Patch & I& CAM —_� Radio Resource + 1 � nr� bWg r�rc s mom � `x+� 9 �aa, l� s Multi -Select Folders P � Auxiliary Inputs/Outputs L L± Radio Radio Resource + Resources ri s,ia�u • 1 7 y Activity Log _.._...._ ........ Window Status Bare • : r The system can support up to eight speakers per dispatch console Footswitch Motorola Solutions' dispatch console is capable of supporting a single footswitch with two pedals. If a footswitch with one pedal is used, the pedal controls the General Transmit feature. If a footswitch with two pedals is used, one pedal controls the General Transmit feature and the other controls the Monitor feature. The footswitch allows a dispatch console user to access the General Transmit feature or Monitor feature without using his/her hands. This is useful in situations where the dispatch console user's hands are not free for activating those features. The footswitch may be permanently fastened to the floor if desired. Telephone/Headset Port The Telephone/Headset Port allows an external telephone set to be connected to the dispatch console. The dispatch console's headset can then be used to communicate on both the radio system and the telephone set. The port provides the following inputs and outputs: 1. A balanced 600-ohm analog audio output containing the headset's microphone audio. 2. A balanced 600-ohm analog audio input for the external telephone's received audio. 3. An input buffer for the Off Hook signal from the external telephone. 4. An input buffer for an Auxiliary Jack Sense signal from the external telephone. When the dispatch console senses a dry closure on the Off Hook input buffer, it removes the selected radio audio from the headset earpiece and puts it back in the appropriate speaker(s). It then routes any audio appearing at the Telephone/Headset Port's audio input to the headset earpiece. It also routes headset microphone audio to the Telephone/Headset Port's audio output. This allows the dispatch console user to communicate hands -free on the telephone set. P25 System and Services Agreement (R1422515R1/131) Page 158 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 When the dispatch console senses a dry closure on the Auxiliary Jack Sense input buffer, it ignores any closures on the Off Hook input buffer. This causes the headset to work with the radio system instead of the external telephone system. This allows the dispatch console headset to be used for radio operations when another person is staffing the telephone set. If the dispatch console user transmits on any radio resources while the Off Hook signal is active, the headset microphone is re-routed to the radio system for the duration of the transmission. When the transmission is ended, the headset microphone is routed back to the Telephone Headset Port's audio output. The headset earpiece audio routing is not changed during the transmission, so the dispatch console user can still hear the telephone's received audio. The Telephone/Headset Port allows a dispatch console user to use a single headset to communicate on both the radio system and a telephone system (e.g., a 911 system). 1.11.11.3 Common Electronics Equipment The common backroom electronics for the MCC7500 is basically a single rack of network equipment that includes Site Routers and LAN switches. When conventional interfaces are required, there will also be Conventional Channel Gateways (CCGW) and a Conventional Site Controller which is only used to provide control of the CCGWs if the console site cannot communicate with the trunking zone. This design saves a significant amount of rack space as compared to the circuit switched Gold Elite consoles that require several racks of equipment for the same functionality. P25 System and Services Agreement (R1422515R1/P1) Page 159 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.12 Network Management System (NMS) This section provides specifications and requirements for an integrated monitoring -and -control system for local and remote site facilities and equipment. The system is used to provide remote indication of status, alarms, and analog values, and to provide remote -control relay operations. A. System Alarms: The system shall acquire, process and display information in an integrated and uniform fashion for a variety of critical systems including: 1. Trunked and conventional radio systems 2. Local and remote site facilities 3. Primary and backup power systems 4. Microwave, leased line and data networks B. Site Alarms: Any change in the state of site equipment shall induce an alarmed state. Equipment monitored shall include, but not be limited to, the following: 1. Surge arrestors 2. Transfer switch (normal or bypass state) 3. Power fail 4. HVAC 5. Smoke detector 6. Intrusion detection 7. High temperature 8. Low temperature 9. High humidity 10. UPS/DC power fail 11. UPS/DC power state (normal or bypass) 12. DC battery charger (low voltage) 13. DC battery charger (high voltage) 14. DC battery charger (no charge) 15. Dehydrator (high pressure) 16. Dehydrator (low pressure) 17. Tower light failure 18. Generator (including generator run, low fuel, high temperature, fail, etc.) 19. Generator not in automatic mode 20. In an effort to reduce false alarms, all alarm contacts normally shall be closed when no alarm is present. C. NMS components include: P25 System and Services Agreement (R1422515R1/P1) Page 160 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. Network management terminals (NMTs) 2. Remote terminal units (RTUs) System Management Overview System management for the ASTRO 25 system provides core network management of the radio enterprise network (REN) infrastructure, complemented by unified cloud management of the County and County's user radios, encryption keys, media content, batteries, and firefighter safety equipment. 1.12.1 Network Management Terminals (NMTS) A. NMTs shall provide primary processing, display and control of information to and from a variety of RTU locations. System status and alarm conditions shall be displayed. The system shall provide the ability to remotely access the system to check the operational status of the system and to view alarms. B. NMTs shall be installed at three locations to be determined. It should be assumed that these locations may not be located at positions with access to the radio backhaul network, and may therefore require virtual private network (VPN) access. C. NMTs shall be configured to allow concurrent access to each of the three locations. D. NMTs shall meet the following general requirements: 1. Expandable software and hardware architecture shall be easily updated by adding software modules and hardware boards. 2. Hardware and software platform shall be PC -based using current versions of hardware and software, and utilize the Microsoft Windows 7® operating system or other as approved by the Contract Administrator. 3. Both graphic and tabular displays shall provide instantaneous and comprehensive network status information. 4. NMTs shall provide full archiving and control functions. 5. Multiple alarm protocols for higher -level network management systems shall be mediated by the NMTs. 6. NMTs shall be designed to monitor a large cross section of equipment so that they can consolidate multiple alarm systems, rather than just poll alarms from RTU locations. P25 System and Services Agreement (R1422515R1/P1) Page 161 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 7. NMTs must perform full management functions with a local terminal. 8. NMTs shall provide email notification of alarms. 9. NMTs shall provide alarm filtration and consolidation. 10. Web -browser interface shall be provided for common management functions. 11. Secure Web -browser interface shall be provided to monitor alarms and perform control and management functions via Intranet or Internet. 12. Local printer for report printing at each NMT location. 13. Security profiles to allow restricted NMT access to specific user profiles. 14. Ability to automatically generate emails for system alarm notifications. 15. Ability to interface Unit ID and alias information with the County's Motorola PremierOne CAD system. 16. Ability to interface the NMS system via standardized data interfaces to third -party systems (CAD, other NMS, etc.) E. NMTs/RTUs Communications Protocol(s) supported: 1. Vendors shall fully describe all protocols used or supported. 2. Vendors shall identify which of the following protocols are supported, either standard or as an OPTION: a. American Standard Code for Information Interchange (ASCII) b. Simple Network Management Protocol (SNMP) 3. Proprietary protocols may be acceptable, as long as all requirements are met. F. Standard Features: Vendor's solution shall include the following features: P25 System and Services Agreement (R1422515R1/P1) Page 162 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. Providershall provide programmable display screens including the following: a. System Summary — High-level screen summary window with links to other screens b. Change of State — Summary of points that have changed state from alarm to normal or normal to alarm c. Standing Alarms — Summary of all points in alarm condition d. Programmable Alarm Windows — Allowing logical grouping of alarms, such as by type or site 2. Shall provide for the graphic depiction of the network allowing annunciation and point selection via icons: a. Nested -tree depiction of the network with drill -down capability b. Capability to drive external display devices 3. Programmable console environment, including: a. Database definition b. Screen colors c. Alarm summary formats d. Blink attributes e. Pager alarm formats f. Audible alert formats 4. Status Points — The following status types shall be supported: a. Simple status —Contact open or closed b. Change detect — Simple status plus change detect since last scan 5. Control Points — The following relay control types shall be supported: a. Direct control b. Select before operate c. Batch — Control multiple relays with a single operation 6. Analog points —Display the value of a monitored quantity such as temperature, fuel level, VSWR, etc. 7. Time stamp indicating date and time of message within 0.5 seconds P25 System and Services Agreement (R1422515R1/P1) Page 163 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 8. Conditional assignable text messages (minimum 256 characters) for each point to be issued on a change of state or alarm 9. Alarm qualification — On a point basis, programmable delay before alarm is issued 10. Alarm deactivation — On a point basis, the ability for the operator to deactivate an alarm to inhibit additional annunciation 11. Alarm history: a. Logging of all alarms to disk and printer (selectable) b. Minimum history log of 500,000 entries 12. Email support —Text message of alarm sent to email lists 13. Ping interrogator — To confirm that servers, routers and IP-based equipment are physically present on the network 14. Editor — Providing point configuration utilities to create and edit point databases 15. Security — Multiple levels of user name and password protection to all for flexible system management 16. Reports — Provider shall define the reports that are available. Provider shall describe how trend analysis is supported and how current system status is reported. System shall be able to provide comprehensive planning and analysis, and shall have a flexible user interface. 1.12.1.1 Network Management System The Network Management System (NMS) is a set of software applications or tools used to manage the ASTRO 25 wide area trunked radio system and its constituent components. The NMS supports the following services: 5. Network Monitoring —Applications are included for monitoring the status of the transport network and the individual infrastructure components; displaying status information; forwarding alert information; and performing diagnostic procedures. 6. Configuration Management —Facilities are provided for entering and maintaining the operational parameters of the infrastructure components and user devices (i.e., the mobile and portable radios). P25 System and Services Agreement (R1422515R1/P1) Page 164 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 7. Accounting Management—NMS supports the tracking of radio usage of the system by providing an optional interface to third party accounting and/or billing applications. 8. Performance Management —Standard and optional applications are available for monitoring, reporting, controlling, and optimizing the use of system resources. 9. Security Management—NMS includes features for setting user privileges and controlling their access to view and/or modify information contained in the configuration databases. The NMS subsystem includes the following virtual, zone -level servers within the zone core of the ASTRO 25 system and is available from either the EOC dispatch center or other dispatch centers via remote desktop when authorized by the System Manager. 10. ZDS. 11. UEM. 12. UCS and UNC. 1.12.1.2 Zone Database Server The ZDS handles a variety of tasks; including hosting the zone configuration database, administering applications licenses, authenticating network manager users accessing the system, and performing back -end support for user applications. The ZDS performs the following database server functions: 13. Maintains the infrastructure (zone configuration) database for the zone. 14. Exports the infrastructure information from its database to the zone controller where it is stored as the local infrastructure database. 15. Maintains a replica of the current UCS database and home zone map. 16. Exports the radio information it receives from the UCS to the zone controller. The ZDS also performs all network management and fault management polling of system devices to support the network management clients. The fault management information that the ZDS collects is passed on to the UEM server. The ZDS handles a variety of administrative tasks, including the following: 17. Administering the standard and optional applications licenses. 18. Authenticating network manager users accessing the system. 19. Performing back -end support services for user applications. 20. Handling telephone interconnect (optional) record processing. 1.12.1.3 User Configuration Server The UCS provides database storage and back -end processes required for most system -wide functions. The UCS makes it possible for management personnel to configure home zone maps, users, radios, talkgroups, critical sites, Adjacent Control Channels (ACC), security information at a system -level, and other system -level parameters. Group and Unit ID home zone assignments are also made at the UCS level. This information is configured using the PM application and is saved in the UCS database. P25 System and Services Agreement (R1422515R1/P1) Page 165 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.12.1.4 Unified Event Manager UEM Enhanced Navigation uses the latest geo-map navigation to provide a high-level system view, with the ability to drill down to get device -specific status. With the use of the SDM 3000, this feature supports device metering, environmental inputs, and digital controls, through a single interface. UEM Enhanced Navigation can also configure role -based access for different UEM users. This feature is ideal for organizations utilizing the ASTRO 25 UEM for fault management functions. Organizations that used the MOSCAD GMC, in combination with UEM in previous ASTRO 25 versions, will now be able to track all device and environmental information from a single -user interface. The organization and accessibility of this data allows for a more intuitive end -user experience. ALL THE INFORMATIONYOU UEM Enhanced Navigation Tools: • Integrated Fault Management allows a single - user interface to view, organize, and manage fault data. • Interactive Maps provide a system -wide view, zone view, and site view. • A detailed user -interface provides context - based navigation, name aliasing, acknowledgment of alarms, digital commands and control, analog input readings, and device metering. • Environmental Alarms monitor environmental inputs and provide a high-level view of the site, including digital input status, analog T•Digital inputs input status or valve, and digital output V0Digital EnvironmentalInput control status. • Real-time Metering allows users to view readings remotely, assess signal strength and power, and diagnose issues remotely. userDefinedNanne U • Command and Control features allow users to enable or disable channels, view multiple channels at once, and set role -based or permissions -based access. P25 System and Services Agreement (R1422515R1/P1) Exhibit A-1 (Radio System) Page 166 of 204 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Network Element Vee<Repeater Site: Site 22 Site 22 -Network Element View General Information Managed Resource. Sne22 E04 Subsystem: 10.104.22.0 Repeater site Edn Source; I0.1C422.0:Rpir Sile Type, Repeater Site Class Name: LogiealManaWResouree Managed. Yes More Information - Commands and Meseriag Information CHANNEL SITE ChannelI Disable Enable Channel2 Disable Enable Site Channel3 Disable Enable Channel4 Disable Enable Channel5 Dlaable Enable Note Objects Site Failsoft Sate CN Site Drinking Wide Trunking III The UEM provides a central location for managing all radio, transport, and environmental devices on the system. The Enhanced UEM introduces support for microwave devices, device metering, environmental inputs and digital controls. There are also new site and network element overview screens with interactive maps and drill down navigation. The UEM application (offered on M and L Cores) includes new functionality. IP connectivity to sites is required. Pa ]�ou pan.-wm. upemni� rs.lDll GE 302� r� �Pam] MD Palle-DMX] Pam. ! Pan . Pan, _ uEla].�mm,,,oas»ao� New functionality (standard): 1. Interactive Map View. 2. Zone level (M & L Core only). 3. Ability to Acknowledge Alarms. 4. Display Name Aliasing. P25 System and Services Agreement (R1422515R1/P1) Page 167 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5. Saved Settings for Reports. The new UEM system, zone, site and network element views provide high level status at a variety of levels. Improved navigation allows a user to drill down from high level status alarms to the finest detail. Context based menus also allow users to jump straight to the details from any screen. View of Collocated Sites - view relative locations of Zone Core, RF Sites and Console Sites to better understand impact of fault alarms. Site Icons - identify site types and alarm status from a single screen. Microwave status view (OPTIONAL) — view status of all microwave radios in a zone from one screen. Link visualization — see what radios are connected to each other to better understand impact of fault events. " Microwave Map 77:7 C + Path 1 - Harris_7R5000 Lin n�m i.n M1fnmi� �1 Path 1 - HorrisrConsteltr�' RAC30v3 Slot 1 on NUe`7:'10.4.233.33 Path 1i�r,IN M1 � •r "" Path 1 - RAC6x_IRU600 Slot 6 on INUe 1 : 10.4.203!33� 1 r.,....,, r,..El9 _ Palh3-MDR7000 Path 1-M Path 1 -RAC40 Slott on INUe 1 :10.4.233.33 wK� Path 2 a HPDBRG7R6000 -'Path 1 RDI3600 ,g Path 5-MDR4000 Path 1 - MDR6000 053 Path 2 - RAC3x Slot 1 on INUe 2 114 233� 3 Path 1- RAC60'IRU6004lolv4&IN...0 1 10.423533 1 Severity. Clear uui�cw AGmawledge All Alarms Path 2-RAC4x Slot"2"on INUe2:104233i33 v Assoc sled Alarms Path 2-MNI-- s..�.,,wMs-eied ,.. . P u.•P. i:, F L:. Events -efv Network Hemenl Path 1 - RAC6x1000Siat 5 on INUe 1 : 10.4.233.33 - Rename , .... i - v... P�.ete oblea and Traces - Path 2 - MDR6000_D 51 'r Ed:. Urdnates Path 1 - IDU_300_20xV2r� r_M.... Path e n, Path4-INU� Path 3 - MDR6000 Path 3 - IDU_GE_20x 10 J � Path 6 DMX30 3 Path 4-Harris_MegaStar�,® `tle x Iu� - nvieu yr..i. , ra.aarae 2171 kni 10 0 mi Path 1 - RAC60-ODU Slot 3 on INUe 1 : 10.4.233.33 Lai: 41.3479 Ln9. -37.1935 The application automatically discovers devices on the network to determine their real-time status. Color -coded symbols displayed on a topography map provide a geographical and hierarchical representation of the entire network. The UEM allows each user to filter out and customize the P25 System and Services Agreement (R1422515R1/P1) Page 168 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 pertinent information important to their roles and responsibilities. Features and benefits of the UEM are outlined in the table below. Benefits of the UEM Feature Centralized View of Entire ll=� Benefit Network Managers can view the entire ASTRO 25 Communications Network system status and quickly isolate problems to the board level. Intuitive Graphical User Network Managers can be quickly notified of failures on Interface (GUI) the system and diagnose device problems, utilizing a display and an intuitive GUI. Components are automatically discovered and map Auto Discovery of Devices views are created to show the overall health of the network. Persistent single view all failure conditions in the Active Alarms View and Alarm network and a quick reference summary of alarms by Summary severity allows users to quickly pinpoint the highest priority failures. Secure Device Access SNMPv3 protocol with Triple DES and AES 256 bit (optional) encryption to prevent security breach attempts. Real time event stream using a standard industry Northbound Interface protocol that can be used to forward events to a (optional) higher -level management application for added flexibility. User specified event notifications sent via email —which Email Notifications can also be forwarded to a portable mobile device — allows System Managers to simultaneously address other tasks. The UEM gives the Network Manager virtually instantaneous notification of any system deficiency or element failure. 1.12.1.5 UEM Event Browser All events (or a filtered subset of events) that are received by UEM is viewable via the UEM event browser. By default, when viewing an event, the event browser displays Severity, Date/Time, Managed Resource, Entity, and Message (see figure below). Additional display properties are available. Up to 10,000 of the most recent events from any managed device within a zone can be displayed. P25 System and Services Agreement (R1422515R1/P1) Page 169 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Network Events Total 10B5 Displaying F1006 tg F 1066 Page Length 50 I Info I Minor I Vajor Dec 01 200714!59:49 ... 1001 DeuiceChange_newl Synchronization Dec 01 200714: 59:49 10101 11 92 Synchronization Dec 01 ,200714:59:49 ... 10.101.11.0 loll 01.11-0 Dec 01,200714:59:49 ... 10.101.11.92 'Synchronization Dec 01 ,2007 14:59:49 ... 1001 DeviceChange_newt Synchronization Dec 01 ,200714:59:49 ... 10.101 .11 .92 Agent Redundancy Dec 01 200714: 59:49 10101 11 92 P—er Supply Dec 01,200714:59:49 ... 10.101.11.92 'Switchl Dec 01 ,200714:59:48 ... 10.101 .11.92 GPS Dec 01,200714:59:49 ... 10.101.11.92 Fan Dec 01 ,2007 14:59:4� ... 10.101 .11 .92 .SitQ Controller Dec 01 200714: 59:48 1010111 0 10 101 11 0 Dec 01 ,200714.59.4$... 1001 DeviceChange_newl Channe12 Dec 01,200714:59:40 ... 1001DevideChnnge_newt Channel1 Dec 01 ,200714:59:4$. 1001DsviceChange_now1 Site Dec 01 ,2007 14:59:48 ... 1001 DeviceChange_new1 'Synchronization Dec 01 200714:59:48 ... 10.101 .11 .92 Synchronization Dec 01 200714: 59:34 10101 11 0 10 101 11 0 Dec 01 ,200714:59:34 ... 10.101.11.94 Synchronization Dec 01,200714:59:34 ... 10.101.11.94 'Synchronization Dec 01,200714:5%34 ... 10.101 .11 .94 Repeiver Dec 01,200714:59:34 ... 10.101.11.94 Power Supply Dec 01 200714: 59:34 10101 11 0 10,101 110 Dec 01,200714:59:34 ... 10.101.11.94 Power Amplifier Dec 01 ,200714:59:34 ... 10.101.11.94 Exciter Message Fault manager has synchronized fault information with 1 Fault manager has synchronized fault information with I At least one node in this subnet is in failed state. Fault Manager received Synchronization Complete notifi Fault information for this device may be out of date.Rea Following Attribute Values have changed. nmaRedAgnt ENABLED, NO REASON ENABLED, NO REASON MINOR MALFUNCTION, HARDWARE FAILURE MAJOR MALFUNCTION, HARDWARE FAILURE ENABLED, NO REASON At least one node in this subnet is in failed state. MALFUNCTION, BAND PLAN MISMATCH MALFUNCTION, BAND PLAN MISMATCH SITE TRUNKING, RECOVERY Fault information for this device may be out of date.Rea Fault information for this device may be out of date.Rea At least one node in this subnet Is In failed state. Fault manager has synchronized fault information with I Fault Manager received Synchronization Complete notifi CRITICAL FAILED, RxLo1 Lock or RxLo2 Lock ENABLED, NO REASON At least one node in this subnet Is In failed state. ENABLED, NO REASON CRITICAL FAILED, TX LOCK _ -- — -_ - - -__- _.. _- - _.�- h UEM Event Browser sample screen P25 System and Services Agreement (R1422515R1/P1) Page 170 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.12.1.6 UEM Alarm Browser The UEM alarm browser (see figure below) allows the user to view all alarms, or a filtered subset of alarms. By default, when viewing an alarm, the alarm browser displays Severity, Date/Time, Managed Resource, Entity, Message, and Owner/Assignee information. Additional display properties are available. UEM supports exporting events and alarms for future analysis. 14+ Alarms Minor Miner Minor Major Inor ARqor Total 19 Displaying F 1 to F 19 Page Length 25 Dec 01 200714:59:49... 1001 DeviceChange_ne... Synchronization Dec 01 200714:59:49... 10.101 .11 .92 Synchronization Dec Al 200714:59:49._ 1010111 0 10101.11 q Dec 01 200714:59ALL 10.101 .11 .92 CPS Dec 31200714:59:49... 10.101.11.92 Fan Dec 01 200714:59:48... 1001 DeviceChange_ne... Channe12 Dec 01 200714:59:48... 1001 DeviceChange_ne... Channel1 .Dec 011�00714-.%,413_ 1 EON ZavicKharge_W_ Ste Dec 01 200714:59:34... 10101 11 94 Synchronization Dec 01 200714:69:34... 10.101.11.94 Receiver Dec 31200714:59:34... 10.101.11.94 Exciter Dec 01 200714.59.34... 10.101 .11 .94 Station Control Board Dec 91200714:59:07... 10.101.11.93 Synchronization Dec 01 200714:59:OT... 10.101 .11 .93 Receiver Dec II1 2007 14.59:OT... 10.101 .11 .93 Station Control Board Dec 01 200714:59:OT... 10.101.11.93 Base Radio Dec II1200714:59A0... 10.101.11.91 Synchronization Dec 01 200714.58:59... 10.101 .11 .91 GPS Dec 01 200714:50:59... 10101 11 91 Fan Fault manager has synchronized fault information with this ... Fault manager has synchronized fault Information with this ... At least one node In this suhnet is in failed state, MINOR MALFUNCTION, HARDWARE FAILURE MAJOR MALFUNCTION, HARDWARE FAILURE MALFUNCTION, BAND PLAN MISMATCH MALFUNCTION, BAND PLAN MISMATCH ATE TRUNKING, RECOVERY Fault manager has synchronized fault information with this CRITICAL FAILED, RxLo1 Lock or RxLo2 Lock CRITICAL FAILED, TX LOCK CRITICAL FAILED, SOB EXTERNAL REFERENCE Fault manager has synchronized fault information with this ... RXINHIBIT, User Requested MINOR FAILED, SCB EXTERNAL REFERENCE SERVICE, USER REQUESTED Fault manager has synchronized fault information with this ... MINOR MALFUNCTION, HARDWARE FAILURE MAJOR MALFUNCTION, HARDWARE FAILURE J UEM Alarm Browser sample screen 1.12.1.7 Network Management Terminals and Licenses The NMS Windows -based client/server architecture distributes most of the user application processing to the client PC workstations. The following applications run on or may be accessed from the Network Management terminal: 1. PM. 2. RCM. 3. ZoneWatch. 4. Zone Historical Reports. 5. UEM. 6. UNC. 1.12.1.8 Provisioning Manager The PM provides data entry screens for the mobile and portable radio units authorized to use the system. The PM is also used to set security information at a system level. The user interface is web- P25 System and Services Agreement (R1422515R1/P1) Page 171 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 based and has intuitive browser -based user navigation features. Configuration reports can be generated. A sample PM screen is shown below. The subscriber profiles feature allows the replication of parameters that are common to multiple radio units, thereby reducing the time and effort to load the user configuration database. Working in concert with the UCS, radio unit data is entered once only for each unit and automatically distributed to the user configuration database residing in the ZDS at its resident zone and all other zones in a multi -zone system. Batch Sppri+�r MpflcnilprLy upan�P Monpgen No Caro rw r�a.o T»Ikpp+up C vantwnal Yogic MGEG Applirn Cwnman Kaf lMn Sample PM screen 1.12.1.9 Radio Control Manager The RCM application provides two types of functions: radio commands can be initiated (e.g., Dynamic Regrouping and Selective Inhibit) and radio events are displayed (e.g., Status and Emergency Alarm). A sample RCM screen is shown in figure below. The RCM has the following features: 1. Dynamic Regrouping —Dynamic Regrouping allows a dispatcher or system manager to dynamically program an affiliated radio user to a particular talkgroup. The dynamic regrouping function is implemented within one second per regrouped radio. A companion function "Cancel Regroup" cancels the regrouping command and removes the radio from the regrouped talkgroup. When a radio is regrouped, the subscriber will acknowledge (ACK) the command, and the ACK is sent to the initiating terminal. The subscriber will generate an audible noise indicating to the user that the radio has been regrouped. P25 System and Services Agreement (R1422515R1/P1) Page 172 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Storm Plans —Storm Plans provide the system with a consistent procedure for special or emergency situations. A completed Storm Plan can have a maximum of four commands, each containing a maximum of 100 individual radio tasks. 3. Selective Inhibit/Cancel Inhibit —Selective Radio Inhibit enables a user to functionally disable a subscriber unit that is currently affiliated to the system. This feature can be used to disable stolen radios or invalid users. If the initial inhibit command fails within 30 seconds, a notice is sent to the initiating terminal to select either "endless search" or "quit". The companion feature "Cancel Inhibit" reactivates the radio in the same FIARVIUMM 4. Other features include: — GUI for ease of use. — Status function. — Online Help. �T.ryetf6 Retllo Y] � Ra.Mlae � 9Rn Tum Entl Nne � Prmeehar � Cunmenm � Reason ��J������� Erryma E _ d aw W ��_.I D—d J �x rws.mlo lP RNA Mm ,A9 T Aw, RAe r_— WM� PM.—Je RYk! ' xELat+Po� fhaWAtleA P�SMeIJ E[Irusmv s she {{ ryaieo F '.Naas TIP TOPS erletl h P� AGM W�wv msrmr A+�nxRoos n.�er g�mx->" � ,E E�9� sn� RCM screen example 1.12.1.10 ZoneWatch Grid and Control A ZoneWatch Grid and Control sample screen is shown in figure below. ZoneWatch Grid and Control is a performance management tool with customizable displays and graphs to monitor real-time communications activity in a zone. The information displayed can help system managers be proactive in making better resource planning decisions, such as when additional channels need to be added to busier sites. ZoneWatch Grid Screen —Air traffic within a single zone is displayed on a Site/Channel grid. Real-time call activity for each channel is displayed in its respective cell. ZoneWatch Control Display —This display presents call activity messages. These can be used to isolate errors, trace the progress of a call and troubleshoot or analyze current system activity. It also provides information about activity occurring on the control channel, such as rejects, emergency alarms, and unit affiliations. P25 System and Services Agreement (R1422515R1/P1) Page 173 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 �,M,.,,, m�,mlomo,ms3w[omm�wm,.e� 53w:ame,mrrRRRrrwm�]RwwwRwwwRwwwwRwww„ L� Idas u.l I.l4lYdai, u,++•- o..W.le. ,e.....-u.m.msrls.o�ua- Ilollsxu[omalp.Y-[,xal,ullx ,o....- c.....11..[..d, a +n,.+n.,:a mamlergo+m�[�low.meeoew.sel�l as[amm wrrrrrrwrtrrw>'lrcrrrrwrcnrrwrrnrrnrrrcrrnrrrrn]�wl 1, la[m Is[ I lysdaya,.w.- ,. ...eb,[a:q,m..9.ie- I [o[ Isgw[oconl6dt[Jsal,ellx,o....- c..A,e.Ne..fem,�.,�1 T �M� olma n Irz[m xs.[s�¢]sweannpa. �n..msn�.w.a:-nawo.aev[se.t�n...>�o.¢=[[ossaam[oco�[p..�xv[lecs[[o[s,a.a"..-<aws.ay.w.nmw.[ T [Ilr[mull[.ladurv[�a.l.-o..w.l..l.,..[I....-n..plwers�.on.�rvr.ilo119xwucose,lsJe[I%611o11¢+_0.w �a...l..ep..l.. is [sn, n..M�-ox o[sa mo[moJm Rldq mmm mm mmmm mmrTmR I�h mmee pfm m drs mmmmmmm mme� moe,i{m eedmryo, mm 1, la[mi3lioy:nnwle®uyay.u.. ssu. npu . �M+.m eaa mwmam RTlmo] o,vroe iswa'd w [0,e mol u d n sl o3 oral vu,o[ oso[c, II Isar I,Is s+lsnwP A,+,.n, w.el- ttslr0[.u.:s.es-eeY e...�ds,[..,tu s�d. �.m �¢.psN a a®'mI aT�4es.! 1 [ ].Yes-eew..L.=Yxa.m- I mwmmmwmaxeartunmmesasoa[d csmmvom mmuommmmoe xswww,mmm mm of mw mpewissm RwOsel et Drop Isop m d05 e1� [bol mm w mmmwmnomwmmmmol m[u Segel .lA lfd 101dabd he[ AI S[ mQ,ol It[re.1 LIIo.l;wn...u,vse,w_sese,m.vµ...e�.. xx e.w„ue:r�,lec suw [men¢.re�4ea..u..[,aT_au.yl[l:[m+..�+a+.ta=esa.m - �M.+'osm,emo.;+lommamsa5, sx5sne[,s uaemm ad�iw sev„mnmsomnmscs ss e,«.e,e<p es os o,m[swo� tsm tom mm L[ Ir.�, I,[csJsn� s.n.n,he•A-'yM.+w••.sax- im, e.,rN.:o mm wwmw mmmo[ [am oemmm ]owmwe] mmmmmmm ZoneWatch control display example 1.12.1.11 Zone Historical Reports Zone Historical Reports are provided. This application produces reports on radio infrastructure and radio resource usage across a single zone. A predefined set of reports, with field selection capability, is supplied to produce "standard" or tailored reports. Historical reports are generated automatically or on demand. Automatic reports are produced at a specific scheduled time and date or on a recurring time and date interval. Reports can be sent to the monitor screen, a printer, Hyper Text Markup Language (HTML), or CSV files. This display provides real-time line charts or 3D bar graphs that illustrate channel utilization for all call types —group, private, control channel, and dynamically blocked calls. 1.12.2 Remote Terminal Units (RTUS) A. RTUS shall be provided in sufficient quantities to monitor the entire network, including: 1. Trunked and conventional radio network components 2. Site facilities including shelter, tower, lighting, power and generator 3. Microwave radios, channel banks, etc. 4. Simulcast paging transmitters 5. Data network equipment, including routers, switches, etc. 6. Other miscellaneous equipment B. RTUs shall be fully compatible with NMTs supplied and provide complementary functionality wherever necessary to provide a complete working system. P25 System and Services Agreement (R1422515R1/P1) Page 174 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. RTUs shall support the following points: 1. Status/alarms — 48 minimum, expandable to 256 2. Control outputs — 8 minimum, expandable to 32 3. Analog inputs — 8 minimum, expandable to 16 D. RTUs shall support time stamp and system time synchronization. E. Terminations for all points shall be provided on suitable terminal blocks providing ease of installation, testing and maintenance. 1.12.2.1 Environmental Alarms Interfaces for the environmental alarms at the radio sites are provided by SDM 3000 Remote Terminal Units (RTU). The SDM 3000 RTU acts as the primary interface to the site devices. The SDM 3000 RTU acts as an intelligent site management terminal that allows for continuous monitoring of critical site components and alarms. The NFM SDM 3000 RTU routes alarms information to the Network Management System and to the Motorola Solutions System Support Center via the IP-interface at each remote site, located on the ASTRO 25 LAN. The system includes an SDM 3000 RTU for each RF and Dispatch site in the system and any site that has microwave. This will allow for monitoring of the required alarms at each location that includes serial alarms from microwave radios at each site and TRAK frequency standards. Each of the SDM 3000 RTUs is provided with digital alarm inputs, and relay outputs for control of external devices. These inputs and outputs may be used by the County to interface to site alarm devices such as power, intrusion, lights, and other site alarms. P25 System and Services Agreement (R1422515R1/P1) Page 175 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.12.2.2 Inputs and Outputs Included on Each SDM 3000 RTU Motorola to provide RTU interface to provide alarms for all equipment included in or interfacing with the System, including retrofitting existing equipment if no RTU interface is already present. Existing sites will be brought up to same level of alarming system as new sites provided under this Agreement, as part of the scope of services being provided by Motorola. Provider shall ensure that the recommended alarms identified in Schedule 5 for each shelter will be monitored and interfaced as part of the System, unless otherwise approved by Contract Administrator. Forty-eight Digital Inputs (DI) providing 48 dry -contact inputs; any of the inputs may be used as low - speed counters under application control. The module provides an isolated current so that the open/closed state of the sensor may be determined. Each of the inputs is opto-isolated from the remaining circuitry on the module to provide maximum input surge immunity. Sixteen Digital Outputs (DO) providing 16 low -current relay outputs; 12 of the relays have Form A contacts and four relays have Form C contacts. Magnetically latched relays should be used in systems that require long operation from the backup battery when the mains power fails; electrically energized relays should be used when it is mandatory that the relays open following loss of power or when the module is removed from the SDM 3000 RTU. Each relay has an internal feedback contact that the application may use to verify that the relay is open or closed. All connections to the relays are made via plug-in screw terminals on the module, and all relays have surge arresting devices installed. Eight Analog Inputs (AI), are provided in various options supporting either 8 4-20 ma inputs, 8 ±1 ma inputs, 8 ±2 ma inputs, 8 ±1 VDC inputs, 8 ±2.5 VDC inputs, or 8 ±5 VDC inputs. Each of the eight inputs, plus ground and temperature, are opto-switched into a precision A-to-D converter; ground is measured so short-term drift may be cancelled and temperature is measured so that the temperature drift associated with all silicon -based chips may be negated. The F4544 SDM3000 RTU for ASTRO sites supports up to six expansion units. The SDM3000 1/0 Expansion Advanced unit includes the following inputs and outputs: 1. 48 WET or DRY Alarm Inputs. 2. 16 Electrically Energized Control Outputs. 3. 8 Analog Inputs (-5V to +5V DC). 1.12.2.3 Example of Local Discrete Alarms The table below shows a general listing of the site equipment alarms (as applicable at each site), which will be monitored at the sites. Site Alarms Site Environmental Alarms Tower Lighting Site Environmental Alarms Fire Suppression System Trouble Fault Building Intrusion Air Conditioner A Failure Building Low Temperature Air Conditioner B Failure Building High Temperature Commercial Power Failure P25 System and Services Agreement (R1422515R1/P1) Page 176 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 In Site •Environmental Building Smoke/Fire Alarms Transfer Switch Position Fire Suppression System Discharge TVSS Failure Generator Alarms Generator Alarms Generator Running Generator Control Switch Not Set Generator Low Fuel Generator Low Oil Pressure Pre -Alarm Generator Over Crank Generator Low Coolant Temperature Pre -Alarm Generator Other Failure Generator High Coolant Temperature Pre -Alarm Generator Battery Charger Alarm Generator Low Oil Pressure Alarm Generator High Coolant Temperature Alarm Generator Low Coolant Temperature Alarm UPS Power System Alarms UPS or DC Power System Alarms UPS Online Rectifier/Battery Charger Low Voltage Microwave System Alarms Microwave System Alarms Transmitter A Transmitter B Receiver A Receiver B Rectifier/Battery DC Voltage Rectifier/Battery Charger Low Voltage Rectifier/Battery Charger No Charge Rectifier/Battery Charger High Voltage Transmission Line High Pressure Transmission Line Lower Pressure 1.12.3 FNE Equipment Specification Sheets Motorola Solutions has provided FNE equipment specification sheets as Evaluation Criteria Attachments Section 2.8. P25 System and Services Agreement (R1422515R1/P1) Page 177 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.13 System Implementation, Test and Acceptance 1.13.1 Cutover Plan A. The Provider shall be responsible for planning and coordinating the implementation of all equipment, subsystems and the overall system. B. Execution of the cutover plan shall ensure that new systems are brought online with minimum interruption to all existing systems and communications. C. During final design, Provider shall deliver a preliminary cutover plan describing how the radio system will be phased into a fully operational system. 1. Provider shall successfully complete all tests and training prior to the actual cutover of systems. 2. Provider shall provide the necessary labor to cutover from existing systems to the Systems. 3. The plan shall include the schedule and procedures associated with the transition of each operational user group. The plan shall specifically address how the existing users will begin using the new system with minimal operational impact. 4. The plan shall provide detailed component or subsystem cutover plans, and specifically shall delineate between systems that affect and do not affect ongoing operations. 5. The plan shall include contingencies. 6. The County reserves the right to approve and change the cutover plan as it relates to any or all system components. Motorola is fully responsible for the turnkey execution of the cutover plan, including any additional equipment and services required to facilitate the cutover plan. These responsibilities include but are not limited to: 1. Calculation of power and heat loading for existing equipment 2. Relocation of existing equipment 3. Reinforcement of floors to support weight of added equipment, including DC power plant 4. Upgrades to site electrical systems to support old and new systems concurrently with consideration factored in for the cutover from AC to DC power P25 System and Services Agreement (R1422515R1/P1) Page 178 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5. Upgrades to site HVAC systems to support old and new systems concurrently 6. Placement of a temporary shelter if space cannot be secured within an existing shelter, and all associated services to relocate equipment between the shelters until a final system configuration is achieved and the temporary shelter is decommissioned. 7. Upgrades of site grounding systems to the latest revision of R56 8. Seamless migration and cutover of the microwave network 9. Initially install equipment operating in the AC mode and cutover operation to DC at a later point The only cost associated with the cutover for which Motorola will not be directly responsible are associated with enhancements to the tower structure if the structural analysis determines the tower cannot safely support the proposed load. 1.13.1.1 High -Level Cutover Plan The initial cut over plan provides a basic outline of recommended procedures to provide Broward County the most efficient system migration minimizing operational impact. The current Gold Elite consoles can be changed out while still operational on the Hosted Master Site. This plan has four critical parts. The steps beyond step 1 (indicated below) require the new radio shelters and towers to be completed. Existing towers that will be reused will need structurals completed with all of the new antennas and be ready to accept new antennas. The following tentative cutover plan will be refined by the Parties during design review, subject to final County approval. The Motorola Gold Elite Consoles at the three dispatch centers would be the first infrastructure that would be changed to the new MCC7500. The new consoles can be staged and shipped with a software release that is compatible with the HMS 7.14 release. This will allow the consoles to be installed while still on the HMS. Since the dispatch screens are nearly the same as the Gold Elite screens, the training requirements will be minimal. Once the VPI IP logging additions are completed by Replay, the consoles can be changed at the Pembroke Pines location one position at a time. Both Gold Elite and the MCC7500 consoles can operate simultaneously thus the acceptance testing can be performed on the first position with minimal disruption to the dispatch center. When all 21 positions have been completed and the operation has been determined to be stable, the existing Gold Elite CEB racks can be removed. This is an important step since the space occupied by the CEB racks will allow the MCC7500 rack to be permanently installed and provide a rack space for the microwave rack and the Master Core equipment racks at Sunrise and Coconut Creek. This procedure will then be repeated at the other two dispatch centers. Upon completion, Broward County will be dispatching on the MCC7500 consoles still operating on the HMS until the new system is ready for cut over. 2. The next step is installation of the new microwave transport once all of the new tower sites have been completed. The new microwave will operate on different frequency bands than the current microwave. Most paths will be 6 GHz but will be use the lower 6 GHz band designated 6L. This may vary depending on the path coordination and available 6 GHz frequencies and will only be known once P25 System and Services Agreement (R1422515R1/P1) Page 179 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 the physical path surveys are completed and frequencies are assigned by coordinators. Some of the shorter paths will be 11 GHz. Once the final antenna heights have been determined from the physical surveys, coordination is completed and frequencies assigned, Motorola can then determine the optimal method to transition equipment while ensuring the continuity of user operations. There are two main ways to cut in a new replacement microwave transport that will be explored: A. Install the new microwave in parallel with the existing microwave. This is the ideal method if it can be done but is dependent on things such as tower structural loading, new antenna locations and frequencies assigned. With this method, the complete microwave system can be installed, and acceptance tests completed. The existing 16 DS1s can then be transferred over using the existing Larus Route Switches. Once the route switching has been tested and verified to be working properly, the existing microwave can be removed. This is another important step as it provides additional space for the new microwave that may have been temporarily located until the old equipment can be removed and will free up one more rack. The new microwave only requires one rack per site therefore, in most cases, this will free up one to two rack spaces. The exception to this is where the existing microwave comes from the County PSB prime site. These existing radios will need to remain in place at Core, Playa and Point of America to connect the existing 16 DS1s to the existing sites. B. Another method that may be considered and will be most appropriate due to tower loading is an "Underbuild." With this method, the new 6 GHz antenna and waveguide is installed and the new and old system shares the new waveguide and antenna where there are new and old parallel paths. The advantage is that the old waveguide and antenna can be removed at the same time keeping the tower loading minimized. Once the remainders of the new paths are complete and the new microwave testing is complete, the DS1s can be transferred to the new microwave and the old parallel paths removed. With the current new microwave path design, the following paths could use this procedure depending on the new frequency assigned: i. Core to Markham Park. ii. Davie to Miramar. iii. Miramar to Channel 2. C. The third step is phasing in the RF sites. The new sites and sites with new shelters will have no issues installing the new DC power systems and the three RF racks. The seven existing sites have no space. The DC power system requires 4 to 6 rack spaces depending on if it is a prime site and backup system site. The -48VDC battery plants must be placed in permanent locations due to the weight. Prior to installing any battery plant, the building floor must be evaluated for maximum Ibs per sq foot. In most cases, a floor plate will be required to distribute the weight to meet the maximum specifications for the particular building. In addition, the battery plants have to be built on site and all battery modules inter connections put in place. Once completed, it is not movable without disassembly. The following will need to be known prior to providing a more detailed cut over plan: — What existing equipment racks will be coming out or can be relocated to a temporary location. P25 System and Services Agreement (R1422515R1/P1) Page 180 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 — There are four sites that will be main system remote simulcast only sites. These are Playa, Point of America, Miramar and Markham Park. — There are three sites that will have the main system, backup system and the 800 MHz MA system. These are Coconut Creek and Davie. Channel 2 is the third is getting a new shelter so will not be an issue with space. — The Core site is a prime site for the main system and the 800 MA system in addition to a main system co -located remote simulcast site, backup system remote simulcast site and 800 MA system co -located remote simulcast site. — There are three new RF racks that contain all of the equipment for the 19 channel system. At minimum, the network rack and one radio rack would need to be temporarily located between existing racks to bring the site on line with 10 channels. — At these six sites, there are some possibilities that can be done to use minimum space to get at least 10 channels on line initially by powering the GTR8000 Base Repeaters using AC from the existing UPS since these stations can do both AC or DC. Most G-series equipment that includes simulcast controllers, and voting comparators can operate AC or DC. The site DC power charger -rectifier can also run from 120 vac from the site UPS to power network equipment such as routers and RTUs that are equipped either AC or DC but not both. This would only require one charger -rectifier module plus one for a backup which is minimal current from the UPS. The GTR8000 Base Repeaters draw similar current as the existing 800 MHz Quantar stations. D. The last step would involve testing the system for proper operation with at least a sub -set of the total system. This could be a few channels on line to test the system features and coverage. The existing MCC7500 training consoles at Pembroke Pines could be moved over to the new Master Core for testing the complete system ATP and the coverage ATP. Once the tests are successful and completed, the system will be ready for transitioning. 1.13.2 Staging A. Each individual assembly or equipment unit shall undergo factory testing prior to shipment. B. Standard factory test documentation that indicates the tests performed and the successful completion of testing, shall be submitted to the County. C. System Staging: 1. The complete system shall be staged and tested at the factory, in the United States, to the greatest extent practical. The intent of the staging tests is to demonstrate to the County that the system is ready for shipment and installation. P25 System and Services Agreement (R1422515R1/P1) Page 181 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Staging will be scheduled at a point that the system design is finalized and all system radio sites have been secured. Staging will not be scheduled in order to expedite payment milestones. 3. The microwave subcontractor must make accommodations to stage its equipment at the P25 Vendor's facility, to allow staging of the complete radio and backup system simultaneously. 4. Provider shall provide all necessary technical personnel and test equipment to conduct staging tests. All deviations, anomalies and test failures shall be resolved at Provider's expense. 5. Provider shall use an approved Staging Acceptance Test Plan. The Staging Acceptance Test Plan shall be submitted no later than 15 business days before the testing starts, and shall be approved no later than five business days before the testing starts. It is expected that the SATP has been performed and all tests have been successful before the County witnesses the official SATP. The SATP shall be signed and dated by Provider and County representatives following completion of all tests. All tests in the Staging Acceptance Test Plan shall be marked as either pass, fail, or pass qualify. 6. Failed tests shall be documented, corrected and retested. All defective components shall be replaced and retested. Defective components that cannot be corrected shall be replaced at the expense of Provider. 7. Retest of individual failed SATP tests or the entire plan shall be at the County's discretion. 8. The fully executed and completed SATP document shall be provided to the County. Once the system details are verified and captured during the Design Review process, the system's Fixed Network Equipment (FNE) will be ordered and manufactured. Motorola will stage all FNE systems before shipment. Motorola Solutions achieves its high levels of customer satisfaction in part by assembling and testing every communications system sold to stringent quality and functional performance tests prior to the system shipping. After the system is assembled and configured, staging technicians and engineers will power up the equipment, load software, set parameters, program, configure, and optimize the radio equipment. Radio parameters will be set according to inputs from the field integration team. System software and system features will be tested and validated. Additionally, MCC 7500 dispatch positions will be assembled, configured, and optimized in order to execute all the ATP tests. All system parameters will be set according to specifications to verify proper operation and functionality. These parameter settings will be recorded and documented to provide baseline information to the field integration team. P25 System and Services Agreement (R1422515R1/P1) Page 182 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Once the system or subsystem has been assembled, optimized, and integrated as a complete working unit, the system will be tested according to the Factory Acceptance Test procedures. Factory acceptance testing will comprise all major systems in the radio solution, including the subscriber radios. These tests will provide the County with the opportunity to observe the radio subscriber equipment programmed and optimized as an integrated system and to test the functionality and features of subscriber radios in a factory environment. During testing, all measurements or outcomes will be recorded within the test script, as indicated in the test. The result of a test procedure will be "Pass", "Fail", or a measured value. 1.13.3 System Installation A. Installation shall include a complete, tested system to include placement of associated cabling, appropriate system layout, and terminal connections. Providershall provide associated power supplies and any other hardware, adapters and/or connections to deliver a complete operable system to the County at the time of acceptance. B. All installations shall be performed by factory -authorized or Vendor -affiliated service shops. Other shops or installers may be used upon mutual agreement between the County and Vendor. Qualified, adequately trained personnel familiar with this type of work shall perform all installations. Providershall provide the names of the service shops, their qualifications, a description of their certified training on the System, a summary of their experience and a list of five references (minimum) for each proposed shop. C. Prior to the start of the system installation, the Provider shall participate in a mandatory project site survey with the County or County's representative to confirm actual equipment location within each space. At that time, the exact equipment locations shall be determined and documented by Provider. D. Provider shall coordinate with others, as appropriate, to confirm that any preparation work that affects the installation of the base station equipment, such as tower work, coring, bracing, conduit, electrical, etc., is complete before final inspection. E. Provider shall provide and pay for all materials necessary for the execution and completion of all work. Unless otherwise specified, all materials incorporated into the permanent work shall be new and shall meet the requirements of this specifications document. All materials furnished and work completed shall be subject to inspection by the County or the County's representative. F. Equipment supplied as spare equipment shall not be used for installation of the System. All spare equipment shall be supplied in an unused condition. G. All equipment and devices shall be cleaned internally and externally, and all damaged finishes shall be repaired. P25 System and Services Agreement (R1422515R1/P1) Page 183 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 H. Worksites shall be left neat and broom swept upon completion of work each day. All shelter floors will be thoroughly cleaned and all scuff marks and abrasions shall be removed prior to acceptance. All trash shall be removed weekly. Inspection: 1. The County shall conduct an inspection of the installations upon substantial completion. Any deficiencies shall be documented on a single punch list and provided to Provider for resolution. 2. Final acceptance testing shall not commence until all punch -list items are resolved. Following factory staging and testing, the equipment will be shipped to the Motorola Solutions storage facility, prior to installation. As the equipment arrives on -site, Motorola Solutions personnel will perform site audits to ensure that each site is ready for equipment installation. After the equipment is installed, Motorola personnel will conduct equipment measurements to ensure that all appropriate levels have been set, and that the equipment is functioning according to the system design and manufacturer's specifications. Once the equipment has been confirmed to be operating properly, Motorola personnel will repeat site - auditing procedures in order to verify that each site adheres to the standards documented in quality control, Motorola Solutions will maintain strict adherence to documented procedures including Motorola Solutions' Standards and Guidelines for Communication Sites (R56) manual. Motorola Solutions will also adhere to TIA, FCC, National Electric Code, and all applicable federal, state, and county codes and ordinances as defined in the RFP. Successfully completing these audits ensure that the quality of the installation will support the system's performance and safeguard against site safety issues. 1.13.4 Fleet Mapping A. Broward County wishes to optimize fleet maps amongst user agencies in order to improve interoperability and usability. The Provider shall develop the fleet map in coordination with the County radio system coordinators. B. Provider shall develop the actual fleet map with input and direction from the County. The fleet map shall contain at a minimum: 1. Talkgroup ID 2. Agency 3. Emergency actions 4. Encryption capability 5. Roaming capability 6. Priority 7. Scan P25 System and Services Agreement (R1422515R1/P1) Page 184 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 C. Proivder also shall develop subscriber unit programming templates. These templates shall have the basic features and functions defined for a particular subscriber unit and user type. Templates shall be developed on a per -agency basis. D. Once the fleet map and templates are approved and completed, Provider shall use these for installation of subscriber units and for further configuration of the system. Providershall submit these with the final as -built documentation. As the system is being installed, the County and Motorola Solutions will develop the plan for controlling radio communications within and across the County's groups, otherwise known as "fleetmapping". Taken as a whole, the process of fleetmapping includes the collection, qualification, and organization of data regarding the radio communications between individuals, and developing specific fleetmaps that determine how the radio communications for each user group of an organization can be most efficiently controlled. Fleetmapping also provides a structured approach to the management of many radio users and provides the opportunity to plan for expansion or make changes within an organization. Its primary objective is to allow the backbone radio system and subsystems to communicate properly with dispatch consoles and radio users in the field. Typical system fleetmap templates are built from customer involvement and feedback, Motorola Solutions' best practices in engineering and guidelines, and system product specifications. Fleetmapping will begin with meetings between the County and Motorola Solutions to define the relevant groups within the County, review current organization SOPs, and current resource utilization. Through these meetings, Motorola Solutions personnel will create a master list of talkgroups based on agencies' organizational structure and cross -functional requirements, and detail the specific loading and configuration of each of those talkgroups, including estimated number of users, anticipated call frequencies and durations. Based on this set of data, Motorola can then create programming templates for each subscriber, including system wide parameters, button and menu assignments, and feature configurations. Once the templates are reviewed and approved by the County groups, Motorola will use the final versions to develop subscriber codeplugs and test them on the live system. Motorola Solutions will also be responsible for installation of mobile subscribers as defined in the proposal. Broward County and /or User Agencies will be responsible to provide vehicles for Motorola Solutions to perform installs in an efficient manner. 1.13.5 Coverage Testing The CATP shall be consistent with the procedures and guidelines outlined in TIA TSB-88, latest revision. P25 System and Services Agreement (R1422515R1/P1) Page 185 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Coverage testing shall commence only after the radio systems are fully tested and aligned. Significant changes to the system shall require retesting of coverage at the County's discretion. 3. Provider shall perform two types of coverage testing: a. Automated objective mobile drive testing providing Bit Error Rate (BER) and signal strength measurements b. Non -automated subjective Delivered Audio Quality (DAQ) testing (intelligibility testing) Both types of testing shall be complementary and serve to fully verify that coverage requirements are met, both technically and operationally. 4. Test Configurations: a. Configurations for the objective and subjective testing shall represent typical operating configurations to the greatest extent possible, using portable and mobile radio equipment to be used with the system. b. Automated Objective Mobile Drive Testing: i) Provider shall test both the signal level and BER, at a statistically significant number of test locations throughout the county utilizing automated test equipment. ii) For testing purposes, the county shall be divided into the minimum amount of uniformly sized test grids per the estimate of proportion formula in TSB-88 3.3. The grid size may vary from a minimum size of 0.25 mile by 0.25 mile to a maximum of 1.25 mile by 1.25 mile. Each of the four subdivided areas with separate coverage requirements must independently achieve a statistically significant number of test points. iii) Inaccessible grids shall not count as either a pass or fail in the statistical analysis. iv) A grid will be considered a "fail" if the outbound signal is measured at a BER greater than or equal to 2.4%, or an inbound signal is measured at a BER greater than or equal to 2.6% (per TSB-88). P25 System and Services Agreement (R1422515R1/P1) Page 186 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 v) Any failed grids may be changed to "pass" if the underlying issue is corrected and the grid is retested. vi) This testing shall include both talk -out and talk -in measurements. c. Non -automated Subjective DAQ Testing: i) Non -automated subjective DAQ coverage testing shall be conducted using typical portable radios supplied with the system. ii) Test radios shall be placed in line with attenuators to simulate the appropriate level of in -building attenuation. Vendors may identify alternate testing methodologies to adequately simulate in -building characteristics. iii) Talk -out and talk -in performance shall be documented. iv) Provider shall provide a standardized test form for testing. v) A grid will be considered a "fail" if both the inbound and outbound subjective audio evaluation has been graded less than DAQ 3.4. (Speech understandable with some repetition) d. The CATP will be successfully completed when both the objective and subjective tests conducted in each of the four coverage areas achieve a pass rate of 95 percent. 1.13.5.1 Coverage Acceptance Test Plan Overview This Coverage Acceptance Test Plan (CATP) is designed to verify that the voice radio system implemented by Motorola Solutions meets or exceeds the required coverage reliability within the Broward County service areas, as defined by the RFP. The CATP defines the coverage testing method and procedure, the coverage acceptance criterion, the test documentation, and the responsibilities of both Motorola Solutions and the County. Coverage acceptance testing is based upon a coverage prediction that accurately represents the implemented infrastructure and parameters that are consistent with the contract agreements. If the implemented system varies from the design parameters, then a revised coverage map will be prepared. New test maps will reflect the measured losses and gains associated with the implemented infrastructure and subscribers. These will be used to define the test configuration and potential areas from which test locations may be included in the evaluation process. P25 System and Services Agreement (R1422515R1/P1) Page 187 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 To verify that the radio coverage reliability is met as is presented, the indicated coverage areas within Broward County will be divided into equally sized test tiles. The table below shows the Coverage ATP test tile sizes and approximately quantity. Test Tiles for Coverage ATP 0.87 I N/A I 1045 I N/A I N/A I N/A 0.62 I N/A I N/A I 549 I 856 I N/A 0.28 I N/A I N/A I N/A I N/A I 1012 1 332 N/A N/A N/A N/A * max tile size of 2km or 1.25mi There will be five Coverage ATP test service areas as noted in the RFP. Each one of these tests will be standing alone and will be completed by separate test teams. The Grid Maps for the five individual tests were included in the response to the RFP as Evaluation Criteria Attachments Section 2.12. The table below shows the predicted service area reliabilities as required by the RFP. Predicted system coverage for CATP Equipment Service Area Service Area Service Area Service Area Service Area Configuration Backup system Everglades 10 Miles Off 20 db Loss 25 db Loss Shore Portable (RSM) .% outside % 20 •• loss 25 •• Loss Mobile %Wave N/A N/A % i Boat Mast The following section provides a detailed description of the CATP. 1.13.5.2 CATP Definitions Several definitions are needed to accurately describe the coverage test method. P25 System and Services Agreement (R1422515R1/P1) Page 188 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Coverage Area The coverage area is the geographical region in which communications will be provided that meets or exceeds the specified Channel Performance Criterion (CPC) at the specified reliability for the specified equipment configurations. These coverage areas are the jurisdictional boundaries of Broward County and the service areas defined by the RFP. Channel Performance Criterion The CPC is the specified minimum design performance level in a faded channel. For this system, the CPC is a Delivered Audio Quality (DAQ) of DAQ-3.4 for portables and mobiles. DAQ definitions are provided in table below. DAQ definitions .A• Faded Subjective Performance Description1 Unusable, speech present but unreadable. 2 Understandable with considerable effort. Frequent repetition due to noise/distortion. 3 Speech understandable with slight effort. Occasional repetition required due to noise/distortion. 3.4 Speech understandable with repetition only rarely required. Some noise/distortion. 4 Speech easily understood. Occasional noise/distortion. 4.5 Speech easily understood. Infrequent noise/distortion. 5 Speech easily understood. Reliability The reliability, also defined as the CPC service area reliability, is the percentage of locations within the coverage area that meet or exceed the specified CPC. It represents the average of all tiles for the defined service area. As already described above, there are five defined service areas as outlined within the RFP. Motorola Solutions has indicated the CPC service area reliability of these areas in the table for the losses detailed in the RFP. Although the coverage maps do not guarantee coverage within a specific location, they do indicate the ability of the system to overcome the expected losses of typical buildings located within the county as defined by the RFP. Equipment Configurations There are two configurations for the field unit equipment or subscriber upon which coverage acceptance is based. Motorola Solutions' coverage maps for this system indicate the coverage area for the following equipment configurations: 1. Portable (2.5-watt). A. Remote speaker microphone. B. Hip level (3.3 feet for transmit and receive) with % wave flex antenna. C. Swivel case clip. P25 System and Services Agreement (R1422515R1/P1) Page 189 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Boat (10-watt) with % wave antenna mounted on a boat mast at 5 feet with a ground plain. The infrastructure that supports this configuration is the following: 4. 11-site TDMA system transmitting simulcast and receiver voting. 1 ASTRO Site Repeater. Transmitting TDMA ASTRO® 25 Harmonized Differential Quadrature Phase Shift Keying (H-DQPSK) Simulcast Modulation, which is fully compliant P25 and Receiving ASTRO® 25 Harmonized Continuous Phase Modulation (HCPM). 1.13.5.3 CATP Method The method used to test coverage is statistical sampling of the predicted coverage area to verify that the CPC is met or exceeded at the required reliability for each of the defined equipment configurations. It is impossible to verify every point within a coverage area, because there are infinite points; therefore, coverage reliability will be verified by sampling a statistically significant number of randomly selected locations, quasi -uniformly distributed throughout the predicted coverage area. This CATP provides a method of tracking test tile location using Motorola Solutions' Voyagers" hardware and software. A GPS receiver will provide location information indicating when a valid test tile is available for testing. The method follows TIA TSB-88.3-D §5.0, "Performance Confirmation" for statistical sampling. This CATP provides an objective, quantitative method of measurement using Voyager software in conjunction with an APX 6000 portable radio for location reference, signal strength measurements and BER measurements. The SSI measurements will be for information only. The BER measurements will be for a pass/fail for the objective portion of the CATP per the RFP. The CATP provides a subjective audio quality test by using actual equipment and simulating the required building loss with attenuators, and then performing voice test messages to determine the pass or fail of the required DAQ-3.4 voice quality. The subjective portion of the test will be for a pass/fail for the subjective portion of the CATP per the RFP. Determine the Required Number of Test Tiles in the Coverage Area The predicted coverage area shown on Motorola Solutions' coverage maps and service area will be divided into a tile pattern to produce at least the number of uniformly sized test locations (or tiles) required by the Estimate of Proportions formula f TSB-88.3-D, §5.2.1, equation 21. The minimum number of test tiles required varies for different systems, from a hundred to many thousands, depending on the size of the service area, desired confidence in results, type of coverage test, and the predicted versus required reliability. Motorola's Hydras"' coverage modeling tool calculates the required test tiles as described. Constraints on Test Tile Sizes The minimum tile size is 100 by 100 wavelengths; however, the minimum practical test tile size is typically about 400 by 400 meters (about 0.25 by 0.25 miles). The minimum practical tile size for any system is determined by the distance traveled at the speed of the test vehicle while sampling, GPS P25 System and Services Agreement (R1422515R1/P1) Page 190 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 error margin, and availability of road access within very small test tiles. A related consideration is the time, resources, and cost involved in testing very large numbers of very small tiles. The maximum test tile size is 2 by 2 kilometers (1.25 by 1.25 miles). In some wide -area systems, this constraint on maximum tile size may dictate a greater number of test tiles than the minimum number required by the Estimate of Proportions formula. Accessibility to Test Tiles Prior to testing (if possible) or during the test, Motorola Solutions and the County will determine whether any test tiles are inaccessible for the coverage test (due to lack of roads, restricted land, etc.). Inaccessible tiles will be eliminated from the acceptance test calculation; however, a minimum number of test locations must be accessed to provide a statistically valid test. This is important since all valid test tiles are part of the prediction and when tiles are removed from the proof of performance testing, the area reliability accuracy could be adversely affected. TSB-88.3-D, §5.5.4 provides consideration for inaccessible test locations called "Estimated based on adjacent grids (single grids only)." Single inaccessible test locations would be considered a "pass" if five of the eight surrounding test tiles provide passing results, provided that the CATP test tiles are defined as follows: 7. Only those test tiles where the majority of the tile falls within the boundaries of the CATP area under test. 8. Those test tiles within the CATP boundaries that are actually tested. 9. Inaccessible test tiles that are surrounded by not less than five contiguous test tiles which have been tested and show an actual passing result (untested test tiles are not counted). 10. Any other untested test tiles that do not fit any of the criteria above (e.g., untested test tiles surrounded by other untested test tiles, or less than five passed test tiles, etc.) would be categorized as simply "untested" and will not be factored into the results as a "CATP tile." Randomly Select a Test Location within Each Tile Using Voyager, the actual test location within each test tile will be randomly selected by the test vehicle crossing into the tile at an arbitrary point, with an arbitrary speed and direction. This will be the queue for the objective sampling test to begin. After the sample is taken for both SSI and BER, the test team will initiate the subjective voice test to determine if the test point passes the audio quality DAQ test. P25 System and Services Agreement (R1422515R1/P1) Page 191 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Perform Measurements in Each Tile In each test tile, a series of 200 or more sequential outbound SSI measurements (sub -samples) will be made and 2 sequential BER measurements (sub -samples) also made for Time Division Multiple Access (TDMA). This test location measurement, containing a number of sub -samples, constitutes the test sample for this location. The test sample will establish the local mean and median SSI/BER within the test tile. with this measurement, the target SSI/BER for each configuration and loss is established. The distance over which the sub -samples are measured will be 40 wavelengths. A mean of multiple SSI/BER sub -samples is used rather than a single measurement to ensure that the measurement is not biased by taking a single sample that might be at a peak or null point on the radio wave. Determine If Each Test Tile Passes or Fails the CPC Requirement for the Objective Test To simulate a portable with the required losses of buildings and portable configuration, the indicated net attenuation in table below is used with a portable and the mobile unity gain antenna on the test vehicle. Both talk -in and talk -out BER tests must pass in a given tile for the grid to pass the objective test. Net target signal strength indication — TDMA mobile Net target signal strength indication — TDMA portable with RSM 1 The -8.6 dB is the antenna loss figure for the APX portable at hip level in a swivel case. The +4.1 dB is the mobile antenna and transmission line that a portable does not have and thus must be added back to get the signal at the input to the test radio. The -1.0 db is for the increased antenna height of the typical test vehicle (5.0'). P25 System and Services Agreement (R1422515R1/P1) Page 192 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Determine If Each Test Tile Passes or Fails the CPC Requirement for the Subjective Test The following tables will be used for the determining the correct net attenuation for the subjective voice quality test using TDMA. The attenuation again simulates losses that may be encountered by various urban area buildings as defined in the RFP. These net attenuations will be used for the subjective voice testing in a vehicle. In each test tile, a voice test exchange will be initiated using predetermined text typical of a common voice exchange between the fixed location and the portable location. The person conducting the test at the portable will be moving at a typical speed for the surrounding conditions. Coverage acceptance testing will be performed in the both the talk -out and talk -in direction to determine if test tile passes or fails. Both talk -in and talk -out tests must pass in a given tile for the grid to pass the subjective test. Net target signal strength indication — TDMA mobile Net target signal strength indication — TDMA portable with RSM A. Determine the Coverage Area Reliability for Acceptance After all accessible tiles in the coverage area have been tested; the coverage area reliability (percentage) will be determined by dividing the number of tiles that pass by the total number of tiles tested. The coverage test acceptance criterion for each equipment configuration is that the tested coverage area reliability must be equal to or greater than the required reliability as shown in the tables. 2 The -8.6 dB is the antenna loss figure for the APX portable at hip level in a swivel case. The +4.1 dB is the mobile antenna and transmission line that a portable does not have and thus must be added back to get the signal at the input to the test radio. The -1.0 db is for the increased antenna height of the typical test vehicle (5.0'). P25 System and Services Agreement (R1422515R1/P1) Page 193 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.13.5.4 Responsibilities and Preparation This information will help set the expectations of the County and Motorola Solutions regarding requirements for equipment, personnel, and time during the coverage test. The County will provide the following for the duration of the coverage test: 1. Boats for testing the off shore and Everglades (Broward County plus 10 miles off shore). This can be given to the in -vehicle team that finishes first. 2. County representative(s) may be provided by County at County discretion (one can be a County Consultant) for any test vehicle or for the fixed location (which may be the dispatch center). Motorola Solutions will provide the following for the duration of the coverage test: 1. Test teams and Vehicles for the duration of the test. A minimum of three test teams will be provided: one team for the Everglades area, a second team for the 20 db service area and a third team for the 25 db service area. Whichever team finishes first can then test the off shore service area or the Backup service area. Motorola will provide all necessary vehicles other than the boat(s) for the water grids. Each test team shall include distinct team members as follows: (1) driver; and (2) operator of the equipment (the test kit Voyager). In addition to the foregoing, Provider will provide additional Motorola representatives or subcontractors for each of the following: (i) at the dispatch location returning DAQ calls; (ii) at a simulcast prime site monitoring inbound BER; and (iii) at the ASR site monitoring inbound BER. 2. At least one calibrated Motorola Voyager coverage testing package per team. 3. Test radios for each field team (unless required otherwise, use the delivered customer subscribers). Coverage acceptance testing will be performed within the borders of Broward County and within the 10 miles off shore service area. Motorola Solutions has determined the minimum number of test tiles required, as described in Section 1.13.5.3 of this CATP. Motorola Solutions and the County will plan the route for the test vehicles through the coverage test area, to ensure that at least the minimum required number of tiles is tested. If possible, any tiles not accessible to the test vehicles will be identified while planning the route. Motorola Solutions will check and/or calibrate the test radios (standard APX 6000 portables) used with the Voyager coverage testing package in the County's presence. Motorola Solutions will conduct this test only once. If any portion of the test is determined to be unreliable because of proven equipment malfunctions or failures, Motorola Solutions will repeat the portion of the test affected by the equipment malfunction or failure. The County will have the option to accept the coverage at any time prior to completion of the coverage test. Before starting the test, the County and Motorola Solutions will agree upon the time frame for Motorola Solutions' submission of a report containing the coverage test results. P25 System and Services Agreement (R1422515R1/P1) Page 194 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.13.6 CATP Procedures 1.13.6.1 Subjective Voice Quality Testing A subjective listening test will be performed for coverage acceptance testing to verify talk -out and talk - in DAQ performance of the system. The procedure for the subjective DAQ coverage test will be as follows: To perform a statistically valid subjective DAQ test, a large group of people is required to ensure high confidence in the results. However, obtaining a large group of people for a subjective listening test is usually impractical; therefore, several (3 to 7) people in a car or van must be used for the test. Since a group this small cannot provide statistically significant results, it is very important that the personnel participating in the subjective test be familiar with the sound of radio conversations. Before subjectively testing, all personnel who will evaluate audio quality must be "calibrated" by listening to examples of static and faded audio of various CPC levels from the type of system being tested. 2. A fixed control point location will be established. Prior to testing, the County and Motorola Solutions will agree upon a procedure to allow each audio transmission to be evaluated for approximately 8 to 20 seconds. 3. The test participants will be divided into teams, each consisting of personnel from the County, Mission Critical and Motorola. Each team will have members that operate a portable unit inside the test vehicle and members that are stationed at the fixed control point location. An odd number of team members is required to avoid ties for the pass/fail consensus. 4. As the field test teams drive through the coverage areas, test locations within each tile will be selected randomly by Voyager that will be conducting the objective BER and informational SSI testing. The voice subjective test may begin after the sampling is complete. This is to prevent any possible receiver degradation to the receiver sampling the SSI/BER and to meet the TSB88 requirement of a randomly selected test point. 5. The field test unit will make a call and identify the test tile by the current x-y tile or tile cell number location and repeat one of ten phonetically balanced phrases (approximately 8 seconds in length). The fixed location unit (console) test team will then determine if the voice passes or fails the DAQ criteria as defined by the table. The fixed location will then repeat 1 of the 10 phonetically balanced phrases (approximately 8 seconds in length) and the field team will in turn determine if the voice passes or fails the DAQ criteria. 6. Test teams will only be permitted to attempt the DAQ test one time per grid. A failure of the initial test must be recorded as a failure for the grid. Multiple attempts compromise the ability to accurately capture signal reliability. 7. The tile pass/fail evaluations will be used to determine the coverage area reliability of the defined coverage areas in the table. A tile will only be counted as a pass if both the talk -in and talk -out BER test yield a passing result. A failure of either test will result in a failure for the grid. 8. Coverage acceptance will be based on demonstrating that the percentage of the tile locations, as described in the table for each equipment configuration will provide an audio quality of DAQ-3.4 or better. The system coverage acceptance criterion will be the successful passing of each of the equipment configurations. P25 System and Services Agreement (R1422515R1/P1) Page 195 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 9. Motorola Solutions reserves the right to review any test tiles that fail the subjective DAQ tests. If a failed grid is to be retested, a sufficient number of tests must be performed to accurately capture signal reliability for the grid. At a minimum, a test must be repeated 20 times within a grid, with all tests yielding a passing result, for a previously failed grid to be converted to a pass. 10. If a coverage test, or a portion thereof, is suspected by Motorola Solutions to have failed due to external interference, those tiles suspected of being affected by an interferer may be re -tested based on the criteria defined above and with the approval of Broward County. If the tiles (or test points) re -tested are confirmed to have failed due to interference, those tiles (or test points) will be excluded from all acceptance calculations and Motorola Solutions will work with Broward County to identify potential solutions to the interference issues. In this circumstance, Motorola must prove the presence of interference, and may only exclude the tiles from consideration with the approval of Broward County. 1.13.6.2 Objective SSI Informational Testing Motorola Solutions will conduct attenuated outbound BER for the area reliabilities as shown in the table for a pass/fail test and collect the SSI for information only. Both the subjective and objective BER testing as described would be performed at the same time but evaluated independently of each other. A tile that tests above the target BER for the objective test point would not constitute a failure for the subjective testing. The reason for this is that the points are taken at different times (thus at different locations). The modeling does not predict the probability of one location against the other but predicts area reliability of all test points for each test within the test area. 1.13.7 CATP Documentation and Coverage Acceptance During the coverage acceptance test, Voyager generates computer files that include the mean and median SSI and BER for each test tile. It also generates a comma separated values (.csv) file that documents these samples for each test point taken. A copy of this data will be provided to the County or Mission Critical at any time during the test or as required. Motorola Solutions will process this data to determine whether the coverage test was passed for the equipment configurations and to produce a map that graphically displays the statistical coverage test results along with the analyzed numbers of the passes and failures. Motorola Solutions will submit to the County a report detailing the coverage test results. This report will include a document, which is to be signed by both the County and Motorola, indicating the test was performed in accordance with this CATP and the results of the test indicate the acceptance or non- acceptance of the coverage portion of the system. The County will have the option to accept the coverage at any time prior to completion of the coverage test or documentation process. P25 System and Services Agreement (R1422515R1/P1) Page 196 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.13.7.1 Mobile/Portable Equipment Checklist Vehicle Make: Radio Serial No.: Vehicle Type: Radio Network ID: Vehicle No.: Date: Service Shop: Technician: Note: A failure of any preliminary check will cause rejection, and the vehicle will be returned for correction before continuing the testing and installation. P25 System and Services Agreement (R1422515R1/P1) Page 197 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Battery Visual 1. Broken or Cracked Case 2. Broken or Cracked Cover 3. Acidic Odor 4. Excessive Corrosion on Battery Posts 5. Battery Posts Tight Wiring Visual 1. Wires Pinched or Damaged 2. Wires Running Over Hot or Moving Parts 3. Condition of Battery Ground 4. Condition of Battery to Hot Lead 5. Wires Run Through Firewall (grommet installed) Radio Check 6. Radio Mounted Securely 7. Antenna Type (unity, 3 dBgw, etc.) 8. Antenna Line Type and Length 9. Antenna Installed Correctly 10. Antenna Length Correct 11. Tx Power Forward 12. Tx Power Reverse (< 4% of Forward Power) 13. VSWR (< 1.5:1) 14. Tx Deviation 15. Tx Frequency 16. Rx Sensitivity 17. Effective Receiver Sensitivity Degradation (refer to the Systems Engineer for maximum allowable degradation) Radio Software Check 18. Verify the hardware revision and model/and serial numbers (include an archive file with the software release version and personality parameters) Comments: Pass Pass Pass Pass Fail Fail Fail Fail P25 System and Services Agreement (R1422515R1/P1) Page 198 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Broward County CATP 114 Wave Objective Inbound & Outbound V6ER Configuration wb me� d: 20 db bldr=3G.0 dhm 35.3=]fl]dbm NMOmHlerokAda- �'9NC ]A d6 Wds=3A.0 dhm-29.3 dhm=0.]dhm-ITmohikaotemra o5le m w]m�s+^^w� -1-.1 Switch Attenuator 3.3 tl6 1- Loss+ l d6.1 I BNC Females) 44 Wave Antenna = 4.3 dB 114 Wave YGPS F op w/ Voyager SW @ Prime Site or ASR site rxmakaaapxr M1FIl 'ymvcraRcnvxmr Power Out = 2.5 Watt or 34.6 dBm APX6D0D Portable GPS Laptop wl Voyager SW USB Programming Cable Subjective Inbound & Outbound Round Trip Configuration Owide=3tOtlhm-5.')=]&]tlhm �h1�=36lltlhm-]5.3=%]tlhm NMOea Nfemok Adapmr EM female m SMA ie 1'9NC 26 dohl�=3M1➢tlhm293tlhm =4]dhn � ST motile vrcenna ffw/rw'ss+eourrt male 1Otl65W ohle morale ohk pma�er attmuamr Power Out = 2.5 Watt or 34.0 dBm 3.3 tl6 Line Loss+l tl6 For Switch Attenuator APx6000 Portable (SNr-Females} 1f 4 wage Antenna = 4 3 dB Broward CATP Attenuation 20 dh area Calculations! 1. Ai w/RSM on hip (swivel or equivalent) = -8.6 dB 2. Building Lass = -20 dB 3. 5.0' Test Antenna Height (standard sedan roof} =-1 dB 4. Mag Mount & 1/4 wave antenna =+4.3 dB 5. Net Attenuation at Receiver Input = 25.3 d6 Broward CATP Attenuation 24 db area Calculations, 1. AP% w/i on hip (swivel or equivalent) = -8.6 dB 2. Building Loss =-24 dB B. 5.C' Test Antenna Height (standard sedan roof] =-1 dB 4. Mag Mount & 1/4 wave antenna =+4.3 d3 5. Net Attenuation at Receiver Input = 29.3 dB Broward CATP Attenuation street area Calculations: 1. APR w/R5M on hip (swivel or equivalent) =-S.6 dB 2. Building Loss = 0 dB S. 5.0' Test Antenna Height (standard sedan roof) _ -1 d3 4. Mag Mount & 1/4 wave antenna =+4.3 d3 5. Net Attenuation at Receiver Input =5.3 dB P25 System and Services Agreement (R1422515R1/P1) Page 199 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.13.8 30-Day Operational Test A. Provider shall perform a 30-calendar-day operational test of the system to ensure that all hardware and software defects have been corrected prior to entering final proof -of - performance testing. The fully integrated operation of the system, including all individual subsystems, shall be demonstrated during these tests. The tests shall be designed to demonstrate the reliability, long-term stability and maintainability of the systems. A failure of any critical component of the system during this test will cause the test to restart after the repair is completed. Providerand the County shall agree on what constitutes a critical failure prior to commencing this test. B. The follow is a non-exclusive listing of items that define a critical failure: 1. System loses controller connectivity (loss of wide -area trunking or console connectivity) 2. Mobiles or portables receiving a denial or busy tone 3. More than one dispatch console operator position off the air 4. The loss of voice communications 5. The loss of data communications 6. Failure of the trunked system switch/controller 7. Greater than two (2) channel resources down, with the exception of unavoidable interference from others 8. A simulcast failure affecting one (1) or more sites or more than two (2) channels 9. Loss or failure of system configuration database 10. Loss or failure of user database 11. Systems not properly transferring to standby generator (if applicable) 12. UPS/DC plant not providing a sufficient buffer during power transfer (if applicable) 13. UPS/DC plant fails to initialize during a power transfer 14. Failures not specifically defined as minor, at the discretion of the County 15. Failures that prevent acceptance criteria from being achieved C. Provider shall provide a 30-day operational test plan during the preliminary design phase. When the system installation, optimization, CATP and ATP have all been completed and the system is ready for use, a 30 day operational test will be started. The details of this procedure will be discussed and agreed to by the County and Motorola Solutions during CDR. This usually involves a group of users designated by the County's user groups to begin using the system for non -mission critical operation to determine if the system appears to be operational and ready for mission critical users. During this 30 day test, the system alarms will be gathered and further evaluated at the end of the test period. The outcome of this evaluation will determine if the system is ready for users to begin using the system. Prior to the test, a list of critical system failures will be developed and agreed upon between Motorola and Broward County. If a critical error occurs during the 30-Day Operational Test, P25 System and Services Agreement (R1422515R1/P1) Page 200 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 the error must be corrected and the test must be restarted. Acceptance will only be provided by Broward County once the system is operational for 30 days without a critical failure. 1.13.9 Preliminary Acceptance Testing A. Prior to Radio System Preliminary Acceptance testing, the Provider shall verify and document that all equipment, hardware and software are upgraded to the latest factory revision. Multiple revision levels among similar equipment are not acceptable. The County shall be given two weeks written notice that the system is ready for final acceptance testing. B. FATP: 1. Provider shall propose a Final Acceptance Test Plan (FATP) for the County's review and approval. Motorola must ensure that the FATP has been pre -performed and all tests have been successful before the County witnesses the official FATP. The FATP shall be signed and dated by Providerand County representatives following completion of all tests. All tests in the FATP shall be marked as either pass, fail, or pass qualify. 2. Provider shall provide all necessary technical personnel and test equipment to conduct FATP tests. All deviations, anomalies, and test failures shall be resolved at Provider's expense. 3. Failed tests shall be documented, corrected and retested. All defective components shall be replaced and retested. Defective components that cannot be corrected shall be replaced at Provider's expense. 4. Retest of individual failed FATP tests or the entire plan shall be at the County's discretion. 5. The fully executed and completed FATP document shall be provided to the County. The FATP will essentially be the same tests that will be performed at the factory staging with additional tests that cannot be performed at the factory. The factory tests and the field /final testing will be determined and agreed to prior to contract signing. These additional tests would include the following: 1. Test all connected alarms reporting to the UEM by simulation of the sensor device. — Open/close contacts. — Disconnect serial cables reporting serial connectivity alarms. 2. DC Power System on RF sites and any new UPS on system controller sites. 3. Generator operation. 4. Complete field testing of the microwave transport using the microwave ATP. P25 System and Services Agreement (R1422515R1/P1) Page 201 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5. Completed CATP. 6. 30 day functional test completed. 1.13.10 As -Built Documentation At the completion of the installation phase, Provider shall provide complete as -built documentation in Microsoft Visio as outlined below: A. Equipment provided B. Plan and elevation drawings of all equipment, including antennas on towers C. Cabling and terminations D. Block and system -level diagrams E. Fleet mapping and programming F. Setup and alignment information G. Successfully completed, signed and dated SATP H. Antenna system drawings, including complete tower drawings with final tower configuration post -implementation I. Cable matrix and punch block documentation J. Completed R56 audits for each location A complete set of maintenance and operations manuals shall be provided at each radio site. Motorola Solutions will provide "As Built" documentation two times during the project. The first will be the CCSI documentation which will include the following at a minimum: 1. Completed Factory Acceptance Testing Procedure documents. 2. Complete system inventory. 3. Complete rack drawings for all sites. 4. System block diagrams. 5. Complete system software documents. The second "As Built" documentation will consist of updated rack drawings that may have changed slightly and include items that are installed in the field that were not staged. In addition, the field documentation will add the following at a minimum: 1. Final rack locations and updated floor plans for each site. 2. Final HVAC and electrical loads for each site. 3. Antenna locations for all sites. 4. Final optimization of all equipment documentation. A. The Provider shall submit three final and complete sets of as -built documentation in their native editable formats and PDF, including the following: 1. Documentation index 2. Field test reports, with dates and actual readings P25 System and Services Agreement (R1422515R1/P1) Page 202 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3. Coverage test reports 4. Warranty documentation 5. Detailed list of materials for each site 6. A copy of all redline documents for each site prior to issuance of the as -built documentation 7. As -built system -level and block diagrams (in Visio format and PDF) 8. As -built site drawings, including all cabling and terminations (in Visio format and PDF) 9. Site layout drawings, as appropriate (in Visio format and PDF) 10. Tower drawings showing any new installations (in Visio format and PDF) 1.13.11 Final Acceptance The County shall deem the System ready for Final Acceptance following successful completion and approval of the following: A. Final design submittals B. SATP C. System installation D. Final inspection and punch -list resolution E. As -built documentation F. FATP, including CATP G. 30-day operational test completion H. 60-day full -load test post-cutover I. Training System functional acceptance tests will be performed when the system optimization is complete. The functional acceptance tests verify the functionality tested at Factory Testing. These tests will verify the entire system in operation, including radio system roaming and subscriber affiliation. Successful completion, with open items, will constitute system acceptance. Final Project Acceptance will be granted when all items that failed any test have successfully passed each applicable test. If deficiencies are found during the testing, both the deficiencies and resolutions to the deficiencies will be documented and agreed upon. Motorola Solutions will remain responsible for the resolution of the documented deficiencies using a punchlist as a controlling document for resolution planning. Once the system is accepted, including final documentation, both parties will finalize the system acceptance. 1.13.12 Decommissioning A. Following the successful cutover to the new system, Provider will be responsible for the decommissioning of the County's existing radio and microwave networks. P25 System and Services Agreement (R1422515R1/P1) Page 203 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 B. At the County's direction, decommissioned equipment shall either be discarded or taken to a location specified by the County C. Provider will be responsible for the removal of all radio and microwave antennas, feedlines, and waveguides and associated tower mounting brackets and connectors D. Provider shall remove all equipment and cables at each radio site. E. Provider shall seal any entry ports for which transmission cables were removed. F. Provider shall remove existing Gold Elite dispatch consoles and associated electronics in the dispatch center equipment rooms. G. Provider shall remove all equipment located at the Broward County Public Safety Building, including the existing system Master Site, Prime Site, Network Management Terminals, and microwave equipment. H. Provider shall update circuit breaker panels current circuit labeling I. Provider shall remove UPS systems and associated transfer switches from remote radio sites J. Provider shall remove unused equipment racks. K. Provider shall fill any holes in the floor or ceiling from removed equipment. P25 System and Services Agreement (R1422515R1/P1) Page 204 of 204 Exhibit A-1 (Radio System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 FACTORY ACCEPTANCE TEST PLAN AGENDA ❑ ARRIVAL AND INTRODUCTIONS (conference room). ❑ FACTORY ACCEPTANCE TEST OVERVIEW / WHAT TO EXPECT / REVIEW FAT PLAN. ❑ SYSTEM TOUR AND FAMILIARIZATION. ❑ FACTORY ACCEPTANCE TEST (FAT) (Unless otherwise specified, tests will be performed on several sites selected at the time of FAT) DAY 1 1. PERFORM A VISUAL INSPECTION AND INVENTORY EQUIPMENT. 2. VERIFY SOFTWARE VERSIONS. 3. VERIFY TRANSMITTER AND RECEIVER FREQUENCIES. 4. VERIFY RADIO TRANSMIT POWER OUTPUT AT TOP OF RACK (TOR). 5. VERIFY RECEIVER THRESHOLDS. 6. VERIFY END -TO -END CIRCUIT ASSIGNMENTS AND CONTINUITY AT ALL SITES. 7. PERFORM A LONG TERM BER TEST (overnight test). Objective: The residual BER test shall be made under NO FADE CONDITIONS. The test period shall be 12 hours with BER not to exceed the test objective of Nx10E-12, where "N" is equal to the number of radio hops (one way). DAY2 8. CHECK LONG TERM BER OVERNIGHT TESTING. 9. VERIFY TRANSMITTER AND RECEIVER SWITCH OPERATION. 10. DACGE CARD TESTING: ETHERNET THROUGHPUT. 11. DEMONSTRATE OPERATION OF ASSENTARIA SITE BOSS 550. 12. DEMOSTRATE OPERATION OF CONFIGURATION AND MANAGEMENT TOOL (PORTAL). 13. DEMONSTRATE PROVISION NMS- OPERATIONAL CAPABILITIES TO INCLUDE ALARMS REPORTING, CONTROLS FUNCTIONALITY. ❑ REVIEW FAT RESULTS AND AGREE ON "ACTION ITEMS" (conference room). ❑ DISCUSS PLANS FOR SHIPMENT (conference room). ❑ AUTHORIZATION FOR SHIPMENT. SIGN -OFF ON CERTIFICATE OF ACCEPTANCE (conference room). P25 System and Services Agreement (R1422515R1/P1) Page 1 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ❑ FACTORY ACCEPTANCE TEST (FAT) 11 OVERVIEW Prior to Factory Acceptance Test, all Equipment is staged on the factory floor and connections are made to simulate network connections and system layout per System documentation. Transmission measurements are conducted between coordinating radio assemblies to assess the overall radio equipment operation. TDM channels and/or Ethernet channels are provisioned per the channel plan and each channel is tested to the specification using appropriate test sets and procedures. For all equipment, tests are conducted in accordance with recommendations stated in the appropriate product manual(s). Network Management System monitoring and control functionalities are verified using the Provision NMS provided for the system or verified using factory provided Provision NMS if NMS is not provided for the system. 13 SCOPE OF WORK Provider staff will perform the tests as outlined. Any exceptions, additions, or deletions will be noted in the appropriate section of the FAT document. The customer representative(s) that witnessed the FAT test process will initial each test of the master copy of FAT document upon completion of the test. The Provider representative will also initial each test as the test program progresses. The primary representative for each party will sign the Certificate of Acceptance upon completion of the tests. The signatories are stating that they have witnessed the FAT as defined in this document, and that witnessed test values were within the specification of recorded test results on factory test data forms. 13 ETHERNET TESTING Throughput The RFC2544 Throughput Test method is used for evaluating the transfer performance of the equipment. Throughput is a measure of how many input frames the network equipment can transfer without dropped frames. Throughput is measured by inputting frames to the device under test (DUT) at a known rate and checking whether or not the transferred frames are lost. The input frame rate is changed to measure the maximum rate at which frames can be transferred without loss. Here's a concrete example. First, frames are input to the DUT at a rate of 10 k fps The DUT is not able to transfer all the input frames and part of the frames seem to be lost. In this case, the frame input frame is lowered to 9.5 k fps and the test is performed again. In this case all the frames are transferred. As a result, the DUT Throughput is evaluated as being between 9.5 and 10 K fps. Naturally, if all the frames are transferred without loss in the first test, the frame input rate is raised and the test is rerun. The frame transfer performance is measured at different rates at different frame sizes and the maximum rate at which frames are transferred without frame loss is the Throughput. RFC2544 Throughput Measurement Method Send rate_ 10 k fps Send rate: 9.5 k fps ���01000i0F �I OOl01100 0O 00 00I i. T �L 1100 01100 LE:X L�J Frame loss 'Transfer of an uccntrrenre:: frames 9.5 k fps — Throughput - 10 k fps P25 System and Services Agreement (R1422515R1/P1) Page 2 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 TEST FAILURE HANDLING PROCESS In the unlikely event that any component should fail during factory acceptance testing, or fail to meet the criteria specified to pass a specific test: a) Where a failed component can be immediately replaced, it will be and testing will continue as per the test procedure. b) If a system test should fail, factory engineers will be given an opportunity to remedy the problem. A re -test will then be performed ACCEPTANCE CRITERIA A punch list of open items will be prepared. Upon conclusion and satisfactory completion of this Factory ATP and after all punch list items have been resolved, a Certificate of Acceptance will be signed by County representative and Provider representative to certify that the equipment has been approved for delivery. NtA Aviat x�rwo�x• Certificate ofFactory Acceptance Thais is to Bert" that The Digital Microwave 4 ,0ew supplied by Aviat Netwoyks for Project Marne her been Inspected. Testec4 and Aecepted by, CUSTOMER NAME Avid(Nehvorks Sales, Order Axxxxx, Month dd, "yy --d r �-,r• -i .ss,�Md P25 System and Services Agreement (R1422515R1/P1) Page 3 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 PRODUCT(s) a) Eclipse IRU 600 b) Asentria S550 ° RFFFRFNCFS a) Instruction Manuals ° TEST EQUIPMENT # Description p Model Number* Serial Number* Calibration Due Date* 1 POWER METER (HP435 or Equivalent) 2 STD POWER HEAD (HP8481A or equivalent) 3 HI POWER HEAD (HP8481B or equivalent) 4 LOW POWER HEAD (HP8481D or equivalent) 5 PATH ATTENUATORS 6 ETHERNET TESTER (SMB600B or equivalent) 7 BER TESTERS: 8 Other: *to be filled during Factory Acceptance Test P25 System and Services Agreement (R1422515R1/131) Page 4 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1:1 PROCEDURE VISUAL INSPECTION AND INVENTORY: 1.1. Visual inspection 1.1.1. Verifv that eauipment is installed per Rack Profiles. 1.1.2. Verify labeling of racks 1.1.3. 1.1.4. Using bill of material list (Rack Build report), inventory all hardware for completeness and accuracy. 1.2. Mechanical Inspection 1.2.1. Check that the shelves are secure and free of defects or dama 1.2.2. Check that all power wiring are properly secured and aligned. 1.2.3. Check that there are no broken, bent or mis-aligned connectors. 1.2.4. Check that there are no misaligned, dented or twisted shelves. 1.2.5. Check that there is no broken or damaged equipment (connectors, wiring, etc.) 1.2.6. Check that all cabling and wirings are terminated and secured in place. 1.1. Mechanical Inspection 1.1.1. Check that the shelves are secure and free of defects or damages. 1.1.2. Check that all power wiring are properly secured and aligned. 1.1.3. Check that there are no broken, bent or mis-aligned connectors. 1.1.4. Check that there are no misaligned, dented or twisted shelves. 1.1.5. Check that there is no broken or damaged equipment (connectors, wiring, etc.) 1.1.6. Check that all cabling and wirings are terminated and secured in place. RACK # SITE NAME VISUAL INSPECTION MECHANICAL INSPECTION 0) N) COMMENTS: INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 5 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. VERIFY SOFTWARE VERSIONS: 2.1. Using Sales Order Specific documents, configuration/management tool and/or Provision NMS, check software versions. 2.2. Verify capacity license(s) and future licenses, if any. 2.3. Record. SW Versions Part Part Number Description (�) Software License EZE-08001 NODE SW LICENSE, 50 Mbps TOTAL RADIO PAYLOAD CAPACITY Software License EZE-08006 NODE SW LICENSE, 400 Mbps TOTAL RADIO PAYLOAD CAPACITY COMMENTS: INITIALS: SYSTEMS INTG. TECH. CUSTOMER REP. P25 System and Services Agreement (R1422515R1/P1) Page 6 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3. VERIFY TRANSMITTER AND RECEIVER FREQUENCIES: Using "Aviat Portal' or Provision NMS, verify that transmit and receive frequencies are programmed per requirements. RESULTS: RACK SITE NAME RADIO TRANSMIT FREQUENCY (MHZ) RECEIVE FREQUENCY (MHZ) PROGRAMMED TX #1 TX #2 PROGRAMMED RX #1 RX COMMENTS: INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 7 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4. TRANSMIT POWER OUTPUT (TOR) 4.1. Mute Transmitter. 4.2. Install a wave -guide to N-type adapter to the TOR wave -guide flange. 4.3. Connect calibrated high power head to adapter. 4.4. Unmute transmitter. 4.5. Measure/record Power Output at the TOR. 4.6. Record the "Portal" reading. 4.7. Mute Transmitter. 4.8. Disconnect calibrated high power head and remove N-type adaptor. 4.9. Restore RF Connection. 4.10. Unmute the "Transmitter". TEST EQUIPMENT: POWER METER, HIGH POWER HEAD REQUIREMENT: Transmitter Power Output Wrn)x Freq Band Modulation Capacity BW STD/HIGH NP HSB (GHzJ MIA (Mbps) (MHz) TX #1&#2 6 128 157(00) 30 HIGH >_+30.5 >_+30.1 6 64 40(25T1's) 10 HIGH >_+31.5 >_+31.1 * Guaranteed at antenna flange port of ACU for "Maximum System Gain". Deduct 0.1dB for each piece of WG Extension/Expansion kit RESULTS: RACK SITE NAME RADIO TX #1 (DBM) TX #2 (DBM) SPEC MEASURED PORTAL SPEC MEASURED PORTAL COMMENTS: INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 8 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5. RECEIVER THRESHOLD 5.1. Connect path simulator between coordinating racks. 5.2. Calibrate path simulator over the dynamic range and note the attenuator settings vs. Received Signal Level (RSL) at TOR. 5.3. Fade the path until BER reading is 1X10-6. 5.4. Record the measured value. 5.5. Repeat for other units under test. RESULTS: TEST EQUIPMENT: BER TESTER, LOW POWER HEAD, PATH SIMULATOR REQUIREMENT: I Threshold" (dBm) an BER = 1 x10-6 Freq Band Modulation Capacity BW NP/SD/FD MHSB-Uneq MHSB-Uneq (GHz) (Cl (Mbps ) (MHz) RCVR # 1 RCVR # 2 6 128 157 (00) 30 < — 72.00 <— — 71.90 I <— — 65.0 6 64 40 (25T1's) 10 <— — 79.25 <— — 78.15 <— — 72.15 * Guaranteed at antenna flange port of ACU for "Maximum System Gain". Deduct 0.1 dB for each piece of WG Extension/Expansion kit. RACK SITE NAME RADIO SPEC MEASURED SPEC MEASURED COMMENTS: INITIALS: SYSTEMS INTG. TECH. CUSTOMER REP. 6. END -TO -END CIRCUIT ASSIGNMENTS PER CHANNEL PLAN AND CONTINUITY AT ALL SITES. 6.1. Connect Ethernet testers to the circuit under test. 6.2. Check end -to -end IP circuit continuity. TEST EQUIPMENT: Ethernet TESTER. P25 System and Services Agreement (R1422515R1/P1) Page 9 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 REQUIREMENT: Traffic continuity per channel plan. Passed: Yes No COMMENTS: INITIALS: SYSTEMS INTG. TECH. CUSTOMER REP. 7. LONG TERM BER TEST 7.1. Restore all connections. 7.2. Set RF paths to nominal level (about —45 dBm TOR RSL). 7.3. Set PORTAL BER counter for the circuit(s) under test. 7.4. Run the test for at least 12 HRS. TEST EQUIPMENT: INTERNAL BER TESTER I CIRCUIT # I DATE/TIME I COMMENTS: INITIALS: CUSTOMER REP. SYSTEMS INTG. TECH. END OF DAY1 8. LONG TERM BER TEST RESULT 8.1. Check BER result for bit error(s) and bit -error -rate. There should not be anv other error(s). i.e. SL. FL. 8.2. Record results REQUIREMENT: Nx10E-12 where "N" is equal to the number of radio hops. (For a single radio hop for 12 hours 28DS1s connected in tandem, there should be no more than 3 errors for a BER of 10E-12). RESULT: CIRCUIT # DURATION ERRORS BER DATE/TIME Passed: Yes No COMMENTS: INITIALS: SYSTEMS INTG. TECH. CUSTOMER REP. P25 System and Services Agreement (R1422515R1/P1) Page 10 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 9. TRANSMITTER/RECEIVER SWITCH OPERATION 9.1. Using Portal or Provision NMS, mute on-line transmitter or switch to off-line transmitter. 9.2. Observe switching to the other transmitter. 9.3. Restore to normal operation. 9.4. Using Portal or Provision NMS, switch to off-line RAC. 9.5. Observe switching to the other receiver. 9.6. Using Portal or Provision NMS, switch to off-line DAC. 9.7. Observe switching to the other receiver. 9.8. Restore to normal operation. TEST EQUIPMENT: BER TESTER REQUIREMENT: Traffic continuity after switching occurs. NODE(S) TESTED: Passed: Yes No COMMENTS: INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 11 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 10. DAC GE CARD —ETHERNET THROUGHPUT TESTING 10.1. This test would attempt to find the highest rate at which the DUT can forward frames without a loss. It uses simple algorithm to choose rates between the previous rate and a new rate; if a port drops frames, it throttles to a lower rate, and if a port doesn't drop any frame, then it throttles to a higher frame. For throughput test, the following parameters will be used: 10.1.1. Initial rate of 100% of maximum DUT Data rate 10.1.2. Maximum rate of 100% of maximum DUT Data rate 10.1.3. Minimum rate of 50% of maximum DUT Data rate 10.2. Run test for 64 to 1518 packet sizes 10.3. Record results Frame size used Typical Expected Passed Rate Packets/Sec (byte) Throughput 64 >_ 92% 1518 >_ 92% PASS if the throughput for each packet size is consistent with the allocated bandwidth, FAIL otherwise (There is no PASS/FAIL criterion for RFC2544). TEST EQUIPMENT: ETHERNETTESTER REQUIREMENT: Typical Expected Throughput is >_ 92% of allocated bandwidth. Passed: Yes No COMMENTS: INITIALS: SYSTEM INTG. CUSTOMER TECH. REP. P25 System and Services Agreement (R1422515R1/P1) Page 12 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 11. ASENTRIA S550 11.1. Verify set-up and configuration. 11.1. Verify operation of relays. NODE(S) VERIFIED: 11.2. Verify operation of digital inputs. NODES)/DIGITAL INPUT(S) VERIFIED: Passed: Yes No COMMENTS: INITIALS: CUSTOMER REP. SYSTEMS INTG. TECH. 12. CONFIGURATION AND MANAGEMENT Demonstrate operation of PC based configuration and diagnostics tool "PORTAL": 12.1. Verify configuration functionality. 12.2. Verify control functionality. 12.3. Verify alarm reporting capabilities. 12.4. Demonstrate diagnostic futures. Passed: Yes No COMMENTS: INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 13 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 13. PROVISION NMS 13.1. Verify set-up and configuration of Provision NMS. 13.2. Verify IP addresses and IP connectivity of NEs by causing alarms or pinging. 13.3. Verify NMS system interoperation: 13.3.1. Generate events in the NE(s) and observe results in NMS. NODES)/EVENT(S) VERIFIED: 13.3.2. From NMS, change the configuration of NE(s). Verify the change. Put NE back to original configuration. NODES)/CONFIGURATION(S) VERIFIED: Passed: Yes COMMENTS: No INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 14 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 14. Verify redundant routing via MPLS (in addition to loop protection) • CTR 8611 ROUTER o Verify set-up and configuration. o Program host name and password. o Enable SSH. o IP interface configuration per IP plan. o OSPF configuration, flat area 0. o BFD for OSFP enabled between all MW router connections. o QoS o MPLS L3VPN. o MPLS PW o Verify static routes in VRF between site router and MW router. o Configure Static LAG configuration between router and DAC GEv3. o Ping between MW routers to verify global connection. o Ping between site routers to verify VRF connections. o Sample RFC 2544 test between selected remote sites and Primary Site. o Redundant Power supply verification. P25 System and Services Agreement (R1422515R1/P1) Page 15 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 I Thu, ZI-Sap Fri, 21-Sap Sat 2:2-Sap Sun, 33•Sop Man 24-Sap IC la N 7. ! I1 6 F n 3 f - fi _ J 3 i . l I r. — — ti 12 J3a 1300 12:C-0 o:aD ,2:DD ❑ JOG UM ❑ a30 , _:_ U MUG 1012-99 'D-DO.D7.M - 2D12-09-2� 0D:46:55 CDkX SFnw Sr Dots I %rfnrmanz 1ndcator Urit Hi3hight RrrLnt Status Min Max j Errors LI VO j �tJal tics '.a 7.31 7.5? OK 5.02 5,61 F- latcr#ar_e Speed Vb Ifs 100 =DD CK 100 70D = n -*i[:3nOCGetq mbV- 7r.56z7s s.463Laa -OK 3.97981a 14,D94WO - _ i{FiC]nLkasL-04 ; s 3453 4453 CIC 7097 6tse _ 0 P25 System and Services Agreement (R1422515R1/P1) Page 16 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 U--!c 8621 R-1-- IRU 600 nl.s m Test # Site Name (s) Comments (�) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ❑ Passed: Yes No ❑ COMMENTS: INITIALS: SYSTEMS INTG. TECH. P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test CUSTOMER REP. Page 17 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 15. Verify T1 interface and throughput • END -TO -END CIRCUIT ASSIGNMENTS PER CHANNEL PLAN AND CONTINUITY CHECKS o Verify programming of circuits per channel plan/system documents. o Determine the termination points of the circuit. o Connect one BER tester to one end of the circuit o Connect another BER tester to the other end of the circuit. o Reset the test sets and verify error -free traffic. o If the circuit is protected, switch traffic to opposite direction o Reset the test sets and verify error -free traffic. o Repeat for the remaining circuits. TEST EQUIPMENT: BER TESTER. REQUIREMENT: Traffic continuity per channel plan. 30 d8 attenuators ECLIM DAC16x Card ECLIPSE - = - DAC16x Card (D51 Card) (DS1 Card) L_'o oFo 01 0 0 0 0 0 0 iv -... ..:-• T.B� a- DS' Test Set Note: Hard copy of the Traffic Plan will be available during FAT. P25 System and Services Agreement (R1422515R1/P1) Page 18 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 INUe #1 INLIe Ai RAC IN DS1 # RAC 1M INUe 01 RAG 215 ego rs Na , : a a e 5 ram M1 DAC18X SLM 3M CROS�T To�T 1 2 3 4 6 SLOTT & E36MHG mom DACOE3B JACKFDS MFAffT IHLko*l 7O� S TDDT11Nu*#2 (SHEETS) 1 2 8 4 5 8LRT0 Mwffr DAOGEB 1}!}r7; IiiR JK D8x1 c —B'g— JKFLD aRI cow Big INUe#1 1 2 9 4 6 SLOT S DAGGES 1 2 8 • 5 rJ&#I SLOT 7 DACGES I�v_uw_am. A18 Cow Results: INUe #1 D51 # RAC 114 From Site To Site Comments Passed: Yes No COMMENTS: INITIALS: SYSTEMS INTG. TECH. CUSTOMER REP. P25 System and Services Agreement (R1422515R1/P1) Page 19 of 22 Factory Acceptance Test NUe 01 �,•(t; SLOTS 3AA DAC1r']C REAR 56C DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 16. VoIP PHONE (LP201) 16.1. Verify set-up and configuration of IP Phones. 16.2. On the first IP phone, dial the second phone by its IP address (eg 10*11*12*13 to call a phone with the IP address 10.11.12.13). A ring tone should be heard from the dialed phone. 16.3. A second person is to answer the ringing IP phone and ensure clear, two-way conversation is possible. Hang up both ends to end the call. 16.4. Repeat the procedure in the opposite direction. 16.5. Record a pass result if dialing, ringing and clear two way speech is achieved in both directions. IP-PH40HE Gonfiguara#ion MMae u N—t rro M C o nllumire PPP+nF !_..r.RgL_ gUNB ConFinurre Voice Configure T.,..« cant."L IFUrMsw C.ar�ra�fr`[ Fur.Cl Nrarsc P.�.f _P C.9r�[i.8ucar PFa na.sa Rn�.ae Pr. w��rA F In.. elw� Uxryradx s+rsta " counnp-ond i� AdArarxy : i92 _ iE.s _ � _ iaa Sub.rnl FM1a�l�: _— _ m _ Fn-- 1-. Q.&d sy: 142 _ jL _FjL PTL�1ory 6a�rrakn Maine 9�rvsr: Bwnorx}tfry 7arrwain Nn♦na Sewnr: sNTP: ilia 4S �_'•1 iat9 W- a w. r-r air - 12 F2Sf- .1+ F SMTP is - Address: ie9 _ 4S _1153L 1- cu." : LParFng: fIP Sharing A�r Addnsss: r` tl� 4fir fZZS _ 2.S _ 256 _ sss 1Nv� Gorrfig�rrse Sor+ear Rort: T'"w 34 dB Attenuatars 34 dB Attenuatars J P25 System and Services Agreement (R1422515R1/P1) Page 20 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Results: RACK ID Site Name IP ADDRESS DIALING TALKING/RECEIVING N) (4) (4) REQUIREMENT: Pass if dialing, ringing and two-way communication is successful, fail otherwise. Passed: Yes No COMMENTS: INITIALS: CUSTOMER REP. SYSTEMS INTG. TECH. 17. VERIFY PROTECTION SWITCHING. 17.1. Using Portal mute on-line transmitter or switch to off-line transmitter. 17.2. Observe switching to the other transmitter. 17.3. Restore to normal operation. 17.4. Using Portal, switch to off-line RAC. 17.5. Observe switching to the other receiver. 17.6. Using Portal, switch to off-line DAC. 17.7. Observe switching to the other receiver. 17.8. Restore to normal operation. 17.9. Using Portal, switch from Primary to Secondary "Rx Source Lock". 17.10. Verify that traffic did not take hit during this process. 17.11. Using Portal, switch from Secondary to Primary "Rx Source Lock". 17.12. Verify that traffic did not take hit during this process. 17.13. Turn off NPC and observe that INU operates on NCC only 17.14. Turn on NPC. Verify that INU operates on NCC and NPC P25 System and Services Agreement (R1422515R1/P1) Factory Acceptance Test Page 21 of 22 DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 17.15. Turn off NCC and observe that INU operates on NPC only, with no reset or power -off 17.16. Turn on NCC. TEST EQUIPMENT: BER TESTER REQUIREMENT: Traffic continuity after switching occurs. Results: RACK ID Site Name Radio # (4) DC POWER TX RX RAC DAC Passed: Yes No COMMENTS: INITIALS: SYSTEMS INTG. TECH. 18. Include testing of radio traffic running across links for all tests CUSTOMER REP. Microwave link traffic is tested in staging by simulating the microwave path using transitions, attenuators, and cables. These will be in place to test traffic end -to -end across all links in a ring configuration. The Microwave Radio traffic is tested during T1, Ethernet, and MPLS Testing Procedures as outlined. 19. Include testing of radio traffic running over T1 links Microwave T1 traffic is tested on the T1s using BER test sets. Testing shall be conducted using actual channel banks to simulate real world traffic but as the current design does not include any T1 channel banks or other equipment to interface with the T1s. This equipment shall be provided to configure and test along with the microwave links. T1s are tested end -to -end as well. P25 System and Services Agreement (R1422515R1/P1) Page 22 of 22 Factory Acceptance Test DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Field Acceptance Test Plan INTRODUCTION 1.1. Purpose of Document Provider will provide for the installation and commissioning of a new digital microwave radio system for County. The purpose of this document is to outline a method of procedure to be used to test the County's Digital Microwave System at the hop level as well as at the System level. 1.2. Responsibilities Provider will perform the testing of all microwave radios and associated ancillary or supporting equipment. Upon successful completion of the Field ATP, the County will sign off on the successful completion of the Field Acceptance Test. 1.3. System Description In this system, the following equipment is to be tested following installation: • Eclipse IRU600 V3 Antenna Systems • Eclipse INUe/NTUe DC Power System 1.4. Reference Drawings and other Documents The following documents will be used during the testing and will be supplied by Provider subject to prior approval by County: • Eclipse IRU600 User Manual • System Layout Drawings • Path Calculations • Frequency Coordination Sheets • Rack Profile Drawings TEST EQUIPMENT • Site Specific Diagrams • Statement of Work • OEM User Manuals • Factory Test Data Sheets • Installation Specification Provider will have a laptop PC with the Eclipse Portal software available on -site when performing the outlined test procedures in this document. This provides access to the Eclipse radio's on -board diagnostics and real-time performance monitoring tools. All test equipment will have a current Calibration certification, if applicable. • Digital Volt Meter - Measures rack DC voltages. • Clamp on ground tester (AEMC 3711 or equivalent) — Measure ground resistance • RF Power Meter (HP435 or equivalent) - Measures transmitter output power. • STD Power Head (HP8481A or equivalent) - Used in conjunction with the RF Power Meter. • Hi Power Head (HP8481 B or equivalent) - Used in conjunction with the RF Power Meter. • Low Power Head (HP8481D or equivalent) - Used in conjunction with the RF Power Meter. • Variable Attenuator with SMA connectors — Used to perform the Receiver threshold test. • Bit Error Rate Tester — Measures the BER. • Ethernet Tester capable of performing RFC2544/1242/4689 Test — Measures the Ethernet performance. # Description Manufacturer* Model Serial Calibration Number* Number* Due Date* 1 Digital Volt Meter 2 RF Power Meter (HP435 or P25 System and Services Agreement (R1422515R1/131) Page 1 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Equivalent) 3 STD Power Head (HP8481A or equivalent) 4 HI Power Head (HP8481 B or equivalent) 5 LOW Power Head (HP8481D or equivalent) 6 Variable Attenuator 7 Bit Error Rate Tester 8 Ethernet Tester (SMB600B or equivalent) 9 Ground Resistance Tester uetaus to oe compietea on site. TESTING 3.1. Field Test Plan Overview Equipment and System Field Testing is conducted on all Provider -supplied equipment and other ancillary equipment to demonstrate compliance with product and contract specifications. Equipment and System Testing consists of three (3) phases: • Inspection/ Station Test • Hop Test • System Test 3.2. Station Test Upon completion of the system installation, the first phase of the Equipment and System Testing commences. This test phase verifies all site and equipment grounding as well as all Provider equipment installation and rack wiring. All work must be done in accordance with industry best practices: 3.2.1. Grounding Inspection Use the following instructions to perform the Grounding Inspection and record the results in the corresponding fields on the Station Test sheet for each site: 3.2.1.1. Verify continuity of ground wires on the indoor equipment and their bonding by measuring from a reference ground conductor (such as the master ground bar). Measurement should be less than 1 ohm 3.2.1.2. Verify the site/tower ground is implemented properly. Measurement should be less than 5 ohms. 3.2.1.3. Verify ground connections on equipment and rack are properly fastened and the system is grounded to an appropriate ground point(s). The ground connection should measure less than 10 when using a clamp -on ground tester. 3.2.2. Equipment Inspection Use the following instructions to perform the Equipment Inspection and record the results in the corresponding fields on the Station Test sheet for each site: P25 System and Services Agreement (R1422515R1/131) Page 2 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.2.2.1. Perform an inventory check on all hardware using the Inventory Checklist found in the installation spec. 3.2.2.2. Perform a visual inspection of the antennas and waveguide routing outside the equipment shelter or on the antenna mounting structure/tower for proper installation and quality of workmanship. 3.2.2.3. Perform a visual inspection of the waveguide routing inside the equipment shelter for proper installation, bending, labeling and quality of workmanship. 3.2.2.4. Perform a visual inspection of the rack, floor mounting and supporting hardware for proper installation of the equipment, mechanical correctness and quality of the workmanship. 3.2.2.5. Perform a visual inspection of all installed rack circuit breakers for correct sizes and positions. Refer to the Sales Order Summary (SOS). 3.2.2.6. Perform a visual inspection of all installed equipment and cabling in the rack (including wall mounted equipment and dehydrators) for proper installation, mechanical correctness and quality of the workmanship. Refer to Rack Profiles (RP), System Block Diagrams (SBD) and Sales Order Summary (SOS). 3.2.3. DC Power System Test This test procedure will verify proper operation of the DC Controller, Rectifiers and verify all Battery cells are good. Use the following instructions to perform the DC power system test for each new DC power system installed and record the results in the corresponding fields on the DC system test sheet. 3.2.3.1. Rack Installation Inspection • Verify the new DC power system is installed per the SOW and installation instructions. • Verify the rack is secured. 3.2.3.2. Measure and record the following using a DVM. • Measure the AC input voltage. • Verify the AC input breakers for the rectifiers. • Measure the DC float voltage. • Compare and verify the measured float voltage to that on the charge display. • Record the DC current load of the equipment. • Verify the load transfer from charger to batteries and back to charger. • Verify redundant operation by turning off one rectifier and note that the system continues to operate. Re -energize the rectifier and note that the system returns to redundant operation. Repeat for each installed rectifier module. • Verify charger alarms are connected correctly to the alarm block. • Measure the voltage of each battery cell and record the cell voltages. 3.2.3.3. Record the battery bank reserve time • At the end of the station tests remove AC power to the DC power system • Record the time that the power was disconnected • Leave the equipment operating normally • Monitor Pro Vision and record the time when Pro Vision reports alarms due to the equipment shutdown. The batteries must support the equipment for a minimum of 8 hours. Note: The sites must be tested sequentially to avoid isolating a site from ProVision monitoring. P25 System and Services Agreement (R1422515R1/P1) Page 3 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.2.4. Dehydrator Test Use the following instructions to test the dehydrator for each site and record the results in the corresponding fields on the Hop Test sheet. 3.2.4.1. Verify alarms on the Dehydrator. • Only perform this test if the system has been designed to support dehydrator alarm reporting. • Verify that all the dry contact alarm connections on the dehydrator has been installed properly and in accordance with the manufacturers recommended setup instructions. • Using a DVM, verify the state of the relay (NO or NC) under no alarm condition. • Create a Power Fail alarm condition on the relay under test by turning the power off at the switch and verify the change in the relay state with the DVM. • Restore power and observe that the alarm clears. • Open the unused manifold ports and verify that the low pressure alarm occurs when the pressure drops below 1 psi. Note the time that the compressor starts to run. • Leave the ports open and allow the compressor to run. After ten minutes of run time the compressor run time alarm will activate. • Close the ports and observe that the alarms clear when the system regains pressure and the compressor cycles off. • Restore configuration to the original settings once completed. • If the dehydrator has been configured to report alarms through SNMP, confirm operation of the alarms through the ProVision Test. 3.3. Hop Test Upon completion of the Station Tests, the second phase of the Equipment and System Testing commences. This test phase verifies all Provider equipment operation including alarm and control points, DC power, and Provider provided OEM equipment, as applicable: 3.3.1. Microwave Equipment Test Use the following instructions to perform the Microwave Equipment Test for each rack and record the results in the corresponding fields on the Hop Test sheet: 3.3.1.1. Verify the redundancy of the power supply if the INU is fitted with the Node Protection Card (NPC). Power protection switching is hitless. • Ensure that the Eclipse INU is powered up. • Ensure that the NCC and NPC Status LED are green. The NPC Protect LED should be unlit. • Disconnect the -48Vdc supply from the NCC and remove the NCC card from the chassis. Eclipse should not lose power. • Power is now provided by the NPC. The NPC Protect LED should now be lit. • Re-insert the NCC card and power to the NCC. 3.3.1.2. Verify INU IP Address as per the NMS Plan and the Sales Order Summary (SOS). • Using Provider Portal/Pro Vision software, log into the INU using the assigned IP Address. Verify the Portal/Networking page has been configured correctly and proper IP addresses, subnet masks, OSPF/RIP settings, DHCP Server settings, static routing and trap destinations has been assigned where applicable. 3.3.1.3. Verify INU and RFU firmware versions. P25 System and Services Agreement (R1422515R1/P1) Page 4 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.3.1.4. Record Transmitter (Tx) and receiver (Rx) ACU Insertion Losses are configured as per the labels on the ACU units. 3.3.2. IRU Transmit Power Output Test Use the following instructions to perform the IRU Transmit Power output Test for each microwave radio and record the results in the corresponding fields on the Hop Test sheet: Verify Transmitter (Tx) Power Output. Refer to the Eclipse/IRU600 Transmitter output power specification datasheet for the expected Tx output power level as per modulation configuration of the RFU/ODU under test. • Zero out and calibrate the power meter and set correct power factor setting for the frequency band under test. • Attach a 20dB attenuator to the power sensor and enter it's attenuation as the Power Meter offset. • Remove the ACU front panel cover of the IRU600 shelf. • In the Portal Diagnostics/System/Controls screen, send a Tx mute to the RFU under test. • Disconnect the RFU Tx output cable and connect the power sensor (with 20dB attenuator) to the RFU Tx output. • In the Portal Diagnostics/System/Controls screen, turn off Tx mute and click send. • Tx power setting can be adjusted in the Portal radio plug-in screen in 0.1 dB steps. Tx power output accuracy is +/- 2dB. • Compare the measured Tx output power to the Detected Tx power displayed in Portal. • To measure the Tx output level of the Diversity radio, send a Tx protection switch to the secondary radio using Portal. Repeat steps 4 to 9 above. • To return to the original setup, mute the Tx, disconnect the power sensor, restore the Tx output cables and unmute the Tx. 3.3.3. IRU Receive Signal Level (RSL) Test Use the following instructions to record the IRU RSL for each microwave hop and record the results in the corresponding fields on the Hop Test sheet: Verify Receiver (Rx) Received Signal Level (RSL). • Measure the top of rack (TOR) RSL at receiver filters output with the power meter. • Compare RSL TOR to path calculation datasheet. • Compare RSL measurement to the RSL level measured by Portal. On protected terminals repeat for standby radio. Measurement must be within +/- 2dB of calculated value. 3.3.4. IRU Receiver Threshold (Fade Margin) and Interference Test Use the following instructions to perform the IRU Receiver Fade Margin and Interference Test for each microwave hop and record the results in the corresponding fields on the Hop Test sheet: 3.3.4.1. Verify Receiver (Rx) Threshold (fade margin). Refer to the Eclipse/IRU600 Receiver Specification datasheet for the expected Rx threshold level as per modulation configuration of the RFU/ODU under test. • Measure insertion loss (Idb) of calibrated variable attenuator equipped with SMA cables at minimum attenuation. • In the Portal Diagnostics/System/Controls screen, send a Tx mute to the RFU under test. • Insert variable attenuator assembly between the transceiver Tx out and the Tx filter. • In the Portal Diagnostics/System/Controls screen, turn off Tx mute and click send. P25 System and Services Agreement (R1422515R1/P1) Page 5 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. • Increase variable attenuator down to 10-6 BER and note attenuation (AdB). • Calculate fade margin (dB): FM = AdB (attenuation) + IdB (insertion loss) • Repeat test inserting the variable attenuator between the transceiver Tx out and the Tx filter. • Compare to margin given in the path calculation sheets. On protected terminals, repeat for standby radio. Margin must be +/- 2dB from calculation. 3.3.4.2. Verify the absence of Interference. Refer to the Eclipse/IRU600 Receiver Specification datasheet for the expected Rx threshold level as per modulation configuration of the RFU/ODU under test. • In the Portal Diagnostics/System/Controls screen, initiate a Tx mute to the far end RFU under test. • Note the RSL level measured by Portal. • Restore configuration to original settings. RSL reading, if any, should be below the 10-3 BER threshold of the radio. Note: The RSSI filter is 56 MHz wide. The Portal RSL reading may indicate an on -path adjacent channel signal that is not an interference signal. A true interference signal would cause degradation in performance at low RSL levels and result in a 10-6 BER threshold degradation. If the 10-6 BER threshold in step 3.3.5.1 is met, there is no interference on the path. 3.3.5. Transmitter/Receiver Switching Test Use the following instructions to perform the Transmitter and Receiver Switching Test of protected terminals for each microwave hop and record the results in the corresponding fields on the Hop Test sheet: 3.3.5.1. Verify Transmitter (Tx) switching when online Tx is removed or fails. Note that Tx switching is not hitless but traffic continuity should be observed after the switch. • Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. • In the Portal Diagnostics/System/Controls screen, send a Tx mute to the RFU under test or switch to the off-line transmitter. • Verify switching to other transmitter was successful. • Verify traffic continuity. • Restore configuration to original settings. 3.3.5.2. Verify Receiver (Rx) switching when source Rx is removed or fails. Note that Rx switching is hitless and traffic continuity should be observed after the switch. • Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. • In the Portal Diagnostics/System/Controls screen, switch to the off-line transmitter or remove the on-line RAC card from the chassis. • Verify switching to other receive was successful. • Verify traffic continuity and the absence of BER errors. • Restore configuration to the original settings once completed. P25 System and Services Agreement (R1422515R1/P1) Page 6 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.3.6. Ethernet Test Use the following instructions to perform the Ethernet Throughput and Latency Test for each microwave hop and record the results in the corresponding fields on the Hop Test sheet. • RFC2544 Throughput Testing • RFC2544 Latency Testing • RFC2544/RFC1242 Frame Loss Testing 3.3.6.1. Verify RFC2544 Throughput on the system. • Verify the microwave equipment is configured as per the SOS. • Configure the Ethernet test set profile to perform RFC2544 throughput measurement that meets the following criteria: Frame sizes: 64 and 1518 Bytes. Test Duration: 60s Accuracy: 0.01 Errors: 0 Trials to average: 1 Nr of validations: 1 3.3.6.2. Verify RFC2544 Latency on the system. • Verify the microwave equipment is configured as per the SOS. • Verify whether measurement will be done using the store and forward method or the bit forwarding method. • Configure the Ethernet test set profile to perform RFC2544 latency measurement that meets the following criteria: Method: Store and Forward (SaF) or Bit Forwarding (BF). Frame sizes: 64 and 1518 Bytes. Test Duration: 120s Nr of measurements: 1 3.3.6.3. Verify RFC2544IRFC1242 Frame Loss on the system. • Verify the microwave equipment is configured as per the SOS. • Verify that the first trial is run at a frame rate that corresponds to 100% of the maximum rate for the frame size on the input media. • Repeat the procedure for the rate that corresponds to 10% less of the previous trial until there are two successive trials in which no frames are lost. • Configure the Ethernet test set profile to perform RFC1242 frame loss measurement that meets the following criteria: Trial Rates : 100%, 90%, 80%, 70%, 60%, 50%, 40%, 30%, 20%, 10% Test Duration: 100s Max Granularity: 10% 3.3.7. AUX Alarm/Data Card Test Use the following instructions to perform the AUX alarm Test and AUX Data Test on the optional AUX plug- in card for each microwave radio and record the results in the corresponding fields on the Hop Test sheet. Verify configuration and functionality of the AUX alarms. • Using Portal, verify that the correct relay contacts have been configured for specific alarm conditions as per the design documentation. • Using a DVM, verify the state of the relay (NO or NC) under no alarm condition. • Create an alarm condition on the relay under test to occur and verify the change in the relay state with the DVM. • Restore configuration to the original settings once completed. P25 System and Services Agreement (R1422515R1/P1) Page 7 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.3.8. Bit Error Rate (BER) Test Use the following instructions to perform a one (1) hour Bit Error Rate (BER) test on the main radio and a one (1) hour BER test on the standby radio, if equipped, and record the results in the corresponding fields on the Hop Test sheet. This test should be performed after the final alignment of the antennas for each hop. Note that DS1's on a single hop may be "daisy -chained" to test all DS1's at the same time. No radio configuration should be performed while the BER test is in progress. 3.3.8.1. One (1) hour Bit Error Rate (BER) Test on Main radio. • Verify the microwave equipment is configured as per the SOS, SBD and DS1 plan. • Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. • Perform a one (1) hour BER test at the DS1 level for the provisioned DS1. Performance objective: 1x10-io BER one-way, under no fade conditions. 3.3.8.2. One (1) hour Bit Error Rate (BER) Test on the standby radio. • Verify the microwave equipment is configured as per the SOS, SBD and DS1 plan. • Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. • Verify that radio traffic has been switched to the standby radio and that the main radio is offline. • Perform a one (1) hour BER test at the DS1 level for the provisioned DS1. Performance objective: 1 x10-,o BER one-way, under no fade conditions. 3.4. System Test The system level tests will be performed after all sites have been hop tested. Some tests will require personnel at more than one site. Tests may be conducted out of sequence to accommodate site logistics. 3.4.1. Ring Wrapping Test Use the following instructions to perform the Eclipse ring wrapping for each microwave hop and record the results in the corresponding fields on the System Test sheet. Note that this test only applies to the ring portion of the network where the system has been configured for ring protection on a DS1 level. Radio Ring wrapping using Eclipse Ring Protection. • Verify that the microwave equipment has been configured for ring protection as per the design documentation. • Connect the BER tester to the DS1 under test and verify continuity and absence of errors in one direction. • Create an alarm on the working channel and verify that the software switches the DS1 traffic to the protected channel. • Clear the alarm on the working channel and verify that the traffic switches back in accordance with the restore time settings in the radio configuration. • Restore configuration to the original settings once completed. 3.4.2. Network Continuity Test Use the following instructions to perform the Network Continuity Test and record the results in the corresponding fields on the System Test sheet. Note that this test only applies to systems utilizing out -of - band management. For in -band management systems, the test should be done in conjunction with the Ethernet test. Perform Network Continuity Test. • Verify the microwave equipment is configured as per the SOS. • Verify laptop is connected to the NMS ports on the NCC. P25 System and Services Agreement (R1422515R1/P1) Page 8 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Using a DOS prompt, send a ping command to the IP Address of the first radio and note the success reply. • Continue sending ping commands to the remainder of the radios in the network as per the SOS and note the success replies. 3.4.3. Provision Element Management System Test Use the following instructions to verify that the ProVision Element Management System is reporting the new sites correctly after installation. The field testing will include verification of any new OEM equipment alarms. 3.4.3.1. Basic ProVision Element Operation • Start Pro Vision Client software • Log in as admin (password admin). It is recommended that you change the admin password immediately. • Check that ProVision opens and displays the tree, map and event panes correctly. • Deploy a segment of the County's network including sites and Provider devices. • Establish communications with the Provider devices. • Record the embedded software version running on the Provider devices under test. • Ensure that lost communications notification is successful. 3.4.3.2. Functionality Tests • Use the event browser to view, acknowledge, or clear network alarms. Use PreFilters, Event Groups, and Scoreboards. • Use the configuration screen to change device parameters. • Review device hardware inventory data. • Enable 15-minute data collection and review RSSI and G.826 history and performance trends. 3.4.3.3. OEM Alarm Reporting • Use the event browser to view, acknowledge, or clear alarms from each of the DC power systems. 3.4.4. Ethernet Ring Protection (ERP, ITU-T G.8032) Verification Use the following instructions to test the Ethernet protection switching on the loop and record the results in the corresponding fields on the System Test sheet. Measure ERP ring switching time • Log into the appropriate INUe and verify that "Node State" is in idle Show Ethernet ring G.8032 brief • Configure the test sets for packet loss test. • Start the packet loss test. • Simulate a RF link failure by muting the transmitter on the path to South EMS. • Verify switching. "Node State" should be in "Protection". • Show Ethernet ring G.8032 brief. • Calculate the number of lost packets in order to determine the switching time Each lost packet represents 1 msec. • Restore the path and measure the ERP revertive switching time. P25 System and Services Agreement (R1422515R1/P1) Page 9 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.4.5. 24-Hour Main Radio BER Test Use the following instructions to perform a twenty four (24) hour Bit Error Rate (BER) test on the main radio and record the results in the corresponding fields on the System Test sheet. This test should be performed after all the individual radio hops have been tested and the Hop Test Sheet been filled out. In order to perform this test, a DS1 circuit off the INU is selected and physically or electronically patched through at the middle and/or repeater sites to the far end site where the circuit is physically or electronically looped back. Note that no radio configuration should be performed while the BER test is in progress. Perform a twelve (12)-hour BER (Bit Error Rate) Test at the DS1 level on the Main radio end -to -end with the DS1 looped back. • Perform the twelve (12) hour test on the linear spur S-5 - S-33, with the test set at S- 5 and the loopback at S-33. Perform the twelve (12) hour test on the loop S-5 — S-15 — S-11 — S-7 — S-8, with the test set at the S-5 radio to S-15 and the loopback at the S-15 radio continue test on a per hop basis. Both loops would need to have this testing completed Performance Objective: BER not to exceed test objective of N X 10-1o, where "N" is equal to the number of radio hops, (i.e. for a single hop looped at one end, N=2; for two hops looped at one end, N=4, and so on). For the linear spur = 6 x 10-,o For the loop = 1.4 x 10-9 3.4.6. ROUTER TESTING • Verify set-up and test configuration. • Verify IP addresses and IP connectivity by pinging. • Dashboard • Node Manager • OSPF • MPLS • BGP • VPN provisioning tool • L3VPN • Test using INM • Test using external test set (Spirent Smartbits 6000 or JDSU) P25 System and Services Agreement (R1422515R1/P1) Page 10 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.5. Additional Tests 3.5.1 Verify redundant routing via MPLS (in addition to loop protection) • Routing/MPLS Connectivity Test Use the following instructions to validate routing/MPLS connectivity, at each MPLS router, to the adjacent routers (Ping Test) and record the results. - Connect to the router CLI interface - Verify that the network ports are up (east and west directions) - Use the ping command to validate IP connectivity to the loopback IP address of each adjacent router and note the successful reply. Routing/MPLS redundant routing Test Use the following instructions to validate redundant routing to the adjacent routers (Ping Test) and record the results. - Connect to the router CLI interface - Verify that the network ports are up - Shutdown one network port - facing the east direction - Use the ping command to validate IP connectivity to the loopback IP address of each adjacent router and note the successful reply. - Bring up the network port facing the east direction - Wait until the routing table is updated and showing the shortest path to the adjacent router in the east direction - Shutdown the other network port - facing the west direction - Use the ping command to validate IP connectivity to the loopback IP address of each adjacent router and note the successful reply. - Bring up the network port facing the west direction • End to End Service Test Use the following instructions to validate end -to -end redundancy for the VPN service at the site: - Connect an Ethernet test set to the VPN port at the local site - Connect an Ethernet test set to the VPN port at the remote end (prime or master site) - Run an IP traffic stream in each direction. Verify that the traffic flow is error free - Connect to the router CLI interface - Check which network port is carrying traffic to the remote end (via the routing table or using the network port interface statistics) - Shutdown one network port - facing the east direction - Validate that the test set traffic continues to pass in both directions after a brief interruption - Measure and record service down time. - Bring up the network port facing the east direction - Wait until the routing table is updated and showing the shortest path to the adjacent router in the east direction - Validate that the test set traffic continues to pass in both directions P25 System and Services Agreement (R1422515R1/P1) Page 11 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.5.2 Verify T1 interface and throughput Note: T1 Circuits are Native T1's and will have a native T1 throughput of 1.544 Mbps as seen on the T1 Test Set. Interface and Throughput verified during the following test. Use the following instructions to perform a one (1) hour Bit Error Rate (BER) test on the main radio and a one (1) hour BER test on the standby radio, if equipped, and record the results in the corresponding fields on the Hop Test sheet. This test should be performed after the final alignment of the antennas for each hop. DS1 #28 must be configured as a test circuit for each path. The far end should be placed in loopback. After testing, leave the DS1 circuit programmed for use in the system level BER test. No radio configuration should be performed while the BER test is in progress. One (1) hour Bit Error Rate (BER) Test on Main radio. Verify the microwave equipment is configured as per the SOS, SBD and DS1 plan. Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. Perform a one (1) hour BER test at the DS1 level for the provisioned DS1. Performance objective: 1x10-10 BER one-way, under no fade conditions. One (1) hour Bit Error Rate (BER) Test on the standby radio. Verify the microwave equipment is configured as per the SOS, SBD and DS1 plan. Connect the BER tester to a DS1 port looped back at the far end site and check DS1 continuity and absence of errors. Verify that radio traffic has been switched to the standby radio and that the main radio is offline. Perform a one (1) hour BER test at the DS1 level for the provisioned DS1. Performance objective: 1x10-10 BER one-way, under no fade conditions. 3.5.3 Verify proper operation of Vol Phone Use the following instructions to test the site -to -site calling functionality of the IP Phone for each microwave hop and record the results in the corresponding fields on the Hop Test sheet. P25 System and Services Agreement (R1422515R1/P1) Page 12 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Verify IP Phone site -to -site calling. Verify that the IP Phone is configured as per the manufacturers recommended configuration instructions and that the phone is connected to the microwave equipment as per the System Block Diagram (SBD). Verify that the IP Phone powers up on boot up of the microwave equipment. If an external wall power supply has been provided, verify that the phone is powered up before the radio boot up. On the first IP phone, dial the second IP phone by its IP address. A ring tone should be heard from the dialed phone. A second person is to answer the ringing IP phone and ensure clear two way conversations is possible. Hang up both ends to end the call. Repeat the procedure in the opposite direction. 3.5.4 Verify power failures to any component in system (Ethernet, T1, 4wire)_ Power protection switching is hitless. Ensure that the Eclipse INU is powered up. Ensure that the NCC and NPC Status LED are green. The NPC Protect LED should be unlit. Disconnect the -48Vdc supply from the NCC and remove the NCC card from the chassis. Eclipse should not lose power. Power is now provided by the NPC. The NPC Protect LED should now be lit. Re-insert the NCC card and power to the NCC. 3.5.5 Verify continuous operation with failure to any module (Ethernet, T1, 4wire)_ VERIFY PROTECTION SWITCHING. Using Portal mute on-line transmitter or switch to off-line transmitter. Observe switching to the other transmitter. Restore to normal operation. Using Portal, switch to off-line RAC. Observe switching to the other receiver. Using Portal, switch to off-line DAC. Observe switching to the other receiver. Restore to normal operation. Using Portal, switch from Primary to Secondary "Rx Source Lock". P25 System and Services Agreement (R1422515R1/P1) Page 13 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Verify that traffic did not take hit during this process. Using Portal, switch from Secondary to Primary "Rx Source Lock". Verify that traffic did not take hit during this process. Turn off NPC and observe that INU operates on NCC only Turn on NPC. Verify that INU operates on NCC and NPC Turn off NCC and observe that INU operates on NPC only, with no reset or power -off Turn on NCC. TEST EQUIPMENT: BER TESTER REQUIREMENT: Traffic continuity after switching occurs. 3.5.6 Testing of radio traffic running across links for all tests Microwave traffic is tested end -to -end through the MPLS routers or T1 circuits to test the Motorola demarcation. Additional testing is conducted on the microwave network via Motorola's testing of the P25 radios. The Microwave Radio traffic is tested during T1, Ethernet, and MPLS Testing Procedures as outlined. 3.5.1 Testing of radio running over T1 links Testing of the T1 circuits on the microwave link will be executed using the Larus loop switch. The Larus Loop Switch will provide the ability to cut -over half the protected circuit without impacting active traffic. While temporarily decommissioning the primary circuit, traffic will remain active on the protected circuit until the primary is restored on the new microwave equipment. At that time the payload can be restored on the Larus to the primary circuit (now on the new microwave network) with the redundant circuit following migration after primary circuit has been functional for a sufficient period of time. The Microwave Radio traffic is tested during T1, Ethernet, and MPLS Testing Procedures as outlined. P25 System and Services Agreement (R1422515R1/P1) Page 14 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 FIELD ACCEPTANCE After all field testing has been successfully completed (including resolution of any punch list items to the reasonable satisfaction of County) and the required test documents have been signed and dated, the Provider Representative and the County Contract Administrator will complete, sign and date the FIELD ACCEPTANCE TEST COMPLETION REPORT enclosed in this document. All punchlist items must be resolved to County's satisfaction prior to sign -off of the system. FIELD TEST DATA FORMS Test Data forms follow. P25 System and Services Agreement (R1422515R1/P1) Page 15 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Station Test Sheet er: Customer; Customer i0icrovvave Sys ter- R-3p'a ement Site me: Lac -.7- Fac ing Site: Bite 2 - S it c S :v 1= t Radio #: ® #1 ® 42 ® #3 ® #4 3.2.1 Grounding Inspection 3.2.1.- Gl'-OLI-I l Con#in_. #, -9.-A - _ :::.ail I"...4 '.2.1.2 Rt.v Gr-au.-J 1-:1 :: ~ : I. Criteria Measured F'aSs =ail 3.2.2 Equlipmedlt InsJ)ection '..2.2.1 Inventory Check = :::.ail I"...4 3.2.2.2 ;f.sual Inspection of Antennas sna `. avequ.ae on to, -.+per - 3.2.2.3 Visual Inspection of VWavegulide?Coax rousting ins kde equipment shelter P a S s =a I... 4. ..2.2.4 Visual Inspection of Rack Pass = it .=.2.5 {seal Irsoection of Rack Breakers Pass = it I... 4. 3.2.2.E j Visual IIISPa:t Cl- v- -- _. -.u. :::.ail I -...A ow e r Sy stem I est 3. Rack Installation Inspection Pass II I... A _.:2 AC Input Voltage Calculated Measured as -31 AC Input Breakers Pass - II I... 4. DC Float Voltage cu ate easure ass 311 volt DO Float Voltage compared to Charge Display Measured LispJay a s s7 Fa—i C Current Lead C-a I cul I ate: Measured mp Load Transfer from C hargerto Batteries and back to Charger Pass C41 I... A Char€JerAlarms Connected to Alarm Block rasa = it I... A Battery Cell voltages Cell # 1 Cell #2 Cell #3 Cell #4 Cell #5 Cell#6 Cell#7 Cell #5 Cell#9 Calculate:: .l F'aSs =ail %.!c. t %.!c. t %.!c. t %.!c. t %.!c. t :c't :c't .; c. t .'ot P25 System and Services Agreement (R1422515R1/P1) Page 16 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 COMMENTS: PROVIDER REPRESENTATIVE COUNTY REPRESENTATIVE Signed: Signed: Name: Name: Title: Title: Date: Date: P25 System and Services Agreement (R1422515R1/P1) Page 17 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Hop 1 Test Sheet County: County/County Project: Microwave System Replacement Site Name: S-5 Facing Site: Site 2 Rack #: Al Radio #: ® #1 ❑ #2 ❑ #3 3.3.1 Microwave Equipment Test 3.3.1.1 INU Redundancy Pass Fail N/A 3.3.1.2 INU IP Address Configuration as per NMS Plan and SOS Pass Fail N/A 3.3.1.3 Firmware Versions INU RFU/ODU RFU/ODU Main: Diversity: 3.3.1.4 ACU Insertion Loss ACU Tx Main: dB Tx Diversity: dB Rx Main: dB Rx Diversity: dB 3.3.2 IRU Transmit Power Output Test Tx Power Output Spec Measured Portal Main: dB Diversity: dB 3.3.3 IRU Receive Signal Level Test RSL Calculated Measured Portal Main: dB Standby: dB 3.3.4 IRU Receiver Threshold (Fade Margin) and Interference Test 3.3.4.1 Rx Threshold Spec Measured Portal Main: dB Standby: dB 3.3.4.2 Interference Spec Measured Portal Main dBm 3.3.5 Transmitter/Receiver Switching Test 3.3.5.1 Transmitter Switching Pass Fail N/A 3.3.5.2 Receiver Switching Pass Fail N/A 3.3.6 Ethernet Test 3.3.6.1 RFC2544 Throughput Test Frame Size (Bytes) Throughput (Mbps) Error Free (Y/N) 64 1518 3.3.6.2 RFC2544 Latency Test Frame Size (Bytes) Latency (ms) Method (SaF/BF) 64 1518 P25 System and Services Agreement (R1422515R1/P1) Page 18 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.3.6.3 RFC 2544/1242 Frame Loss Test Frame Size (Bytes) Rates N Frame Loss (%) 100 90 80 70 60 50 40 30 20 10 3.3.7 AUX Alarm/Data Card Test AUX Alarm Test Pass Fail N/A 3.3.8 One (1) Hour BER Test 3.3.8.1 One (1) Hour BER Test on Main Radio Calculated Measured Pass/Fail >1x10-10 dB 3.3.8.2 One (1) Hour BER Test on Standby Radio Calculated Measured Pass/Fail >1x10-10 dB PROVIDER REPRESENTATIVE COUNTY REPRESENTATIVE Signed: Signed: Name: Name: Title: Title: Date: Date: P25 System and Services Agreement (R1422515R1/P1) Page 19 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Provider Field Acceptance Test Completion Report County: County Project: Microwave System Comments (if any): (Use additional sheets if required) ADDITIONAL COMMENTS: PROVIDER REPRESENTATIVE COUNTY REPRESENTATIVE Signed: Signed: Name: Name: Title: Title: Date: Date: P25 System and Services Agreement (R1422515R1/P1) Page 20 of 20 Field Acceptance Test Plan DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SOW A-2 Facilities and Infrastructure Development SECTION 1 OVERVIEW Unless otherwise approved by the Contract Administrator in writing, eight of the County's ten existing tower sites will be utilized for the new Systems, and seven additional tower sites will be added by Provider to improve coverage. Provider is responsible for and will provide all necessary civil work to upgrade existing towers and support facilities, as well as to develop new radio sites and towers for the expanded network. Provider's solution for the County's radio system includes a comprehensive scope of work, repeatable methodology, and experienced subcontractors to avoid unexpected costs and to implement Motorola Solutions' best -in -class site design. Motorola shall ensure that all services and work provided under this SOW A-2 comply with all of the requirements, standards, and specifications set forth herein. Unless otherwise agreed by the Parties in writing, County shall issue separate Notices to Proceed for each of the following stages of each Site: (1) Design, (2) Permitting, and (3) Construction. Motorola shall not commence the applicable work at any Site without the applicable Notice to Proceed. 1.1 General A. Provider shall be responsible for all required permitting, environmental/historical filings, FAA/FCC filings, and any other steps necessary to provide a "turnkey" solution for the development of all radio site facilities and infrastructure. B. For the Final Design as referenced in A-1, the Provider shall provide detailed drawings including all structures and foundations, sealed by the DB-Firm Consultant, who must be a professional engineer licensed in the State of Florida. 1. Motorola shall provide detailed drawings containing dimensions in native file format and PDF, which show all system components and locations. 2. Motorola shall provide drawings and specifications that shall describe all auxiliary equipment. 3. Manufacturer slick sheets of all equipment used also shall be provided. C. Code Compliance: Motorola shall perform the following: 1. Installation of all electrical equipment, power distribution, lighting assemblies, and associated wiring shall comply with the most recent edition of the NEC and P25 System and Services Agreement (R1422515R1/P1) Page 1 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Occupational Safety and Health Administration (OSHA) regulations. 2. All electrical equipment shall be listed or approved by Underwriters Laboratories (UQ. 3. Provider shall comply with all codes and industry best practices and guidelines stipulated in Section 1.8.1, Standards and Guidelines. D. Provider shall assume total responsibility for maintaining liability insurance covering the following items: 1. Project design 2. Implementation 3. Licenses 4. Shipping 5. Receiving 6. All required site work 7. Any other items required for Provider or any subcontractors E. Prior to any excavations, Provider and its subcontractors shall follow the applicable procedures outlined at the following website: www.sunshine8ll.com. F. Provider will coordinate with the applicable utility companies for all utility -related items, such as electrical service hookups and disconnects. G. Concrete: 1. For all foundations and concrete work, Provider shall provide to the DB-Firm Consultant a test sample of each mix of concrete demonstrating that it has been tested for compliance with the foundation specifications set forth by the requisite Facilities and Infrastructure engineer. Provider shall provide written reports certifying the strength of the concrete with each test cylinder. 2. If any concrete used in the foundation does not meet specifications, Provider shall remove the foundation and pour a new foundation using compliant materials and utilizing the test sample procedure identified above in G.1, at no expense to the County. 1.2 Towers. Provider shall be responsible for the following, unless otherwise expressly stated: A. General: P25 System and Services Agreement (R1422515R1/P1) Page 2 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1. If it is determined that additional towers are required or existing towers must be replaced or modified, Provider shall update the proposed solutions during the negotiation period. 2. Provider shall guarantee the structural integrity of all towers utilized for the System for a period of not less than 20 years from the date of Final Acceptance. B. Tower Loading: 1. The tower and foundation shall be designed for all proposed equipment, legacy equipment, appurtenances, ancillary equipment, and initial antenna loading plus 50 percent future antenna system growth, without addition to or modification of the finished tower or foundation. 2. The tower structures shall be designed and installed in accordance with latest revision of the ANSI/EIA-222 standard. C. Towers shall include the following: 1. Ice Bridge — A 24-inch, open mesh -type horizontal transmission line ice bridge, extending from the tower cable ladder to the equipment building, including 24 four - inch -diameter line entry ports shall be provided. 2. Transmission Line Support — A vertical transmission line support system shall be provided to securely attach the antenna transmission lines. Holes shall be provided in the tower support members, tower hanger adapter plates, or separate ladder structures to allow installation of bolt -in cable hangers at maximum 3-foot intervals. The mounting holes shall be precision punched or drilled and sufficiently separated to accommodate the snap -in or bolt -in hangers. 3. Climbing Access —A ladder, beginning at a point at least ten feet off the ground, shall be provided as an integral part of the tower to permit access by authorized personnel. The tower shall be equipped with an OSHA -approved anti -fall safety device in accordance with ANSI/EIA-222. This device must not interfere with the climber's ease of reach by hand or foot from one rung of the ladder to the next, either going up or coming down. Two safety climbing belts shall be supplied with each new tower. 4. Lighting: a. Tower lighting shall be supplied as required by the applicable determination as issued by the FAA for this project and fully compliant with FAA AC 70/7460-1K, latest revision. P25 System and Services Agreement (R1422515R1/P1) Page 3 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 b. Tower lights shall be LED -based where permitted by the FAA. c. The system control circuitry shall provide synchronization and intensity control of the obstruction lighting system, and shall monitor the overall integrity of the lighting system for component failures or improper operation. d. Provider shall wire all alarms to the provided Type 66 block located in the communications shelter or equipment room. All alarms shall be clearly labeled. 5. A lightning ground rod shall be installed at the very top of the tower to extend at least 2 feet above the top of the tower or lighting fixture. 6. Labeling shall be clearly provided near the base of all new towers for the following: a. Make b. Model c. Serial number d. Tower height e. Latitude and longitude f. FAA and FCC identification numbers (if applicable) D. Construction: 1. All welding must be done in the factory prior to the galvanizing process. Field welding is not acceptable. 2. The tower shall be constructed of high -strength steel. All components and hardware shall be hot -dip galvanized with a zinc coating after fabrication, per EIA standards. A zinc coating shall be permanently fused to the steel, both inside and outside, so that all surfaces are protected and no painting is required for rust protection. 3. Prior to galvanization, each piece of steel and every weld must be deburred and smooth -finished. E. Final Testing and Acceptance — Upon completion of the work, documentation detailing final inspection and testing shall be submitted, documenting the following: 1. Steel structure: a. Vertical alignment and plumbness b. All bolts tight and torqued to specification c. No damaged or missing structural members d. All surface scratches and damage to the galvanization repaired e. No signs of stress or vibration f. All climbing ladders and other devices installed correctly P25 System and Services Agreement (R1422515R1/P1) Page 4 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 g. Labels and tags 2. Foundation: a. Concrete finish needs to exhibit no cracks or blemishes b. Grouting, if used, shall have drain holes if the tower uses hollow leg construction or monopole design c. Backfilling and grading shall be conducted 3. Grounding —Shall meet applicable standards such as Motorola R56, Grounding Guidelines; items include, but are not limited to: a. Verify lugs and exothermic welds b. Test and record ground resistance c. Install lightning ground rod at top of tower 4. Ice Bridge — Install per tower manufacturer specifications 5. Lighting and controls: a. Inspect conduit and wiring installation and correct if necessary b. Verify proper lamp operation and correct if necessary c. Verify alarm contact operation and correct if necessary d. Verify labeling and correct if necessary 6. Photographs — Motorola shall furnish photographs to the County for the final configuration of the following prior to system acceptance: a. Overall structure from north, east, south, and west b. Footers c. Grounding 1.3 Shelters. Provider shall provide all of the following, unless otherwise expressly stated: A. General: 1. Shelters shall be prefabricated and preassembled. The shelter can be constructed from concrete. P25 System and Services Agreement (R1422515R1/P1) Page 5 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 B. Size: 1. Shelter dimensions shall correspond with the Final Design. 2. Minimum shelter size shall be 12 feet x 30 feet, with a minimum interior height of 9 feet. C. Foundation — The foundation for the shelter shall consist of concrete piers or a poured concrete slab constructed by Provider that will properly support and secure the shelter. Foundation drawings recommended by the shelter manufacturer shall be the criteria by which the foundation is constructed. D. Flooring: 1. Provider shall ensure that each structure has a floor or solid foundation that features a minimum uniform load rating of 200 pounds per square foot with no more than 3,000 pounds over any 4-square-foot area. This rating shall be increased in sections as necessary to support heavyweight equipment, including the requested DC power supply. If the shelter is delivered with the floor already assembled, the floor shall exhibit a minimum 90-pounds-per-square-foot, uniform live -load capacity while the building is being lifted. 2. Floors shall be insulated to a minimum R-11 rating. Insulation shall be secured in place to prevent shifting during construction and transportation. 3. Exterior covering of the floor shall be included to prevent rodent infestation. 4. The floor shall be covered by a high -quality, industrial- or commercial -grade asphalt or vinyl tile. All edges shall be covered by wall molding. E. Walls: 1. Walls shall be constructed to a minimum 160-mile-per-hour (MPH) wind -load rating, including overturning moments. 2. Bullet Proof — Walls shall withstand the effects of bullets or other projectiles equivalent to a .30-06 high -power rifle load fired from a distance of 50 feet with no penetration to the inner cavity of the wall and with no interior damage sustained including, without limitation, to insulation, interior walls, or any interior equipment or portions of the structure. 3. The outside walls shall be finished with concrete or an aggregate composition. P25 System and Services Agreement (R1422515R1/P1) Page 6 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4. A wall feed -through bushing with 24 four -inch -diameter openings shall be provided on the tower side of the building to accommodate elliptical waveguide and coaxial transmission lines. The openings shall be properly booted to provide a good weather seal. The wall feed -through bushing shall be bonded to the site ground system per guidelines specified in Section 1.8.1, Standards and Guidelines. 5. The inside walls shall be finished with minimum 5/8-inch plywood (or equivalent) to allow mounting of panels, blocks, etc., and shall be trimmed with coordinated molding. 6. High-performance insulation shall provide a minimum insulation factor of R-11. F. Roof: 1. The shelter roof shall support a minimum 100-pounds-per-square-foot uniform live load. 2. The roof shall be pitched to facilitate run-off of water. 3. The roof shall be sufficient to withstand the impact of ice falling from the adjacent tower without suffering any damage and provide 150 PSF loading. 4. High-performance insulation shall provide a minimum insulation factor of R-19. G. Door: 1. The shelter shall have one 42-inch x 84-inch insulated door, with three stainless - steel, tamper -proof hinges, passage -style lever handle, deadbolt lockset, and fiberglass weather hood or awning. The door shall be equipped with a hydraulic door closer. 2. The exterior door shall be of aluminum or steel (stainless or galvanized) construction with a finish to match the building finish. 3. The door shall be sufficient to withstand the effects of bullets or other projectiles equivalent to a .30-06 high -power rifle load fired from a distance of 50 feet with no penetration to the inner cavity of the door and with no damage to the interior including, without limitation, insulation, interior walls, and any interior equipment or contents. 4. The door sill shall be of stepped construction so as to prevent rain water from entering the shelter at the bottom of the door or from around the door frame. The door frame shall have a weather seal around the door to limit air and water intrusion. P25 System and Services Agreement (R1422515R1/P1) Page 7 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 H. Finishing: 1. The interior and exterior finishes shall be described by the Vendor. Color and finishes shall be selected by the County. 2. All joints shall be sealed with a compressible, resilient sealant. I. Alternating Current (AC) Power System: 1. Provider shall deliver the building complete with a 400-ampere-capacity, 240-volt, single-phase electrical panel box with a ground bar. 2. This panel shall be equipped with a 200-ampere-capacity main circuit breaker used to supply power for all electrical functions related to the site. 3. Overall panel size shall be determined by the need to provide the number of individual breakers required, plus a reserve of at least six 240-volt slots. 4. Breakers for shelter air-conditioning shall be of the bolt -down, not snap -in, type. 5. Receptacles: a. Receptacles shall meet current Motorola R56 standards, or Harris AEA-123 4618/1, Grounding Guidelines, or equivalent. b. Each radio equipment unit (or rack) shall be supplied with two 20-ampere circuits, each terminated at a typical NEMA 20-ampere, twist -lock receptacle. Receptacles shall be mounted to the side of the overhead cable tray. c. Service receptacles shall be mounted on the walls at 6-foot intervals or less. d. One weatherproof ground fault interrupter (GFI) exterior power receptacle shall be provided with each shelter, to be mounted near air-conditioning units. e. Each receptacle shall be fed from an individual breaker. The feeding breaker shall be identified at the receptacle and the receptacle shall be identified at the breaker. All breakers or circuits shall be 20-ampere, unless otherwise noted. J. Power Line Surge Suppression: 1. AC surge protection shall be provided and installed inside the shelter. P25 System and Services Agreement (R1422515R1/P1) Page 8 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. An acceptable unit shall be an in -line type such as the AC Data Systems "integrated load center." An alternate unit must meet or exceed all of the capabilities of this model unit. 3. Minimum surge protector requirements: a. Built-in redundancy of dual stages per phase with filtering b. Surge energy shunted to ground, not to neutral c. Front panel indicator lamps d. Remote/local status contacts e. Fusible link protected so as not to interrupt power f. Field replacement protection blocks and fuses, if needed g. UL-Listed components h. 45 kiloampere (kA) per phase, ANSI C62.1 8/20 waveform i. Electromagnetic interference/radio frequency interference (EMI/RFI) filtering per M I L-STD-220 j. Capable of handling the full 240-volt, 200-ampere capacity of the electrical system K. Wiring Methods: 1. Shall meet all applicable local, state, and national standards. 2. All wiring noted on the site drawings or otherwise included by Provider shall be installed in conduit or ductwork. Where no protection method is specified, conduit shall be used. 3. All conduits and ducts shall be securely surface -mounted and supported by approved clamps, brackets, or straps as applicable, and held in place with properly selected screws. No wiring shall be imbedded inside any walls, floors or ceilings. Entrance power, outside light, air-conditioning outlet, and telecommunications company (telco) are the only wiring that may penetrate shelter walls or floor. 4. All wire raceways, conduits, etc., shall be mechanically joined and secured. 5. Flexible steel conduit or armored cable shall protect wiring connected to motors, fans, etc., and other short runs where rigid conduit is not practical. 6. Unless otherwise specified, all power wiring shall be minimum 12 American wire gauge (AWG) size, solid copper conductors with insulation rated for 600 volts AC. P25 System and Services Agreement (R1422515R1/131) Page 9 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 L. Light Fixtures: 1. Ceiling -mounted, 4-foot fluorescent light fixtures (two 40-watt bulbs per fixture) with RFI ballasts shall be supplied for the equipment shelters. A sufficient quantity of light fixtures shall be supplied to provide a uniform light level throughout the building of 150 foot candles at four feet above the floor. 2. Light fixtures shall be fed as a gang from a common breaker and controlled by an on/off switch near the door. M. Outdoor Lighting: 1. An exterior 100-watt, wall -mounted light shall be mounted on the front entrance of the shelter. 2. The exterior lighting system shall be fed from a separate, appropriately rated breaker and controlled by an on/off switch mounted near the door. N. Heating, Ventilation and Air -Conditioning (HVAQ 1. Provider shall provide an HVAC system for each shelter, which system will include dual AC units with a lead -lag controller. Each AC unit shall be sized for 100 percent of the building's required cooling capacity, as determined by the British thermal unit (BTU) analysis. 2. Provider shall perform a BTU analysis (heat -load calculations) for all shelter equipment during preliminary design to verify HVAC system size. All calculations shall include a 50-percent expansion factor, and all assumptions regarding power consumption, duty factor, and heat loading shall be thoroughly explained. Provider shall ensure that each shelter's HVAC system has all needed additional capacity. 3. Each unit shall be capable of maintaining an inside ambient temperature range between 65 and 85 degrees Fahrenheit (F). Each unit shall be sized to maintain temperatures inside the shelter at 70 degrees F. 4. The HVAC system shall be controlled by a wall -mounted thermostat. The thermostat shall turn the heater on when the temperature inside the shelter drops to 65 degrees F and off when it rises to 68 degrees F. It shall turn on the air -conditioner when the interior temperature reaches 78 degrees F and off when the temperature drops below 75 degrees F. Thermostat control shall be adjustable within the range of 45 to 85 degrees F. O. Antenna Cable Conduit Entry — Provider shall supply a bulkhead panel to accommodate coaxial transmission lines between 1/2-inch and 1 5/8-inch diameter elliptical P25 System and Services Agreement (R1422515R1/P1) Page 10 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 waveguides. A minimum of 12 transmission lines shall be accommodated with 4-inch openings. The building manufacturer shall seal the conduits into the wall to assure that they are watertight. P. Cable Tray — All new shelters shall be equipped with the cable trays. Provider shall install a minimum 18-inch-wide cable tray system above the equipment. Q. Shelters shall be supplied by Provider with at least one 10-pound carbon dioxide (CO2) fire extinguisher, an approved eyewash station, and a first -aid kit. 1.4 Generator and Automatic Transfer Switch (ATS) This section provides the specifications and requirements for standby power systems to supply electrical power in the event that the normal supply fails. Provider shall provide all necessary equipment and services to ensure that each radio site (new and existing) has power systems that meet all of the requirements stated herein. A. Provider shall provide an emergency generator system at each radio communications site (both new and existing) for backup power. B. Standby power systems shall consist of a liquid -cooled engine, an AC alternator and system controls with all necessary accessories for a complete operating system, including but not limited to the items as specified. C. Provider shall perform electrical -loading analysis for shelter equipment, including HVAC subsystems, during preliminary design to verify generator size and fuel -tank capacity. All electrical -loading calculations shall include a 50-percent expansion factor, and all assumptions regarding power consumption and duty factor shall be thoroughly explained. D. In the event of a commercial power outage, the emergency generator shall provide power to the entire shelter without a system outage. E. Quality Assurance —The standby power system shall be supplied by a manufacturer that is currently and has been regularly engaged in the production of engine -alternator sets, ATS, and associated controls for the past ten years, thereby identifying one source of supply and responsibility. F. The generator system and all accessories and ancillary equipment shall comply with the following standards: 1. NFPA 37, Flammable and Combustible Liquids Code 2. NFPA 55, Standard for the Storage and Handling of Compressed Gases 3. NFPA 70, National Electrical Code, with particular attention to Article 700, "Emergency Systems" 4. NFPA 110, Requirements for Level 1 Emergency Power Supply System 5. NFPA 101, Code for Safety to Life From Fire in Buildings and Structures P25 System and Services Agreement (R1422515R1/P1) Page 11 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. ANSI/NEMA MG 1, Motor and Generators 7. ANSI/NEMA AB 1, Molded Case Circuit Breakers 8. ANSI/NEMA 250, Enclosures for Electrical Equipment (1,000 Volts Maximum) G. Labeling and Identification —All wiring harnesses and connectors shall be clearly identified by number and function according to the associated schematic diagrams and documentation provided by Provider. H. Factory Testing: 1. Before shipment of the equipment, the generator set shall be tested under rated load for performance and proper functioning of control and interfacing circuits. Tests shall include: a. Verification that all safety shutdowns are functioning properly b. Verification of single-step load pick-up per NFPA 110-1996, paragraph 5-13.2.6 c. Verification of transient and voltage -dip responses and steady-state voltage and speed (frequency) checks d. Full load test for a minimum of one hour 2. Provider shall provide complete report(s) of all testing performed. Startup and Checkout: 1. Motorola's subcontractor providing the electricity -generating plant and associated items covered herein shall provide factory -trained technicians to check the completed installation and to perform an initial startup inspection to include: a. Ensuring that the engine starts (both hot and cold) within the specified timeframe. b. Verifying that engine parameters are within specification. c. Verification of no-load frequency and voltage adjustment, if required. d. Testing of all generator automatic shutdowns. e. Performing a simulation of power failure to test generator startup and the ability of the ATS to pick up building load correctly. f. Returning to commercial power and testing the generator and ATS to demonstrate correct cycling to normal commercial power. P25 System and Services Agreement (R1422515R1/P1) Page 12 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 g. Performing a load test of the generator, to ensure full -load frequency and voltage is within specification when using building load. This test shall be run for a minimum of one hour. h. Testing and verifying all remote indicators and controls. 2. Provider shall provide complete report(s) of all testing performed. 1.4.1 Diesel Generator A. Provider shall supply a Diesel Generator system at each new radio site and at the County's existing Markham Park, Davie, and Miramar locations. B. The prime mover shall be a liquid -cooled, diesel engine. C. The engine shall have a sufficient horsepower rating to drive the generator to full output power without a gear box between the engine and generator. D. The engine shall have a battery -charging DC alternator with a solid-state voltage regulator. E. The generator shall meet temperature -rise standards for Class "H" insulation, operating within Class "F" standards for extended life. F. The alternator shall have internal thermal -overload protection and an automatic reset field circuit breaker. G. One-step load acceptance shall be 100 percent of the generator set nameplate rating, and shall meet the requirements of NFPA 110, paragraph 5-13.2.6. H. The electricity -generating plant shall be mounted with vibration isolators on a welded - steel base that shall permit suitable mounting to any level surface. I. A main -line -output circuit breaker carrying the UL mark shall be factory installed. 1. Form C auxiliary contacts rated at 250-volt AC/10 amps shall be provided to allow remote sensing of the breaker status. 2. A system utilizing manual -reset field circuit breakers and current transformers is unacceptable. J. An alternator strip heater shall be installed to prevent moisture condensation from forming on the alternator windings. P25 System and Services Agreement (R1422515R1/P1) Page 13 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 K. Controls: 1. All engine alternator controls and instrumentation shall be designed, built, wired, tested and shock -mounted in a NEMA 1 enclosure mounted to the generator set by the manufacturer. It shall contain panel lighting, a fused DC circuit to protect the controls and a +/- 5 percent voltage -adjusting control. 2. The generator set shall contain a complete 2-wire automatic engine start -stop control that starts the engine on closing contacts and stops the engine on opening contacts. 3. A programmable cyclic cranking limiter shall be provided to open the starting circuit after four attempts if the engine has not started within that time. Engine control modules must be solid-state plug-in type for high reliability and easy service. 4. The panel shall include: a. Analog meters to monitor i) AC voltage ii) AC current iii) AC frequency b. A phase selector switch c. Emergency stop switch d. Audible alarm e. Battery charger fuse f. Programmable engine control g. Monitoring module 5. The programmable module shall include: a. Manual on/off/auto switch b. Four LED status lights to indicate i) Not in Auto ii) Alarm Active iii) Generator Running iv) Generator Ready 6. The module shall display all pertinent unit parameters including: a. Generator Status — on/off/auto b. Instrumentation — Real-time readouts of the following engine and alternator analog values: i) Oil pressure P25 System and Services Agreement (R1422515R1/P1) Page 14 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ii) Coolant temperature iii) Fuel level iv) DC battery voltage v) Run-time hours c. Alarm Status: i) High or low AC voltage ii) High or low battery voltage iii) High or low frequency iv) High or low oil pressure v) Low water level vi) High or low water temperature vii) High and pre -high engine temperature viii) High, low and critical -low fuel levels (where applicable) ix) Over crank x) Over speed xi) Unit not in automatic mode L. Unit Accessories: 1. Weather -protective enclosure: a. The generator set shall be factory enclosed in a heavy -gauge steel enclosure constructed with 12-gauge corner posts, uprights and headers. b. The enclosure shall be coated with electrostatically applied powder paint, baked and finished to manufacturer's specifications. c. The enclosure shall have large, hinged doors to allow access to the engine, alternator and control panel. 2. The exhaust silencer(s) shall be provided of at least the size recommended by the generator manufacturer and shall be of critical grade. 3. The generator set shall include an automatic dual -rate battery charger manufactured by the generator set supplier. The battery charger shall be factory installed on the generator set. Due to line voltage drop concerns, a battery charger mounted in the transfer switch is unacceptable. 4. A heavy-duty, lead -acid, 12-volt DC battery shall be provided by the generator set manufacturer. The generator set shall have a frame suitable for mounting the battery and include all connecting battery cables. P25 System and Services Agreement (R1422515R1/P1) Page 15 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.4.2 Automatic Transfer Switch A. Motorola shall install a transfer switch at each new location, and replace transfer switches at existing sites if necessary to maintain compatibility with the site generator. B. The ATS shall be compatible with the generator set so as to maintain system compatibility and local service responsibility for the complete emergency power system. C. Representative production samples of the ATS supplied shall have demonstrated through tests the ability to withstand at least 10,000 mechanical operation cycles. One operation cycle is defined as the electrically operated transfer from normal to emergency and back to normal. D. Wiring must comply with NEC table 373-6(b). The manufacturer shall furnish schematic and wiring diagrams for the particular ATS proposed and a typical wiring diagram for the entire system. E. Ratings and Performance: 1. The ATS shall be adequately sized to match the generator and shelter electrical systems. 2. The ATS shall be a 2-pole design rated for 600-volt AC, 200-amperes continuous operation in ambient temperatures of -20 degrees F (-29 degrees Celsius) to +140 degrees F (+60 degrees Celsius). 3. The operating mechanism shall be a single operating coil design, electrically operated and mechanically held in position. 4. A provision shall be supplied to be able to manually operate the switch in the event of logic or electrical coil failure. F. Controls: 1. A solid-state under -voltage sensor shall monitor all phases of the normal source and provide adjustable ranges for field adjustments for specific application needs. a. Pick-up and drop -out settings shall be adjustable from a minimum of 70 percent to a maximum of 95 percent of nominal voltage. b. A utility -sensing interface shall be used, stepping down system voltage of 120/240-volt AC 1 phase to 24-volt AC, helping to protect the printed circuit board from voltage spikes and increasing personnel safety when troubleshooting. P25 System and Services Agreement (R1422515R1/P1) Page 16 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Controls shall signal the generator set to start in the event of a power interruption. a. A solid-state time delay start, adjustable from 0.1 to 10 seconds, shall delay this signal to avoid nuisance start-ups on momentary voltage dips or power outages. 3. Controls shall transfer the load to the generator set after it reaches proper voltage. a. Adjustable from 70-90 percent of system voltage. b. Adjustable from 80-90 percent of system frequency. c. A solid-state time delay, adjustable from 5 seconds to 3 minutes, shall delay this transfer to allow the generator to warm up before application of load. There shall be a switch to bypass this warm-up timer when immediate transfer is required. 4. Controls shall retransfer the load to the line after normal power restoration. a. A return -to -utility timer, adjustable from 1 to 30 minutes, shall delay this transfer to avoid short-term normal power restoration. 5. The operating power for transfer and retransfer shall be obtained from the source to which the load is being transferred. 6. Controls shall signal the generator to stop after the load retransfers to normal. a. A solid-state engine cool -down timer, adjustable from 1 to 30 minutes, shall permit the engine to run unloaded to cool down before shutdown. b. Should the utility power fail during this time, the switch shall immediately transfer back to the generator. 7. The transfer switch shall have a time -delay -neutral feature to provide a time delay, adjustable from 0.1 to 10 seconds, during the transfer in either direction, during which time the load is isolated from both power sources. This allows residual voltage components of motors or other inductive loads (such as transformers) to decay before completing the switching cycle. 8. A switch shall be provided to bypass all transition features when immediate transfer is required. P25 System and Services Agreement (R1422515R1/P1) Page 17 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 9. The transfer switch shall have an in -phase monitor, which allows the switch to transfer between live sources if their voltage waveforms become synchronous within 20 electrical degrees within 10 seconds of the transfer -initiation signal. If the in -phase monitor will not allow such a transfer, the control must default to time -delay -neutral operation. 10. Front -mounted controls shall include a selector switch to provide for a NORMAL TEST mode with full use of time delays; FAST TEST mode that bypasses all time delays to allow for testing the entire system in less than one minute; or AUTOMATIC mode to set the system for normal operation. a. The controls shall provide bright lamps to indicate the transfer switch position in either UTILITY (white) or EMERGENCY (red). A third lamp is needed to indicate STANDBY OPERATING (amber). These lights must be energized from the utility source or the generator set. b. The controls shall provide a manually operated handle to allow for manual transfer. This handle must be mounted inside the lockable enclosure and accessible only by authorized personnel. c. The controls shall provide a safety disconnect switch to prevent load transfer and automatic engine start while performing maintenance. This switch also shall be used for manual transfer switch operation. d. The controls shall provide LED status lights to give a visual readout of the operating sequence including: i) Utility on ii) Engine warm-up iii) Standby ready iv) Transfer to standby v) In -phase monitor vi) Time delay neutral vii) Return to utility viii) Engine cool down ix) Engine minimum run 1.4.3 Diesel Fuel System A. Provider shall provide a complete fuel system, including without limitation all tanks and all associated piping, valves, controls, and other equipment for each new tower site. Above -ground tanks shall be bullet-proof and housed within a locked enclosure. Tanks shall withstand the effects of bullets or other projectiles equivalent to a .30-06 high- P25 System and Services Agreement (R1422515R1/P1) Page 18 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 power rifle load fired from a distance of 50 feet with no penetration to the inner cavity of the tank and with no interior damage sustained. C. Tank and fuel system components shall be sized to provide a minimum of 72 hours of run time at full load. D. Clear access shall be provided for refueling by a fuel truck of sufficient capacity to provide 100% refueling of the on -site fuel tanks in a single fueling. E. Controls and Monitoring Equipment: 1. Fuel capacity gauge with low -fuel -level alarm contact closure 2. Multi -valve for filling, pressure relief and gauging 1.5 Site Preparation A. The Provider shall perform all appropriate preparations for site improvements, including, at a minimum, the site preparation detailed herein. Work includes, but is not limited to the following: 1. Protecting existing plants and grass to remain 2. Removing existing plants and grass as necessary 3. Clearing and grubbing 4. Stripping and stockpiling topsoil 5. Removing above- and below -grade site improvements 6. Disconnecting, capping or sealing, and removing site utilities 7. Temporary erosion and sedimentation control measures 8. Access road development B. The following Construction Specifications Institute (CSI) standard sections are referenced and incorporated as if fully set forth in this specifications document: 1. Division 1 Section, Temporary Facilities and Controls — for temporary utilities, temporary construction and support facilities, temporary security and protection facilities, and temporary erosion and sedimentation control procedures 2. Division 1 Section, Execution Requirements — for verifying utility locations and for recording field measurements 3. Division 1 Section, Selective Demolition — for partial demolition of buildings or structures undergoing alterations P25 System and Services Agreement (R1422515R1/P1) Page 19 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4. Division 2 Section, Building Demolition —for demolition of buildings, structures, and site improvements 5. Division 2 Section, Tree Protection and Trimming —for protecting trees remaining onsite that are affected by site operations 6. Division 2 Section, Earthwork —for soil materials, excavating, backfilling, and site grading 7. Division 2 Section, Lawns and Grasses — for finish grading including preparing and placing planting soil mixes and testing of topsoil material C. Provider and its subcontractors shall comply with local guidelines for erosion and sedimentation (E&S) control. D. Provider shall carefully examine and study existing conditions, difficulties and utilities affecting execution of work. Later claims for additional compensation due to additional labor, equipment or materials required due to difficulties encountered or underground water conditions will not be considered. E. Provider shall verify that existing plant life to remain and clearing limits are clearly tagged, identified and marked in such a manner as to ensure the safety of said plant life throughout construction operations. F. Protection: 1. Provider shall protect and maintain benchmark, monument, property corner, and other reference points, reestablishing them by Registered Professional Surveyor if disturbed or destroyed, at no cost to the County. 2. Provider shall locate and identify existing utilities that are to remain and protect them from damage, reestablishing them if disturbed or destroyed, at no cost to the County. 3. Provider shall protect trees, plant growth and features to remain as final landscape. Branches or roots of any trees that are to remain shall not be disturbed. Adequate guards, fences, lighting, warning signs and similar items shall be provided and maintained as required. 4. Provider shall install protection such as fencing, boxing of tree trunks, or other measures as approved by the Project Engineer. 5. Provider shall conduct operations with minimum interference to public or private accesses and facilities; maintain ingress and egress at all times; and clean or sweep P25 System and Services Agreement (R1422515R1/P1) Page 20 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 any roadways daily or as required by the governing authority. At such times as deemed necessary by the County, dust control shall be provided by water -sprinkling systems or equipment provided by Provider. 6. Provider shall provide any and all necessary traffic control in accordance with Contract documents, the U.S. Department of Transportation "Manual of Uniform Traffic Control Devices" and the Florida Department of Transportation requirements. G. Clearing: 1. Provider shall clear areas required for access to the site and execution of work. 2. Unless otherwise indicated, Provider shall remove trees, shrubs, grass, other vegetation, improvements, or obstructions interfering with the installation of new construction. Removal includes digging out stumps, roots and root material. Depressions caused by clearing and grubbing operations are to be filled to sub -grade elevation to avoid water pooling. Satisfactory fill material shall be placed in horizontal layers not exceeding 8-inches loose depth, and thoroughly compacted per fill requirements of this section and CSI Division 2-Site Construction -Section 02200. 3. Provider shall remove grass, trees, plant life, stumps and all other construction debris from the site to a location that is suitable for handling such material according to State laws and regulations. H. Demolition — Provider shall remove existing pavement, utilities, curbing and shrubbery as necessary for construction of improvements. I. Topsoil Excavation: 1. Provider shall strip topsoil from areas that are to be filled, excavated, landscaped or regraded to such a depth that it prevents intermingling with underlying subsoil or questionable material. 2. Provider shall stockpile topsoil in storage piles in areas not scheduled for construction, job trailer location or equipment lay -down areas, or where directed by the Project Engineer. Storage piles shall be constructed to freely drain surface water. Storage piles shall be covered as required to prevent windblown dust. Unsuitable soil shall be disposed of as specified for waste material, unless otherwise indicated by the County. Excess topsoil shall be removed from the site by Provider. 3. Final topsoil coatings shall consist of organic soil applied in depth of not less than six inches. Satisfactory topsoil is reasonably free of subsoil, clay lumps, stones and other objects greater than two inches in diameter, as well as weeds, roots and other objectionable material. P25 System and Services Agreement (R1422515R1/P1) Page 21 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 J. Access Roads: 1. To the extent necessary at any Site (including without limitation West Lake Park, West Hollywood, Parkland, Tamarac, Deerfield, and Fire Station 106), Provider shall construct and maintain a 12-foot-wide access road to the perimeter fence gate at new sites. 2. Road beds shall be prepared, rolled and provided with six inches of aggregate base course. 3. Roads shall be graded appropriately for proper drainage and minimal erosion. 1.6 Fencing A. The Provider shall provide, install and maintain chain -link fencing around the perimeter of all new sites. B. Framework: Type I or Type II steel pipe 1. Type I — Schedule 40 steel pipe with 1.8 ounces of zinc coating per square foot of surface area conforming to ASTM F1083. 2. Type II — Pipe manufactured from steel conforming to ASTM A569. External surface triple coated per ASTM F1234. Type II pipe shall demonstrate the ability to resist 1,000 hours of exposure to salt spray with a maximum of 5 percent red rust in a test conducted in accordance with ASTM B117. 3. All coatings are to be applied inside and out after welding. 4. Unless otherwise noted, Type II framework shall be provided. 5. Pipe shall be straight, true to section and conform to the following weights: Table 1: Tvpe I and Tvpe II Steel Pipe Specifications Pipe Size • • 1 5/8" 2.27 1.84 2" 2.72 2.28 2 %" 3.65 3.12 3" 5.79 4.64 3 %" 7.58 5.71 P25 System and Services Agreement (R1422515R1/P1) Page 22 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 4" 9.11 6.56 6 5/8" 18.97 N/A C. Fabric: 1. Aluminized fabric shall be manufactured in accordance with ASTM A491 and coated before weaving with a minimum of 0.4 ounces of aluminum per square foot of surface area. The steel wire and coating shall conform to ASTM A817. Fabric shall be 9-gauge wire woven in a 2-inch diamond mesh. The top selvage shall be twisted and barbed. The bottom selvage shall be knuckled. 2. Zinc -coated fabric shall be galvanized after weaving with a minimum of 1.2 ounces of zinc per square foot of surface area, and shall conform to ASTM A392, Class I. Fabric shall be 9-gauge wire woven in a 2-inch diamond mesh. The top selvage shall be twisted and barbed. The bottom selvage shall be knuckled. D. Fence Posts: E. Gate Posts: i ame c: rence rose �pecmcauons PostsFence Under 6' 2" 2 %2" 6'-9' 2 %" 3" 9'-12' 3" 4" Table 3: Gate Posts Specifications Up to 6' I Up to12' I 3" 7' to 12' 13' to 25' 4" F. Rails and Braces: 1 5/8-inch outside diameter (O.D.) G. Gates: Frame assembly of 2-inch O.D. pipe (Type I or Type 11) with welded joints. Weld areas shall be repaired with zinc -rich coating applied per manufacturer's directions. The fence fabric shall match the fence posts, gateposts and gates. Gate accessories, hinges, latches, center stops, keepers and necessary hardware shall be of a quality required for P25 System and Services Agreement (R1422515R1/P1) Page 23 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 industrial and commercial application. Latches shall permit padlocking. Provider shall provide one padlock for each gate with three keys for each padlock. All padlocks shall be keyed alike. H. Installation: 1. General — Fence installation shall conform to ASTM F567, Standard Practice for Installation of Chain -Link Fence. 2. Height — Fence height shall be as indicated on Contract drawings. If no height is indicated, the fence shall be 7-feet high, plus one foot for barbed wire. 3. Post Spacing — Line posts shall be uniformly spaced between angle points at intervals not exceeding 10 feet. 4. Bracing — Gate and terminal posts shall be braced back to adjacent line posts with horizontal brace rails and diagonal truss rods. 5. Top Rail —The top rail shall be installed through the line post loop caps, connecting sections with sleeves to form a continuous rail between terminal posts. 6. Fencing shall have a bottom rail instead of a tension wire. 7. Fabric —The fabric shall be pulled taut with the bottom selvage two inches above grade. The fabric shall be fastened to the terminal posts with tension bars threaded through mesh and secured with tension bands at maximum 15-inch intervals. The fabric shall be tied to the line posts and top rails with tie wires spaced at a maximum of 12 inches on posts and 24 inches on rails. The fabric shall be attached to the bottom rail with top rings at maximum 24-inch intervals. 8. Barbed Wire — Barbed wire shall be anchored to the terminal extension arms, pulled taut and firmly installed in the slots of the line post extension arms. 9. Valleys — Should the fence cross a ditch or drainage swell, 3/8-inch diameter aluminum alloy rods shall be driven vertically 18 inches into the ground on 4-inch centers, and woven through the fence fabric to provide security for these areas. 10. Vegetation stop and aggregate shall be applied to the entire compound area (the area inside the fencing) and six inches beyond the fencing. Vegetation stop shall be constructed with weed barrier geotextile and aggregate shall be applied three inches in depth and consist of American Association of State Highway and Transportation Officials (AASHTO) #10 coarse aggregate. P25 System and Services Agreement (R1422515R1/P1) Page 24 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1.7 DC Power System Provider shall provide a -48 VDC power system to support P25 equipment, microwave equipment, and ancillary site equipment at proposed sites. The DC power system for the three regional public safety answering points (PSAPs), the Emergency Operations Center (EOC) site, and the EMS site shall only be required to support microwave equipment. A. Provider shall provide dedicated 220 VAC/30-amp circuits for each pair of rectifiers on the DC plant, and provide electrical connections and grounding to the DC plant. B. Provider shall perform electrical loading analysis for shelter equipment, excluding HVAC subsystems, during preliminary design to verify the DC system size required. All assumptions regarding power consumption and duty factor shall be thoroughly explained and approved in advance by County Contract Administrator. C. Provider shall appropriate distribution breakers and circuits for DC power to each designated row of equipment racks. Equipment installed within those racks shall be immediately accessible to the DC power source. D. Provider shall provide an N+1 redundancy scheme for all voltage levels. E. Quality Assurance: 1. Electrical components, devices, and accessories shall be listed and labeled, as defined in NFPA 70, by a qualified testing agency, and marked for intended location and application. 2. UL compliance shall be listed and labeled under UL 1778 by a nationally recognized testing laboratory (NRTL). 3. NFPA compliance shall identify uninterruptible power supply (UPS) components as suitable for installation in computer rooms according to NFPA 75, Standard for the Protection of Information Technology Equipment. F. Performance Requirements: 1. Input: a. Single-phase, 3-wire b. Voltage: 120/240 V nominal c. Frequency: 50/60 Hz +/- 3 Hz P25 System and Services Agreement (R1422515R1/P1) Page 25 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. Output: a. Capacity: Assumed at 1,000 amperes, to be finalized during the design phase b. Voltage:-24/-48 VDC, 12 VDC, and 120 VAC with minimum 10 Amp surplus supply current at each voltage level 3. Minimum Duration of Supply —The DC power system shall provide eight hours of runtime at 50 % load and four hours of runtime at 100 % load with a 25-percent equipment growth factor. 4. EMI Emissions — Comply with FCC Rules and Regulations and with Title 47 of the Code of Federal Regulations (CFR), Part 15 for Class A equipment. 5. Electronic Equipment —Solid-state devices using hermetically sealed semiconductor elements. Devices include rectifier -charger, inverter, and system controls. 6. Surge Suppression — Protect internal DC components from surges that enter at each AC power input connection, and protect controls and output components. 7. The DC power system shall include a bypass switch to permit technician access to batteries and rectifiers without power interruption. 8. The DC power system shall include alarm contacts to be interfaced to the site alarming system. G. Tests and Inspections: Provider with perform the following tests and inspections in compliance with the following details. Provider shall properly remedy (including by repair or replacement) any portion of the DC power system that fails, in whole or in part, any test or inspection. 1. Comply with manufacturer's written instructions. 2. Inspect interiors of enclosures, including the following: a. Integrity of mechanical and electrical connections b. Component type and labeling verification c. Ratings of installed components 3. Test manual and automatic operational features, as well as system -protection and alarm functions. 4. Provide inspection reports. P25 System and Services Agreement (R1422515R1/P1) Page 26 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 H. Demonstration: Train County's maintenance personnel to adjust, operate, and maintain the DC power system, including at each site to the extent of any variations between sites. 1.8 48VDC Power System Overview Unless otherwise approved by County in advance, Motorola Solutions' subcontractor, ARM Electrical Services, will provide and install the required -48vdc Eltek DC Power system for each RF site. This system consists of a charger -rectifier and battery plant that will provide the required 8 hours of reserve power to the RF sites assuming 50% average transmit time for base repeaters on each site. In addition, the system will provide over 4 hours of reserve power assuming all trunked stations on site are running continuous transmit. In both scenarios, the DC system includes a 25% growth factor for future additions and the required N for 1 redundancy for rectifier modules, and includes all equipment at each site as of the Effective Date. The Eltek charger -rectifier will be factory racked, wired and tested. The assembly will contain individual DC circuit breaker distribution panel(s), voltage and current continuous metering capabilities, high/low DC voltage disconnect switching and all necessary maintenance and management alarm and control functions. The charger will be provided in redundant arrangement with units of identical capacity and type working on a load -sharing basis during normal operation. Solid state monitoring by the power board will be continuous and automatic switchover employed in the event of failure of either unit. Upon switchover the surviving rectifiers will be able to carry the entire site load and provide 24-hour recharge in the event of any loss of AC power. Each RF site has the required additional redundant voltage outputs of +12 vdc, -24 vdc and 120 vac all rated at a minimum of 10 amps each. These do converters and AC inverters operate from the main charger -rectifier using the -48vdc input. The DC distribution circuit breaker panels and the main -48 VDC ground (return) buss will be isolated in this rack as part of the Eltek power board assembly. The main distribution circuit breaker panel will provide the main bus feeds for the radio racks. Each 19 inch radio rack will have a split breaker sub -panel for the various radio equipment breakers. The battery plants are built using EnerSys PowerSafe DDm series batteries designed using proven gas recombination technology which removes the need for water addition by controlling the evolution of hydrogen and oxygen during charging. The batteries will be rack mounted in battery racks for floor space conservation. 1.9 Site Development Schedule The site development schedule is fully integrated into the overall Project Schedule (set forth in Schedule 10) that includes milestones for key project tasks. Provider and DB-Firm shall comply with the Project Schedule for all Services under this SOW A-2, unless otherwise approved in writing by the Contract Administrator. P25 System and Services Agreement (R1422515R1/P1) Page 27 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SECTION 2 RADIO SITES Provider shall perform all services and provide all equipment to ensure that each Radio Site meets the specifications and standards set forth herein and in the applicable System and Site Attachments Table for each site. For all new towers identified herein, Provider will provide the site engineering and complete all obligations set forth under Section 3.1.1 below for new sites. Any design details, diagrams, specifications, or other information detailed herein may be modified upon further review by the Parties only upon written confirmation by both Parties. Any such modification shall not require an amendment, change order, or work authorization, provided that there is no additional cost to County. P25 System and Services Agreement (R1422515R1/P1) Page 28 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.1 Site Name: Core Core is an existing Broward County Radio site. In accordance with Solicitation R1422515131 Appendix B- Addendum 2, a new 24' X 32' pre- cast shelter will be installed in addition to the existing 24' X 32' shelter. A new DC Power System will be installed in the new shelter, along with a new generator and transfer switch. The existing shelter will utilize the existing UPS and existing generator. Site Details: Site Engineering: :6 Figure 2-1: Core • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted by the construction activity, and perform all actions necessary to alleviate or remedy that impact. • Provide a structural engineering analysis for antenna support structure to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install three Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 29 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Existing Facility Improvement Work: • Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade shelter and supporting systems to optimal conditions, including the following: o Ensure roof is in good condition and free of leaks o Repair any damaged flooring or siding to building o Seal building to prevent pest entry o Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 30 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-1: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 08 56.5 80 11 18.8 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 296 Self -supported tower IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type N/A N/A N/A New Ice Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator / Transfer Switch New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)' /2-inch 7/8-inch 1-1/4- inch 1-5/8- inch Wave Guide 975 975 1500 N/A 440 1 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 31 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.2 Site Name: Coconut Creek Coconut Creek is an existing Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the existing 24' X 32' shelter, tower and generator will be used. A new DC Power System will be installed. The existing UPS will be decommissioned and removed. Figure 2-2: Coconut Creek Site Details: Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install eight antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install three tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install two Microwave Dishes, • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 32 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Existing Facility Improvement Work: • Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade shelter and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to building — Seal building to prevent pest entry — Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 33 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-2: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 18 12.4 80 11 43.8 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 400 Self -supported tower IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type N/A N/A N/A New Ice Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator / Transfer Switch New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 8 3 2 New RF Lines (Linear Ft.)Z 1/2-inch 7/8- inch 1-1/4-inchor1 1-5/8- inch Wave Guide 1720 1290 2025 320 200 z Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 34 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.3 Site Name: Markham Park Markham Park is an existing Broward County Radio site. In accordance with Solicitation 111422515131 Appendix B- Addendum 2, a new 24' X 32' pre -cast shelter will be installed, in addition to the existing shelter. A new DC Power System will be installed in the new shelter, along with a new generator and transfer switch. The existing UPS and generator will remain as is. The existing guyed tower will be utilized. Figure 2-3: Markham Park Site Details: Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install three Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. Existing Facility Improvement Work: • Install one new 80kW diesel generator and automatic transfer switch. P25 System and Services Agreement (R1422515R1/P1) Page 35 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade shelter and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to building — Seal building to prevent pest entry — Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 36 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-3: System and Site Improvements Ground Elevation (Ft.) 9 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 26 08 43.1 80 1143.8 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 415 Guyed tower IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 TIGHT New Ice Bridge Length (Ft.) 15 New Shelter Type Precast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator / Transfer Switch New Generator (Type) 175KW Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp; 120/240- volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 2 3 New RF Lines (Linear Ft.)3 /2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guid e 850 850 1200 N/A 540 3 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 37 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.4 Site Name: Playa Playa Condominiums is an existing Broward County W Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the existing Roof top equipment room and generator will be used. A new DC Power System will be installed. The existing UPS will be decommissioned and removed. t Figure 2-4: Playa Site Details: Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter one, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system, including an x-ray analysis of the walls. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install five antenna(s) for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 38 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Existing Facility Improvement Work: • Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade shelter and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to equipment room — Seal equipment room to prevent pest entry — Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 39 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-4: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 26 10 32.3 80 05 52.2 Site Owner Playa Existing Tower Ht (Ft.) Existing Tower Type 280 Roof Top IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) ring Type N/A N/A t�NA NewIce Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator (kW) New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)' 1/2-inch 7/8-inch 1-1/4- inch 1-5/8- inch Wave Guide 200 500 N/A N/A 200 4 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 40 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.5 Site Name: Davie Davie is an existing Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the existing 12' X 32' shelter and tower will be used. A new DC Power System will be installed, along with a new generator and transfer switch. The existing generator, automatic transfer switch and UPS will be decommissioned. The transfer switch and UPS will be removed. Figure 2-5: Davie Site Details: Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter one, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install eight antenna(s) for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install three tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install three Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. Existing Facility Improvement Work: Install one new 80kW diesel generator and automatic transfer switch. Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. P25 System and Services Agreement (R1422515R1/P1) Page 41 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Upgrade site grounding to the latest revision of R56 Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system Upgrade shelter and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to building — Seal building to prevent pest entry — Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 42 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-5: System and Site Improvements Ground Elevation (Ft.) 7 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 03 54.7 80 20 19.2 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 315 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type N/A N/A N/A New Ice Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) 500 Diesel New Generator /Transfer Switch New Generator (Type) 80kw / 400 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 8 3 3 New RF Lines (Linear Ft.)5 1/2-inch 7/8-inch 1-1/4- inch 1-5/8- inch Wave Guide 975 975 1200 N/A 660 S Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 43 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.6 Site Name: Points of America Points of America Condominiums is an existing Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the existing Roof top equipment room and backup power will be used. A new DC Power System will be installed. The existing UPS will be decommissioned and removed. Site Details Site Engineering: k9- Figure 2-6: Points of America Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter one, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two Tower Top Amplifiers • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. Existing Facility Improvement Work: • Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. P25 System and Services Agreement (R1422515R1/P1) Page 44 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade equipment and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to equipment room — Seal equipment room to prevent pest entry — Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 45 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-6: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 05 48.0 80 06 26.0 Site Owner Points of America Existing Tower Ht (Ft.) Existing Tower Type 250 Roof Top IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type N/A N/A N/A New Ice Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator /Transfer Switch New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)6 1/2-inch 7/8-inch 1-1/4- inch 1-5/8- inch Wave Guide 200 500 N/A N/A 200 6 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 46 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.7 Site Name: Miramar Miramar is an existing Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, a new 12' X 32' pre -cast shelter with a new DC Power System will be installed in addition to the existing shelter. The existing tower will be used. A new DC Power System will be installed for the new shelter, along with a new generator and transfer switch. The existing generator, automatic transfer switch and UPS will not be decommissioned. Figure 2-7: Miramar Site Details Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. Existing Facility Improvement Work: Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. P25 System and Services Agreement (R1422515R1/P1) Page 47 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Install one new 80kW diesel generator and automatic transfer switch. • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade shelter and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to building — Seal building to prevent pest entry — Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) P25 System and Services Agreement (R1422515R1/P1) Page 48 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-7: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 25 57 30.7 80 20 18.5 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 315 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Precast New Shelter Width (Ft.) New Shelter Length (Ft.) 12 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 650 Diesel New Generator /Transfer Switch New Generator (Type) 100kw / 00 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 400-amp - 120/240- volt, single-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)' 1/2-inch 7/8-inch 1-1/4- inch 1-5/8- inch Wave Guide 650 650 900 N/A 305 ' Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 49 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.8 Site Name: Channel 2 Channel 2 is an existing Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, a new 24' X 32' pre -cast shelter with a new DC Power System and with a new generator will be installed. The existing shelter will be demolished and removed. A new 300' Self supported tower will be installed. Figure 2-8: Channel 2 Site Details: Tower Work: • Construct drilled pier tower foundation including excavation, rebar, and concrete • Erect new 300-foot self -supported tower. • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install eight antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install three tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 50 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-8: System and Site Improvements LA Ground Elevation (Ft.) 10 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 25 58 49.3 80 1145.8 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 390 Guyed IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 25 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator /Transfer Switch New Generator (Type) 175 kw / 600 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp - 208-240- volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 8 3 2 New RF Lines (Linear Ft.)' 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 990 990 1525 N/A 375 s Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 51 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 F A n a r_�ryy 2v m R U w € i7 ra w R E 2 - C F i s F Y 4 g 390 on IR' Rl Au aft m e 28C Q it mt o tt 2ae o n 300,a ft 10C Oft 60.0 it 14C_O Oft t20.0 ft h09r1 i eQott BO—aft 400fr 200tt dda DESIGNED APPURTENANCE LOADING TYPE ELEVATION TYPE ELEVATION 2 1 - LRE with P 6" 11Chmine red (arm=1151 300 1'C 07-11 27L 0•U--.1 Side A.(64"pipe? 275 Beacon e00 TC907-11 275 20' 9eacon Eatapder 900 5'Uni1—f SideArm(84" PIP11 275 Cc9D7-a 360 C m-11 775 B'Unversal-S.d¢A-N4"tape) 30U E!Unrve ISde Arm (e4"pipe) 275 Cc00i.14 200 CC807-11 {50%wture) 275 O'UnNEr9g Side Arm 184"pip£) 3W E'Unrverssl 5ideAm(84"pipe)i5- tuwrel 275 tin Tndbbaiepie5428E-071 iT 30n 6'Plvat Side Artn (SQ"pipe) 800 CC807-11(50%fu[ure7 275 Bird Te tlm r1egle542HE-83IA I 300 0'ur—sat 51 de Arm (64"pipe) [5 d°'v iU_) 275 B'Plw[Side A-m 50"pipe) Don CC807-11 160%future) 900 CC307-11 (50%Uw) 275 a'UONersa151deArrn(A4" prpe)(50% wwre) a00 F Universal Sde Arm(54"pipe)(58% wture) 275 CC002.1f 150%fuYurel ma 2.112-X22'Sch 411 113 A'UnNersal Side Arm (A4" pipe) (5C% tut") 309 2 ?2'x 22S[h U 113 PADa-599C(wf Rad—Aserm 13 Birtl Temnolotl'es 42HE-831-01-F I50% wwre) 300 PADMDBC WRadpmeA=MEd) i56%ware 113 E'Pi— Side Arm(50' pip2)(58% iuwre) Pon 3-x24'sr 4n 9d PAC15-59BC£r°"7Radoft AswriW) 90 BrtaTerstn°Iaq�es428E B31-n1T (40%30p wklrei 8'Y24.5M4C Cd B'arwt�eegrmf58^vrpa)[5U'� wwre) 3ne P1k[13-59RC(w1RadbmAse4madi 15n%wwra 9Q SYMBOL LIST MARK SIZE MARK SIZE A P-4.00'-n 75'mnn.-20'-GTrsns R"Er(Rrod H #12ZG59-200'-d,975'c°nn (Ar°d195639j 2261041 I. #12ZG5p -2 25' - O B75' coon. (Rmd 195RE01 B P-5➢0'-0.75'cnnn.-T.,n-w.c.1Pmd-22wa0 J ,a122G-50-Z50"-0.075'rnnn -TR4-[Bond C P-500--0.75•conrr-20-C4PIr 1i70187t 195362) D P-DAil'-075'wnn.-H90-TraAs,29'-C-tF.Ck K 912SC-50-253'-0.875'1nnn Trod f95264) 222377) L 012ZC-58-275°-0875'eann.(Pmd19D289) E #T2ZC-SB-175"-1.UU"umn-TR1-iPirad Id p127G55-390'-©E75' conn.(Trdd 1R55Pt1 MATERIAL STRENGTH GRADE Fy I Fu I GRADE I FY I Fu A577-50 IM.1 166 ks1 A572-69 160 ksl 17S hs AW as kb I 5d ks. TOWER DESIGN NOTES 1. Tower is located in Broward County, Florida. 2. Tower designedfor Exposure C to the-TIA-222-G Standard. 3. Tower designed fora 140 mph basic wind in accordance with the TIA-222-G Standard. 4. Deflections are based upon a 60 mph wind. S. Tower Structure Class III. 6. Topographic Category f with Crest Height of DAD 8 7. TOWER RATING. 99.5% ALL REACTIONS ARE FACTORED MAX. CORNER REACTIONS A T BASE: DOM. 842 K UPLIFT -731 K SHEAR: 93 K AXIAL 97K SHEAR MOMENT 150 K 23151 kip-ff TORQUE 97 fup-ft REAC77ONS -140 mph IMNO valnaont 1545 PidCo Drive Plymouth, IN Phone', 574-936-4221 FAX: JA Quotation 334251-02 V-33 x300' Che ` MoWrofa Solutions ° "by SKK Ana°• c°de- TIA-222-G NTS Pam - Hd EA P25 System and Services Agreement (R1422515R1/P1) Page 52 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.9 Site Name: Deerfield Deerfield is a new Broward County Radio site. In accordance with Solicitation R1422515131 Appendix B- Addendum 2, the site will receive a new 24' X 32' precast shelter with a new DC Power System, generator and a new 300' self - supported tower. Figure 2-9: Deerfield Site Details Tower Work: • Construct drilled pier type tower foundations including excavation, rebar, and concrete • Erect new 300-foot self -supported tower. • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower -top amplifier. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4 inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Perform alignment of each of three microwave paths to ensure that the microwave dishes are optimally positioned. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 53 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-9: System and Site Improvements Ground Elevation (Ft.) 15 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 17 31.6 80 06 29.4 Site Owner Broward County New Tower Ht (Ft.) New Tower Type 300 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator (kW) New Generator (Type) 175 kw / 600 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp - 208-240- volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)9 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 660 660 915 N/A 265 9 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 54 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.10 Site Name: Tamarac Tamarac is a new Broward County Radio site at the existing Tamarac location. In accordance with Solicitation R1422515131 Appendix B- Addendum 2, the site will receive a new 24' X 32' precast shelter with a new DC Power System, generator and a new 300' self -supported tower. Figure 2-10: Tamarac Site Details: Tower Work: • Construct drilled pier type tower foundations including excavation, rebar, and concrete. • Erect new 300' self-supporting tower (or, if determined appropriate by County, a 180' monopole tower, with the commensurate reduction in cost applied toward other services, including Optional Services). • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install one tower -top amplifier. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Perform alignment of each of three microwave paths to ensure that the microwave dishes are optimally positioned. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/131) Page 55 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-10: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 26 12 43.5 80 16 20.5 Site Owner City of Tamarac New Tower Ht (Ft.) New Tower Type 300 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 100 Diesel New Generator (kW) New Generator (Type) 175 kw / 600 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp - 208-240- volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 1 2 New RF Lines (Linear Ft.)10 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 660 660 1005 N/A 330 10 Or as required. P25 System and Services Agreement (R1422515R1/131) Page 56 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.11 Site Name: West Lake Park West Lake Park is a new Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2 the site will receive a new 24' X 32' precast shelter with a new DC Power System, generator and a new 300' Self Supported tower. Figure 2-11: West Lake Park Site Details: Tower Work: • Construct drilled pier type tower foundations including excavation, rebar, and concrete. • Erect new 300-foot self -supported tower. • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower -top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install 2 Microwave Dishes. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Perform alignment of each of three microwave paths to ensure that the microwave dishes are optimally positioned. • Supply and install 1 ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 57 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-11: System and Site Improvements Ground Elevation (Ft.) 7 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 01 57.9 80 07 45.7 Site Owner Broward County New Tower Ht (Ft.) New Tower Type 300 IMPROVEMENTSSITE New Compound/Expansion Size self -supported Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator (kW) New Generator (Type) 175 kw / 600 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp - 208-240- volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)" 1/2-inch 7/8-inch 1-1/4-inch 1-5/8-inch Wave Guide 660 660 915 N/A 263 "Or as required. P25 System and Services Agreement (R1422515R1/131) Page 58 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3d9.Oft 2A0�Q it 290.Qtt A QIt 220L- 2000 1aO Q It 60➢It 1+9 01t 71ar 00.3 it 60.0 ft 60 Ph 40 9 tt 2II0tt P.9 ft DESIGNED APPURTENANCE LOADING TYPE ELEVATION TYPE ELEVATION 21' U7F,d, tl1 7-5" hghmlhg and (slrr 113) 305 CC 107-11 275 a'Uhrversal Sde Arm(194"pR+e) 215 Beacon 300 CCR07-11 275 29' neamn Ettender 305 9Lrwersal SideAw (134' pipe) 275 CCE07-11 39n M117-11 2T5 6'UnNelSal Side Arm134-DI0e1 300 5'IJnrversa1 Side Alm(114'pipe? 215 CCEU7-11 300 CCROT-1100%f4n1e1 275 6'UnNef SldeArm184'plPe) 309 3'U-11PI 00Ami(64"pfpe)[50W% Future) 275 131rd hhnnlagles 428E-M)-al-T 306 R Plwt SideA— JW' plRe') 300 CCa07-11(60%More) 275 gird Techhnlogies 429E.631,91 T 330 6'Fln""'Side Arm(84"pipe) (sp% to Lure) 275 6 PIVR[ Side Arm(%' pipe) 309 C(EQ7-11 (59%f=re) 390 CC907-11150'M Mure) 275 R`unrver�VSlde Aan(A4' pipel(5n% lytufe) 350 5'UnNersal Side Arm [E4"pioe)[50% future) 275 CIMF 11 Wi future) 30Q 2-1f2'x 22'Sch. 4P 9f3 S`UnNersaV Side Arm 194'plpe)(50% furore) 330 2-1I2'x22'Sch. 40 113 PAC&598C rM Radc-Assumed) 113 Hlyd Te-n 01091 SS 428E-631-0I T(50%Da future) PALF53r6 C 11Wl BM— Assumed) (50%fifilre 116 6' Riva Side Arm(50' pipe)(5096 furore) 30P T" 24'S&40 90 PAU9-599C (Wr Redeme A55urned) 130 91rd Technoleg�es 42EF-631.91-T(5n% fuUM 399 21. N'^,m 4n I 3P PA1XMC W RadomeA—d) (5n%iutura B5 IT FAr Side A-j8W pine) (5C% M—) 303 SYMBOL LIST MARK SIZE MARK SIZE A P-4U1. n.76'mnn-2n-G7r3rrs66-013(R.d H *1 ZMES-2CW- 0. A75'coon. IP,.d 1 B5629) 2261 A41 1 #12ZG-Ce.225"- C.075'conn. T1.d 195960) 6 P- 5Id0'- 0,75' corm-7rans70' - '-(Pnmi 226200) J *12ZC-58 - 2.50' - S.975" coon.-TR4-4Fftd C P-5E0"-575"coon. 20'-C-(Prrud 726192 195902) 0 P-6nn"-0.76" vo HREI Tr ns20-,Fftd K#122[3.5E-2.5n•-nEY5"cunh(Firnd195964) 229377) L #12ZCrH 275-9E75"coon (Pirod 1962A91 #12ZG-50.175"-109"coon-TR7-(Pirod M f712ZG58-300'-0.675'Con1,(Pndl96521) L� '05 213, o , x• . n,,..,M - i1fIATERIAL STRENGTH 6GRADE Fy Fu GRADE Fy Fu A672-50 50 ka 66 ksr A572-5A 59 ka 15 ks1 AN36 ka 5A 1,s1 TOWER DESIGN NOTES 1. Tower is located in Broward County, Florida. 2. Tower designed for Exposure C to [he TIA-222-G Standard. 3. Towerdesigned fora 140 mph basic wind in accordance with the TIA-222 G Standard. 4. De9eetions are based upon a 6U mph wSnd. 5. Tower Structure Class III. 6. Topographic Category 1 with Crest Height of 0.00 ft 7. TOWER RATING: 99.5% ALL REACTIONS ARE FACTORED MAX. CORNER REACTIONS ATBASE: DOWN.' 842 K UFUFT -731 K SHEAR: 93 K AXIAL 97K SHEAR MOMENT 150 K k 23151 kip-ft TORQUE 97 Ai" REACTIONS -140 mph WIND Valmont Qaotatian 334261-02 1545 Pidco Drive "I"' V-33x300' Plymouth, IN client Motorola Solutions °ra"'i °v SKK Apad Phone: 574-9364221 code- TIA-222-G �a[e' 04R6117 scale' NTS FAX: pgrh Lw9 N° E-1 Figure 2-12: West Lake Park Tower P25 System and Services Agreement (R1422515R1/P1) Page 59 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.12 Site Name: Sunrise Dispatch Sunrise Dispatch is an existing dispatch site. Any services or work necessary to be performed at this site to achieve the specifications of the System and meet the other requirements of the Agreement shall be f -M ,, completed by Motorola as C - - -- part of the scope of services hereunder. ial1 Figure 2-13: Sunrise Dispatch Tower 2.13 Site Name: Coconut Creek Dispatch Coconut Creek Dispatch is an existing dispatch site performed at this site to achieve the specifications of the System and meet the other requirements of the Agreement shall be completed by Motorola as part of the scope of services hereunder. Any services or work necessary to be Figure 2-14: Coconut Creek Dispatch P25 System and Services Agreement (R1422515R1/P1) Page 60 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.14 Site Name: Pembroke Pines Dispatch Pembroke Pines Dispatch is an existing dispatch site. Any services or work necessary to be performed at this site to achieve the specifications of the System and meet the other requirements of the Agreement shall be completed by Motorola as part of the scope of services hereunder. Figure 2-15: Pembroke Pines Dispatch P25 System and Services Agreement (R1422515R1/P1) Page 61 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.15 Site Name: FS 106 Broward County FS 106 is a new Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the site will receive a new 24' X 32' precast shelter with a new DC Power System, generator and a new 300' self -supported tower. Amok Any services or work necessary to be performed at this site to achieve the specifications of the System and meet the other requirements of the Agreement shall be completed by Motorola as part of the scope of services hereunder. E5 Figure 2-16: FS 106 Site Details: Tower Work: • Construct drilled pier type tower foundations including excavation, rebar, and concrete • Erect new 300' self -supported tower. • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install 4 antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower -top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install four Microwave Dishes. • Perform sweep tests on transmission lines. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install 1 ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 62 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-12: System and Site Improvements 7ndtion (Ft.) 17 n No Zoning No A&E Services Yes Latitude Longitude 26 08 44.2 80 37 42.5 Site Owner Broward County New Tower Ht (Ft.) New Tower Type 300 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator (kW) New Generator (Type) 175 kw / 600 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp - 208-240- volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 4 2 4 New RF Lines (Linear Ft.)12 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 660 660 660 N/A 560 "Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 63 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 a � R U Q a [dl H o e ui :5 ♦° u C L p R a �1 z N 9 a i7 r w li a # m _ 311oft r®r ®I I / AM U It 289.Oft 240_O Rk 22D_O In 20O�0 Rft tkv 0ItO Et BE a Ft !AD On (g00n /r Doors 60 O 1t 000R 43 D n 7DDn left DESIGNED APPURTENANCE LOADING TYPE ELEVATiGN TYPE ELEVATION 11' LRE vanh 7'-S° logh.1,,q rpd (—=113) 309 CQ17-11 275 6'U—mal Bide Arm t84'pipe) 275 Beacon 800 CCUN-11 275 20' EeaFarl Er,(ender 303 0Um rsal $,d,A m (84° pipe) 27h CCB07.11 '300 CM37.11 275 VUniv-1 Side Arm(94'ppel 300 5U--1 SidEAfm(34°Pipe) W5 CCE07-11 SOO CC80 -11 IEO%furure) 275 6' Unrveisa151tleArm484' pipe) 30U 6' Un-lsal W, Ar,i 04" pipe) (50% Kure) 27& gird Technologies 428C--63I-01-T aoo V FIi Side Arm(Wplpe) ant CCR37-11150%More) 276 Bird Technologies 426E-691.01-T 300 6' Universal 5ide Arm(94'pip.)(50% Nt—) 275 6 Pivot Si de Arm (5U' pipe) wu ('0I"'-11 (50°A rulu2 900 C-007-11150%haure) 275 60nversal Slde ARn(04'plpel(50% future) 300 6'Unwersa1 Side Ann(84"pipe)(51% future) 216 CCO07-11 (sD%rut—) 3oa 7-VT = 22' Seh 4o 117 E'DrTVersel SldeAmn(04.'pjr,)(60% future) 301 2-1/2'x 22'Sch. 4C 118 PAU6-596C WRadmeAssomeli) 10 Bird T2onologies428E081-01-T(5C°4 More) 103 PA06596C tw7Rad—Asaumed) (50%future 112 UP ! L 5 de An (W piW (5GS tuwv) 300 3" 1: 24' Bcti. 40 90 PA135.590C Iw+RatlomeA;sumedj 90 Bird Technologies420E-831.01-T E60% kture) 303 -.' .44,E an PO E Piwc 5ide Arrl(50' pipe? (M% More) 303 (50%�� (tMRad°rrieAs9emed} 00 SYMBOL LIST MARKI SIZE MAPK SIZE A P-4GO". 0.75'coon-2D'-C-T-6B-4e(r-Srod H #12i658-2ca°- a015' coon, Inmd 105639) 226184) #127G58 -2:26' - 0.975' cone. IPlmd Isrson) B P-5L0"-0.IT Cann-TM-2(]'LjPirod 276:00t J F127C-58-250'-0. F175"rnnn_TR4-(Rmd C P 5CO"-R15"-vn_R1'-C{prrod 229192� 195uu) E P-600"-0.75"conn-HEM-Tm—X-G(P-rod K #122R-56. 2.50'-0.875"cona.(Puod 195964j 229371) L #127a% 275-0976"cgnn.(Pirod 196299y E #1270-68-1.75"-1 001c°nn-71-(Pend M 1F12LC'58-3 Eu,- 1. 87 S Conn IFlmd 1UH5217 .t3) '^MATERIAL STRENGTH 6GRADE Fy Fu GRADE Fy Fu 7MO 50 kR 69 ksi Afi7Zfi8 68 ks 7fi ksr 928 36 ks� 6P Iasi TOWER DESIGN NOTES 1. Tower is located in Broward County, Florida. 2. Tower designed for Exposure G to the TIA-222-G Standard. 3. Tower designed fora 140 mph basic wind in accordance with the TIA-222-G Standard. 4. Deflections are based upon a 60 mph wind. 5. Tower Structure Class III. 6. Topographic Category 1 with Crest Height of 0,00 & 7. TOWER RATING. 99.5% ALL REACTIONS ARE FACTORED MAX CORNER REACTIONS AT BASE: DOWN.' 842 K UPLIFT., -731 K SHEAR: 93K AXIAL 979 SHEA� MOMENT 150 K j 23151 hip-(t TORQUE 97 kip- t REACTIONS - 140 mph WIND Y•nlmant 1545 Pidco Drive Plymouth, IN Phone:574-936-4221 FAX: ° Quotation 334251-02 `J'a V-33x300' c'"L Motorola Salutlons 13r dy SKK App'd Cdde TIA-222-G ❑a[e 04/06/17 Sra1e: Patrc IT, p"'91v° IT, Figure 2-17: FS 106 Tower P25 System and Services Agreement (R1422515R1/P1) Page 64 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.16 Site Name: Parkland Parkland is a new Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the site will receive a new 24' X 32' precast shelter with a new DC Power System, generator and a new 300' self - supported tower. Figure 2-18: Parkland Site Details: Tower Work: • Construct pier and pad type tower foundations including excavation, rebar, and concrete • Erect new 300' self -supported tower. • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower -top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install 4 Microwave Dishes. • Perform sweep tests on transmission lines. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install 1 ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 65 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-13: System and Site Improvements Ground Elevation (Ft.) 17 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 2621 17.8 80 16 59.2 Site Owner Broward County New Tower Ht (Ft.) New Tower Type 300 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator (kW) New Generator (Type) 175 kw / 600 A Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp - 208-240-volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 2 4 New RF Lines (Linear Ft.)13 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 660 660 915 N/A 630 13 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 66 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 F A n a r_�ryy 2v m R U w € i7 ra w R E 2 - C F i s F Y 4 g 390 on IR' Rl Au aft m e 28C Q it mt o tt 2ae o n 300,a ft 10C Oft 60.0 it 14C_O Oft t20.0 ft h09r1 i eQott BO—aft 400fr 200tt dda DESIGNED APPURTENANCE LOADING TYPE ELEVATION TYPE ELEVATION 2 1 - LRE with P 6" 11Chmine red (arm=1151 300 1'C 07-11 27L 0•U--.1 Side A.(64"pipe? 275 Beacon e00 TC907-11 275 20' 9eacon Eatapder 900 5'Uni1—f SideArm(84" PIP11 275 Cc9D7-a 360 C m-11 775 B'Unversal-S.d¢A-N4"tape) 30U E!Unrve ISde Arm (e4"pipe) 275 Cc00i.14 200 CC807-11 {50%wture) 275 O'UnNEr9g Side Arm 184"pip£) 3W E'Unrverssl 5ideAm(84"pipe)i5- tuwrel 275 tin Tndbbaiepie5428E-071 iT 30n 6'Plvat Side Artn (SQ"pipe) 800 CC807-11(50%fu[ure7 275 Bird Te tlm r1egle542HE-83IA I 300 0'ur—sat 51 de Arm (64"pipe) [5 d°'v iU_) 275 B'Plw[Side A-m 50"pipe) Don CC807-11 160%future) 900 CC307-11 (50%Uw) 275 a'UONersa151deArrn(A4" prpe)(50% wwre) a00 F Universal Sde Arm(54"pipe)(58% wture) 275 CC002.1f 150%fuYurel ma 2.112-X22'Sch 411 113 A'UnNersal Side Arm (A4" pipe) (5C% tut") 309 2 ?2'x 22S[h U 113 PADa-599C(wf Rad—Aserm 13 Birtl Temnolotl'es 42HE-831-01-F I50% wwre) 300 PADMDBC WRadpmeA=MEd) i56%ware 113 E'Pi— Side Arm(50' pip2)(58% iuwre) Pon 3-x24'sr 4n 9d PAC15-59BC£r°"7Radoft AswriW) 90 BrtaTerstn°Iaq�es428E B31-n1T (40%30p wklrei 8'Y24.5M4C Cd B'arwt�eegrmf58^vrpa)[5U'� wwre) 3ne P1k[13-59RC(w1RadbmAse4madi 15n%wwra 9Q SYMBOL LIST MARK SIZE MARK SIZE A P-4.00'-n 75'mnn.-20'-GTrsns R"Er(Rrod H #12ZG59-200'-d,975'c°nn (Ar°d195639j 2261041 I. #12ZG5p -2 25' - O B75' coon. (Rmd 195RE01 B P-5➢0'-0.75'cnnn.-T.,n-w.c.1Pmd-22wa0 J ,a122G-50-Z50"-0.075'rnnn -TR4-[Bond C P-500--0.75•conrr-20-C4PIr 1i70187t 195362) D P-DAil'-075'wnn.-H90-TraAs,29'-C-tF.Ck K 912SC-50-253'-0.875'1nnn Trod f95264) 222377) L 012ZC-58-275°-0875'eann.(Pmd19D289) E #T2ZC-SB-175"-1.UU"umn-TR1-iPirad Id p127G55-390'-©E75' conn.(Trdd 1R55Pt1 MATERIAL STRENGTH GRADE Fy I Fu I GRADE I FY I Fu A577-50 IM.1 166 ks1 A572-69 160 ksl 17S hs AW as kb I 5d ks. TOWER DESIGN NOTES 1. Tower is located in Broward County, Florida. 2. Tower designedfor Exposure C to the-TIA-222-G Standard. 3. Tower designed fora 140 mph basic wind in accordance with the TIA-222-G Standard. 4. Deflections are based upon a 60 mph wind. S. Tower Structure Class III. 6. Topographic Category f with Crest Height of DAD 8 7. TOWER RATING. 99.5% ALL REACTIONS ARE FACTORED MAX. CORNER REACTIONS A T BASE: DOM. 842 K UPLIFT -731 K SHEAR: 93 K AXIAL 97K SHEAR MOMENT 150 K 23151 kip-ff TORQUE 97 fup-ft REAC77ONS -140 mph IMNO valnaont 1545 PidCo Drive Plymouth, IN Phone', 574-936-4221 FAX: JA Quotation 334251-02 V-33 x300' Che ` MoWrofa Solutions ° "by SKK Ana°• c°de- TIA-222-G NTS Pam - Hd EA P25 System and Services Agreement (R1422515R1/P1) Page 67 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 F A n a r_�ryy 2v m R U w € i7 ra w R E 2 - C F i s F Y 4 g 390 on IR' Rl Au aft m e 28C Q it mt o tt 2ae o n 300,a ft 10C Oft 60.0 it 14C_O Oft t20.0 ft h09r1 i eQott BO—aft 400fr 200tt dda DESIGNED APPURTENANCE LOADING TYPE ELEVATION TYPE ELEVATION 2 1 - LRE with P 6" 11Chmine red (arm=1151 300 1'C 07-11 27L 0•U--.1 Side A.(64"pipe? 275 Beacon e00 TC907-11 275 20' 9eacon Eatapder 900 5'Uni1—f SideArm(84" PIP11 275 Cc9D7-a 360 C m-11 775 B'Unversal-S.d¢A-N4"tape) 30U E!Unrve ISde Arm (e4"pipe) 275 Cc00i.14 200 CC807-11 {50%wture) 275 O'UnNEr9g Side Arm 184"pip£) 3W E'Unrverssl 5ideAm(84"pipe)i5- tuwrel 275 tin Tndbbaiepie5428E-071 iT 30n 6'Plvat Side Artn (SQ"pipe) 800 CC807-11(50%fu[ure7 275 Bird Te tlm r1egle542HE-83IA I 300 0'ur—sat 51 de Arm (64"pipe) [5 d°'v iU_) 275 B'Plw[Side A-m 50"pipe) Don CC807-11 160%future) 900 CC307-11 (50%Uw) 275 a'UONersa151deArrn(A4" prpe)(50% wwre) a00 F Universal Sde Arm(54"pipe)(58% wture) 275 CC002.1f 150%fuYurel ma 2.112-X22'Sch 411 113 A'UnNersal Side Arm (A4" pipe) (5C% tut") 309 2 ?2'x 22S[h U 113 PADa-599C(wf Rad—Aserm 13 Birtl Temnolotl'es 42HE-831-01-F I50% wwre) 300 PADMDBC WRadpmeA=MEd) i56%ware 113 E'Pi— Side Arm(50' pip2)(58% iuwre) Pon 3-x24'sr 4n 9d PAC15-59BC£r°"7Radoft AswriW) 90 BrtaTerstn°Iaq�es428E B31-n1T (40%30p wklrei 8'Y24.5M4C Cd B'arwt�eegrmf58^vrpa)[5U'� wwre) 3ne P1k[13-59RC(w1RadbmAse4madi 15n%wwra 9Q SYMBOL LIST MARK SIZE MARK SIZE A P-4.00'-n 75'mnn.-20'-GTrsns R"Er(Rrod H #12ZG59-200'-d,975'c°nn (Ar°d195639j 2261041 I. #12ZG5p -2 25' - O B75' coon. (Rmd 195RE01 B P-5➢0'-0.75'cnnn.-T.,n-w.c.1Pmd-22wa0 J ,a122G-50-Z50"-0.075'rnnn -TR4-[Bond C P-500--0.75•conrr-20-C4PIr 1i70187t 195362) D P-DAil'-075'wnn.-H90-TraAs,29'-C-tF.Ck K 912SC-50-253'-0.875'1nnn Trod f95264) 222377) L 012ZC-58-275°-0875'eann.(Pmd19D289) E #T2ZC-SB-175"-1.UU"umn-TR1-iPirad Id p127G55-390'-©E75' conn.(Trdd 1R55Pt1 MATERIAL STRENGTH GRADE Fy I Fu I GRADE I FY I Fu A577-50 IM.1 166 ks1 A572-69 160 ksl 17S hs AW as kb I 5d ks. TOWER DESIGN NOTES 1. Tower is located in Broward County, Florida. 2. Tower designedfor Exposure C to the-TIA-222-G Standard. 3. Tower designed fora 140 mph basic wind in accordance with the TIA-222-G Standard. 4. Deflections are based upon a 60 mph wind. S. Tower Structure Class III. 6. Topographic Category f with Crest Height of DAD 8 7. TOWER RATING. 99.5% ALL REACTIONS ARE FACTORED MAX. CORNER REACTIONS A T BASE: DOM. 842 K UPLIFT -731 K SHEAR: 93 K AXIAL 97K SHEAR MOMENT 150 K 23151 kip-ff TORQUE 97 fup-ft REAC77ONS -140 mph IMNO valnaont 1545 PidCo Drive Plymouth, IN Phone', 574-936-4221 FAX: JA Quotation 334251-02 V-33 x300' Che ` MoWrofa Solutions ° "by SKK Ana°• c°de- TIA-222-G NTS Pam - Hd EA P25 System and Services Agreement (R1422515R1/P1) Page 68 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.17 Site Name: West Hollywood West Hollywood is a new Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the site will receive a new 24' X 32' precast shelter with a new DC Power System, generator and a new 300' self - supported tower. Figure 2-19: West Hollywood Site Details: Tower Work: • Construct pier and pad type tower foundations including excavation, rebar, and concrete • Erect new 300' self -supported tower. • Supply and install grounding for the tower base. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower -top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install two Microwave Dishes. • Perform sweep tests on transmission lines. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install 1 ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 69 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-14: System and Site Improvements Ground Elevation (Ft.) 17 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 26 03 37.2 80 12 00.0 Site Owner Broward County New Tower Ht (Ft.) New Tower Type 300 Self Supported IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type 60 80 Light New Ice Bridge Length (Ft.) 15 New Shelter Type Custom pre -cast New Shelter Width (Ft.) New Shelter Length (Ft.) 24 32 New Fuel Tank (Gal.) New Fuel Tank (Type) 1000 Diesel New Generator (kW) New Generator (Type) 175 Outdoor New Electrical Circuits Amps/Volts Type Cable (Ft.) 600-amp; 120/240-volt, three-phase Underground 50 New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)14 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 660 660 915 N/A 335 14 Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 70 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 F A n a r_�ryy 2v m R U w € i7 ra w R E 2 - C F i s F Y 4 g 390 on IR' Rl Au aft m e 28C Q it mt o tt 2ae o n 300,a ft 10C Oft 60.0 it 14C_O Oft t20.0 ft h09r1 i eQott BO—aft 400fr 200tt dda DESIGNED APPURTENANCE LOADING TYPE ELEVATION TYPE ELEVATION 2 1 - LRE with P 6" 11Chmine red (arm=1151 300 1'C 07-11 27L 0•U--.1 Side A.(64"pipe? 275 Beacon e00 TC907-11 275 20' 9eacon Eatapder 900 5'Uni1—f SideArm(84" PIP11 275 Cc9D7-a 360 C m-11 775 B'Unversal-S.d¢A-N4"tape) 30U E!Unrve ISde Arm (e4"pipe) 275 Cc00i.14 200 CC807-11 {50%wture) 275 O'UnNEr9g Side Arm 184"pip£) 3W E'Unrverssl 5ideAm(84"pipe)i5- tuwrel 275 tin Tndbbaiepie5428E-071 iT 30n 6'Plvat Side Artn (SQ"pipe) 800 CC807-11(50%fu[ure7 275 Bird Te tlm r1egle542HE-83IA I 300 0'ur—sat 51 de Arm (64"pipe) [5 d°'v iU_) 275 B'Plw[Side A-m 50"pipe) Don CC807-11 160%future) 900 CC307-11 (50%Uw) 275 a'UONersa151deArrn(A4" prpe)(50% wwre) a00 F Universal Sde Arm(54"pipe)(58% wture) 275 CC002.1f 150%fuYurel ma 2.112-X22'Sch 411 113 A'UnNersal Side Arm (A4" pipe) (5C% tut") 309 2 ?2'x 22S[h U 113 PADa-599C(wf Rad—Aserm 13 Birtl Temnolotl'es 42HE-831-01-F I50% wwre) 300 PADMDBC WRadpmeA=MEd) i56%ware 113 E'Pi— Side Arm(50' pip2)(58% iuwre) Pon 3-x24'sr 4n 9d PAC15-59BC£r°"7Radoft AswriW) 90 BrtaTerstn°Iaq�es428E B31-n1T (40%30p wklrei 8'Y24.5M4C Cd B'arwt�eegrmf58^vrpa)[5U'� wwre) 3ne P1k[13-59RC(w1RadbmAse4madi 15n%wwra 9Q SYMBOL LIST MARK SIZE MARK SIZE A P-4.00'-n 75'mnn.-20'-GTrsns R"Er(Rrod H #12ZG59-200'-d,975'c°nn (Ar°d195639j 2261041 I. #12ZG5p -2 25' - O B75' coon. (Rmd 195RE01 B P-5➢0'-0.75'cnnn.-T.,n-w.c.1Pmd-22wa0 J ,a122G-50-Z50"-0.075'rnnn -TR4-[Bond C P-500--0.75•conrr-20-C4PIr 1i70187t 195362) D P-DAil'-075'wnn.-H90-TraAs,29'-C-tF.Ck K 912SC-50-253'-0.875'1nnn Trod f95264) 222377) L 012ZC-58-275°-0875'eann.(Pmd19D289) E #T2ZC-SB-175"-1.UU"umn-TR1-iPirad Id p127G55-390'-©E75' conn.(Trdd 1R55Pt1 MATERIAL STRENGTH GRADE Fy I Fu I GRADE I FY I Fu A577-50 IM.1 166 ks1 A572-69 160 ksl 17S hs AW as kb I 5d ks. TOWER DESIGN NOTES 1. Tower is located in Broward County, Florida. 2. Tower designedfor Exposure C to the-TIA-222-G Standard. 3. Tower designed fora 140 mph basic wind in accordance with the TIA-222-G Standard. 4. Deflections are based upon a 60 mph wind. S. Tower Structure Class III. 6. Topographic Category f with Crest Height of DAD 8 7. TOWER RATING. 99.5% ALL REACTIONS ARE FACTORED MAX. CORNER REACTIONS A T BASE: DOM. 842 K UPLIFT -731 K SHEAR: 93 K AXIAL 97K SHEAR MOMENT 150 K 23151 kip-ff TORQUE 97 fup-ft REAC77ONS -140 mph IMNO valnaont 1545 PidCo Drive Plymouth, IN Phone', 574-936-4221 FAX: JA Quotation 334251-02 V-33 x300' Che ` MoWrofa Solutions ° "by SKK Ana°• c°de- TIA-222-G NTS Pam - Hd EA P25 System and Services Agreement (R1422515R1/P1) Page 71 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.18 Site Name: Pompano Beach Club Pompano Beach Club is a new Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the existing Roof top equipment room and building backup power (generator) will be used. A new DC Power System will be installed. The equipment room will be modified to support the equipment. Any services or work necessary to be performed at this site to achieve the specifications of the System and meet the other requirements of the Agreement shall be completed by Motorola as part of the scope of services hereunder. Site Details i Figure 2-20: Pompano Beach Club Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter one, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Install five antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install two tower top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install two Microwave Dishes. • Install Elliptical waveguide as required. P25 System and Services Agreement (R1422515R1/P1) Page 72 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install one ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. Existing Facility Improvement Work: • Fabricate steel weight distribution plate and make electrical modifications in order for the existing shelter to receive the new DC Power System. • Upgrade site grounding to the latest revision of R56 • Provide all necessary equipment and services necessary to fully cutover users from the old system to the new system • Upgrade equipment and supporting systems to optimal conditions, including the following: — Ensure roof is in good condition and free of leaks — Repair any damaged flooring or siding to equipment room — Seal equipment room to prevent pest entry — Service all HVAC units and upgrade and/or replace as necessary to ensure proper cooling of equipment • Replace existing 200 amp electric panel with new panel • Interface to existing 3 Phase transformer P25 System and Services Agreement (R1422515R1/P1) Page 73 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-15: System and Site Improvements Ground Elevation (Ft.) 10 Site Acquisition No zoning No A&E Services Yes Latitude Longitude 26 05 48.0 80 06 26.0 Site Owner Pompano Beach Club Existing Tower Ht (Ft.) Existing Tower Type 300 Roof Top IMPROVEMENTSSITE New Compound/Expansion Size Width (Ft). Length (Ft.) ring Type N/A N/A t�NA NewIce Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator /Transfer Switch New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 5 2 2 New RF Lines (Linear Ft.)` 1/2-inch 7/8-inch 1-1/4- inch 1-5/8- inch Wave Guide 200 500 N/A N/A 200 "Or as required. P25 System and Services Agreement (R1422515R1/P1) Page 74 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.19 Site Name: EMS EMS is an existing Broward County Radio site. In accordance with Solicitation R1422515P1 Appendix B- Addendum 2, the existing 24' X 32' shelter, tower and generator will be used. A new DC power system will be provided. The existing UPS will be decommissioned and removed. Figure 2-21: EMS Site Details: Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. • Decommission antennas, feed lines, and equipment associated with the "backup" system for the existing system Antenna and Transmission Line: • Install three antennas for the RF system. • Supply and install side arm(s) for all antenna and dish mounts. • Install one tower -top amplifiers. • Install 1/2-inch transmission line as required. • Install 7/8-inch transmission line as required. • Install 1-1/4-inch transmission line as required. • Install three Microwave Dishes. • Perform sweep tests on transmission lines. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Supply and install 1 ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition P25 System and Services Agreement (R1422515R1/P1) Page 75 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-16: System and Site Improvement Ground Elevation (Ft.) 10 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 26 09 14.4 80 10 38.3 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 400 Guyed tower PROVEMENTS New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type N/A N/A N/A New Ice Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator (kW) New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A N/A New Antenna: RF New Antenna: TTA New MW Dish: 3 1 3 New RF Lines (Linear Ft.)" 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide 450 450 900 N/A 355 "Or as required. P25 System and Services Agreement (R1422515R1/131) Page 76 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2.20 Site Name: EOC Emergency Operations Center (EOC) is an existing Broward County facility. In accordance with Solicitation R1422515P1, Appendix B- Addendum 2, this will be a Microwave site on the system. Figure 2-22: EOC Site Details: Site Engineering: • Perform National Environmental Policy Act (NEPA) Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 Code of Federal Regulations (CFR) Chapter 1, subsection 1.1307 that may be potentially impacted by the construction activity. • Provide a structural engineering analysis for antenna support structure, to support the antenna system. • Provide tower climbing and tower mapping services to collect information about structural members and existing equipment. Antenna and Transmission Line: • Supply and install side arm(s) for all antenna and dish mounts. • Install 2 Microwave Dishes. • Perform sweep tests on transmission lines. • Install Elliptical waveguide as required. • Perform alignment of each of the microwave paths to ensure that the microwave dishes are optimally positioned. • Perform sweep tests on transmission lines. • Supply and install 1 ground buss bar at the bottom of the antenna support structure for grounding RF cables before they make horizontal transition. P25 System and Services Agreement (R1422515R1/P1) Page 77 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-17: System and Site Improvements Ground Elevation (Ft.) 9 Site Acquisition No Zoning No A&E Services Yes Latitude Longitude 26 07 22.5 80 10 37.5 Site Owner Broward County, FL Existing Tower Ht (Ft.) Existing Tower Type 180 Monopole PROVIEMENTS New Compound/Expansion Size Width (Ft). Length (Ft.) Clearing Type N/A N/A N/A New Ice Bridge Length (Ft.) N/A New Shelter Type N/A New Shelter Width (Ft.) New Shelter Length (Ft.) N/A N/A New Fuel Tank (Gal.) New Fuel Tank (Type) N/A N/A New Generator (kW) New Generator (Type) N/A N/A New Electrical Circuits Amps/Volts Type Cable (Ft.) N/A N/A 2 New Antenna: RF New Antenna: TTA New MW Dish: N/A N/A 2 New RF Lines (Linear Ft.)17 1/2-inch 7/8-inch 1-1/4-inch 1-5/8- inch Wave Guide N/A N/A N/A N/A 260 17 Or as required. P25 System and Services Agreement (R1422515R1/131) Page 78 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SECTION 3 RESPONSIBILITIES AND ASSUMPTIONS The following description of responsibilities and assumptions is provided to clarify the parties' respective responsibilities. In the event of a conflict between anything set forth herein and the Specifications or the Final Acceptance Criteria, the Specifications and the Final Acceptance Criteria shall govern the responsibilities of Provider and the requirements for Final Acceptance. 3.1 Motorola Solutions Responsibilities Motorola shall be responsible for the following: 3.1.1 Site Engineering for New Sites • Prepare site construction drawings showing the layout of various new and existing site components. • Conduct site walks to collect pertinent information from the sites (e.g., location of Telco, power, existing facilities, etc.). • Perform a boundary and topographic survey for the property on which the communication site is located or will be located. • Prepare a site exhibit and sketch of the site to communicate to the property owner of the lease space and planned development at the particular site location. • Prepare record drawings of the site showing the as -built information. • Perform construction staking around the site to establish reference points for proposed construction. • Perform NEPA Threshold Screening, including limited literature and records search and brief reporting, as necessary to identify sensitive natural and cultural features referenced in 47 CFR Chapter 1, subsection 1.1307 that may potentially be impacted by the construction activity. This does not include the additional field investigations to document site conditions if it is determined that the communication facility "may have a significant environmental impact" and thus require additional documentation, submittals, or work. Regional Environmental Review (RER) report submittals if required by FEMA have not been included. Perform Cultural Resource study as needed to identify sensitive historical and archaeological monuments that might be impacted by construction. • Conduct soil boring tests at tower locations and prepare geotechnical report of soil conditions at the location of tower foundations. • Conduct construction inspection of foundation steel prior to pour, materials testing of concrete and field density tests of backfill to ensure quality construction. • Check tower erection for plumbness, linearity and alignment after installation. • Perform inspection of the site and the work performed by the Contractor to document that the site is built in accordance with the "Site Plans" and document any deviations or violations. • Prepare, submit and track application for local permit fees (zoning, electrical, building, etc.), prepare FAA filings, and procure information necessary for filing. P25 System and Services Agreement (R1422515R1/P1) Page 79 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Any other required site preparation activities identified in the specifications or not immediately identified as a Broward County responsibility. 3.1.2 Site Preparation for New Sites • Obtain the permits such as electrical, building, and construction permits, and coordinate any inspections with local authorities that may be needed to complete site development work. • Provide mobilization costs for the construction crews. • Perform light clearing of brush, grubbing, and disposal of vegetation and shrub growth in the site compound area. • Grade the site compound and 10-foot path around it to provide a level, solid, undisturbed surface for installation of site components. • Supply and install gravel surfacing to a depth of six inches, including herbicide treatment and geotextile fabric installation within the fenced in site compound area, and a three-foot path around it. • Provide silt fence around the compound to control soil erosion. • Supply and install eight -foot -high chain -link fencing with gate around the shelter compound. • Perform site touch-up (fertilize, seed, and straw) disturbed areas not covered with gravel after completion of construction work. • Secure power connection to the site, associated permitting and installation of a meter and disconnect within 50 feet of the shelter location. County will assist with interacting with the applicable utilities to the extent reasonably requested by Motorola, but all services shall be provided at no cost to County. Demarcation points shall be as determined by the applicable utilities. • Any other required site preparation activities identified in the specifications or not immediately identified as a Broward County responsibility. 3.1.3 Site Component Installation for New Sites (New shelter sites are Channel 2, Deerfield, Tamarac, West Lake Park, FS 106, Pompano Beach, West Hollywood and Parkland) • Construct one reinforced concrete foundation necessary for a 24-foot X 32-foot shelter (all new shelters shall be 24 x 32 where physically possible, unless otherwise agreed by the parties). • Construct concrete slab for above -ground diesel tanks at 3000 psi with reinforcing steel necessary for foundations (except for Channel 2 site). • Supply and install one prefabricated 24-foot X 32-foot shelter as specified in Section 5.3 Shelters. (Note: Motorola Solutions agrees with the county in that falling ice impacting the roof of the shelters will not be an issue. However, Motorola Solutions has chosen to exceed the roof loading in order to comply with the intent of the shelter specs (5.3 Shelters, F. Roof, F). As such, Motorola Solutions has increased the roof load by 50% to 150 psf.). • Supply and install diesel fuel tanks, and connect to the generators (except for Channel 2 site). P25 System and Services Agreement (R1422515R1/P1) Page 80 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Supply and install fuel tank monitors on the tanks to monitor low fuel in tanks and run alarm wiring to the building located within 50 feet of the tank (except for Channel 2 site). • Supply and install one standby power generator as noted and ATS, including interconnection wiring between the generator, transfer switch, and site electrical service mains (except for Channel 2 site). • Provide a protected CMU enclosure as noted surrounding the generator and fuel tank (except for Channel 2 site). • Supply and install one single-phase meter pedestal (see individual sites for amperage) and hook-up for electrical service by the local utility. • Provide all trenching, conduit, and cabling necessary for underground hook-up of power to the shelter from nearby utility termination located within 50 cable feet of the shelter. • Supply and install a perimeter grounding system around the compound, shelter and tower (where applicable). The ground system is to tie to the fence and all new metal structures within the compound to meet current Motorola Solutions' R56 standards. • Conduct one three-point ground resistance test of the site. • Supply and install one freestanding 24-inch-wide cable/ice bridge from the tower to the shelter. • Any other required site preparation activities identified in the specifications or not immediately identified as a Broward County responsibility. 3.1.4 Motorola Responsibilities for Existing Sites • Upgrading existing site grounding systems to the latest revisions of R56, including internal shelter grounding, external shelter grounding, tower grounding, and subterranean grounding • Reinforce flooring as necessary to support the DC power system • Evaluate heating and cooling for existing HVAC systems and provide any enhancements necessary • Evaluate floor loading and upgrade floors if necessary to accommodate the weight of the equipment, including the DC plant • Ensure a sufficient number of entry ports, and add additional ports if necessary • Add additional support facilities for the proposed radio network, including but not limited to cable ladders, ice bridge, ground bus bars, etc. • All applicable environmental and permitting (NEPA, SHPO, building permits, etc.) • Provide any facility upgrades necessary to support the cutover, including temporary shelters, entry ports, ice bridge, cable ladders, etc. • Decommission old antennas and feedlines at the conclusion of the project • Reconfigure site power distribution system for DC • Upgrade site electrical system in order to comply with NFPA 70, Article 708 • Provide a site structural analysis for each site • Perform tower mapping to validate existing antenna systems and heights for use in the structural analysis • Motorola will provide electrical upgrades, with respect to breaker panels and circuit breakers in order to accommodate the new DC power system for the new radio system. P25 System and Services Agreement (R1422515R1/P1) Page 81 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Perform electrical and heat loading to determine the full impact at each site, and provide the necessary remediation, if required. • Upgrade shelter and supporting systems to optimal conditions, including the following: o Ensure roof is in good condition and free of leaks o Repair any damaged flooring or siding to building o Seal building to prevent pest entry o Service all HVAC units and upgrade or, if necessary to ensure proper cooling of equipment, replace. (County may elect to replace as part of Optional Services, if the HVAC units are not required to be replaced to ensure proper cooling of equipment.) • Any other required site preparation activities identified in the specifications or not immediately identified as a Broward County responsibility. 3.1.5 Additional Requirements for all Sites • Ensure a fully functioning automatic fire suppression system exists at all sites which is fully compliant with NFPA and all other applicable codes. 3.2 Broward County Responsibilities County shall be responsible for the following: 3.2.1 Broward County Responsibilities for Existing Sites • Pay for the usage costs of power, leased lines, and generator fueling both during the construction/installation effort and on an ongoing basis. • Pay for application fees, taxes, and recurring payments for ownership of the property. • Maintain existing access roads in order to provide clear and stable entry to the site for heavy-duty vehicles and cranes. Sufficient space must be available at the site for these vehicles to maneuver under their own power, without assistance from other equipment. • Arrange for space on the structure for installation of new antennas at the heights on designated existing antenna -mounting structures. The towers will meet all applicable EIA/TIA-222 G structural, foundation, ice, wind, and twist and sway requirements. • Provide any previously procured and currently available as -built structural and foundation drawings of the structure and site location(s) along with geotechnical report(s) if available solely for Motorola reference in conjunction with Motorola Solutions' obligation to conduct a structural analysis and tower mapping at each site. • Allow use of existing support facilities for the antenna cables (cable ladder, entry ports) from the antenna to the equipment room. P25 System and Services Agreement (R1422515R1/P1) Page 82 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3.2.2 Broward County Responsibilities for New Sites • Review site design drawings within thirty calendar days of submission by Motorola Solutions or its subcontractor(s). Should a re -submission be required, the Broward County shall review and approve the re -submitted plans within seven calendar days from the date of submittal. • Pay for application fees, taxes, and recurring payments for ownership of the property. • Provide personnel to observe construction progress and testing of site equipment according to the schedule provided by Motorola Solutions. • Provide a right of entry letter from the site owner for Motorola Solutions to conduct field investigations. 3.2.3 Broward County Responsibilities for All Sites • All recurring and non -recurring utility costs including, but not limited to, generator fuel (except first fill), electrical, and Telco, will be borne by Broward County or site owner. 3.3 Assumptions The following assumptions were utilized by Provider in estimating the schedule and work required, and are stated here solely for clarification purposes. Failure of any assumption stated in this Section 3.3 shall not diminish or alleviate any obligation of Provider or modify the scope of services or the cost to County of the services required under this Agreement, unless expressly approved by the County in writing. 3.3.1 Assumptions for Existing Sites • No prevailing wage, certified payroll, or mandatory minority workers are required for this work, other than to the extent expressly set forth in the Agreement. • All site work is assumed to be done during normal business hours as dictated by time zone (Monday thru Friday, 7:30 a.m. to 5:00 p.m.). 3.3.2 Assumptions for New Sites • All site work is assumed to be done during normal business hours as dictated by time zone (Monday thru Friday, 7:30 a.m. to 5:00 p.m.). • Site will have adequate electrical service for the new shelter and tower. Utility transformer, transformer upgrades, line, or pole extensions have not been included. • Hazardous materials are not present at the work location prior to commencement of work by Motorola. Testing and removal of pre-existing hazardous materials found during site investigations, construction or equipment installation will be the responsibility of the Broward County. P25 System and Services Agreement (R1422515R1/P1) Page 83 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • The schedule is based on a maximum of 30 days will be required for obtaining approved building permits from time of submission. Motorola is responsible for obtaining building permits, and will not hold the County responsible for delays in the permitting process. • Based on Motorola Solutions' assessments during site walks, no improvements are required for concrete trucks, drill rigs, shelter delivery, and crane access. Therefore, Motorola will be responsible for these upgrades if the determination made during the site walks was incorrect. • Subsurface conditions for tower design are based on Presumptive Sand soil parameters, as defined by EIA/TIA-222-G. Motorola will be responsible for any additional work or materials if this assumption is incorrect. • The new tower locations will pass the FAA hazard study, zoning, FCC, and environmental permitting. To the extent any failure is due to design, construction, or any work undertaken by Motorola under this Agreement, Motorola will be responsible for rectifying any failures. • Tower and foundation sizing is based on the tower loading requirements as a result of the RF Antenna System design and the Microwave Antenna System design (i.e., dish sizes and locations obtained from paper path studies). If as a result of NEPA studies, any jurisdictional authority should determine that a communications facility "may have a significant environmental impact," the environmental impact studies or field testing and evaluation related to such determination have not been included. • A waiver to zoning requirements like setbacks, tower height limitations, etc. required by the Final Design can be obtained. • The soil resistivity at the site is sufficient to achieve resistance of ten ohms or less. Communications site grounding will be designed and installed per Motorola Solutions' Standards and Guidelines for Communications Sites (1356). Motorola will be responsible for any additional work or materials if this assumption is incorrect. • Underground utilities are not present in the construction area, and as such no relocation will be required. • Spoils from the tower foundations can and will be transported to a proper facility away from the site by Motorola. SECTION 4 SUBSTANTIAL AND FINAL COMPLETION ACCEPTANCE CRITERIA Each site will be deemed separately tested and determined to have achieved Substantial Completion upon written notice by the County Contract Administrator of successful completion of the Substantial Completion Criteria set forth below. Each Site will also be separately tested and determined to have achieved Final Completion upon written notice by the County Contract Administrator of successful completion of the Final Completion Criteria set forth below. Substantial Completion Criteria • Site development completed per issued for construction (IFC) drawings, project requirements, and contractual obligations (including any Broward County/Motorola Solutions approved changes) and approved by the County: P25 System and Services Agreement (R1422515R1/P1) Page 84 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 — This shall be confirmed by DB-Firm and reviewed with Motorola Solutions construction manager and project manager before inspections occur. • All jurisdictional and contractual required testing and inspections to be performed by the DB-Firm. (Contractual testing and inspections defined and agreed to with project team and Broward County prior to project kickoff; Provider is solely responsible for conducting, coordinating, and paying for all jurisdictional testing and inspections). • Motorola Solutions site development checklist shall be completed and signed off by DB-Firm prior to Broward County inspection (review with project team and Broward County and amend checklist as required at project kickoff or before work begins). • R56 audit completed by third party and checklist approved by Broward County, with all issues resolved by Provider and checklist approved by Broward County. • Pictures demonstrating compliance with all acceptance criteria • Site turnover package completed by Provider and turned over to Motorola Solutions (as defined and agreed to with the project team and Broward County). • All punch list and deficiencies shall be completed by Provider prior to Broward County and Motorola Solutions inspections. • Written certification by Consultant and Contract Administrator, in their reasonable sole discretion, that the work at each Site is at a level of completion in substantial compliance with the Agreement and SOW A-2 such that all conditions of permits and regulatory agencies have been satisfied and County can enjoy use or occupancy and can use or operate the Site in all respects for its intended purpose. A Certificate of Occupancy (or a Temporary Certificate of Occupancy or other alternate municipal/county authorization for limited or conditional occupancy acceptable to the Contract Administrator) must be issued for Substantial Completion to be achieved, however, the issuance of a Certificate of Occupancy or the date thereof are not to be determinative of the achievement or date of Substantial Completion. Final Completion Criteria: • All Sites have achieved Substantial Completion. • Successful completion of thirty (30) day Burn -in Period without Severity 1 or 2 Event. • Any and all action items identified in the R56 audit gaps, including without limitation gaps in compliance, recommendations to bring site up to standard, or other recommended corrective action, have be addressed and fully resolved by Provider and such resolution verified and approved by Broward County. • All punch list items are fully resolved to County's reasonable satisfaction prior to Final Completion. • Any acceptance criteria that was not fully met for Substantial Completion has been fully completed. P25 System and Services Agreement (R1422515R1/P1) Page 85 of 85 SOW A-2 (Civil and Infrastructure) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SOW A-3 Microwave System SECTION 1 DIGITAL MICROWAVE NETWORK A. The Microwave System shall consist of the following components: 1. Point-to-point digital microwave radios 2. Microwave antennas 3. Antenna systems 4. Alarms 5. Network Management System B. The digital microwave network shall be implemented in accordance with the Project Schedule. C. The Software and Equipment provided as part of this SOW A-2 are included in Schedule 1 and Schedule 2. D. The Microwave System shall be implemented in parallel with the Radio System, unless otherwise approved by the Contract Administrator. E. The Microwave System shall support the full set of backhaul requirements for the Radio System defined in SOW A-1. 1.1 Minimum Requirements A. The digital microwave backhaul network shall consist of monitored hot standby (MHSB) or ring -protected, point-to-point licensed microwave hops. B. Microwave terminal equipment shall include transmitter, receiver, modem, power supply, automatic switching device, multiplexer, service channel(s), and all associated interconnections to provide a complete and functional system. C. The radio shall deliver two -frequency, full -duplex operation. Space diversity configurations are acceptable, if necessary, to meet reliability requirements. P25 System and Services Agreement (R1422515R1/131) Page 1 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 D. The network shall support MPLS routing to support seamless integration and ad -hoc routing with landline-based Ethernet connections. E. Microwave connectivity shall be provided to all radio site and dispatch locations. F. The microwave configuration shall include a minimum of two loops, with each loop serving an evenly divided number of locations. G. Redundant landline-based Ethernet connectivity shall be provided (utilizing circuits provided by AT&T through Broward County) to all critical infrastructure locations (system controllers, prime controllers, dispatch locations) as well as the EMS, Coconut Creek, Channel 2, and Davie locations identified in Appendix B. Radio backhaul must seamlessly route and self -heal between the combined microwave and landline network. Motorola shall be responsible for the interface to the circuits provided by Broward County. H. Capacity: 1. Each hop shall be equipped for the radio network requirements for the equipment defined in SOW A-1, and existing legacy radio system channels to include the County's 28-channel SmartX system using the T1 protocols, the County's 4-site alphanumeric paging system, and any other equipment mutually agreed to by the Provider and the County.. 2. Each hop shall deliver a minimum Ethernet payload capacity of 155 megabits per second (Mbps) or more, as required to serve the network identified in SOW A-1. All path designed for 155 Mbps airlink capacity, the common path to both rings can deliver 254 Mbps capacity. 3. Provider shall cutover the microwave system in advance of the radio system. Performance Objectives: 1. Each microwave hop shall be designed to meet or exceed a one-way, end -to -end, per -path availability of 99.999% for 10-6 BER at the required capacity. P25 System and Services Agreement (R1422515R1/P1) Page 2 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. The meantime between failures (MTBF) for the MHSB transceiver equipment shall exceed 25 years. 3. The expected minimum field MTBF is as follows: ECLIPSE MTBF VALUES IN U MODULES Assembly Expected Mknimum Field MTBF, Years Indoor Chassis. IDC 930 I ndoor Ch asses Extended, IDCe 6D3 Netwcrh Controller Card 162 FAN Card (IRU) 2829 FAN Card (2RL1) 1281 Node Protection Card (NPC) 237 ALJX Cart? (ALIX) 408 Radio A ss Card (RACBOM) 240 Data Access Card (4x) 897 Data Access Card (1 Sx) 612 Data Access Cart) (3xD63) 1110 Data Acces8 Card (1 x159o) 218 Data Access Card (2x155ol 134 Data Access Card (2059e) 705 Data Access Card (1 x155oM) 330 Data Access Card (GE3) 432 f+letwo6. Convergence Module (NCM) 369 INDOOR RADIO FREQUENCY UNITS {iRua Assembly Expected Minimurn Field MTBF, Years IRD600(4) 1-?',I IRD600EHP 8r C. This ORU600 MTEF regvoe aloes not h?cbde tlA@ remavabJ@ FAN moduA@. wrricb is assumed to Le a rna�nterrarrce ftem, rWweaWe every 3 years. P25 System and Services Agreement (R1422515R1/P1) Page 3 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Aimn Expected M nirn n Rind MTBF. Yaars IDG * #UGC + FAN * RAC60 + DACGE" T :::) ODOM IDCe + NCG * 2xFAN * RAC60 * DAGGE3 + 40 DAC16x + IRU6000 IDCe + NCG * 2xFAN * RAC60 * DACGE3 + DAC16x + 1RU800 EHP J. Frequency: 1. Provider is responsible for all microwave frequency research, prior coordination and preparation of all associated FCC license applications, and submittals on behalf of the County. 2. The County shall be responsible for coordination fees and licensing fees, if any, and signatures, if applicable. 3. The Provider shall utilize the 6 GHz and 11 GHz frequency bands for each hop based on the design in section 1.1.5 and FCC Part 101 regulations. K. Data Rates: 1. DS1 bit rate —1.544 Mbps (as defined by Bellcore GR-499-CORE, Section 9.3; ANSI T1.102; ITU-T 703) 2. DS3 bit rate—44.736 Mbps (as defined by Bellcore GR-499-CORE; ANSI T1.102; ITU- T 703) 3. OC-3 Optical bit rate—155.52 Mbps (as defined by ANSI T1.106/88) 4. Ethernet Interface bit rate — 10/100/1000 Mbps (as defined by IEEE 802.3) L. Transmitter: 1. Provider shall provide transmit output power referenced to the antenna port. L6 GHz 30 MHz/128 QAM Tx out: 28/31/37 dBm SP/HP/EHP 11 GHz 40 MHz/256 QAM Tx out: 22.5/25.5/32 dBm SP/HP/EHP 2. Transmit output power shall be software adjustable. 3. Automatic Transmit Power Control (ATPC) shall be available. 4. A switch from the main transmitter to the standby transmitter shall not result in a system outage. Provider shall describe expected switchover time. 5. Transmit Switching is not hitless, but It is within 50 ms for local alarms P25 System and Services Agreement (R1422515R1/131) Page 4 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. Radios shall be equipped with redundant power amplifiers. Switching between power amplifiers shall not result in a system outage. M. Receiver: 1. Provider shall provide a guaranteed receiver threshold. L6 GHz 30 MHz/128 QAM Threshold: -72.25 dBm 11 GHz 40 MHz/256 QAM Threshold: -64.75 dBm 2. Provider shall provide performance criteria of the microwave radios for the following: a. Co -channel interference b. Adjacent -channel interference c. Dispersive fade margin DFM: 50/40 L6 GHz profiles above/11 GHz profiles above 3. The receiver shall be designed so as to ensure that the receiver with the better performance is operational at any given moment. Provider shall equip radios with a 10:1 split to prevent frequent switching. 4. Transfer to the backup receiver shall not result in a system outage. N. Antenna System: 1. Microwave antennas shall be compatible with the radio frequency bands and conform to applicable FCC requirements. Solid parabolic type, Category A antennas shall be used in accordance with FCC Part 101.115 for use in public safety -grade communications systems. Provider shall utilize the smallest dish sizes possible that will satisfy the link reliability requirements. 2. A pressurized elliptical waveguide shall be used. Connectors shall be standard, premium type, and compatible with the antenna and EIA radio interfaces. 3. The following mounting equipment shall be installed per manufacturer specifications: a. Hanger kits (no snap -on kits) P25 System and Services Agreement (R1422515R1/P1) Page 5 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 b. Hoisting grips c. Cable boots d. 2 Stiff Arms per dish antenna 4. An automatic dehydrator/pressurization system shall be provided to maintain at least 5 pounds per square inch gauge (psig) positive pressure of conditioned air in the elliptical waveguide and antenna feed unit. Individual pressure gauges on a distribution manifold shall be provided for each line. 5. All installed antenna/transmission lines shall be purged, pressure tested, and tested for low voltage standing wave ratio (VSWR) using return loss measurements. The minimum VSWR shall be 1.5:1 with a return loss of 14 dB. 6. All RF paths shall be tested to demonstrate proper antenna alignment by measuring the net path loss between sites as measured at the equipment rack interface. 0. Channel Bank/Multiplex equipment: 1. The Provider shall provide digital channel bank multiplex equipment or equivalent. (T1 cards provided on the radio to provide native T1 interface to the existing system.) a. If necessary, the Provider shall provide multiplex equipment (M13 mux) to convert DS3 signals to 28 DS1s. b. All multiplex equipment shall be equipped with standby switching and alarms. The equipment also shall be capable of remote alarm/control. c. The system must support an interface to the existing Motorola TeNsr channel banks and Larus route switch for ease of integration with the existing radio system. P. Microwave NMS: 1. Provider shall provide a single service channel, or order wire, for each microwave terminal. The service channel shall be accessible via a single RS 232C data circuit and provide a single voice circuit. P25 System and Services Agreement (R1422515R1/131) Page 6 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 2. A modern VOIP Digital Orderwire is included and shall be provided by Motorola. 1.2 Microwave Engineering A. Provider shall conduct physical path surveys to assure that all paths meet proper clearance criteria. B. Provider also shall conduct mandatory site visits at all sites and notify the County of any site modifications necessary for the microwave hop. C. Provider shall provide antenna centerline mounting height recommendations, based upon the information gathered during the physical path surveys and site visits. D. Provider shall include fade margin calculations with the proposal, showing the preliminary antenna sizes, system gains, and system losses. E. Radomes shall be provided for each microwave antenna. F. The equipment shall be type accepted for licensing under Part 101 of the FCC Rules and Regulations. 1.3 Remote Terminal Units (RTUS) A. RTUs shall be provided in sufficient quantities to monitor the entire network, which equipment is included in the itemized Equipment list set forth in Schedule 1 to SOW A-1, including: 1. Microwave radios, channel banks, etc. 2. Data network equipment, including routers, switches, etc. 3. Dehydrator 4. Any other alarmable component of the microwave system 5. Site environmental alarms are not required. B. RTUs shall be fully compatible with network management terminals (NMTs) supplied C. RTUs shall support the following points: 1. Status/alarms — 48 minimum, expandable to 256 points 2. Control outputs — 8 minimum, expandable to 32 P25 System and Services Agreement (R1422515R1/P1) Page 7 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3. Analog inputs — 8 minimum, expandable to 16 D. RTUs shall provide time stamp and system time synchronization. E. Terminations for all points shall be provided on suitable terminal blocks providing ease of installation, testing, and maintenance. 1.4 Microwave Backhaul Design To provide reliable connectivity between the radio system sites and the dispatch locations, the microwave system is a state of the art MPLS Layer 3 backhaul network using Aviat Eclipse IRU600 v3 radios and CTR 8611 MPLS routers. The system shall include NO SINGLE POINT OF FAILURE, including IP, T1, or any other protocols that will support the new or legacy radio systems. The microwave backhaul network consists of 18 microwave links, operating in the 6 and 11 GHz bands, which have been configured in two interconnected rings. The rings have been designed with a shared path between them (EMS to Core), rather than intersecting at a single site, with the rest of the sites distributed between rings with nine and ten sites per ring. This will provide additional reliability to the network, by preventing a single site failure from separating the rings. The link that will be shared between the two rings was selected due to its short distance, which will allow it to operate at a higher modulation and reliability. This will allow for that link to provide a higher capacity than the other links under most operating conditions. The network layout used in the design has been provided in the figure below. P25 System and Services Agreement (R1422515R1/P1) Page 8 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 �P,1&:0 vs La a-b sa M4� ._...... wu6cP to tecw ao M+ts ' 1:enoMtsa�tnwewse�so fft Pm V]I1 C44.WPAR. 265aw 254 wbp W LT[LUCi11HEE fob ❑ MmoPae ❑ PWNp ' Aviat ero9 PAM- . wx w - Pr SL-hA157525�8�.d2 Figure 1-1. P25 System and Services Agreement (R1422515R1/P1) Page 9 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Typical 3-Direction Site FF;:;:•••::r••;• LOT 1 LOT 2 SLOT 3 FAN o LOT 4 SLOT 5 SLOT 6 o L),T, � o WT3 ._, o I-aT .I e_ O JOT 1- O ( Typical 2-Direction Site IRU600 v3 RF Shelves INUe Redundant Power Supply O Redundant Ethernet Cards (1 per direction)O Redundant Controller functions O 0 0 M - CTR 8611 PLS Router Redundant Power Supply (D Redundant Ethernet Cards (1 per direction) Redundant Controller Card O O IRU600 v3 - RFShelf O LOT 1 SLOT 2 SLOT 3 LOT, SLOTS SLOT SLOT �e LaT, ,e L,1 INUe Redundant Power Supply O Redundant Ethernet Cards (1 per direction)O Redundant Controller functions O • • CTR 8611 MPLS Router O" (Do Redundant Power Supply O O = •O- • Redundant Ethernet Cards (1 per direction)O O Redundant Controller Card � O , 4, 0 J. • P25 System and Services Agreement (R1422515R1/P1) Page 10 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ISB�E EIA 11611E 6diE e xM oma�mm Paddand Ana: _ IN'Wo"UGHz9M1Mlx r 164sN eu U" w 11S�1280 V1Y 11, MW 3YMHx _•••_••• Mope hilSB!&0 Coe tCr k RUM VI 1, CAA. URW 265 aw 254 Mhm W 0-01.kl pompano Heat Talr — PYya Markham Nrk Cory &C 9ltp 1oa EMS �►.� arnucrvaEe P.kd al Irrwrka ❑ ra D MwgOele `-■.. aerie ❑ o�rarq Wa A.Ryaraan Mh d Lake Park Aviat RYIM A..lnr_ sm mco rfLyji Mllemu 6'jstem Layccl Cn .. 3N �x.1a, xx wrn ar-.a'r SLl1A167525 7=2 Figure 1-1: Microwave System Layout Provider will configure the backhaul network as an IP/MPLS overlay on the microwave transport. All microwave paths have been designed with the Aviat IRU600 radio in an all indoor configuration with the non -standby transceivers and CTR 8611 MPLS routers. The ring configuration used in the design, along with the fast path restoration and network reconvergence capabilities of the MPLS assures high availability on the links and minimizes service disruption due to an interconnection failure. This will providethe reliability, quality of service, and bandwidth optimization necessary to support the mission critical needs of the ASTRO 25 radio system. 1.5 Microwave Path Design All microwave paths used in the transport shall exceed Broward County's RFP requirements. All of the paths shall exceed the 155 Mbps of available network throughput required by Broward County, while still maintaining a one-way path availability exceeding 99.999% on all links. The P25 System and Services Agreement (R1422515R1/P1) Page 11 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 path from EMS to Core, which is the intersection point between the two rings, shall maximize bandwidth and reliability, which will allow that link to deliver 254 Mbps of available network throughput. Preliminary Path Profiles are generated from NED digital Terrain Database. Preliminary antenna heights/centerlines were derived based the clearance criteria, which are 100%F1@K=1.33, and 30%F1@K=0.67 for main path and 60%F1@K=1.33 for the diversity path. Antenna centerlines are based on clutter data and assuming 80 ft. obstructions along the paths. The Vigants 1975 reliability model was used for the paths as it is the most robust option when compared to other models. These paths were designed to meet or exceed 99.999% annual one-way reliability per hop at BER threshold of 10-6. Path calculations are based on the radio guaranteed specifications and assuming no diffraction loss on the paths. Antennas are RFS 6ft Standard PAD6-59 and SC3-W100 which meets FCC Class A requirements. The antennas chosen are preliminary and one or more of these antennas may change to high performance or even ultra- high performance models during frequency coordination depending on frequency congestion in the area. 1.6 Racks, Jackfields and DC Power Plants Motorola Solutions will supply the new Eclipse microwave radio system and networking equipment for each site integrated (prewired and pre -tested) through Provider's Factory Systems Integration and Configuration engineering services in a 7.5ft x 19in standard aluminum rack. Each rack will be equipped with one Trimm Breaker panel which is the standard power distribution panel used for the Eclipse platform. The Trimm Breaker Panel will be wired and configured for a redundant power supply with 6A/613 positions. Trimm SNAPAK circuit breakers will be supplied with each panel for the microwave radio system, Jackfields and MPLS routers. Motorola will provide the necessary -48 VDC power input for the microwave radio system. 1.7 VOIP Orderwire The Eclipse platform has the built in capabilities to operate a Voice Over IP (VOIP) Orderwire; each site is equipped with an IP Phone connecting to one of the Eclipse INUe controller card NMS ports. The VOIP packets are transported from site to site out of- band over the Eclipse radio NMS overhead channel. At the site connection point, a Netvanta 7100 IP PBX for VOIP OW is provided. It can support up to 30 SIP phones (upgrade available to 100 SIP phones) and maintain 30+ simultaneous calls. At each site, one rack mounted VOIP Phone is included with a POE injector. 1.8 MPLS Router (CTR 8611) The CTR 8611 router will be provided at all sites to support Ethernet Traffic and providing IP/MPLS capabilities. The CTR 8611 is a modular router that has two slots for hot swappable Switching and Control Modules (SCM), two slots for hot swappable power feeds, four slots for P25 System and Services Agreement (R1422515R1/P1) Page 12 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 line modules and three slots for hot swappable High Speed Modules (HM) providing a forwarding capacity of up to 7.5 Gbps. 1.9 IRU 600 Radio The Aviat Eclipse IRU 600 being provided by Provider is an all -indoor microwave radio that delivers mission critical communications for mobile operators, public safety agencies, governments, and utilities. The IRU 600 delivers superior RF performance and flexible configuration options. The IRU 600 is the latest in a long line of all -indoor microwave solutions from Aviat Networks that delivers market -leading transmitter power performance, with a low loss antenna coupling unit featuring a transmit switch for protected applications, all in an compact form factor and ultra -low power consumption. IRU 600 has been specifically designed with high system gain to lower microwave total cost of ownership by minimizing antenna sizes to lower installation and tower leasing costs. The Eclipse platform is validated to FIPS 140-2 Level 2 and FIPS 197, making it the most secure microwave radio on the market for transporting sensitive data and safeguarding against unwanted and unlawful access. FIPS 140-2 Level 2 validation is the cornerstone for a complete security solution, including Secure management, Payload encryption and RADIUS authentication — especially important for mobile, public safety and government networks that need a comprehensive security solution. 1.10 Network Management System The Eclipse digital microwave radio system being provided by Provider supports network management environments via a Simple Network Management Protocol (SNMP) based Element Management System. The management system for the Eclipse is Aviat Networks ProVision EMS (Element Management System). Provider will provide all necessary software licenses, hardware, and services to meet the RFP requirements and provide a fully functional network management system. ProVision provides full compatibility for monitoring all Aviat Networks products that supports SNMP. This includes the Eclipse, Truepoint 5200, and Constellation microwave radio products. All Legacy (Harris/Farinon) products that are managed only via the proprietary SCAN protocol can also be remotely monitored and managed by ProVision with the use of a FarScan Proxy software not included at this time. ProVision is the strongest element management system available for the Eclipse platform. ProVision support features include: • GUI -based end -to -end Eclipse circuit discovery and provisioning. • Detailed Ethernet throughput monitoring for Capacity Management. Inventory reports capturing all serial and part numbers for every Eclipse nodes and their installed modules in the network. • Automatic back up of Eclipse configuration files Strong Security Performance Data Collection and Network Health Reports for trends analysis. P25 System and Services Agreement (R1422515R1/P1) Page 13 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Remote Software loading and activation Alarm/Event notifications with support for email, SMS and paging, plus audio and visual pop-up notifications. 1.11 Demarcation Points Provided Provider will provide and configure all the interfaces necessary to support the Ethernet interface requirements of the ASTRO 25 radio system design, as well as the legacy radio system T1 requirements. 1.12 Remote Terminal Units (RTUs) The Radio System design includes Remote Terminal Units (RTU) at each location in the system, including sites that have only microwave equipment. The RTUs identified in the Radio Design will be utilized for the microwave system. 1.13 Project Schedule Provider's installation of the Microwave System shall be in accordance with the Project Schedule, unless otherwise approved in writing by the Contract Administrator. Generally, installation begins as soon as site construction work is completed at each site. The radio system FNE installation begins once Microwave is completely installed at all sites. SECTION 2 BACKHAUL SYSTEM IMPLEMENTATION Motorola Solutions will provide the microwave backhaul network to support the P25 system. Motorola Solutions will align the rollout and configuration of Aviat's MPLS-based microwave network consistent with the implementation schedule provided to ensure an efficient system deployment and to comply with the Project Schedule outlined in SOW A-1. Responsibilities and deliverables for Motorola Solutions and the County are defined in the chart below. P25 System and Services Agreement (R1422515R1/P1) Page 14 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Table 2-1: Responsibility Matrix slalomOwl �- .. Motorola Solutions to finalize Microwave Installation is the backhaul network design Motorola Solutions Complete and installation. Motorola Solutions to configure the backhaul network according to the Motorola Solutions Backhaul Results are Available design at each ASTRO for Review 25/backhaul network demarcation point. Motorola Solutions to provide Test Results Provided that backhaul test results to the Motorola Solutions demonstrate network County, demonstrating performance in compliance network performance. with the Specifications County to review the results Review of results is complete for approval. Broward County and results are acceptable and approved. Motorola to secure FCC Documentation of FCC call licenses for the microwave Motorola Solutions signs with associated grant dates, construction buildout system. dates, and expiration dates. All Microwave paths are not final and guaranteed until the Motorola Solutions Physical path survey physical path surveys have been completed. 2.1 Microwave Network Installation Dual Loop 18 Path MPLS Microwave System To provide the required site connectivity for the Motorola Solutions P25 radio system, Motorola Solutions will provide and install Aviat's digital microwave system. Motorola Solutions will perform parallel microwave installation pending the outcome of the structural analysis for the existing towers. If a parallel operation is not possible due to excessive loading, the microwave installation will be completed on a site -by -site and hop -by -hop basis. If this approach is required, Motorola will have sole responsibility for interfacing the new IP microwave system with the legacy TDM microwave system to ensure a seamless microwave cutover without loss of legacy radio connectivity at any point in time. The existing SMARTX SmartZone radio system sites will be connected to the network at the completion of the new microwave acceptance testing. P25 System and Services Agreement (R1422515R1/P1) Page 15 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SECTION 3 PRELIMINARY ACCEPTANCE CRITERIA The Microwave System will be deemed preliminarily accepted upon written notice by the County Contract Administrator of successful completion of the following acceptance test criteria (test criteria may be modified only by written approval of both parties): 1. Factory Acceptance Test Plan (Schedule 11) 2. Field Acceptance Test Plan (Schedule 12) 3. Verification of Path Calculations and Profiles Factory and Field Testing is conducted on all Aviat Networks -supplied equipment and other ancillary equipment to demonstrate compliance with product and contract specifications. Factory and Field Acceptance Testing consists of three (3) phases: • Station Test • Hop Test • System Test • MPLS Router Verification Station Test: deals with station grounding integrity, Equipment inspection including inventory and visual inspections of breakers/fuses, cables, cards and any OEM equipment. Hop Tests: verifies all Aviat Networks Equipment operation including alarm and control points, DC power and any provided OEM. It includes Antenna system test, DC power test, Microwave equipment test including equipment protection, transmit output power, Receive Signal Level (RSL), Receiver Threshold (Fade Margin) test, Transmitter/Receiver Switch test, Ethernet test, BER test (for T1s) and Service Channel test. System Test: verifies loop protection functionality, VOIP OW test, network continuity test, ProVision EMS test, System BER test, MPLS L3VPN over RSTP-TE 1:1 tunnel testing. MPLS Router Verification: 1. Use show commands to verify all routes are in the routing tables, including gobal and VRF tables 2. Ping test between MPLS router ports to verify global connection 3. Ping between Motorola Site Routers to verify VRF connections, a laptop can be used if the if site routers are not available 4. On occasion Command Line Interface (CLI) for spot check 5. Basic L2 verification i. LACP/LAG verification on MHSB/SD hops 6. Basic Layer 3 verification P25 System and Services Agreement (R1422515R1/P1) Page 16 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 i. Configuration verification 1. Management Access: log in using SSH 2. Interface configuration: verified under number 2 above 3. Routing protocol: verified under number 2 above 7. Run Y.1564 test on selected TE tunnels, could be the longest tunnels in the system Path Calculations and Profiles: The Microwave System shall comply with the path calculations and profiles set forth in Schedule 9 (as modified during the design process to the extent approved by the County). The path calculations and profiles set forth in Schedule 9 are based upon Motorola's evaluation of the assessment tower locations, terrain, known obstructions, and requirements of the system, and provides the following preliminary path calculations and profiles. Any changes to these calculations and profiles shall be submitted to County for approval by the Contract Administrator. Nothing in this paragraph alleviates the obligations of Motorola to meet the system specifications and provide the System with the required coverage. P25 System and Services Agreement (R1422515R1/P1) Page 17 of 17 SOW A-3 (Microwave System) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SOW A-4 Subscriber Equipment 1. OVERVIEW There are an estimated 7,930 subscriber radios that will need to be replaced across primary system users to ensure compliance with a P25 Phase II 700/800 MHz system. Subscriber Equipment shall be available for purchase by the County as well as any municipality, local government or public safety entity on the Broward system. As defined in Section 5.6 of the Agreement, any Eligible Purchaser may purchase Subscriber Equipment or Subscriber Equipment Maintenance set forth in this SOW A-4 in accordance with the terms of the Agreement. All such Subscriber Equipment shall meet the General Requirements set forth in Section 1.2 herein, and shall be warranted in accordance with Section 1.3 herein. Provider shall provide, to the extent elected by any Eligible Purchaser, Subscriber Equipment Maintenance in accordance with Section 1.4 herein. Eligible Purchasers may elect to terminate any Subscriber Equipment Maintenance elected hereunder on at least ninety (90) days prior notice, and may acquire new or recommence previously terminated Subscriber Equipment Maintenance with no penalty or additional cost other than set forth herein. Eligible Purchasers are not limited to the specific products or features specified herein, but can configure and select items from Provider's entire APX product line with the same applicable discounts set forth in Section 3.0 herein to meet their agencies specific needs. Anything indicated herein as "Optional" may be elected in the sole discretion of the Eligible Purchaser at the pricing set forth herein, subject to inclusion of the applicable services by Broward County at the System level, if applicable. 2. SUBSCRIBER EQUIPMENT REQUIREMENTS 2.1 GENERAL REQUIREMENTS All Subscriber Equipment must meet the following general requirements: A. All Subscriber Equipment shall be of high quality and intended to provide high reliability under heavy use in severe environments. Subscriber Equipment shall be FCC type accepted in accordance with the Commission's Part 90 rules and regulations. B. All Subscriber Equipment shall meet MIL-STD-810 C, D, E, and F. C. All Subscriber Equipment shall be software programmable. D. All Subscriber Equipment shall support the following operating modes: 1. Conventional analog frequency modulation (FM) network 2. Conventional analog FM off -network (talk around) P25 System and Services Agreement (R1422515R1/P1) Page 1 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 3. Conventional P25 Phase I network 4. Conventional P25 Phase I off -network (talk around) 5. Trunked P25 Phase I network 6. Trunked P25 Phase 11 network E. All Subscriber Equipment shall be programmed for operation on the P25 Phase II 700/800 MHz system that will be implemented through this contract. F. All fielded subscriber equipment that will be programmed to operate on the County's new system must undergo preventive maintenance to restore the radio to the manufacturer's specifications at the time the radio is programmed to operate on the new system. G. To support a seamless cutover to the new system, subscribers shall be installed prior to system cutover and programmed with talkgroups from both the old and new systems. Once cutover to the new system has been completed, talkgroups from the old system shall be removed (second touch). H. Any fielded radios programmed to operate on the new system must undergo Preventive Maintenance (PM) to restore the radio to the original operating specifications at the time the codeplug is updated. 2.2 PORTABLE RADIOS REQUIREMENTS A. Features: 1. Full compliance with P25 Phase I and P25 Phase II features and operation 2. PTT button 3. Top -mounted on/off volume knob 4. Talkgroup/channel selector 5. Emergency button, protected from inadvertent activation 6. Alphanumeric display (on applicable models), minimum of eight characters 7. Transmit indicator 8. OPTIONAL— Over -the -air programming (OTAP) and associated fixed equipment 9. OPTIONAL — Over -the -air rekeying (OTAR) and associated fixed equipment 10. OPTIONAL — Subscriber radio GPS and associated fixed equipment 11. OPTIONAL — Radio management license B. Battery: 1. Provider shall provide batteries without cadmium. Options include the following: P25 System and Services Agreement (R1422515R1/P1) Page 2 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 a. Nickel -Metal Hydride (NiMH) b. Lithium -ion c. Batteries certified as intrinsically safe. 2. Batteries shall provide a minimum operational use of 12 hours based on a 5-5-90 duty cycle. 3. Recharge time to full capacity shall not exceed one hour. C. Accessories: 1. AES encryption 2. Data cables 3. Battery chargers: a. Single -bay battery charger b. Multiple -bay battery charger c. Vehicular charger 4. Alternate antennas 5. Remote speaker microphone 6. Remote speaker microphone with antenna 7. Headset: a. Wired b. Wireless/Bluetooth 8. Carrying cases/belt clips 2.3 MOBILE RADIOS/CONTROL STATIONS REQUIREMENTS A. Mobile radios shall be supplied complete with microphone, external speaker, cables, fusing, mounting hardware, coaxial cable, and antennas to provide for a complete installation. B. Control station radios shall be supplied complete with desk microphone, speaker, cables, coaxial cable, and antennas to provide for a complete working package. C. Control stations should include up to 100 feet of %" LDF plenum rated coaxial cable with associated RF surge suppressor, ground kits, mounting hardware, and an omnidirectional antenna to be mounted on the roof. D. Control station configurations shall be offered with both a deskset consolette setup with built-in power supply, and as a mobile radio with a DC power supply. P25 System and Services Agreement (R1422515R1/P1) Page 3 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 E. Features: 1. Full compliance with P25 Phase I and P25 Phase II features and operation 2. Remote speaker microphones 3. Front -mounted on/off volume knob 4. Talkgroup/channel selector 5. Emergency button, protected from inadvertent activation 6. Alphanumeric display 7. Transmit indicator 8. Dash- and remote -mount configurations 9. OPTIONAL — Over -the -air programming (OTAP) and associated fixed equipment 10. OPTIONAL — Over -the -air rekeying (OTAR) and associated fixed equipment 11. OPTIONAL —Subscriber radio GPS and associated fixed equipment 12. OPTIONAL — Control station combiners for configurations supporting 4/8/12/16/32 ports F. Accessories: 1. AES encryption 2. Cables: a. Data cables b. Extension cables i) Adapters ii) Power cables 3. Antennas 4. 7.5- and 13-watt external speakers 5. Public address kits 6. Remote speaker microphones 7. Desktop microphone (control stations only) 8. GPS functionality and associated fixed network hardware 9. Mobile data interface 3. SUBSCRIBER WARRANTY Provider shall warrant all Subscriber Equipment purchased prior to P25 System Final Acceptance by Broward County or by any Eligible Purchaser for three years from date of purchase at no additional cost. Any Subscriber Equipment purchased on or after Final Acceptance shall be warranted for at least one year from date of purchase. Notwithstanding the above, the following warranties and support are included at no additional cost in the following items (for clarity, the purchaser may elect to purchase additional support, if elected by the purchaser): P25 System and Services Agreement (R1422515R1/131) Page 4 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • APX radios: 1 year Service from the Start - Lite. • Accessories standard warranty: 1 year Service from the Start - Lite. • Batteries: 18 months warranty • Extended warranty is available up to 5 years, as an option, as elected by the purchaser. Provider shall repair any radio that fails due to manufacturer defects within the applicable warranty period at no additional cost to the County or Eligible Purchaser. 4. SUBSCRIBER EQUIPMENT MAINTENANCE Motorola Subscriber Equipment Maintenance is provided by technicians or certified Motorola partners backed up by Motorola's technically elite team of System Technologists and our Central Systems Engineering teams. Motorola is committed to: • Unequaled, best -in -class customer service response for critical communication solutions. • Highly qualified and trained employees and partners focused on service delivery. • Stable, trained and committed partners able to provide more readily deployable resources. • A highly trained and certified technician base working our customers' radios. Motorola Solutions delivers the quality service and enhanced customer support critical to every customer relationship. Motorola Solutions will: • Continually improve the quality of service delivery through ongoing continuous improvement plans where goals are established, met, sustained and then re- established to push forward. • Recognize and reward partners that continuously invest in their abilities to provide quality service to our customers. • Audit points of presence to be sure they continue to meet the standards of the Subscriber Equipment Maintenance. • Develop training roadmaps for both our bench and field technicians. Motorola's Radio Support Center will either repair locally or will ship the repaired within five days or less from receipt of the radio submitted for repair to help get units back into customer hands as quickly as possible. The Eligible User will be responsible for shipment to Motorola and associated costs, and Motorola will be responsible for return shipping and associated costs. Motorola will only use highly -qualified, dedicated and financially stable service delivery partners dedicated to the user's satisfaction. Users can rest assured that technical support queries are dealt with promptly to ensure minimal downtime is incurred. Motorola Solutions technical experts work with the Motorola Solutions partner to isolate, diagnose and resolve potential issues, reducing the risk of the issue escalating. When it comes to repair, users' devices will be handled by one of Motorola P25 System and Services Agreement (R1422515R1/P1) Page 5 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Solutions' certified repair technicians. State-of-the-art diagnostics equipment, repair tools, and an extensive inventory of replacement parts help us to provide expert repair on your ASTRO 25 devices. In addition, Motorola Solutions service centers are fully certified to comply with ISO9001 and TL9000 standards using proven, repeatable processes to help ensure your repair is completed right the first time and every time. Any Motorola Solutions' service depots and field centers must meet the following requirements, designed to drive key service behaviors and performance critical to your confidence in Motorola: • Calibration of equipment — Test equipment used by field and bench service technicians must be calibrated on a regular basis in accordance with manufacturer recommendations. This requirement is audited on a regular basis. • Information Security Policy — Service technicians and partners have a robust policy to secure the information assets of its company, all other companies it does business with and all customers of Motorola Solutions. This policy must ensure that the our service team's technical resources are properly protected, that the integrity and privacy of confidential information is maintained, that information resources are available when they are needed and that users of these resources understand their responsibilities. Naturally, our depots follow Motorola Solutions' Information Security policies. • Technician and installer certification —Technicians and installers must meet minimum certification requirements. The necessary certifications can vary depending on specific customer needs in the marketplace. • Insurance/environmental health & safety Policy —All service partners must meet environmental, health and safety standards and must maintain standard business and liability insurance. • Contract -specific benefit criteria — When a service partner provides services contracted by Motorola Solutions as part of a specific contract or series of contracts, the benefits of associated technical training, technical manuals and technical call center support will be provided for those products or series of products supported by such contract. Motorola's personnel or subcontractors providing Subscriber Equipment Maintenance possess general technician and installer certifications obtained through Electronics Technicians Association International (ETA-1). Motorola Solutions has also developed a series of certifications geared specifically to Motorola Solutions platforms and equipment. Certifications are only achieved once a technician has successfully completed specific training programs and passed the certification exams. Motorola Solutions technical professionals are trained to specifically meet the needs of every customer's radio subscriber needs, specifically: creating templates, building codeplugs, programming, installation services and support services. Each user agency in Broward County can rest assured their needs, operational goals, security protocols and responsiveness will be meet by our team of professionals: P25 System and Services Agreement (R1422515R1/P1) Page 6 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5. SUBSCRIBER MAINTENANCE OPTIONS Eligible Purchasers may select from any combination of the following for some, none, or all of their purchased Subscriber Equipment: 5.1 PORTABLE, MOBILE, CONTROL STATION AND CONSOLETTE SERVICE FROM THE START - LITE: Service from the Start - LITE provides board level service for the covered equipment. Services are performed at the Radio Support Center (RSC). In addition to board level service for the covered equipment, Service From the Start- LITE includes service on single mobile control heads provided that they are required for normal operation of the Equipment and are included at the point of manufacture. Service from the Start — LITE also includes: — Normal wear and tear repair coverage. — 5-day repair turnaround time from Eligible Purchaser notification of defect to receipt of replacement or repaired device — Expert technical support (7x24365). — Software maintenance and updates. Service From the Start Lite includes the following to be provided by Motorola: • Test and restore the Equipment to Motorola factory specifications, including Factory Mutual (FM), and Mine Hazard Safety Association (MHSA). • Reprogram Equipment to original operating parameters based on the Customer template, if retrievable, or from a Customer supplied backup. If the Customer template or code plug is not usable, a generic template or code plug utilizing the latest Radio Service Software (RSS) or Customer Programming Software (CPS) version for that Equipment will be used. The Equipment will require additional programming by the Customer to Restore the original template. All Firmware is upgraded to the latest release for each individual product line. • Clean external housing of the Equipment. External components of unit will only be replaced when functionality has been diminished. • Motorola will pay the inbound freight charges if the Customer uses the Motorola designated delivery service (Federal Express). Motorola will pay the outbound freight charges (return to Customer). • Provide the Motorola repair request and Inventory Adjustment Form (IAF) via Motorola On Line (MOL). • Process inventory adjustment requests received by email or fax from Customer. If the request is received by email, Motorola will email an acknowledgement to the sender. • Perform covered services as requested by Customer on the Motorola repair request form. • If applicable, notify Customer of changes in Motorola designated inventory adjustment email address or fax number. P25 System and Services Agreement (R1422515R1/P1) Page 7 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5.2 PORTABLE, MOBILE, CONTROL STATION AND CONSOLETTE SERVICE FROM THE START - COMPREHENSIVE: Service from the Start (SFS) Comprehensive provides all component level service for the covered equipment. Services are performed at the Radio Support Center. In addition to all the Services identified in Service from the Start — LITE, Service from the Start — Comprehensive also includes repair or replacement of cracked housings, frames, covers, crushed components, shields, missing components, circuit boards, warp circuit boards, damage to LCD screens, electrical damage, water/chemical corrosion, and contaminants visible which cannot be cleaned up reliably. 5.3 PORTABLE MOBILE, CONTROL STATION AND CONSOLETTE SUBSCRIBER LOCAL Subscriber Local Support provides an operational check of equipment that is covered under a service agreement. An operational check is an analysis of the equipment to identify external or internal defects. If the equipment has an external defect, or can be restored without opening the radio case, the equipment will be restored and returned to customer. If the equipment has an internal defect, or is not serviceable without opening the radio case, then the equipment will require additional service and will be shipped to the Motorola Depot for repair utilizing the Service from the Start or Service from the Start Comprehensive support. Subscriber Local Support is provided locally by a Motorola Authorized Service facility. 5.4 LOCAL SUPPORT: User Agency may elect to combine subscriber support services, which are Service from the Start (Lite or Comprehensive) with Local Support. Radios will be repaired locally except when shipment is necessary to Motorola Depot. This type of service may reduce the turnaround time for radio repair. 5.5 PORTABLE, MOBILE, CONTROL STATION AND CONSOLETTE SUBSCRIBER PICK UP AND DELIVERY: Pick Up and Delivery is an option to our Subscriber Support Services, where Motorola Solutions provides pick up and deliver services for subscribers. This service reduces the time and expense for the agencies to ship, deliver and pick up subscribers. 5.6 PORTABLE, MOBILE, CONTROL STATION AND CONSOLETTE SUBSCRIBER PREVENTATIVE MAINTENANCE: Subscriber Preventative Maintenance (PM) provides for an operational test to ensure the customer's equipment meets and continues to meet the manufacturer's specification. This service will be provided during standard business days at the Motorola Authorized service facility. P25 System and Services Agreement (R1422515R1/P1) Page 8 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 5.7 PORTABLE, MOBILE, CONTROL STATION AND PREVENTIVE MAINTENANCE PLAN: Preventive maintenance plan to restore the radio to the manufacturer's specifications at the following recurring intervals: a. 6 months b. 1 year c. 2 years L'F:1ILIII kTj1.114.113A.S191]Z61:iIts] 29 W 011 In addition to the above, Eligible Purchasers may purchase added services and coverage beyond the warranty period on a per -request fee structure, including: 1. Programming of a radio to update the radio's firmware (firmware purchased separately) 2. Reprogramming of existing radios operated by users on the Broward County system to operate on the new P25 Phase II system, including a) Updating radio firmware (flash) to support P25 Phase II operation and any other required feature sets b) Retuning radio with the updated codeplug and fleetmap for the new system c) Retuning radio to update codeplug and fleetmap to remove the legacy radio system talkgroups (second touch). P25 System and Services Agreement (R1422515R1/P1) Page 9 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 6. SUBSCRIBER EQUIPMENT APXTM SERIES P25 TWO-WAY RADIOS The APX series incorporates many new features key to ensure the safety of users, including further audio quality enhancements, ruggedization, intuitive displays and controls, and features critical to ensuring the safety of first responders and citizens throughout the County. All the proposed portable and mobile radios are fully -compliant to the County's requirements, and offer additional capabilities and features that exceed the County's requirements. The APX radios will work seamlessly with Broward County's current radio network and the ASTRO P25 System. This is critical to enable a seamless and more efficient user cutover as each agency will be able to use a single radio supporting operation on both the legacy and new P25 system. Broward County and Authorized Third Party Users will be able to leverage text messaging, location services and other data enrichments that will provide increased redundancy and information sharing with Broward County's first responders. APX Series Radios include: • The ability for the radio to be easy-to-use/accessible [APX Ergonomics]. • The ability to talk and hear clearly in loud environments [APX Audio]. • The ability to communicate in more places [APX Coverage]. • The ability to perform in extreme situations [APX Durability]. Motorola Solutions created the APX series to redefine safety in mission critical radio communication. Every feature and function on an APX two-way radio is designed with its users in mind —from the rugged, easy -to -operate design, to the loudest, clearest audio. The result is improved safety for all mission critical users —from the firefighter in a burning building, to the police officer serving a high -risk warrant, to the paramedic racing to provide urgent medical attention. Motorola Solutions has application -tailored radios and accessories designed specifically with each of these users in mind. Motorola Solutions' APX series portable and mobile radios provide a number of advantages over other 3r6 party vendors' equipment, including but not limited to: • Enhanced Audio (Dual-Mic/High Noise/Wind porting/increased power of speakers and RSM). • Configurable Audio and Radio Profiles. • Ergonomics (Size/Weight/User Interface/Color/Top Display). • Ruggedness (Scale/Ball Drop/Dunk Tank/Endoskeleton). • Features (Integrated GPS/Bluetooth/Man-down/Text Messaging Service). • Phase II TDMA and software updates to include other functionalities. • Data applications (database access, status message, location, text, POP25, OTAR, etc.). • Best in class Noise Suppression and Audio Capabilities. P25 System and Services Agreement (R1422515R1/P1) Page 10 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Mission -Critical Grade Bluetooth. • SCBA Integration. • Text Messaging and Integrated Solutions. • GPS/AVL API and Integrated Solutions. • Enhanced Data with 12x data throughput for Biometrics, Telemetry, etc. • End -to -End Encrypted Voice + Data. • Next Generation Solutions and applications: BOLO on APX Radios, Geo-Fencing, and more... APX Audio Design Advantages • Adaptive Dual-mic Noise Cancelling Technology. • Adaptive Noise Reduction Algorithms that perform in Analog & Digital Operation. • Adjustable Audio Parameters to optimize performance in various noise environments. • Significantly lower audio distortion for better intelligibility. • Automatic Gain Control or analog noise suppression: — Non-AGC Portables may experience interoperability problems in mixed fleets due to fluctuating audio levels. APX Feature Advantages • P25 Radio Authentication. • FIPS 140-2 Level 3 Certified Encryption Module. • Demonstrated P25 Phase 2 TDMA operation. • Secure Bluetooth. • APX Bluetooth Near Field Pairing technology enables fast, simple, and secure encrypted pairing with any Bluetooth enabled APX. • APX features Superior Roaming, Fastest Site Switching and ability to specify Site Priority (most/least preferred). • Integrated Voice & Data with Text Messaging capabilities in P25 Digital operation • Integrated GPS inside the radio. • Man -Down automatic emergency notification in the event of user injury + GPS notification of user location upon Man -Down alarm. • Motorola Solutions OTAP advantages: — Voice priority during OTAP: Users can initiate Push To Talk calls during OTAP data sessions. — Presence Notification + Batch Programming — which facilitates system management and improves administrative efficiency so that Radio IP addresses do not need to be entered manually one radio at a time. — User selected reboot following OTAP data sessions so that critical voice calls are not interrupted. — Pause/resume data feature with differential write: Permits OTAP data package to pick up where it left off when interrupted by voice communications — competing solutions must start over when interrupted + must be write entire software package regardless of similarity to existing software. P25 System and Services Agreement (R1422515R1/P1) Page 11 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Data roaming: Users can roam and maintain data session. • P25 CAP certified on Motorola Solutions infrastructure and a wide variety of 3rd party infrastructure. • Personnel Accountability applications with APX portables for fire-scene/SWAT team staff safety within buildings. • More Programmable Front Buttons, Side buttons Home & Data Buttons, and Navigation Pad than competing radios. • Support of both Tactical + Trunking OTAR. • Customizable Channel Announcements. • RFID option. APX Ergonomics Advantages • Ergonomic spacing between controls. • Large, accessible emergency button. • Oversized ergonomic knobs for ease of use for users with gloves. • 3-Position Toggle and 2-Position Concentric Switches. • Top Display for easy viewing of channel/zone information, even when on the user's hip. • Large Color LCD Display For Better Viewing and Enables Intelligent Lighting. • Radio Profiles/Intelligent Lighting Bar. • Shielded PTT button. • Universal PTT is textured with locater ridges, enabling quicker blind operation in high -stress situations. • Multiple keypad/display options in APX models to permit customizing to agency use cases • Light weight. • Blind Operation/Operate by feel. APX Ruggedization Advantages • Gorilla Glass (TM) Lens — Tempered glass for displays which provides a wider viewing angle, plus greater scratch and heavy impact resistance than competing radios, plus prevents distorted view with polarized lenses. • APX Endoskeleton Design Provides Improved Submersibility and Ruggedness for Internal Components. • MIL Spec Conformance with best -in -industry shock, submerged water and scratch resistance. • IP ratings up to optional IP67. • Conformance to Motorola Solutions Internal 12M specifications which are even more stringent than MIL Spec. • Motorola Solutions Accelerated Life Tests. P25 System and Services Agreement (R1422515R1/131) Page 12 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX RF Performance Advantages • APX radios significantly outperform competing radios in key RF metrics ensuring superior talk-in/talk-out capability. Motorola Solutions' best in class RF specifications for better performance in challenging/fringe coverage. • Intermodulation Distortion/Rejection (Higher dB 4 better performance): — APX hardware is optimized to reduce Intermodulation Distortion with a spec that is 2 times better than some competitors. — This dramatically increases the radios coverage performance in high RF traffic environments (Cities/Urban Centers). • Sensitivity (Lower the µV 4 better performance): — Lowest possible signal strength that a radio can intelligibly detect in a given environment (the lower the (µV) number the better). — Allows the radio to receive signals in difficult coverage areas such as inside buildings. • Selectivity/Adjacent Channel Rejection (Higher dB 4 better performance): — Radio's ability to hear only the voice traffic from the desired channel, and reject other signals that are very close to that frequency. — Specification helps considerably when operating near other transmitters, especially in urban environments with high RF traffic. • Audio Distortion (Lower the % distortion 4 better performance): — Measurement of the amount of audio distortion produced at a given output power level. — Less distortion equals clearer/crisper voice being heard from the radio especially at high audio volume. • FM Hum and Noise (Higher dB -)� better performance): — Measurement of the radio noise floor of both Transmitter and Receiver. — Lower noise floor of the radio means greater the likelihood that a low-level audio signal will come through, such as when the talker is whispering. APX Mobile Control -Head Interface Advantages • Quick & easy to operate Siren Controls, Pursuit Knob, Light Switches, and PA Button. • Mission critical display lens is resistant to high force impacts — competing solutions using resistive touch -screens require a soft top layer which is much more vulnerable to wear and tear, and can be easily damaged by sharp edges. • Large Programmable One Touch Consolidated Action Buttons. • Quick & Easy Brightness, Night Mode, and Covert Mode controls. • Concave/Convex Integrated DEK Buttons enable easy Blind Operation. • Tri-color Backlighting (Green, Orange & Red) for Intelligent Lighting. • Superior IP 56 ratings for better water resistance than competing mobile control head interfaces. • Motorola Solutions' 05 Control Head provides 5 programmable soft key buttons and 5 scroll -through menus enable up to 24 total programmable soft keys + 4-way navigation button. P25 System and Services Agreement (R1422515R1/131) Page 13 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Motorola Solutions' 07 Control Head provides 4 programmable soft key buttons and 5 scroll -through menus enable up to 24 total programmable soft keys + 4-way navigation button + DTMF keypad w/pre-configured Siren/Lights/PA/Gun Lock controls. Motorola Solutions' 09 Control Head provides the largest available LCD display in the industry, with 5 programmable soft key buttons and 5 scroll -through menus enable up to 24 total programmable soft keys + 4-way navigation button + full 12 Button DTMF keypad, a data applications button, and Quick & easy to operate Siren Controls, Pursuit Knob, Light Switches, and PA Button controls. Motorola Solutions' APX series of portable and mobile mission -critical grade radios provide best -in -industry performance via the above summary of unique quality differentiators, along with many other additional detailed attributes and features. APX RADIO APPLICATIONS APX ADVANCED DATA FEATURES The Motorola Solutions APX Advanced Data solution set and features provide the following unique capabilities within the P25 radio industry: • 200 Character free -form text messaging. • Send messages to text groups. • Choose from 150 pre -defined Quick -Access messages. • Store -and -forward message delivery. • System supports up to 20,000 active users. • Up to 50,000 outbound text messages per hour. Integrated GPS Capability The entire APX family of portable and mobile radios offer the County users and agencies the ability to locate and track each field unit from a central location. The integrated GPS receiver in the APX transmits the outdoor location of an individual or vehicle to map -based location software that will interface with PremierOne CAD. Text Messaging Text messaging offers freeform and canned messaging between field users and dispatch operators. This enables selected field users to not only communicate with one another and with dispatch operators via voice transmission, but also through discreet texts. Information (such as addresses, license plates, phone numbers) communicated out via text messaging results in fewer repeat voice communications improving efficiency. Through PremierOne and the MCC7500 dispatch consoles text messaging is available for group texting situations. Motorola Solutions ASTRO 25 7.17 release offers group text from the MCC7500 without the need of additional infrastructure. In the 7.17 release the transmission of the text will occur on the control channel of the ASTRO 25 infrastructure. P25 System and Services Agreement (R1422515R1/P1) Page 14 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 P0P25 Over the Air Programming (OTAP) All proposed radios can optionally provide the County with the functional and cost benefits of Motorola Solutions' Programming -Over Project 25 (POP25) over -the -air programming (OTAP) technology. POP25 functionality reduces the time, effort, and costs needed to update radio functionality by allowing radios' configuration to be accessed and updated over the air. Broward County's radio users will be able to continue working in the field while their radios are updated to the most current configuration. Voice communications have priority during programming. Please reference Motorola Solutions OTAP advantages in prior section. OTAP is an optional feature available on all proposed portable and mobile radios. Outdoor Location Solution Motorola Solutions' Outdoor Location Solution is offered on the ASTRO 25 Trunking Integrated Voice & Data (IV&D) System, It uses Global Positioning System (GPS) Satellites to provide the location of personnel and vehicles which can be fed to a map based location application to provide dispatch operators with an invaluable tool for managing and tracking personnel and resources. The ability to locate users in a mission critical situation dramatically increases user safety while improving resource allocation and responsiveness. ASTRO Outdoor Location Server: Unified Network Services (UNS) The Motorola Solutions Unified Network Services (UNS) application acts as a gateway for the location, telemetry, and presence information from the ASTRO radios and transfers data to back office applications. It simplifies the integration process for developers by receiving in disparate GPS protocols and translating them into a unified protocol out to the third party application. Additionally, it provides for intelligent routing of messages to the devices, and thus lowers traffic over the network. ASTRO Presence The Presence functionality within UNS provides the presence and absence information of subscriber radios to any compatible data applications located in the Customer Enterprise Network (CEN). It interfaces with data applications and subscriber radios using User Datagram Protocol/Internet Protocol (UDP/IP). This allows the dispatcher to know whether or not a subscriber unit is powered on or off or located somewhere within the radio network. Location Application Programming Interface (API) The ASTRO 25 Location Application Programming Interface (API) contains all the necessary interface documentation that a third party application developer needs to receive location, telemetry, and presence data from the UNS. The API pushes data messages containing location, telemetry, and presence information in near real time to the third -party application and allows support for remote commands through a set of messages that can be sent to the mobile units. P25 System and Services Agreement (R1422515R1/P1) Page 15 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ASTRO 25 Enhanced Data ASTRO 25 voice systems have been building to portable grade coverage specifications for several years. The ASTRO 25 system provides all of the components and the wide -area system coverage necessary to perform a mobile and portable GPS reporting function. Motorola Solutions understands the customer's needs to poll for location data more frequently. Constant tracking of the locations of all field personnel has been a need for the Public Safety sector for a long time. Next generation of ASTRO 25 Integrated data benefits will provide the following benefits: • Provide outdoor location data for all of the users with a faster polling rate. • Increased AVL and telemetry capacity as compared to Classic P25 Integrated Data. • Ability to have "protected", data only, Enhanced Data channels. • Ability to prioritize data over non Emergency voice calls on Enhanced Data channels. Enhanced Data exceeds today's P25 standards of 50 radios reporting at a 2 minute cadence. It has the potential to pull GPS coordinates for 500 radios per enhanced data channel at a 2 minute cadence (or 150 at 30 seconds, or 75 at 15 seconds). This is up to 12 times more efficient than the P25 standard and critical for optimum performance. Please note that this reporting rate of 30 seconds per user is based on specific channel criteria such as user loading, channel availability and other message traffic on the Enhanced Data channel(s). PremierOne CAD Integration ASTRO 25, APX series radios and PremierOne CAD have true integration benefits to benefit all users such as: • APX Texting: — Send and receive messages to APX radios. — Query databases from APX radios. — Receive dispatch information to APX radios. — Administer Status updates with APX radios. • Unit Location: — Allows APX radios to be placed onto CAD MAP. — GPS Cadence received directly with PremierOne CAD. — GPC location services work with Portable and Mobile radios: ♦ Ability to track vehicles and individuals. • GeoFence creation aids in incident command. APX RADIO MANAGEMENT AND PROGRAMMING Motorola Solutions' Radio Management is an optional solution unique to Motorola Solutions APX subscriber radios and Motorola Solutions ASTRO 25 infrastructure that comprehensively manages radio configuration and subscriber radios, and will dramatically reduce the Total Cost of Ownership. Key Radio Management Features include: P25 System and Services Agreement (R1422515R1/P1) Page 16 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Radio Inventory. • Centralized Radio Configuration and Codeplug Management. • Automated Radio Updates of BOTH Codeplugs and Software Flash Versions. • Only Motorola Solutions Infrastructure can Batch Program Motorola Solutions APX Radios over a P25 System. • No Missed Calls with OTAP due to Voice Priority with Motorola Solutions' Infrastructure. Motorola Solutions' Radio Management tool simplifies the configuration and management of radios. With an order of a Motorola Solutions radio, an electronic order with the serial number is generated. The serial numbers from the electronic order can then be entered into the Radio Management application. The radios associated with the serial number can then be assigned a codeplug template in the Radio Management Application, and a job can be scheduled to program the radios. Once the radios arrive, a group of radios can be programmed at one time. Radio Manager will track which radios have been successfully programmed. When codeplug updates occur, the radio codeplug database is stored on a cloud server. This allows remote programmers to access and program radios, and share codeplug templates across multiple radios. Changes to codeplug templates can be automatically applied to all affected radios. Radio programming jobs can be scheduled ahead of time. The programming of radios can occur via a USB port on a PC on the LAN/WAN network or with Over The Air Programming (OTAP) on an ASTRO 25 radio network. The APX Radio Management application can program up to 16 radios at one time and track which radios have been successfully programmed, providing a clear view of the entire radio fleet and a codeplug history for each radio. Radio Management batch programming of APX radios via OTAP can only occur with a Motorola Solutions ASTRO° 25 Project 25 system, which has voice priority over data, so a user's call, emergency notifications or critical communications will not be interrupted with OTAP. Should an OTAP session be interrupted with communications, programming will resume after the call without the need to restart, expediting the process. APX INTEROPERABILITY AND COMPATIBILITY Motorola Solutions APX subscribers offer the highest degree of interoperability and compatibility. Trunking Support All Motorola Solutions high-performance mobile and portable radios are compatible with the Project 25 Phase II standards for TDMA digital trunking. They all support conventional analog and digital operation, as well as trunked digital operation in the same radio. In addition, they support Project 25 features for interoperability with systems from both Motorola Solutions and other manufacturers. They are ideally suited to situations where County users and agencies need instant interoperability on different systems. P25 System and Services Agreement (R1422515R1/P1) Page 17 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Backwards and Forwards Compatibility Motorola Solutions' current P25 radio portfolio is designed with both backwards and forwards compatibility. The radios in our portfolio have been designed to operate on analog conventional, Project 25 conventional, and Project 25 trunking systems, and can also operate on systems using Motorola Solutions Project 16 analog trunking, SMARTNET, SmartX and SmartZone technology. Project 25 Phase 1 FDMA and Phase 2 TDMA Operation The APX mobile and portable radios can operate in both Project 25 Phase 1 FDMA and optionally Project 25 Phase 2 TDMA trunking modes. Using Motorola Solutions' unique Dynamic Dual Mode (DDM) capability, APX radios can dynamically switch between FDMA and TDMA without the user having to change channels. This provides interoperability on demand with existing and future networks. Interoperability in 700/800 MHz and VHF Frequencies APX multi -band radios can operate on both 700/800 MHz, VHF and UHF frequencies to enable instant interoperable communications for improved coordination, response, and first responder safety. In addition, this provides an easy way to seamlessly transition from the County's legacy SmartZone system to a new ASTRO 25 system. In mission critical situations, agencies from different jurisdictions often operate on different frequency bands — requiring personnel to carry two radios in order to communicate with one another. With dual/all-band APX portable and mobile radios, the County users and agencies can purchase one radio for instant communication over multiple frequency bands. This eliminates the need for field users to carry multiple radios, and reduces the amount of equipment that must be maintained and installed. APX COMPLIANCE TO STANDARDS Motorola Solutions recognizes the importance of P25 standards development and follows the P25 standard documents to ensure interoperability of our system and subscriber equipment with system and subscriber equipment of other P25 compliant manufacturers. Motorola Solutions' ASTRO 25 network and APX subscribers conform to all applicable P25 specifications as outlined in Motorola Solutions P25 Conformance documents. P25 System and Services Agreement (R1422515R1/P1) Page 18 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 MOTOROLA SOLUTIONS APX TECHNOLOGY - DETAILS APX Series Vocoder — Audio Engineering Design Principles Motorola Solutions' audio engineering design begins with Digital Signal Processor (DSP) technology, with added custom high -power loudspeakers and precise acoustic microphones to achieve outstanding noise cancelling, exceptional loudness and clarity, and unparalleled intelligibility for mission critical communications. Motorola Solutions APX series vocoders use the new AMBE+2 Vocoder per the P25 Phase 2 standard. • P25 vendors utilize the IMBE or the AMBE+2 vocoders from DVSI. • AMBE+2 is a new vocoder and is required for all new P25 Radios. • AMBE+2 Comes with Noise Suppression Algorithm. • IMBE and AMBE+2 are fully compatible. APX Durability Durability is central to the design of Motorola Solutions radios — For example, due to the way the battery slides into the frame of the radio instead of simply clipping onto the back, Motorola Solutions APX portable radios can survive larger drops and not lose power. In addition to standardized testing, Motorola Solutions has meticulously engineered these radios to survive the harshest of durability and environmental tests, including: numerous drops onto concrete with the same radio, vibration, extreme temperature fluctuations, humidity, electric discharge, repeated button presses, screen impacts, and more. These tests are all performed sequentially with the same radio having to go through and pass all test before a passing grade is achieved. All this cumulates into a rugged radio that the County's first responders can rely on no matter the circumstances. Motorola Solutions public safety radios meet applicable Military Specifications 810, C, D, E, F, and G. Using MacroBlend housing material, they are designed to survive severe shock and vibration, and exposure to damaging environments such as temperature shock, salt fog, UV radiation, dust, blowing rain, and electrostatic discharge (ESD). Motorola Solutions radios are tested and exposed to extreme conditions to simulate years of abuse. We also perform functional and parametric testing to verify that the radios still work after they are exposed to the environment. Our testing standards and methods include: • Military Specification MIL -STD 810 C, D, E, F, G. • European "IP" specs. • Motorola internal 12M specifications. • Motorola Accelerated Life Tests. P25 System and Services Agreement (R1422515R1/P1) Page 19 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Motorola Solutions' internal 12M specifications are more stringent than industry -standard testing. For example, Military Specifications for a drop test calls for the unit to be dropped onto a plywood surface. Motorola Solutions' drop tests utilize a steel landing surface, which increases the severity of the test. It is Motorola Solutions procedure that each test unit should be subjected to every environmental test, rather than using a different unit for each test. This ensures that our radios perform to specification regardless of the amount and type of abuse they receive. Motorola Solutions goes well above and beyond standard durability testing and performs a large suite of APX Accelerated Life Tests on each model subscriber radio. A subset of these tests include: • Temperature Cycle (-30 to +60 C/3 Days). • Temperature Shock (-40 to +85 C/2 Hours). • Portable and Mobile Vibration. • 40G Crash Test for Mobile Mounting. • Electrostatic Discharge. • Solar Radiation (120F/Vehicle Dash/8 Hours). • Portable Drop (4 Feet/Steel Plate/All Sides/64x). • Steel Ball Drop (1 Meter). • Water Immersion (2 Meters/2 Hours). • Salt Fog. • Dust Chamber (MS Limestone, 2 Hours). • Driven Rain (60 Kmph). • Truck Bed Packaging Vibration and Drop Test (Freeze/6 Sides/8 Corners). Motorola Solutions performs rigorous testing and subjects each model radio to unrealistically harsh conditions for one reason — to ensure that the County's users responders can trust their radio to perform when they need it most. APX ADVANCED HARDWARE FEATURES Motorola Solutions offers a large number of standard and optional hardware features to enhance the usability of APX radios for the County's users. These hardware features include: GPS Location Integrated GPS receiver can transmit the outdoor location of an individual or vehicle to map - based location software. Motorola Solutions APX series radios feature GPS internal to the portable radio — users do not depend on an external RSM for GPS to function. Enlarged Buttons Enlarged and ergonomic emergency button, PTT button, display, and keypad controls. Increased spacing between controls increases ease of use for users. Optional XE series for added robustness and ergonomics with gloves. P25 System and Services Agreement (R1422515R1/P1) Page 20 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Color Display Resists scratches, wear and tear, and tested for durability against cracks. Optimized to provide contrast without glare and provide increased viewing from angles. Radio Authentication Providing an extra, secure level of verification every time a radio registers onto a system. Mission Critical Wireless A unique Bluetooth solution that provides an encrypted link to high performance accessories and applications to support different mission critical environments. Supports commercial off the shelf (COTS) and personal area network (PAN) devices. Motorola Solutions APX series radios include Bluetooth functionality for the County users and agencies. No additional costs are required for the County's users and agencies to utilize Bluetooth functionality. APX ADVANCED SOFTWARE FEATURES Motorola Solutions offers a large number of standard and optional software features to enhance the usability of APX radios for the County's users and agencies. A handful of these software features are summarized below. Radio Profiles Radio profiles enable users to customize their radios' interface to their environments and activities, including the radio's default audio level, lighting and tone alerts. For example, a user in bright sunlight or high -noise environments can increase the lighting or audio level or if the user is conducting ongoing, covert surveillance, they can create a profile that provides lower lighting with subdued alert tones and audio. Intelligent Lighting Motorola Solutions APX radios can offer a high resolution display that uses color and lighting to indicate radio mode, potential emergencies, or specific events. Intelligent lighting is a standard feature that enables users to see critical information at a glance, regardless of the amount of ambient lighting. P25 System and Services Agreement (R1422515R1/P1) Page 21 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 In addition, the following software features are available: • Text Messaging — Offers a freeform or canned messaging solution so you can efficiently and discreetly send and receive messages to and from subscribers or dispatch operators. • Unified Call List — Consolidates all call lists underneath one unified list so you can easily access all information associated with a particular contact. • Voice Announcement — Allows users to navigate through channels, talkgroups, and zones in the radio while an audible, pre-recorded voice file provides a description of the selected channel or zone. Standard feature on all model radios. • P25 TDMA Capable — Provides twice the voice capacity, so you can add more users to your system without the need for additional frequencies or infrastructure. • Multiband Operation — Multiple frequency bands supported with best -in -class transceiver specifications and performance. • Seamless Scan — Seamless scanning of multiple protocols including FDMA and TDMA systems and multiple RF bands. • Enhanced Data — Enhanced Data provides up to 12x higher data throughput than traditional classic P25 Data. Enhanced Data supports rapid GPS reporting cadences with up to 150 radio users reporting GPS status every 30 seconds — in a single radio channel. Provides for substantial savings on infrastructure cost for Land Mobile Radio data communications, and enables new higher -throughput data applications on mobile radios. • Site -Selectable Alert — Continuous tones sent to alert sites of evacuation of sites, vehicle stops, fire -hall alerting, or other pre -determined actions. APX END -TO -END VOICE ENCRYPTION The Subscriber Equipment offers unsurpassed encryption and information privacy mechanisms, going beyond the required standards. The Motorola Solutions APX family of radios all utilize the Motorola Advanced Cryptographic Engine (MACE). The MACE has the capability to not only store the County's encryption keys but will also protect those keys from being accessed by unauthorized users through physical or electronic means. This capability allows the APX Family of Radios to meet Federal Information Processing Standard Publication (FIPS) encryption standards FIPS 140.2 Level 3 and FIPS 197. The radios support multi -algorithm Project 25 and legacy encryption capabilities, including AES and optionally DES / DES -XL / DES-OFB / DVP-XL / ADP for increased interoperability with other systems. Encryption and decryption services are provided by the system's secure endpoints: consoles, logging interfaces, and field radio units. Communications remains completely secure between the source and the destination. No decoding of information occurs at any other intermediate point along the communications path, ensuring a much higher level of security. Encryption keys are distributed to consoles and subscribers, and that is the only place the audio is decrypted Encryption and decryption services are provided by the system's secure endpoints: consoles, logging interfaces, and field radio units. Communications remains completely secure between the source and the destination. No decoding of information occurs at any other intermediate P25 System and Services Agreement (R1422515R1/P1) Page 22 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 point along the communications path, ensuring a much higher level of security. Encryption keys are distributed to consoles and subscribers, and that is the only place the audio is decrypted. Clear Voice Encrypted Voice Clear Voice APX Radios cru lob )) tr.. -o.... . P25 i�AOi; APX NETWORK r Radio ___W� ))� ASTRO Console To increase the effectiveness of encryption, users have the ability to be able to update encryption keys while radios and their users can stay in the field. Motorola Solutions' over -the - air rekeying (OTAR) feature offers the users the benefit of real-time, ongoing security for deployed APX subscribers. APX END -TO -END DATA ENCRYPTION The optional Encrypted Integrated Data (EID) feature adds security to data sent between a radio and an agency data application (eg. data server, wireless applications, GPS location updates, etc). In other words, any packet data flowing to or from a radio are ciphered and then deciphered in the radio and Customer Enterprise Network (CEN) premises. This solution ensures that agency data sent wirelessly is secure and immune to compromise throughout the entire route, secured using AES or other selected APX encryption algorithm from end to end. APX TRANSMITTER AND RECEIVER PERFORMANCE Motorola Solutions APX portables and mobiles offer industry -leading transmitter and receiver performance specifications. The end result is simple — increased coverage and better audio for end users. Paired with a Motorola Solutions trunked simulcast radio system, users can be assured of uncompromising coverage and audio performance from APX subscribers. APX 4000 PORTABLE RADIOS The APX 4000 provides users with a feature -rich portable radio with a unique form factor in a compact and rugged design. The APX 4000 operates on both Project 25 Phase 1 and Phase 2 TDMA trunking systems. The radio also operates on analog and Project 25 conventional systems. The APX 4000 is the smallest and lightest P25 Phase 2 TDMA radio on the market. The APX 4000 portable can be ordered in two different models; the APX 4000 Model 2 (front display and limited keypad) and a Model 3 (front display with full keypad). The portable can support a variety of software capabilities & features to best meet your user's needs. P25 System and Services Agreement (R1422515R1/P1) Page 23 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The APX 4000 offers the voice and data capabilities with a color display and speaker in a compact, rugged design. APX 4000 Model 2 Features • Top -mounted orange display. • Three programmable side buttons for easy access features. • Push -to -talk button designed for easy activation. • Rugged GCAI accessory connector for improved audio accessories. • Alphanumeric display featuring 3-line x 14-character, 1 line of icons, and 1 line of soft menu. • 3 x 2 keypad to navigate through menus. • Cellular -style user interface and color display. • Easy access emergency button. • Meets Military Specs 810 (C, D, E, F and G). APX 4000 Model 3 Features The Model 3 has all the features as the Model 2 with the addition of a 3 x 6 keypad with up to 24 programmable soft keys utilizing the navigational button. *Due to its unique design the APX 4000 portable radio is compatible with existing APX remote speaker microphones (RSM), display RSM, and existing APX customer programming software (CPS) and programming cables. It is not compatible with public safety microphones (PSM) and supports a different set of batteries and chargers than the APX6000 and APX8000 radios. The APX 4000 portable supports the following APX advanced feature sets. Advanced Data Capabilities With Integrated Voice & Data (IV&D), the APX 4000 can be utilized for various applications: • Programming over Project 25 (POP25) — Motorola Solutions' POP25 solution allows subscriber radios to be programmed over the air via ASTRO 25 systems, while remaining in the field. Text Messaging - Text messaging offers a free form or canned messaging solution so that users can efficiently send and receive messages to and from subscribers or dispatch operators. Integrated GPS — The Integrated GPS receiver can transmit the outdoor location of the portable to a map -based location application. Technology Rich The APX 4000 radios are designed with advanced hardware components that allow for the following features: • Multiple Protocols for Enhanced Interoperability — The APX Series radios support Analog, Digital Conventional, P25 Phase 1 FDMA, and P25 Phase 2 TDMA. • Seamless Scan — Seamless scanning of multiple protocols including FDMA and TDMA systems. P25 System and Services Agreement (R1422515R1/P1) Page 24 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Advanced Software Features The advanced software features listed below allow for easy and efficient usability and configuration of the subscribers: • Intelligent Lighting — Intelligent lighting uses color to notify the user of the radio mode, triggered emergencies, or specific events. Color alerts provide information at a glance. • Radio Profiles — Radios can be configured with multiple user -selected or automated operating behaviors, such as audio level, lighting and tones. Whether on surveillance or working in bright sunlight, the user can customize settings as needed with these radio profiles. • Unified Call List — Consolidates all call lists underneath one unified list. Users can easily access all information associated to a particular contact. • Adaptive Dual -Microphone Noise Reduction —An intelligent dual -microphone noise cancellation implemented to aggressively reduce background noise, source location, or microphone used during the transmission. APX 4500 MOBILE RADIO The APX 4500 brings together powerful technology in a compact, rugged, mobile radio. Its control head can be used in either dash -mount or remote -mount configurations, and offers the following user interface features: • 02 control head support. • Can be ordered with a 3 x 6 keypad microphone accessory with three programmable soft keys. • Four programmable soft key buttons and five scroll -through menus with up to 20 programmable soft keys, utilizing the navigational button on the keypad microphone only. • Dual function knob that supports both channel selection and volume control. • Recessed orange emergency button. • Meets Military Specs 810 (C, D, E, F and G). Outlined below is a list of the various features and benefits specific to the APX 4500 mobile. Enhanced Interoperability The APX 4500 series supports the following system and operational modes, and capabilities: • Motorola SmartZone trunking. • Project 25 Phase 1 FDMA trunking. • Project 25 Phase 2 TDMA trunking. • 12.5/20/25 kHz bandwidth receiver — analog capable. • 12.5 kHz bandwidth receiver —digital capable. The APX 4500 is a single -band mobile offering that supports operation on either Motorola SMARTNET/SmartZone trunking or APCO Project 25 (FDMA and TDMA) P25 System and Services Agreement (R1422515R1/P1) Page 25 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 trunked systems. However, it cannot be programmed to support both 3600 & 9600 system types at the same time. Operating Modes and Features The APX 4500 series supports 512 talkgroups/modes as well as the following features and functionality: • Conventional channels. • Talk -around channels. • Supports up to 20 trunking systems, and 100 personalities. • Scan and priority scan available. • Dynamic regrouping capable. • Call -alert paging and individual call. • Transmit or receive by Unit ID or alias. • Features share the unified call list. Encryption Capabilities The APX 4500 supports multiple encryption algorithms including software -based and FIPS- approved UCM-based solutions. • AES. • Single-algorithm/multi-key support. • Minimum of 48 encryption keys/radio with the multi -key option. • Hardware and software encryption (ADP). • FIPS 140-2 Level 3 certification with AES encryption module. Data Capabilities The APX 4500 uses ASTRO 25 infrastructure's Integrated Voice & Data capabilities to support the following optional data applications: • Over- the -Air Programming (POP25). • Integrated GPS for personnel location. • Text Messaging. APX 6000 PORTABLE RADIOS The APX 6000 is Motorola's fourth -generation P25 portable and was designed with direct input from first responders. Engineered with high performance technology and utilizing innovative designs, the APX 6000 provides users with an ergonomic and rugged device that delivers superior audio performance with real-time information in a smaller package. The APX 6000 is easy to use, allowing personnel to focus on their job at hand, rather than the technology. In addition, the APX 6000 equips first responders with the clearest audio of any Motorola Solutions portable on the market. P25 System and Services Agreement (R1422515R1/P1) Page 26 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 The APX 6000 comes standard with IP67 submersibility (1m/30mins) and is upgradable to Delta T submersibility (2m/2hrs). The APX 6000 offers yellow or green color housing options, as well as the standard black housing. The APX 6000 offers voice and data capabilities with a color display, top display, keypad, and best -in -class audio in a compact rugged design. Its unique T-Grip form factor provides secure and easy handling. The APX 6000 portable can support a variety of software capabilities and feature sets to best meet your radio user's needs, and is available in three different models: • Model 1.5 (top display). • Model 2.5 (Dual -Display and limited Keypad). • Model 3.5 (dual display with full keypad) APX 6000 Model 1.5 The Model 1.5 is equipped with the following features: • A monochrome LCD top -mounted display with 1 line/8 characters and one row for icons. • Large angled Volume On/Off knob and large Channel selector knob for easy gloved operation. • Top -mounted orange emergency button. • Three programmable side buttons for easy feature access. • Large Universal Push -to -Talk button backlit for easy activation. • Rugged GCAI accessory connector for improved audio accessories. • Meets Military Specs 810 (C, D, E, F and G). APX 6000 MODEL 2.5 The Model 2.5 has all the features that are included in Model 1.5, with the addition of the following: • Alphanumeric display with 4-line, 14-characters and 2 rows for icons. • 3 x 2 keypad to navigate through menus. • Cellular style user interface and color display. • Easy Access Emergency Button. APX 6000 MODEL 3.5 The model 3.5 has all the features that the model 2.5 has with the addition of the following features: • 4-line, 14-character, with 2 rows for icons alphanumeric display. • 3 x 6 keypad, with up to 24 programmable soft keys. APX 6000 offers various benefits, feature sets and capabilities. Outlined below is a list of the various features and benefits specific to all APX 6000 portable radios. P25 System and Services Agreement (R1422515R1/131) Page 27 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 System Compatibility and Supported Operation Modes The portables support the following system and operation modes and capabilities: • Clear or encrypted APCO Project 16 SMARTNET/SmartZone systems. • Project 25 Phase 1 FDMA and Phase 2 TDMA trunking systems. • 3600 and/or 9600 band trunking interoperability. • 12.5/30/25 kHz bandwidth receiver — analog systems. • 12.5 kHz bandwidth receiver — digital systems. • 6.25e TDMA. Operating Modes and Features The APX 6000 portables supports up to 870 talkgroups/modes. In addition, the following features and functionality are offered: • Conventional channels. • Talk -around channels. • Can support up to 35 trunking systems, and 200 personalities. • Scan and Priority Scan available. • Dynamic Regrouping capable. • Call -Alert Paging and Individual Call: — Transmit or Receive by Unit ID or Alias. — Features share the Unified Call List. • Maximum of 1500 aliases. Unsurpassed Encryption Capabilities The APX 6000 supports single encryption algorithm, including both software -based and FIPS approved UCM based solutions: • Multi-Algorithm/Multi-Key Support. • Tactical OTAR and P25 OTAR capability • Minimum of 64 Encryption Keys/Radio. • Hardware and Software Encryption: — 40kbit RSA Software Encryption (ADP). — Type III/IV Hardware UCM Encryption. — FIPS140 Certification with Encryption Module. Optional Data Capabilities With the integrated voice & data (IV&D) standard option the APX 6000 can support the following data applications: • Over -the -Air Programming (POP25). • Integrated GPS for personnel location. • Text Messaging. P25 System and Services Agreement (R1422515R1/P1) Page 28 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX 6500 MOBILE RADIO The APX 6500 P25 mobile allows users to choose from 4 control heads; mid- and high -power models and multiple installation configurations in an easy -to -install design. APX 6500 mobiles support multiple configurations to best support installation requirements and user needs. • Easy and efficient serviceability — The high -power mobile's new trunion design provides secure engagement, it is also includes a new handle design that allows the radio to be removed without having to remove the cables. • Enhanced Interoperability — System Compatibility & Supported Operation Modes. APX 6500 Mobile Radio The mobiles support the following system and operation modes and capabilities: • Clear or encrypted APCO Project 16 SMARTNET/SmartZone systems. • Project 25 Phase 1 FDMA and Phase 2 TDMA trunked systems. • 3600/9600 systems interoperability. • 12.5/20/25 kHz bandwidth receiver — analog capable. • 12.5 kHz bandwidth receiver — digital capable. • 6.25e TDMA. The APX 6500 supports up to 870 talkgroups/modes, as well as the following features and functionality: • Conventional channels. • Talk -around channels. • Can support up to 50 trunking systems, and 100 personalities. • Scan and Priority Scan available. • Dynamic Regrouping capable. • Call -Alert Paging and Individual Call: — Transmit or Receive by Unit ID or Alias. — Features share the Unified Call List. • Maximum of 1500 aliases. The APX 6500 supports multiple encryption algorithms, including software based and FIPS approved UCM based solutions. • ADP/AES/DES/DES-XL/DES-OFB/DVP-XL. • Multi-Algorithm/Multi-Key Support. • Over the Air Encryption Key Management OTAR. • Tactical OTAR and P25 OTAR capability • 96 Encryption Keys/Radio. • Hardware and Software Encryption: — 40kbit RSA Software Encryption (ADP). — Type III/IV Hardware UCM Encryption. P25 System and Services Agreement (R1422515R1/P1) Page 29 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 — FIPS140 Certification with UCM Module. The APX 6500 uses ASTRO 25 infrastructure's Integrated Voice & Data capabilities to support the following optional data applications: • Over -the -Air Programming (POP25). • Integrated GPS for personnel location. • Text Messaging. APX 7500 MOBILE RADIO The APX 7500 offers all of the communications features and benefits of our APX line of radios in an easy -to -install design. Reliable Construction The APX 7500 mobile platform dramatically improves reliability by reducing the number of discreet parts and connectors. Side connectors with hard gold contacts molded into plastic eliminate loose wires and parts, and radial silicone seals protect the internal components. The radio housing is ultrasonically welded to distribute impacts over the entire area of the radio and additional adhesive layers and gaskets prevent water intrusion. Easy Vehicular Installation and Serviceability The APX has hard gold contacts molded into plastic to eliminate loose wires and There are two models of the APX 7500: the APX 7500 Mid - parts Power and APX 7500 High Power. The Mid -Power version is designed to maintain the same mounting footprint as the XTL mobile radio. This makes them easy to install and allows reuse of mounting holes and cables. The High Power version's trunion was completely redesigned to include installation guides and rails, better engagement into the tray, and enhanced handle grip. This enables the radio to be removed and installed easily and quickly, without removing the cables. All APX 7500 mobile radios can be equipped with 12 character RFID optional tags, which provide a fast, accurate way of obtaining valuable asset tracking information without having to uninstall the radio. Multiple Control Heads Each APX 7500 mobile radio can be controlled by multiple control heads, with four different wired locations. There are five control heads available on the APX7500: the 02, 03, 05, 07, and the 09. /—A a Motorola's APX 7500 consolette, shown in Figure 1 provides high -tier mobile features, designed in a compact, specialized housing, with a built-in power supply. P25 System and Services Agreement (R1422515R1/P1) Page 30 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Figure 1: Full Front Panel w/05/Keypad/Clock/Vu—L999 Model APX 7500 Consolettes The APX 7500 mobile supports a control station configuration including: • Base -mount with enclosure. • Desktop use or rack mountable. • AC or DC powered with power cable. • Internal speaker. • Tone remote, digital remote or local control. • Full front panel display with keypad, clock, and VU meter (L999 model). • Limited front panel display with clock and VU meter (L998 model). Consolettes are ideal for local law enforcement, utility, and transportation users who need a low cost desktop control station or wireless dispatch solution. These consolettes can also be used as an emergency backup station, a low-cost dispatch center for local agencies, and as a fire station alerting system. They are offered in local, tone remote, and digital remote control configurations. Please note that the consolette AC power supply does not contain circuitry for charging a battery to provide back-up power for the consolette. Motorola Solutions recommends operating the consolette via AC power and UPS, or by DC power from an external DC power system with battery back-up power. APX 8000 PORTABLE RADIO With four RF bands and multi -mode system access, the APX 8000 allows users to communicate across borders using a single device. Use analog MDC 1200 or digital P25 mode, conventional or trunked operation, SMARTNET or SmartZone legacy systems, clear or secure - all across 7/800MHz, VHF and UHF Range 1 & 2 bands. Adaptive Audio Engine Whether it's loud or windy, whether you whisper or yell, the APX 8000 adaptive audio engine and ultra -loud speaker brings clarity into every conversation. The radio dynamically changes the level of noise suppression, microphone gain, windporting, and adaptive speaker equalization to consistently produce the loudest, clearest audio in any environment. P25 System and Services Agreement (R1422515R1/P1) Page 31 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Comfortable Design Intuitively designed with a familiar look and feel, the compact APX 8000 is always comfortable to use, from your holster to your grip. The aggressive T-shape makes the radio easier to grip, even with wet or slippery hands. It contains four radio bands and a flexible, all -band antenna. Rugged and Durable The APX 8000 has a water -tight seal, drop -resistant dual battery latch, pressure -tested tempered glass display, and a shock -absorbing aluminum alloy endoskeleton, ensuring that the APX 8000 is ready for unpredictable environments. It can survive 2 meter water submersion for 2 hours, the MIL -STD 810 C, D, E, F, G procedures, and Motorola's renowned Accelerated Life Test. Models Available for the APX8000 The APX 8000 is available in three models. Model 1.5 Model 2.5 Model 3.5 Top Display Top and Front Display with Top and Front Display Limited Keypad with Full DTMF Keypad The Top Display (Model 1.5) features: • Up to 3000 Channels. • Full Bitmap Top Display: — 1 line of icons. — 1 line x 8 characters of text. — Multi -color backlight. • No keypad. • Buttons & Switches: — Large PTT Button. — Angled On/Off volume control. P25 System and Services Agreement (R1422515R1/P1) Page 32 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 — Orange emergency button. — 16-position top -mounted rotary switch. — 2-position concentric switch. — 3-position toggle switch. — 3 programmable side buttons. The Top and Front Display with Limited Keypad (Model 2.5) includes all the features of the Model 1.5, plus the following: • Full Bitmap Display: — 2 lines of icons. — 4 lines x 14 characters of text. — 1 menu line x 3 menus. — White backlight. • Backlit Keypad: — Home and Data buttons. — 3 soft keys. — 4 direction navigation key. Finally, the Top and Front Display with Full DTMF Keypad (Model 3.5) includes all the features of the Model 2.5, with the addition to a 43 DTMF keypad. P25 System and Services Agreement (R1422515R1/P1) Page 33 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX XE PORTABLE RADIOS APX Variants: XE (Extreme Edition) Series Product Advantages The XE Mission Extreme feature addition to the APX radio line provides Fire Departments with the level of ruggedization and survivability needed in the especially harsh environments seen by Fire first responders. Motorola Solutions has included several key new innovative features to enhance personnel safety. The APX XE series of radio solutions provides extreme rugged and ergonomic design with innovative features developed specifically for the fire market to enhance personnel safety in extreme environments. Fire -Centric Audio Enhancements • High -strength atuminumalloy chassis • Sealed endoskele€onkeeps liquids out Durable plashcouter housing resists high-impactshocks and drops Ensure the right radio goes with the right respanderwiM optronal colored housing Meets or exceeds stringent MIL-STD specifications High impactdispiay for quick, easy reading Rugged option avaiiahie • "led controls provides assurance 2Mease of use forgioved hands Rugged design to withstand harsh environments Enlarged top display with intelligent lighting provides information at a glance • Superior RF and Factory Mutuai(FM) specifications • ExtrerneAudio Profile deiivers increased noise suppression tin loud Fireground environments • 2 microphone design for exceptional noise cancelling • Equipped with latest AMBE digital voice vocoder • 1w speaker class d amplification provides loudest radio an the market` line ::: man mom • New Extreme One applications such as man down Sided Audio Profile: — A unique audio profile with noise reduction algorithms and filters specifically designed for the most challenging of noise environments. • Enhanced Dual Microphone noise -cancelling. • Adaptive and fast acting dual -sided design that allows effective noise reduction regardless of what microphone the user is talking into. • Loudest Audio Output with least distortion. • Large 1Watt Rated Speaker that delivers clarity 50% louder than typical P25 Radios. Fire -Centric Ergonomic Enhancements Project 25 Phase 2technology provides twice the voice capacRy Mili band operation for seamless interoperahility' Backwards and forwards compatible with all Motorola ASTRO Mission Critical radio systems Mission Critical Wireless and GPS capable Capable to support futureto support • Protective Bumper Ring. • Exaggerated Knobs and Controls. • PTT/Side Button design changes for Improved Gloved Operation: — Larger Ridge/Increased Texture. — Larger programmable side buttons. P25 System and Services Agreement (R1422515R1/P1) Page 34 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Rubber over mold for improved grip. • Redesigned speaker grill for improved water porting. • Larger emergency button. • Taller top display for larger fonts. Video Demonstrations of APX XE Series Performance The following URL provides a video presentation which illustrates the advantages of APX XE series radio equipment with compelling live demonstrations of APX audio performance: http://video.motorolasolutions.com/video.aspx/motorola-s-apx-xe-remote-speaker- microahone/1094198138001. In an effort to deliver optimal intelligible audio in the presence of high background noise, the use of "Best Practices" as defined by the International Association of Fire Chiefs (IAFC) along with optimal Customer Programming Software (CPS) audio settings in the radio, have also shown to be very beneficial in delivering improved communications. The following URL provides additional best practices for Fire agency users with Motorola APX XE series radios which have been presented to the International Association of Fire Chiefs: http://video.motorolasolutions.com/video.aspx/say-it-loud-and-clear/2203239567001. APX 8500 MOBILE RADIO The APX 8500 offers all of the communications features and benefits of our APX line of radios in an easy -to -install design. The APX 8500 includes four RF bands and multi -mode system access. The APX 8500 is designed to communicate across borders using a single device. The interoperability of the APX 8500 allows users to employ analog MDC 1200 or digital P25 mode, conventional or trunked operation, SMARTNET or SmartZone legacy systems, clear or secure; all across 7/800MHz, VHF and UHF Range 1 & 2 bands. Reliable Construction The APX 8500 mobile platform dramatically improves reliability by reducing the number of discreet parts and connectors. Side connectors with hard gold contacts molded into plastic eliminate loose wires and parts, and radial silicone seals protect the internal components. The radio housing is ultrasonically welded to distribute impacts over the entire area of the radio. Additional adhesive layers and gaskets prevent water intrusion. Easy Vehicular Installation and Serviceability The APX has hard gold contacts molded into plastic to eliminate loose wires and The APX 8500 is a mid -power version mobile radio, designed parts for ease of installation. All APX 8500 mobile radios are equipped with 12 character RFID tags, which provide a fast, accurate way of obtaining valuable asset tracking information without having to uninstall the radio. P25 System and Services Agreement (R1422515R1/P1) Page 35 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Multiple Control Heads Each APX 8500 mobile radio can be controlled by multiple control heads, with four different wired locations. There are five control heads available: the 02, 03, 05, 07 and 09. The 02, 03, and 07 are available in dash mount and remote mount configurations. The 03 and 09 are available in remote mount configurations only, and have a screen and keypad for detailed data inputs. APX ACCESSORIES Remote Speaker Microphones (RSMs) Motorola Solutions APX RSMs and PSMs deliver audio that is clearer, easier to understand, and up to 50% louder than XTS-series RSMs. That's because they have the same speaker found in our APX portable radios — for the best -in -class accessory audio available. Some RSMs feature leading -edge IMPRES technology which communicates with the APX radio to help suppress ambient noise, improve voice intelligibility, and amplify loudness — even in noisy situations and difficult weather. Broward County agencies can rely on Motorola Solutions RSMs to carry on a conversation clearly even with traffic rushing by or pumper trucks running. Shows Information Instantly Select from a variety of models, including RSMs with a display. These easy -read screens let users see zone and channel information at -a -glance. Since the display mirrors the one on top of the portable, it delivers the information users need, when they need it. Many of our RSMs/PSMs give users immediate access to radio controls —from volume and channel selector to emergency and programmable buttons. Reduce Background Noise The Windporting feature on select RSMs/PSMs is specifically designed for windy outdoor environments. Windporting dramatically reduces the noise caused by howling winds and harsh weather. In addition, it prevents water from clogging the microphone and distorting transmissions. In a domed stadium or an open-air event, noise -canceling acoustics on select RSM models negate background noise so your voice comes through loud and clear anytime you speak into the microphone. Whatever the work condition, there's a microphone made for each unique situation. Endures Adverse Conditions Many of our RSMs and PSMs meet tough specs — IP57 submersibility ratings — to withstand water immersion longer. Even if users drop them in a puddle or wear them in the rain, they'll stay connected. Our rugged accessories take toughness further — exceeding IP57 standards for submersibility and providing an optimal level of water protection. If you're on the fireground and your RSM gets drenched by a hose, it will stand up. Display RSMs sport the first rugged, submersible audio jack so you can receive discreet communications with a separate earpiece accessory and not worry about water damaging your connection. P25 System and Services Agreement (R1422515R1/P1) Page 36 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX XE Remote Speaker Microphone Firefighter safety is critical to us. Motorola Solutions has teamed up with first responders around the world to develop a rugged remote speaker microphone (RSM) that complements our APX XE radios and withstands the harshest conditions. The APX XE RSM is part of our complete portfolio of fire -specific radios and accessories, with ultra -rugged features, advanced ergonomics and special innovations to improve responder safety. From exaggerated controls to exceptional noise suppression, it's made for the noisiest, nastiest days. IMPROVED DURABILITY Extreme Water Porting Grill Enhanced grill for improved water porting. Generation 1 Gensrafion 2 i Extreme Temperature Cable Enhanced RSM cable designed to withstand heat temperatures of up to 500'F_ IMPROVED FUNCTIONALITY Continuous Light Control (Flashlight)"' Dedicated front button that allows user to turn on/off LED light. Light Control Button I Requires long press of 1 NNTN8203 second to turn light orloff 4F flashlight function. EXTREME Water Porting Grill Enhanced grill for improved _ water porting. ' I EXTREME Temperature Cable Enhanced to withstand extreme Pleat corditions. r , ■ mono mom ttr NNTN8203 YLW NNTN8203 BLK Everything about the XE RSM is designed for easy use on the fireground. From exaggerated controls, you can operate with bulky gloves to an asymmetrical shape so you can find the controls you need without looking. The large emergency button is easy to locate, but shielded so it's not accidentally activated. The prominent push -to -talk button is easy to find and press with gloves on. The easily accessible, programmable buttons and a volume switch on the corner of the RSM that "rocks up and down" to distinguish it from other controls. The XE RSM is available in three different housing colours to meet your specific needs and includes a large metal D-ring that flips up or down so you can attach it any way you want on your turnout gear. A high visibility strobe light activates when the emergency button is pressed, this strobe has been verified by firefighters in training conditions to be visible in smoke up to 10 feet. In addition, if the RSM is sprayed with a hose or dropped in a pool of water, you will see what rugged specs and a unique water -draining speaker design really mean. Noise Suppression at its Best The XE RSM is the first accessory with dual microphones that locate the talker and cancel out background noise. It suppresses noise so effectively, you can be heard in the loudest environments —over roaring fire, pumper trucks and wailing sirens. A large speaker delivers the loudest, clearest accessory audio available — 50% louder and clearer than our existing XTS RSMs —so transmissions are clear and intelligible, not distorted or garbled. Because the XE RSM P25 System and Services Agreement (R1422515R1/P1) Page 37 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 leverages the exceptional noise suppression technology of our best -in -class APX radios, you can be heard and be clearly understood in all types of extremes. UL RATED Channel change knob designed for easy access XE-100 RSM • Extra large emergency button with embedded orange lighting PMMM4106 Transmit LED to match radio transmit LED Excellent audio with 5 MIC DINC X Noise Suppression for clear audio in traffic noise, crowds, sirens and other loud environments • Clear and crisp audio in rain and wind UL RATED Reduced TX idle noise xE-500 RSM PMMN4106_BLK Withstands heat shock conditions of 500 F (260 C) for at least 5 minutes Drains water from any wearing position • Waterproof built to I1368, 2 meters 2 hours (Delta T) Microphone protected from dirt • Improved XE-treme temp cable — surpasses competing vendor RSM cables • Intrinsic Safety Rating: XE-500 RSM - UL (TIA4950) xE RSM THE RIGHT FIT AND FEEL FOR FIREFIGHTERS VOLUME D-RING LOOP - TOGGiE �I SWITCH 760 DEGREE CLAMPING CLIP. RICH VI31&CITY REFLECTIVE STROBE L11BEL I STROBE DUAL CONTROL LIGHT MCROPHONES WATER- PROGRAMMABLE RESISTANT BUTTON LARGE, YET SPEAKER i, .__ PROTECTED 1 EMERGENGY HIG4- FIELD BUTTON IMPACT REPLACEABLE GREEN CABLE COLOR P25 System and Services Agreement (R1422515R1/P1) Page 38 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX XE RSM A REMOTE SPEAKER MIC DESIGNED FOR FIREFIGHTERS Asymmetrical form factor allows user to orient without looking Protected PT with strong tachlefeedback Large volume toggle switch 350 degree durable clamping clip and large d-ring hook Rugg ed specifications to withstand harsh environments 1st RSM to feature 2-microphone design for exceptional noise cancelling Larger 1w speaker provides 501A louder audio than existing XTS RSMs Optimized to perform with best -in -class APX portable family • High impact green color • Reflective label on front for increased visibility • Emergency activated strobe lightviewable up to 10' feel in thick smoke • Compatible with ALL APX portables APX Extreme Performance (XP) RSM Designed with mission critical law enforcement users in mind, the APX XP RSM suppresses noise so effectively, you can be heard over traffic noise, crowds and sirens. Its unique dual - microphone design tracks the talker's voice so that you can keep your eye on what is in front of you while still talking on the microphone. A digital signal processor (DSP) algorithm helps suppress background noise so you can be heard clearly regardless of the noise around you. It includes a flexible 360-degree rotatable shoulder clip, designed specifically to fit comfortably on the police uniform epaulet. A D-ring provides an additional attachment option. This IMPRES RSM is the thinnest RSM in the APX portfolio and is specifically designed for tough mission critical use — buttons are enlarged for easy access, yet recessed to avoid accidental activation. Mission Critical Wireless - Bluetooth Accessories Motorola's APX 4000, 6000, and 8000 portable radios ship standard with Bluetooth functionality enabled. Broward County users can use COTS Off -The -Shelf Bluetooth accessories or Motorola Mission Critical Wireless accessories to meet their operational needs. P25 System and Services Agreement (R1422515R1/P1) Page 39 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Mission Critical Wireless Proprietary wireless Bluetooth protocol for Motorola Certified Accessories. •MCW Wireless POD •Discrete covert accessories Bluetooth COTS -Supports COTS protocol for wireless audio accessories. -Allows for 3rd party integration support for I P data devices. PAN (Personal Area Network) -Up 10 7 simultaneous BT Connections (6 Data + 1 Audio) -Connection range: 10 meters (33 ft), line of sight. F'rUMN EaSed 1243 bit [_ eM M Vacs C.IXY1CCtirn is s3 urc with F'ainnq Mat taAos loss then 2s. %01[ LO oncryptlon K—Jy iu talk in Iw lhwr b, No ddilicrwl latux:y wi— using tl. 13luetwlh PTT — nc[.W,FQ the PTT dirMily Gun thn radio Motorola Solutions Mission Critical Wireless Advantages • CRITICAL VOICE ON DEMAND — With enhanced security, quick pairing and fast push - to -talk (PTT), our APX Mission Critical Wireless portfolio stands out in meeting these most critical criteria. When you use our accessories with Bluetooth-enabled APX radios, you can be sure every data transmission and every word gets through. • JUST "TOUCH" AND GO — Our accessories pair with just a "touch" and usually connect in less than 10 seconds — even around other Bluetooth devices. Grab an earpiece or earbuds, place the PTT pod within an inch of any APX portable and securely pair. There's no need to enter codes or navigate through menus. • EVERY TRANSMISSION IS SECURE — While the APX radio is pairing, a Bluetooth ID and a strong 128-bit key are exchanged to encrypt the Bluetooth link. P25 System and Services Agreement (R1422515R1/P1) Page 40 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Body -Worn Cameras/Video Speaker Mics DEMS Si500 Motorola Solutions latest innovation addresses the need for body cameras. Motorola Solutions has integrated a camera device with the APX radio creating a Video Speaker Microphone (VSM). This innovation reduces the need for additional devices for all types of responders that seek a body camera solution. Motorola Solutions is completing beta tests currently and will be releasing this product in Q3 of 2016. The advanced body cameras and cloud storage solution offers any of Broward County users the ability to leverage their current investments of APX radios, PremierOne CAD and an ASTRO 25 radio network to the fullest. Body -Worn Camera Complete Solutions with Command Central Vault Cloud Storage Our Solutions combines the power of Si500 VSMs with CommandCentral Vault which provides foundation for anybody —worn program. • CommandCentral Store. • CommandCentral Manage. • CommandCentral Judicial. • Flexible storage models: — 100GB of storage per user per year. — Combine all storage into one large bucket of storage for all to share. Si500 Video Speaker Microphone Sight and Sound Simplified—Si500 Motorola's Si Series Video Speaker Microphones (VSM) (Figure 2), enables agencies to trim down the number of devices needed for public safety personnel to do their job effectively. An extension of the high —performing Motorola APX` radio, the Si Series is a smart interface with an integrated remote speaker microphone and body —worn camera in one. It assures the reliable voice and mission critical sight, sound and security your officers need to work more safely. The Si500 VSM combines voice communications, video, still images, and emergency alerting into one compact and easy —to —use device. Extend the Power of APX, Best —in —Class Performance Like our industry —leading APX radios, every feature and function of the Si500 VSM is designed with your safety in mind: from best —in — class audio to purpose—built ergonomics. Figure 2: Si500 Video Speaker Microphone The Si Series VSM is Ultra —rugged, IP67 and MIL —STD rated for harsh environments The new Adaptive Audio Engine that automatically adjusts audio settings based on the user's wearing position and environment. With five integrated microphones and a loud 0.5—watt rated speaker, it provides the same audio quality of the APXTm 6000 portable radio. P25 System and Services Agreement (R1422515R1/P1) Page 41 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Si500 Key Features • 100+dB Audio delivers APX audio quality. • Five integrated microphones with adaptive audio technology. • Articulating camera optimizes your recording field of view based on officer body type and posture. • 0.5 Lux low light performance. • Pre —buffering to capture events prior to recording (video and/or audio). • Automatic recording with the press of the emergency button on VSM or APX radio and with external Bluetooth sensor triggers. • 32GB storage on the device. • Integrated Wi—Fi for wireless video download. • Video metadata captures time, date, and location via GPS with APX subscriber connectivity. • Flexible energy solutions (see Figure 3, 4 and 5. Purpose Built Controls • Large Volume & PT_ Controls • Flexible Programma Buttons Audio Privacy • Private audio via 3_ audio connector MO�'OROLa Flexible Configuration • Articulating camera for optimized video & photo capture • Configurable record LED and Covert` Device mode Automated Video Capture • Record via manual slider. or configure automated recording with Emergency or BT Sensors Figure3: Ergonomics of the Si500 VSM '_O 210-Adiculabrig Camera �a Optimized for realistic low -light video Still image capture Preview mode Review mode 1 Adiculating (� Camera Video tagging Covert Mode Metadata Integration Operation Large Icon. Vibration and Audible Tone Emergency Indicate Recording Button P25 System and Services Agreement (R1422515R1/P1) Page 42 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Figure 4: Video Functionality of the Si500 VSM ACTIVITY Iieuu im"Im . n.P.n nwra' rrr HOME PANEL CONVERSATIONS rt� , nun t i 6 H 0_ 1—1 DAM ]dr] laetleY 7 tart tL1R1Wee GrnYI8L4M Figure 5: Radio Functionality of the Si500 VSM CommandCentral Vault CommandCentral Vault is a cloud —based content management solution to securely store, review, manage and share all forms of digital evidence. It provides a single place to aggregate evidence from multiple sources such as fixed video, social media, body -worn cameras (such as the Si500/300), audio notes and other multimedia sources. Supporting both automatic and manual uploads combined with end —to —end streamlined content management enables agencies to simplify workflows and the overhead of dealing with increasing amounts of content. CommandCentral Vault is fully integrated with Motorola's Si500 VSM and supports other sources of body -worn camera video evidence. Simplified Storage Multimedia captured from the Si500 is seamlessly transferred into CommandCentral Vault via secure Wi—Fi network connection. Multimedia stored in CommandCentral Vault can be automatically tagged and grouped with associated call to service event from CAD and further associated to a record ID or case within your Records Management System (RMS). This will dramatically reduce manual administrative workload from the staff as compared to other systems where you would have to manually enter in this information. CAS Security CommandCentral Vault uses a CAS Government Cloud to store all content securely and is contractually committed to meeting CAS requirements. Secure uploading of multimedia content eliminates the hassle, maintenance and security challenges of an on —site storage solution. P25 System and Services Agreement (R1422515R1/P1) Page 43 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 CommandCentral Vault Key Features • CJIS—capable government cloud storage. • Automated redaction, eliminating tedious frame —by —frame process. • Dynamic watermarking to prevent unauthorized screen capturing and sharing. • Secure chain of custody with cryptographically signed content, preventing manipulation. • Role —based access. • Advanced end —to —end content management: capture, review, manage, and share. • Simplified multi —media storage and transfer from Si500/Si300 as well as external ingestion of video, photographs, and documents into the case folder. CommandCentral Vault Capabilities Streamlined Workflow and Redaction CommandCentral Vault enables users to quickly and easily search, review, annotate, mark, provide additional tags and playback content with a geospatial view to quickly identify when and where content was captured. It significantly streamlines the redaction process allowing users to simply select an object or individual and automatically apply the logic across the entire video, saving hours of administrative time. Agency administrative personnel also have complete control over what capabilities users have to comply with their policies. Simple Sharing CommandCentral Vault provides streamlined end —to —end content management from the moment an incident is recorded by an officer to when it may be requested internally or externally from your government enterprise. Rapid prioritization and fulfillment saves time and delivery of content is fast and secure. From judicial requests to citizen FOIA requests, CommandCentral Vault provides customizable agency forms, workflow, and queuing tools to simplify sharing. Maintain Chain of Custody CommandCentral Vault ensures end —to —end security of stored content, and original content is never edited to reduce challenges to the chain of custody. Full auditing allows your agency to track all activity on content from the moment it's stored and classified. CommandCentral Vault —Store Module The CommandCentral Store module is the baseline a a __t ` ENO-TOENO CONTENT M-GEMENT ENO-TO£NG SECURITY AUTOMATED REWCTION Pomnul.s OipN.ny.IBmtl wnbnt EIIminel. tedmo nw-Ih^lrnnb ovana wyoloprapnicaly e.cmg_s.Igc anae w.incaue�.1 wonGis awasa �>a�aarec �ewss nre vteao. AUTOCORREIATE CU� CE METAUPTA SHARISiTNOOY SNARING Un4 t0 CAO.IM RMS I. nq..Mn 9implry and ntluc. tls.t. mnimia tl e,.Z T.ad. a� 4.n. le NMIt f.q�.sh a.r,n�..tiv. owm..a rctrvnr wtu. tun ..aa���aPamiry. ..nn �e...�nl., a.r-m-�ne...une m.n...ne package provided by CommandCentral Vault and is offered on a per user license basis. It provides licensed users the ability to seamlessly upload content from multiple sources, P25 System and Services Agreement (R1422515R1/P1) Page 44 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 including body —worn devices via secure Wi—Fi. Cloud storage that meets CJIS standards is included as well as the ability to perform the following actions on stored content: • Annotate images and video to provide additional context during review. • Automatic association of stored content with CAD/RMS data to group related case files and provide faster search for case related content. • Review content and associated metadata with geospatial mapping playback. • Chain of custody controls to preserve and verify original content. • Mark content to adhere to retention policies. CommandCentral Vault —Manage Module With the optional Manage module your agency can select to enhance content management capabilities. With the Manage module your entire agency (per user licensing does not apply) is provided all the capabilities with the baseline Store module, including: • Agency —wide content search for permitted users. • Enhanced review functionality with playback speed controls. • Additional administrative content restriction controls. • Automated redaction based on facial and/or object recognition. CommandCentral Vault —Judicial Module With the optional judicial module your agency can rapidly share evidence and other content with legal personnel reducing administrative overhead and delays. With the Judicial module your entire agency (per user licensing does not apply) is provided all the capabilities of the Store and Manage modules, including: • Creating video clips to provide specific evidence related to a judicial request. • Restricted distribution to ensure only permitted individual have access to necessary content. • Secure links to requested content to maintain chain of custody. CommandCentral Vault —Public Information Request, FOIA Module In addition to Store capabilities you receive: • A secure, agency —branded web portal to enable FOIA requests from the public. • The ability to collect payments for FOIA requests. • The ability to tailor customizable workflow forms to your agency needs. • Automated redaction based on facial and/or object recognition. P25 System and Services Agreement (R1422515R1/P1) Page 45 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 Batteries and Battery Chargers Motorola Solutions created our patented IMPRES technology as an integral part of our two-way radio batteries and chargers. Users who rely on IMPRES call it innovative and indispensable. We call IMPRES the intelligent way to communicate — offering enhanced performance and exceptional capabilities for your radio, your battery and its charger, and your users. IMPRES Smart Energy System Our innovative IMPRES battery charging and reconditioning system streamlines and automates battery maintenance. It draws on our exclusive technology that enables communication between battery and charger to help lengthen battery life and extend talk time. Automates Battery Maintenance Users want to be sure they can get the most out of every battery by maximizing its life. IMPRES automates battery reconditioning, adapting the intervals to each battery's usage pattern. IMPRES batteries and chargers have the capability to exchange data. This allows the IMPRES charger to evaluate the usage pattern of an IMPRES battery and determine the optimum reconditioning interval, thus optimizing battery life. Eliminates Overcharging IMPRES batteries can be left in their IMPRES chargers for extended periods without heat damage from the charger. If radios are accidentally left in the charger — overnight, over a weekend or longer — there should not be any worry about shortening the battery's life. Because the IMPRES charger automatically monitors battery capacity, batteries are safely charged to the right capacity and always ready to go. Better Data for Better Decisions IMPRES batteries store critical usage information. Each two-line IMPRES charger display presents data at a glance, so users and administrators can make informed decisions about battery replacement. Data includes key information such as battery capacity, time remaining to complete charging, and each battery's unique serial number. If you are operating a large fleet of batteries, IMPRES Battery Data Reader is a valuable diagnostic tool to evaluate individual IMPRES batteries. Furthermore, IMPRES Battery Fleet Management collects and consolidates that data automatically, so you can quickly and easily identify when batteries need to replaced. Tested Tough and Proven Tough All Motorola IMPRES batteries are Proven Tough. Time after time, in lab test after test — for Drop, Vibration and ESD (Electrostatic Discharge) — they withstand shocks, knocks, drops and shakes and outperform the leading brands. If your radio is banged on a ride, rattled by heavy equipment or shocked by static electricity, you can depend on IMPRES batteries to stay true and stand tough. IMPRES Advantages include: Batteries are charged based on kit number. P25 System and Services Agreement (R1422515R1/P1) Page 46 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 • Accommodates a mixed fleet of batteries transitioning from non-IMPRES to IMPRES systems. • Continuous monitoring of charge temperature. • Negative pulse charge algorithm. • Intelligent charge control allows batteries to be stored in a charger indefinitely. • Eliminates unnecessary reconditioning that reduces life. • Maximizes battery life. • Enables extended warranties. Battery Recharge Time Under typical charge cycles, most batteries will be charged in an hour with a rapid charge. Motorola's IMPRES chargers are specifically designed to match current drain profiles of the APX portable to maximize battery life and performance over time. Max battery charge rate (min time) is governed by the cell's ability to absorb charge. The cell manufacturers spec the max charge rate and we follow their recommendations to maximize cell life. 3.0 Pricing All Subscriber Equipment and Subscriber Equipment Maintenance shall be offered and available to the County and all Eligible Purchasers at the prices listed in the following pages, minus the applicable discount listed below. Radio pricing excludes the costs for installation and unit programming. No minimum quantity requirements apply unless expressly stated below. In the event more than on discount rate applies, only the higher discount rate will be applied. Discount Duration of Availability Discounted Product(s) Discount Rate Standard Discount Duration of Agreement P25 configured subscriber radios 25% Subscriber accessories 23% Migration Incentive For two (2) years after the Effective Date of Agreement P25 configured subscriber radios 40% Subscriber accessories 29% Volume Discounts: 500-999 Duration of Agreement P25 configured subscriber radios 30% Subscriber accessories 25% Volume Discounts: 1000-1999 Duration of Agreement P25 configured subscriber radios 33% Subscriber accessories 27% Volume Discounts: 2000 and greater Duration of Agreement P25 configured subscriber radios 40% Subscriber accessories 29% P25 System and Services Agreement (R1422515R1/P1) Page 47 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 DESCRIPTION LIST $ DISC % DISC $ RVN5224AE APX PORTABLE & MOBILE PROGRAMING SOFTWARE (3YR SUBSCRIPTION) $399.99 0% $399.99 HKN6184C MOBILE PROGRAMMING CABLE, USB $52.00 23% $40.04 PMKN4012B MOBILE PROGRAMMING CABLE $77.00 23% $59.29 T7914 RADIO MANAGEMENT ONLINE $0.00 20% $0.00 UA00049AA ADD: RADIO MANAGEMENT LICENSES ONLINE (PER RADIO) $100.00 20% $80.00 DESCRIPTION C►TY PRICE RADIO PROGRAMMING or REFLASHING RADIO (EXLUDES THE COST OF FLASH) MOBILE PER RADIO <51 $70.00 MOBILE PER RADIO 51-100 $54.00 MOBILE PER RADIO >500 $46.00 PORTABLE PER RADIO <51 $70.00 PORTABLE PER RADIO 51-100 $54.00 PORTABLE PER RADIO >500 $46.00 BUILDING TWO WAY RADIO PROGRAMMING TEMPLATES CITY PRICE 250 mode template with excel template 1 $620.00 REPROGRAMMING EXISTING RADIOS (EXCLUDE THE COST OF FLASH) RETUNING RADIO WITH UPDATED CODEPULUG AND FLEETMAP CITY PRICE PORTABLE & MOBILE <51 $70.00 PORTABLE & MOBILE 51-100 $54.00 PORTABLE & MOBILE >500 $46.00 RETUNING RADIO, UPDATE CODEPLUG AND FLEETMAP AND REMOVE LEGACY SYSTEM PROGRAMIING (2 TOUCH) PORTABLE & MOBILE <51 $140.00 PORTABLE & MOBILE 51-100 $108.00 PORTABLE & MOBILE >500 $92.00 DASH MOUNT RADIOS (Standard Sedan or Light Trucks) CITY PRICE INSTALLATION 1 $200.00 REMOVAL AT TIME OF NEW OR RE -INSTALLATION 1 $47.00 REMOVAL WITHOUT NEW OR RE -INSTALLATION 1 $65.00 REMOTE/ TRUNK MOUNT RADIOS (Standard Sedan or Light Trucks) CITY PRICE INSTALLATION 1 $270.00 REMOVAL AT TIME OF NEW OR RE -INSTALLATION 1 $65.00 REMOVAL WITHOUT NEW OR RE -INSTALLATION 1 $80.00 DASH MOUNT RADIOS (Ambulance or Fire Truck type vehicles) CITY PRICE INSTALLATION 1 $465.00 REMOVAL AT TIME OF NEW OR RE -INSTALLATION 1 $165.00 SECONDARY REMOVAL AT TIME OF NEW OR RE -INSTALLATION 1 $65.00 REMOVAL WITHOUT NEW OR RE -INSTALLATION 1 $195.00 SECONDARY REMOVAL WITHOUT NEW OR RE -INSTALLATION 1 $65.00 P25 System and Services Agreement (R1422515R1/P1) Page 48 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 REMOTE MOUNT (Ambulance or Fire Truck type vehicles) CUSTOMER PRICING CITY PRICE SINGLE CONTROL HEAD TYPE INSTALLATION 1 $465.00 DUAL CONTROL HEAD TYPE INSTALLATION REQUIRE SURVEY TO ENSURE CUSTOMER EXPECTATION IS PROPERLY MET 1 QUOTED REMOVAL AT TIME OF NEW OR RE -INSTALLATION (SINGLE CONTROL HEAD) 1 $165.00 REMOVAL WITHOUT NEW OR RE -INSTALLATION (SINGLE CONTROL HEAD) 1 $270.00 REMOVAL AT TIME OF NEW OR RE -INSTALLATION (DUAL CONTROL HEAD) 1 $170.00 REMOVAL WITHOUT NEW OR RE -INSTALLATION (DUAL CONTROL HEAD) $ 1 $285.00 CONTROL STATIONS CITY PRICE INSTALLATION: (Includes penetration of (1) wall 50 ft of 1/2 inch cable, installation of cable, connectors, yagi RF antenna type antenna) 1 $500.00 REMOVAL 1 $195.00 PORTABLE SUBCRIBER SERVICE FROM THE START LITE <500 LITE <500 COMPRE HENSIVE <500 COMPRE HENSIVE >500 APX4000 $50.40 $49.00 $98.40 $96.60 APX6000 $50.50 $49.00 $98.40 $96.60 APX8000 $70.50 $69.00 $118.00 $116.75 PORTABLE SUBCRIBER LOCAL SUPPORT <500 >500 APX4000 $66.00 $64.35 APX6000 $66.00 $64.35 APX8000 $78.00 $76.05 PORTABLE SUBCRIBER PICK UP AND DELIVERY <500 >500 APX4000 $24.00 $23.40 APX6000 $24.00 $23.40 APX8000 $24.00 $23.40 MOBILE SUBSCRIBER SERVICE FROM THE START LITE <500 LITE <500 COMPRE HENSIVE <500 COMPRE HENSIVE >500 APX4500 $74.40 $72.45 $122.40 $120.60 APX6500 $74.40 $72.45 $122.40 $120.60 APX7500 $95.20 $92.84 $127.63 $125.08 MOBILE SUBSCRIBER LOCAL SUPPORT <500 >500 APX4500 $42.00 $40.95 APX6500 1 $42.00 1 $40.95 APX7500 1 $54.00 1 $52.65 P25 System and Services Agreement (R1422515R1/P1) Page 49 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 MOBILE SUBSCRIBER PICK UP AND DELIVERY <500 >500 APX4500 $36.00 $35.10 APX6500 $36.00 $35.10 APX7500 $36.00 $35.10 CONTROL STATION SERVICE FROM THE START LITE <500 LITE <500 COMPRE HENSIVE <500 COMPRE HENSIVE >500 APX4500 $116.40 N/A N/A N/A APX6500 $116.40 N/A N/A N/A APX7500 $149.20 N/A N/A N/A APX8500 $149.20 N/A N/A N/A CONTROL STATION LOCAL SUPPORT <500 >500 <500 >500 APX4500 N/A N/A N/A N/A APX6500 N/A N/A N/A N/A APX7500 N/A N/A N/A N/A APX8500 N/A N/A N/A N/A MOTOROLA WILL WORK WITH ANYAGENCY IF SERVICES ARE DESIRED CONSOLETTE SERVICE FROM THE START LITE <500 LITE <500 COMPRE HENSIVE <500 COMPRE HENSIVE >500 APX7500 CONSOLETTE $95.20 $92.84 N/A N/A CONSOLETTE LOCAL SUPPORT <500 >500 <500 >500 APX7500 CONSOLETTE $54.00 $52.65 N/A N/A MOTOROLA WILL WORK WITH ANYAGENCY IF SERVICES ARE DESIRED PORTABLE PREVENTATIVE MAINTENANCE 1x ANNUAL <500 >500 APX4000 $50.40 $49.00 APX6000 $50.50 $49.00 APX8000 $70.50 $69.00 PORTABLE PREVENTATIVE MAINTENANCE BIANNUAL <500 1>500 APX4000 $95.75 $93.35 APX6000 $95.75 $93.35 APX8000 $133.95 $130.60 PORTABLE PREVENTATIVE MAINTENANCE 1x EVERY 2 YEAR <500 >500 APX4000 $50.40 $49.00 APX6000 $50.50 $49.00 APX8000 $70.50 $69.00 MOBILE, Control Station, or Consolette SUBSCRIBER PREVENTATIVE MAINTENANCE ANNUAL <500 >500 APX4500 $74.40 $72.45 P25 System and Services Agreement (R1422515R1/P1) Page 50 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX6500 $74.40 $72.45 APX7500 $95.20 $92.84 MOBILE, Control Station, or Consolette SUBSCRIBER PREVENTATIVE MAINTENANCE BIANNUAL <500 >500 APX4500 $148.80 $145.08 APX6500 $148.80 $145.08 APX7500 $190.40 $185.64 MOBILE, Control Station or Consolette SUBSRICBER PREVENTATIVE MAINTENANCE 1x EVERY 2 YEAR <500 >500 APX4500 $74.40 $72.45 APX6500 $74.40 $72.45 APX7500 $95.20 $92.84 P25 System and Services Agreement (R1422515R1/P1) Page 51 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 1000 PORTABLE RADIOS STANDARDAPX • • • YEAR WARRANTY MR �� MODEL DESCRIPTIONS H84UCD9PW5 N APX 1000 7/800 MHZ MODEL 1.5 PORTABLE • • CITY IDISC% LIST$ 25% DISC $ 1 25% $2,875.00 $2,156.25 40% DISC $ $1,725.00 H84UCF9PW6 N APX 1000 7/800 MHZ MODEL 2 PORTABLE 1 25% $3,075.00 $2,306.25 $1,845.00 H84UCH9PW7 N APX 1000 7/800 MHZ MODEL 3 PORTABLE 1 25% $3,275.00 $2,456.25 $1,965.00 OPTIONS(not limited to): CITY 1111111LIST $ 25% DISC $ 40% DISC $ G996 ADD: PROGRAMMING OVER P25 (OTAP) 1 2S% $100.00 $75.00 $60.00 QA09008 ADD: GROUP SERVICES 1 25% $150.00 $112.50 $90.00 H869 ENH: MULTIKEY 1 25% $75.00 $56.25 $45.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 QA09012 ADD: MISSION CRITICAL GEOFENCING 1 25% $150.00 $112.50 $90.00 QA01767 ADD: P25 LINK LAYER AUTHENTICATION 1 25% $100.00 $75.00 $60.00 QA2749 IMPRES LIION 2350MAH 1 25% $85.00 $63.75 $51.00 QA04146 ALT: IMPRES LIION 2800MAH 1 25% $100.00 $75.00 $60.00 QA01767 ADD: P25 LINK LAYER AUTHENTICATION 1 25% $100.00 $75.00 $60.00 H885 ADD: 3 YEAR SERVICE FROM THE START 11 0% $90.00 1 $90.00 1 $90.00 Q887 ADD: 5 YEAR SERVICE FROM THE START 11 0% $162.00 1 $162.00 1 $162.On P25 System and Services Agreement (R1422515R1/P1) Page 52 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 111 I • RTABLE RADIOS STANDARD• •ICE & DATA, GPS, BLUETOOTH, WHIP ANTENNA, 1900MAH WARRANTY H51UCF9PW6 N APX 4000 7/800 MHZ MODEL 2 PORTABLE 1 25% $3,988.00 $2,991.00 $2,392.80 H51 UCH9PW7 N APX 4000 7/800 MHZ MODEL 3 PORTABLE 1 25% $4,417.00 $3,312.75 $2,650.20 OPTIONS(not limited to): CITY STD DISC% LIST $ 25% DISC $ 40% DISC $ G996 ADD: PROGRAMMING OVER P25 (OTAP) 1 25% $75.00 $56.25 $60.00 QA01767 ADD: P25 LINK LAYER AUTHENTICATION 1 25% $75.00 $56.25 $60.00 QA03399 ADD: ENHANCED DATA 1 25% $112.50 $84.38 $90.00 QA04447 ADD: APX GEOFENCE 1 25% $112.50 $84.38 $90.00 QA09008 ADD: GROUP SERVICES 1 25% $112.50 $84.38 $90.00 H04 ADD: TACTICAL REKEY WITH MULTIKEY 1 25% $262.50 $196.88 $210.00 H869 ENH: MULTIKEY 1 25% $247.50 $185.63 $198.00 Q629 ENH: AES ENCRYPTION 1 25% $356.25 $267.19 $285.00 H499 ENH: SUBMERSIBLE (DELTA T) 1 25% $187.50 $140.63 $150.00 QA04934 ALT: IMPRES LI-ION 2500MAH RUGGED UL BATTERY 1 25% $37.50 $28.13 $30.00 QA02750 ALT: IMPRES LI-ION 2800MAH BATTERY 1 25% $100.00 $75.00 $60.00 H885 ADD: 3 YEAR SERVICE FROM THE START 1 0% $90.00 $67.50 $90.00 Q887 ADD: 5 YEAR SERVICE FROM THE START 1 0% $162.00 $121.50 $162.00 P25 System and Services Agreement (R1422515R1/P1) Page 53 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 . • .;.,ZA, 11JITEGRATEM VTICE & 1ATA, GPS,9LUET41TTS!, MODEL DESCRIPTION• H98UCD9PW5 N APX6000 7/800 MHZ MODEL 1.5 PORTABLE 1 25% $5,175.00 $3,881.25 $3,105.00 H98UCF9PW6 N APX6000 7001800 MODEL 2.5 PORTABLE 1 25% $5,496.00 $4,122.00 $3,297.60 H98UCH9PW7 N APX6000 7001800 MODEL 3.5 PORTABLE 1 25% $5,925.00 $4,443.75 $3,555.00 XTREME (XE) DELTA T/UL OPTIONS(not limited to): QTY DISC% LIST $ 25% DISC $ 40% DISC $ QA02006 ENH: APX6000XE RUGGED RADIO (standard UL battery NNTN8930 comes with option) 1 25% $800.00 $600.00 $480.00 QA05575 ALT: LIION IMPRES2 4500MAH UL/CSA 1 25% $165.00 $123.75 $99.00 OPTIONS(not limited to): QTY DISC% LIST $ DISC $ 40% DISC $ QA01843 ADD: MANDOWN OPERATION 1 25% $150.00 $112.50 $90.00 QA09006 ADD: ADAPTIVE NOISE SUPPRESSION & 3 WATT SPEAKER UPGRADE 1 25% $150.00 $112.50 $90.00 G996 ADD: PROGRAMMING OVER P25 (OTAP) 1 25% $100.00 $75.00 $60.00 QA01767 ADD: P25 LINK LAYER AUTHENTICATION 1 25% $100.00 $75.00 $60.00 QA00631 ADD: DVRS PSU ACTIVATION 1 25% $100.00 $75.00 $60.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 QA09012 ADD: MISSION CRITICAL GEOFENCING 1 25% $150.00 $112.50 $90.00 QA09008 ADD: GROUP SERVICES 1 25% $150.00 $112.50 $90.00 H869 ENH: MULTIKEY 1 25% $330.00 $247.50 $198.00 Q15 ADD: AES/DES-XL/DES-OFB ENCRYPTION 1 25% $799.00 $599.25 $479.40 Q629 ENH: AES ENCRYPTION 1 25% $475.00 $363.75 $285.00 Q498 ASTRO 25 OTAR W/ MULTIKEY (INCLUDES H04 TACTICAL) 11 25% $740.00 $555.00 $444.00 H04 ADD: TACTICAL REKEY WITH MULTIKEY 1 25% $350.00 $262.50 $210.00 QA06304 ATL: IMPRES 2 LIION 4500MAH - UL/CSA RUGGED 1 25% $100.00 $75.00 $45.00 QA05574 ALT: LIION IMPRES 2 UL/CSA 2650MAH 1 25% $110.00 $82.50 $66.00 H64 ALT: PUBLIC SAFETY YELLOW HOUSING 1 25% $25.00 $18.75 $15.00 QA01427 ALT: IMPACT GREEN HOUSING 1 25% $25.00 $18.75 $15.00 QA09001 ADD: WI-FI CAPABILITY 1 25% $300.00 $225.00 $180.00 H499 ENH: SUBMERSIBLE (DELTA T) 1 25% $150.00 $112.50 $90.00 HA00022AB ADD: 3 YEAR SERVICE FROM THE START 1 0% $90.00 $90.00 $90.00 Q887 ADD: 5 YEAR SERVICE FROM THE START 1 0% $162.00 $162.00 $162.00 P25 System and Services Agreement (R1422515R1/P1) Page 54 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX 8000 PORTABLE RADIOS STANDARD RADIO BUNDLE: P25, TDMA, INTEGRATED VOICE & DATAdj BLUETOOTH, WHIPWNA, 3100MAH BATTERY, 3 YEAR WARRANTY • • 0' DISC $ H91TGD9PW5 N JAPX 8000 ALL BAND MODEL 1.5 PORTABLE 1 $8,547.00 $6,410.25 $5,128.20 DUAL BAND 1 $7,747.00 $5,810.25 $4,648.20 SINGLE BAND 1 $6,947.00 $5,210.25 $4,168.20 H91TGD9PW6 N JAPX 8000 ALL BAND MODEL 2.5 PORTABLE 1 $8,753.00 $6,564.75 $5,251.80 DUAL BAND 1 $7,953.00 $5,964.75 $4,771.80 SINGLE BAND 1 $7,153.00 $5,364.75 $4,291.80 H91TGD9PW7 N JAPX 8000 ALL BAND MODEL 3.5 PORTABLE 1 $9,062.00 $6,796.50 $5,437.20 DUAL BAND 1 $8,262.00 $6,196.50 $4,957.20 SINGLE BAND 1 $7,462.00 $S,S96.50 $4,477.20 XTREME (XE) DELTA T/UL OPTIONS(not limited to): CITY LIST $ 25% DISC $ 40% DISC $ QA02006 ENH: APX8000XE RUGGED RADIO (standard UL battery PMNN4504 comes with option) 1 $800.00 $600.00 $480.00 QA05595 ALT: LIION 4100MA TIA4950 UL 1 $130.00 $97.50 $78.00 OPTIONS(not limited to). CITY LIST $ 25% DISC $ 40% DISC $ QA01843 ADD: MANDOWN OPERATION 1 $150.00 $112.50 $90.00 G996 ADD: PROGRAMMING OVER P25 (OTAP) 1 $100.00 $75.00 $60.00 QA01767 ADD: P25 LINK LAYER AUTHENTICATION 1 $100.00 $75.00 $60.00 QA09012 ADD: MISSION CRITICAL GEOFENCING 1 $150.00 $112.50 $90.00 QA00631 ADD: DVRS PSU ACTIVATION 1 $100.00 $75.00 $60.00 QA09008 ADD: GROUP SERVICES 1 $150.00 $112.50 $90.00 H869 ENH: MULTIKEY 1 $330.00 $247.50 $198.00 Q498 ASTRO 25 OTAR W/ MULTIKEY (INCLUDES H04 TACTICAL) 1 $740.00 $555.00 $444.00 H04 ADD: TACTICAL REKEY WITH MULTIKEY 1 $350.00 $262.50 $210.00 QA03399 ADD: ENHANCED DATA 1 $150.00 $112.50 $90.00 Q15 ADD: AES/DES-XL/DES-OFB ENCRYPTION 1 $799.00 $599.25 $479.40 Q629 ENH: AES ENCRYPTION 1 $475.00 $356.25 $285.00 QA09001 ADD: WIFI CAPABILITY 1 $300.00 $225.00 $180.00 H64 ALT: PUBLIC SAFETY YELLOW HOUSING 1 $25.00 $18.75 $15.00 QA01427 ALT: IMPACT GREEN HOUSING 1 $25.00 $18.75 $15.00 H499 ENH: SUBMERSIBLE (DELTA T) 1 $150.00 $112.50 $90.00 QA05573 ALT: LIION IMPRES 2 5100MAH DELTA T 1 $135.00 $101.25 $81.00 QA05571 ALT: LIION 4850MAH IMPRES DELTA T 1 $115.00 $86.25 $69.00 HA00022AB ADD: 3 YEAR SERVICE FROM THE START 1 $110.00 $110.00 $110.00 Q887 ADD: 5 YEAR SERVICE FROM THE START 1 1 $213.00 1 $213.00 1 $213.00 P25 System and Services Agreement (R1422515R1/P1) Page 55 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 APX 1500 MOBILE RADIOS•. • whip antennas and control MODELSTANDARD RADIO BUNDLE: P25, TDMA, IV&D, GPS, PALM MIC, 7.5 WATT SPEAKER, 3DB LOW PROFILE ANTENNA, 3 YEAR WARRANTY • CITY • • M36URS9PW1 N APX1500 7/800 02 CONTROL HEAD, DASH MOUNT 1 25% $3,881.00 $2,910.75 $2,328.60 CONTROL STATION OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ G91 ADD: CONTROL STATION POWER SUPPLY 1 25% $269.00 $201.75 $161.40 W665 ADD: CONTROL STATION OPERATION 1 25% $70.00 $52.50 $42.00 W382 ADD: CONTROL STATION DESK GCAI MIC 1 25% $169.00 $126.75 $101.40 OPTIONS (not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ GA01767 ADD: APX MOBILE RADIO AUTHENTICATION 1 25% $100.00 $75.00 $60.00 G335 ADD: ANT 1/4 WAVE 762-870MHZ 1 25% $14.00 $10.50 $8.40 G831 ADD: SPKR 15W WATER RESISTANT 1 25% $60.00 $45.00 $36.00 G996 ENH: OVER THE AIR PROVISIONING 1 25% $100.00 $75.00 $60.00 G683 ADD: ONE TOUCH STATUS MESSAGING 1 25% $75.00 $56.25 $45.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 GA00226 ADD: GPS ANTENNA 1 25% $75.00 $56.25 $45.00 GA09008 ADD: GROUP SERVICES 1 25% $150.00 $112.50 $90.00 GA01202AA ADD: APX GEOFENCE MOBILE 1 25% $150.00 $112.50 $90.00 G24 ADD: 3 YEAR SERVICE FROM THE START 1 0% $131.00 $131.00 $131.00 GA00318 ADD: 5 YEAR SERVICE FROM THE START 1 11 0% $246.00 1 $246.00 1 $246.00 P25 System and Services Agreement (R1422515R1/P1) Page 56 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 7='WAPX 11 MOBILE RADIOS(standard REMOTESTANDARD RADIO BUNDLE: P25, TDMA INTEGRATED VOICE & DATA GPS PALM YEAR WARRANTY (IF • MODEL• M22URS9PW1 N APX4500 7/800 02 CONTROL, HEAD DASH MOUNT MIC 7.5 WATT CITY 1 SPEAKER, 3DB LOW • 25% $4,381.00 PROFILE Al �EM • $3,285.75 $2,628.60 M22URS9PW1 N APX4500 7/800 02 CONTROL HEAD, REMOTE MOUNT 1 25% $4,493.00 $3,369.75 $2,695.80 CONTROL STATION OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ G91 ADD: CONTROL STATION POWER SUPPLY 1 25% $269.00 $201.75 $161.40 W665 ADD: CONTROL STATION OPERATION 1 25% $70.00 $52.50 $42.00 W382 ADD: CONTROL STATION DESK GCAI MIC 1 25% $169.00 $126.75 $101.40 OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ GA00631 ADD: DVRS MSU ACTIVATION 1 25% $250.00 $187.50 $150.00 G201 ADD:IMPACT GREEN COLOR HOUSING (02) 1 25% $25.00 $18.75 $15.00 G335 ADD: ANT 1/4 WAVE 762-870MHZ 1 25% $14.00 $10.50 $8.40 G831 ADD: SPKR 15W WATER RESISTANT 1 25% $60.00 $45.00 $36.00 G996 ENH: OVER THE AIR PROVISIONING 1 25% $100.00 $75.00 $60.00 G683 ADD: ONE TOUCH STATUS MESSAGING 1 25% $75.00 $56.25 $45.00 GA01767 ADD: APX MOBILE RADIO AUTHENTICATION 1 25% $100.00 $75.00 $60.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 GA00226 ADD: GPS ANTENNA 1 25% $75.00 $56.25 $45.00 GA01202AA ADD: APX GEOFENCE MOBILE 1 25% $150.00 $112.50 $90.00 GA09008 ADD: GROUP SERVICES 1 25% $150.00 $112.50 $90.00 G843AH ADD: AES ENCRYPTION 1 25% $475.00 $356.25 $285.00 W969 ADD: MULTIPLE KEY ENCRYPTION OPERATION 1 25% $330.00 $247.50 $198.00 G618 ADD: CBL REMOTE MOUNT 10 FEET 1 25% $10.00 $7.50 $6.00 G610 ADD: CBL REMOTE MOUNT 30 FEET 1 25% $25.00 $18.75 $15.00 G24 ADD: 3 YEAR SERVICE FROM THE START 11 0% $131.00 $131.00 $131.00 GA00318 ADD: 5 YEAR SERVICE FROM THE START 11 0% $246.00 1 $246.00 $246.00 P25 System and Services Agreement (R1422515R1/P1) Page 57 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 AFX 1 1 MOBILEIMD105 (standard whip STANDARD• • antennas 05 and control CONTROL headcables) ••111W 7M25URS9PW1 N • u• APX6500 7/800 MHZ MID POWER MOBILE 05 CONTROL HEAD, DASH MOUNT 1 25% $5,640.00 $4,230.00 $3,384.00 M25URS9PW1 N APX6500 71800 MHZ MID POWER MOBILE 05 CONTROL HEAD, REMOTE MOUNT 1 25% $5,812.00 $4,359.00 $3,487.20 CONTROL STATION OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ G91 ADD: CONTROL STATION POWER SUPPLY 1 25% $269.00 $201.75 $161.40 W665 ADD: CONTROL STATION OPERATION 1 25% $70.00 $52.50 $42.00 W382 ADD: CONTROL STATION DESK GCAI MIC 1 25% $169.00 $126.75 $101.40 DUAL CONTROL HEAD OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ GA00092 ADD: DUAL-CONTRL HD HARDWARE (must ladd additional mic, cables & speakers) 1 25% $570.00 $427.50 $342.00 OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ QA00631 ADD: DVRS PSU ACTIVATION 1 25% $100.00 $75.00 $60.00 GA00631 ADD: DVRS MSU ACTIVATION 1 25% $250.00 $187.50 $150.00 G335 ADD: ANT 1/4 WAVE 762-870 MHZ 1 25% $14.00 $10.50 $8.40 G831 ADD: SPKR 15W WATER RESISTANT 1 25% $60.00 $45.00 $36.00 G996 ENH: OVER THE AIR PROVISIONING 1 25% $100.00 $75.00 $60.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 GA01202AA ADD: APX GEOFENCE MOBILE 1 25% $150.00 $112.50 $0.00 GA01767 ADD: APX MOBILE RADIO AUTHENTICAT 1 25% $100.00 $75.00 $60.00 GA09008 ADD: GROUP SERVICES 1 25% $150.00 $112.50 $90.00 GA00226 ADD: GPS ANTENNA 1 25% $75.00 $56.25 $45.00 G298AS ENH: ASTRO 25 OTAR W/ MULTIKEY 1 25% $740.00 $555.00 $444.00 W969 ADD: MULTIPLE KEY ENCRYPTION OPERATION 1 25% $330.00 $247.50 $198.00 G851 ADD: AES/DES-XL/DES-OFB ENCRYPTION 1 25% $799.00 $599.25 $479.40 G843 ADD: AES ENCRYPTION APX 1 25% $475.00 $356.25 $0.00 G618 ADD: REMOTE MOUNT CBL 10 FEET 1 25% $10.00 $7.50 $6.00 G610 ADD: REMOTE MOUNT CBL 30 FEET 1 25% $25.00 $18.75 $15.00 GA879 ADD REMOTE MOUNT CBL 115 FEET 1 25% $55.00 $41.25 $33.00 G72 ADD: 03 HAND HELD CONTROL HEAD 1 25% $946.00 $709.50 $567.60 GA00805AA ADD: 07 CONTROL HEAD 1 25% $632.00 $474.00 $379.20 GA00245AA ADD: 09 CONTROL HEAD 1 25% $1,200.00 $900.00 $720.00 G24 ADD: 3 YEAR SERVICE FROM THE START 1 0% $131.00 $131.00 $131.00 GA00318 ADD: 5 YEAR SERVICE FROM THE START 1 0% $246.00 $246.00 $246.00 P25 System and Services Agreement (R1422515R1/P1) Page 58 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 PROFILE,STANDARD RADIO BUNDLE: MODEL• M30TSS9PW1 N P25, TDMA, INTEGRATED VOICE & DATA, GPS, PALM MIC, • •UNT 17FT CABLE, APX7500 DUAL BAND MID POWER, 05 CONTROL HEAD, DASH MOUNT 7.5 CITY WATT CONSOLETTESPOWER) 1 SPEAKER, • 25% ANTENNA $7,360.50 (7/800 3DB $5,520.38 LOW 0% D $4,416.30 M30TSS9PW1 N APX7500 DUAL BAND, MID POWER, 05 CONTROL HEAD, REMOTE MOUNT 1 25% $7,532.50 $5,649.38 $4,519.50 M30TXS9PW1 N APX7500 DUAL BAND, HIGH POWER 05, CONTROL HEAD, REMOTE MOUNT 1 25% $8,078.50 $6,058.88 $4,847.10 CONTROL STATION OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ G91 ADD: CONTROL STATION POWER SUPPLY 1 25% $269.00 $201.75 $161.40 W665 ADD: CONTROL STATION OPERATION 1 25% $70.00 $52.50 $42.00 W382 ADD: CONTROL STATION DESK GCAI MIC 1 25% $169.00 $126.75 $101.40 MULTIPLE CONTROL HEAD OPTIONS(not limited to): LIST $ 25% DISC $ 40% DISC $ GA00092 ADD: DUAL-CONTRL HD HARDWARE(must add additional mic, cables & speakers) 1 25% $570.00 $427.50 $342.00 GA00093 ADD: APX7500 TRI-CONTROL HARDWARE(must add additional mic,cables & speakers) 1 25% $1,000.00 $750.00 $600.00 GA00094 ADD: APX QUAD -CONTROL HARDWARE(must add additional mic, cables & speakers) 1 25% $1,300.00 $975.00 $780.00 CONSOLETTE RADIOS (no antenna, line or combiners in bundle, only radio and internal configurations): CITY DISC% LIST $ 25% DISC $ 40% DISC $ L30URS9PW1 N JAPX7500 SINGLE BAND CONSOLETTE 1 25%1 $7,548.00 $5,661.00 $2,732.40 LIMITED FRONT PANEL 1 25% $8,028.00 $6,021.00 $288.00 FULL FP W/05/KEYPAD 1 25% $8,337.00 $6,252.75 $473.40 L30TSS9PW1 N IAPX7500 CONSOLETTE DUAL BAND CONSOLETTE 1 25% $8,548.00 $6,411.00 $2,732.40 LIMITED FRONT PANEL 1 25% $9,028.00 $6,771.00 $288.00 FULL FP W/05/KEYPAD 1 25%1 $9,337.00 $7,002.75 $473.40 CONSOLETTE OPTIONS(not limited to): CITY DISC% LIST $ 25%DISC $ 40% DISC $ DSCOL54160 VHF OMNIMEANDER COLLINEAR DIRECTIONAL ANTENNA 1 8% $ 1,921.00 $1,767.32 $1,152.60 DSCOL4570 UHF OMNI COLLINEAR DIRECTIONAL ANTENNA 1 8% $ 912.00 $839.04 $547.20 DSANT790F2 7/800 OMNI COLLINEAR DIRECTIONAL TELEWAVE ANTENNA 1 8% $ 1,012.00 $931.04 $607.20 100 FT 112 SUPERFLEX CABLE AND CONNECTORS 1 8% $585.90 $539.03 $351.54 OPTIONS(not limited to): CITY DISC% LIST $ 25% DISC $ 40% DISC $ GA01767 APX MOBILE RADIO AUTHENTICATION 1 25% $100.00 $75.00 $60.00 GA00631 ADD: DVRS MSU ACTIVATION 1 25% $250.00 $187.50 $150.00 GA00805 ADD: APX 07 CONTROL HEAD. 1 25% $632.00 $474.00 $379.20 G174 ADD: ANT 3DB LOW -PROFILE 762-870 1 25% $43.00 $32.25 $25.80 W484 ALT: ANT 3DB GAIN 762-87OMHZ 1 25% $38.00 $28.50 $22.80 G296 ADD: 1/4 WAVE WHIP ROOF TOP 136-144 1 25% $13.50 $10.13 $8.10 G300 ADD:1/4 WAVE ROOF TOP ANT VHF 1 25% $13.50 $10.13 $8.10 G430 ADD: ANT 5.ODB 445-470 MHZ 1 25% $110.00 $82.50 $66.00 G426 ADD: ANT 1/4 WAVE WHIP 450-470 MHZ 1 25% $25.00 $18.75 $15.00 G510 ADD: ANT LOW PROFILE 450-512 MHZ 1 25% $50.00 $37.50 $30.00 W432 ADD: AUXILARY SPKR 13W (3.2OHM) 1 25% $71.50 $53.63 $42.90 G996 ENH: OVER THE AIR PROVISIONING 1 25% $100.00 $75.00 $60.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 GA01202 ADD: APX GEOFENCE MOBILE 1 25% $150.00 $112.50 $90.00 GA00226 ADD: GPS ANTENNA 1 25% $75.00 $56.25 $45.00 W969 ADD: MULTIPLE KEY ENCRYPTION OPERATION 1 25% $330.00 $247.50 $198.00 G298 ENH: ASTRO 25 OTAR W/ MULTIKEY 1 25% $740.00 $555.00 $444.00 G851 ADD: AES/DES-XL/DES-OFB ENCRYPTION 1 25% $799.00 $599.25 $479.40 G843 ADD: AES ENCRYPTION APX 1 25% $475.00 $356.25 $0.00 G609 ADD: REMOTE MOUNT CBL 50 FEET 1 25% $35.00 $26.25 $21.00 P25 System and Services Agreement (R1422515R1/P1) Page 59 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 G607 ADD:CBL REMOTE MOUNT 75 FEET 111 25% $45.00 1 $33.75 1 $27.00 G879 ADD:REMOTE MOUNT CBL 115 FEET 1 25% $55.00 $41.25 $33.00 G78 ADD: 3 YEAR SERVICE FROM THE START 1 0% $168.00 $168.00 $168.00 GA00318 ADD: 5 YEAR SERVICE FROM THE START 1 0% $319.00 $319.001 $319.00 P25 System and Services Agreement (R1422515R1/P1) Page 60 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 v�•�r.T.�,�,r.i•n•y�n•.ir.t.� IIIIIIIII III STANDARD RADIO BUNDLE: P25, TDIMA, INTEGRATED VOICE & DATA, GPS, LOW PROFILE,•MOUNT MODEL• APX8500 ALL BAND, MID POWER, 05 CONTROL M37TSS9PW1 N HEAD, DASH MOUNT MOBILE RADIO PALM • MIC, 1 7.5 WATT 25% - - , SPEAKER, 17FT $8,324.00 ANTENNA (7/800 CABLE) $6,243.00 3DB 40% DISC $4,994.40 DUAL BAND 1 25% $7,524.00 $5,643.00 $4,514.40 SINGLE BAND 1 25% $6,724.00 $5,043.00 $4,034.40 M37TSS9PW1 N JAPX8500 ALL BAND, MID POWER, 05 CONTROL, HEAD REMOTE MOUNT MOBILE RADIO 1 25% $8,496.00 $6,372.00 $5,097.60 DUAL BAND 1 25% $7,696.00 $5,772.00 $4,617.60 SINGLE BAND 1 25% $6,896.00 $5,172.00 $4,137.60 CONTROL STATION OPTIONS(not limited to): QTY DISC% LIST $ 25% DISC $ 40% DISC $ G91 ADD: CONTROL STATION POWER SUPPLY 1 25% $269.00 $201.75 $161.40 W665 ADD: CONTROL STATION OPERATION 1 25% $70.00 $52.50 $42.00 W382 ADD: CONTROL STATION DESK GCAI MIC 1 25% $169.00 $126.75 $101.40 MULTIPLE CONTROL HEAD OPTIONS(not limited to): QTY DISC% LIST $ 25% DISC $ 40% DISC $ GA00092 ADD: DUAL-CONTRL HD HARDWARE(must add additional mic, cables & speakers) 1 25% $570.00 $427.50 $342.00 GA00093 ADD: APX7500 TRI-CONTROL HARDWARE(must add additional mic,cables & speakers) 1 25% $1,000.00 $750.00 $600.00 GA00094 ADD: APX QUAD -CONTROL HARDWARE(must add additional mic, cables & speakers) 1 25% $1,300.00 $975.00 $780.00 OPTIONS(not limited to): QTY DISC% LIST $ 25% DISC $ 40% DISC $ GA01767 APX MOBILE RADIO AUTHENTICATION 1 25% $100.00 $75.00 $60.00 QA00631 ADD: DVRS PSU ACTIVATION 1 25% $100.00 $75.00 $60.00 GA00805 ADD: APX 07 CONTROL HEAD. 1 25% $632.00 $474.00 $379.20 W432 ADD: AUXILARY SPKR 13W (3.20HM) 1 25% $71.50 $53.63 $42.90 GA09001 ADD: WIFI 11 25% $300.00 $225.00 $180.00 G996 ENH: OVER THE AIR PROVISIONING 1 25% $100.00 $75.00 $60.00 QA03399 ADD: ENHANCED DATA 1 25% $150.00 $112.50 $90.00 GA09008 ADD: GROUP SERVICES 1 25% $150.00 $112.50 $90.00 GA00229 ENH: APX GPS ACTIVATION 1 25% $150.00 $112.50 $90.00 GA01202 ADD: APX GEOFENCE MOBILE 1 25% $150.00 $112.50 $90.00 W969 ADD: MULTIPLE KEY ENCRYPTION OPERATION 1 25% $330.00 $247.50 $198.00 G298 ENH: ASTRO 25 OTAR W/ MULTIKEY 1 25% $740.00 $555.00 $444.00 G851 ADD: AES/DES-XL/DES-OFB ENCRYPTION 1 25% $799.00 $599.25 $479.40 G843 ADD: AES ENCRYPTION APX 1 25% $475.00 $356.25 $0.00 G609 ADD: REMOTE MOUNT CBL 50 FEET 1 25% $35.00 $26.25 $21.00 G607 ADD:CBL REMOTE MOUNT 75 FEET 1 25% $45.00 $33.75 $27.00 G879 ADD:REMOTE MOUNT CBL 115 FEET 1 25% $55.00 $41.25 $33.00 G831 ADD: SPKR 15W WATER RESISTANT 1 25% $60.00 $45.00 $36.00 W432 ADD: AUXILARY SPKR 13W (3.20HM) 1 25% $71.50 $53.63 $42.90 G174 ADD: ANT 3DB LOW -PROFILE 762-870 1 25% $43.00 $118.50 $25.80 W484 ALT: ANT 3DB GAIN 762-87OMHZ 1 25% $38.00 $28.50 $22.80 G299 ADD: 1/4 WAVE ROOF TOP 150.8-162 1 25% $19.50 $14.63 $11.70 GA00506 ADD: ANT MCL 1/4 WAVE WHIP 425- 470 1 25% $50.00 $37.50 $30.00 GA00226 ADD: GPS WIN ANTENNA 1 25% $75.00 $56.25 $45.00 G78 ADD: 3 YEAR SERVICE FROM THE START LITE 1 0% $250.00 $250.00 $250.00 GA00318 ADD: 5 YEAR SERVICE FROM THE START LITE 1 0% $363.00 $363.00 $363.00 P25 System and Services Agreement (R1422515R1/P1) Page 61 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 ADDITIONAL EQUPMENT, ACCESSORIES AND PROGRAMMING EQUPMENT/SOFTWARE (NOT LIMITED TO) PORTABLE AND MOBILE ANTENNAS LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE NAF5085A APX 700/800 & GPS ANTENNA $45.00 23% $34.65 $31.95 ALL PORTABLE NAR6595A ANT 1/4 WAVE 7/800 STUBBY $29.00 23% $22.33 $20.59 ALL PORTABLE NAG4000 APX GPS STUBBY ANTENNA $18.00 23% $13.86 $12.78 ALL PORTABLE NAR6593A ANT,HLCL,136MHZ MIN,1.577GHZ M $38.00 23% $29.26 $26.98 6000, 7000, 8000 PMAE4065A UHF (380-520) GPS ANTENNA $21.00 23% $16.17 $14.91 6000, 7000, 8000 NAR6594A ANT VHF 7/800/GPS $75.00 23% $57.75 $53.25 6000, 7000, 8000 PMAS4001A UHF (380-520) /7-800 GPS 1 $31.00 1 23% $23.87 1 $22.01 17000,8000 KT000026A01 ANTENNA, ALL -BAND, 20CM 1 $108.00 1 23% $83.16 1 $76.68 18000 PORTABLE BATTERIES LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE NNTN8128BR BATT IMP STD LI ION 1900M $102.00 23% $78.54 $72.42 1000, 4000 PMNN4424AR BATT IMP LI ION 2300M $117.00 23% $90.09 $83.07 1000, 4000 PMNN4448AR BATT IMP STD IP67 LIION 2700MAH $127.00 23% $97.79 $90.17 1000, 4000 NNTN8560A BATT IMPRES LIION TIA4950 UL IP67 2500T $155.00 23% $119.35 $110.05 1000, 4000 NNTN8930 BATTERY PACK,LITHIUM ION,APX TIA4950 STD BATTERY $155.00 23% $119.35 $110.05 6000, 7000 NNTN8921 BATT IMPRES 2 LIION TIA4950 UL IP68 4500MAH $177.00 23% $136.29 $125.67 6000, 7000 PMNN4485 BATT IMPRES 2 LIION R IP68 2550T $127.00 23% $97.79 $90.17 6000, 7000, 8000 PMMNN4486 BATT IMPRES 2 LIION R IP68 3400T $142.00 23% $109.34 $100.82 6000, 7000, 8000 PMNN4494 BATT IMPRES 2 LIION R IP68 5100T $172.00 23% $132.44 $122.12 6000, 7000, 8000 PMMNN4487 BATT IMPRES 2 LIION R IP68 4850T $162.00 23% $124.74 $115.02 6000, 7000, 8000 NNTN7035 BATT IMP FM R NIMH 2O00M 2200T BLK $149.00 23% $114.73 $105.79 6000, 7000, 8000 NNTN8092 BATT IMP FM R LI ION 2300M 2350T BLK $142.00 23% $109.34 $100.82 6000, 7000, 8000 PMNN4504 BATT IMPRES LIION UL2054 DIV2 IP68 3400MAH $150.00 23% $115.50 $106.50 8000XE ONLY PMNN4505 ALT: LIION IMPRES TIA4950 UL DELTA-T $179.00 23% $137.83 $127.09 8000XE ONLY PORTABLE BATTERY CHARGERS LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE PMPN4174A SINGLE -UNIT IMPRES CHARGER $69.25 23% $53.32 $49.17 1000, 4000 NNTN8525A TRAVEL CHARGER $95.00 23% $73.15 $67.45 1000, 4000 WPLN4219B IMPRES MULIT-UNIT CHARGER W/DISPLAY $715.00 23% $550.55 $507.65 1000, 4000 NNTN7586 APX DUAL UNIT CHARGER WITHOUT DISPLAY $295.00 23% $227.15 $209.45 6000, 7000, 8000 NNTN8844A CHARGER, MULTI -UNIT, IMPRES 2, 6-DISP, NA/LA- PLUG, ACC USB CHGR $1,250.00 23% $962.50 $887.50 6000, 7000, 8000 RLN6434A 1AP7, TRAVEL CHARGER $111.00 23% $85.47 $78.81 6000, 7000, 8000 NNTN8860A CHARGER, SINGLE -UNIT, IMPRES 2, 3A, 115VAC, US/NA $150.00 1 23% $115.50 $106.50 6000, 7000, 8000 P25 System and Services Agreement (R1422515R1/P1) Page 62 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 PORTABLE REMOTE SPEAKER MICROPHONES LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE IMPRES RSM DSPLY W JACK, HMN4104B W CHNL $413.00 23% $318.01 $293.23 ALL PORTABLE APX IMPRES RSM, NOISE CANC. EMERGENCY BUTTON PMMN4062A 3.5MM JACK IP54 $118.00 23% $90.86 $83.78 ALL PORTABLE PMMN4065A APX IMPRES RSM W/VOL, IP57 $107.00 23% $82.39 $75.97 ALL PORTABLE IMPRES RSM, 3.5MM AUDIO PMMN4069A JACK $121.00 23% $93.17 $85.91 ALL PORTABLE PMMN4083A IMPRES RSM DELTA-T, $125.00 23% $96.25 $88.75 ALL PORTABLE PLUS RSM NC IP54 THRD PMMN4084A 3.5MM JACK RX $95.00 23% $73.15 $67.45 ALL PORTABLE AUDIO ACCESSORY -REMOTE SPEAKER MICROPHONE,IMPRES PMMN4099A WINDPORTING RSM, IP55 $132.00 23% $101.64 $93.72 ALL PORTABLE AUDIO ACCESSORY -REMOTE SPEAKER MICROPHONE,IMPRES XE RSM NNTN8575A XT CABLE BLK, YLW, GRN $480.00 23% $369.60 $340.80 ALL PORTABLE IMPRES XP RSM FOR APX W/ DUAL MIC NOISE NMN6271A SUPPRESSION $325.00 23% $250.25 $230.75 ALL PORTABLE IMPRES XP RSM FOR APX W/ DUAL MIC NOISE SUPPRESSION, 3.5MM NMN6274A THRDJACK $369.00 23% $284.13 $261.99 ALL PORTABLE MPRES XE500 RSM GRN, PMMN4106A PLW,BLK $550.00 23% $423.50 $390.50 ALL PORTABLE PORTABLE PUBLIC SAFETY MICROPHONES LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE PSM IP55 WITH 3.5MM JACK PMMN4059B RX 181N $164.00 23% $126.28 $116.44 ALL PORTABLE PSM IP55 WITH 3.5MM JACK PMMN4060B RX 241N $180.40 23% $138.91 $128.08 ALL PORTABLE PSM IP55 WITH 3.5MM JACK PMMN4061 B RX 301N $164.00 23% $126.28 $116.44 ALL PORTABLE APX PSM 700/80OMHZ PMAF4002 ANTENNA $12.00 23% $9.24 $8.52 ALL PORTABLE PORTABLE AND MOBILE BLUETOOTH LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE ASSEMBLY ACCESSORY WIRELESS ACCY KIT NFP 12 NTN2570C CABLE $325.00 23% $250.25 $230.75 ALL PORTABLE ACCESSORY KIT,APX WIRELESS RSM W/ DUC RLN6554A US/NA/JP/TW $300.00 23% $231.00 $213.00 ALL PORTABLE MISSION CRITICAL WIRELESS RLN6544A RSM W/ BATTERY AND CLIP $250.00 23% $192.50 $177.50 ALL PORTABLE MOBILE MICROPHONE WITH PMMN4097C �BLUETOOTH GATEWAY $215.00 23% $165.55 $152.65 MOBILE ONLY PORTABLE HEADSETS/ETC LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE 1-WIRE EARBUD,116CM NNTN8295A CORD,BLACK $40.00 23% $30.80 $28.40 ALL PORTABLE 2-WIRE EARBUD,116CM NNTN8298A CORD,BLACK $49.95 23% $38.46 $35.46 ALL PORTABLE PMLN5653A BONE CONDUCTION EAR MIC $399.00 23% $307.23 $283.29 ALL PORTABLE IMPRES 2 WIRE PMLN6127A SURVEILLANCE -BLK $105.00 23% $80.85 $74.55 ALL PORTABLE P25 System and Services Agreement (R1422515R1/P1) Page 63 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 PMLN6123A IMPRES 3 WIRE W/ TRANS �TUBE-BLK $173.00 23% $133.21 $122.83 ALL PORTABLE PORTABLE HOLSTERS LIST $ DISC % 23% DISC $ 29% DISC $ RADIO TYPE PMLN7182A APX TWO - KNOB, SWIVEL, LEATHER CARRY CASE $60.00 23% $46.20 $42.60 1000, 4000 PMLN4651A BELT CLIP 2" $11.00 23% $8.47 $7.81 1000, 4000 PMLN5657B APX6000 CC 2.75 SWLBL 2900&2150MAH $71.50 23% $55.06 $50.77 6000, 8000 PMLN5659B APX6000 CC 2.75 SWL BL 4200MAH $67.00 23% $51.59 $47.57 6000, 8000 PMLN5875 APX6000XE 2.75SWBL2900,2300&2150MAH $65.00 23% $50.05 $46.15 6000XE, 8000XE PMLN5876A APX6000XE 3 FIXBL 2900,2300&2150MAH $62.00 23% $47.74 $44.02 6000XE, 8000XE PMLN5877A APX6000XE CC 2.75 SWL BL 4200MAH $65.00 23% $50.05 $46.15 6000XE, 8000XE PMLN5324C LEATHER CASE 2.75 SWL BL 2500MAH $65.00 23% $50.05 $46.15 7000 PMLN5327C LEATHER CASE 2.75 SWL BL 4200MAH $67.00 23% $51.59 $47.57 7000 NNTN8111 B APX7000XE CC 2.75 SWLBL2900/2150MAH $65.00 23% $50.05 $46.15 7000XE NNTN8113A APX7000XE CC 2.75 SWL BL 4100MAH $65.00 23% $50.05 $46.15 7000XE RLN6486A ACCESSORY KIT,FIREMAN'S RADIO STRAP $37.00 23% $28.49 $26.27 ALL PORTABLE RLN6487A ACCESSORY KIT,FIREMAN'S RADIO STRAP, XL $28.50 23% $21.95 $20.24 ALL PORTABLE RLN6488A ACCESSORY KIT,ANTI-SWAY STRAP $15.00 23% $11.55 $10.65 ALL PORTABLE KVL 4000 KEYLOADER LIST $ DISC % 8% DISC $ 10% DISC $ RADIO TYPE T7537B KVL 4000 PDA SNAP -ON $1,250.00 8% $1,150.00 $1,125.00 ALL APX RADIOS U239AD ADD: ASTRO 25 MODE $250.00 8% $230.00 $225.00 ALL APX RADIOS CA01598AA ADD: AC LINE CORD US $11.00 8% $10.12 $9.90 ALL APX RADIOS CA00182AP ADD: AES ENCRYPTION SOFTWARE $750.00 8% $690.00 $675.00 ALL APX RADIOS C543 ADD: CABLE FOR RNC, DIU, MGEG $84.00 8% $77.28 $75.60 ALL APX RADIOS C725AA ADD: KEYLOAD CABLE FOR APX PORTABLE $75.00 8% $69.00 $67.50 ALL APX RADIOS CA02187 ADD: KEYLOADING CABLE ADAPTER (GCAI) $41.50 8% $38.18 $37.35 ALL APX RADIOS TOTAL: $2,461.50 $2,264.58 $2,215.35 OPTIONS(not limited to): LIST $ DISC % 8% DISC $ 10% DISC $ RADIO TYPE QA01767AA ADD: KVL RADIO AUTHENTICATION $500.00 8% $460.00 $450.00 ALL APX RADIOS X795AJ ADD: ASN MODE $600.00 8% $552.00 $540.00 ALL APX RADIOS X423AF ADD: DES/DES-XL/DES-OFB ENCRYPTION $1,550.00 8% $1,426.00 $1,395.00 ALL APX RADIOS CA02186 ADD: KEYLOAD CABLE FOR CRYPTR MICRO $190.00 8% $174.80 $171.00 ALL APX RADIOS DSMT9234MUCDC USE; MODEM BY MULTITECH - REQUIRED FOR KVL-KMF COMMUNICATION REMOTELY $250.00 20% $230.00 $225.00 ALL APX RADIOS DSPSA1U1EE RUGGED USB CLIENT TO ETHERNET ADAPTER WITH USE; CABLE BUILT IN. $226.00 20% $207.92 $203.40 ALL APX RADIOS Antenna, Line & Combiners (not limited to): LIST $ DISC % 8% DISC $ 10% DISC $ IRADIO TYPE P25 System and Services Agreement (R1422515R1/P1) Page 64 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 DSCOL54160 VHF OMNIMEANDER COLLINEAR DIRECTIONAL ANTENNA $1,921.00 8% $1,767.32 $1,728.90 ALL MOBILE DSCOL4570 UHF OMNI COLLINEAR DIRECTIONAL ANTENNA $912.00 8% $839.04 $820.80 ALL MOBILE DSANT7901`2 7/800 OMNI COLLINEAR DIRECTIONAL TELEWAVE ANTENNA $1,012.00 8% $931.04 $910.80 ALL MOBILE SURGE SUPRESSOR, GROUND KITS AND $826.00 8% $759.92 $743.40 ALL MOBILE RF SURGE SUPRESSOR, GROUND KITS AND $791.00 8% $727.72 $711.90 ALL MOBILE DSCSO496040531 4 PORT COMBINER $2,159.00 8% $1,986.28 $1,943.10 ALL MOBILE DSCSO496080531 8 PORT COMBINER $2,421.00 8% $2,227.32 $2,178.90 ALL MOBILE DSCSO496160531 12 PORT COMBINER $5,426.00 8% $4,991.92 $4,883.40 JALL MOBILE DSCSO496240531 16 PORT COMBINER $8,427.00 1 8% $7,752.84 $7,584.30 JALL MOBILE DSCSO496320531 32 PORT COMBINER $10,796.00 1 8% $9,932.32 $9,716.40 JALL MOBILE P25 System and Services Agreement (R1422515R1/P1) Page 65 of 65 Exhibit A-4 (Subscriber Equipment) DocuSign Envelope ID: D58746D1-9A8A-44B8-8B7C-555C1CC2A771 SOW A-5 Optional Services County or any of the Eligible Subscribers may acquire any of the goods or services described herein, which shall be acquired by an appropriate purchasing document and statement of work in accordance with the terms of the Agreement. 1. P25 Radio Authentication This functionality provides System security authentication process for radio subscribers. 2. Over the Air Off -Frequency Radio Identification An anticipated future service offering from Motorola to provide functionality for push -to -talk users to identify out of tune or off -specification radios. 3. Additional Goods and Services In addition to the foregoing, County may acquire as Optional Services any other goods and services reasonably related to the maintenance, operation, or configuration of the Radio System, Microwave System, Civil and Infrastructure Services, or the P25 System that Provider makes available to its customers. Any such election shall be documented through an appropriate Work Authorization negotiated and executed by the Parties, subject to the terms and conditions of the Agreement. P25 System and Services Agreement (R1422515R1/P1) Page 1 of 1 SOW A-5 (Optional Services)