The URL can be used to link to this page

Home My WebLink AboutR-2026-014 Authorizing Purchase and Installation of CommandCentral AXS Dispatch Console Equipment from Motorola Solutions Inc.RESOLUTION NO. 2026-014 A RESOLUTION AUTHORIZING THE PURCHASE AND INSTALLATION OF COMMANDCENTRAL AXS DISPATCH CONSOLE EQUIPMENT FROM MOTOROLA SOLUTIONS, INC. BE IT RESOLVED BY THE BOARD OF ALDERMEN OF THE CITY OF RIVERSIDE, MISSOURI, AS FOLLOWS: THAT the Board of Aldermen hereby approves and authorizes the purchase of CommandCentral AXS Dispatch Console equipment and related services for the Riverside Police Departmentfrom Motorola Solutions, Inc., in substantial accordance with the Motorola proposal dated November 18, 2025, at a total cost not to exceed $302,204.00; and FURTHER THAT the Mayor is hereby authorized to execute, on behalf of the City, the Motorola Solutions proposal, state contract documents, purchase orders, statements of work, and any related agreements or amendments necessary to complete the Project, provided that such documents are consistent with this Resolution, the Missouri State Contract No. MT250038001, and are approved as to form by the City Attorney; and FURTHER THAT pursuant to City Code Section 135.080. D, the Board of Aldermen hereby finds and determines that it is in the best interest of the City to enter into the purchase authorized by this Resolution, and hereby approves proceeding without the bidding procedures otherwise required by the City Code; and FURTHER THAT the Mayor, the City Administrator, and other appropriate City officials are hereby authorized to take any and all actions as may be deemed necessary or convenient to carry out and comply with the intent of this Resolution and to execute and deliver for and on behalf of the City all certificates, instruments, agreements, and other documents, as may be necessary or convenient to perform all matters herein authorized. PASSED AND ADOPTED by the Board of Aldermen of the City of Riverside, Missouri, the 27th day of January 2026. Kathleen L. Rose, Mayor ATTEST: Melissa McChesney, City Clerk Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted RIVERSIDE PD AXS CONSOLE UPGRADE RIVERSIDE PD NOVEMBER, 2025 TABLE OF CONTENTS Section 1 System Description ..........................................................................................................................1-1 1.1 Solution Overview ............................................................................................................. 1-1 1.2 AXS Overview ...................................................................................................................1-1 1.2.1 Making Consoles Easy to Operate ................................................................................1-2 1.2.1.1 Next Generation Dispatch Experience .................................................................. 1-2 1.2.1.2 Cross Platform Dispatch Capabilities .................................................................... 1-3 1.2.1.3 Headset Sharing .................................................................................................. 1-4 1.2.1.4 Standard Radio Transmission and Reception ....................................................... 1-4 1.2.1.5 Emergency Radio Transmission and Reception ................................................... 1-5 1.2.1.6 Radio Patch Control ............................................................................................. 1-6 1.2.1.7 Call Management and Control .............................................................................. 1-6 1.2.1.8 Enhanced Integrated Install Recall Recorder (IRR)............................................... 1-7 1.2.2 Protecting Consoles and Communications ....................................................................1-7 1.2.2.1 Secure Access to the Console .............................................................................. 1-7 1.2.2.2 Secure Communications at the Console ............................................................... 1-7 1.2.2.3 Secure Communications at the Logging Recorder ................................................ 1-8 1.2.2.4 Key Management via Key Variable Loader (KVL) ................................................. 1-8 1.2.2.5 Key Management via Key Over-the-Ethernet Keying (OTEK) ............................... 1-8 1.2.3 Incorporating Console Configuration and Management .................................................1-8 1.2.4 Dispatch Console Solution Components........................................................................ 1-8 1.2.4.1 CommandCentral AXS Dispatch Console Operator Position ................................. 1-9 1.3 Assumptions ................................................................................................................... 1-11 Section 2 Statement of Work............................................................................................................................. 12 2.1 Overview ............................................................................................................................ 12 2.2 Acceptance Test Plan ........................................................................................................ 17 2.3 Cutover Plan ...................................................................................................................... 17 2.4 Schedule............................................................................................................................ 17 Section 3 Managed Detection and Response (MDR) ........................................................................................ 18 3.1 Solution Overview .............................................................................................................. 18 3.1.1 Site Information .............................................................................................................. 18 3.1.2 Managed Detection and Response Elements ................................................................. 19 3.1.2.1 ActiveEye Security Platform ................................................................................ 19 3.1.2.2 ActiveEye Managed Security Portal ....................................................................... 19 3.1.2.3 Dashboard ............................................................................................................ 20 3.1.2.4 Security Cases ...................................................................................................... 20 3.1.2.5 Alert Details and Trends ...................................................................................... 20 3.1.2.6 Investigations and Reporting .............................................................................. 20 3.1.2.7 Security Advisories .............................................................................................. 21 3.1.2.8 Information Sharing ............................................................................................. 21 3.1.2.9 User Access ......................................................................................................... 21 Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Section 4 MDR Statement of Work ................................................................................................................... 22 4.1 Overview ........................................................................................................................... 22 4.2 Description of Service ....................................................................................................... 22 4.2.1 Deployment Timeline and Milestones .............................................................................22 4.2.2 General Responsibilities ................................................................................................ 23 4.2.2.1 Motorola Solutions Responsibilities ....................................................................... 23 4.2.2.2 Customer Responsibilities ..................................................................................... 23 4.3 Security Operations Center Monitoring and Support ......................................................... 24 4.3.1 Scope ........................................................................................................................... 24 4.3.2 Ongoing Security Operations Center Service Responsibilities ....................................... 24 4.3.3 Technical Support ..........................................................................................................25 4.3.4 Incident Response ........................................................................................................ 25 4.3.5 Event Response and Notification................................................................................... 26 4.3.6 Priority Level Definitions and Notification Times ............................................................ 27 4.4 Limitations and Exclusion .................................................................................................. 28 4.4.1 Service Limitations ......................................................................................................... 29 4.4.2 Processing of Customer Data in the United States and/or other Locations .................... 29 4.4.3 Customer and Third-Party Information ........................................................................... 29 4.4.4 Third-Party Software and Service Providers, including Resale ...................................... 30 Section 5 Advanced Plus Services ................................................................................................................... 31 5.1 Overview ........................................................................................................................... 31 5.2 Advanced Plus Services Element Descriptions ................................................................. 31 5.2.1 ASTRO System Monitoring ........................................................................................... 31 5.2.2 Remote Technical Support ............................................................................................ 32 5.2.3 Network Hardware Repair .............................................................................................. 32 5.2.4 Network Hardware Repair with Advanced Replacement ................................................ 32 5.2.5 Remote Security Update Service .................................................................................. 32 5.2.6 On-site Infrastructure Response .................................................................................... 33 5.2.7 Annual Preventive Maintenance .................................................................................... 33 5.3 Motorola Solutions Service Delivery Ecosystem ................................................................ 33 5.3.1 Centralized Managed Support Operations ..................................................................... 33 5.3.2 Field Service ................................................................................................................. 34 5.3.3 Repair Depot ..................................................................................................................34 5.3.4 Customer Support Manager ...........................................................................................34 5.3.5 Customer Hub ................................................................................................................34 Section 6 Pricing Summary .............................................................................................................................. 36 Section 7 Contractual Documentation ............................................................................................................. 7-1 Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Motorola Solutions, Inc. Schaumburg, IL 60196 USA 1303 E. Algonquin Rd. Tel. + 1 847 576 5000 Fax + 1 847 538 6020 November 18, 2025 Chief Skinrood Riverside Police Department 2990 NW Vivion Road Riverside, MO 64150 Re: AXS Console Add On Motorola Solutions, Inc. (“Motorola Solutions”) is pleased to provide the following firm proposal for the City of Riverside, MO to add QTY 3 AXS Dispatch Console equipment and services. As the leading provider of mission critical public safety communications in the State of Missouri and throughout the United States, Motorola Solutions understands the daily operations and challenges that first responders face. This proposal is subject to the terms and conditions included in the Missouri State Contract #MT250038001. The pricing will remain valid for 45 days from the date of the cover letter. We thank you for the opportunity to present our proposed solution, and we hope to strengthen our relationship and partnership with the Riverside Police Department by implementing this project. Questions or inquiries may be addressed to your Area Sales Manager, Mike Skalitzky, at 312-590-1496 and michael.skalitzky@motorolasolutions.com. Sincerely, Mike Skalitzky Area Sales Manager Motorola Solutions Inc. Phone: 312-590-1496 Email: michael.skalitzky@motorolasolutions.com Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted SECTION 1 SYSTEM DESCRIPTION 1.1 SOLUTION OVERVIEW Motorola Solutions, Inc. (Motorola) is pleased to propose an upgrade from the existing MCC7500 consoles to the new Command Central AXS dispatch consoles. This will meet Riverside Disptach’s existing and future mission-critical communication needs. The solution is based on leveraging the existing MARRS ASTRO system. The following equipment is proposed for Riverside’s dispatch center. Two existing dispatch positions will be replaced by the new AXS platform, and one new AXS position will be added. The proposed dispatch solutions includes the following major components: • Three (3) CommandCentral AXS Console Operator Positions which each include the following: o CCHUB with internal PC o Encryption capabilities for AES, DES_OFB and ADP o 3 Speakers o 1 Microphone o 1 footswitch o 2 headset jacks • One (1) DSC8000 Site Controller (Optional) • One (1) new 24” touch screen computer display for the new position (Existing two monitors will be used for the two replacement AXS consoles) 1.2 AXS OVERVIEW Motorola Solutions, Inc.’s (Motorola) CommandCentral AXS Dispatch Console reduces the barriers between systems in Riverside’s dispatch center, allowing access to all the mission- critical tools and applications dispatchers need in the moments that matter. This makes operation more efficient in emergency situations. Resources are accessible with an intuitive, highly configurable browser-based GUI. Dispatchers will have an expansive feature set and a mission-critical IP network for transporting information and calls throughout the system. CommandCentral AXS improves the efficiency and operation of dispatchers in the following ways (additional fees may apply depending upon feature and hardware additions): • Next Generation Dispatch Experience – The solution responds to touch, type or click, giving dispatchers the flexibility to interact and stay connected to teams in the way that best suits them. Extensive configuration options, flexible deployment configurations and simple scalability means agencies only pay for what is needed now, with the room to adapt and grow as needs change over time. • Purpose-Built Dispatch Console Accessories – Enhances the dispatch experience with accessories, such as gooseneck microphone, speakers, headset jack, and footswitch, designed and tested for industry-leading performance and reliability. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted This solution also reduces operating costs and provides a smaller physical footprint in the command center without compromising on features or reliability. This combination of seamless communications, modern architecture, and advanced integration capabilities enables the CommandCentral AXS solution to scale and evolve as needs change over time. 1.2.1 Making Consoles Easy to Operate Motorola’s proposed consoles are optimized for real-time audio, prioritizing emergency calls over other traffic, and minimizing voice queuing. Using robust error mitigation to maintain call quality even when the system is heavily loaded, the proposed console reduces communication errors that may force dispatchers or radio users to repeat their transmissions. 1.2.1.1 Next Generation Dispatch Experience CommandCentral AXS features a highly configurable graphical user interface (GUI) that provides quick, single-view access to important information and functionalities. The browser- based GUI’s versatile folders, tabs, and scalable resources allow users to organize and configure their dispatch experience and make engagement more familiar and intuitive from shift to shift. Folders and tabs can be relocated, exposed, or overlapped as needed, giving dispatchers more control of what information they see and how they interact with those resources. CommandCentral AXS also offers multiple options for routing audio to speakers and controlling volume levels. Figure 1: Next Generation Dispatch Experience CommandCentral AXS features flexible window positioning and capabilities for quick and efficient access to services such as: Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted • Activity Log – Provides an efficient point of reference for all incoming calls into a dispatch console, showing dispatchers detailed, searchable call information (radio resource name and call time) to enable faster and more informed response. • Paging – Allows users to send user configured pages on radio resources. This flexible paging feature is integrated with CommandCentral AXS for both conventional and trunked radio resources, while an external paging encoder port on the CommandCentral Hub enables third-party paging encoders to send pages on the selected radio resources. • Patch Capabilities – Enables dispatchers to set up a communication path between two or more resources that are normally unable to communicate with each other, such as trunked resources and conventional resources. • Alert Tones – Allows dispatchers to send one of fifteen user-configurable alert tones on selected radio resources. Fifteen defaults .wav files are provided with the dispatch console software, but any combination of these default files may be replaced with user configured.wav files to meet specific needs. • Channel Marker – Enables dispatchers to send a periodically repeating piece of audio on radio resources to meet the specific needs. 1.2.1.2 Cross Platform Dispatch Capabilities This solution is designed to take full advantage of Motorola’s end-to-end software suite, CommandCentral. These cross-platform integrations enhance the dispatch capabilities of CommandCentral AXS. Figure 2: Motorola’s End-to-End Portfolio CommandCentral AXS is an integral part of our end-to-end portfolio, providing greater interoperability and support for Riverside Dispatch’s current and future investments. As needs grow and change over time, this solution’s flexible integration capabilities evolve to satisfy Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted new demands. This adaptability also enables dispatchers to be effective with the integrations and capabilities they need. 1.2.1.3 Headset Sharing CommandCentral AXS supports Headset Sharing, which enables a dispatcher to use a common headset for both radio and 911 communications and to quickly access basic 911 call taking functionality from CommandCentral AXS. This improves the dispatcher’s efficiency and accuracy when they have to concentrate on the radio dispatch GUI while handling 911 calls. 1.2.1.4 Standard Radio Transmission and Reception A typical proposed dispatch position has a headset and two speakers. One speaker is for selected audio and the second speaker is for all remaining unselected audio. Additional speakers can be added to a console allowing dispatchers to configure a specific speaker for a set of designated audio sources. This simplifies multitasking between multiple audio sources and allows flexibility in the way the audio is presented to the dispatcher. Receiving Calls from the Field and Other Dispatchers The proposed console provides dispatchers with greater flexibility for how to hear calls from field radio users and other dispatchers. Each dispatcher can define his or her own audio reception profile by selecting a single audio source, whether conventional or talkgroup, to be heard on a selected speaker or headset (Single Select). The dispatcher can also define groups of radio resources that can all be heard on a selected speaker or headset (Multi- Select). Initiating Calls to the Field and Other Dispatchers The dispatcher has several different ways of initiating a call. In most circumstances, a General Transmit is appropriate. With the General Transmit, the dispatcher selects a resource on the console and activates the transmission through a footswitch, headset transmit button, or a microphone transmit button. If the dispatcher needs to quickly transmit on a resource that is not selected, the dispatcher uses the Instant Transmit function. A safety switch is available, which prevents accidental activation of functions that may cause negative consequences. The safety switch can be used with Aux I/Os and preprogrammed pages, as well as Instant Transmit switches. Audio Communication to the Field and Other Dispatchers The dispatcher can transmit audio in different ways. They can make calls to all users listening to a specific conventional radio resource or a specific trunking talkgroup. When multiple resources are required, the dispatcher can select additional talkgroups and/or conventional channels, as needed using the Multi-Select feature. The proposed console also enables dispatchers to make private calls to individual field radio users or dispatchers. Once a private call is established, it can be patched in with another resource at the dispatcher’s discretion. Controlling Console Audio The proposed console offers dispatchers several different ways of controlling or muting the audio on their consoles, such as the following: Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted • Audio volume can be changed for any specific resource. • All non-selected resources on the console can be muted for 30 seconds (All Mute) or unmuted, if already muted. • A dispatcher can transmit on a resource while receiving audio from the same resource or other resources. • A dispatch position can be configured to automatically mute the other dispatch audio on a shared resource to prevent acoustic feedback when a co-located dispatch position transmits. • RF Cross Mute automatically mutes the receive audio from a specified channel when the dispatcher transmits on another specified channel to prevent acoustic feedback. Controlling Network Audio Dispatchers can control audio on the ASTRO® 25 network. The dispatcher can enable or disable radio users to compartmentalize traffic, reduce interruptions, and maintain communications between dispatch and the field. When this function 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 position. 1.2.1.5 Emergency Radio Transmission and Reception As part of a mission-critical communications network, the proposed dispatch console facilitates immediate prioritization and resolution of emergency communications between Riverside’s dispatch and first responders in the field. This enables dispatchers and first responders to focus on their mission and not their equipment, especially during critical situations. Receiving an Emergency Call When a user in the field or another dispatcher initiates an emergency call, the console emits both visual and audible indications (Emergency Alarm). The audible indication alerts the dispatcher that an emergency is underway; the visual indication directs the dispatcher’s attention to the specific resource making the emergency call. The dispatcher can immediately reserve a voice channel for the duration of the emergency. Responding to an Emergency Call A dispatcher can bypass the standard console interface to auto-open a quick list, which contains specific controls for recognizing an emergency call, initiating an emergency call, and ending an emergency call (Auto-Open of Quick List). The dispatcher can then recognize the emergency call, which ends the audible emergency indication and notifies all dispatchers that the emergency is being addressed (Emergency Recognize). The audible emergency indication may also be muted by a dispatcher without recognizing the emergency alarm (Mute Tones at a Single Op). This can be used in a situation where one agency is monitoring a channel that belongs to another agency. That channel can be configured to not generate audible and/or visual emergency indications. Ending an Emergency Call When an emergency is over, the dispatcher can end the Emergency Alarm. The visual indication on the dispatch position GUI is removed, and the console informs the other dispatch Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted positions that the emergency is over (Emergency End/ Knockdown). The emergency mode remains active on the initiating radio unit until it is ended (reset) by the radio user. 1.2.1.6 Radio Patch Control The dispatcher can patch communication between trunked and/or conventional radios that are normally unable to communicate with each other due to different features, programming, or even different frequency bands. A patch group is a group of linked resources that can both receive messages from a console and transmit to all other members of the patch group. Setting up a Standard Patch Patches are supported between trunked resources and/or conventional resources. After the patch is created, the dispatch position transmits all audio on one resource to all other resources in the patch group. In a patch between trunked resources, patched radio users with displays see the ID or alias of the other patched radio(s), as opposed to that of the console. This minimizes confusion and the need for the dispatcher to intervene in the call. Patches are automatically reestablished, if interrupted, so the dispatcher can concentrate on continuing operations. Predefined Patches Patches can be predefined and automatically reinitiated each time a dispatch position computer is restarted (Patch Auto-Start). 1.2.1.7 Call Management and Control The dispatcher can use the following functionality to manage and control audio for different types of calls between the dispatch position and radio users or other dispatchers. Automatic Prioritization of Calls Calls on the dispatch position are prioritized through a transmission hierarchy. Calls from primary supervisors take priority over those from secondary supervisors, which in turn take priority over non-supervisors. Instant Transmit or All-Points Bulletin (APB) transmissions, regardless of whether they are from a supervisor, take priority over general or patch transmissions. Multiple dispatchers can be designated as primary supervisors on the same system, which is useful when multiple agencies share one system. With the Network Manager Client installed, supervisors can disable and enable dispatch console functionality as needed. Manual Prioritization of Calls System Access Priority Select allows a dispatcher to prioritize trunked resources on the system as either normal or tactical. A dispatcher can change the priority of a trunked resource to tactical to give the resource a better chance of gaining communication access on a busy system. Only emergency calls have a higher priority than tactical. When the System Access Priority Select status of a resource is changed, it is updated at all dispatch consoles in the systems that are monitoring that trunked resource. Using the Multi-Select Feature The Multi-Select feature allows a dispatch position to define groups of selected radio resources. When a Multi-Select group is opened, all of the resources in the group are Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted simultaneously selected. Resources can be added or removed from a Multi-Select group while the group is open. The dispatcher can transmit on several resources simultaneously or can listen to multiple resources simultaneously in their headset or select speakers. Standard Call Indications The dispatch position indicates the availability of any given resource, regardless of whether the resource is involved in a transmission. An inbound call indication provides the dispatcher with a visual cue of audio activity on a radio resource and allows a dispatcher to see at a glance what the status of a resource is at any moment. Call Alerting A dispatcher can use Call Alert to page an unattended radio or dispatch position through a series of beeps and an indication of the sender’s ID. When available, the radio user or dispatcher sees the unit ID of the calling dispatch console or radio ID and is able to return the call. Additionally, a Call Alert can trigger an activity. For instance, a Call Alert may cause a vehicle’s horn to sound and its lights to flash. The dispatcher can even send a Call Alert to a user who is involved in voice and data communications over the network. 1.2.1.8 Enhanced Integrated Install Recall Recorder (IRR) The Enhanced IRR is seamlessly integrated with the dispatch position’s software, allowing audio and call data from any radio or telephony resource to be recorded and easily played back. Call data includes PTT IDs, name of resource, start time and date, and stop time and date. Two analog inputs are available for use with recording audio from external devices. 1.2.2 Protecting Consoles and Communications The console enables end-to-end encryption from the dispatcher to the ASTRO® 25 network, so that Riverside Dispatch’s communications will not be undermined by unencrypted transmissions. Each dispatcher is able to fully participate in secure communications while being confident that sensitive, vital information is not heard by unauthorized individuals. 1.2.2.1 Secure Access to the Console To use the dispatch position, a dispatcher must enter a valid radio system user account name and password. The dispatch position validates that information with the radio system’s network manager and allows the dispatcher 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. 1.2.2.2 Secure Communications at the Console The console encrypts and decrypts radio voice messages. Thus, radio voice messages are encrypted from end-to- end between the radio user to the dispatch position. The dispatcher can choose whether to encrypt their transmissions on a particular trunked resource. Dispatchers can interface with agencies that have different encryption configurations without any manual intervention or delay. The AXS Console supports multiple encryption algorithms (AES, DES-OFB, and/or ADP) and multiple secure keys. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted The dispatchers may talk and listen on radio resources which have different encryption algorithms without any manual intervention or delay. The key material for performing audio encryption and decryption is stored locally on the console. This key material is also associated with a Common Key Reference (CKR), so that the appropriate key can be selected for a given talkgroup or a special call type. 1.2.2.3 Secure Communications at the Logging Recorder Not only are real-time communications encrypted, encryption extends to call logging to ensure that even recorded communications are not vulnerable to retrieval by unauthorized people. The AIS can support different encryption algorithms simultaneously. Like the dispatch console, the AIS also requires a valid radio system user account name and password be entered and validated by the radio system’s network manager before it allows access to recorded information. A user can access only the recordings for which the user has access rights. This enables agencies to keep their logs private from other agencies on the same system. 1.2.2.4 Key Management via Key Variable Loader (KVL) Key management via a key variable loader (KVL) feature provides the ability to manage all the keys for an AXS Console or archiving interface server using only a KVL 1.2.2.5 Key Management via Key Over-the-Ethernet Keying (OTEK) Key management through OTEK provides the ability to manage the keys for a dispatch console or AIS using only a Key Management Facility (KMF). In OTEK, the management and distribution aspects of key management are all performed by the KMF. Distribution of the key management information is done across the radio system’s IP network from the KMF to the dispatch console and AIS. 1.2.3 Incorporating Console Configuration and Management The proposed console system is configured and managed by the same configuration manager, fault manager, and performance reporting applications as the radio system. The user can define exactly which resources are available and how they are presented to the dispatcher. This provides Riverside Dispatch with a single point for configuring and managing the entire ASTRO® 25 system. Changes are automatically distributed throughout the system. This centralized approach saves valuable time and effort for system administrators and technicians and reduces the errors that can occur when radio IDs and other data are entered at multiple locations. In addition, call traffic and performance reports for each dispatch position can be generated from the system’s network manager, enabling administrators to quickly and easily ensure optimal effectiveness and efficiency. 1.2.4 Dispatch Console Solution Components The proposed components are connected together and to the rest of the ASTRO® 25 system on an IP network through console site routers and switches. The console functions as an integrated component of the total radio system and fully participates in system-level features, such as end-to-end encryption. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted The console connects directly to the radio system’s IP transport network. Audio processing, encryption, and switching intelligence for dispatch are performed within each software- based dispatch position without additional centralized electronics. Since the network is IP-based, the system interfaces and components can be distributed physically throughout the network. Some of the available console components are identified below. 1.2.4.1 CommandCentral AXS Dispatch Console Operator Position The dispatch position supports multiple peripheral accessories, including a USB microphone, USB headset, and USB footswitch. The following list describes the components included in the proposed configuration. Figure 3: CommandCentral AXS Dispatch Console Accessories Example Computer Display The dispatch position will use a 24” Computer Display. B1956 CommandCentral Hub (CC Hub) The CommandCentral Hub (CC Hub) is the platform on which the CommandCentral AXS Dispatch Console operates. The CC Hub contains a number of analog inputs and outputs for connecting various peripheral devices as well as a workstation class computer motherboard. The PC that is internal to the CC Hub will be programmed with a Microsoft Windows based operating system (OS) image developed for the dispatch application. Desktop Speakers Three audio speakers have been included with each dispatch position and can be configured to transmit audio from a specific talkgroup or set of talkgroups. Each speaker is a self- contained unit, with individual volume controls, and can be placed on a desktop or mounted on a rack or computer display. Headset Jack The dispatch position supports up to two headset jacks, both push-to-talk (PTT) and non-PTT- enabled, for simultaneous use by the dispatcher and a supervisor. The headset jack contains two volume controls for the separate adjustment of received radio and telephone audio. Headset Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted The proposed headset consists of two elements. The headset base includes an audio amplifier, a Push-to-Talk switch, and a long cord that connects to the dispatch position. The headset top consists of the earpiece and microphone as well as a short cable that connects to the headset base. Gooseneck Microphone The microphone controls the dispatch position's general transmit and monitor features through two buttons on its base. The microphone can be fastened down or left loose. It can be used alone or in conjunction with a headset. Footswitch Each dispatch position includes a dual pedal footswitch that controls general transmit and monitor functions. Telephone/Headset Interface Port The telephone/headset port provides a connection for an external telephone to the dispatch position. This allows the operator to use a single headset to communicate on both the radio system and an external telephone system. External Paging Encoder Port The external paging encoder port provides a connection for an optional external tone paging encoder to provide tone paging services via the dispatch console. Analog paging tones generated by the encoder are transmitted by the dispatch console on the selected trunked and/or conventional radio resource(s). Local Logging Recorder Port As an alternative or supplemental approach to an audio logging subsystem, the analog output port on the CommandCentral Hub allows an optionally available external logging recorder to be connected to a dispatch console. Long-term audio recording is used to record a portion of the inbound and outbound audio present on a specific dispatch position. These recordings are typically archived for long-term storage, and provide a historical record of the radio communications made at a given dispatch position. The analog output port can be configured to log any combination of these audio sources, such as: • Audio received from a currently selected radio. • Microphone audio being transmitted by this dispatcher to the currently selected or unselected radio resources. • Any tones generated by the dispatch position that appear in its speakers (trunking tones, emergency tones, etc.) or tones generated by an external paging encoder. Private Aux I/O Port The dispatch console supports four Private Aux I/O relays located on the CommandCentral Hub of the dispatch position. Each relay can be configured to support any one of the five functions or it can be configured to be unused. • Call on Selected Channel • Op PTT Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted • Emergency Beacon • Activate Private Relay when Public Aux I/O is Active • Select Phone Off Hook Relay 1.3 ASSUMPTIONS Motorola has taken the following into consideration in preparing this proposal. In the event that any of these considerations are found to be invalid, Motorola will review the impact on the schedule and pricing and may need to issue a contract change order. • Existing two monitors will be reused for the 2 replacement AXS console positions. • Existing backup radios and CCGW will be reused. • No site work is required. Motorola assumes that all power, grounding, HVAC, etc.is available to accommodate the proposed loading. • Customer will provide 20A Quad Outlets within 6ft of the newdispatch console position equipment to provide the necessary power to the new dispatch console equipment. • The AXS console location will be within 300ft of the backroom network equipment. • Any required system interconnections not specifically outlined here will be provided by the customer. • The Customer will provide a dedicated delivery point, such as a warehouse, for receipt, inventory and storage of equipment prior to delivery to the site(s). • The Customer will provide the dispatch furniture on which the AXS consoles will be installed on. They will also provide the power outlets to power the new equipment. • The Customer will provide the required connectivity to the MARRS Master Site. • Logging recorder is not included in the proposal. Any required changes to the logger would be a responsibility of the customer. • Riverside Dispatch to resolve any environmental issues including, but not limited to, asbestos, structural integrity (rooftop, water tank, tower, etc.) of the site, and any other building risks. (Resolve environmental or hazardous material issues). • Any site/location upgrades or modifications are the responsibility of Riverside Dispatch. • Frequencies for the system shall be available and to be provided by the Customer. FCC licensing and coordination will be customer responsibility. • No coverage guarantee is included in this proposal. • • Motorola is not responsible for interference caused or received by the Motorola-provided equipment except for interference that is directly caused by the Motorola-provided transmitter(s) to the Motorola-provided receiver(s). Should your system experience interference, Motorola can be contracted to investigate the source and recommend solutions to mitigate the issue. • Manage, Detection, and Response (MDR) has been included in this proposal. • The inclusion of MDR is dependent on the host system enabling MDR. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted SECTION 2 STATEMENT OF WORK 2.1 OVERVIEW This document delineates the general responsibilities between Motorola and Riverside PD as agreed to by contract. The following table describes the tasks involved with installation and configuration. Tasks | Motorola Solutions | Customer PROJECT INITIATION Contract Finalization and Team Creation Execute contract and distribute contract documents. X | X Assign a Project Manager as a single point of contact. X | X Assign resources. X | X Schedule project kickoff meeting. X | X Deliverable: Signed contract, defined project team, and scheduled project kickoff meeting. Project Administration Ensure that project team members attend all meetings relevant to their role on the project. X | X Set up the project in the Motorola Solutions information system. X | Record and distribute project status meeting minutes. X | Maintain responsibility for third-party services contracted by Motorola Solutions. X | Complete assigned project tasks according to the project schedule. X X Submit project milestone completion documents. X | Upon completion of tasks, approve project milestone completion documents. X Conduct all project work Monday thru Friday, 8 a.m. to 5:00 p.m. X | X Deliverable: Completed and approved project milestones throughout the project. Project Kickoff Introduce team, review roles, and decision authority. X | X Present project scope and objectives. X | Review SOW responsibilities and project schedule. X | X Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Tasks | Motorola Solutions | Customer Schedule Design Review. X | X Deliverable: Completed project kickoff and scheduled Design Review. Design Review Review the Customer’s operational requirements. X | X Present the system design and operational requirements for the solution. X | Present installation plan. X | Present preliminary cutover plan and methods to document final cutover process. X | Present configuration and details of sites required by system design. X | Validate that Customer sites can accommodate proposed equipment. X X Provide approvals required to add equipment to proposed existing sites. X | Review safety, security, and site access procedures. X | X Present equipment layout plans and system design drawings. X | Provide heat load and power requirements for new equipment. X | Provide information on existing system interfaces. X | X Provide frequency and radio information for each site. X | Assume liability and responsibility for proving all information necessary for complete installation. X | Assume responsibility for issues outside of Motorola Solutions’ control. X | Review and update design documents, including System Description, Statement of Work, Project Schedule, and Acceptance Test Plan, based on Design Review agreements. X Execute Change Order in accordance with all material changes to the Contract resulting from the Design Review. X Deliverable: Finalized design documentation based upon “frozen” design, along with any relevant Change Order documentation. SITE PREPARATION AND DEVELOPMENT Site Access Provide site owners/managers with written notice to provide entry to sites identified in the project design documentation. | X Deliverable: Access, permitting, and licensing necessary to install system equipment at each site. General Facility Improvements Provide adequate HVAC, grounding, lighting, cable routing, and surge protection based upon Motorola Solutions’ Standards and Guidelines for Communication Sites (R56), as identified by the customer and Motorola Solutions in the Detailed Design Review. | X Ensure the resolution of environmental and hazardous material issues at each site including, but not limited to, asbestos, | X Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Tasks | Motorola Solutions | Customer structural integrity (tower, rooftop, water tank, etc.), and other building risks. Ensure that electrical service will accommodate installation of system equipment, including isolation transformers, circuit breakers, surge protectors, and cabling. | X Provide obstruction-free area for the cable run between the demarcation point and system equipment. | X Provide structure penetrations (wall or roof) for transmission equipment (e.g. antennas, microwave radios, etc.). | X Supply interior building cable trays, raceways, conduits, and wire supports. | X Deliverable: Sites meet physical requirements for equipment installation. SYSTEM INSTALLATION Equipment Order and Manufacturing Create equipment order and reconcile to contract. X | Manufacture Motorola Solutions-provided equipment necessary for system based on equipment order. X | Procure non-Motorola Solutions equipment necessary for the system. X | Deliverable: Equipment procured and ready for shipment. Equipment Shipment and Storage Provide secure location for solution equipment. | X Pack and ship solution equipment to the identified, or site locations. X | Receive solution equipment. | X Inventory solution equipment. X | Deliverable: Solution equipment received and ready for installation General Installation Deliver solution equipment to installation location. X | Coordinate receipt of and inventory solution equipment with designated contact. X | Install all proposed fixed equipment as outlined in the System Description based upon the agreed-upon floor plans, connecting audio, control, and radio transmission cables to connect equipment to the power panels or receptacles, and audio/control line connection points. Installation performed in accordance with R56 standards and state/local codes. X | Provide system interconnections that are not specifically outlined in the system design, including dedicated phone circuits, microwave links, or other types of connectivity, as identified by the customer and Motorola Solutions in the Detailed Design Review. | X Ensure that Type 1 and Type 2 AC suppression is installed to protect installed equipment, as identified by the customer and Motorola Solutions in the Detailed Design Review. | X Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Connect installed equipment to the provided ground system. X | Tasks | Motorola Solutions | Customer Label equipment, racks, and cables. X | Perform preliminary audit of installed equipment to ensure compliance with requirements and R56 standards. X | Note any required changes to the installation for inclusion in the “as-built” system documentation. X | Deliverable: Equipment installed. Console Installation and Configuration Install PC workstation with keyboard and mouse and monitor. X | Install consoles and the purchased peripheral equipment in accordance with R56 standards and state/local codes. X | Develop templates for console programming. X | Perform console programming and configuration. X | Deliverable: Console equipment installation completed. SYSTEM OPTIMIZATION AND TESTING R56 Site Audit Perform R56 site-installation quality-audits, verifying proper physical installation and operational configurations. X | Deliverable: R56 Standards and Guidelines for Communication Sites audits completed successfully. Solution Optimization Verify that all equipment is operating properly and that all electrical and signal levels are set accurately. X | Verify that all audio and data levels are at factory settings. X | Verify communication interfaces between devices for proper operation. X | Ensure that functionality meets manufacturers’ specifications and complies with the final configuration established during design review or system staging. X | Deliverable: Completion of System Optimization. Functional Acceptance Testing Verify the operational functionality and features of the solution supplied by Motorola Solutions, as contracted. X | Witness the functional testing. X | X Document all issues that arise during the acceptance tests. X | If any major task for the system as contractually described fails during the Customer acceptance testing or beneficial use, repeat that particular task after Motorola Solutions determines that corrective action has been taken. | X Resolve any minor task failures before Final System Acceptance. X | Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Tasks | Motorola Solutions | Customer Document the results of the acceptance tests and present for review. X | Review and approve final acceptance test results. | X Deliverable: Completion of functional testing and approval by Customer. PROJECT TRANSITION Cutover Finalize Cutover Plan. X | X Conduct cutover meeting with relevant personnel to address both how to mitigate technical and communication problem impacts to the users during cutover and during the general operation of the system. X | Notify the personnel affected by the cutover of the date and time planned for cutover. | X Provide ongoing communication with users regarding the project and schedule. X | X Cut over users and ensure that consoles are operating on system. | X Resolve punchlist items, documented during the Acceptance Testing phase, in order to meet all the criteria for final system acceptance. X | Assist Motorola Solutions with resolution of identified punchlist items by providing support, such as access to the sites, equipment and system, and approval of the resolved punchlist items. | X Deliverable: Migration to new system completed, and punchlist items resolved. Transition to Warranty Review the items necessary for transitioning the project to warranty support and service. X | Motorola Solutions to provide services during year 1 warranty which align with the proposed services. X | Provide a Customer Support Plan detailing the warranty support associated with the contract equipment. X | Participate in the Transition Service/Project Transition Certificate (PTC) process. X | Deliverable: Service information delivered and approved by Customer Finalize Documentation and System Acceptance Provide manufacturer’s installation material, part list and other related material to Customer upon project completion. X | Execute Final Project Acceptance. X | X Deliverable: All required documents are provided and approved. Final Project Acceptance. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted 2.2 ACCEPTANCE TEST PLAN Under the direction of the Motorola Project Manager, teams consisting of representatives from the Customer with Motorola will execute agreed-upon test procedures to confirm that the system has been designed and installed to meet all of the features and performance capabilities agreed upon in the contract. A detailed Acceptance Test Plan will be developed during the implementation phase. 2.3 CUTOVER PLAN Riverside Dispatch and Motorola will need to develop a cutover plan. Motorola will closely work with the customer and provide a cutover plan during the implementation phase of this project. This plan will allow the integration with minimal interruption to the day-to-day operation. From a high-level, the following tasks will need to be completed. Some of these tasks may be not necessarily be completed in the specific order listed below. The transition steps will be updated as necessary during project deployment. The preliminary high-level cutover plan is as follows: • Riverside Dispatch prepares space and power for the three (3) new positions. • The customer will provide the link connectivity to the core which will help establish connectivity from the proposed consoles to the core. • Motorola will install the proposed equipment. • Motorola will verify the functionality of the three (3) new positions. The cutover plan is preliminary and Riverside Dispatch and Motorola needs to agree on the cutover plan for a seamless transition. 2.4 SCHEDULE Below is a high level schedule of tasks with an approximate timeline and order of events. A final project schedule will be developed based upon mutual agreement between Motorola Solutions and Riverside PD at the Detailed Design Review (DDR). The equipment order/ship timeline reflected below is the average lead time for materials. The duration may be impacted by global supply chain shortages. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted SECTION 3 MANAGED DETECTION AND RESPONSE (MDR) Overview In accordance with the terms and conditions of the Agreement, this Statement of Work (SOW), including all of its subsections and attachments, defines the principal activities and responsibilities of all parties for the delivery of Motorola Solutions, Inc. (Motorola Solutions) Cybersecurity services as presented in this proposal to Riverside PD (hereinafter referred to as “Customer”). In order to receive the services as defined within this SOW, the Customer is required to keep the system within a standard support period as described in Motorola Solutions’ Software Support Policy (SwSP). Description of Service Deployment Timeline and Milestones To initiate the ASTRO 25 Managed Detection and Response service to function, Motorola Solutions and the Customer must perform deployment tasks. Service deployment is broken into the following phases, each with specific deliverables. Phase 1: Information Exchange After contract execution, Motorola Solutions will schedule a service kick-off meeting with Customer and provide information-gathering documents. The kick-off meeting may be conducted either remotely or in-person, at the earliest, mutually available opportunity. Customer is to identify and ensure participation of key team members in kickoff and project initiation activities. Phase 2: Infrastructure Readiness Motorola Solutions will provide detailed requirements regarding Customer infrastructure preparation actions after kick-off meeting. It is the Customer’s responsibility to accomplish all agreed upon infrastructure preparations. Phase 3: System Buildout and Deployment Motorola Solutions will build and provision tools in accordance with the requirements of this proposal and consistent with information gathered in earlier phases. Motorola Solutions will also provide detailed requirements regarding Customer deployment actions. The Customer must deploy tools, as applicable, in their environment, in accordance with provided requirements. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Phase 4: Monitoring Turn Up Motorola Solutions will verify all in-scope assets are properly forwarding logs or events. Motorola Solutions will notify Customer of any exceptions. Motorola Solutions will begin monitoring any properly connected in-scope sources after the initial tuning period. Phase 5: Tuning and Customer Training Motorola Solutions will conduct initial tuning of the events and alarms in the service and ActiveEye training. General Responsibilities Motorola Solutions Responsibilities • Provide software and licenses to the Customer necessary to remotely monitor the ASTRO 25 network. • Verify connectivity and monitoring is active prior to start of service. • Coordinate with the Customer to maintain Motorola Solutions service authentication credentials. • Maintain trained and accredited technicians. • Monitor the Customer’s ASTRO 25 network and applicable CEN systems 24/7/365 for malicious or unusual activity. • Respond to security incidents in the Customer’s system in accordance with Section: 0Priority Level Definitions and Notification Times. This may include, but is not limited to, requesting additional information from the Customer, continuing to monitor the event for further development or informing the Customer to enact the Customer’s documented Incident Response plan. • Ensure that all monitored devices within the network are properly configured for Syslog, forwarding events to the centralized event log server. • Assist the Customer with identifying devices that support logging within the ASTRO 25 network and applicable CEN systems have been configured to forward Syslog events to the AERSS. • Provide the Customer with access to the ActiveEye Security Management platform, so the Customer can access security event and incident details. Customer Responsibilities • The ASTRO 25 Managed Detection and Response service requires a connection from the Customer’s ASTRO 25 network and applicable CEN systems to the Internet. Establish connectivity with sufficient bandwidth before service commences. Internet service bandwidth requirements are as follows: - Bandwidth throughput of 10Mbps per zone. - High availability Internet Connection (99.99% (4-9s) or higher). - Packet loss < 0.5%. - Jitter <10 ms. - Delay < 120 ms. - RJ45 Port Speed - Auto Negotiate • Maintain an active Security Update Service (SUS) subscription, ensuring patches and antivirus definitions are applied according to the release cadence of the service. • For regional adders to another system, the hosted core (regional system) must subscribe to and maintain either an ActiveEye Pulse or ASTRO 25 Managed Detection and Response service. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted • Allow Motorola Solutions continuous remote access to monitor the ASTRO 25 network and applicable CEN systems. This includes keeping the connection active, providing passwords, and working with Motorola Solutions to understand and maintain proper administration privileges. • Provide continuous utility service(s) to any Motorola Solutions equipment installed or utilized at the Customer’s premises to support service delivery. • Provide Motorola Solutions with contact information necessary to complete the Customer Support Plan (CSP). Notify the assigned Customer Support Manager (CSM) in advance of any contact information changes. • Notify Motorola Solutions if any new components are added to or removed from the environment as it may be necessary to update or incorporate in Managed Detection and Response. Changes to monitored components may result in changes to the pricing of the Managed Detection and Response service. • As necessary, upgrade the ASTRO 25 system, on-site systems, and third party software or tools to supported releases. • Allow Motorola Solutions’ dispatched field service technicians physical access to monitoring hardware when required. • Cooperate with Motorola Solutions and perform all acts that are required to enable Motorola Solutions to provide the services described in this SOW. • Configure and maintain networking infrastructure physical and logical configuration to mirror (typically via a port(s) on a switch) network traffic to the ActiveEye sensor for applicable CEN systems. • Responding to Cybersecurity Incident Cases created by the Motorola Solutions Security Operations Center. Service Modules The following subsections describe the delivery of the service modules selected. Log Analytics Motorola Solutions Responsibilities • Consult with and advise the Customer on performing necessary system configurations to direct log sources to the appropriate Remote Security Sensor. • Configure Customer’s networking infrastructure to allow AERSS to Communicate with ActiveEye as defined. • The SOC will consult with the Customer to identify appropriate log sources for the level of threat detection desired in each environment. Applies to included console infrastructure. Security Operations Center Monitoring and Support Scope Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Motorola Solutions will start monitoring the ASTRO 25 Managed Detection and Response service in accordance with Motorola Solutions processes and procedures after deployment, as described in Section: Deployment Timeline and Milestones. The SOC receives system-generated alerts 24x7 and provides the Customer with a toll-free telephone number and email address for support requests, available 24x7. Support requests are stored in a ticketing system for accountability and reporting. The SOC will respond to detected events in accordance with Section: Priority Level Definitions and Notification Times. Ongoing Security Operations Center Service Responsibilities Motorola Solutions Responsibilities If a probable security incident is detected, provide phone and email support to: • Engage the Customer’s defined Incident Response Process. • Gather relevant information and attempt to determine the extent of compromise using existing monitoring capabilities in place as part of the ASTRO 25 MDR service. • Analysis and support to help the Customer determine if the Customer’s corrective actions are effective. • Continuous monitoring, in parallel with analysis, to support incident response. Customer Responsibilities • Provide Motorola Solutions with accurate and up-to-date information, including the name, email, landline telephone numbers, and mobile telephone numbers for all designated, authorized Customer escalation Points of Contact (PoC). • Provide a timely response to SOC security incident tickets or investigation questions. • Notify Motorola Solutions at least 24 hours in advance of any scheduled maintenance, network administration activity, or system administration activity that would affect Motorola Solutions’ ability to perform the Managed SOC Service, as described in this SOW. Technical Support ActiveEye Security Management Technical Support provides the Customer with a toll-free telephone number and email address for ActiveEye Security Management support requests, available Monday through Friday from 8am to 7pm CST. Motorola Solutions Responsibilities • Notify Customer of any scheduled maintenance or planned outages. • Provide technical support, security control, and service improvements related to ActiveEye. Customer Responsibilities • Provide sufficient information to allow Motorola Solutions technical support agents to diagnose and resolve the issue. Limitations and Exclusions Technical support is limited to the implementation and use of the ActiveEye Security Management platform and does not include use or implementation of third-party components. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Incident Response An Indicator of Compromise (IoC) is an observable event that Motorola Solutions Security Analysts have determined will jeopardize the confidentiality, integrity, or availability of the system. Examples of IoC include ransomware or malicious use of PowerShell. When an IoC is observed by the Security Analyst, Motorola Solutions and Customer will be responsible for the tasks defined in the following subsections. Motorola Solutions Responsibilities • Upon the identification of an IoC, notify the Customer's documented contact and initiate the escalation plan. • Take documented, Customer approved actions in an attempt to contain an IoC to the extent enabled via Motorola Solutions managed technology. Communicate to the Customer any additional potential containment actions and incident response resources that can be taken across the Customer’s managed IT infrastructure. • Perform investigation using the ActiveEye Managed Detection and Response integrated and enabled data sources in an initial attempt to determine the extent of an IoC. • Document and share IoC and artifacts discovered during investigation. Motorola Solutions services exclude performing on-site data collection or official forensic capture activities on physical devices. Customer Responsibilities • Maintain one named PoC to coordinate regular team discussions and organize data collection and capture across the Customer and Motorola Solutions teams. • If determined to be required by Customer, contract an Incident Response service provider to perform procedures beyond the scope of this Agreement such as forensic data capture, additional malware removal, system recovery, ransomware payment negotiation, law enforcement engagement, insurance provider communications, identify patient zero, etc. Event Response and Notification Motorola Solutions will analyze events created and/or aggregated by the Service, assess their type, and notify the Customer in accordance with the following table. Table 0-1: Event Handling Event Type | Details | Notification Requirement False Positive or Benign Any event(s) determined by Motorola Solutions to not likely have a negative security impact on the organization. None Event of Interest (EOI) Any event(s) determined by Motorola Solutions to likely have a negative security impact on the organization. Escalate to Customer in accordance with routine notification procedure. Escalate in accordance with urgent notification procedure when required by agreed-upon thresholds and SOC analysis. Notification procedures are included in Table 0-2: Notification Procedures. Notification Motorola Solutions will establish notification procedures with the Customer, generally categorized in accordance with the following table. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Table 0-2: Notification Procedures Notification Procedure | Details Routine Notification Procedure The means, addresses, format, and desired content (within the capabilities of the installed technology) for Events of Interest. These can be formatted for automated processing, e.g., by ticketing systems. Urgent Notification Procedure Additional, optional means and addresses for notifications of Events of Interest that require urgent notification. These usually include telephone notifications. Motorola Solutions will notify the Customer according to the escalation and contact procedures defined by the Customer and Motorola Solutions during the implementation process. Tuning Motorola Solutions will assess certain events to be environmental noise, potentially addressable configuration issues in the environment, or false positives. Motorola Solutions may recommend these be addressed by the Customer to preserve system and network resources. Motorola Solutions will provide the Customer with the ability to temporarily suppress alerts reaching ActiveEye, enabling a co-managed approach to tuning and suppressing events or alarms. The SOC may permanently suppress particular alerts and alarms if not necessary for actionable threat detection. Tuning Period Exception The tuning period is considered to be the first 30 days after each service module has been confirmed deployed and configured and starts receiving data. During the tuning period, Motorola Solutions may make recommendations to the Customer to adjust the configurations of their installed software so Services can be effectively delivered. Service Availability will not be applicable during the tuning period and responses, or notifications may not be delivered. However, Motorola Solutions will provide responses and notifications during this period. Motorola Solutions may continue to recommend necessary tuning changes after this period, with no impact on Service Availability. Priority Level Definitions and Notification Times Motorola Solutions will analyze events created and/or aggregated by the ASTRO® 25 Managed Detection and Response services, assess their type, and notify the Customer in accordance with the following table. Table 0-3: Priority Level Definitions and Notification Times Incident Priority | Incident Definition | Notification Time Critical P1 Security incidents that have caused or are suspected to have caused significant and/or widespread damage to the functionality of Customer’s ASTRO 25 system or information stored within it. Effort to recover from the incident may be significant. Examples: ▪ Malware that is not quarantined by anti-virus. ▪ Evidence that a monitored component has communicated with suspected malicious actors. Response provided 24 hours, 7 days a week, including US Holidays. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Incident Priority | Incident Definition | Notification Time High P2 Security incidents that have localized impact but are viewed as having the potential to become more serious if not quickly addressed. Effort to recover from the incident may be moderate to significant. Examples: ▪ Malware that is quarantined by antivirus. ▪ Multiple behaviors observed in the system that are consistent with known attacker techniques. Response provided 24 hours, 7 days a week, including US Holidays. Medium P3 Security incidents that potentially indicate an attacker is performing reconnaissance or initial attempts at accessing the system. Effort to recover from the incident may be low to moderate. Examples: ▪ Suspected unauthorized attempts to log into user accounts. ▪ Suspected unauthorized changes to system configurations, such as firewalls or user accounts. ▪ Observed failures of security components. ▪ Informational events. ▪ User account creation or deletion. ▪ Privilege change for existing accounts. Response provided Monday through Friday 8 a.m. to 5 p.m. local time, excluding US Holidays. Low P4 These are typically service requests from Customer. Response provided Monday through Friday 8 a.m. to 5 p.m. local time, excluding US Holidays. Scope Limitations & Clarifications Service Limitations Cybersecurity services are inherently limited and will not guarantee that the Customer's system will be error-free or immune to security breaches as a result of any or all of the services described in this proposal. Motorola does not warrant or guarantee that this service will identify all cybersecurity incidents that occur in the Customer’s system. Services and deliverables are limited by, among other things, the evolving and often malicious nature of cyber threats, conduct/attacks, as well as the complexity/disparity and evolving nature of Customer computer system environments, including supply chains, integrated software, services, and devices. Motorola Solutions does not represent that it will identify, fully recognize, discover, or resolve all security events or threats, system vulnerabilities, malicious codes or data, backdoors, or other system threats or incompatibilities as part of the service, or that the agreed upon engagement will be sufficient to identify, mitigate or prevent any cyber incident. Processing of Customer Data in the United States and/or other Locations Customer understands and agrees that data obtained, accessed or utilized in the performance of the services may be transmitted to, accessed, monitored, and/or otherwise processed by Motorola in the United States (US) and/or other Motorola operations globally. Customer consents to and authorizes all such processing and agrees to provide, obtain, or post any necessary approvals, consents, or notices that may be necessary to comply with applicable law. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Customer and Third Party Information The Customer understands and agrees that Motorola may obtain, use and/or create and use anonymized, aggregated and/or generalized Customer data, such as data relating to actual and potential security threats and vulnerabilities, for its lawful business purposes, including improving its services and sharing and leveraging such information for the benefit of Customer, other customers, and other interested parties. For purposes of this engagement, so long not specifically identifying the Customer, Customer Data shall not include, and Motorola shall be free to use, share and leverage security threat intelligence and mitigation data generally, including without limitation, third party threat vectors and IP addresses, file hash information, domain names, malware signatures and information, information obtained from third party sources, indicators of compromise, and tactics, techniques, and procedures used learned or developed in the course of providing services. Third-Party Software and Service Providers, including Resale Motorola may use, engage, license, resell, interface with or otherwise utilize the products or services of third-party processors or sub-processors and other third-party software, hardware, or services providers (such as, for example, third-party endpoint detection and response providers). Such processors and sub-processors may engage additional sub-processors to process personal data and other Customer Data. Customer understands and agrees that the use of such third-party products and services, including as it relates to any processing or sub- processing of data, is subject to each respective third-party’s own terms, licenses, End User License Agreements (EULA), privacy statements, data processing agreements and/or other applicable terms. Such third-party providers and terms may include the following, if applicable, or as otherwise made available publicly, through performance, or upon request. Motorola disclaims any and all responsibility for any and all loss or costs of any kind associated with security events. Motorola disclaims any responsibility for customer use or implementation of any recommendations provided in connection with the services. Implementation of recommendations does not ensure or guarantee the security of the systems and operations evaluated. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted SECTION 5 ADVANCED PLUS SERVICES 5.1 OVERVIEW Advanced Plus Services for ASTRO® 25 infrastructure is a comprehensive program to sustain the long- term performance of the Riverside PD’s network. Advanced Services consists of the following elements: • ASTRO System Monitoring. o Managed Detection and Response (MDR). o Network Event Monitoring. • Remote Technical Support. • Network Hardware Repair. • Network Hardware Repair with Advanced Replacement. • Security Update Service (SUS). • Remote Security Update Service (RSUS). • On-site Infrastructure Response. • Annual Preventative Maintenance. • Together, these elements will help to avoid operational disruptions and maintain the value of Riverside PD’s communications investment. 5.2 ADVANCED PLUS SERVICES ELEMENT DESCRIPTIONS The following sections describe the elements proposed for Riverside PD’s ASTRO 25 infrastructure. 5.2.1 ASTRO System Monitoring ASTRO System Monitoring Service includes advanced network and security monitoring along with connectivity to deliver these services. Managed Detection and Response Experienced, specialized cybersecurity analyst at Motorola’s Security Operations Center (SOC) will monitor the Customer's ASTRO® 25 radio network for security threats. SOC analysts will coordinate with the Customer through the ActiveEyeSM Security Platform to identify and mitigate threats to the Customer’s networks. Network Event Monitoring Real-time, continuous ASTRO® 25 radio communications network monitoring and event management. Using sophisticated tools for remote monitoring and event characterization, Motorola will assess events, determine the appropriate response, and initiate that response. Possible responses include remotely Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted addressing the issue, escalation to product technical support groups, and dispatch of designated field technical resources. 5.2.2 Remote Technical Support Motorola Solutions’ Centralized Managed Support Operations (CMSO) will provide Remote Technical Support for infrastructure issues that require specific technical expertise. Experienced technical support specialists will be available to consult with Riverside PD to help diagnose, troubleshoot and resolve infrastructure issues. Service Desk maintenance procedures and incident resolution techniques are based on ISO 9001 and TL 9000 standards. 5.2.3 Network Hardware Repair To restore Riverside PD’s ASTRO 25 network components if they malfunction, Motorola Solutions will repair Motorola Solutions-provided infrastructure equipment. This includes select third-party infrastructure equipment supplied by Motorola Solutions. Motorola Solutions will ship and return repaired equipment, and will coordinate the repair of third-party solution components. 5.2.4 Network Hardware Repair with Advanced Replacement To restore Riverside PD’s ASTRO 25 network components if they malfunction, Motorola Solutions will repair Motorola Solutions-provided infrastructure equipment. This includes select third-party infrastructure equipment supplied by Motorola Solutions. Motorola Solutions will ship and return repaired equipment, and will coordinate the repair of third-party solution components. To reduce the impact of a malfunction, Motorola Solutions will exchange malfunctioning equipment with Advanced Replacement units or Field Replacement Units (FRU), as available. Motorola Solutions’ repair depot will diagnose and repair malfunctioning components, and once repaired, add those to the depot’s FRU inventory. Replacement components will remain in Riverside PD’s ASTRO 25 network to maintain continued network functionality. 5.2.5 Remote Security Update Service Commercial security software updates are often designed without consideration for specialized systems like radio communications networks. These updates may inadvertently disrupt ASTRO 25 network operations and functionality. To minimize cyber risks and software conflicts, Motorola Solutions provides the Remote Security Update Service (RSUS). With this service, Motorola Solutions deploys antivirus and operating system security updates on an ASTRO 25 network in a dedicated information assurance lab to test and validate them for use with ASTRO 25 networks. Motorola Solutions tests whether applying these security updates degrades network service. If an update degrades performance, Motorola Solutions searches for a solution or workaround to address the issue before releasing that update. If Riverside PD prefers to maintain their existing FRU inventory rather than using Motorola Solutions’ depot inventory, Motorola Solutions can provide “loaner” FRUs during the repair process. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted With RSUS, Motorola Solutions will remotely install tested updates on Riverside PD’s ASTRO 25 network. If there are any recommended configuration changes, warnings or workarounds, Motorola Solutions will provide detailed documentation on a secured extranet website. 5.2.6 On-site Infrastructure Response Motorola Solutions will provide repair service from trained and qualified technicians. Once dispatched, technicians will travel to Riverside PD’s ASTRO 25 network location to diagnose issues and restore functionality. These technicians will run diagnostics on hardware to identify defective components, and repair or replace them as appropriate. Infrastructure Response times are based on a given issue’s impact on overall system function. 5.2.7 Annual Preventive Maintenance Motorola Solutions will annually test and service network components. Qualified field technicians will perform routine hands-on examination and diagnostics of network equipment to keep them operating according to original manufacturer specifications. 5.3 MOTOROLA SOLUTIONS SERVICE DELIVERY ECOSYSTEM Advanced Services are delivered through a tailored combination of field service personnel, centralized teams, product repair depots and Customer Hub. These service resources will collaborate to swiftly analyze network issues, accurately diagnose root causes, and efficiently resolve issues to return the network to normal operation. Motorola Solutions services will be delivered by staff experienced in servicing mission-critical networks. Motorola Solutions uses the Information Technology Infrastructure Library (ITIL) framework to define service tasks based on industry-recognized best practices. As staff perform tasks, service incident information will be available to Riverside PD’s administrators and personnel through Customer Hub. Service activities and Motorola Solutions’ service team are described in more detail below. 5.3.1 Centralized Managed Support Operations The cornerstone of Motorola Solutions’ support process is the Centralized Managed Support Operations (CMSO) organization. This TL 9000/ISO 9001-certified organization is staffed 24x7x365 by experienced service desk specialists, security analysts, and operations managers. The CMSO houses critical central functions, including the Service Desk. The CMSO Service Desk will serve as a single point of contact for services. It processes service requests, service incidents, change requests, and dispatching. The Service Desk communicates necessary Travel times and service levels are governed by local geography. Motorola Solutions will provide additional information in the Statement of Work for ASTRO 25 Advanced Services and in the Customer Support Plan agreed between Riverside PD and Motorola Solutions. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted information to stakeholders, bridging communications among Riverside PD, Motorola Solutions, and third-party subcontractors. Service Desk teams record, track and update incidents through the Motorola Solutions Customer Relationship Management (CRM) system. They document and respond to inquiries, requests, concerns and service tickets. When an incident is initiated, the CMSO will engage with teams to resolve that incident. The CMSO will escalate to new teams when needed. Depending on the incident, the CMSO will coordinate incident resolution with local field service and authorized repair depots. 5.3.2 Field Service Motorola Solutions authorized and qualified field service technicians will perform the On-site Infrastructure Response service, repair malfunctioning hardware in the field, and conduct preventive maintenance tasks. These technicians will coordinate with the Service Desk, technical support teams, and product engineering as needed to resolve incidents. 5.3.3 Repair Depot The Motorola Solutions Repair Depot will provide Riverside PD with a central repair location. This will eliminate the need to send network equipment to multiple vendor locations for repair. Motorola Solutions tracks products sent to the Depot via a case management system throughout the repair process. This system will enable Riverside PD’s representatives to check repair status, from inbound shipment to return. 5.3.4 Customer Support Manager A Motorola Solutions Customer Support Manager (CSM) will be Riverside PD’s key point of contact for the definition and administration of services. The CSM will work with Riverside PD to define service delivery details to address Riverside PD’s specific priorities. 5.3.5 Customer Hub To provide Riverside PD with quick access to service details, Motorola Solutions will provide our Customer Hub online network information tool. Customer Hub provides our customers with real-time critical network and services information through an easy-to-use graphical interface. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted Customer Hub offers real-time, role-based access to critical network and services information. With Customer Hub, Riverside PD’s administrators will be able to monitor system health and maintenance updates. Capabilities include: • Viewing network and support compliance. • Viewing incident reports. • Updating and creating incidents. • Checking system update status. • Receiving pro-active notifications regarding updates. Available 24x7x365 from any web-enabled device, the information provided by Customer Hub will be based on your needs and user access permissions, ensuring that the information displayed is secure and pertinent to your operations. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted SECTION 6 PRICING SUMMARY Motorola is pleased to provide the following equipment and services to Riverside PD. Description AXS Console (QTY 3) System Hardware, Equipment, Installation, removal of existing MCC 7500s, Onsite Training and 1 Year Warranty $332,204 Customer Loyalty Discount for Contract Execution by January 23rdth, 2026 -$42,000 Total AXS Dispatch System Price $290,204 New DSC Site Controller Equipment Upgrade $12,000 Total Recommended System Purchase $302,204 Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted SECTION 7 CONTRACTUAL DOCUMENTATION This proposal shall be governed by the terms contained herein and the terms of the MO State Contract # MT250038001 (“Contract”). The Contract is hereby incorporated as an integral part of this proposal. Riverside PD Dispatch Console November, 2025 Use or disclosure of this proposal is subject to the restrictions on the cover page. Motorola Solutions Confidential Restricted