Carlsbad City Council
February 4, 2025

RESOLUTION NO. 2025-034

A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF CARLSBAD,

CALIFORNIA, AUTHORIZING THE CITY MANAGER TO EXECUTE AN
AGREEMENT WITH MOTOROLA SOLUTIONS, INC. FOR THE POLICE

DEPARTMENT'S COMPUTER-AIDED DISPATCH SYSTEM IN AN AMOUNT NOT TO EXCEED $2,452,419.00 OVER A NINE-YEAR PERIOD
WHEREAS, the City Council ofthe City of Carlsbad, California has determined that it is in the best interest of the city to replace the Police Department's computer-aided dispatch (CAD) system; and WHEREAS, the existing CAD system has reached the end of its typical lifespan and is in need of updating; and
WHEREAS, the Police Department solicited proposals from firms interested in and qualified to design, implement, and support an off-the-shelf CAD system and mobile computing application; and WHEREAS, staff selected Motorola Solutions Inc. ("Motorola") as the CAD replacement system and mobile computing application vendor following a formal proposal process; and WHEREAS, City Council approved the original agreement to purchase a CAD system, mobile computing application, and other products and services from Motorola with Resolution No. 2022-107 on May 10, 2022; and
WHEREAS, the cloud-based CAD system originally proposed by Motorola became unavailable, and staff have negotiated a new agreement for a comparable managed on-premises solution; and WHEREAS, the first six years of the new on-premises CAD solution is the same cost as the original six-year cloud-based CAD agreement for $1,856,620.00; and WHEREAS, staff negotiated an additional three years of maintenance at favorable pricing for a cost of $595,799.00 for a total agreement amount not to exceed $2,452,419.00 over a nine-year period; and
WHEREAS, Carlsbad Municipal Code 3.28.060 - Procurement of Professional Services and Services requires the City Council's approval for the procurement of professional services or services that cost more than $100,000 per agreement year; and
WHEREAS, the Strategic Digital Transformation Investment Program (SDTIP) for fiscal year 2022-23 included funding for the implementation and first year of maintenance services for the CAD system; and
WHEREAS, the funding for years 2 - 9 will be included as part of the Information Technology Department Operating Fund's annual budget process.

WHEREAS, the City Manager will have the authority to execute the new Motorola CAD system agreement in an amount not to exceed $2,452,419.00; and WHEREAS, Motorola will provide implementation, management, and full maintenance services for the CAD system as specified in the agreement.

NOW, THEREFORE, BE IT RESOLVED by the City Council of the City of Carlsbad, California, as follows :

1. 2.

That the above recitations are true and correct.

That the managed on-premises CAD system and related products and services agreement (Attachment A) is hereby approved, and the City Manager is authorized to execute all required documents on behalf of the City.

3. That the total cost of the nine-year agreement will not exceed $2,452,419 .00.

4. That the funding for the first year of the Agreement is budgeted in the SDTIP Project funds.

5. That the funding for years 2 - 9 will be included as part of the Information Technology Department Operating Fund's annual budget process.

PASSED, APPROVED AND ADOPTED at a Regular Meeting of the City Council of the City of Carlsbad on the 4th day of February 2025, by the following vote, to wit:

AYES:

NAYS:

ABSTAIN:

ABSENT:

Blackburn, Bhat-Patel, Acosta, Burkholder, Shin.

None.

None .

None .

KEITH BLACKBURN, Mayor
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A

AGREEMENT FOR POLICE DEPARTMENT ON-PREMISES COMPUTER-AIDED DISPATCH SYSTEM

AND RELATED SERVICES
MOTOROLA SOLUTIONS, INC.

THIS AGREEMENT ("Agreement") is made and entered into as of the Ldh day of _::,...,J....Jr.::.:!,,-JL..!,,,::!,cJ...s;,,d,&f-::.,,-----' 2025, ("Effective Date") by and between the City of Carlsbad, California, a municipal corpor ion ("City" or "Customer'') and Motorola Solutions, Inc., a Delaware corporation ("Contractor" or "Motorola") .

RECITALS
A. On January 8, 2020, the City issued a request for proposals No. 20-13 ("RFP No. 20-13") for a computer -aided dispatch system ("CAD").

B. .contractor responded to RFP No. 20-13, and based on Contractor's proposal, other submittals, and product demonstrations and representations, City selected Contractor's PremierOne cloud­ based CAD system.

C. On May 12, 2022, City and Contractor entered into an agreement for the purchase of Contractor's flagship PremierOne cloud-based CAD system and mobile application along with Command Central Aware, its real-time crime center application, and other related products and services as described in the agreement as well as MS00 In-Car Video as a Service ("May 2022 Agreement").

To date, with the exception of the in-car video portion of the agreement, City has not received any other products or services, most notably, the PremierOne cloud-based CAD system.

D. The Parties agree that instead of a PremierOne cloud-based CAD system, Contractor will provide a PremierOne on-premises CAD system as a service for which Contractor agrees to provide and install all necessary physical hardware, equipment , and associated software as well as service, maintain, repair, and replace the physical hardware , equipment, and associated software for the term of this Agreement. As part of this on-premises CAD system, Contractor agrees to be exclusively responsible for managing, maintaining , and operating the equipment, hardware , software, operating systems, and infrastructure in such a manner that, in effect, the City has a cloud-based CAD system for the term of this Agreement.

E. The Parties agree that the MS00 In-Car Video as a Service portion of the May 2022 Agreement will be covered in a separate agreement . Accordingly, the costs associated with in-car video are not included in this Agreement.

F. The remaining products and services in the May 2022 Agreement will be provided by Contractor as part of this Agreement and as outlined in the scope of work .

G. The Parties agree the cost of the foregoing will not exceed $1,856,620 for the first six years of this Agreement, which reflects the cost of the May 2022 Agreement (excluding in-car video).

Thereafter, the maintenance and support cost for years seven through nine will be $180,000 with a yearly 10% escalator for a total of $2,452,419 as outlined in the scope of work.

H. The Parties agree to terminate the May 2022 Agreement.

NOW, THEREFORE, in consideration of these recitals and the mutual covenants contained in this Agreement, City and Contractor agree as follows :

1. MAY 2022 AGREEMENT TERMINATION
The Parties agree the May 2022 Agreement is terminated in its entirety effective immediately.

2. SCOPE OF WORK
City retains Contractor to perform, and Contractor agrees to render, those services (the "Services") that are defined in attached Exhibit "A" (“On-Prem SOW ”), which is incorporated by this reference in accordance with this Agreement’s terms and conditions.

3. TERM
The term of this Agreement will be effective for a period of nine (9) years from the date first above written.

In addition to the Termination Section of this Agreement, the City may elect to terminate the Agreement after year six (6), seven (7), and eight (8) without (i) constituting a breach of this Agreement, (ii) incurring liability for breach, and (iii) responsibility for payment obligations beyond products delivered or services satisfactorily performed up to the termination date. This Agreement is subject to the annual appropriation of funds by the City Council.

4. COMPENSATION

4.1 Total Compensation. The total fee payable for the Services to be performed during the Agreement term shall not exceed two million four hundred fifty -two thousand four hundred nineteen dollars ($2,452,419). No other compensation for the Services will be allowed except for items covered by subsequent amendments to this Agreement. The cost for Services shall not exceed the yearly amounts specified in Exhibit “A.”

4.2 Payment Terms . Payment shall be issued within 30 days of receipt of an uncontested invoice. There shall be no interest or late fees charged on late payments.

4.3 No Additional Cost . “No Additional Cost” means no additional cost over and above $2,452,419.

5. ON-PREM CAD AS A SERVICE

5.1 On-Prem CAD Equipment. Contractor agrees to provide and install all necessary physical hardware, equipment, and any software necessary to run the equipment or hardware required for the on-premises CAD system as well as configure, service, maintain, repair, and replace, as nece ssary, the physical hardware, equipment, and associated software (“On -Prem CAD Equipment”). If Contractor intentionally or inadvertently failed to identify necessary physical hardware, equipment, or associated software in the On-Prem SOW, Contractor agrees to be responsible for providing the omitted product at No Additional Cost.

5.2 On-Prem CAD Management. The Parties intend to replicate the effect of having a cloud - based CAD through an on-premises CAD system as a service . Accordingly, Contractor agrees to be exclusively responsible for managing, maintaining, and operating the equipment and hardware, infrastructure, software, and operating systems as a whole such that, in effect, the City has a cloud-based CAD. Contractor’s responsibili ties also include, but are not limited to, performing backups, upgrades, security patching and monitoring. Contractor agrees, and is responsible for, taking all necessary steps to fulfill the intent of the Parties as specified in this section. (Collectively, Contractor’s responsibilities in this section are defined as “On-Prem CAD Management”). If Contractor intentionally or inadvertently failed Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 10 of 372

to identify any services or products in the On -Prem SOW required for On -Prem CAD Management , Contractor agrees to be responsible for providing the omitted service or product at No Additional Cost.

5.3 On-Prem CAD . Contractor agrees to provide an on -premises CAD system (and other components and services ) that perform as specified in Appendix B – Functional Requirements of Contractor’s response to RFP No. 20-13 dated July 23, 2021 (“RFP Matrix Response”), the On-Prem SOW, Section 5.1 “On-Prem CAD Equipment ,” and Section 5.2 “On-Prem CAD Management. ” The RFP Matrix Response is incorporated in this Agreement by reference and attached as Exhibit “B.” The Parties agree that in the event the On-Prem SOW intentionally or inadvertently omitted any promises or representations included in the RFP Matrix Response, Contractor will perform, fulfill, and comply with Contractor’s promises and representations included in the RFP Matrix Response. Notwithstanding the aforementioned, the RFP Matrix Response and On-Prem SOW are subject to any modifications identified in this Agreement. (Collectively, the criteria and specifications in the RFP Matrix Response and On-Prem SOW as well as the language of Section 5.1 “ On-Prem CAD Equipment” and Section 5.2 “On -Prem CAD Management” mean “On-Prem CAD”). The On -Prem CAD will be installed in the data center at 1635 Faraday Ave., Carlsbad, California, 92008.

6. ON-PREM CAD RELIABILITY PERIOD AND FINAL SYSTEM ACCEPTANCE

6.1 Final System Acceptance . The On-Prem CAD will be deemed completed only when City has determined the following: (1) Contractor has met all the requirements of the RFP Matrix Response (Exhibit “B”); (2) Contractor has met all the requirements of the On -Prem SOW (Exhibit “A”); (3) the On - Prem CAD has successfully completed a feature -by-feature functional validation test in accordance with the RFP Matrix Response and functional validation scenarios in accordance with Section 6 “Product Validation” of the On-Prem SOW; and (4) Contractor has fulfilled the Reliability Period as defined below.

City will provide Contractor written confirmation of final acceptance and completion of the On-Prem CAD.

For clarity, Critical Priority Level 1, High Priority Level 2, and Medium Priority Level 3 issues must be addressed during functional validation scenarios testing in accordance with Section 2.4.6 “Functional Validation” and Section 6 “Product Validation” o f the On-Prem SOW. However, Low-level Priority issues shall not thwart final acceptance and completion.

6.1.1 Reliability Period. A 90-day reliability period (“Reliability Period”) commences at Go Live and provides City with remote access to Contractor’s implementation team resources while using the On-Prem CAD in a live operation mode. During this period, the system will perform without any Priority Level 1 and 2 incidents as defined in the Maintenance and Support Agreement . The Reliability Period is provided at No Additional Cost to City.

If a Critical Priority Level 1 incident occurs, the Reliability Period will stop until the issue is corrected, then restart on Day 1. For High Priority Level 2 issues, the Reliability Period will be stopped and if corrected within 24 hours, the Reliability Period will resume from the day it was stopped. If a High Priority Level 2 issue requires more than 24 hours to resolve, the Reliability Period will start over from Day 1. If multiple High Priority Level 2 issues occur such that combined, they result in m ultiple critical functions being unavailable or a single function being unavailable multiple times, or severely degraded such that the City’s Police Department’s core business functions and capabilities are no longer delivered or capable, the City reserves the right to categorize them as a Priority Level 1 incident and restart the Reliability Period.

Medium Priority Level 3 and Low Priority Level 4 issues will not interrupt the continuation of the Reliability Period.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 11 of 372

7. SERVICE RESPONSE TIMES AND AVAILABILITY

7.1 Service Response Times. The table below lists the on premise workstation performance requirements for transactional commands.

Activity Maximum Response Time
Command transactions 1 second
Command transactions with extended search 3 seconds

“Transactional Response Time” is the interval of time from when an Authorized User performs a transaction to when visual confirmation of transaction completion is received by the Authorized User.

Command transactions are defined as commands executed from the PremierOne CAD client command line or executed from a form on the CAD client.

Examples of command transactions are:
a. Address validation during incident initiation
b. Incident update (adding comments, changing incident type) c. Newly initiated call displays pending calls window(s) d. Display of unit recommendation form for an incident
e. Dispatch a unit to or clear a unit from an event
f. Perform Location Detail command to obtain premise history within the past 7 days g. Request a unit history for the past 48 hours
h. Traffic pursuit

Command transactions with extended search are defined as PremierOne CAD functions performed from a form on the CAD client that include multiple search parameters or an extended search time frame (i.e. more than 7 days for premise history searched or more than 48 hours for unit history searched).

Examples of command transactions with extended search are:
a. Premise history searches for over 7 days or that involve multiple search parameters b. Unit history commands for longer than the past 48 hours

Queries of external databases (i.e. Records Management System, State/NCIC queries) and reports run against the RDW are excluded from Response time metrics.

7.2 Service Availability . The CAD application will be available 99.9 percent of the time (“Service Availability”). The following specification defines both system availability and the method by which it is calculated.
1) System availability will be expressed as a percentage of the maximum expected availability over a given period.
2) Scheduled down time for system upgrades or scheduled maintenance periods will not be construed as time the service is unavailable.
3) Service unavailability due to the following exclusive list of force maj eure events will not be construed as time service is unavailable: (1) natural disasters, (2) third-party service outages, or (3) network disruptions outside of Contractor’s network.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 12 of 372

4) The percentage availability for any period will be calculated as follows:
(Total Hours in Period – Hours System Unavailable) x 100 Total Hours in Period

7.3 Failure to Meet Service Availability. At Ci ty’s request, Contractor will calculate City’s Service Availability during a given calendar month. If Service Availability has not been met, Contractor will provide a service credit up to a maximum of 50% of the fees for any given month as outlined in the table below.

Fees for any given month will be calculated by dividing the annual recurring costs by twelve (12) . Any service credit will be applied to the following annual billing invoice. If the Agreement is terminated for Contractor’s breach, Contractor shall refund all outstanding service credits by check.

Service Availability Monthly Service Credit

98.5%-99.89% 5%

97.5%-98.4% 10%

95.5%-97.4% 15%

93.5%-95.4% 30%

93.4% or less 50%

8. STANDARD OF PERFORMANCE
While performing the Services, Contractor will exercise the reasonable professional care and skill customarily exercised by reputable members of Contractor's profession practicing in the Metropolitan Southern California area and will use reasonable diligence and best judgment while exercising its professional skill and expertise.

9. TIME IS OF THE ESSENCE
Contractor acknowledges that time is of the essence with respect to Contractor’s performance under this Agreement and agrees to prompt and timely performance of all Services and other obligations in accordance with this Agreement.

10. STATUS OF CONTRACTOR
Contractor will perform the Services in Contractor's own way as an independent contractor and in pursuit of Contractor's independent calling, and not as an employee of City. Contractor will be under control of City only as to the result to be accomplished, but will consult with City as necessary. The persons used by Contractor to provide services under this Agreement will not be considered employees of City for any purposes.

The payment made to Contractor pursuant to the Agreement will be the full and complete compensation to which Contractor is entitled. City will not make any federal or state tax withholdings on behalf of Contractor or its agents, employees or subcontractors . City will not be required to pay any workers' compensation insurance or unemployment contributions on behalf of Contractor or its employees or subcontractors. Contractor agrees to indemnify City within thirty (30) days for any tax, retirement contribution, social security, overtime payment, unemployment payment or workers' compensation payment which City may be required to make on behalf of Contractor or any agent, employee, or subcontractor of Contractor for work done under this Agreement. At the City’s election, City may deduct the indemnification amount from any balance owing to Contractor.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 13 of 372

11. SUBCONTRACTING
Contractor will not subcontract any portion of the Services without prior written approval of City , which shall not to be unreasonably withheld. If Contractor subcontracts any of the Services, Contractor will be fully responsible to City for the acts and omissions of Contractor's subcontractor and of the persons either directly or indirectly employed by the subcontractor, as Contractor is for the acts and omissions of persons directly employed by Contractor. Nothing con tained in this Agreement will create any contractual relationship between any subcontractor of Contractor and City. Contractor will be responsible for payment of subcontractors. Contractor will bind every subcontractor and every subcontractor of a subcontractor by the terms of this Agreement applicable to Contractor's work unless specifically noted to the contrary in the subcontract and approved in writing by City.

11.1 On-Prem Subcontracting . For Clarity , City shall have final authority to approve or disapprove of any subcontractors used to fulfill Section 5.1 “On-Prem CAD Equipment” and Section 5.2 “On-Prem CAD Management”; provided, however, City’s approval shall not be unreasonably withheld.

Accordingly, Contractor shall provide City with sufficient information about the subcontractor(s) to make an informed decision as to subcontractor(s) competency and availability.

12. OTHER CONTRACTORS
The City reserves the right to employ other Contractors in connection with the Services.

13. TECHNOLOGY TERMS AND CONDITIONS

13.1 Data Definitions . For purposes of this Agreement (not only this section) , “ City Data ” means any data that is processed , created, or stored through the Services. “City’s Confidential Data” means Criminal Justice Information Services (CJIS) defined data, Personally Identifiable Information (PII), Protected Health Information (PHI), financial information, and any other sensitive information regardless of whether it is marked as confidential, orally identified as confidential at the time of disclosure, or confirmed as confidential in writing. For clarity, City Data includes City’s Confidential Data.

For clarity, Section 9 “Confidentiality” of Motorola’s Terms and Conditions , specifically the Master Customer Agreement applies to City’s Confidential Data (Exhibit “C”).

13.2 Sensitive Information. In instances where any agreement, purchase order, or Scope of Work is for the provision of Public Cloud Services where City’s Confidential Data may be exchanged, Contractor shall provide an independently certified System and Organization Controls (SOC) 2 Type 2 Audit Report or a SOC Cybersecurity Report or equivalent certification for all parties to the Agreement and annual updates during the term of the Agreement . The City and Contractor shall review the findings of each report and mutually agree on a reme diation plan to address any identified weaknesses or deficiencies. The City reserves the right to approve or deny access based on the results of the (SOC) 2 Type 2 Audit Report, SOC Cybersecurity Report, or equivalent certification.

13.3 Sub-processors. With written consent from the City, Contractor may engage sub - processors who in turn may engage additional sub -processors to process data in accordance with this Agreement and U.S. Department of Justice requirements. When engaging sub-processors, Contractor will enter into agreements binding su b-processors to data processing , data security, confidentiality , and background check obligations that are no less stringent than those required under this Agreement; Contractor shall also ensure that sub-processors bind any additional sub-processors to the same.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 14 of 372

13.4 Data Access and Availability. Contractor shall ensure the City has full access to retrieve all data from the On -Prem CAD and the On -Prem CAD Equipment via a live database connection or Application Programming Interface (API) to the primary software database or a secondary contractor managed copy via datalake or data warehouse (RDW). This external data access will be live or within a five (5)-minute or less data sync from live production system data. Contractor will provide City access to documentation on database schemas. Contractor will not prevent City from accessing data for purposes of synchronizing CAD data with City’s datalake.

13.5 Data Center Location and Data Ownership. The Contractor shall provide its services to the City and its end users solely from data centers in the continental United States. Storage of City Data at rest shall be located solely in data centers in the United States. Contractor will notify the City of any plans to temporarily or permanently relocate its hosted services to another data center. Contractor shall not allow personnel or subcontractors to store City Data on portable devices, including personal computers, except for devi ces that are used an d kept only at its U.S. data centers. The Contractor shall permit its personnel and subcontractors to access City Data remotely only as required to provide technical user support or other customer support. The City will own all right, title and interest in City Data that is related to the services provided by this Agreement.

13.5.1 Exception. Contractor may provide its billing services in data centers in Poland.

Only City Data that is necessary to process City invoices may be transmitted to and stored in data centers in Poland. For clarity, no other City Data may be processed, transmitted, or stored in data centers outside of the continental United States, which would otherwise constitute a data breach by Motorola.

13.6 Data Protection. Contractor shall ensure there is no inappropriate or unauthorized use , access, or disclosure of City Data at any time. To this end, Contractor shall safeguard the confidentiality, integrity, and availability of City Data within its control using security technologies and techniques in accordance with standard industry practices for such data and in accordance with the CJIS Security Policy and the CLETS Policies Practices and Procedures. The CJIS Security Policy and CLETS Policies and Practices and Procedures are amended from time to time; Contractor is responsible for adhering to the most current versions.

13.7 Data Breach and Security Incident Responsibilities. This section only applies when there is a breach of City Data within the possession or control of Contractor or a security incident. Contractor shall: (1) immediately notify City by telephone if Contractor confirms that there is or reasonably believes that there has been a data breach or security incident; (2) cooperate with the City as reasonably requested by the City to investigate and resolve the data breach or security incident and provide daily updates; (3) quarantine the data breach or security incident and ensure secure access to City Data; (4) promptly implement necessary remedial measures; and (5) document responsive actions taken related to the data breach or security incident.

13.8 Background Checks . As permitted or required by law, the Contractor shall conduct criminal background checks and not utilize any staff, including subcontractors or sub-processors, to fulfill the obligations of the Agreement who have been convicted of any crime of dishonesty, including but not limited to criminal fraud, or otherwise convicted of any felony or any misdemeanor offense for which incarceration for up to one (1)-year is an authorized penalty. The Contractor shall promote and maintain an awareness of importance of securing the City’s information among the Contractor’s employee and agents.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 15 of 372

13.9 Information Technology Access . All electronic and information technology procured through this Agreement must meet the applicable accessibility standards of Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) as amended and is viewable at http://www.section508.gov.

Further, the Contractor assures the City that the Contractor complies with the American with Disabilities Act of 1990 (42 US.C. 12101 et seq.), including the Department of Justice’s final rule revising the regulation implementing Title II of the Americans with Disabilities Act to establish specific requirements, including the adoption of specific technical standards, for making accessible the services, programs, and activities offered by State and local government entities to the pu blic through the web and mobile applications (“apps”) which became effective June 24, 2024 (89 FR 31320.). And in accordance with California Government Code Section 7405(b), the Contractor shall have the ongoing obligation to promptly respond to and resolve any complaint regarding accessibility that is brought to the attention of the Contractor.

13.10 Data Security Obligations . Collectively, the obligations set forth in Sections 13.2, 13.3,

13.5, 13.6, 13.7, and 13.8 are defined as Contractor’s “Data Security Obligations.”

14. INDEMNIFICATION

14.1 Contractor Performance. Contractor agrees to defend (with counsel that has a minimum of five (5) years of experience defending California public agencies), indemnify, and hold harmless the City and its officers, elected and appointed officials, employees and volunteers from and against all claims , damages, losses and expenses including attorney fees arising out of the performance of the work described in this Agreement caused by any negligence, recklessness, or willful misconduct of the Contractor, any subcontractor, anyone directly or indirectly employed by any of them or anyone for whose acts any of them may be liable.

The parties expressly agree that any payment, attorney fees, costs or expenses City incurs or makes to or on behalf of an injured employee under the City’s self-administered workers’ compensation is included as a loss, expense or cost for the purposes of this section, and that this section will survive the expiration or early termination of this Agreement.

14.2 Intellectual Property. To the fullest extent permitted by law, Contractor will indemnify, defend (with counsel that has a minimum of five (5) years of experience defending California public agencies), and hold harmless the City, its officers, elected and appointed officials, employees, and volunteers from any and all third -party claims, costs (including without limitation reasonable attorney fees), damages, and losses for infringement or violation of any U.S. Intellectual Property Right by any product or service provided by this Agreement. Contractor’s duties under this section are conditioned upon: (a) C ity promptly notifying Contractor in writing of the infringement claim; (b) Contractor having sole control of the defense of the suit and all negotiations for its settlement or compromise, provided that such settlement or compromise does not require the admission of liability, fault, or wrongful act or conduct on the part of City ; and (c) C ity cooperating with Contractor and, if requested by Contractor, providing reasonable assistance (at no cost to City) in the defense of the infringement claim.

Contractor will have no duty to defend or indemnify City for any infringement claim that arises from or is based upon: (a) C ity Data, C ity-Provided Equipment, Non -Motorola Content, or third-party provided equipment, hardware, software, data, or other third -party provided material s outside the scope of the On-Prem SOW; (b) the combination of the Product or Service with any products or materials not provided by Contractor or Products or Services that are not a material part of the alleged patented invention and are not suitable for substantial non -infringing use; (c) while this Agreement does not contemplate any custom designs, modifications, or manufacturing of Products or Services, in the event of such occurrence, Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 16 of 372

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 Contractor; (e) use of the Product or Service in a manner for which the Product or Service was not authorized 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.

Aside from Contractor’s indemnification obligation, should the product or services (regardless of whether it is a third-party product or service as long as it is provided within the scope of the On-Prem SOW) or any part of them become, or in Contractor’s reasonable opinion are likely to become, the subject of a claim for infringement of a third party intellectual property right, then Contractor shall, at its sole option and expense: (i) procure for City the right to use and access the infringing or potentia lly infringing item(s) of the service or product (“Infringing Item”) free of any liability for infringement; or (ii) replace or modify the Infringing Item with a non -infringing substitute otherwise materially complying with the functionality of the replaced service or product; or (iii) if neither of the foregoing is reasonably practicable, terminate the right to use and access and refund any prorated prepaid fees for the Infringing Item in the event of a service or product . However, in the event Contractor exercises option (iii), Contractor shall provide Customer with ninety (90) days of use and access to the Infringing Item prior to termination.

14.3 Damage and Loss of Data. Contractor agrees to defend (with counsel that has a minimum of five (5) years of experience defending California public agencies), indemnify, and hold harmless the City and its officers, elected and appointed officials, employees and volunteers from and against all claims, damages, losses and expenses including attorney fees arising out of (i) data breach, including but not limited to, unauthorized access, acquisition, disclosure, or use of City Data; (ii) hacking, (iii) loss, corruption, or theft of data, (iv) ransomware, (v) denial of se rvice, or (vi) Contractor’s breach of its Data Security Obligations. In addition to the foregoing, Contractor shall be responsible for costs of data restoration, system recovery, incident response, and other actions necessary to restore the integrity and availability of City Data and systems impacted by such events.

14.4 Limitations on Liability. Contractor will not disclaim or exclude liability for damages to the City’s digital infrastructure, City Data, tangible and real property arising from negligence, recklessness, or willful misconduct of the Contractor, any subcontractor, anyone directly or indirectly employed by any of them or anyone for whose acts any of them may be liable during the performance of this Agreement.

Contractor agrees to defend, indemnify, and hold harmless City to the fullest extent possible up to ten million dollars in damages subject to Section 8 “Limitation of Liability” of Motorola’s Terms and Conditions, specifically the Master Customer Agreement (Exhibit “C”). This Section 14 “Indemnification” provides City’s sole and exclusive remedies and Contractor’s entire liability for claims arising out of this Section 14.

15. SERVICE GUARANTEE

15.1. On-Prem CAD Equipment Guarantee . Contractor represents and guarantees that all necessary On-Prem CAD Equipment required for the On-Prem CAD will be free of defects in materials and workmanship and will operate in good working order for the term of this Agreement and optional extensions regardless of whether it is manufactured by Contractor or a third party. Contractor will repair, Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 17 of 372

and if necessary, replace any non -conforming On-Prem CAD Equipment required for the On -Prem CAD regardless of whether it is manufactured by Contractor or a third party at No Additional Cost to City.

15.2 On-Prem CAD Management Guarantee. Contractor represents and guarantees that it will take all necessary steps to fulfill the On-Prem CAD Management services, which includes but is not limited to, managing, maintaining, and operating the equipment and hardware, infrastructure, software, an d operating systems as though the City had a cloud -based CAD. Contractor will take all necessary steps to fulfill this representation and guarantee at No Additional Cost to City, including but not limited to, performing backups, upgrades, security patching, monitoring, and as otherwise specified in the On-Prem SOW.

15.3 Functional Requirements Guarantee. Contractor represents and guarantees that the On- Prem CAD will meet the RFP Matrix Response (Exhibit “B”) and functional validation scenarios in accordance with Section 6 “Product Validation” of the On-Prem SOW (Exhibit “A”).

15.4 Service Response Times and Availability. Contractor represents and guarantees that the On-Prem CAD will perform in accordance with the Service Response Times and Availability Section of this Agreement.

15.5 General Guarantee. Contractor represents and guarantees the On-Prem CAD will perform substantially in material accordance with this Agreement.

15.6 Limitation on Liability. Liability arising out of this Service Guarantee Section will be limited to two million dollars ($2,000,000), which will be adjusted annually each Agreement year, commencing on the second Agreement year, based on the 12 -month percent change in the most rece ntly published annual Consumer Price Index – West Urban (“CPI-WU”), as reported by the U.S. Bureau of Labor Statistics (the “CPI Change”) with the base month being that in which the Agreement is fully executed.

16. [RESERVED]

17. DISASTER RECOVERY
Contractor shall provide a disaster recovery (“DR”) system and services to City at No Additional Cost.

Contractor shall maintain an up -to-date DR system that is tested at least on an annual basis. DR testing should be coordinated and scheduled based on City requirements and include operating on DR system for a time sufficient to assure sustained operations in DR as defined by the City in Exhibit “A.” The DR system shall include applicable recovery time and recovery point objectives as defined in Exhibit “A.” In the event that testing identifies deficiencies, a remediation plan and schedule shall be pro vided to City that are acceptable to the City. A copy of the DR plan and services is attached hereto as Exhibit “A.”

18. MOTOROLA’S TERMS AND CONDITIONS
The Parties incorporate by reference Motorola’s Terms and Conditions, attached as Exhibit “C.” For clarity, these additional terms and conditions are subject to the Conflicting Terms Section and Order of Precedence Section of this Agreement.

19. INSURANCE
Contractor will obtain and maintain for the duration of the Agreement and any and all amendments, insurance against claims for injuries to persons or damage to property which may arise out of or in connection with performance of the services by Contractor or Contractor’s agents, representatives, or Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 18 of 372

employees or subcontractors. The insurance will be obtained from an insurance carrier admitted and authorized to do business in the State of California. The insurance carrier is required to have a current Best's Key Rating of not less than "A-:VII"; OR with a surplus line insurer on the State of California’s List of Approved Surplus Line Insurers (LASLI) with a rating in the latest Best’s Key Rating Guide of at least “A:X”; OR an alien non-admitted insurer listed by the National Association of Insurance Commissioners (NAIC) latest quarterly listings report.

19.1 Coverages and Limits. Contractor will maintain the types of coverages and limits indicated below, unless Risk Manager or City Manager approves a lower amount. These amounts of coverage will not constitute any limitations or cap on Contractor's indemnification obligations under this Agreement. City, its officers, agents and employees make no representation that the limits of the insurance specified to be carried by Contractor pursuant to this Agreement are adequate to protect Contractor. If Contractor believes that any required insurance coverage is inadequate, Contractor will obtain such additional insurance coverage, as Contractor deems adequate, at Contractor's sole expense.

19.1.1 Commercial General Liability (CGL) Insurance. Insurance written on an “occurrence” basis, including personal & advertising injury, with limits of $2,000,000 per occurrence and $4,000,000 aggregate. If a general aggregate limit applies, either the general aggregate limit shall apply separately to this project/location or the general aggregate limit shall be twice the required occurrence limit.

19.1.2 Automobile Liability. (if the use of an automobile is involved for Contractor's work for City). $2,000,000 combined single-limit per accident for bodily injury and property damage.

19.1.3 Workers' Compensation and Employer's Liability. Workers' Compensation limits as required by the California Labor Code and Employer’s Liability of $1,000,000 per accident, disease, and policy limit. Workers' Compensation will not be required if Contractor has no employees and provides, to City's satisfaction, a declaration stating this.

19.1.4 Cyber/Professional Liability. Errors and omissions and cyber liability appropriate to Contractor’s profession with limits of $5,000,000 per claim and $10,000,000 per policy period. Coverage must be maintained for a period of three (3) years following the date of completion of the work.

19.2 Additional Provisions. Contractor will ensure that the policies of insurance required under this Agreement contain, or are endorsed to contain, the following provisions:

19.2.1 The City will be included as an additional insured on Commercial General Liability which shall provide primary coverage to the City.

19.2.2 Contractor will obtain occurrence coverage, excluding Cyber/Professional Liability, which will be written as claims-made coverage.

19.2.3 This insurance will be in force during the life of the Agreement and any extensions of it and will not be canceled without thirty (30) days prior written notice to City sent by certified mail pursuant to the Notice provisions of this Agreement.

19.3 Providing Certificates of Insurance and Endorsements. Prior to City's execution of this Agreement, Contractor will furnish certificates of insurance and endorsements to City.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 19 of 372

19.4 Failure to Maintain Coverage. If Contractor fails to maintain any of these insurance coverages, then City will have the option to declare Contractor in breach.

19.5 Submission of Insurance Policies. City reserves the right, with fifteen (15) days written notice, to require, at any time, certificates of insurance and endorsements of any or all required insurance policies and endorsements.

20. BUSINESS LICENSE
Contractor will obtain and maintain a City of Carlsbad Business License for the term of the Agreement, as may be amended from time-to-time.

21. ACCOUNTING RECORDS
Contractor will maintain complete and accurate records with respect to costs incurred under this Agreement. All records will be clearly identifiable. Contractor will allow a representative of City during normal business hours to examine, audit, and make transcripts or copies of records and any other documents created pursuant to this Agreement. Contractor will allow inspection of all work, data, documents, proceedings, and activities related to the Agreement for a period of four (4) years from the date of final payment under this Agreement. Under no circumstances will Contractor be required to create or maintain documents not kept in the ordinary course of Contractor ’s business operations, but Contractor shall comply with California Government Code § 8546.7. Contractor will not be required to disclose any information, which it considers confidential or proprietary to Contractor; provided, however, this section will not be construed to limit the City’s disclosure of government records subject to the California Public Records Act ( California Government Code § 6250 et seq.) and California Civil Discovery Act (California Code of Civil Procedure § 2016.010 et seq.).

22. OWNERSHIP OF DOCUMENTS
All work product produced by Contractor or its agents, employees, and subcontractors pursuant to this Agreement is the property of City. In the event this Agreement is terminated, all work product produced by Contractor or its agents, employees and subcontractors pursuant to this Agreement will be delivered at once to City. Contractor will have the right to make one (1) copy of the work product for Contractor’s records.

23. COPYRIGHTS
Contractor agrees that all copyrights that arise from the services will be vested in City and Contractor relinquishes all claims to the copyrights in favor of City.

24. NOTICES
The name of the persons who are authorized to give written notice or to receive written notice on behalf of City and on behalf of Contractor under this Agreement are:

For City: For Contractor:

Name IT Director Name Ken Nordholm
Title IT Director Title Senior Account Manager
Dept IT Department Address 10680 Treena St, Suite 200
CITY OF CARLSBAD San Diego, 92131
Address 1635 Faraday Ave Phone (858) 414-6647
Carlsbad, CA 92008 Email [email protected] Phone (442) 339-2454
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 20 of 372
City Attorney Approved Version 5/22/2024

Each party will notify the other immediately of any changes of address that would require any notice or delivery to be directed to another address.

25. CONFLICT OF INTEREST
Contractor shall file a Conflict of Interest Statement with the City Clerk in accordance with the requirements of the City of Carlsbad Conflict of Interest Code. The Contractor shall report investments or interests as required in the City of Carlsbad Conflict of Interest Code.

Yes ☐ No ☒
If yes, list the contact information below for all individuals required to file:

Name Email Phone Number

26. GENERAL COMPLIANCE WITH LAWS
Contractor will keep fully informed of federal, state and local laws and ordinances and regulations which in any manner affect those employed by Contractor, or in any way affect the performance of the Services by Contractor. Contractor will at all times observe and comply with these laws, ordinances, and regulations and will be responsible for the compliance of Contractor's services with all applicable laws, ordinances and regulations.

Contractor will be aware of the requirements of the Immigration Reform and Control Act of 1986 and will comply with those requirements, including, but not limited to, verifying the eligibility for employment of all agents, employees, subcontractors and consultants whose services are required by this Agreement.

27. CALIFORNIA AIR RESOURCES BOARD (CARB) ADVANCED CLEAN FLEETS REGULATIONS Contractor’s vehicles with a gross vehicle weight rating greater than 8,500 lbs. and light -duty package delivery vehicles operated in California may be subject to the California Air Resources Board (CARB) Advanced Clean Fleets regulations. Such vehicles ma y therefore be subject to requirements to reduce emissions of air pollutants. For more information, please visit the CARB Advanced Clean Fleets webpage at https://ww2.arb.ca.gov/our-work/programs/advanced-clean-fleets.

28. DISCRIMINATION AND HARASSMENT PROHIBITED
Contractor will comply with all applicable local, state and federal laws and regulations prohibiting discrimination and harassment.

29. MEDIATION
If the parties mutually agree, they may attempt to resolve disputes arising from this Agreement through mediation; provided, however, that such participation is fully voluntary. Neither party is obligated to participate in mediation or any other alternative dispute resolution process for any reason. If the parties mutually agree to mediate, each party will bear its own costs of mediation, but the parties may share the cost of the mediator equally. Each Party will participate in the mediation in good faith. Mediation will take place virtually or in northern San Diego County, California . All mediation communications will be Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 21 of 372
City Attorney Approved Version 5/22/2024

maintained in strict confidence by the parties unless disclosure is necessary to enforce a mediation settlement agreement.

30. TERMINATION

30.1 Termination for Breach. In the event of the Contractor's failure to prosecute, deliver, or perform the Services, City may terminate this Agreement for nonperformance by tendering thirty (30) days’ written notice by certified mail to Contractor with an opportunity to cure within such notice period.

Contractor will be paid for work performed up to the termination date without any further payment obligations or liability under this Agreement. City will make the final determination as to the portions of tasks completed and the compensation to be made.

Contractor may only terminate this Agreement for City’s breach by tendering thirty (30) days’ written notice by certified mail with an opportunity to cure within such notice period. Contractor will be paid for work performed to the termination date; however, the total will not exceed the lump sum fee payable under this Agreement. City will make the final determination as to the portions of tasks completed and the compensation to be made.

30.2 Termination for Convenience . City may terminate this Agreement for convenience by providing sixty (60) days’ written notice to Contractor. City will pay Contractor for products delivered or services satisfactorily performed up to the termination date, but City shall not be responsible for any other payment obligations under this Agreement . City will make the final determination as to the portions of tasks completed and the compensation to be made.

30.2.1 Request for Proposals (“RFP”). For clarity, City retains the right to issue a RFP or otherwise acquire a different CAD system at any time during this Agreement. As such, City may terminate this Agreement and enter into a new agreement with another vendor/contractor without (i) constituting a breach of this Agreement, (ii) incurring liability for breach, and (iii) responsibility for payment obligations beyond products delivered or services satisfactorily performed up to the termination date.

30.3 Other Termination Terms.

30.3.1 Copy of City Data . Upon termination, City has thirty (30) days to download City Data or may request a quotation to engage Contractor to provide such services (“Data Copy Period”) .

During the Data Copy Period, Contractor shall not destroy City Data. City shall notify contractor in writing when it has completed the downloading process and has a full validated copy of City Data (“Data Copy Completion”).

30.3.2 Destruction of City Data . Upon City’s notification of Data Copy Completion , Contractor will destroy all City Data. Contractor will certify in writing that all City Data has been destroyed upon City’s request.

30.3.3 No Additional Cost Items . For clarity, upon termination for any reason, City will not be liable for payment related to any service, hardware, or equipment provided at No Additional Cost.

31. STATUTE OF LIMITATIONS
City will not be subject to any shortened statute of limitation s period for any claim or cause of action arising out of this Agreement.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 22 of 372
City Attorney Approved Version 5/22/2024

32. COVENANTS AGAINST CONTINGENT FEES
Contractor warrants that Contractor has not employed or retained any company or person, other than a bona fide employee working for Contractor, to solicit or secure this Agreement, and that Contractor has not paid or agreed to pay any company or person, other than a bona fide employee, any fee, commission, percentage, brokerage fee, gift, or any other consideration contingent upon, or resulting from, the award or making of this Agreement. For breach or violation of this warranty, City will have the right to annul this Agreement without liability, or, in its discretion, to deduct from the Agreement price or consideration, or otherwise recover, the full amount of the fee, commission, percentage, brokerage fees, gift, or contingent fee.

33. CLAIMS AND LAWSUITS
By signing this Agreement, Contractor agrees that any Agreement claim submitted to City must be asserted as part of the Agreement process as set forth in this Agreement and not in anticipation of litigation or in conjunction with litigation. Contractor ack nowledges that if a false claim is submitted to City, it may be considered fraud and Contractor may be subject to criminal prosecution. Contractor acknowledges that California Government Code sections 12650 et seq., the False Claims Act applies to this Agreement and, provides for civil penalties where a person knowingly submits a false claim to a public entity. These provisions include false claims made with deliberate ignorance of the false information or in reckless disregard of the truth or falsity of information. If City seeks to recover penalties pursuant to the False Claims Act, it is entitled to recover its litigation costs, including attorneys fees. Contractor acknowledges that the filing of a false claim may subject Contractor to an administrative debarment proceeding as the result of which Contractor may be prevented to act as a Contractor on any public work or improvement for a period of up to five (5) years. Contractor acknowledges debarment by another jurisdiction is grounds for City to terminate this Agreement.

34. JURISDICTION AND VENUE
This Agreement shall be interpreted in accordance with the laws of the State of California regardless of conflict of laws principles. Any action at law or in equity brought by either of the parties for the purpose of enforcing a right or rights provided for by this Agreement will be tried in a court of competent jurisdiction in the County of San Diego, State of California, and the parties waive all provisions of law providing for a change of venue in these proceedings to any other county.

35. SUCCESSORS AND ASSIGNS
It is mutually understood and agreed that this Agreement will be binding upon City and Contractor and their respective successors. Neither this Agreement nor any part of it nor any monies due or to become due under it may be assigned by Contractor without the prior consent of City, which shall not be unreasonably wi thheld; provided, however, the Agreement terms , conditions, and services rendered remain unchanged.

36. THIRD PARTY RIGHTS
Nothing in this Agreement should be construed to give any rights or benefits to any party other than the City and Contractor.

37. CONFLICTING TERMS
To the extent any terms, conditions, or definitions of any amendment, exhibit, or attachment to this Agreement conflict or are inconsistent, in whole or in part, with the terms, conditions, or definitions of this Agreement, the terms of this Agreement control.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 23 of 372
City Attorney Approved Version 5/22/2024

38. ORDER OF PRECEDENCE
In the event of any conflict, ambiguity, or inconsistency between the documents, the following order of precedence shall take place: the terms of this Agreement, On-Prem SOW , RFP Matrix Response, and Motorola’s Terms and Conditions, in that order, shall control and prevail.

39. SURVIVAL
Regardless of the circumstances of termination or expiration of th is Agreement, or portion thereof, the provisions of Section 14 “Indemnification,” Section 15 “Service Guarantee,” Section 30.3.1 “Copy of City Data,” 30.3.2 “Destruction of City Data,” Section 31 “Statute of Limitations,” Section 34 “Jurisdiction and Venue,” Section 37 “Conflicting Terms,” Section 38 “Order of Precedence,” and Contractor’s Data Security Obligations under this Agreement as well as Section 8 “Limitation of Liability” and Section 9 “Confidentiality” of Motorola’s Terms and Conditions, specifical ly the Master Customer Agreement (Exhibit “C”) will survive the termination or expiration and continue according to their terms.

40. ENTIRE AGREEMENT
This Agreement, together with any other written document referred to or contemplated by it, along with the purchase order for this Agreement and its provisions, embody the entire Agreement and understanding between the parties relating to the subject matter of it. In case of conflict, the terms of the Agreement supersede the purchase order. Neither this Agreement nor any of its provisions may be amended, modified, waived or discharged except in a writing signed by both parties. This Agreement may be executed in counterparts.

41. SEVERABILITY
If any provision of this Agreement is invalid, illegal, or unenforceable, such invalidity, illegality, or unenforceability will not affect any other term or provision of this Agreement or invalidate or render unenforceable such term or provision.

///

///

///

///

///

///

///

///

///

///

///

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 24 of 372
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A

42. AUTHORITY
The individuals executing this Agreement and the instruments referenced in it on behalf of Contractor each represent and warrant that they have the legal power, right and actual authority to bind Contractor to the terms and conditions of this Agreement.

Executed by Contractor this d~ih

CONTRACTOR
day of ~l,Uvtµ , 2025.

CITY OF C{ LSBAD, a municipal corporation of
the State of California Motorola Solutions, Inc.
a Delaware corporation
By:
(sign here)
Jerry Burch MSSSI vice President
(print name/title)
By:
(sign here)
Ryan Christensen Assistant secretary
(print name/title)
By:

City Manager
ATTEST:

SHERRY FREISINGER, City Clerk
If required by City, proper notarial acknowledgment of execution by contractor must be attached. !f..E. corporation. Agreement must be signed by one corporate officer from each of the following two groups.

Group A
Chairman,
President, or
Vice-President
Group B
Secretary,
Assistant Secretary,
CFO or Assistant Treasurer
Otherwise, the corporation must attach a resolution certified by the secretary or assistant secretary under corporate seal empowering the officer(s) signing to bind the corporation .

APPROVED AS TO FORM:

CINDIE K. McMAHON, City Attorney
BY: 4,tA~Jj tw,/4,
Deputy City Atorney
City Attorney Approved Version 5/22/2024

The City of Carlsbad, CA
Exhibit A
Statement of Work for Motorola PremierOne
On-Premises Computer Aided Dispatch (CAD) System

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 26 of 372
The City of Carlsbad, CA
Exhibit A

Table of Contents
Section 1 .....................................................................................................................................................................5 Solution Description................................................................................................................. 5

1.1 SOLUTION DESCRIPTION INTRODUCTION ................................ ................................ ....... 5

1.2 COMPLETE SOLUTION OVERVIEW ................................ ................................ ................... 5

1.3 BASIS FOR SYSTEM SIZING ................................ ................................ ............................... 6

1.4 APPLICATION SOFTWARE AND SYSTEM COMPONENTS ................................ ............... 6

1.4.1 On-premise CAD Subsystem ................................................................................................................... 6

1.4.2 CommandCentral Components ................................................................................................................ 7

1.5 SOLUTION OVERVIEW ................................ ................................ ................................ ........ 7

1.5.1 System Application Client Software Subscriptions ................................................................................... 8

1.5.2 PremierOne CAD Capabilities .................................................................................................................. 8

1.5.3 Disaster Recovery - CAD Continuity Summary ...................................................................................... 10

1.5.4 PremierOne CAD Interface Strategy ...................................................................................................... 14

1.5.5 PremierOne Mobile Solution Description ............................................................................................... 15

1.5.6 PremierOne Reporting Services............................................................................................................. 16

1.5.7 Geographic Information System (GIS) ................................................................................................... 17

1.5.8 ActiveEye Managed Detection and Response for PremierOne ............................................................. 17

1.6 PREMIERONE INTERFACES ................................ ................................ ............................. 20

1.7 PREMIERONE INTEGRATIONS ................................ ................................ ......................... 20

1.7.1 PremierOne Integration – Astro Radio Push-to-Talk (PTT) ................................................................... 20

1.7.2 PremierOne Integration - Vigilant ........................................................................................................... 20

1.7.3 PremierOne Integration - VESTA ........................................................................................................... 20

1.7.4 RapidSOS Integration ............................................................................................................................ 21

1.8 COMMANDCENTRAL AWARE SOLUTION DESCRIPTION ................................ .............. 22

1.8.1 CommandCentral Overview ................................................................................................................... 22

1.8.2 CommandCentral Aware Features and Integrations .............................................................................. 22

1.9 COMMANDCENTRAL INVESTIGATEPLUS................................ ................................ ....... 26

1.10 COMMANDCENTRAL COMMUNITY ................................ ................................ .................. 27

1.11 CJIS AND COMPLIANCE ................................ ................................ ................................ ... 28 Section 2 .................................................................................................................................................................. 29 Statement of Work Overview ................................................................................................. 29

2.1 STATEMENT OF WORK OVERVIEW................................ ................................ ................. 29

2.1.1 Award, Administration and Project Initiation ........................................................................................... 29

2.1.2 Project Management Definitions ............................................................................................................ 29

2.1.3 Project Management Plan ...................................................................................................................... 30

2.1.4 Project Status ......................................................................................................................................... 30

2.1.5 General Customer Responsibilities ........................................................................................................ 38

2.2 PROJECT ROLES AND RESPONSIBILITIES ................................ ................................ .... 39

2.2.1 Motorola Project Roles and Responsibilities Overview .......................................................................... 39 Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 27 of 372
The City of Carlsbad, CA
Exhibit A

2.2.2 Customer Roles and Responsibilities..................................................................................................... 41

2.3 PROJECT INITIATION AND PLANNING ................................ ................................ ............ 44

2.3.1 Project Planning Session - Teleconference/Web Meeting ..................................................................... 44

2.3.2 Project Kickoff Session - Teleconference/Web Meeting ........................................................................ 46

2.3.3 GIS Planning Session - Teleconference/Web Meeting .......................................................................... 46

2.3.4 Interface Planning Sessions - Teleconference/Web Meetings .............................................................. 47

2.3.5 Connectivity Planning Session - Teleconference/Web Meeting ............................................................ 48

2.4 PREMIERONE SERVICES PROJECT EXECUTION ................................ .......................... 49

2.4.1 PremierOne Hardware and Environment ............................................................................................... 49

2.4.2 Cybersecurity Services (Managed Detection and Response) ............................................................... 51

2.4.3 PremierOne Business Process Review (BPR) ....................................................................................... 53

2.4.4 PremierOne GIS ..................................................................................................................................... 55

2.4.5 Provisioning ............................................................................................................................................ 58

2.4.6 CAD Client Installation ........................................................................................................................... 61

2.4.7 Functional Validation .............................................................................................................................. 63

2.5 PREMIERONE REPORTING ................................ ................................ .............................. 64

2.6 INTERFACE AND INTEGRATION DELIVERY ................................ ................................ ... 65

2.7 INTERFACE DEPLOYMENT ................................ ................................ .............................. 65

2.7.1 Interface Validation ................................................................................................................................. 66

2.8 PREMIERONE AND COMMANDCENTRAL TRAINING AND CONSULTATIVE SERVICES ................................ ................................ ................................ ................................ ............ 67

2.8.1 Training ................................................................................................................................................... 67

2.8.2 CommandCentral Aware and Community Professional Consulting Services ........................................ 68

2.8.3 CommandCentral Investigate Professional Consulting Services ........................................................... 68

2.9 PREMIERONE CAD AND COMMANDCENTRAL GO LIVE ................................ ............... 69

2.9.1 PremierOne Go Live Planning ................................................................................................................ 70

2.9.2 Motorola Support Engagement .............................................................................................................. 70

2.9.3 CommandCentral Aware and Community Production Use .................................................................... 71

2.9.4 CommandCentral Investigate Production Use ....................................................................................... 71

2.9.5 PremierOne Go Live Event .................................................................................................................... 71

2.9.6 Ninety (90) Day Reliability Period and Final System Acceptance .......................................................... 72

2.10 PROJECT CLOSURE ................................ ................................ ................................ ......... 72

2.10.1 Transition to Support .............................................................................................................................. 72

2.11 Appendix A - PremierOne CAD File Build ................................ ................................ ........ 72

2.11.1 Incident Types ........................................................................................................................................ 72

2.12 Appendix B - PremierOne CAD/Mobile Standard Reports ................................ .............. 74 Section 3 .................................................................................................................................................................. 79 Cost Summary ........................................................................................................................ 79

3.1 Pricing Summary ................................ ................................ ................................ ............... 79

3.2 Detail Pricing................................ ................................ ................................ ...................... 80 Section 4 .................................................................................................................................................................. 81 Payment Schedule .................................................................................................................. 81 Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 28 of 372
The City of Carlsbad, CA
Exhibit A

4.1 One-time Payment Milestones ................................ ................................ .......................... 81 Section 5 .................................................................................................................................................................. 83 Project Schedule and Personnel ........................................................................................... 83

5.1 Project Schedule ................................ ................................ ................................ ............... 83

5.2 Project Team Organization Chart ................................ ................................ ..................... 89 Section 6 .................................................................................................................................................................. 90 Product Validation .................................................................................................................. 90

6.1 PRODUCT VALIDATION PURPOSE ................................ ................................ .................. 90

6.2 VERIFICATION PROCESS OVERVIEW ................................ ................................ ............. 90

6.3 VALIDATION PROCESS ACTIVITIES ................................ ................................ ................ 90

6.3.1 Prepare Functional Validation Plan ........................................................................................................ 90

6.3.2 Prepare Interface Validation Plan........................................................................................................... 91

6.3.3 Validation Plan Approval ........................................................................................................................ 91

6.3.4 Validation Execution ............................................................................................................................... 91

6.3.5 Validation Failures .................................................................................................................................. 91

6.4 SAMPLE FUNCTIONAL VALIDATION WORKBOOK ................................ ........................ 92 Section 7 .................................................................................................................................................................. 93 Hardware, Network, and Environmental Specification ........................................................ 93

7.1 Solution Equipment ................................ ................................ ................................ ........... 93

7.1.1 System Equipment Requirements .......................................................................................................... 93

7.2 Component Specifications ................................ ................................ ................................ 95

7.2.1 Network and Other Environment Specifications ..................................................................................... 97

7.2.2 CommandCentral Network Connection Requirements .......................................................................... 98

7.2.3 Mobile and Handheld Cellular Network Requirements .......................................................................... 98

7.2.4 Aware Network and Bandwidth Requirements ....................................................................................... 98

7.2.5 Vigilant LPR Requirements .................................................................................................................... 99

7.2.6 ASTRO 25 Radio and Infrastructure Requirements ............................................................................... 99

7.2.7 Equipment Server Rack Specifications ................................................................................................ 100 Section 8 ................................................................................................................................................................ 102 PremierOne Interface Functional Descriptions (IFDs)....................................................... 102

8.1 Summary of Interfaces ................................ ................................ ................................ .... 102

8.2 IFDs vs ISDs ................................ ................................ ................................ ..................... 103

8.3 Priority of Query Returns ................................ ................................ ................................ 104

8.4 Query responses ................................ ................................ ................................ ............. 105

8.5 Interface Functional Descriptions ................................ ................................ .................. 106

8.5.1 Axon Interface ...................................................................................................................................... 106

8.5.2 CLETS/NCIC Queries from CAD (State Query) ................................................................................... 107

8.5.3 NetRMS Data Feed from CAD ............................................................................................................. 110

8.5.4 Niche RMS Data Feed from CAD......................................................................................................... 112

8.5.5 Niche RMS Queries .............................................................................................................................. 113

8.5.6 SpidrTech Data Feed ........................................................................................................................... 116 Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 29 of 372
The City of Carlsbad, CA
Exhibit A

8.5.7 Stored Procedure Queries- Crossroads Citation Queries, Crossroads Traffic Accident Queries, Legacy Queries, NetRMS Queries from CAD ................................................................................................... 117 Section 9 ................................................................................................................................................................ 120 PremierOne Training Plan .................................................................................................... 120

9.1 OVERVIEW ................................ ................................ ................................ ....................... 120

9.2 CUSTOMER TRAINING ROLES ................................ ................................ ....................... 120

9.2.1 Customer Training Representative....................................................................................................... 120

9.2.2 Learning Management Administrator ................................................................................................... 120

9.2.3 Customer Training Attendees ............................................................................................................... 120

9.3 PREMIERONE TRAINING PLAN SCOPE ................................ ................................ ........ 121

9.3.1 PremierOne CAD.................................................................................................................................. 121

9.3.2 PremierOne Mobile .............................................................................................................................. 121

9.3.3 CommandCentral Aware ...................................................................................................................... 122

9.3.4 CommandCentral Investigate End User ............................................................................................... 122

9.3.5 CommandCentral Community Digital Evidence Collection .................................................................. 122

9.4 PREMIERONE TRAINING GENERAL INFORMATION ................................ .................... 122

9.4.1 Training Courses .................................................................................................................................. 122

9.4.2 Training Facilities and Schedules......................................................................................................... 122

9.4.3 Training Methods and Procedures ....................................................................................................... 123

9.4.4 Training Environment ........................................................................................................................... 123

9.4.5 Session Attendance ............................................................................................................................. 123

9.4.6 Learning experience Portal (LXP) Requirements ................................................................................. 124

9.4.7 LXP Learner Subscription Package ..................................................................................................... 124

9.5 PREMIERONE COURSE DETAILS ................................ ................................ .................. 124

9.5.1 Training Course Classifications ............................................................................................................ 124

9.5.2 Training Course Descriptions ............................................................................................................... 126 Section 10 .............................................................................................................................................................. 139 Maintenance and Support Agreement ................................................................................ 139

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 30 of 372
The City of Carlsbad, CA

Section 1
Solution Description

1.1 SOLUTION DESCRIPTION INTRODUCTION
This Agreement’s purpose is to move the City of Carlsbad’s Computer Aided Dispatch system, interfaces, and directly associated software from the originally contracted Cloud-Based Solution (PremierOne Cloud CAD) to an on-premise solution (PremierOne CAD) delivered as a service and to keep the costs of the on-premise solution for the implementation period and the first 6 years of support equal to the originally contracted costs of a cloud-based solution. CommandCentral Aware and CommandCentral Investigate Plus (formerly CommandCentral Analytics Plus) remain cloud-based solutions.

Motorola will provide all hardware, equipment and software necessary (included but not limited to equipment, hardware, and software specified in Sections 7.1 and 7.3) to implement an on-premise system and will support and maintain all said Motorola provided hardware and software. The goal of this support model is to mimic a cloud-based solution in which Carlsbad would have had very minimal support responsibilities. Accordingly, Motorola agrees to be exclusively responsible for managing, maintaining, and operating the equipment and hardware, infrastructure, software, and operating systems as a whole such that, in effect, the City has a cloud-based system, but through an on-premises solution (“On-Prem CAD”). To effectuate the intent of the parties, Motorola agrees to take all necessary steps to ensure the On-Prem CAD, in effect is like a cloud-based solution at no additional cost for the Agreement term and optional extensions; Contractor’s responsibilities also include, but are not limited to, performing backups, upgrades, security patching and monitoring and as otherwise specified in this Exhibit “A” (“On-Prem CAD Management”).

Due to the extensive nature of the contractual changes required, this new Scope of Work is provided.

We have listened to the immediate, as well as future needs you have described to us over the past several months. We want to be "all in" with the City of Carlsbad and the building block strategy to achieve your vision. Our offer to you includes not only the required RFP blocks, but also the Real Time Crime Center platform, built on Motorola CommandCentral Aware, for 175 named users. And because your first responders have spoken loud and clear, our offer also includes the Legacy Query Interface, PremierOne CAD Radio Push to Talk (“PTT”) Interface, CommandCentral Investigate Plus, and CommandCentral Community. Each of these represents a vital building block in your pursuit for a safer community through better outcomes driven by smart technology.

The City of Carlsbad is making an investment in technology, but most importantly, you have a vision of building the future with a long-term partner. It is this attitude that has captured our attention, our desire, and our financial investment to share your vision and propel Carlsbad to stand out as a Lighthouse and showcase for agencies and cities across North America.

1.2 COMPLETE SOLUTION OVERVIEW
Motorola Solutions’ PremierOne CAD and PremierOne Mobile and CommandCentral Aware provide actionable intelligence to inform decisions, recognize trends, and gain mission critical insights to improve operations. With PremierOne and CommandCentral, your users will be able to reliably share information across dispatch, field, and crime center workflows to connect teams, increase situational Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 31 of 372
The City of Carlsbad, CA

awareness, and improve incident outcomes.

This unified platform reduces the complexity
of data capture, communication, and
management, enabling your personnel to
focus on what matters most-- their mission.

PremierOne CAD and CommandCentral
Aware are the convergence points that
centralizes communications and incident
data, enabling personnel to quickly access
incoming calls, related records, and
responder location and status. Dispatch
delivers this critical intelligence to
PremierOne Mobile users, supporting first responders in the field. CommandCentral Aware combines disparate systems and data into an accessible interface. This single interface offers command centers a complete operating picture to support field personnel in real time. CommandCentral Aware unifies data from mapping, correlated event monitoring, analytics, and communications. This unified interface streamlines public safety workflows and viewpoints, enabling users to access and act on critical information.

1.3 BASIS FOR SYSTEM SIZING
• Up to 500,000 CAD Calls for Service per year
• Up to 100 PremierOne CAD clients
• Up to 250 PremierOne Mobile clients

1.4 APPLICATION SOFTWARE AND SYSTEM

COMPONENTS
The solution consists of the following component and subsystem elements:

1.4.1 On-premise CAD Subsystem
• PremierOne CAD with Automatic Resource Location (ARL) • PremierOne Integrations
- Vesta 9-1-1/TDD
- Vigilant ALPR
- ASTRO APX Radio Push-to-Talk (PTT)
- RapidSOS
• PremierOne Interfaces
- NetRMS Calls for Service Data Feed
- NetRMS Query
- SPIDR Tech Calls for Service Data Feed
- Axon Calls for Service Data Feed
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 32 of 372
The City of Carlsbad, CA

- CLETS/NCIC State Query
- Crossroads Accidents Query
- Crossroads Citations Query
- Legacy Data Query
- Niche RMS Calls for Service Data Feed
- Niche RMS Query
• PremierOne Mobile (Windows, iOS, Android) with Mobile Mapping • SSRS Reporting

1.4.2 CommandCentral Components
• CommandCentral Aware - Real Time Crime Center
• CommandCentral Aware Integrations
- PremierOne CAD Integration for incident and unit location - Vigilant License Plate Recognition Integration
- VESTA 9-1-1 Call Location Integration
- ASTRO P25 Radio Location on Push-To-Talk (PTT)
- Agency Esri Data Sets
- AccuWeather Service
- In-Car Camera Video Streaming
• CommandCentral Aware Connectors:
- ONSSI VMS
- Drone Interface*
- DW Spectrum Traffic Cameras
• CommandCentral Investigate Plus
• CommandCentral Community Integration/Interfaces
- PremierOne CAD Incidents
- Niche Records Data Feed
*CAD Integration Processor: The City of Carlsbad Police Department is currently using ALOFT for its drone software and is currently assessing the use of the Motorola CAPE software. An interface for the Drone software will be implemented, and if the CAPE software is implemented after an interface to ALOFT has been developed, the CAPE interface will be provided at no extra charge.

The following solution descriptions outline the unique benefits of PremierOne CAD and Mobile to empower your users with a proven public safety platform.

1.5 SOLUTION OVERVIEW
Motorola Solutions’ PremierOne Computer-Aided Dispatch (CAD) is an easy-to-use solution that streamlines intelligence capture and dispatch to help keep first responders and their communities informed and safe. As a convergence point that centralizes communications and incident data, PremierOne CAD enables personnel to quickly access incoming calls, related records, and responder Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 33 of 372
The City of Carlsbad, CA

location and status. The PremierOne CAD workstation displays this information as actionable intelligence, providing dispatchers with a more complete operating picture to enable them to efficiently allocate resources, more quickly inform field personnel, and manage incidents as they evolve.

1.5.1 System Application Client Software Subscriptions
Table 1-1: System Subscriptions
System Client Licenses Quantity Type
PremierOne CAD Dispatch Clients with Mapping and CAD Web Client
50 Subscription
PremierOne Mobile Clients (Windows) 175 Subscription
PremierOne Mobile Clients and CommandCentral Responder for CAD (when available)(Android/iOS)
175 Subscription
CommandCentral Aware (Named Users) 175 Subscription
CommandCentral Community Unlimited Users Subscription
CommandCentral Investigate Plus 115 Subscription

1.5.2 PremierOne CAD Capabilities
Motorola Solutions has designed PremierOne CAD to be the central convergence point for communications from multiple sources and systems, mission-critical information, and resource management.

The user interface offers quick access to information via a location-based, Esri-standard GIS map.

Users perform commands and functions using a mouse, command lines, function keys, shortcuts, or user definable right-click menus. The GPS-aided resource management tool displays the location and identity of GPS-equipped vehicles or devices enabling a coordinated response while further supporting officer safety.

PremierOne CAD Access and Basic Operation
PremierOne CAD can be installed on any computer that meets the minimum functional requirements for operation. Users perform the majority of actions within the PremierOne CAD work monitor. Status monitors present summary information about incidents or units. A user may have one or more status monitor window(s) available at the workstation. Status monitors are configurable to meet your personnel’s specific needs.

Users may operate PremierOne CAD either with or without a mouse. While all commands and actions within the application can be accessed with the mouse, users also may drive PremierOne CAD almost exclusively from the keyboard. A few PremierOne CAD functions, such as selecting units from a map, must be performed with a mouse.

Incident and Unit Management
PremierOne CAD helps dispatchers manage multiple incidents of varying sizes and criticalities by presenting incident data via a streamlined user interface (UI). It provides quick access to dispatch functionality, summarizes at-a-glance unit and incident status, and places related information, such as unit communications, locations, and alerts, in context. This immediate access to real-time information Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 34 of 372
The City of Carlsbad, CA

enables dispatchers to quickly initiate incidents and assign units to them, as well as manage ongoing events and the resources allocated to them.

Dispatchers can initiate incidents via command line or from the incident initiation form provided within PremierOne CAD. Once the incident is initiated, units can be dispatched using one of four methods:
• Dispatch incident function key.
• Incident dispatch command.
• Dispatch form.
• Drag and drop feature within status monitors and map.

Once initiated, incidents can be managed through the various incident management features of PremierOne CAD:
• Updating existing incident information.
• Associating incidents.
• Disassociating incidents.
• Cloning incidents.
• Closing incidents.
• Reopening incidents.
• Displaying a summary list of incidents.
• Searching for incidents.
• Pre-assigning or pre-empting incidents to units with the Call Stacking feature. • Viewing records of all transactions associated with an incident with the audit feature.

Dispatchers can monitor units and manage their assignments through the PremierOne CAD interface, via the following unit management functionality:
• View and update unit assignment data.
• Make unit status changes.
• View a unit’s history.
• View the current activities for a unit.
• Clear units from an incident.
• Manipulate units that are assigned to incidents.
• Place a group of units on or off duty via a single transaction with Roll Call, allowing users to update shift assignments for on duty units without the need to first take these units off duty.

PremierOne CAD can also change a unit’s capabilities based on the personnel assigned to that unit.

Manual incident notifications feature is a process by which PremierOne CAD informs users that they are to manually notify individuals who are not a part of PremierOne CAD, and helps to prevent multiple notification recipients from contacting an individual simultaneously.

Incident Mapping and Automatic Resource Location
In addition to the information described above, dispatchers can view incident and resource location data directly within PremierOne CAD via a consolidated, Esri standard GIS map. This centralized map display is integrated directly into PremierOne CAD, providing geographic context to real-time incident Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 35 of 372
The City of Carlsbad, CA

information. Specific mapping functions built into PremierOne CAD allow dispatchers to manipulate the map and configure the display with icons to help target incident response.

Also, PremierOne CAD uses Automatic Resource Location (ARL) to determine the actual location of emergency vehicles in relation to an emerging incident. This enables PremierOne CAD to make response recommendations based on the location of units rather than based solely on jurisdictional assignment. Once resources are assigned to an incident, PremierOne CAD’s ARL capability tracks those resources as they are on route to an incident.

Mail and Messaging Services
PremierOne CAD’s mail and user-to-user messaging functionalities allow users to exchange and distribute email and instant messages (IM) within the dispatch center and to units equipped with Mobile Data Terminals (MDT). PremierOne CAD also supports recurring messages, BOLO (Be on the Look Out) messages, notification message capability, message prioritization, targeted distribution list, and management of the mail-messaging functionality.

When using these messaging services, users can search through the PremierOne CAD address book to find contacts. PremierOne CAD includes a global address book and the ability to create both shared address books and user-specific personal address books.

System Security and Roles
PremierOne CAD is designed to ensure operational and data security. Each user and device on the system is assigned to one or more agency-created roles. PremierOne CAD recognizes these users and devices, and provides access to their authorized functions based on their assigned role. This controlled access enables the enforcement of access rights and permissions, ensuring that the right users are interacting with the necessary functions for their role. Personnel can also be searched by their skills.

Additional Capabilities
The PremierOne CAD solution also supports the following capabilities:
• Address Geo-validation & Premise Hazards.
• Mapping Manual GeoFencing & Road Closure.
• Multi-Discipline, Multi-Agency Support.
• Contractor Rotation.
• Forms & Status Monitors Configuration.
• Status Backdating.
• Move-Ups.
• Query Return.
• Fire Recommendations.
• Reports.

1.5.3 Disaster Recovery - CAD Continuity Summary
The goal of disaster recovery is to resume critical CAD workflows and preserve incremental data during outages with minimum operational downtime until a full system or center recovery. To achieve that, MSI provides services that integrate into existing hybrid and CommandCentral CAD architecture and UX to:

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 36 of 372
The City of Carlsbad, CA

• Leverage the CAD Web Client as an extension to on-prem CAD system during normal operations;
• Automate setup and onboarding of needed cloud infrastructure to enable a disaster recovery solution in response to an outage;
• Facilitate needed data transfer from on-prem to cloud with minimal downtime and disruption to call taking and dispatch operations in the event of a primary CAD outage (“failover”); • Provide critical capabilities to capture, and track calls for services, unit assignments, as well and other critical dispatch duties using a simple-to-use UI; • Facilitate needed data transfer from the cloud back to on-prem (“failback”) when primary CAD recovery is complete to make the transition as painless and short as possible; and, During an outage, CommandCentral CAD becomes the primary CAD system by replacing PremierOne CAD for the duration of the outage (planned or unplanned). Upon successful PremierOne CAD recovery, the solution will revert to normal operations and again function as an extension of PremierOne CAD. System downtime associated with failover to CommandCentral CAD is not expected to exceed 30 minutes. A more precise failover downtime will be mutually explored and agreed to throughout the development process.

CommandCentral CAD Overview
CommandCentral CAD Disaster Recovery solution leverages CommandCentral CAD as its foundation.

CommandCentral CAD is a cloud-native CAD monitoring, call taking, and dispatch solution accessible by authorized users via Chrome browser. While other browsers may function with CommandCentral Cloud, Motorola tests it with Chrome browser. It is a secure application with a cloud-native backend built on the MSI Cloud Infrastructure Engineering platform in the Azure U.S government cloud. A subset of the application’s functionality is available as an extension to PremierOne CAD through the CAD Web Client, as well as a complete standalone system through CommandCentral CAD. For this program, the agency is entitled to the application available as an extension to PremierOne CAD during normal operations and as an alternate CAD during a primary CAD outage.

CommandCentral CAD Core Functionality
CommandCentral CAD provides dispatchers and other authorized personnel with the following functionality:
• Monitoring capabilities (incident and unit)
• CAD Map (incident display and display of assigned units) • Incident search capabilities
• Incident history
• Incident management capabilities
- Incident create (single/multi-discipline)
- Field initiated incident
- Unit assignment
- Add comment, persons, vehicles
- Incident close and reopen
- Request a Records/RMS ID
- Display of associated incidents
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 37 of 372
The City of Carlsbad, CA

• Unit status update, place on/off duty
• Responder location (via CommandCentral Responder for CAD) • Address verification and reverse geocoding using ESRI World Geocoder/Agency-provided data • Premise hazards
• Basic Person and Vehicle query state and national as driver license, warrant, vehicle registration, stolen vehicle
• Basic printable CAD incident and unit reports
• Basic offline capabilities
- Incident creation
- Add comments
- Unit dispatch
- Unit status change
- Incident close
- Free a unit
Monitoring
Dispatchers can monitor units and incidents from the CommandCentral CAD application. This user interface allows call-takers and dispatchers to find the resources they need, with available units sorted by “Unit ID” or by “Area” for quick access. The Unit Details window provides a view of officers assigned to a unit, the incident a unit is dispatched to, assigned areas, and any equipment or capabilities of that unit.

The application also provides an Incident Monitor that displays incident status, making critical event information accessible at a glance. Similar to Unit Details, dispatchers can double-click into incident details to see specific information related to that incident. This information includes Address, Incident Type, Description, Priority Level, and Assigned Units.

CommandCentral CAD monitoring functions include the following:
• Basic incident and unit status monitors
• Multi-monitor support
Dispatching
CommandCentral CAD provides easy access to dispatch functions using an intuitive interface.

Dispatchers can quickly create an incident from a form in the CAD application, where required fields are highlighted to speed up data entry. The system supports address verification using ESRI World Geocoder or agency-provided GIS data.

The CAD application also allows dispatchers to search incidents and history to find additional information about past events. Dispatchers can review, add, and modify details about CAD-involved People and Vehicles.

CommandCentral CAD Disaster Recovery Scope
The following sections provide a brief description of the proposed CommandCentral CAD Disaster Recovery Solution.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 38 of 372
The City of Carlsbad, CA

As a part of the solution, CUSTOMER is entitled to the following capabilities and support:
• Provide authorized users access to CAD Web Client with a PremierOne CAD backend during normal operations;
• All on-prem CAD incident data is saved to the Cloud via the CommandCentral Connector (C3) integration. Only incidents that are less than 72-hours old can be reopened or modified within the CC CAD system.
• Enablement of CommandCentral CAD services required to minimize downtime when switching from normal operations to CAD continuity mode;
• Ability to request failover over to CommandCentral CAD as a disaster recovery solution for planned or unplanned outages of PremierOne CAD;
• Provide authorized users access to CommandCentral CAD as a standalone CAD continuity solution during primary CAD outage;
• Leverage primary CAD incident and unit numbering to ensure continuity of defined numbering scheme;
• Incident and unit synchronization report to ensure consistent data synchronization from primary CAD to CommandCentral CAD during normal operations;
• Import a subset of provisioning data from primary CAD needed to provision and operate CommandCentral CAD as a standalone CAD system during a primary CAD outage; • At failback, merging of incident and unit data generated during a primary CAD outage in CommandCentral CAD into the PremierOne CAD operational database; • Incident and unit merging report to ensure consistent data merging from CommandCentral CAD to primary CAD upon failback;
Out of Scope Functionality
The following is out of scope and will not be available as a part of the proposed CAD continuity and disaster recovery via CommandCentral CAD:
• Ability to change agency code tables, incident and unit settings, and new preassigned units via CommandCentral CAD during primary CAD outage (i.e. any CAD related provisioning changes); • Ability to change or add new GIS data such as addresses or beats during the outage; • Custom development of new features in CommandCentral CAD beyond the general availability feature set;
• Any capabilities outside of call taking and dispatch workflows (e.g. records management, digital evidence management, PremierOne mobile clients (Windows devices), etc.); • Automatic failover from primary CAD to CommandCentral CAD (failover will require intentional activation, but the process once activated will be automated); • Real-time failover from primary CAD to CommandCentral CAD without downtime (system downtime associated with failover to CommandCentral CAD is not expected to exceed 30 minutes);
• Integration with any 3rd-party systems beyond basic state and national query and E911 (Requires the on-prem anchor server to remain available); • Side-by-side operation of CommandCentral CAD (standalone cloud CAD) to PremierOne CAD; • Server restoration using agency CAD data backed up to the cloud storage; Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 39 of 372
The City of Carlsbad, CA

• Hardware for training environment.

1.5.4 PremierOne CAD Interface Strategy
PremierOne CAD supports a variety of interfaces to enhance dispatch operations by integrating PremierOne CAD with the capabilities provided by other solutions. Motorola Solutions provides the interfaces noted in Section 1.4 which are licensed as part of the PremierOne solution. Interface Feature Descriptions (IFD’s) are provided below in Section 8. The IFD details the specific features and functionality of the interface, interface technical information, including data elements, and describes the implementation process and responsibilities of the involved parties.

Table 1-2: List of Integrations, Interfaces, and Connectors PremierOne CAD
NetRMS Data Feed from CAD Outbound Calls For Service Records Data Feed NetRMS Queries from CAD Query records in NetRMS based on Vehicles, Names, Locations, ETC.

SpidrTech Data Feed Outbound Calls For Service Records Data Feed Axon Data Feed for BWCs Outbound Calls For Service Records Data Feed Coplogic/DORS Inbound CAD
Incident Creates
Inbound CAD Incident Create
CLETS/NCIC Queries from CAD
(State Query)
State Query
Crossroads Traffic Accident
Queries
Query Third Party System
Crossroads Citation Queries Query Third Party System
Legacy Query Query Third Party System
Data Warehouse Feed 2nd CAD RDW
Astro APX PTT Integration (If Available from NextGen RCS) Vesta 9-1-1/TDD/TTY Integration
On premise Microsoft Entra ID
Service
Integration
CommandCentral Aware
PremierOne CAD Integration
M500 In Car Video Integration
Vigilant LPR Integration
Vesta 911 Call Location
Integration
Integration
Astro P25 Radio Location on PTT-
GPS Coordinates to CAD
Integration
Environmental Systems Research
Institute, Inc. (Esri)
Integration
OnSSI VMS/Occularis Connector
Drone Interface Connector
DW Spectrum Traffic Cameras Connector
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 40 of 372
The City of Carlsbad, CA

PremierOne CAD
New Interface/Integrations
RapidSOS Integration
Niche RMS Data Feed from CAD Calls for Service Data Feed Interface Niche RMS Queries Query Third Party System

1.5.5 PremierOne Mobile Solution Description
Overview
Motorola Solutions’ PremierOne Mobile extends command center capabilities and information from PremierOne CAD by providing enhanced mobile capabilities to officers and first responders in the field.

Public safety personnel can prepare for an incident by using the PremierOne Mobile applications to access real-time information in their vehicle or on their smart device. This mobile access to critical intelligence capabilities informs a safer and more accurate response.

The PremierOne Mobile client features quick access to the information needed by field personnel in rapidly changing situations. Designed with one-level navigation via touchscreen or keyboard, the client applications offer single-key traffic stops, one-touch status updates, and single-tap view of incident or unit details. This seamless, on-the-go experience enables users to begin incident response on a vehicle laptop and continue that response outside of the vehicle on a cellular device.

Users can access Windows, Android, and iOS clients on in-vehicle laptops, smartphones, and tablets.

Users can access the Windows client and an iOS or Android client simultaneously.

PremierOne Mobile Capabilities
PremierOne Mobile supports the following operating systems: Windows, iOS, and Android. It provides public safety personnel in the field with improved access to mission critical information. These mobile capabilities support your responders in the following areas.

Field Response - PremierOne Mobile allows users to dynamically receive incident details as emergency events unfold, and provides them with drive directions. As personnel, vehicles, and locations are associated with an incident, previous incident details are automatically made available to those individuals in real-time.

Enhanced Situational Awareness - PremierOne Mobile connects dispatchers and field responders to allow for a seamless delivery of up-to-date information to the point of engagement. Critical details and automatic notifications and alerts (“hot hits” responders, messaging, BOLOs, premise and hazard information) can easily be accessed by first responders, while geofencing and status monitoring provide additional location and activity details of all units and incidents to remain connected to developing situations and inform better decisions.

Incident Management - PremierOne Mobile provides full incident control to field personnel, enabling them to monitor, engage with, and close out an incident. Users can update event details, comments, and locations from the mobile client, scan a driver’s license to automatically search and add a subject, and easily attach photos to incidents from Android and iOS devices to create a more autonomous and productive mobile workforce.

Streamlined Operations - PremierOne Mobile features a configurable, browser-based UI and access to advanced administration capabilities, allowing users to schedule and deploy remote installations and upgrades with a client that fits your agency’s operational needs. Users can choose when to accept Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 41 of 372
The City of Carlsbad, CA

upgrades to avoid interruption of critical tasks. PremierOne Mobile also supports single client to fleet- wide, multi-agency remote deployments and silent updates.

Features Supported by Platform
The PremierOne Mobile and Handheld applications support the features outlined in the table below.

Table 1-3: High-level PremierOne Mobile Features by Client Platform PremierOne – Available Clients Windows Mobile Android
Handheld
iOS
Handheld
Operating System Windows 11 + Android 14 iOS 17
Cloud Enabled ● ● ●
Silent Dispatch ● ● ●
Incident & Unit Management ● ● ●
Real-Time Status Monitors 7 5 5
Field Initiation for Traffic Stops & Other Incidents ● ● ● Database Querying ● ● ●
BOLOs ● ● Query Only
Responder and Unit Location Tracking ● ● ●
Premise & Hazard Details with Images ● ● ●
Geofencing with Entry & Exit Alerts ● ● ●
4G & LTE Network Capability ● ● ●
CJIS Security Support with FIPS 140- 2 Encryption &
Auditing
● ● ●
Barcode Scan ● ● ●
Voice Entry for Comments ● ●
Navigation via Esri ArcGIS ● ● ●
Navigation via Apple Maps ●
Navigation via Google Maps ●
Messaging ● ●
Advanced Mapping, BOLOs, Premise & Hazards ●
Advanced Configurations ●

1.5.6 PremierOne Reporting Services
SQL Server Reporting Services (SSRS)
SQL Server Reporting Services (SSRS) provides a set of on-premises tools and services that create, deploy, and manage paginated reports. Paginated reports are ideal for fixed-layout documents optimized for printing, such as PDF and Word files. The SSRS solution flexibly delivers the right information to the right users. Users can consume the reports in a web browser on their computer or mobile device, or via email.

A standard reports library is included in the product. These reports will be loaded to the Customer system(s), and be used during the Reporting Workshops. The Workshops will provide the attendees Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 42 of 372
The City of Carlsbad, CA

with the knowledge on how to create custom reports against the PremierOne databases utilizing Microsoft’s SSRS software.

1.5.7 Geographic Information System (GIS)
Geo-spatial data is uploaded to the system through tools implemented within Esri ArcGIS. Address validation data is maintained in redundant Microsoft SQL Server geodatabases that store locations and boundaries both spatially and in optimized search tables. Esri ArcGIS Servers provide routing and ETA calculations using the Network Analyst extension. Client maps are displayed using Esri ArcGIS Engine.

The system uses GIS for display, location validation, and unit recommendation. The system’s tools made available for ArcTool box, provides the ability to load local data manually or through an automated model.
• The system’s Response Boundary Data Import Tool imports and aggregates boundaries in multiple layers into a single spatial table within the geodatabase for support of multi-agency / multi-jurisdictional scenarios. GIS data is a required key component of a system deployment.

GIS provides the mechanism for location validation and recommendation for response. • A system conformant and geographically accurate GIS data is required for the proper operation of the system. It is the Customer’s responsibility to provide a complete and accurate GIS data that conforms to the PremierOne GIS Data Requirements for use in PremierOne. Each agency being added to the system must have their geographic coverage included in the geodatabase imported into the system.
• The use of remote and/or Esri Online services is not supported. Motorola Solutions is not responsible for map availability or any degradation of client performance caused by the use of third-party hosted internet map services as these services are outside the domain of the system infrastructure and are not managed by Motorola Solutions. The system is a mission critical application that must control the import/access of the GIS data.

1.5.8 ActiveEye Managed Detection and Response for PremierOne Overview
Identifying and mitigating cyber threats requires continuous monitoring and technical capabilities to distinguish real threats from millions of alerts, as well as the expertise to quickly evaluate and remediate them if needed. With ActiveEyeSM Managed Detection and Response (MDR) for PremierOne, Motorola Solutions will provide your agency with access to the ActiveEye Security Platform, along with 24/7 support from specialized cybersecurity experts who will monitor your mission- critical computer-aided dispatch (CAD) servers and infrastructure that is managed by Motorola for indicators of threats and remediate them if needed.

The ActiveEye MDR solution can help secure your agency’s Motorola managed on-premise CAD solution through a combination of ActiveEye technology, endpoint detection, and the expertise of Motorola Solutions’ cybersecurity analysts in our Security Operations Center (SOC).

ActiveEye Security Management Platform
The ActiveEye Security Platform collects, manages, and analyzes security events. Built-in analytics examine multiple real-time threat intelligence feeds, reference past events, and follow playbooks to automate most actions. Analytics also prioritize events to quickly identify those that require remediation.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 43 of 372
The City of Carlsbad, CA

As a Security Orchestration, Automation, and Response (SOAR) platform, ActiveEye speeds up remediation, using predefined or custom playbooks to automatically investigate and respond to threats.

ActiveEye’s automatic investigation capabilities include looking up threat intelligence, querying past data, adding recommended action notes to cases, and bringing event details to the main investigation screen. Its automated response capabilities include changing alert priorities, closing alerts, blocklisting files, removing files from systems, or isolating hosts from the network.

This automated approach to threat identification and remediation eliminates more than 95 percent of false positives, allowing our SOC analysts to shift their focus to more complex investigation and response tasks.

ActiveEye Managed Security Portal
The ActiveEye Security Portal, a cloud-based web application, enables improved visibility of cybersecurity incidents to your agency and allows Motorola Solutions to coordinate responses if needed. From this central platform, your agency’s personnel will be able to view threat insights, event investigations, security reports, threat advisories, and the status of cases.

Figure 1-6: ActiveEye Interface
Dashboard
The ActiveEye dashboard provides a summary of key information. It includes a snapshot of open alerts, alert categories, key performance indicators (KPI), open cases, and recent threat advisories. Users can also see more in-depth information, such as the number of security cases, alert details, alert trends, reports, and group communications.

Security Cases
When a threat is identified, the SOC will create a security case. Through the ActiveEye Portal, your agency’s personnel will be able to view details of current or past cases, create new cases, or respond to ongoing cases strictly for informational purposes.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 44 of 372
The City of Carlsbad, CA

Alert Details and Trends
Alerts can be evidence of a past, active, or developing threat. ActiveEye records relevant data for each alert, enabling users to quickly view its trigger, the systems it impacts, and any actions taken to address the alert.

ActiveEye also provides tools for reviewing groups of alerts based on key attributes or time periods.

Attribute filters enable users to toggle which alert groups are shown in ActiveEye, helping users spot trends or threat activity. Users can also compare alert logs for specific time periods to determine if specific trends are associated with a threat or are false positives.

Investigations and Reporting
ActiveEye includes robust ad hoc reporting capabilities that provide important information about active and historical threats. Users can share information outside of ActiveEye by downloading reports in .csv or .json format.

In addition to ad hoc reporting, ActiveEye can provide a daily email summary and monthly report. Daily email summaries can include alert counts, security cases opened or closed, saved queries that have new data, and detailed endpoint security statistics. If needed, ActiveEye can send one or more summary emails with different content for different groups. Monthly reports are available as a PDF download.

Security Advisories
ActiveEye also enables the SOC to share Security Advisories on active threats. These advisories guide security teams on how to take actions against threats and where to get more information.

Information Sharing
ActiveEye includes several other functions for sharing information. Automatic security alerts notify pre- defined contacts of incidents, based on incident priority. Other information-sharing functions include:
• SOC Bulletins - Instructions from your agency’s personnel or the SOC that analysts reference when creating security cases. These can communicate short-term situations where a security case may not be required, such as during testing or maintenance windows. • Customer Notebook - The SOC will use the Customer Notebook to document your agency’s environment and any specific network implementation details assisting the SOC investigation of security cases.
• Contact Procedures - Escalation procedures and instructions on who to contact if an incident occurs. Contact procedures include instructions and procedures for specific security incident levels. The SOC manage contact procedures and work with the agency to identify any needed escalation points.

User Access
User access settings make it simple to add, update, and remove access to ActiveEye. Users may be given administrative access, allowing them to perform administrative tasks such as setting up new service connectors, resetting passwords, and setting up multi-factor authentication for other users.

Service Modules
One or more service modules can be integrated through the ActiveEye platform. These modules provide more information for ActiveEye to correlate, offering a clearer vision of events on your agency’s Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 45 of 372
The City of Carlsbad, CA

network. In addition, modules enable security teams and analysts to more easily access and compare data from disparate systems.

Endpoint Detection and Response
If an attacker attempts to breach your existing security controls, it is critical to respond quickly.

Integrating Endpoint Detection and Response (EDR) tools with the ActiveEye platform enables security analysts to respond to attacks and view threat intelligence in a single interface. Through the ActiveEye platform, analysts can isolate hosts, block files, allow files, and remove files.

ActiveEye MDR includes ongoing monitoring by Motorola Solutions SOC cybersecurity analysts to look for potential cybersecurity threats to connected networks, applications, and devices on a 24/7 basis.

The SOC team operates from secure, redundant locations in the United States, and can securely operate at remote locations if necessary. Team members complete regular training on customer data management and privacy to protect sensitive customer data. Based on their broad security experience, the SOC’s analysts will recommend security device configurations and implement playbooks to increase focus on the most critical threats.

If a threat investigation requires input from your agency’s security team, the SOC will create a security case and follow defined escalation procedures for each priority level. ActiveEye will enable your agency’s personnel to view security cases and event investigation history.

In the event of a potential incident, the SOC will use data available in ActiveEye and access your agency’s system to determine the extent of malicious activity. If needed, the SOC will add more detection policies to your agency’s service modules.

1.6 PREMIERONE INTERFACES
The interface details are provided in the Interface Functional Descriptions (IFDs) in Section 8.

1.7 PREMIERONE INTEGRATIONS

1.7.1 PremierOne Integration – Astro Radio Push-to-Talk (PTT) The ASTRO APX Integration with PremierOne CAD displays the units that trigger the radio Emergency button or the Emergency icon on the PremierOne Mobile client on the PremierOne CAD work monitor.

Detailed implementation discussion is a part of the System Admin Training Class.

1.7.2 PremierOne Integration - Vigilant
The Vigilant integration with PremierOne CAD provides dispatchers a notification of the license plate "hit" by creating an Incident automatically. An acknowledgement is not required for the Incident to be created and the dispatcher can choose to close the Incident if it is not needed.

1.7.3 PremierOne Integration - VESTA
The VESTA integration allows Automatic Number Identification (ANI) and Automatic Location Identification (ALI) information to be passed from the VESTA 911 system to PremierOne CAD. This integration enables Call Takers to have the essential data to initiate a call for service in the CAD Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 46 of 372
The City of Carlsbad, CA

System. When the 911 system receives the ANI/ALI data feed from the third party provider, it passes it to the CAD System, via a Lantronix device. When the call is picked up by a Call Taker, the call handling system determines the call position and routes the parsed data to the associated CAD Workstation.

The data is then displayed in the Incident Initiation form.

VESTA Integration Use Cases
• A 911 call is answered, the ANI/ALI information is passed to the CAD client ∙ The CAD system automatically populates the Incident Initiation form
• CAD user can request a manual refresh using shortcut keys (e.g. Shift + F11) to populate the Incident Initiation form with ANI/ALI data
• The interface supports Phase 0, Phase I, and Phase II class of service types. ∙ The CAD system can place ALI data in a CAD Incident Queue, when a user is working on an active incident • The CAD system can process a re-bid request for wireless call • CAD user can associate a Telecommunications Device for the Deaf (“TDD”) conversation to an incident
• CAD user can view the TDD conversation of an incident • If ALI data is not available for a call, the CAD system will display one of the following messages in the ALI data field:
- No communication with the database
- No information available
- ALI receive error, press RTX
- Conversion NPA-NPD error

1.7.4 RapidSOS Integration
PremierOne Integrates RapidSOS features into PremierOne CAD allowing for faster and more reliable caller location and to calltakers, improving response to emergency situations RapidSOS Location Data Integration
When a calltaker answers a call from within PremierOne, RapidSOS will retrieve the caller’s device- based hybrid (DBH) location and provide it within three seconds on the calltaker’s CAD interface. The calltaker can then use RapidSOS to track the location of the caller throughout the call, with location data accurate to within three seconds each time the calltaker re-bids the location.

RapidSOS Supplemental Data Integration
In addition to location data, RapidSOS aggregates available medical or emergency information about the caller from multiple data resources and then displays it to the calltaker through the PremierOne user interface. This helps get crucial information to calltakers faster than questioning the caller —information that the calltaker can then pass on to first responders to help them maintain their own and the caller’s safety.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 47 of 372
The City of Carlsbad, CA

1.8 COMMANDCENTRAL AWARE SOLUTION

DESCRIPTION

1.8.1 CommandCentral Overview
Agencies can increase the value of their current investments by connecting CommandCentral Aware to other software platforms. These integrations include PremierOne CAD, VESTA 9-1-1, ASTRO 25 Radio, Avigilon (ACC), ONSSI VMS, Vigilant License Plate Recognition (LPR), the VMS for a Drone system, and the DW Spectrum traffic cameras. Users can communicate with confidence, knowing their information is hosted in the highly secure Microsoft Azure cloud.

1.8.2 CommandCentral Aware Features and Integrations
CommandCentral Aware provides a range of capabilities, described in the sections below.

Mapping
CommandCentral Aware features a unified interface to display locations and alerts. Users can view all location-based data on the map display to enhance decision-making. CommandCentral Aware Mapping features also include the following:
• Event Monitors – View device status and location, CAD incidents, open-source data alerts, and sensors on a map. This map can consist of Esri online, Esri server, or static map layers. This map can be modified with other data layers.
• Data Layer Panel – Show or hide data layers to refine the map view. • Event Information Display – View details associated with each icon on the map. • Historical Map – View a 90-day lookback of radio locations, CAD incidents, service requests, or emergencies. An export tool extracts the recreated timeline to KML format to view in Google Earth or Esri ArcGIS Pro. The Location Replay feature enables the historic path of a device’s location.
• Breadcrumbing – Track individual APX user radios. Tracking begins at the time the action is toggled on. Devices can provide up to the last 30 minutes of live movement.

Geographic Information System (GIS) Data Set
CommandCentral Aware integrates with hosted GIS data sets from Esri ArcGIS Server or ArcGIS online. The geospatial information contained within these data sets are core to the intelligent map display. This enhances workflow details driven by geography and the metadata contained within these data sets.

Esri’s powerful geospatial engine within CommandCentral Aware is used to automatically invoke spatial queries, including nearby items and geographic boundaries. This geospatial processing enables intelligence-driven analysis in order to focus on the concentrated area of concern and orientate those responding.

Data sets help users to:
• Refine displayed data based on the geographic area defined per user. Data includes area, beat, sector, precinct, zone, or quadrant.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 48 of 372
The City of Carlsbad, CA

• Find nearby entities by predefined distance. Parameters include closest camera while in route, closest cameras to an event - CAD, gunshot detection, alert. • Determine road blockages caused by traffic jams, flooded roadways, or other obstacles.

AccuWeather Integration
CommandCentral Aware includes integration with AccuWeather. This integration provides customized weather-driven services. Services include site-specific forecasts, severe weather warnings, historical data, and custom analytics. AccuWeather also provides the following data:
• Location key for your desired location.
• Forecast information for a specific location.
• Current Conditions data for a specific location.
• Daily index values for a specific location. Index availability varies by location. • Radar and satellite images.

Rules Engine
The Command Central Aware rules engine allows users to create rule-sets to trigger actions based on event types. For example, rows in the Event Monitor can be highlighted, and sound alerts for critical CAD incidents can be customized. These visual or auditory triggers reduce the number of steps needed to support an incident.

PremierOne Computer Aided Dispatch (CAD) Integration
CommandCentral Aware integrates with PremierOne CAD to provide CAD status and event monitor capabilities. The CAD status monitor allows users to see a listing of incidents (event type, location incidents, narrative, priority, status, geographic area, location of devices or units).

Vigilant License Plate Recognition (LPR) Integration
Motorola Solutions’ LPR enables law enforcement agencies to organize and archive data collected from multiple mobile and fixed site LPR deployments. LPR technology has numerous applications including parking enforcement, law enforcement and city surveillance, and security and monitoring. Capabilities of Motorola Solutions’ LPR system are as follows:
• Photograph a vehicle and focus on its license plate in moving traffic. • Raise an alert, show a photo of the vehicle and license plate, and display why it is of interest in response to a match.
• Mine and analyze plate identification data for patterns. • Map all locations related to a single plate to locate and map vehicle movements. The web interface allows data to be shared across multiple locations and agencies. Create wildcard hotlists with partial license plate numbers, and hotlists that notify assigned investigators of hits without alerting in-car vehicle officers.
• Associate related data from disparate systems to get a full view of an incident or hot-list hit/alarm occurrence via the Correlation Engine. Display nearby video sources based on the LPR hot-list hit/alarm, sensor alarms, and provided third-party data alerts. • Enforce parking with digital tire chalking for enforcement of time limits and residential, university semester, employee, short-term, and shared permits.

Support law enforcement and city surveillance with live data transmission between vehicles and the back office, and back office data mining and geo-fencing.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 49 of 372
The City of Carlsbad, CA

VESTA 911 Call Handling Integration
CommandCentral Aware integrates VESTA 911 call data. The CommandCentral Aware application shows key caller events alongside location updates to monitor the status of wireless callers. This provides essential information to assist personnel responding to an incident.

Video Management System Integration (Drone system and ONSSI VMS) A core component of CommandCentral Aware is Video View. The module provides the ability to consume video content from systems such as the Drone system’s VMS. Each VMS brings with it a variety of tools via an SDK. These tools can include, but are not limited to, location, user controlled Pan Tilt Zoom (PTZ), Digital Zoom, Image Capture, Video rewind and export clip, and allow for historic search of recorded video. These features improve productivity from call to closure and increase responder safety.

In addition to functional tools, the Video View module can consume video analytics of automated license plate recognition, facial recognition and object detection. These capabilities will add greater refinement to video feeds to accurately assess detail that the eye may not see, further enhancing the users experience within CommandCentral Aware. Component configuration within CommandCentral Aware allows for specific use case definition expanding automated intelligence into the application via:
• Workflow Configuration: Automatically associates related data together from disparate systems to get a comprehensive view of the incident or threat occurrence. Displays nearby video sources based on CAD incident, sensor alarms and provided third party data alerts. • Real–Time Video Streaming: Virtually patrol the community or immediately view the scene of an event in seconds by accessing up to 16 cameras simultaneously from video feeds via VMS System. Easily reference the video source, date, time, and location as well as customize camera groups for quicker access to particular locations. • Device and Content Control: Users can operate PTZ capable cameras, as well as perform a 10- second review from buffer. Snapshot pictures and video clips can be captured, stored, and shared for timely situational awareness. Users can create rule– sets to perform automated actions based on event types, helping to reduce the amount of steps necessary to support an incident effectively.
• Camera Location and Group Definition: Can be provisioned through the CommandCentral Aware or read directly from the VMS.
• Camera Field of View can be defined via CommandCentral Aware and viewed on the map display. Users can toggle off and on the cameras that may or may not be pointed in the direction of the incident.
• Video Camera Audit Log: Ability to capture user interactions and record them to a log.

Visualization of the response scene seconds before the responder(s) arrive creates a virtual officer in the Command Center which provides additional security to those at the edge. This virtual officer can also act in the capacity of virtual patrol assigned to observe live video during large events or within high crime areas.

Table 1-4– Supported Video Capabilities within CommandCentral Aware Feature Description
Camera Import Importing cameras and the directory tree from VMS to CommandCentral Aware Camera Location Use coordinates stored in-camera custom fields at the NVR (or) pulls geo-location coordinates from the camera units. Specifically identified during installation.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 50 of 372
The City of Carlsbad, CA

Feature Description
PTZ Control of pan, tilt, and zoom (PTZ) functions on capable camera units that have been imported into CommandCentral Aware.

PTZ Presets PTZ cameras predefined pan, tilt, zoom values are applied to live feed.

PTZ Tours PTZ cameras execute a scan of its vicinity.

Live Video Direct feed from the camera as provisioned in the VMS system.

Recorded Video Playback video from the archive.

Live Snapshots Perform a screen capture of the live scene to send as an attachment via messaging service.

Recorded
Snapshots
Ability to isolate and capture a section of the recorded video to be distributed by the messaging service.

Recorded Fast
Forward
Display frame recorded sample at a faster rate playing forward.

Record Fact
Backward
Display frame recorded sample at a faster rate playing backward.

Digital Zoom Magnifies a selected area for live and recorded video.

Video Export Ability to prepare a video clipping for export to messaging or evidence collection.

APX Radios Location on Push-to-Talk or Location-on-Receive (TDMA) CommandCentral Aware provides the location of users from GPS-enabled land mobile radio (LMR) (ASTRO 25 radios) and broadband devices (LTE/Wi-Fi-enabled smartphones, tablets, and modems).

When a user presses the PTT, Emergency Button, Man-Down, or On-Demand buttons (or Stale Location or Not Reporting indications activate), CommandCentral Aware pinpoints the location. With each PTT press, CommandCentral Aware updates, delivers, and ingests device location data. This keeps command center personnel informed during critical incidents and allows dispatch to make more informed decisions. A user can be affiliated with multiple devices (both broadband and LMR). Multiple users and their devices can be affiliated with a unit.

Location on PTT increases location accuracy even when the radio system is congested with voice traffic. 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 forwarded to the application via Intelligent Middleware (IMW). The CommandCentral Aware application then allows dispatchers to view the location of any APX radio in near real-time to accelerate response.

An APX radio in a group 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 without impacting voice quality. Radios with Location on PTT can be configured to send their location after each PTT during group calls and during emergency calls.

Note: The County of San Diego Regional Communication System (“RCS”) is working with Motorola to add location services with an agency level distribution server. While Carlsbad is encouraged to work with the RCS to tailor this capability and validate deployment schedules, we expect this capability will be made available by the RCS. This unique operation will enable agencies and departments to have their own, as well as regional access to participating first responder locations.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 51 of 372
The City of Carlsbad, CA

CommandCentral Aware for Mobile Video (In-Car Camera Streaming) CommandCentral Aware Plus integrates with M500 in-car camera systems to support up to 500 in-car camera systems. Users can view real-time location, system details, and livestreams from systems in the field that are actively recording.

When in-car cameras are active in the field and the in-vehicle modem is on, the CommandCentral Aware user can view the system’s location on the map, see it listed in the event monitor, and open up a video livestream upon recording being initiated in the field. CommandCentral Aware users can control the livestream to see front, cabin, rear, panoramic and side (depending on camera model) views of events both in and outside of the patrol car. CommandCentral Aware users can access up to ten simultaneous in-car camera livestreams.

Aware Design Limitations
• A maximum of 3000 Icons viewed on the CommandCentral Aware client at one time, per instance.
• A maximum of 100 updates per second on the CommandCentral Aware client. • A maximum 5000 radios per server.

1.9 COMMANDCENTRAL INVESTIGATEPLUS
CommandCentral Investigate Plus, powered by LexisNexis, integrates with your existing data sources, leverages inter–jurisdictional data, and includes integrated search of billions of public records from over 10,000 sources. It also provides highly configurable experiences with purpose–built tools for roles across your agency.

Detectives can use link analysis across datasets to easily track down leads and close cases. Command staff can quickly identify emerging trends and, with the help of analysts, better understand those patterns and develop proactive initiatives to effectively address them.

This is a cloud–based product, subscribed to as a service. It is highly accessible and cost effective with predictable pricing. Product updates are seamless with new capabilities being delivered regularly. And, the cloud also provides proven security, reliability, and availability that keeps you operationally ready.

CommandCentral Investigate Plus includes a professional services engagement for implementation and deployment, and is built upon our operational expertise, tools, and best practices, perfected over our 90+-year history of working side–by–side with public safety.

Key Features & Functionality
• PremierOne CAD/RMS Integration
• Configurable, Role–Based Experiences
• Robust Data Visualization
• Easy Project Sharing
• Inter–Jurisdictional Data Sharing
• Cloud–Based & Delivered “as-a-Service”
• Granular Data Manipulation & Detail (140 Data Points Supported) • Accurint for Law Enforcement Enterprise Subscription
• Access to Over 10,000 Public Records for 267M+ People Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 52 of 372
The City of Carlsbad, CA

• Flexible Analysis Project Creation
• Advanced Link Analysis
• CommandCentral Platform Integration

1.10 COMMANDCENTRAL COMMUNITY
CommandCentral Community is designed to facilitate open and efficient communication between the City of Carlsbad and the community members you serve. CommandCentral Community will enable the City of Carlsbad to anonymously and securely collect tip details from citizens and use that information to build a more accurate operating picture of individual incidents.

Citizens can submit tips easily and quickly through a mobile-friendly interface, improving the situational awareness of public safety personnel by giving them as much information as possible when responding to emergency situations and performing ongoing investigations. Digital evidence collected from citizens is automatically stored in CommandCentral Evidence.

Incident and case report information is integrated with mapping software that automatically publishes crime data from Niche Records and/or PremierOne CAD to an interactive, online, public-facing map.

Incidents/case reports are represented by dots on a map that may be clicked into to provide limited information, including the decentralized address (hundred block), incident/case report number, date and time, and an incident/crime type. Incident comments and/or report narratives or victim information is not made available and certain crime types, e.g. sexual assaults, may be made “not visible” on the map.

This integration improves public perception by proactively sharing local crime information and providing visibility to the effectiveness of Police Department operations.

The CommandCentral Community experience centers around CityProtect.com. This mobile friendly webpage offers citizens a centralized set of tools to contribute to public safety. The tools and forms within CityProtect.com create a dialogue with your community and promote the value of citizen intelligence. Sharing and receiving important information is streamlined to make engagement easier.

Key Features & Functionality
• Agency Page
• Crime Map
• Camera Registration
• Digital Evidence Collection
• Public Submissions (Non-Emergency Online Reporting and Anonymous Tipping) PremierOne CAD Integration
Data publisher software will be installed on the PremierOne CAD which uses an ODBC driver to query the data source and then publish that data to CommandCentral Community.

Niche Records Interface
Niche Records must provide the data in a CSV, or other delimited text format. The Data publisher software will be configured to read it using a text ODBC driver and publish the data to the crime map.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 53 of 372
The City of Carlsbad, CA

1.11 CJIS AND COMPLIANCE
At Motorola Solutions we believe compliance is a team effort. As our customers’ partner in compliance, we are committed to employing privacy and security protocols that enable our customers to comply with the most stringent legal and regulatory requirements. In addition, we build on a strong foundation with an architecture (both Azure and on premise) designed and managed to meet a broad set of international compliance standards, as well as region-specific and industry-specific standards.

System services are designed to use FIPS certified technologies to protect data at rest and in transit.

PremierOne services utilize FIPS compliant Transport Layer Security (TLS) 1.2 protocol with AES 256- bit message encryption to establish secure communication with PremierOne Records and Records Mobile Clients.

Motorola Solutions employs rigorous third-party audits to verify its adherence to security controls and standards. To demonstrate Motorola Solutions safeguarding of customer data, comprehensive third party audits of primary Software Enterprise development and support operations have been completed and those operations have achieved ISO/IEC 27001:2013 (information security management systems) certification and AICPA SOC2 Type 2 reports will be available in early 2021. ISO/IEC 27017:2015 (information security controls for cloud services), ISO/IEC 27018:2019 (protection of personal information in public clouds) and ISO/IEC 27701:2019 (privacy information management) will be available in mid-2021. Supplemental SOC2 Type 2 reports and ISO/IEC 27001:2013 certifications for the development and support operations at satellite locations have been completed.

Motorola Solutions understands our customers’ critical need to safeguard the lifecycle of Criminal Justice Information. To support that need, Motorola Solutions designs its products and services to support compliance with the FBI’s Criminal Justice Information Services (CJIS) Security Policy and we commit to the terms of the CJIS Security Addendum. With a dedicated team of CJIS compliance professionals, we assist our customers through administering and coordinating CJIS compliant personnel credentialing, providing documentation assistance in connection with CJIS audits and advising on how to configure and implement our solutions in a manner consistent with the CJIS Security Policy.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 54 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Section 2
Statement of Work Overview

2.1 STATEMENT OF WORK OVERVIEW
In accordance with the terms and conditions of the Agreement, this Statement of Work (“SOW”) defines the principal activities and responsibilities of Motorola Solutions (“Motorola”) and the City of Carlsbad, CA, hereinafter referred to as “Customer” for the delivery of the Motorola solution as presented in Section 1 Solution Description. When assigning responsibilities, the phrase “Motorola” includes our subcontractors and third-party partners.

Deviations and changes to this SOW are subject to mutual agreement between Motorola and the Customer and will be addressed in accordance with the change provisions of the Agreement.

Unless specifically stated, all Motorola work is considered complete upon Motorola fulfilling the Motorola Responsibility listed for each task/activity and providing the deliverable(s) listed in the Motorola Deliverables tables.

Motorola and the Customer will work to complete their respective responsibilities in accordance with the mutually agreed upon governing project schedule. Any changes to the governing project schedule will be mutually agreed upon via the change provision of the Agreement.

The number and type of software or subscription licenses, products, or services provided by Motorola or its subcontractors are specifically listed in Section 1 Solution Description.

The specific software applications that comprise the System are outlined in Section 1 Solution Description and Section 3 Pricing Summary.

2.1.1 Award, Administration and Project Initiation
Project Initiation and Planning will begin following execution of the Agreement between Motorola and the Customer. Unless otherwise stated, all Motorola work will be completed remotely.

2.1.2 Project Management Definitions
The following project management terms are used in this document. Since these terms may be used differently in other settings, these definitions are provided for clarity. • Project Schedule means the schedule providing dates and timeframes for completion of tasks and deliverables during the course of the Project. The Project Schedule is subject to change at the mutual agreement of Motorola and the Customer.
• Project Management Plan is composed of the Communications Management Plan, Risk Management Plan, and Change Management Plan that provide the criteria for managing those tasks within the project.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 55 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

2.1.3 Project Management Plan
The project will be implemented in accordance with a Project Management Plan that will be reviewed and updated during the planning phase of the project. The Project Management Plan defines a comprehensive strategy for managing the project.

Project Portal/Repository
A project portal or repository will be established in MS SharePoint into which all project documentation and controls will be posted. The project documents and artifacts described below will be maintained throughout the implementation phase.

Documentation is organized into the following categories:
• Project Status
- Project Calendar
- Monthly Status Report
- Project Status Meeting Minutes
- Ad-hoc Project Meeting Minutes
- Project Schedule
- Action Item Register
- Risk Management Register
• Project Controls
- Requests for Information
- Project Tasks
- Change Control Requests
- Project Submittals
- Change Request Log
- Milestone Completion Certificates
- Project Knowledge Database (Lessons Learned)
• Project Communications
- Communication Plan
- Project Team Rosters
• Project Delivery
- Contract
- Technical Design and Implementation
- Business Process and Application
- User Management and Training

2.1.4 Project Status
Project Calendar - The Motorola Project Manager will maintain the project calendar that reflects all meetings and briefings.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 56 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Status Meetings - The Motorola Project Manager will conduct status meetings with the Customer Project Manager(s). The project schedule will be reviewed and baselined during Project Planning.

Thereafter, the Scheduler will collect the status of all activities, including milestones due, review upcoming milestones, and update the schedule and critical path in preparation for weekly schedule reviews with Motorola and the Customer. If the critical path in the schedule experiences a 10% variance, or changes to critical milestones, it will necessitate a discussion and approval of a Re- baselined schedule. The Scheduler will also make changes to the schedule that result from executed change orders. The current schedule will be stored in the project repository and will be sent to Customer to publish in Smartsheet.

Action Item Register – The Action Item Register is utilized to log activity within the project that requires action from a project resource. The Register will provide updated details about the status of the requested action.
• Risk Identification
- During the planning phase, an initial evaluation of risks will occur by the project team, led by the Motorola PM. When a risk is identified, the Motorola PM will review project documentation and conduct brainstorming sessions with the project team. A project team member can identify new risks at any point during the project. • Risk Response Planning
- The Risk Register will be used to prioritize risks. The risks will be rated using the probability/likelihood and estimated impact. The risk trigger and owner will be identified for further monitoring of the risk.
• Risk Monitoring & Control
- Each risk is recorded in the Risk Management Register. A risk control plan is established for each risk. The focus of the control plan is to manage or minimize the effect or impact of each risk by increasing the number of choices available and/or reducing the probability of occurrence.
- The risk owner will be responsible for monitoring the risk through the project execution and will report the status during every Status Meeting. Any updates to the probability/likelihood and impact of the risks will be communicated to the PM. • Change Requests & Lessons Learned
- Any change to the project activities to mitigate a risk or workaround for an unidentified risk may generate change requests. These change requests will follow the procedures detailed in the Change Orders section of this document.
- Lessons learned will be documented in the Project Knowledge Database (Lessons Learned).

Project Controls
The following types of documents will be used to manage the various project controls. All of these documents will be recorded in the Project Control Workbook (informally referred to as the project log). If the parties agree a change in scope of work, schedule, or terms of this Agreement are necessary, these changes will be executed as an amendment to the agreement. The city reserves the right to determine whether an amendment to the Agreement is required as determined by the City Attorney’s Office. The parties agree and understand that a Request for Information or other Motorola document requiring the city’s signature that is not an amendment to the Agreement is merely part of Motorola’s internal project processing controls and does not constitute a legally binding agreement.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 57 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Requests for Information – A Request for Information (RFI) will be issued by Motorola to Customer when there is a need for the formal collection of information from a party within the project.

An RFI may also be used when a specific task requires completion within a specified period of time.

The RFI memorializes the ask, identify completion criteria and formally introduce a required completion date.
• Receipt and Processing – Unless specified within the RFI, a complete response is due to the issuing party within five (5) business days of its delivery to the responsibility party unless the assigned resource indicates the response requires additional time. If the RFI is requesting an action, the completed action is expected on or before the close of business on the 5th day unless the assigned resource indicates the action requires additional time. • Request for Extension – If the requested information is unavailable or requires more time to collect, the responsible party must respond to the RFI as soon as practical, requesting an extension. The responsible party will specify the requested extension in days; if no duration is specified, five (5) days will be granted. If the requested extension is greater than five (5) days, the matter will be reviewed between the Motorola and Customer PMs. • Acceptance/Archive – The requestor will log the response on the RFI in the RFI folder noting the date of receipt, mark it complete in the Project Control Workbook, and submit the response to the team.

Project Task Orders
Project Tasks are called Project Task Orders in the project management tool. A Project Task Order is a controlled method of ordering work and tracking progress. Project Task Orders define specific tasks, deliverables, and timelines that are critical to the project's delivery. It may apply to a task/activity from the Scope of Services, or it may be a task that has come up as a result of other activities. Overall, Project Task Orders enhance project governance and ensure that the project stays on track, delivering the desired outcomes within the agreed-upon scope.

Timeline Process for Project Task Order Delivery

1. Request Initiation: The process begins with the initiation of the Task Order request in the project management tool by the project manager or authorized personnel. This includes defining the scope of work, required deliverables, and any other specific requirements.

2. Project Task Order Preparation: Once the Project Task Order is prepared, it shall be submitted to the project for processing. Relevant stakeholders, and or project resources will engage and complete the requested action or submit a response to the order requesting clarification or declaring that the work will not be completed. Any required revisions are made during this stage.

3. Final Approval and Issuance: After obtaining the completed task order response the project manager will confirm that the order’s requirements were met and the order will be closed.

Information will be shared with the appropriate resources and circulated appropriately.

Policy for Time Extension
If circumstances arise that necessitate an extension to the Project Task Order delivery timeline, the recipient must submit a notification for an extension, explaining the reasons for the extension, and providing an updated estimated completion date. The extension notification must be submitted as soon as the need for an extension becomes evident, and it should be sent to the project manager or the designated authority responsible for Project Task Order administration. The project managers, in consultation with relevant stakeholders, will review the extension notification and assess its validity.

Both parties, working collaboratively with each other, will review the extension notification and determine the best course of action. A new agreed-upon completion date will be documented in an Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 58 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

addendum to the original Task Order. Any change to a Project Task Order delivery timeframe that may impact the project schedule and/or milestone(s) will be subject to the Change Control Process.

Delinquency Policy
In the event of delinquency, where the responsible party fails to meet the agreed-upon Project Task Order delivery timeline without an approved extension, the following actions will be taken:

1. Escalation and Communication: The project manager will communicate with the recipient to understand the reasons for the delay and discuss possible solutions.

2. Impact Evaluation: The project manager will assess the impact on the overall project timeline and objectives.

3. Notification and Mitigation: The project manager will make formal notification to program administrators with Motorola and Customer, determine a new delivery timeline, provide the updated timeline to the scheduler, and re-log the task order with the identified extensions.

The delinquency will be added to the regular project status meeting and will be included in the project manager's executive report to Customer. The delinquency and the actions taken will be documented for future reference and to ensure compliance with contract terms. The project manager may also initiate measures to mitigate the impact of the delay on the project's overall schedule and success.

Change Control Requests
The Change Control Request (CCR) is a formal process for documenting changes that are made to critical portions of the system. Once an environment is in place and being used for configuration and/or training it is important that we control access and downtime for that system, as extended downtime or changes to it could impact project progress. The Change Control Process is a formal submission for any requested change and then tracks it as it goes through the right approvals so that everyone who should be advised of the proposed change is aware of it and buys into it. It keeps order in the project to make sure that uptime of critical environments is maintained. • Motorola and Customer will complete and submit a Change Control Form to the Customer Change Control Board for all changes to critical portions of the system once the system is being used for configuration and/or training. The Change Control Form contains the following information:
- Description of Change
- Justification
- Implementation Plan
- Risk and Impact Analysis
- Back out Plan
- Test Plan
- Validation Plan
- Planned Start Data & Time
• The Change Control Board (CCB) meets weekly, and reviews all submitted change control requests. If the CCB approves the change, a mutually agreed start date and time will be determined.
• Receipt and Processing – Once the CCB approves the change request, a signed acknowledgement of the submission is due back to the issuing party within three (3) business days of delivery. Depending on the span of changes, a CCR may require multiple signatures Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 59 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

from within the same organization. In this case, twenty-four (24) hours will be allocated for each individual to review and sign the CCR.
• Request for Extension – Due to the urgency of the type of work associated with the CCR process, an abbreviated revision cycle shall be observed. If the submitted document requires a revision, the details of the revision should be submitted to the issuer within two (2) business days of its delivery. The issuer then has two (2) business days to respond to the revision request. If the revision requires more than two (2) business days to complete, the issuer shall respond to the revision request specifying the amount of time requested. This response is due within the aforementioned two (2) business days.
• Acceptance/Archive – When responses are completed, the Motorola PM will disseminate the CCR to all parties, log the completed CCR in the project artifacts folder, and mark it complete in the Project Control Workbook.

Project Submittals
A Project Submittal (SUB) is an official document submission to the project artifacts. It includes technical diagrams, design documents, specification documents (including business process information and provisioning data), training material, product information, software release notes, or other documents that require permanent recording in the project archives. The submittal process serves as a method of review and acceptance of those documents. The recipient of a SUB circulates it for proper approval and returns it with a signature in cases where one is required. • Receipt and Processing – Unless specified within the SUB, a signed acknowledgement of the submission is due back to the issuing party within three (3) business days of delivery. • Request for Extension – A revision to the SUB should be submitted to the issuer prior to the expiration of business on the third (3) business days after delivery. The issuer has three (3) business days to respond to the revision request. If the revision requires more than three (3) business days to complete, the issuer shall respond to the revision request specifying the requested amount of time. This response is due within three (3) business days. If the requested extension is greater than seven (7) days, the matter will be formally reviewed between the Motorola and Customer PMs.
• Acceptance/Archive – Upon acknowledgement, the requestor shall log the completed SUB in the project SUB folder, mark it complete in the Project Control Workbook, indicate the date of approval, and post the SUB and acknowledgement to the project artifacts log.

Change Order Process and Amendments
Motorola uses the term “Change Order” for changes that, per City processes and procedures, require an amendment to the Agreement. For clarity, where the term “Change Order” appears throughout this document, the parties agree and understand that an amendment is required to be legally binding.

Again, agreed upon changes to scope of work, schedule, or terms require an Amendment.

The change order process defines the procedures by which the project scope may be changed. It includes the paperwork, tracking systems, and approvals necessary for authorizing changes.

The intent of the change order process is to ensure concurrence between the Customer and Motorola on any changes to the contracted scope, schedule, and/or price defined in the Agreement.

Amendments to the agreement may originate for several reasons including but not necessarily limited to:
• Change to the price
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 60 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

• Addition/deletion to scope of work defined in this document • System design change
• Requirement changes
• Functional change
• Milestone/deliverable change
• Milestone Payment change
• Procedural change spelled out in the Agreement
• Supplier change of equipment
• Alternate equipment or solution(s)
The Change Order process may be initiated as a Request for Information (RFI) to identify the potential change in project scope and request information about the impact of the change. For clarity, RFIs cannot alter the scope and terms of the agreement. The Motorola Program Manager reviews the potential change with the Customer project manager to determine the proper course of action necessary to respond to the requested change. This review may involve resources from Contracts, Engineering, and/or key subcontractors (if applicable) to properly evaluate and respond to the merits of the change. An evaluation usually determines whether a proposed change is feasible, meets the intent of the change, is appropriately priced, if applicable, and tests for acceptance of the change by both parties involved. If the City and Motorola determine the potential change identified in the RFI changes the agreement scope, schedule, or price in the agreement, the change will be executed with a contract amendment.
• Receipt and Processing – When the RFI is issued by the City, Motorola shall submit to City a written response, which shall include any adjustments to the contractual baselines within a reasonable number of days, unless otherwise agreed by the Parties. When issued by Motorola, and unless specified within the RFI, an email acknowledgement is due back to the issuing party within a reasonable number of business days of delivery. • Request for Extension – Due to the urgency of the type of work associated with the change order process, an abbreviated revision cycle shall be observed. If the submitted document requires a revision, the details of the revision should be submitted to the issuer within a reasonable number of business days of its delivery. The issuer then has a reasonable number of business days to respond to the revision request. If the revision requires more than two (2) business days to complete, the issuer shall respond to the revision request specifying the amount of time requested. This response is due within a reasonable number of business days. • Contract Amendment – The City Attorney’s Office will review the RFI to determine if it requires a contract amendment. If the City Attorney’s Office determine that a contract amendment is appropriate, the City will notify the Motorola Program Manager and will proceed with the amendment process. If a contract amendment is required, the change to the project scope, schedule, or terms will not be authorized and executed until the contract amendment is executed.
• Acceptance/Archive – The contract amendment must be authorized and executed by the Customer and Motorola before work in the amendment can begin. Upon execution, the Scheduler updates the schedule, if applicable. The Motorola PM updates the appropriate Project Delivery document(s), as applicable. The requestor logs the executed amendment in the Change Order Log, marks it complete in the Project Control Workbook, indicates the date of execution, and posts the amendment to the project artifacts log.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 61 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

• This section will not be construed to mean the parties will renegotiate Agreement terms aside from changes to the scope of work and associated increases in cost for additional products or services.

Milestone Completion Certificates (CERTs) formally document the completion of a Major Project Deliverable (MPD) or Major Billing Event (MBE) (which triggers an invoice). • The Motorola PM will deliver CERTs to the Customer PM for approval. The CERT will identify the specific milestone and identify whether or not it is a progress or payment milestone. • Receipt and Processing – Unless specified within the CERT, acknowledgement of receipt is due within five (5) business days of its delivery to the Customer signatory. Notwithstanding the aforementioned, acknowledgement does not constitute acceptance under any circumstances. • Request for Extension – If an extension is required before acknowledgement can be made, the Customer signatory must respond within three (3) business days, requesting a formal extension and the additional days required. If no duration is specified, three (3) days will be granted. If the requested extension is greater than five (5) days, the matter will be formally reviewed between the Motorola and Customer PMs.
• Acceptance/Archive – Upon the City’s written acceptance, the Motorola PM will log the acknowledged CERT in the project repository and mark the acceptance as complete in the Project Control Workbook.

Project Knowledge Database will be the repository for ad-hoc artifacts related to change requests, business process engineering, training, etc.

Project Delivery
The Project Delivery repository space (SharePoint Team site) contains the documents/deliverables developed and updated during implementation activities. Documents in this space include but are not necessarily limited to business process reviews and workbooks, business process re-engineering documents, provisioning worksheets, hardware inventory and installation, testing/validation exercises, training classes and schedules, interface deployment, software version management and release notes, third party partner scope, cutover planning, as-built documentation, and documents related to the transition to the support phase.

A Project Submittal (SUB) (as described above) will be completed to describe all document deliverables created/developed during the implementation. Iterative changes to such documents, such as updated provisioning data, will also be documented with a SUB.

Communication Plan
The Communication Plan will be created after project kickoff. The Communication Plan will consist of two sections: the internal Project Communication Plan and the Stakeholder Communication Plan.

The adoption and adherence to the Communication Plan will:

1. Generate Awareness and alignment across all stakeholder Departments, and among project stakeholders, project delivery teams, and executive leadership.

2. Create understanding of acceptable methodologies for the delivery and acceptance of time- sensitive documents that trigger important activity which directly ties to the project's Critical Path.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 62 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

3. Trigger action between and among project resources, stakeholders, and sponsors.

4. Hold all parties accountable to agreed upon timelines and processes for documentation of critical project activities.

5. Ensure adherence to agreed upon delivery timeline and the timely and efficient delivery of tasks within the project’s scope.

The Internal Communication Plan describes and includes the following types of communications:
• Project team meetings – Informal meetings amongst project team member to discuss general status and raise potential concerns.
- Meeting notes, minutes, action item lists will be documented and managed by Motorola in coordination with the Customer Project Team.
• Request for Information (RFI) - Issued when there is a need for the formal collection of information from a party within the project.
• Project Task Order - Serves as a formal request between the parties to perform defined tasks or services, outlining the scope of work, responsibilities, and performance expectations. • Project Submittal (SUB) - An official document submission to the project artifacts. It may include technical diagrams, specification documents, training material, product information, software release notes, or other documents that require permanent recording in the project’s archive. • Note to File (NTF) - Serves as a mechanism of documentation for any agreement that does not change scope, budget, or schedule, but requires logging between or among project stakeholders.
• Change Control Request (CCR) - Utilized to manage requests to conduct alterations to any system that is being utilized in a production capacity and or any system that is deemed critical to the operation and advancement of project delivery activities. • Milestone Acceptance Certificate (CERT) - executed when a Major Project Deliverable (MPD) or Major Billing Event (MBE) has been completed.
• Invoice Event - Triggered by the completion of specific events that have been agreed upon between Customer and Motorola and documented within the “Payment Milestones” of the executed contract.

Each type of communication includes the purpose, delivery method, signature requirements, approval lifecycles, request for revisions or time extension, delinquency criteria, and approval process.

A corresponding Communication Schedule Matrix describes the Communication, Method, Frequency, Goal, Owner, and Audience for each type of communications.

The Stakeholder Communication Plan will be developed by the Customer Project Team in consultation with Customer stakeholders and Motorola. The Stakeholder Communication Plan will be the governing document regarding the proper process of communicating with the various stakeholders, subcontractors, the media, and other key project participants. The Stakeholder Communication Plan will incorporate Organizational Change Management communication.

Motorola and Customer shall use Microsoft teams, channels, and SharePoint for teleconference, instant messaging, and project file management. The Stakeholder Communication Plan is an external facing plan to ensure that stakeholders are well informed, and to support stakeholder buy-in for the project. It will also use various communications channels, including but not limited to: e-mail, workshops, development, and publication of documents and notifications at stakeholder facilities, multi-media presentations, etc.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 63 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverables
• Communication Plan
Quality Management
Motorola Quality Management covers the general policies that govern our approach to quality. These policies are used to satisfy our customers, manage our processes, and meet our business objectives.

Our project quality framework supports a set of guidelines and checkpoints designed to demonstrate that the solutions we design, integrate, implement and support, will meet your requirements and expectations. Each project quality plan is created using a collaborative approach to manage the unique needs of your project. Motorola instills quality into the project to lower the risk and lower the total costs over the life of the system.

Our “culture of quality,” involves the standardization of business practices, investment in quality tools, and the delivery of quality training to our management, field personnel, and customers.

Quality Audits
Motorola will perform Quality audits on a regular basis throughout the implementation phase and will be used to verify that the project team is following prescribed processes and procedures. The audits take into consideration the status and importance of the processes and areas to be audited, as well as the results of any previous audits.

Quality Audit Purpose Planned Frequency
Documentation Reviews Review of project documents and
communications to ensure documentation
standards are being followed.

Weekly
Quality Audits Project deliverables subject to quality audits and reviews:

Schedule
Communications Management Plan
Weekly

2.1.5 General Customer Responsibilities
In addition to the Customer Responsibilities stated elsewhere in this SOW, the Customer is responsible for:

1. All Customer-Provided equipment including hardware and third party software necessary for access or delivery of the service not specifically listed as a Motorola deliverable. This will include end user workstations, Internet Service Provider (ISP), network equipment, telephone/CPE or TDD equipment and the like.

2. Configuration, maintenance, testing and supporting the third party systems that the Customer operates and which will be interfaced to as part of this project. The Customer is responsible for providing Application Programming Interface (API) documentation to those systems that document the integration process for the level of interface integration defined by Motorola.

3. Active participation of Customer Subject Matter Experts (SME’s) in project delivery meetings and working sessions during the course of the project. Customer SME’s will possess requisite knowledge of Customer operations and legacy system(s) and possess skills and availabilities to operate and manage the System.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 64 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

4. The provisioning of Customer Code Tables and GIS data as requested by Motorola. This information must be provided in a timely manner in accordance with the Project Schedule.

5. Electronic versions of any documentation associated with the business processes identified

6. Provide a facility with the required computer and audio-visual equipment for training and work sessions as defined in the Training Plan.

7. Ability to participate in remote project meeting sessions using MS Teams.

2.2 PROJECT ROLES AND RESPONSIBILITIES

2.2.1 Motorola Project Roles and Responsibilities Overview A Motorola team made up of specialized personnel will be appointed to the project under the direction of the Motorola Project Manager. Team members will be multi-disciplinary and may specialize in different products. Team members will be engaged in different phases of the project as necessary.

The personnel role description noted below provides an overview of typical project team members.

There may be other personnel engaged in the project under the direction of the Project Manager.

Motorola Project Manager
Motorola’s project management approach has been developed and refined based on lessons learned in the execution of hundreds of system implementations. Using experienced and dedicated people, Project Management Institute standardized processes, and integrated software tools for effective project execution and control, we have developed and refined practices that provide design, production, and testing that is optimized to deliver a high quality, feature-rich system.

A Motorola Project Manager will be assigned as the principal business representative and point of contact for the organization. Due to Motorola’s varied product offerings and divisions, the Motorola project manager will be the sole communications and activities gatekeeper for all Motorola project related activities for the City of Carlsbad, unless mutually agreed upon. This is to ensure that the Motorola implementation is treated as a single, unified project implementation and not a disjointed implementation of varied product implementations, with varied methodology, and differing training approaches.

Responsibilities of the Project Manager include:

1. Managing the Motorola responsibilities related to the delivery of the project including DOJ approval activities.

2. Project scheduling and management of the assigned Motorola personnel and applicable subcontractors/supplier resources.

3. Management of the Change Order process per the Agreement.

4. Maintain project communications with the Customer or the customer’s agents.

5. Identification and management of project risks.

6. Collaborative coordination of Customer resources in an effort to minimize and avoid project delays.

7. Measuring, evaluating, and reporting progress against the Project Schedule.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 65 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

8. Conducting remote status meetings in a cadence agreed by the project team with the Project Managers to discuss project status.

9. Participate in weekly calls regarding current activities.

10. Preparing and submitting a status report that identifies the activities of the previous month, as well as activities planned for the current month, including an updated project schedule and action item log.

11. Providing timely responses to issues related to project progress raised by the Customer.

12. Being the primary point of contact and communication channel for all Motorola functionality and internal company divisions to help facilitate a single Motorola client experience during the project.

Motorola Application Specialist
The Motorola Application Specialist will work with the Customer to enable the project team to support and guide the Customer with the provisioning of the System Capabilities.

Responsibilities of the Motorola Application Specialist will include:

1. Provide consultation services to the Customer regarding the provisioning and operation of the System.

2. Provide provisioning training to the Customer to provide the knowledge to setup and maintain the system.

3. Complete base provisioning and module configuration.

4. Complete the provisioning ownership handoff to the Customer.

5. Complete the project defined milestones and tasks as defined in this SOW.

6. Provide guidance on the Customer’s operational Change Management needs relative to the use of the System.

7. Provide training as defined by this SOW and described in the Training Plan.

8. Provide onsite assistance during the Go Live event.

Motorola GIS Analyst
The Motorola GIS Analyst specializes in geographical information technology. Responsibilities of the Motorola GIS Analyst include:

1. Performing the GIS Analysis on the Customer supplied GIS source data.

2. Providing the Customer the results of the GIS Analysis based on the requirements of the Motorola GIS Build Requirements document.

3. Consultation services regarding the conversion of Customer GIS source data for Motorola use.

4. Provide GIS Training as defined in this SOW and in the Training Plan.

5. Import of the Customer provided GIS data into the System.

6. Geocoding Data, Centerlines to support Routing and Response Area Polygons (for CAD) Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 66 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Solution Architect
The Solutions Architect is responsible for the delivery of the technical elements of the System. They confirm the delivered technical elements meet contracted requirements. They are engaged throughout the duration of the delivery.

Motorola Cloud Activation Team
The Cloud Activation team will establish a temporary cloud tenant for the initial provisioning of the Customer’s environment and work with the Customer to grant Customer access. Once the On-Premise hardware is installed and Motorola’s remote access is granted, the provisioning work will be transferred from the cloud tenant to the On-Premise environment.

Motorola Customer Success Advocate
A Customer Success Advocate (CSA) will be assigned to the Customer following the Go Live event.

Their role is to assist the Customer with maximizing the use of their Motorola software and service investment by being the Customer’s trusted advisor in actively managing, escalating, and logging issues with Support, Product Management, and Sales while providing ongoing Customer communication about progress, timelines, and next steps.

Motorola Customer Support Services Team
Motorola’s Customer Support team will provide ongoing support, Customer Support Plan (CSP) following Customer Final System Acceptance.

2.2.2 Customer Roles and Responsibilities
The success of the project is dependent on early assignment of key Customer resources. It is critical that these resources are empowered to make provisioning decisions based on the Customer’s operational and administration needs. The Customer project team should be engaged in the project from initiation until beneficial use of the system. The continued involvement in the project and use of the system will convey the required knowledge to maintain the system post completion of the project. Note that in some cases, one person may fill more than one role. The project team must be committed to participate in activities for a successful implementation. Team member roles are generally described below:

Customer Project Manager
The Customer Project Manager will act as the primary Customer point of contact for the duration of the project. The Project Manager will be responsible for managing the Customer project team including the timely facilitation of their efforts, tasks, and activities. This includes the management of any Customer vendors that are subcontractors.

Responsibilities of the Customer Project Manager include:

1. Maintaining project communications with the Motorola Project Manager.

2. Identifying the efforts required of Customer staff to meet the task requirements and milestones in this Statement of Work and Project Schedule, including DOJ approval activities.

3. Consolidating all project-related questions and queries from Customer staff to present to the Motorola Project Manager.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 67 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

4. Reviewing the Project Schedule with the Motorola Project Manager and assisting in finalizing the detailed tasks, task dates, and responsibilities.

5. Measuring and evaluating progress against the Project Schedule.

6. Monitoring the project to ensure that resources are available as scheduled.

7. Attending status meetings.

8. Providing timely responses to issues related to project progress

9. Liaising and coordinating with other agencies, Customer vendors, contractors, and common carriers.

10. Reviewing and administering change control procedures, hardware and software certification, and all related project tasks required to maintain the Project Schedule.

11. Ensuring Customer vendors’ adherence to overall Project Schedule and plan.

12. Assigning one or more personnel who will work with Motorola staff as needed for the duration of the project, including at least one application administrator for CAD, Mobile, as applicable, and one or more representative(s) from the IT department.

13. Identifying the resource that has the authority to formally acknowledge and approve change orders, approval letter(s), and milestone recognition certificates and to approve and release payments in a timely manner.

14. Providing supervised building access to Motorola personnel to all facilities, if necessary, where any on premises components of the system will be installed during the project.

15. As applicable to this project assuming responsibility for all fees for licenses and inspections and for any delays associated with inspections due to required permits.

16. Providing reasonable care to prevent equipment exposure to contaminants that cause damage to the equipment or interruption of service.

17. Ensuring a safe work environment for all project personnel.

Customer Transformation Lead
The Customer Transformation Lead, who may or may not be your Project Manager, must be able to holistically represent your organization and be able to work cross functionally between Motorola, your organization and all stakeholders involved in the delivery of your new system. The transformation lead must be empowered to acknowledge the resource and time commitments required of your organization and authorize Motorola to proceed with scheduling the Project Kickoff event.

Customer System Administrator
The Customer System Administrator is responsible for managing the technical efforts, tasks and activities of their system as defined in the Customer Support Plan (CSP) in Section 10.

Customer IT Personnel
IT personnel provide required information related to Azure Active Directory, LAN, WAN, ISP, wireless networks, server, and client infrastructure and must also be familiar with connectivity to internal, external and third party systems to which the PremierOne system will interface.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 68 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Customer Application Administrator
The Customer Application Administrator is responsible for the management of the Customer owned application provisioning maintenance. The Application Administrator will be involved early in the project starting at the Business Process Review (BPR), attend the Provisioning Workshop and Train the Trainer Training and remain engaged throughout the project to ensure that they are able to maintain the system provisioning post Customer Provisioning handoff. Responsibilities of the Customer Application Administrator include:

1. Participate in overall delivery and training activities to gain an understanding of the software, interfaces, and functionality of the system.

2. Participate with the SMEs during the BPR, provisioning process, and training.

3. Have the authority to make global provisioning choices and decisions and will be the point(s) of contact for reporting and verifying problems and maintaining provisioning.

4. Obtain inputs from other City stakeholders related to business processes and provisioning.

Customer GIS Analyst
The Customer GIS Analyst is responsible for the development and maintenance of all of the GIS data used in the PremierOne system. The Customer GIS Analyst must have working experience with Esri software including ArcCatalog, ArcMap, and ArcPro, including knowledge of model builder, toolbox tools, and general database structure. Also, it is very important to have a working relationship with the named Application Administrator(s). The GIS Administrator will be heavily involved in the data preparation for the System as well as data maintenance throughout the term of the Agreement. This will include but is not limited to the following standard responsibilities:

1. Providing GIS data in the correct schema

2. Developing, maintaining and updating GIS data

3. Support of the GIS elements used in the PremierOne Services (Server and clients) Subject Matter Experts
The Subject Matter Experts (SME) (Super Users) are the core group of users that will be involved with the business process reviews and analysis, the provisioning process, including making global provisioning choices and decisions, and training. These members should be experienced users in the working area(s) they represent, i.e. dispatch, patrol, etc. and should be empowered to make decisions related to provisioning elements, workflows, screen layouts, etc.

Customer Training Representative
Training representatives will be the point of contact for the Motorola Application Specialist when policy and procedural questions arise, act as course facilitators, and are the Customers’ educational monitors.

Additional Resources
Additional resources, such as trainers and database administrators may also be required.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 69 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Customer Agency Stakeholders
User agency stakeholders, if the system is deployed in a multi-agency environment, are those resources representing agencies outside of the Customer Agency. These resources will provide provisioning inputs to the SMEs if operations for these agencies differ from that of the Customer agency.

2.3 PROJECT INITIATION AND PLANNING
A clear understanding of the needs and expectations of both Motorola and the Customer are critical to the success of the project. Project Planning requires the gathering of project specific information that is critical to setting clear project expectations and guidelines, creating the Project Management Plan, Project schedule, and setting the foundation for a successful implementation.

2.3.1 Project Planning Session - Teleconference/Web Meeting A Project Planning Session will be scheduled after the Agreement has been executed between the assigned Motorola and Customer Project Managers.

The Business Process Review Agency Pre-Kick Off Survey is a survey that is sent to the Customer to collect Agency specific information such as dispatch logistics, communication center information, operational process, and workflow. The information in the survey is used to prepare for the Business Process Review.

The Aware Technical Discovery Requirements document contains information required to establish network connectivity and to perform integration and establish connectors with additional and third party systems.

The GIS Discovery Survey is used to assist Motorola Solutions in gathering information to better understand the Customer’s current capabilities and needs relating to the GIS.

The agenda will include:
• Review the Agreement documents
• Review the applications, query(ies) and interface(s) described in the System Description document and the individual Interface Functional Descriptions (IFDs). Review project delivery requirements as described in this Statement of Work (SOW). • Discuss Customer involvement in provisioning and data gathering to confirm understanding of the scope and time commitments required
• Review the PremierOne Agency Build Guide. The PremierOne Agency Build Guide provides a structural overview of the Customer’s System. This includes the definition of Agency Type Code, Name, ID, and default areas.
• Review the initial project schedule and incorporate Customer feedback resulting in the governing Project Schedule. The Project Schedule will include all project related tasks for both customer and Motorola will be maintained by Motorola and updated through mutual collaboration. Schedule updates that impact milestones will be addressed via the Change Order provision of the Agreement.
• Finalize the Project Management Plan.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 70 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

• Confirm requirements for CJIS background investigations and/or contractors, fingerprint requirements for Motorola employees and/or contractors. Motorola will conform to the City’s backgrounding process (HireRight).
• Review Virtual Desktop (VD) and Learning eXperience Portal (LXP) role in the delivery and discuss required Customer provided information to access them • Review Customer obligation to manage change among the stakeholder and user communities • Provide the Business Process Review Agency Pre-Kick Off and GIS Discovery Survey • Review project completion criteria and the process for transitioning to support Completing the Business Process Review Agency Pre-Kick Off Survey and the GIS Discovery Survey are critical Project Tasks. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.

Motorola Responsibilities

1. Schedule the remote Project Planning Session

2. Provide the initial Project Schedule and Project Management Plan

3. Provide the Business Process Review Agency Pre-Kick Off Survey and the GIS Discovery Survey

4. Provide the Agency Build Guide

5. Provide the Aware Technical Discovery Requirements document

6. Finalize the Project Management Plan

7. Baseline the Project Schedule

8. Provide and manage Issue/Resolution Checklist
Customer Responsibilities

1. Identify and engage project team members responsible for carrying out the system implementation.

2. Provide input to the Project Schedule dates

3. Provide information necessary to perform background checks for Motorola employees and/or contractors.

4. Review and complete the Business Process Review Agency Pre-Kick Off and the GIS Discovery Survey within ten (10) business days of the Project Planning Session so as not to impact the Project Schedule.

5. Provide required information to complete the PremierOne File Build tables file. Required information is to be provided prior to GIS Check Point #1 Addressing Validation, Routing, and Boundaries.

6. Complete the information on the Aware Technical Discovery Requirements document prior to the Project Kickoff Session.

7. Review and provide feedback on the Project Management Plan Motorola Deliverables - Project Planning Session
Project Schedule Baseline
Project Management Plan
Business Process Review Agency Pre-Kick Off Survey
GIS Discovery Survey
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 71 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverables - Project Planning Session
PremierOne Agency Build Guide
Aware Technical Discovery Requirements document
Completion Criteria - Project Planning Session
The Project Planning Session is considered complete upon conclusion of the meeting.

Payment Milestone 1 - Project Plan
The City’s approval of the Project Schedule and Project Management Plan

2.3.2 Project Kickoff Session - Teleconference/Web Meeting The objective of the Project Kickoff meeting is to provide a high-level overview of the service and delivery process to the Customer’s team. During the Project Kickoff meeting the Motorola Project Manager will provide an overview of the following:
• A high level review of the Project Deliverables
• Roles and responsibilities for the project team members • A high level review of the baseline Project Schedule including project milestones and checkpoints
• Discuss any project related questions
Motorola Responsibilities

1. Schedule the remote Kickoff Teleconference/Web Meeting

2. Prepare the Kickoff Meeting agenda.

3. Distribute any documentation that the Customer should review in advance of the Kickoff Meeting.

4. Conduct the Kickoff Teleconference/Web Meeting.

Customer Responsibilities

1. Schedule the personnel from the Customer project team to attend. This should include key stakeholders that have authority or responsibility over the project.

Motorola Deliverables - Project Kickoff Session
Project Kickoff Session Agenda
Completion Criteria - Project Kickoff Session
The Project Kickoff Session is considered complete upon conclusion of the meeting.

2.3.3 GIS Planning Session - Teleconference/Web Meeting A GIS planning session will be scheduled to review the GIS Build Requirements Document and complete an overview of the GIS components of the project. The agenda will include:
• Review the Motorola GIS Build Requirements Document
• Discuss Customer GIS skill-set and responsibilities
• Review the requirements of the Customer GIS sample data that is required Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 72 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

• Discuss any GIS related project questions
Providing the GIS Customer Data is a critical Project Task. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.

Motorola Responsibilities

1. Schedule the remote GIS Planning Session
Customer Responsibilities

1. Review the GIS Build Requirements document prior to the meeting.

2. Provide the GIS sample to Motorola within ten (10) business days of the GIS Planning Meeting so as not to impact the Project Schedule
Motorola Deliverables - GIS Planning Session
GIS Build Requirements Document
Completion Criteria - GIS Planning Session
The GIS Planning Session is considered complete upon conclusion of the meeting.

Milestone – GIS Planning Session
Customer delivery of sample GIS data within 10 days of GIS Planning Session.

2.3.4 Interface Planning Sessions - Teleconference/Web Meetings Interface Planning Sessions will be scheduled to discuss the user experience presented by each contracted interface as defined in the PremierOne the Interface Functional Descriptions (IFDs) in Section 8. The agendas will include:
• Conduct a review of the functionality delivered with each interface • Discuss interface deployment requirements (NDA, network information, API and access credentials required to connect to third party systems) • Review Interface Project Schedule tasks and milestones The interface deployment requirements (NDA, network information, API and access credentials required to connect to third party systems) are needed to begin deployment of the interfaces.

Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.

Motorola is not responsible for third party vendor management, scheduling or additional third party cost for software, customization, development, or testing unless the work is defined in this SoW or amended to the Agreement via a Change Order.

Motorola Responsibilities

1. Identify additional information such as third party API, SDKs, data schema and any internal and 3rd party documents necessary to establish interfaces.

2. Conduct reviews of the interfaces to explain how each functions as well as any dependency on third party API, SDKs, data schema and any internal and third party documents necessary to establish interfaces with local and remote systems.

3. Provide Motorola Non-Disclosure Agreements (NDA) as required.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 73 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Customer Responsibilities

1. Provide the required interface deployment requirements (NDA, network information, API and access credentials required to connect to third party systems) within ten (10) business days of each Interface Planning Meeting so as not to impact the Project Schedule.

Motorola Deliverable - Interface Planning Session
Updated IFDs, if/as applicable.

Completion Criteria - Interface Planning Session
The Interface Planning Session is considered complete upon conclusion of the meeting.

Milestone - Interface Planning Session
Mutually accepted IFDs
Customer delivery of interface deployment requirements within 10 days of Interface Planning session or as mutually agreed.

2.3.5 Connectivity Planning Session - Teleconference/Web Meeting A Connectivity Planning Session will be scheduled to discuss the connectivity required for the on premise and cloud based products and interfaces being implemented. The agenda will include:
• Review Microsoft Entra ID requirements
• Review of connections of end user workstations to the Cloud services and the on premise solution.
• System connectivity to on premise and cloud-based products and interfaces being implemented. • Plan for State/NCIC query connectivity (as applicable).

Network and connectivity to the Cloud environment is a Customer responsibility and is crucial to the operation and use of the Cloud services. Delayed, unavailable, or inadequate network connectivity may have a significant impact on system operation and the Project Schedule.

Motorola Responsibilities

1. Review the workstation connection process.

2. Provide the connectivity process for the included interfaces.

3. Review connectivity options for the CLETS/NCIC interface.

4. Provide the information required for DOJ approval.

Customer Responsibilities

1. Ensure resources knowledgeable on the Customer networks attend the review.

2. Provide the details related to the interfaced systems for the services.

3. Provide the requirements for connecting to the State/NCIC interface.

4. Provide the network connectivity to the end user workstations, State/NCIC, and interfaced systems.

5. Complete the base PremierOne Cloud Services connectivity requirements within ten (10) business days of the Connectivity Planning Session so as not to affect the Project Schedule.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 74 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverable - Connectivity Planning Session
Motorola’s inputs to Customer’s DOJ approval process
Completion Criteria - Connectivity Planning Session
The Connectivity Planning Session is considered complete upon conclusion of the meeting.

Milestone - Connectivity Planning Session
Complete the base connectivity requirements within ten (10) days of the planning session.

2.4 PREMIERONE SERVICES PROJECT EXECUTION
The execution of PremierOne is done through a series of milestones that are designed to enable the success of the project. Motorola will work closely with the Customer to complete provisioning, validate operational readiness, and complete user training in preparation for operational use.

This service utilizes the PremierOne deployment model which enables the core capabilities of the service for the Customer’s operations. PremierOne contains features, functionalities and modules that are capable of being enabled but may not be in the scope of this project. The features, functionalities, and modules that are within the scope of this project are described in Section 1 Solution Description and in the Motorola RFP responses for functional requirements.

Understanding time is of the essence with respect to System delivery, both the Customer and Motorola will strive to perform in accordance with the Project Schedule and take steps necessary to mitigate potential delay. Motorola’s implementation delivery services are based on the following durations, dependent upon the product mix of the System:
• Actual project duration will be established as part of the Project Schedule development activities.
• Customer sign-off is required for the Project Completion Milestone.

2.4.1 PremierOne Hardware and Environment
General Hardware and Environment Requirements
Motorola and the Customer will provide hardware and/or an environment that conforms to the following general requirements:

Motorola Responsibilities:

Motorola is responsible for the providing, installing and maintaining the operation of the PremierOne and CommandCentral Equipment listed in Table 7-1 in Section 7 Hardware, Network, and Environmental Specifications.

1. Provide, install, and configure equipment in accordance with Section 7 Hardware, Network, and Environmental Specifications.

2. Install and configure server application software.

3. Provide, install, and maintain antiviral/malware software.

4. Conduct a “power on” test to validate that the installed hardware and software are ready for configuration.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 75 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

5. Load preliminary provisioning data on primary system hardware.

6. Install and enable CloudConnect Virtual Machine and contracted cloud-based software.

7. Install, configure, and test CAD VPN-centric access with direct connectivity to the Carlsbad PremierOne CAD environment.

8. Verify contracted software is available and accessible on the installed system.

9. Establish connectivity to CommandCentral CAD Disaster Recovery (DR)

10. Synchronize the primary CAD system and the DR systems.

11. Verify failover to the CommandCentral CAD DR and restoration (failback) to the primary CAD system.

Customer Responsibilities

1. Supply hardware, operating system software, third party components necessary to operate client devices such as desktops, printers, and mobile devices.

2. Provide advanced authentication for Mobile/Handheld device connectivity if required.

3. Provide a network diagram depicting all the devices, device types, and interfaces that the service will connect to and through, including, but not limited to all blocked ports, hubs, switches, routers, firewalls, and any other network equipment.

4. Confirm the server room complies with the requirements stated in Section 7 Hardware, Network, and Environmental Specifications.

5. Enable outgoing network connection (external firewall) to the CommandCentral cloud via an internet connection.

6. Provide, install, maintain, and service any software as required for anti-viral, anti-malware protection on the workstations/devices. If the software requires connectivity to a central server for maintenance and updates, the connectivity, including ports and access, needs to be provided.

7. Confirm access to installed software.

8. If the customer chooses during the deployment planning to host one of the MSI services virtual machines (e.g. CommandCentral cloud connector) on customer owned infrastructure, provide an IP address on the customer network.

9. Provide external interface connection demarcation points at locations agreed to by Motorola.

These locations shall normally be adjacent to the cloud interface appliance.

10. Provide access, administrative or otherwise, to appropriate systems, locations, information, tools, and equipment to ensure proper connectivity, installation, operations, and maintenance of the service.

11. Provide 24-hour access to a secured two-way Internet connection to the cloud interface appliance and firewalls for the purposes of deployment, maintenance, and monitoring.

12. Allow a site-to-site VPN with at least 4 addressable IP's on the inside subnet capable of establishing and maintaining an IPSec tunnel with 75Mb/s of throughput.

13. The Motorola delivery model is reliant upon our ability to perform most tasks remotely, which requires secure, remote broadband access for remote deployment, monitoring, and support of the interface Anchor Server appliance.

14. Provide, install, maintain, and service any software as required for anti-viral, anti-malware protection on workstations that access the service. If the software requires connectivity to a Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 76 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

central server for maintenance and updates, the connectivity including ports and access needs to be provided.

15. Have a fully implemented Mobile Device Management (MDM) software for Handheld Mobile devices, as desired by the Customer.

16. Provide wireless connectivity for mobile clients and handheld clients to the PremierOne CAD server and/or to a VPN. Optimal application performance on mobile workstations requires 4G connectivity.

Motorola Deliverables - PremierOne Hardware and Environment Installed System Equipment
Connectivity to Disaster Recovery environment
Completion Criteria - PremierOne Hardware and Environment This task is considered complete upon demonstration that the system equipment is installed, application software is available, and connectivity with the DR environment is established.

Payment Milestone 2 - Completion of Software Installation The City’s acknowledgement that system equipment is installed and application software is available, including connectivity to the Disaster Recovery environment.

2.4.2 Cybersecurity Services (Managed Detection and Response) Motorola ActiveEyeSM Managed Detection and Response provides endpoint monitoring by experienced, specialized cybersecurity analysts with extensive experience working with PremierOneⓇ mission-critical networks.

The following elements are available as part of the Managed Security Service:
• ActiveEye Security Management Platform.
• Applicable service modules. These modules use Service Connectors to integrate specific network components into the ActiveEye monitoring platform and SOC services. • Technical Support for troubleshooting.
• Security Operations Center (SOC) monitoring and support. • Monitoring and response for applicable ActiveEye service modules.

In order to establish initial expectations for deployment, Motorola will work with Customer to help you understand the impact of ActiveEye Managed Detection and Response.

Motorola Responsibilities

1. Schedule a service kick-off meeting with Customer. The kick-off meeting will be conducted remotely at the earliest mutually available opportunity.

2. Provision tools in accordance with the requirements of this Service.

3. Collaborate with Customer’s Primary Point of Contact (POC) to define the timing, confirm scope.

Customer Responsibilities

1. Attend the kick-off meeting.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 77 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Note - Failure to complete the actions above will delay the accomplishment of the implementation.

ActiveEye Security Management Platform
The ActiveEye Security Platform will collect, analyze, and automate the investigation of IT and security activity. The web-based ActiveEye portal enables Customer to view threat insights, create security reports, and view threat advisories. In addition, Customer will be able to use the ActiveEye portal to manage notification settings and communications with the Motorola SOC.

The ActiveEye platform collects data directly to its cloud service interface. Motorola will provide 24/7 access to the ActiveEye Security Management Platform. Motorola will notify Customer if access will be affected, such as by scheduled maintenance. Motorola will also provide a detailed response/monitoring plan during Active Eye deployment based on the City’s requirements.

Motorola Responsibilities

1. Provide access to the ActiveEye portal for Customer and Motorola Managed Services team.

After initial deployment, Customer will have self-service access to add/remove/update user access as needed.

2. Provide the subscribed services.

3. Install agents on in-scope systems and devices, as required.

4. Configure all necessary PremierOne components of Customer’s infrastructure to integrate with ActiveEye.

5. Resolve platform issues and technical errors as identified.

6. Retain security logs within ActiveEye for thirty days. Security logs will be archived for one year by the long-term storage policy. Archived logs will be made available for audit purposes as the result of a security incident.

Customer Responsibilities

1. Provide reasonable assistance to Motorola to perform the Service, as described in this SOW.

2. Provide the name, email, landline telephone numbers, and mobile telephone number for all security Points-of-Contact (POC).

3. Perform all network and system integrations necessary for ActiveEye Service. This includes providing external Internet connectivity for ActiveEye security components.

4. Securely manage user access to the ActiveEye portal, creating new user accounts when needed and removing a user’s access when it is no longer required.

Completion Criteria - ActiveEye Security Management Platform This task is considered complete upon demonstration that the Customer has access to the ActiveEye portal.

Endpoint Detection and Response
ActiveEye managed Endpoint Detection and Response integrates endpoint detection and response (EDR) tools with the ActiveEye Security Management Platform to provide additional threat intelligence, automated investigation, and orchestrated response actions to optimize protection of critical systems.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 78 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

EDR integration with ActiveEye accelerates investigations by making necessary information available for analysts in a single platform, where they can quickly access details of what caused an alert, its context, and its history.

The platform enables analysts to initiate response actions (i.e. isolate host, block list a file, allow list a file, and remove file) on endpoints to respond to detection of verified malicious activity within Customer’s system. Available responses are determined by Customer’s EDR tool and security policies.

Motorola Responsibilities

1. Provide ports and protocols to Customer for the EDR solution.

2. Deploy and maintain EDR agents to PremierOne host environment.

3. Configure EDR solution to enable ActiveEye connection for event/alert collection and response actions.

Customer Responsibilities

1. Configure customer edge networking infrastructure to allow EDR agents to communicate over the internet with the cloud.

Completion Criteria - Endpoint Detection and Response
This task is considered complete upon deployment of EDR agents in the PremierOne host environment and configuration of the EDR solution.

2.4.3 PremierOne Business Process Review (BPR)
Motorola will lead the PremierOne Business Process Review (BPR) to understand the Customer’s operational processes and workflows. A BPR session will be conducted for each of the contracted System application categories: CAD, Mobile. The information collected in the BPR will provide Motorola the framework for how the System will be provisioned and configured to best meet the Customer’s needs and the requirements in the Functional Matrix.

Prior to the Business Process Review, Motorola will schedule a remote session to review the Customer results of the Pre-Kickoff Business Process Survey.

The Business Process Review Customer Survey review and PremierOne Service Connectivity are required to be completed prior to the Business Process Review.

The Customer is responsible for engaging all user agencies that will be provisioned on the service to obtain required inputs. A single instance of the activities described as “the BPR” will be conducted for a combined law enforcement dispatch audience unless specifically stated otherwise in this SOW. The result will be a single provisioning profile for law enforcement and dispatch. If an additional BPR or provisioning for additional agencies is required, it will be addressed via the Change Order provision of the Agreement.

The BPR should be attended by senior operational decision makers, such as dispatch supervisors, senior call takers/dispatchers, and mobile (Windows and Android/iOS) users, as applicable. Manager level personnel can help guide the discussion of policies that have the potential to be improved or modified. Customer personnel will include Motorola’s responses to requirements from the Functional Requirements Matrix. The practical input based on experience in the agency’s operational environment is often indispensable in the later configuration of the System to effectively meet the Customer’s needs.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 79 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

The BPR agenda will include items such as the following:
• Business Process Review Survey Responses
• Provisioning processes for the System applications (CAD/Mobile) • Overview of the System applications
• Agency and Discipline Information (Agency Type, # of Personnel, shift types, etc.) • User Permissions/Security
• Provisioning Overview - PremierOne Agency Build Guide (provided post contract) • For CAD -
- Agency Data Gathering Discussion (Includes incident types, unit status codes, dispositions, unit IDs, and personnel)
- Dispatcher/Responder Workflow - Incident creation to closure - Notifications and Status Monitors
• Reporting Review
• Operational Process Discussion (e.g. Incidents, Units, Call Taker and Dispatcher roles and responsibilities)
• Site Visits and Ride Alongs with specific agencies and divisions Motorola Responsibilities

1. Provide the BPR Agenda/Workbook prior to the meeting.

2. Complete the BPR Workbook.

3. Review the documented business processes and provide configuration options.

4. Review the completed BPR Workbook.

5. Conduct a single BPR session for each product in the System (e.g. One for CAD, One for Mobile (Windows and Android/iOS). CAD and Mobile BPR’s will be conducted within the same on-site trip.

Customer Responsibilities

1. Review the BPR Agenda/Workbook prior to the meeting.

2. Schedule applicable resources (e.g. dispatch, police, and fire/EMS, personnel for sit alongs and ride-alongs).

3. Provide resources knowledgeable in the Customer’s business processes to provide relevant documentation on the workflow and operating procedures.

4. Provide required information to complete the BPR e.g.:

A. Field Modification Decisions.

B. Personnel Information Provided.

C. Workflow Configuration.

D. Document Colors.

E. Agency Logo provided - (If desired by Customer).

5. Review the completed BPR Workbook.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 80 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverables - PremierOne CAD Business Process Review (BPR) BPR Agenda
BPR Workbook
 Completion Criteria - PremierOne CAD Business Process Review (BPR) The Business Process Review Session is considered complete upon conclusion of the meeting and delivery of the approved BPR Workbook.

Milestone - PremierOne CAD Business Process Review (BPR) Customer provides information required to complete BPR Workbook during BPR session.

2.4.4 PremierOne GIS
GIS Scope Review
The Motorola GIS Analyst meets remotely with the Customer’s GIS Administrator to discuss the approach to developing the GIS data for use with the PremierOne System.

GIS Scope Review topics that will be discussed include:
• For CAD - Agency Response boundaries needs, routing requirements, premise hazard areas and specifics for address validation using street centerlines, common places, address points, alias tables, and premise hazard areas.
• The GIS Data Verification Report describes the Customers source feature classes and data values that have been made available to Motorola. The data is reviewed and any items identified that may impact the applicable functionality of the data within the Motorola System are noted within the GIS Data Verification Report. The GIS Data Verification Report is delivered post contract after review of the Customer GIS data.

The Customer GIS Data is required to be made available prior to the GIS Scope Review.

Motorola Solutions Responsibilities

1. Review GIS Draft Data Verification Report.

2. Discuss current GIS business practices.

3. Discuss frequency of GIS updates to current service and desired frequency.

Customer Responsibilities

1. Ensure availability of GIS administrator for this meeting.

2. Finalize the agency code and beat names for the geodatabase. All of the data will be required but the streets, address points and common places can be works in progress that can be updated as the project moves along. The agency and beat names should be final by provisioning.

Providing the Agency Code and Beat Names for the geodatabase is a critical Project Task.

Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 81 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverables – PremierOne GIS Scope Review
GIS Draft Data Verification Report
Completion Criteria - PremierOne GIS Review
Completion of PremierOne GIS Review meeting
PremierOne CAD – GIS Boundaries Meeting
If PremierOne CAD is contracted as a System component, the Motorola GIS Analyst will meet remotely with the Customer’s GIS Administrator and CAD SMEs to discuss and confirm Response Boundaries data that is loaded into the PremierOne CAD service. Motorola will provide an overview of the available boundary types and their function that can be used in the PremierOne CAD service.

Topics that will be discussed include confirmation of the Customer’s Agency Code and Beat Names, and provide an overview of the Agency Code and Beat names role in the PremierOne CAD to determine if any modifications need to be made prior to import into the PremierOne CAD.

The Agency Code and Beat Names are required to be provided by the Customer prior to the GIS Boundaries Meeting.

Motorola Solutions Responsibilities

1. Provide an overview of the Agency Code and Beat Names role in the PremierOne CAD.

Customer Responsibilities

1. Ensure availability of GIS administrator for this meeting.

2. Confirm Agency Code and Beat Names readiness for load into PremierOne CAD.

Import of the Agency Code and Beat Names for the geodatabase is a critical Project Task.

Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.

Completion Criteria - GIS Boundaries Meeting
Completion of PremierOne GIS Boundaries Meeting
Agency Code and Beat Names imported into PremierOne CAD GIS Check Point Meetings
The Motorola GIS Analyst and Customer’s GIS Administrator will participate in up to five (5) - two (2) hour remote Check Point Meetings in accordance with the Project Schedule.

Meeting topics will include:
• GIS Check Point #1 Initial Data Review/Discussion
- Delivery of revised Customer GIS Data based on GIS Draft Data Verification Report is required prior to this Check Point
• GIS Check Point #2 Readiness for GIS Load
- Delivery of revised Customer GIS Data based on GIS Draft Data Verification Report updates is required prior to this Check Point
• GIS Check Point #3 Customer GIS Load Review
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 82 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

- Completion of PremierOne GIS Import Training is required prior to this Check Point • GIS Check Point #4 General GIS Check-In
• GIS Check Point #5 GIS Go Live Readiness
Motorola Solutions Responsibilities

1. Conduct the GIS Check Point Meetings

2. Evaluate Customer GIS data as submitted
Customer Responsibilities

1. Based on the GIS Data Draft Verification Report, make required changes to meet the Motorola defined GIS requirements
Motorola Deliverables - GIS CheckPoint Meetings
GIS Draft Data Verification Report Updates
Completion Criteria - GIS CheckPoint Meeting
Completion of PremierOne GIS Check Points Meetings
PremierOne Services and PremierOne System - GIS Draft Geodatabase The draft geodatabase will be created and uploaded to the PremierOne server to support provisioning efforts and draft maps will be created for use by the CAD workstations. Error reports that are produced as a result of developing the draft geodatabase will be delivered to the Customer in updates to the GIS Data Draft Verification Report.

The final geodatabase will be delivered during the GIS Import Tool Training, which is described in the Training Plan.

Following completion of GIS Import Tool Training, the Customer will be responsible for maintenance of the geodatabase.

Motorola Solutions Responsibilities

1. Create the draft geodatabase, maps, and Routing Network.

2. Create the draft geodatabase.

3. Provide updates to the GIS Data Verification Report reflecting any issues found during the geodatabase build.

4. Provide up to three (3) draft geodatabases.

Customer Responsibilities

1. Correct any GIS errors identified in the GIS Data Verification Report from geodatabase build.

Motorola Deliverables - PremierOne GIS Draft Geodatabase GIS Data Verification Report Updates
Up to three (3) draft geodatabases
Completion Criteria - GIS Draft Geodatabase
This task is completed upon delivery of the third draft geodatabase, maps, and Routing Network.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 83 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

2.4.5 Provisioning
PremierOne Provisioning
PremierOne provisioning includes the configuration of user configurable parameters (i.e. unit names, personnel, status codes). A temporary PremierOne environment will be provisioned using Motorola standard provisioning parameters and will incorporate Customer specific provisioning. Once the On Prem hardware is installed and remote access established, the provisioning information will be transferred to the production system.

Motorola will review the standard provisioning databases as documented in the Provisioning Worksheets during the BPR that will be imported into the System by Motorola. Motorola will complete the provisioning of the System based on the Customer’s Call flow, process, and operational processes as applicable to the System.

Customer specific provisioning parameters will be collected from the Customer using Provisioning Worksheets. Motorola will review the Provisioning Worksheets with the Customer to identify the information that is required for the Customer specific provisioning data tables. The Customer will be responsible for completing the Provisioning Worksheets in the proper format and with agency specific information. The information collected in the Provisioning Worksheets will be imported into the System exactly as it is provided by the Customer. PremierOne provisioning activities will be completed for each functional application group included in the System: CAD/Mobile/CommandCentral Aware/CommandCentral Community.

The CommandCentral CAD Disaster Recovery Solution leverages PremierOne CAD provisioning data.

Therefore, no provisioning changes will be supported while using CommandCentral CAD during a primary CAD outage. The Customer will utilize their existing PremierOne CAD provisioning when using CommandCentral CAD Disaster Recovery Solution.

PremierOne provisioning data collection and import is a critical Project Milestone. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.

At the completion of the provisioning the System will be configured to allow the evaluation of processes such as Call Flow, Incident Management, Users, Permissions, etc. Motorola will schedule a remote session with the Customer to demonstrate that the PremierOne provisioning is completed in accordance with the BPR Workbook and the Customer Provisioning Worksheets.

The responsibility for maintaining the Customer provisioning will transfer to the Customer post completion of the Provisioning Workshop.

Motorola Responsibilities

1. Review the standard provisioning database with the Customer prior to the start of provisioning.

2. Provide and review the Provisioning Worksheets with the Customer.

3. Conduct a conference call with the Customer to demonstrate the completeness of the Customer Provisioning Worksheets prior to the start of provisioning.

4. For PremierOne CAD, the Motorola Application Specialist will complete the standard provisioning as defined in Appendix A - PremierOne Attachment with the exception of NENA incident types.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 84 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

5. For PremierOne Mobile (Windows and Android/iOS), the Motorola Application Specialist and the Customer’s Mobile Administrator(s) will participate in up to four (4) two (2) hour remote CheckPoint Meetings in accordance with the Project Schedule as follows:

A. PremierOne Mobile Check Point #1 Initial Provisioning Review/Discussion B. PremierOne Mobile Check Point #2 Follow-up Provisioning Review/Discussion C. PremierOne Mobile Check Point #3 Customer Provisioning Review/Handoff D. PremierOne Mobile Client Installation Training (Windows, Android/iOS) is required to be completed prior to this meeting.

E. PremierOne Mobile Check Point #4 Mobile Trainer the Trainer Readiness F. Due to a large amount of Mobile provisioning being driven off of CAD provisioning, the provisioning of Mobile will generally follow the completion of the base CAD provisioning.

6. Complete the import of the data from Provisioning Worksheets.

Customer Responsibilities

1. Provide required information to complete the Provisioning Worksheets within ten (10) business days of the so as not to impact the Project Schedule.

Motorola Deliverables - PremierOne System Provisioning
PremierOne Customer Provisioning Worksheets
Completion Criteria - PremierOne System Provisioning
Demonstration of completed provisioning in accordance with the Provisioning Worksheets.

Milestone - PremierOne System Provisioning
Customer completion of Provisioning Worksheets within 10 days of receipt of the worksheets.

PremierOne Provisioning Workshop(s)
Post completion of the PremierOne Functional Validation, remote Provisioning Workshop(s) will be conducted. The workshop is a remote working meeting that will include a review and hands on training of the Customer maintained provisioning. Participants in the workshop should be part of the Customer deployment team.

This workshop is not meant to be comprehensive application end user training. The purpose of this workshop is to provide the training and knowledge required to maintain the Customer provisioning.

A PremierOne provisioning workshop will be completed for each functional application group included in the System: CAD/Mobile (Windows, Android, iOS).

The responsibility of building and maintaining System provisioning will transfer to the Customer post completion of the Provisioning Workshop. Provisioning should be kept updated for operational use by the regular maintenance of all provisioning (Personnel, Units, Caution Notes, Premises).

Motorola Responsibilities

1. Provide the PremierOne Provisioning Agenda and training materials.

2. Post completion of the Provisioning Workshop Motorola will schedule up to two (2) remote two (2) hour Provisioning Check-In sessions with the Customer to verify accuracy of the Customer provisioned data in accordance with the Project Schedule.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 85 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

3. Complete the PremierOne Provisioning Workshop.

4. Hand-off responsibility for maintaining provisioning data to the Customer.

Customer Responsibilities

1. Review the PremierOne Provisioning Agenda and Motorola provided training materials.

2. Assign participants that will be responsible for the maintenance of provisioning data.

3. Complete the assigned LXP courses prior to the start of the PremierOne Provisioning Workshop(s).

4. Assume responsibility for the continued maintenance of the Customer provisioning.

Motorola Deliverables - PremierOne Provisioning Workshop PremierOne Provisioning Agenda and Training Materials
Completion Criteria - PremierOne Provisioning Workshop
Completion PremierOne Provisioning Workshop(s)
Hand-off the responsibility for provisioning to the Customer CommandCentral Aware, CommandCentral CAD DR, and Community Provisioning Motorola will discuss industry best practices, current operations environment, and subsystem integration in order to determine the optimal configuration for CommandCentral Solution.

Motorola Responsibilities

1. Using the CommandCentral Admin Console, provision users, groups, rules, and based on Customer Active Directory data or similar.

2. Provision agency’s CommandCentral initial users and permissions.

3. Provide information on configuring CommandCentral Aware layers.

4. Provide information on provisioning Community Agency Pages, Crime Maps, etc.

5. Document provisioning approach for CommandCentral Aware and Community.

6. Provide instruction on provisioning in-car camera systems to support location and live streaming.

7. Complete provisioning of CommandCentral Aware and Community in accordance with the mutually approved approach.

Customer Responsibilities

1. Supply the access to Microsoft Entra ID for the purpose of Motorola conducting CommandCentral Solution provisioning.

2. Respond to Motorola inquiries regarding users/groups/agency mapping to CommandCentral Solution functionality.

3. Approve provisioning approach for CommandCentral Aware and Community.

Completion Criteria - CommandCentral Aware and Community Provisioning CommandCentral provisioning is complete upon Motorola completing provisioning activities in accordance with the mutually approved approach.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 86 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

CommandCentral Investigate Plus Installation and Credentialing Motorola Solutions enables the CommandCentral Investigate service during the order process.

LexisNexis accreditation is required to be completed by the Customer prior to the implementation of CommandCentral Investigate. Motorola will provide the CommandCentral Investigate credentialing application for the Customer to complete. Following review of the application for accuracy, Motorola will schedule a site inspection which is performed by a third party vendor called Trendsource. The inspection may take up to 1 hour. The site inspection representative is required to follow a LexisNexis questionnaire during the review. The types of questions asked during the site inspection include general information about your business, the office environment, high-level security features in place for your physical location and user workstations, and questions about how the data will be stored and secured. The representative will take a few photographs, some from the outside of your facility, and some of the general work area where data will be accessed and stored. The site inspection process is designed to avoid any review of confidential processes or practices. The representative will not ask to see the data center or any confidential/secured areas of the business, and they will not take photographs of these areas. They will not ask about proprietary controls such as firewalls or IP restrictions. The representative is not authorized to give a copy of the site inspection questionnaire to the Customer.

Motorola Responsibilities

1. Provide the credentialing application to Customer.

2. Complete site inspection and provide site inspection questionnaire.

3. Remotely activate CommandCentral Investigate and initiate email that provides information on setting up the service and provisioning users.

4. Use the CommandCentral Admin tool to enable Customer access to CommandCentral Investigate. This activity is completed during the order process.

5. Connect Customer incident data ingest (PremierOne CAD).

Customer Responsibilities

1. Complete the credentialing application.

2. Participate in the site inspection and ensure a resource is available to respond to questions during the inspection.

3. Provide access to Motorola Solutions’ team to connect incident data ingest.

4. Provide Motorola Solutions with crime type classification.

5. Set up users within CC Admin and set up user permissions groups.

Completion Criteria – CommandCentral Investigate Plus
CommandCentral Investigate subscription enabled and access verified.

2.4.6 CAD Client Installation
PremierOne CAD Client and Mobile Devices (Windows)
Client software will be installed on workstations/mobile devices to facilitate provisioning activities and provide instruction to Customer personnel who will complete software installation on the remaining workstations/mobile devices.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 87 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Responsibilities

1. Discuss client software distribution methodology.

2. Provide instruction on client software installation and install client software on up to five (5) CAD Client workstations and five (5) Mobile Windows clients.

Customer Responsibilities

1. Provide and install workstation/mobile device hardware in accordance with manufacturer’s specifications.

2. Supply Windows Server Client Access Licenses (CALs) for all system client devices accessing CAD and Mobile.

3. Assign personnel to observe the software installation process.

4. Provide advanced authentication for Mobile/Handheld device connectivity if required.

5. Provide power and network connectivity at designated workstation installation locations.

6. Provide wireless connectivity and middleware to deliver mobile Virtual Private Network (mVPN) with routing and IP persistence to the system network.

7. Complete installation of client software on remaining workstations and mobile devices.

Completion Criteria - PremierOne CAD Client Installation Overview/instruction/successful demonstration of PremierOne Client Installation on up to five (5) CAD and five (5) Mobile clients
Payment Milestone 2– Completion of Software Installation Motorola completes CAD Client Installation on 5 CAD Workstations and 5 Mobile Windows clients.

PremierOne Mobile Client Installation (Android/iOS)
The Customer can download the PremierOne Mobile client from an on-line app store. Motorola will provide the Customer app store locations from which the Android/iOS client can be downloaded and installed.

Deployment of PremierOne Mobile (Android/iOS) updates is a Customer responsibility.

CommandCentral Aware Client Installation
Motorola will configure Aware client software on the Customer-provided Aware workstations.

Motorola Responsibilities

1. Verify remote access capability after Customer completes physical installation of workstations.

2. Configure CommandCentral Aware client application.

Customer Responsibilities

1. Perform physical installation of the CommandCentral Aware workstations. Connect to power and network. Assign IP addresses for the network.

2. Provide supervised remote access to the CommandCentral Aware workstations.

Completion Criteria - CommandCentral Aware Client Installation Configuration of and successful demonstration of CommandCentral Aware client application.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 88 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

2.4.7 Functional Validation
Motorola will execute the PremierOne and CommandCentral Functional Validation prior to Customer training and in accordance with the Functional Validation Workbook referenced in Section 6. The purpose of this exercise is to verify and document that the PremierOne service is ready to be used in a production environment.

The following priority level definitions provide the classification of anomalies that may manifest during the functional validation review.

Critical-Priority Level 1: An incident is deemed CRITICAL if one or multiple critical functions are unavailable or severely degraded such that the customers' core business functions and capabilities are no longer delivered or capable. The resulting critical impact to the customers’ business is such that focus and resources must be applied to restoration or mitigation
Data has stopped showing in the application or users are no longer able to access the product due to a system-wide outage
High-Priority Level 2: An incident is deemed HIGH if a business function is unavailable and normal customer business activity is impacted or degraded, and a workaround may be available to mitigate the effects of the service impact; however overall efficiency or effectiveness is degraded.

This may apply to both critical and non-critical functions.

Recoverable application crash, All data inaccessible (e.g. videos inaccessible, missing incidents).

Medium-Priority Level 3: An incident is deemed MEDIUM if business functions are available, however, there is a deviation from the expected or agreed upon level of service or other service condition not aligned with the other defined impact levels.

Data missing; (e.g. incomplete video thumbnails, inconsistent incident population).

Low-Priority Level 4: An incident is deemed LOW if business functions are available, but minor issues exist such as cosmetic issues, documentation errors, general usage questions, and configuration questions.

Critical Priority Level 1, High Priority Level 2, and Medium Priority Level 3 issues, whether identified during PremierOne Functional Validation or during Customer Led Scenario Validation, will be retested following any corrective action taken to resolve the issue. Corrective action may consist of a configuration/provisioning change either by Motorola or the Customer, resolution of installation or environment variables such as network access or speed or remediation plan for software defects.

Numerous Medium Level severity issues may also prevent commencement of Beneficial Use.

Corrective action may consist of a configuration/provisioning change either by Motorola or the Customer, resolution of installation or environment variables such as network access or speed or remediation plan for software defect. Motorola and the Customer will mutually agree to a remediation plan to address the situation whereby numerous Medium Level Priority issues are considered “blocking” issues.

Following the corrective action, the validation scripts associated with the corrected function will be retested to verify corrections. Motorola will not conduct a full retest of all scripts in the Functional Validation Workbook in Section 6 but such testing may be conducted by the Customer. The Functional Validation verifies the functionality of the system. The City reserves the right to make the final determination that all Critical, High and Medium-level Priority issues have been resolved sufficiently to move forward with Go-Live.

Functional validation is provided for each Product contained in the System as follows:

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 89 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

PremierOne CAD Functional Validation
Motorola will schedule a remote two (2) day session with the Customer to demonstrate the CAD functional validation. PremierOne CAD functional validation verifies the functionality of the CAD service and does not include the testing of other products or interfaces.

PremierOne Mobile Functional Validation
Motorola will schedule a remote one-half (1/2) half day session with the Customer to demonstrate the Mobile functionality on two (2) PremierOne Mobile Windows devices and one (1) Android/iOS device.

PremierOne Mobile functional validation verifies the functionality of the Mobile service and will be completed post completion of the PremierOne CAD functional validation.

CommandCentral Functional Validation Demonstration
Motorola will provide a functional demonstration script and will demonstrate CommandCentral Aware/ and Community functionality during a one-half (1/2) day session with the Customer.

Customer Led Scenario Validation
Post completion of the Functional Validations the Customer will begin utilizing the PremierOne services and CommandCentral Aware to perform “Day in the Life” scenario validation using scenarios developed by them that have been based on their everyday operations/workflow as well as more complex unique scenarios they may encounter. The Customer will perform validation that the system meets requirements in the Functional Requirements Matrix with guidance from Motorola product experts.

Issues that are discovered during this validation exercise will be reported to Motorola for issue resolution in accordance with the Agreement.

Payment Milestone 3 – Completion of Functional Validation Tasks Completion of Functional Validation tasks (included in Payment Milestone 3)

2.5 PREMIERONE REPORTING
Motorola will establish a reporting data warehouse (RDW) to support ad hoc reporting with PremierOne CAD data using SQL Server Reporting Services (SSRS). The standard CAD Reports are listed in 2.11 of this document (Appendix B) and will be provided. Motorola will review the standard reports library and introduce the functionality available within SQL Server Reporting Service (SSRS) through the SSRS Workshop. The Workshop will be conducted in accordance with the Training Plan in Section 9.

Customer-specific or Customer defined reports are not included in the scope of this project unless defined in this SOW.

Motorola Responsibilities

1. Develop the RDW environment in PremierOne CAD.

2. Conduct SSRS Report Builder Training.

3. Provide the Standard PremierOne CAD Reports library.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 90 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Customer Responsibilities

1. Identify the agency’s reporting administrator and provide their Name, Email, and Phone Number.

2. Participate in SSRS Report Builder Training.

Completion Criteria - PremierOne Reports
PremierOne Standard Reports
PremierOne SSRS Reporting

2.6 INTERFACE AND INTEGRATION DELIVERY
The installation, configuration, and demonstration of interfaces may be an iterative series of activities depending upon access to third party systems. Interfaces will be installed and configured in accordance with the PremierOne Service Description, Project Schedule, and Interface Functional Documents (IFDs) provided to Customer prior to contract and incorporated as Ordering Documents. Integrated functionality between Motorola developed products will be completed through the software installation and provisioning activities described herein. Integration activities that have specific requirements will be completed as outlined in this SOW.

2.7 INTERFACE DEPLOYMENT
Connectivity will be established between the Motorola system and the external and/or third party systems to which the contracted software will interface. Motorola will configure the system to support each System interface. The Customer is responsible for engaging third party vendors if and as required to facilitate connectivity and validation of the interfaces.

Motorola Responsibilities

1. Establish connectivity to external and third party systems.

2. Configure interfaces to support the functionality described in the PremierOne (IFDs) and/or Interface Specification Descriptions (ISDs).

3. Installation and configuration of Common Service Interface (CSI) components.

4. Provide the Customer with the Interface Configuration Guides.

5. Provide Customer training for the PremierOne CAD provisioning of the interface as applicable.

6. Validate each interface can transmit and or receive data in accordance with the IFDs.

Customer Responsibilities

1. Act as liaison between Motorola and third party vendors or systems as required to establish interface connectivity with the Motorola system.

2. Provide personnel proficient with and authorized to make changes to the network and third party systems to support Motorola’s interface installation efforts.

3. Provide network connectivity between PremierOne and the third-party systems.

4. Complete the Interface Configuration Guides in accordance with the project schedule.

5. 5. Complete Customer defined PremierOne CAD provisioning as applicable.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 91 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverables - PremierOne Interface Deployment Interface Configuration Guides
Interface deployment/configuration complete - Interface ready for Interface Validation Demonstration
Unknown circumstances, requirements, and anomalies at the time of initial design can present difficulties in interfacing to some third party applications. These difficulties could result in a poorly performing or even a non–functional interface. At such time that Motorola is provided with information and access to systems Motorola will be able to mitigate these difficulties. If Motorola mitigation requires additional third–party integration, application upgrades, API upgrades, and/or additional software licenses those costs will be borne by the Customer or addressed through the Change Order provision of the Agreement.

2.7.1 Interface Validation
The objective of Interface Validation Demonstration is to verify that the installed interfaces perform according to the IFDs or ISDs, as applicable.

Motorola is not responsible for issues arising from lack of engagement of third-party and/or Customer resources to perform work required to enable/provision and or configure an interface to a 3rd party system, or troubleshooting any issues on the Customer’s third-party systems.

Interfaces that cannot be demonstrated due to connectivity issues to external systems or the unavailability of Customer’s third party system will be demonstrated to the degree the PremierOne functionality can be demonstrated. If interface validation cannot be completed in accordance with the project schedule due to connectivity issues to external systems or the unavailability of Customer’s third party system, a change order may be required to perform such validation when the issue is resolved.

Motorola Responsibilities

1. Conduct a demonstration of each interface, with the Customer, to validate each function per the IFDs and/or ISDs.

2. Develop a remediation plan for features that do not perform in accordance with the IFDs and/or ISDs.

3. Upon completion, provide the Customer with a Project Milestone Document, to be signed and returned to Motorola. Exceptions will be noted in the Project Milestone Document.

4. Schedule follow-up validation to demonstrate resolution of any Critical, High, and Medium-level Priority issues as defined in this SOW.

Customer Responsibilities

1. Provide access to a resource with access to the interfacing system to validate functionality.

2. Coordinate testing with third party systems.

3. Develop scenario-based test plan if desired.

4. Witness the execution of the validation and acknowledge successful completion.

5. Validate data sent from PremierOne CAD is correct.

6. Upon completion, sign and return the Project Milestone Document within ten (10) business days

7. Participate in the documentation of items that do not perform in accordance with the IFD and work with Motorola to develop remediation action(s).

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 92 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Motorola Deliverables - PremierOne and CommandCentral Interface Validation Demonstration Documented Interface Validation results including exceptions Completion Criteria - PremierOne Interface Validation Demonstration Interface Validation Demonstration completed and Customer written acknowledgement of functionality in accordance with IFDs
Payment Milestone 3 – Completion of Functional Validation Tasks Completion of Functional Validation tasks (included in Payment Milestone 3)

2.8 PREMIERONE AND COMMANDCENTRAL TRAINING

AND CONSULTATIVE SERVICES

2.8.1 Training
Training is conducted based on the quantities and terms that are specified in the Customer Training Plan. Training is made available via in-person training (PremierOne) and the Learning exPerience Portal (LXP) (PremierOne and CommandCentral). The LXP is accessed via Internet browser. Motorola will set up an instance of the LXP that provides autonomy to the agency utilizing LXP. This subscription service provides you with continual access to our library of on–line learning content and allows your users the benefit of learning at times convenient to them. Content is added and updated on a regular basis to keep information current. All Motorola tasks are completed remotely and enable the Customer to engage in training when convenient to the user.

LXP Administrators can add/modify users, run reports, and add/modify groups.

Motorola Responsibilities

1. Initial set up and addition of administrators.

2. Provide instruction to Customer LXP Administrators on:

A. Adding and maintaining users and groups.

B. Assigning courses and Learning Paths.

C. Running reports.

3. Delivery of in-person training courses as described in the Training Plan in Section 9.

4. Conduct up to eight (8) hours of remote consultation following PremierOne CAD Train the Trainer training to develop end-user training curriculum.

Customer Responsibilities

5. Provide Motorola with names (first and last) and emails of Customer LXP administrators.

6. Provide access to learningservices.motorolasolutions.com.

7. Complete LXP Administrator training.

8. Advise users of the availability of the LXP.

9. Add/modify users, run reports, and add/modify groups.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 93 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

10. Ensure attendance of personnel for in-person and virtual training courses in accordance with the project schedule and the number of students per course defined in the Training Plan.

2.8.2 CommandCentral Aware and Community Professional Consulting Services
Professional Consulting Services provide the Customer an opportunity to utilize Motorola subject matter experts as needed to address operational concerns: impromptu training, process re-engineering, or one on one personalized support.

Motorola Responsibilities

1. Conduct a discovery teleconference with Customer’s PM and/or team to understand the Customer needs prior to scheduling on-site service.

2. Provide Customer with a summary of the needs discussed during the teleconference that serve as the focus for the on-site service delivery.

3. Upon agreement of the focus of on-site service, schedule a mutually agreeable date for delivery of on-site service.

4. 4. Provide five days total spread across two trips of on-site service Monday through Friday, 8:00 am to 5:00 pm local time.

5. Provide Customer with a summary report of the activities completed as part of on-site service delivery.

Customer Responsibilities

1. Participate in the discovery teleconference and agree to objectives.

2. Schedule a mutually agreeable date for delivery of on-site service.

3. Coordinate availability of people or resources required for Motorola to fulfill the focus of on-site service.

Motorola Deliverables – Training and Consultative Services Virtual Training Courses
Access to and instruction for LXP
CommandCentral Aware Consultative Services
Completion Criteria - Training and Consultative Services Conclusion of and Customer acknowledgement of Motorola provided LXP Administrator instruction, in - person and virtual courses, and CommandCentral consultative services, per the Training Plan.

Payment Milestone 4 – Completion of Training Plan
Completion of training included in the Training Plan (Payment Milestone 4)

2.8.3 CommandCentral Investigate Professional Consulting Services Motorola Consulting Services provides the Customer an opportunity to use Motorola subject matter experts to address operational concerns or implementation of strategic initiatives. The full scope of consultative services will be determined during the discovery session between Motorola and the Customer. Certain consultative services are required as part of this offer while other services, outlined Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 94 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

in the following solution specific tables, are selected and customized to meet the needs of the Customer.

Motorola Responsibilities

1. Conduct discovery teleconference with the Customer to understand goals and objectives for the product as well as strategic initiatives.

2. Conduct a three (3) day on-site review of day-to-day operational use of Investigate to discover how the functional areas are utilizing the solution. Includes on-the-job training for efficient use and recommendations for optimizing. A briefing will be conducted at the end of the day to provide an update on information exchanged, activities planned, and any additional actions needed.

3. Provide Customer with an After-Action Report of the activities completed and next-step recommendations.

4. Conduct an after visit teleconference with Customer’s point of contact to outline the Customer’s priorities according to the After-Action Report.

5. Coordinate with Customer the work that needs to be completed and designate the appropriate owner of the activity.

Customer Responsibilities

1. Participate in the discovery teleconference and agree to objectives.

2. Schedule mutually agreeable dates for delivery of on-site service.

3. Coordinate availability of people or resources required for Motorola to fulfill the focus of on-site service.

4. Confirm Customer end-users have completed required training prior to on-site service.

5. Participate in the after visit teleconference and collaborate on priorities and work items to be delivered.

Motorola Deliverables – Training and Consultative Services CommandCentral Aware Consultative Services
After-Action Report
Completion Criteria - Training and Consultative Services Delivery of After-Action Report and completion of teleconference post the on-site visit.

2.9 PREMIERONE CAD AND COMMANDCENTRAL GO
LIVE
The transition to live operations to Motorola’s PremierOne CAD system is a team approach. Motorola will assist the Customer in the transition of live operations from the Customer’s legacy solution to the PremierOne System. Motorola will work with the Customer to confirm the PremierOne System Go Live date and time.

The services included in this Agreement are based on a single Go Live event of PremierOne CAD and Mobile.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 95 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

2.9.1 PremierOne Go Live Planning
Motorola will work with the Customer to develop a detailed Cutover Plan. This plan includes the following information:
• Motorola and Customer resources and staffing required • Pre-cutover tasks/activities that need to be performed leading up to the Go Live event • Readiness review meetings
• Contingency/roll-back plans
• Cutover tasks and responsibilities during and after the Go Live event • Post Go Live event support resources and schedules
• Issue reporting process
• Escalation process
Motorola Responsibilities:

1. Facilitate meetings with Customer staff to develop and document the Cutover Plan.

Customer Responsibilities:

1. Coordinate the participation of Customer technical and operational staff in cutover planning and development and documentation of the Cutover Plan.

Motorola Deliverables - PremierOne Go Live Planning
Deliver PremierOne Cutover Plan

2.9.2 Motorola Support Engagement
As part of go live planning, the Motorola Project Manager will complete a Customer Support Plan (included in Section 10 of these Ordering Documents) that includes Customer contact information and information required for remote access to the system. Motorola will schedule a Support Engagement meeting between the Project Managers, the Customer Support Advocate (“CSA”), the Focal Support Technician and the Customer’s project team representatives. The CSA will review the Customer Support Plan with the Customer, including the process for obtaining support and the contact information.

Motorola Responsibilities:

1. Create Customer Solution Support Plan

2. Facilitate Support Engagement Meeting
Customer Responsibilities:

1. Coordinate the participation of Customer technical and operational staff in the Support Engagement Meeting
Motorola Deliverables - Support Engagement
Updated Customer Support Plan
Completion Criteria - Support Engagement
Completion of Support Engagement Meeting
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 96 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

2.9.3 CommandCentral Aware and Community Production Use Following the completion of the functional demonstration of CommandCentral Aware and Community, the Customer may commence using CommandCentral Solution for all purposes including production use.

2.9.4 CommandCentral Investigate Production Use
Following the completion of the activation of CommandCentral Investigate, it is deemed available for all purposes including production use.

2.9.5 PremierOne Go Live Event
The transition to production use of the PremierOne solution will be conducted according to the Cutover Plan.

The Go Live event represents the transition to the Motorola Solutions Support organization in accordance with the Cutover Plan.

Motorola will provide Go Live support as listed in the cutover Plan. A summary of the applicable Go Live support services are described below:
• CAD Go Live Support includes one (1) CAD Application Specialist per twelve (12) hour shift to provide 24-hour support at one (1) location for up to three (3) days. A third CAD Application Specialist will be available for up to thirty-six (36) hours over three (3) days to be deployed as mutually agreed upon.

Motorola Responsibilities:

1. Work with Customer to schedule the date and time for the go live event

2. Execute the Cutover Plan

3. Provide on-site resources to support dispatch and mobile operations and address questions.

Customer Responsibilities:

1. Schedule and coordinate end user participation in the live operations cutover

2. Perform and support the cutover activities defined in the Cutover Plan

3. Provide technical and operational support for the supervision and monitoring of CAD and Mobile end users 24/7 beyond Motorola onsite support

4. Inform Customer staff about the Customer Solution Support Plan and the process to contact Customer Support.

Completion Criteria - PremierOne Go Live Event
Completion of Go Live Activities
Live PremierOne system
 Payment Milestone 5 – Completion of Go-Live Activities Completion of Go Live activities such that the City has full use of a PremierOne CAD System and associated interfaces (Payment Milestone 5)
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 97 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

2.9.6 Ninety (90) Day Reliability Period and Final System Acceptance A 90-day Reliability Period commences at Go Live as specified in the Agreement.

Payment Milestone 6 – Completion of Reliability Period and Final System Acceptance Completion of Reliability Period and Final System Acceptance (Payment Milestone 6)

2.10 PROJECT CLOSURE
Project Closure involves the steps to close the project and transition the PremierOne System from the delivery team to Customer Support.

2.10.1 Transition to Support
The system will transition to the support phase of the Agreement per the terms and conditions of the applicable Agreements and Customer Support Plan.

2.11 Appendix A - PremierOne CAD File Build

2.11.1 Incident Types
The City of Carlsbad will not be implementing the NENA standard Incident Types. The Customer will prepare their recommendations for the Incident Types they want to implement and maintain. The Customer will have the required Incident Types available prior to the provisioning class. Motorola will provide provisioning training and experienced based recommendations.

Codefile Item Global Code
Table

NENA/APCO
Standard
Customer
Provided
List and Statute Management
Article Type X NCIC
City X NCIC
Country List X NCIC
Eye Color Description X NCIC
Gender Description X NCIC
Gun Make X NCIC
Hair Color Description X NCIC
Person Build X NCIC
Person Race Description X NCIC
Person Suffix X NCIC
License Plate Type X NCIC
Skin Tone X NCIC
State List X NCIC
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 98 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Codefile Item Global Code
Table

NENA/APCO
Standard
Customer
Provided
Vehicle Color X NCIC
Vehicle Make X NCIC
Vehicle Model X NCIC
Vehicle Style X NCIC
Vehicle Type X
Agency Type Standard
Agency Name X
Plans -Response/ Active Plans X
Permissions
Agency - Permissions X
Roles - Permissions X
Resources - Personnel
Personnel X
Resources - Device ID’s
Devices/Workstation ID’s X
Unit Recommendations - Agency Type Level
Response IDs X
Incident Management
Modifying Circumstances APCO
Incident Status - Common NENA
Incident Source Call Origination NENA
Common Disposition Code NENA
Person Role Standard
Agency Role Standard
Incident Response Factors APCO
Coverage Groups X
Premise Hazard Types Standard
Premise Hazard Records X
Jurisdiction
Area/Beat/Sectors X
Location X
Station Names X
Unit Recommendations
Response Category X
Resources
Resource Attribute (Capability/Skill ) NENA
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 99 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Codefile Item Global Code
Table

NENA/APCO
Standard
Customer
Provided
Resource Type NENA
Vehicle ID X
Unit Recommendations
Vehicle Relationship Type NENA
Run Card X
Unit Management
Primary Unit Status - Common Standard
Secondary Unit Status - Common Standard
Unit ID - Optional X
Unit Pre-Assignments X
Status Monitors Standard
Command Lines Standard

2.12 Appendix B - PremierOne CAD/Mobile Standard
Reports
This table lists the standard reports that are provided with PremierOne CAD/Mobile.

Report Input Parameters Output
CAD Reports
Abandoned Call
Summary
Date Range, Disposition,
User ID, Phone Number
Provides the time the abandoned call record was
created, the trunk/line on which the call was
received, the phone number of the caller,
Disposition, elapsed time of the call, the call taker’s User ID and Workstation ID.

Average Response Times
by Incident Type
Date Range, Agency Provides Average Response times (At Scene - Incident Create Time) by Incident Type.

BOLO Messages Date Range, Sender
Agency ID, Device ID,
Sender ID, Group By
(Agency-, Device-,
Sender ID)
Provides a record of BOLO Messages sent:

Sender ID, Device ID, Sent On, Recipient(s), Size,
Status, Attachments. Ability to view content
(Details).

Drill down for the following:

BOLO Message
Attachments
N/A Provides a list of BOLO Message attachments:

Sender ID, Sent On, Recipients, Attachment
Name, and Size
BOLO Message Detail
Report
N/A Lists all fields of BOLO messages, organized by
Summary, Subject and Vehicle information
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 100 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Report Input Parameters Output
Calls For Service Date Range (Year) Lists the E911 Call Count, by month for year(s).

Drill down for the following:

Calls For Service Daily N/A Lists the E911 call count, daily for month.

Calls For Service Hourly N/A Lists the E911 call count, hourly by day of week.

Calls For Service Weekly N/A Lists the E911 call count, by week for each month.

Change Account Password
Report
N/A Provides a list of account password change
incidents and whether they were a success or a
failure.

Incident Comments Agency ID, Max Records,
Date Range, Call sign,
Office ID, Address,
Location Name,
Comment Text
Lists the comment text for the input parameters.

For comments, a minimum of three characters are
required. Incident comments are returned in the
order of relevancy.

NOTE: The search for incident comments
is a full text search, and not a string
match; this is the same search
method used by most web
browsers. For example, ban does
not return banana. You can,
however, add specific words to the
SQL database dictionary. Full text
searches include plurals.

Incident Details N/A Provides incident details: General Incident information, Location, and Caller information, Time
Stamps, Assigned Units, Assigned Personnel,
Comments, and Changes.

Incident Group By Date Range, Agency Provides an incident summary, with incidents grouped by type: Incident Type, Incident Number,
Incident Date, Priority, Incident Disposition,
Assigned Units, and Assigned Officers.

Incident Summary Date Range, Agency Provides incident summary information: Incident #, Create Date/time, Duration (create to close),
I_type, Priority, Location, Dispo(s), Assigned
Unit(s), Assigned Officer(s). Links to Incident Detail
Report.

Incidents by Area Agency ID, area Shows all incidents occurring in a specified geographical area. For example, incidents in area
AR1.

Interface Query Summary User ID, User Agency ID,
Device ID, Group by,
Date range
Provides information on who ran which query, from
which device & when: User Agency ID, Device
Type,
Device ID, Query Name, Executed On Search
Parameters
Drill down for the following:

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 101 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Report Input Parameters Output
Interface Query Detail User ID, Device ID, Date
Range, User Agency ID,
Group by: Agency,
Device, User ID, Query
Type
Provides Query specific details: User ID, Agency
ID,
Device ID, Device. Query Name, Submitted On
Search Parameters, Response(s): Database,
Code,
Received On, Hit Message
Logon and Logoff Agency ID, User ID,
Device ID, Date Range,
Group by: Date, Device,
User ID,
Provides information on who logged in when and
how many times: Date, User ID, Device ID Unit ID,
# of
Logon Attempts, # of Valid Logons, # of Number
Logoffs
Master Incident Date range, agency ID,
Incident Type, Beat,
Current Disposition,
Priority, Call Source, Call
sign, Officer ID, Address,
Location Name
Provides incident summary information for the input
criteria. The following information displays: Incident
Number, Address, Building/Apt, Location Name,
Date,
Report Number (RD), Source Code, Priority,
Incident Type, Primary Unit, Officer, Area, Beat,
And Disposition.

Master Response
Statistics
Agency ID, Date Range,
Incident Type, Priority,
Grouping
Provides the following information: Incident Date,
Priority, Start to Create, Start to Dispatch, Dispatch
to Enroute, Enroute to On Scene, Start to On
Scene, Start to Close, and Create to Close.

Message History Date Range, Agency ID Provides the messaging history for an agency. The following information is included: Sender ID,
Sender Name, Sent On, Recipient(s), Device ID,
Type, Size, and Subject.

Messaging Report –
Recipient
Sender, Agency ID,
Device ID, Sender ID
(All), Date Range
Provides information on messages received by
specific user.

Drill down for the following:

Message details Provides the specific message
Messaging Report –
Sender
Sender Agency ID-,
Device ID-, Sender ID-
(All), Date Range (-7 day)
pre populated. Ability to
specify message size
limits. Group by Sender-,
Device-, Agency ID.

Lists who sent messages and who they sent them
to. You can select sender ID, Device ID (one,
many, all).

Drill down for the following:

Message details Provides the specific message
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 102 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Report Input Parameters Output
Messaging Summary User Agency ID, User ID
(one, many, all), date
range
List message statistics: how many messages
received, sent, deleted, & message size by users
over a time range
Phone Number Lookup Date Range, Agency,
Phone Number
Provides: Time, Action, Direction, Agent, Position,
Location
Provisioning Device Agency ID, Device Type Lists all devices & device properties as provisioned in the system. Grouped by Device Type (Device
Type, Device Name, Make, Serial Number,
Description)
Provisioning Personnel Agency ID. Provides ability
to search by: User ID,
FirstName, LastName.

Lists LastName, FirstName, User ID of all
personnel provisioned in system. Drill through to
Personnel Details Report (Work, Roles, Resource
Assignments, Personal & Contacts).)
Provisioning Vehicle Agency ID, Vehicle Type.

Provides ability to select
Vehicle Type (one, many,
all)
Lists all vehicles provisioned in system by Vehicle
Type: Vehicle Code, Description, License Plate,
Odometer, Equipment, Type Equipment ID,
Capability
Purge Schedule Agency ID, Database
Type, Date Range
Provides schedule of records to be purged within
date range
Purged Premise Hazard Agency ID, Date Range Lists deleted Premise Hazard Records within date range.

Purged Records History Agency ID, Database
Type, Date Range
Lists purged records within date range
ReportingDW Schema Table or View Name,
Field Name, Show Empty
Tables, Only Show
Commonly Used Tables
and Views.

Lists RDW tables and views based on filters
selected.

Roles and Privileges Agency ID, Role Lists roles and assigned permissions Terminal Logon Agency ID, Device ID,
Date Range
Lists failed login attempts by device type and
device ID.

Users and Corresponding
Roles
Agency ID, Last, First
Name
Lists users and their assigned roles
Mobile Reports
Mobile Query Report - One
report with options to
search by:

VIN Agency ID, VIN, Date
Range, Search Text
Lists all queries run on a particular VIN during a
date/ time range.

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 103 of 372
The City of Carlsbad, CA
Change Order #2 Attachment B and/or Exhibit A

Report Input Parameters Output
Person Agency ID, Person, Date
Range, Search Text
Lists all queries run on a particular Person during a
date/time range.

Plate Agency ID, Plate, Date
Range, Search Text
Lists all queries run against a particular Plate
during a date/time range.

Officer Activity Agency ID, User ID, Date
Range
Shows all incident, query, and messaging activity for
a particular officer during a date/time range.

Unit Officer Agency ID, Date Range Provides breakdown of time (and % time) spent by Units & Officers on each status (# of Incidents,
Assigned Officers, Unit Status (i.e. en-route, on
scene, Break, Dispatched etc.), Total Time Spent
in Each Status, % Time in Status)

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 104 of 372
The City of Carlsbad, CA November 20, 2024
Change Order #2 Attachment B and/or Exhibit A
Cost Summary

Section 3
Cost Summary
Please reference Motorola’s Cost Proposal on the following pages.

3.1 Pricing Summary
Description Price ($) After
Discount
Total Not To Exceed One Time Cost Based on SOW **** (Excluding Options) Includes Year 1 of Application Software Subscription (PremierOne CAD, Mobile, CommandCentral Aware, CommandCentral Investigate Plus)
(50 Premier One CAD Named Users, 175 Mobile Named Users, 175 Command Central Aware Named Users, 115 CommandCentral Investigate Users, 200 Learning Experience Portal Users and all licensing and services necessary for Disaster Recovery solution )
$1,065,179
Total Annual Recurring Costs ***(Excluding Options) Years 2-6 Includes Application Software Subscription (PremierOne CAD, Mobile, CommandCentral Aware, CommandCentral Investigate Plus)
(50 Premier One CAD Named Users, 175 Mobile Named Users, 175 Command Central Aware Named Users, 115 CommandCentral Investigate Plus Users, 200 Learning Experience Portal Users and all licensing and services necessary for Disaster Recovery solution )
$791,441

TOTAL SYSTEM
CAD/Mobile/Aware/Options (Years 1-6)
$1,856,620
***Includes four (4) Summit User Group Registrations Annually ****The Total Not to Exceed price is for a 20-month delivery schedule. For each month project is finished under 18 months, Motorola will credit $13,334 per month on the following years annual recurring cost invoice
The following Options Available for Purchase have been included in the “all in” offer at no additional cost.
• Legacy Query Interface
• PremierOne CAD Radio PTT Interface
• CommandCentral Investigate Plus
Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 105 of 372
The City of Carlsbad, CA November 20, 2024
Change Order #2 Attachment B and/or Exhibit A
Cost Summary

3.2 Detail Pricing
Description Price ($) After
Discount
Motorola will provide:
▪ The software subscriptions listed in Section 1.5.1 of the Solution Description and the equipment described in Section 2.4.1.1 of the Statement of Work and Section 7

Included

#2-RapidSOS Integration: Implementation / Installation Services Included Remove DORS Interface (Incident Create and Query) Included 90-Day Reliability Period Included
Disaster Recovery Solution Included
Total Annual Recurring Costs (24/7) for Years 7-9
Year 7 $180,000
Year 8 $198,000
Year 9 $217,800

Total annual recurring costs include Application Software Subscriptions for PremierOne CAD, Mobile, CommandCentral Aware, CommandCentral Analytics Plus (50 PremierOne CAD Named Users, 175 Mobile Named Users, 175 CommandCentral Aware Named Users, 115 CommandCentral Analytics Plus Users, 200 Learning Experience Portal Users and all licensing and services necessary for Disaster Recovery solution)
$595,800
Total Pricing Years 1-6

Total Pricing Years 7-9
$1,856,620

$595,800
Agreement Total $2,452,419

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 106 of 372
The City of Carlsbad, CA November 20, 2024
Change Order #2 Attachment B and/or Exhibit A
Payment Schedule

Section 4
Payment Schedule

4.1 One-time Payment Milestones
The payment milestones are based on the total of $1,065,179 Consisting of:

Total Not To Exceed One Time Cost in Section 3.1 $1,065,179

2. 10% Upon Approval of Project Plan $106,518

3. 10% Upon Completion of Software Installation of all PremierOne CAD system equipment in sections 2.4.1 PremierOne Hardware and Environment and 2.4.5 CAD Client Installation $106,518

4. 20% Upon Completion of Functional Testing Validation tasks included in sections 2.4.6 Functional Validation and 2.7.1 Interface Validation $213,036

5. 20% Upon Completion of Training as specified in Section 9 PremierOne Training Plan $213,036

6. 20% Upon Completion of Go-Live activities such that the city has full use of a Premier One CAD System and associated interfaces $213,036

7. 20% Upon Final System Acceptance as defined in the Agreement $213,036 Years 2-6 Payments
Item Recurring
Cost Year 1
Recurring
Cost Year 2
Recurring
Cost Year 3
Recurring
Cost Year 4
Recurring
Cost Year 5
Recurring
Cost Year 6
Application Software
Subscription
(PremierOne CAD,
Mobile,
CommandCentral
Aware,
CommandCentral
Investigate Plus and
Disaster Recovery)
First Year
subscription
included in
One-Time
Costs
$158,288 $158,288 $158,288 $158,288 $158,289
Total Annual
Recurring Costs
(Excluding
Options)
$158,288 $158,288 $158,288 $158,288 $158,289

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 107 of 372
The City of Carlsbad, CA November 20, 2024
Change Order #2 Attachment B and/or Exhibit A
Payment Schedule

Years 7-9 Payments
Item Recurring
Cost Year 7
Recurring
Cost Year 8
Recurring
Cost Year 9
Application Software Subscription (PremierOne
CAD, Mobile, CommandCentral Aware,
CommandCentral Investigate Plus and Disaster
Recovery)

$180,000

$198,000

$217,800

Remaining Annual Payments by Fiscal Year (Estimated)
Item FY 24-25 FY 25-26 FY 26-27 FY 27-28 FY 28-29 FY 29-30 FY 30-31 One Time
Payment
Milestones
(Estimated)

$426,072

$639,107

Application
Software
Subscription
(PremierOne
CAD, Mobile,
CommandCentral
Aware,
CommandCentral
Investigate Plus
and Disaster
Recovery)
$158,288 $158,288 $158,288 $158,288 $158,288
Total Fiscal Year
Payment

$426,072

$639,107
$158,288 $158,288 $158,288 $158,288 $158,288

Docusign Envelope ID: 0BEC84EE-8EC1-4B8A-8EEE-4B35F046186A Feb. 4, 2025
Item #3 Page 108 of 372
The City of Carlsbad, CA November 20, 2024
Change Order #2 Attachment B and/or Exhibit A
Project Schedule and Personnel