Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Home
My WebLink
About
Motorola Solutions Inc; 2022-05-12;
Attachment A May 10, 2022 Item #11 Page 309 of 604 DocuSign Envelope ID: AB2013B4-94BF-480C-8860-74DCD9D59AF5 Master Customer Agreement This Master Customer Agreement (the "MCA") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and the entity set forth in the signature block below ("Customer''). Motorola and Customer will each be referred to herein as a "Party" and collectively as the "Parties". This Agreement (as defined below) is effective as of the date of the last signature (the "Effective Date"). 1. Agreement. 1.1. Scope: Agreement Documents. This MCA governs Customer's purchase of Products (as defined below) and Services (as defined below) from Motorola. Additional terms and conditions applicable to specific Products and Services are set forth in one or more addenda attached to this MCA (each an "Addendum", and collectively the· "Addenda"). In addition, the Parties have agreed upon the Cost Summary, Payment Schedule, Solution Description, Statement of Work, Project Schedule, Training Plan, Maintenance and Support Agreement (and exhibits) and Motorola's response to the City's RFP and other ordering documents setting forth the Products and Services to be purchased by Customer and provided by Motorola and additional rights and obligations of the Parties (the "Ordering Documents"). To the extent required by applicable procurement law, a proposal submitted by Motorola in response to a competitive procurement process will be included within the meaning of the term Ordering Documents. This MCA, the Addenda, and any Ordering Documents collectively form the Parties' "Agreement". 1.2. Order of Precedence. Each Addendum will control with respect to conflicting terms in the MCA, but only as applicable to the Products and Services described in such Addendum. Each Ordering Document will control with respect to conflicting terms in the MCA or any Addenda, but only as applicable to the Products and Services described on such Ordering Document. Among the Ordering Documents, later dated documents take precedence over earlier dated documents. 2. Products and Services. 2.1. Products. Motorola will (a) sell hardware provided by Motorola ("Equipment'), (b) license software which is either preinstalled on Equipment or installed on Customer-Provided Equipment (as defined below) and licensed to Customer by Motorola for a perpetual or other defined license term ("Licensed Software"), and (c) license cloud-based software as a service products and other software which is either preinstalled on Equipment or installed on Customer-Provided Equipment, but licensed to Customer by Motorola on a subscription basis ("Subscription Software") to Customer, to the extent each is set forth in an Ordering Document, for Customer's own use in accordance with this Agreement. The Equipment, Licensed Software, and Subscription Software shall collectively be referred to herein as "Products", or individually as a "Product'. At any time during the Term (as defined below), Motorola may substitute, with Customer's approval, any Products at no cost to Customer, if the substitute is substantially similar to the Products set forth in the applicable Ordering Documents. 2.2. Services. 2.2.1. Motorola will provide services related to purchased Products ("Services"), to the extent set forth in an Ordering Document. 2.2.2. Integration Services: Maintenance and Support Services. If specified in an Ordering Document, Motorola will provide, for the term of such Ordering Document, (a) design, deployment, and integration Services in order to design, 1 May 10, 2022 Item #11 Page 310 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9D59AF5 install, set up, configure, and/or integrate the applicable Products at the applicable locations ("Sites"), agreed upon by the Parties ("Integration Services"), or (b) break/fix maintenance, technical support, or other Services (such as software integration Services) ("Maintenance and Support Services"), each as further described in the applicable statement of work. Maintenance and Support Services and Integration Services will each be considered "Services", as defined above. 2.2.3. Service Ordering Documents. The Fees for Services will be set forth in an Ordering Document and any applicable project schedules. A Customer point of contact will be set forth in the applicable statement of work for the Services. 2.2.4. Service Completion. Unless otherwise specified in the applicable Ordering Document, Services described in an Ordering Document will be deemed complete upon Motorola's performance of all Services listed in such Ordering Document ("Service Completion Date"); provided, however, that Maintenance and Support Services may be offered on an ongoing basis during a given Ordering Document term, in which case such Maintenance and Support Services will conclude upon the expiration or termination of such Ordering Document. 2.3. Non-Preclusion. To the extent permitted by law, if, in connection with the Products and Services provided under this Agreement, Motorola makes recommendations, including a recommendation to purchase other products or services, nothing in this Agreement precludes Motorola from participating in a future competitive bidding process or otherwise offering or selling the recommended products or other services to Customer. 2.4. Customer Obligations. Customer will ensure that information Customer provides to Motorola in connection with receipt of Products and Services are accurate and complete in all material respects. Customer will make decisions within a reasonable time and obtain any required management or City Council approvals that are reasonably necessary for Motorola to provide the Products and Services and perform its other duties under this Agreement. Unless the applicable Ordering Document states otherwise, Motorola may rely upon and is not required to evaluate, confirm, reject, modify, or provide advice concerning any assumptions or Customer information, decisions, or approvals described in this Section. If any assumptions in the Ordering Documents or information provided by Customer prove to be incorrect, or if Customer fails to perform any of its material obligations under this Agreement, Motorola's ability to perform its obligations may be impacted and changes to the Agreement, including the scope, Fees, and performance schedule may be required. 2.5. Documentation. Products and Services may be delivered with documentation for the Equipment, software Products, or data that specifies technical and performance features, capabilities, users, or operation, including training manuals, and other deliverables, such as reports, specifications, designs, plans, drawings, analytics, or other information (collectively, "Documentation"). Documentation is and will be owned by Motorola, unless otherwise expressly agreed in an Addendum or Ordering Document that certain Documentation will be owned by Customer. Motorola hereby grants Customer a limited, royalty-free, worldwide, non-exclusive license to use the Documentation solely for its internal business purposes in connection with the Products and Services. 2.6. Motorola Tools and Equipment. As part of delivering the Products and Services, Motorola may provide certain tools, equipment, models, and other materials of its own. Such tools and equipment will remain the sole property of Motorola unless they are to be purchased by Customer as Products and are explicitly listed on an Ordering Document. 2 May 10, 2022 Item #11 Page 311 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 2.7. Authorized Users. Customer will ensure its employees and Authorized Users comply with the terms of this Agreement and will be liable for all acts and omissions of its employees and Authorized Users. Customer is responsible for the secure management of Authorized Users' names, passwords and login credentials for access to Products and Services. "Authorized Users" are Customer's employees or full-time contractors engaged for the purpose of supporting the Products and Services that are not employees, contractors or competitors of Motorola, and the entities (if any) specified in an Ordering Document or otherwise approved by Motorola in writing (email from an authorized Motorola signatory accepted), which may include affiliates or other Customer agencies. 2.8. Export Control. Customer, its employees, and any other Authorized Users will not access or use the Products and Services in any jurisdiction in which the provision of such Products and Services is prohibited under applicable laws or regulations (a "Prohibited Jurisdiction"), and Customer will not provide access to the Products and Services to any government, entity, or individual located in a Prohibited Jurisdiction. Customer represents and warrants that (a) it and its Authorized Users are not named on any U.S. government list of persons prohibited from receiving U.S. exports, or transacting with any U.S. person; (b) it and its Authorized Users are not a national of, or a company registered in, any Prohibited Jurisdiction; (c) Customer will not permit its Authorized Users to access or use the Products or Services in violation of any U.S. or other applicable export embargoes, prohibitions or restrictions; and (d) Customer and its Authorized Users will comply with all applicable laws regarding the transmission of technical data exported from the U.S. and the country in which Customer, its employees, and the Authorized Users are located. 2.9. Change Orders. Unless a different change control process is agreed upon in writing by the Parties, a Party may request changes to an Addendum or an Ordering Document by submitting a change order to the other Party (each, a "Change Order"). Change Orders are effective and binding on the Parties only upon execution of the Change Order by an authorized representative of both Parties. If an executed Change Order causes an increase or decrease in the Products or Services, the Parties by means of the Change Order will make appropriate adjustments to the Fees, project schedule, or other matters. 3. Term and Termination. 3.1. Term. The term of this MCA ("Term") will commence on the Effective Date and continue until six (6) months after the later of (a) the termination, expiration, or discontinuance of services under the last Ordering Document in effect, or (b) the expiration of all applicable warranty periods, unless the MCA is earlier terminated as set forth herein. The applicable Addendum or Ordering Document will set forth the term for the Products and Services governed thereby. 3.2. Termination. Either Party may terminate the MCA or the applicable Addendum or Ordering Document if the other Party breaches a material obligation under the Agreement and does not cure such breach within thirty (30) days after receipt of notice of the breach or fails to produce a cure plan within such period of time. Each Addendum and Ordering Document may be separately terminable as set forth therein. 3.3. Suspension of Services. After reasonable notice and an opportunity to cure, Motorola may terminate or suspend any Products or Services under an Ordering Document if Motorola determines: (a) the related Product license has expired or has terminated for any reason; (b) the applicable Product is being used on a hardware platform, operating system, or version not approved by Motorola; (c) Customer fails to make any payments when due; or (d) Customer fails to comply with any of its other obligations or otherwise delays Motorola's ability to perform. 3 May 10, 2022 Item #11 Page 312 of 604 DocuSlgn Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 3.4. Effect of Termination or Expiration. Upon termination for any reason or expiration of this Agreement, an Addendum, or an Ordering Document, Customer and the Authorized Users will return or destroy (at Motorola's option) all Motorola Materials and Motorola's Confidential Information in their possession or control and, as applicable, provide proof of such destruction, except that Equipment purchased by Customer should not be returned. Notwithstanding the reason for termination or expiration, Customer must pay Motorola for Products and Services already delivered. Customer has a duty to mitigate any damages under this Agreement, including in the event of default by Motorola and Customer's termination of this Agreement. Upon termination, Customer may download Customer Data or may request a quotation to engage Motorola to provide such services to download Customer Data. 3.5. Termination for Convenience. Customer may terminate this Agreement or applicable Addendum or Ordering Document by providing sixty (60) days' written notice to Motorola. City will pay Motorola for Products delivered or Services satisfactorily performed up to the effective date. 4. Payment and Invoicing. 4.1. Fees. Fees and charges applicable to the Products and Services (the "Fees") will be as set forth in the applicable Addendum or Ordering Document. Changes in the scope of Services described in an Ordering Document may require an adjustment to the Fees due under such Ordering Document. If a specific invoicing or payment schedule is set forth in the applicable Addendum or Ordering Document, such schedule will apply solely with respect to such Addendum or Ordering Document. 4.2. Taxes. The Fees do not include any excise, sales, lease, use, property, or other taxes, assessments, duties, or regulatory charges or contribution requirements (collectively, "Taxes"), all of which will be paid by Customer, except as exempt by law, unless otherwise specified in an Ordering Document. If Motorola is required to pay any Taxes, Customer will reimburse Motorola for such Taxes within thirty (30) days after Customer's receipt of an invoice therefore. Customer will be solely responsible for reporting the Products for personal property tax purposes, and Motorola will be solely responsible for reporting taxes on its income and net worth. The City of Carlsbad is not subject to Taxes related to this Agreement. 4.3. Invoicing. Motorola will invoice Customer at the frequency set forth in the applicable Addendum or Ordering Document, and Customer will pay all invoices within thirty (30) days of the invoice date or as otherwise specified in the applicable Addendum or Ordering Document. Motorola may invoice electronically via email, and Customer agrees to receive invoices via email at the email address set forth in an Ordering Document. 5. Sites; Customer-Provided Equipment; Non-Motorola Content. 5.1. Access to Sites. Customer will be responsible for providing all necessary permits, licenses, and other approvals necessary for the installation and use of the Products and the performance of the Services at each applicable Site, including for Motorola to perform its obligations hereunder, and for facilitating Motorola's access to the Sites. · 5.2. Site Conditions. Customer will ensure that (a) all Sites are safe and secure, (b) Site conditions meet all applicable industry and legal standards (including standards promulgated by OSHA or other governmental or regulatory bodies), (c) to the extent applicable, Sites have adequate physical space, air conditioning, and other environmental conditions, electrical power outlets, distribution, equipment, connections, and telephone or other communication lines 4 May 10, 2022 Item #11 Page 313 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 (including modem access and interfacing networking capabilities), and (d) Sites are suitable for the installation, use, and maintenance of the Products and Services. 5.3. Site Issues. Motorola will have the right, with advance notice and Customer supervision, to inspect the Sites and advise Customer of any deficiencies or non-conformities with the requirements of this Section 5 -Sites; Customer-Provided Equipment; Non-Motorola Content. If Motorola or Customer identifies any deficiencies or non-conformities, Customer will promptly remediate such issues or the Parties will select a replacement Site. If a Party determines that a Site identified in an Ordering Document is not acceptable or desired, the Parties will cooperate to investigate the conditions and select a replacement Site or otherwise adjust the installation plans and specifications as necessary. A change in Site or adjustment to the installation plans and specifications may cause a change in the Fees or performance schedule under the applicable Ordering Document. 5.4. Customer-Provided Equipment. Certain components, including equipment and software, not provided by Motorola may be required for use of the Products and Services ("Customer- Provided Equipment"). Customer will be responsible, at its sole cost and expense, for providing and maintaining the Customer-Provided Equipment in good working order. Customer represents and warrants that it has all rights in Customer-Provided Equipment to permit Motorola to access and use the applicable Customer-Provided Equipment to provide the Products and Services under this Agreement, and such access and use will not violate any laws or infringe any third- party rights (including intellectual property rights). Customer (and not Motorola) will be fully liable for Customer-Provided Equipment, and Customer will immediately notify Motorola of any Customer-Provided Equipment damage, loss, change, or theft that may impact Motorola's ability to provide the Products and Services under this Agreement, and Customer acknowledges that any such events may cause a change in the Fees or performance schedule under the applicable Ordering Document. 5.5. Non-Motorola Content. In certain instances, Customer may be permitted to access, use, or integrate Customer or third-party software, services, content, and data that is not provided by Motorola (collectively, "Non-Motorola Content") with or through the Products and Services. If Customer accesses, uses, or integrates any Non-Motorola Content with the Products or Services, Customer will first obtain all necessary rights and licenses to permit Customer's and its Authorized Users' use of the Non-Motorola Content in connection with the Products and Services. Customer will also obtain the necessary rights for Motorola to use such Non-Motorola Content in connection with providing the Products and Services, including the right for Motorola to access, store, and process such Non-Motorola Content (e.g., in connection with Subscription Software), and to otherwise enable interoperation with the Products and Services. Customer represents and warrants that it will obtain the foregoing rights and licenses prior to accessing, using, or integrating the applicable Non-Motorola Content with the Products and Services, and that Customer and its Authorized Users will comply with any terms and conditions applicable to such Non-Motorola Content. If any Non-Motorola Content requires access to Customer Data (as defined below), Customer hereby authorizes Motorola to allow the provider of such Non-Motorola Content to access Customer Data, in connection with the interoperation of such Non-Motorola Content with the Products and Services. Customer acknowledges and agrees that Motorola is not responsible for, and makes no representations or warranties with respect to, the Non-Motorola Content (including any disclosure, modification, or deletion of Customer Da.ta resulting from use of Non- Motorola Content or failure to properly interoperate with the Products and Services). If Customer receives written notice that any Non-Motorola Content must be removed, modified, or disabled within the Products or Services, Customer will promptly do so as soon as reasonably practicable. Motorola will have the right to disable or remove Non-Motorola Content if Motorola believes a violation of law, third-party rights, or Motorola's policies is likely to occur, or if such Non-Motorola 5 May 10, 2022 Item #11 Page 314 of 604 DocuSign Envelope ID: A8201384-948F-480C-B860-74DCD9D59AF5 Content poses or may pose a security or other risk or adverse impact to the Products or Services, Motorola, Motorola's systems, or any third party (including other Motorola customers) after providing reasonable notice. Nothing in this Section will limit the exclusions set forth in Section 7.2 -Intellectual Property Infringement. 6. Representations and Warranties. 6.1. Mutual Representations and Warranties. Each Party represents and warrants to the other Party that (a) it has the right to enter into the Agreement and perform its obligations hereunder, and (b) the Agreement will be binding on such Party. 6.2. Motorola Warranties. Subject to the disclaimers and exclusions below, Motorola represents and warrants that (a) Services will be provided in a good and workmanlike manner and will conform in all material respects to the descriptions in the applicable Ordering Document; and (b) for a period of one hundred-eighty (180) days commencing upon the Service Completion Date for one-time Services, the Services will be free of material defects in materials and workmanship. Other than as set forth in subsection (a) above, recurring Services are not warranted but rather will be subject to the requirements of the applicable Addendum or Ordering Document. Motorola provides other express warranties for Motorola-manufactured Equipment, Motorola-owned software Products, and certain Services. Such express warranties are included in the applicable Addendum or Ordering Document. Such representations and warranties will apply only to the applicable Product or Service that is the subject of such Addendum or Ordering Document. 6.3. Warranty Claims; Remedies. To assert a warranty claim, Customer must notify Motorola in writing of the claim prior to the expiration of any warranty period set forth in this MCA or the applicable Addendum or Ordering Document. Unless a different remedy is otherwise expressly set forth for a particular warranty under an Addendum, upon receipt of such claim, Motorola will investigate the claim and use commercially reasonable efforts to repair or replace any confirmed materially non-conforming Product or re-perform any non-conforming Service, at its option. Such remedies are Customer's sole and exclusive remedies for Motorola's breach of a warranty. Motorola's warranties are extended by Motorola to Customer only, and are not assignable or transferrable. 6.4. Pass-Through Warranties. Notwithstanding any provision of this Agreement to the contrary, Motorola will have no liability for third-party software or hardware provided by Motorola; provided, however, that to the extent offered by third-party providers of software or hardware and to the extent permitted by law, Motorola will pass through express warranties provided by such third parties. 6.5. WARRANTY DISCLAIMER. EXCEPT FOR THE EXPRESS AND PASS THROUGH WARRANTIES IN THIS AGREEMENT, PRODUCTS AND SERVICES PURCHASED HEREUNDER ARE PROVIDED "AS IS" AND WITH ALL FAUL TS. WARRANTIES SET FORTH IN THE AGREEMENT ARE THE COMPLETE WARRANTIES FOR THE PRODUCTS AND SERVICES AND MOTOROLA DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND QUALITY. MOTOROLA DOES NOT REPRESENT OR WARRANT THAT USE OF THE PRODUCTS AND SERVICES WILL BE UNINTERRUPTED, ERROR-FREE, OR FREE OF SECURITY VULNERABILITIES, OR THAT THEY WILL MEET CUSTOMER'S PARTICULAR REQUIREMENTS. 7. Indemnification. 6 May 10, 2022 Item #11 Page 315 of 604 DocuSign Envelope ID: AB2013B4--94BF-4B0C-B860-74DCD9D59AF5 7.1. Mutual Indemnification. Subjectto the limitations Paragraphs 8.1 and 8.2, each Party shall defend, indemnify, and hold harmless the other Party (including its elected and appointed officials, officers, employees, agents, and affiliated or subsidiary entities) against any claim, loss or liability (including reasonable attorney fees) ("Claim") for personal injury, death, or direct damage to tangible property to the extent it is caused by the Party's negligence while performing its duties under of this Agreement. A Party's duties under this Section 7.1 -Mutual Indemnification are conditioned upon the other Party providing prompt written notification of the Claim and reasonable cooperation and assistance in the defense of the Claim. Nothing contained in this agreement shall be construed as a waiver of any immunities or defenses a Party may have under applicable provisions of the law. 7.2. Intellectual Property Infringement. Motorola will defend Customer against any third-party claim alleging that a Motorola-developed or manufactured Product or Service (the "Infringing Product") directly infringes a United States patent or copyright ("Infringement Claim"), and Motorola will pay all damages finally awarded against Customer by a court of competent jurisdiction. for an Infringement Claim, or agreed to in writing by Motorola in settlement of an Infringement Claim. Motorola's duties under this Section 7.2 -Intellectual Property Infringement are conditioned upon: (a) Customer promptly notifying Motorola in writing of the Infringement Claim; (b) Motorola having sole control of the defense of the suit and all negotiations for its settlement or compromise; and (c) Customer cooperating with Motorola and, if requested by Motorola, providing reasonable assistance in the defense of the Infringement Claim. 7.2.1 . If an Infringement Claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its option and expense: (a) procure for Customer the right to continue using the Infringing Product; (b) replace or modify the Infringing Product so that it becomes non-infringing; or (c) grant Customer (i) a pro-rated refund of any amounts pre-paid for the Infringing Product (if the Infringing Product is a software Product, i.e., Licensed Software or Subscription Software) or (ii) a credit for the Infringing Product, less a reasonable charge for depreciation (if the Infringing Product is Equipment, including Equipment with embedded software). 7.2.2. In addition to the other damages disclaimed under this Agreement, Motorola will have no duty to defend or indemnify Customer for any Infringement Claim that arises from or is based upon: (a) Customer Data, Customer-Provided Equipment, Non-Motorola Content, or third-party provided equipment, hardware, software, data, or other third-party provided materials; (b) the combination of the Product or Service with any products or materials not provided by Motorola 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, a Product or Service designed, modified, or manufactured in accordance with Customer's designs, specifications, guidelines or instructions; (d) a modification of the Product or Service by a party other than Motorola; (e) use of the Product or Service in a manner for which the Product or Service was not 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. 7.2.3. This Section 7.2 -Intellectual Property Infringement provides Customer's sole and exclusive remedies and Motorola's entire liability in the event of an Infringement Claim. For clarity, the rights and remedies provided in this Section 7 May 10, 2022 Item #11 Page 316 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCO9O59AF5 are subject to, and limited by, the restrictions set forth in Section 8 -Limitation of Liability below. 8. Limitation of Liability. 8.1 . DISCLAIMER OF CONSEQUENTIAL DAMAGES. EXCEPT FOR PERSONAL INJURY OR DEATH, MOTOROLA, ITS AFFILIATES, AND ITS AND THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, SUBCONTRACTORS, AGENTS, SUCCESSORS, AND ASSIGNS (COLLECTIVELY, THE "MOTOROLA PARTIES") WILL NOT BE LIABLE IN CONNECTION WITH THIS AGREEMENT (WHETHER UNDER MOTOROLA'S INDEMNITY OBLIGATIONS, A CAUSE OF ACTION FOR BREACH OF CONTRACT, UNDER TORT THEORY, OR OTHERWISE) FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES OR DAMAGES FOR LOST PROFITS OR REVENUES, EVEN IF MOTOROLA HAS BEEN ADVISED BY CUSTOMER OR ANY THIRD PARTY OF THE POSSIBILITY OF SUCH DAMAGES OR LOSSES AND WHETHER OR NOT SUCH DAMAGES OR LOSSES ARE FORESEEABLE. EXCEPT FOR PERSONAL INJURY OR DEATH, THE CUSTOMER, ITS AFFILIATES, AND ITS AND THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, SUBCONTRACTORS, AGENTS, SUCCESSORS, AND ASSIGNS (COLLECTIVELY, THE "CUSTOMER PARTIES") WILL NOT BE LIABLE IN CONNECTION WITH THIS AGREEMENT (WHETHER UNDER CUSTOMER'S INDEMNITY OBLIGATIONS, A CAUSE OF ACTION FOR BREACH OF CONTRACT, UNDER TORT THEORY, OR OTHERWISE) FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES OR DAMAGES FOR LOST PROFITS OR REVENUES, EVEN IF CUSTOMER HAS BEEN ADVISED BY MOTOROLA OR ANY THIRD PARTY OF THE POSSIBILITY OF SUCH DAMAGES OR LOSSES AND WHETHER OR NOT SUCH DAMAGES OR LOSSES ARE FORESEEABLE. 8.2. DIRECT DAMAGES. EXCEPT FOR PERSONAL INJURY OR DEATH, THE TOTAL AGGREGATE LIABILITY OF THE MOTOROLA PARTIES, WHETHER BASED ON A CLAIM IN CONTRACT OR IN TORT, LAW OR EQUITY, RELATING TO OR ARISING OUT OF THE AGREEMENT WILL NOT EXCEED THE FEES SET FORTH IN THE ORDERING DOCUMENT(S) UNDER WHICH THE CLAIM AROSE. NOTWITHSTANDING THE FOREGOING, FOR ANY SUBSCRIPTION SOFTWARE OR FOR ANY RECURRING SERVICES, THE MOTOROLA PARTIES' TOTAL LIABILITY FOR ALL CLAIMS RELATED TO SUCH PRODUCT OR RECURRING SERVICES IN THE AGGREGATE WILL NOT EXCEED THE TOTAL FEES PAID FOR SUCH SUBSCRIPTION SOFTWARE OR RECURRING SERVICES, AS APPLICABLE, DURING THE CONSECUTIVE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT FROM WHICH THE FIRST CLAIM AROSE. EXCEPT FOR PERSONAL INJURY OR DEATH, THE TOTAL AGGREGATE LIABILITY OF THE CUSTOMER PARTIES, WHETHER BASED ON A CLAIM IN CONTRACT OR IN TORT, LAW OR EQUITY, RELATING TO OR ARISING OUT OF THE AGREEMENT WILL NOT EXCEED THE FEES SET FORTH IN THE ORDERING DOCUMENT(S) UNDER WHICH THE CLAIM AROSE. NOTWITHSTANDING THE FOREGOING, FOR ANY SUBSCRIPTION SOFTWARE OR FOR ANY RECURRING SERVICES, THE CUSTOMER PARTIES'TOTAL LIABILITY FOR ALL CLAIMS RELATED TO SUCH PRODUCT OR RECURRING SERVICES IN THE AGGREGATE WILL NOT EXCEED THE TOTAL FEES PAID FOR SUCH SUBSCRIPTION SOFTWARE OR RECURRING SERVICES, AS APPLICABLE, DURING THE CONSECUTIVE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT FROM WHICH THE FIRST CLAIM AROSE. 8.3. · ADDITIONAL EXCLUSIONS. NOTWITHSTANDING ANY OTHER PROVISION OF THIS AGREEMENT, MOTOROLA WILL HAVE NO LIABILITY FOR DAMAGES ARISING OUT OF (A) 8 May 10, 2022 Item #11 Page 317 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74OCD9D59AF5 CUSTOMER DAT A, INCLUDING ITS TRANSMISSION TO MOTOROLA, OR ANY OTHER DA TA AVAILABLE THROUGH THE PRODUCTS OR SERVICES; (B) CUSTOMER-PROVIDED EQUIPMENT, NON-MOTOROLA CONTENT, THE SITES, OR THIRD-PARTY PROVIDED MATERIALS, OR THE COMBINATION OF PRODUCTS AND SERVICES WITH ANY OF THE FOREGOING UNLESS THE COMBINATION WAS ANTICIPATED IN THE ORDERING DOCUMENT(S) FOR THE PRODUCTS OR SERVICES; (C) LOSS OF DATA OR HACKING; (D) MODIFICATION OF PRODUCTS OR SERVICES BY ANY PERSON OTHER THAN MOTOROLA UNLESS AUTHORIZED BY MOTOROLA OR ANTICIPATED IN THE ORDERING DOCUMENT(S) FOR THE PRODUCTS OR SERVICES; (F) DATA RECOVERY SERVICES OR DATABASE MODIFICATIONS NOT PROVIDED BY MOTOROLA; OR (G) CUSTOMER'S OR ANY AUTHORIZED USER'S MATERIAL BREACH OF THIS AGREEMENT OR INTENTIONAL MISUSE OF THE PRODUCTS AND SERVICES. 8.4. Voluntary Remedies. Motorola is not obligated to remedy, repair, replace, or refund the purchase price for the disclaimed issues in Section 8.3 -Additional Exclusions above. 8.5. Statute of Limitations. Customer may not bring any claims against a Motorola Party in connection with this Agreement or the Products and Services more than one (1) year after the date of accrual of the cause of action. 9. Confidentiality. 9.1. Confidential Information. "Confidential Information" means any and all non-public information provided by one Party ("Discloser") to the other ("Recipient") that is disclosed under this Agreement in oral, written, graphic, machine recognizable, or sample form, being clearly designated, labeled or marked as confidential or its equivalent. With respect to Motorola, Confidential Information may include Documentation. In order to be considered Confidential Information, information that is disclosed orally must be identified as confidential at the time of disclosure and confirmed by Discloser by submitting a written document to Recipient within thirty (30) days after such disclosure. The written document must contain a summary of the Confidential Information disclosed with enough specificity for identification purpose and must be labeled or marked as confidential or its equivalent. 9.2. Obligations of Confidentiality. During the Term and for a period of three (3) years from the expiration or termination of this Agreement, Recipient will (a) not disclose Confidential Information to any third party, except as expressly permitted in this Section 9 -Confidentiality; (b) restrict disclosure of Confidential Information to only those employees (including, employees of any wholly owned subsidiary, a parent company, any other wholly owned subsidiaries of the same parent company), agents or consultants who must access the Confidential Information for the purpose of, and who are bound by confidentiality terms substantially similar to those in, this Agreement; (c) not copy, reproduce, reverse engineer, de-compile or disassemble any Confidential Information; (d) use the same degree of care as for its own information of like importance, but at least use reasonable care, in safeguarding against disclosure of Confidential Information; (e) promptly notify Discloser upon discovery of any unauthorized use or disclosure of the Confidential Information and take reasonable steps to regain possession of the Confidential Information and prevent further unauthorized actions or other breach of this Agreement; and (f) only use the Confidential Information as needed to fulfill its obligations and secure its rights under this Agreement. 9.3. Exceptions. Recipient is not obligated to maintain as confidential any information that Recipient can demonstrate by documentation (a) is publicly available at the time of disclosure or becomes available to the public without breach of this Agreement; (b) is lawfully obtained from a third party without a duty of confidentiality to Discloser; (c) is otherwise lawfully known to Recipient 9 May 10, 2022 Item #11 Page 318 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 prior to such disclosure without a duty of confidentiality to Discloser; or (d) is independently developed by Recipient without the use of, or reference to, any of Discloser's Confidential Information or any breach of this Agreement. Additionally, Recipient may disclose Confidential Information to the extent required by law, including a judicial or legislative order or proceeding. 9.4. Ownership of Confidential Information. All Confidential Information is and will remain the property of Discloser and will not be copied or reproduced without the express written permission of Discloser (including as permitted herein). Within ten (10) days of receipt of Discloser's written request, Recipient will return or destroy all Confidential Information to Discloser along with all copies and portions thereof, or certify in writing that all such Confidential Information has been destroyed. However, Recipient may retain (a) one (1) archival copy of the Confidential Information for use only in case of a dispute concerning this Agreement and (b) Confidential Information that has been automatically stored .in accordance with Recipient's standard backup or recordkeeping procedures, provided, however that Recipient will remain subject to the obligations of this Agreement with respect to any Confidential Information retained subject to clauses (a) or (b). No license, express or implied, in the Confidential Information is granted to the Recipient other than to use the Confidential Information in the manner and to the extent authorized by this Agreement. Discloser represents and warrants that it is authorized to disclose any Confidential Information it discloses pursuant to this Agreement. 10. Proprietary Rights; Data; Feedback. 10.1. Data Definitions. The following terms will have the stated meanings: "Customer Contact Data" means data Motorola collects from Customer, its Authorized Users, and their end users for business contact purposes, including marketing, advertising, licensing and sales purposes; "Service Use Data" means data generated by Customer's use of the Products and Services or by Motorola's support of the Products and Services, including personal information, product performance and error information, activity logs and date and time of use; "Customer Data" means data, information, and content, including images, text, videos, documents, audio, telemetry, location and structured data base records, provided by, through, or on behalf of Customer, its Authorized Users, and their end users through the use of the Products and Services. Customer Data does not include Customer Contact Data, Service Use Data, or information from publicly available sources or other Third-Party Data or Motorola Data; "Third-Party Data" means information obtained by Motorola from publicly available sources or its third party content providers and made available to Customer through the Products or Services; "Motorola Data" means data owned or licensed by Motorola; "Feedback" means comments or information, in oral or written form, given to Motorola by Customer or Authorized Users, including their end users, in connection with or relating to the Products or Services; and "Process" or "Processing" means any operation or set of operations which is performed on personal information or on sets of personal information, whether or not by automated means, such as collection, recording, copying, analyzing, caching, organization, structuring, storage, adaptation, or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. 10.2. Motorola Materials. Customer acknowledges that Motorola may use or provide Customer with access to software, tools, data, and other materials, including designs, utilities, models, methodologies, systems, and specifications, which Motorola has developed or licensed from third parties (including any corrections, bug fixes, enhancements, updates, modifications, adaptations, translations, de-compilations, disassemblies, or derivative works of the foregoing, whether made by Motorola or another party) (collectively, "Motorola Materials"). The Products and Services, Motorola Data, Third-Party Data, and Documentation, are considered Motorola Materials. Except when Motorola has expressly transferred title or other interest to Customer by way of an 10 May 10, 2022 Item #11 Page 319 of 604 DocuSign Envelope ID: AB201384-94BF--4B0C-B860-74DCD9D59AF5 Addendum or Ordering Document, the Motorola Materials are the property of Motorola or its licensors, and Motorola or its licensors retain all right, title and interest in and to the Motorola Materials (including, all rights in patents, copyrights, trademarks, trade names, trade secrets, know-how, other intellectual property and proprietary rights, and all associated goodwill and moral rights). For clarity, this Agreement does not grant to Customer any shared development rights in or to any Motorola Materials or other intellectual property, and Customer agrees to execute any documents and take any other actions reasonably requested by Motorola to effectuate the foregoing. Motorola and its licensors reserve all rights not expressly granted to Customer, and no rights, other than those expressly granted herein, are granted to Customer by implication, estoppel or otherwise. Customer will not modify, disassemble, reverse engineer, derive source code or create derivative works from, merge with other software, distribute, sublicense, sell, or export the Products and Services or other Motorola Materials, or permit any third party to do so. 10.3. Ownership of Customer Data. Customer retains all right, title and interest, including intellectual property rights, if any, in and to Customer Data. Motorola acquires no rights to Customer Data except those rights granted under this Agreement including the right to Process and use the Customer Data as set forth in Section 10.4 -Processing Customer Data below and in other applicable Addenda. The Parties agree that with regard to the Processing of personal information which may be part of Customer Data, Customer is the controller and Motorola is the processor, and may engage sub-processors pursuant to Section 10.4.3 -Sub-processors. 10.4. Processing Customer Data. Motorola Use of Customer Data. To the extent permitted by law, Customer grants Motorola and subcontractors designated within this agreement a right to use Customer Data to (a) perform Services and provide Products under the Agreement, and (b) analyze the Customer Data to operate, maintain, manage, and improve Motorola Products and Services for Customer. Customer Data shall not be used for demonstration or testing purposes for products, services and uses by Motorola or any subcontractor that is beyond the scope of products delivered as part of this agreement unless authorized in writing by Customer. Customer agrees that this Agreement, along with the Documentation, are Customer's complete and final documented instructions to· Motorola for the processing of Customer Data. Any additional or alternate instructions must be agreed to according to the Change Order process. Customer represents and warrants to Motorola that Customer's instructions, including ·appointment of Motorola as a processor or sub-processor, have been authorized by the relevant controller. 10.4.1. Collection, Creation, Use of Customer Data. Customer further represents and warrants that the Customer Data, Customer's collection, creation, and use of the Customer Data (including in connection with Motorola's Products and Services), and Motorola's use of such Customer Data in accordance with the Agreement, will not violate any laws or applicable privacy notices or infringe any third-party rights (including intellectual property and privacy rights). Customer also represents and warrants that the Customer Data will be accurate and complete, and that Customer has obtained all required consents, provided all necessary notices, and met any other applicable legal requirements with respect to collection and use (including Motorola's and its subcontractors' use) of the Customer Data as described in the Agreement. 10.4.2. Sub-processors. Customer agrees that Motorola may engage sub-processors who in turn may engage additional sub-processors to Process data in accordance with this Agreement. When engaging sub-processors, Motorola will enter into 11 May 10, 2022 Item #11 Page 320 of 604 DocuSign Envelope ID: AB201384-948F-4B0C-B860-74DCD9D59AF5 agreements with the sub-processors to bind them to data processing obligations to the extent required by law. 10.5_ Data Retention and Deletion. Except for anonymized Customer Data, as described above, or as otherwise provided under the Agreement, Motorola will delete all Customer Data following termination or expiration of this MCA or the applicable Addendum or Ordering Document, with such deletion to occur no later than one-hundred eighty (180) days following the applicable date of termination or expiration, unless otherwise required to comply with applicable law. Any requests for the exportation or download of Customer Data must be made by Customer to Motorola in writing before expiration or termination, subject to Section 13.9 -Notices. Motorola will have no obligation to retain such Customer Data beyond ·expiration or termination unless the Customer has purchased extended storage from Motorola through a mutually executed Ordering Document. 10.6. Service Use Data. Customer understands and agrees that Motorola may collect and use Service Use Data for its own purposes, including the uses described below. Motorola may use Service Use Data to (a) operate, maintain, manage, and improve existing products and services, (b) test products and services, (c) to aggregate Service Use Data and combine it with that of other users. Service Use Data may be not be disclosed to third parties unless expressly authorized by law and only with Customer's prior approval. 10.7. Third-Party Data and Motorola Data. Motorola Data and Third-Party Data may be available to Customer through the Products and Services. Customer and its Authorized Users may use Motorola Data and Third-Party Data as permitted by Motorola and the applicable Third-Party Data provider, as described in the applicable Addendum. Unless expressly permitted in the applicable Addendum or required by law, Customer will not, and will ensure its Authorized Users will not: (a) use the Motorola Data or Third-Party Data for any purpose other than Customer's internal business purposes; (b) disclose the data to third parties; (c) "white label" such data or otherwise misrepresent its source or ownership, or resell, distribute, sublicense, or commercially exploit the data in any manner; (d) use such data in violation of applicable laws; (e) remove, obscure, alter, or falsify any marks or proprietary rights notices indicating the source, origin, or ownership of the data; or (f) modify such data or combine it with Customer Data or other data or use the data to build databases. To the degree Motorola Data and Third-Party Data is required by law to be released or used, Customer will notify Motorola as soon as reasonably practicable. Additional restrictions may be set forth in the applicable Addendum. Any rights granted to Customer or Authorized Users with respect to Motorola Data or Third-Party Data will immediately terminate upon termination or expiration of the applicable Addendum, Ordering Document, or this MCA. Further, after providing reasonable notice and an opportunity to cure, Motorola or the applicable Third-Party Data provider may suspend, change, or terminate Customer's or any Authorized User's access to Motorola Data or Third-Party Data if Motorola or such Third-Party Data provider believes Customer's or the Authorized User's use of the data violates the Agreement, applicable law or Motorola's agreement with the applicable Third-Party Data provider. Upon termination of Customer's rights to use any Motorola Data or Third-Party Data, Customer and all Authorized Users will immediately discontinue use of such data, delete all copies of such data, and certify such deletion to Motorola. 10_8. Feedback. Any Feedback provided by Customer is entirely voluntary, and will not create any confidentiality obligation for Motorola, unless designated in writing as confidential by Customer. Motorola may use, reproduce, license, and otherwise distribute and exploit the Feedback without any obligation or payment to Customer or Authorized Users and Customer represents and warrants that it has obtained all necessary rights and consents to grant Motorola the foregoing rights. 12 May 10, 2022 Item #11 Page 321 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9D59AF5 10.9. Improvements; Products and Services. The Parties agree that, notwithstanding any provision of this MCA or the Agreement to the contrary, all fixes, modifications and improvements to the Services or Products conceived of or made by or on behalf of Motorola that are based either in whole or in part on the Feedback, Customer Data, or Service Use Data (or otherwise) are the exclusive property of Motorola and all right, title and interest in and to such fixes, modifications or improvements will vest solely in Motorola. Customer agrees to execute any written documents necessary to assign any intellectual property or other rights it may have in such fixes, modifications or improvements to Motorola. 11. Force Majeure; Delays Caused by Customer. 11.1. Force Majeure. Except for Customer's payment obligations hereunder, neither Party will be responsible for nonperformance or delayed performance due to events outside of its reasonable control. If performance will be significantly delayed, the affected Party will provide notice to the other Party, and the Parties will agree (in writing) upon a reasonable extension to any applicable performance schedule. 11.2. Delays Caused by Customer. Motorola's performance of the Products and Services will be excused for delays caused by Customer or its Authorized Users or subcontractors, or by failure of any assumptions set forth in this Agreement (including in any Addendum or Ordering Document). In the event of a delay under this Section 11.2 -Delays Caused by Customer, (a) Customer will continue to pay the Fees as required hereunder, (b) the Parties will agree (in writing via a mutually executed change order or new or additional Ordering Documents) upon a reasonable extension to any applicable performance schedule, and (c) Customer will compensate Motorola for its out-of-pocket costs incurred due to the delay (including those incurred by Motorola's affiliates, vendors, and subcontractors) as agreed upon in a mutually executed change order. · 12. Disputes. The Parties will use the following procedure to resolve any disputes relating to or arising out of this Agreement (each, a "Dispute"): 12.1. Governing Law. All matters relating to or arising out of the Agreement are governed by the laws of the State of California. 12.2. Negotiation; Mediation. Either Party may initiate dispute resolution procedures by sending a notice of Dispute ("Notice of Dispute") to the other Party. The Parties will attempt to resolve the Dispute promptly through good faith negotiations, including timely escalation of the Dispute to executives who have authority to settle the Dispute (and who are at a higher level of management than the persons with direct responsibility for the matter). If a Dispute is not resolved through negotiation, either Party may initiate mediation by sending a notice of mediation ("Notice of Mediation") to the other Party. The Parties will choose an independent mediator within thirty (30) days of such Notice of Mediation. Neither Party may unreasonably withhold consent to the selection of a mediator, but if the Parties are unable to agree upon a mediator, either Party may request that the American Arbitration Association nominate a mediator. Each Party will bear its own costs of mediation, but the Parties will share the cost of the mediator equally. Each Party will participate in the mediation in good faith. All in person meetings under this Sectiori 12.2 - Negotiation; Mediation will take place virtually or in northern San Diego County, California, and all communication relating to the Dispute resolution will be maintained in strict confidence by the Parties. Notwithstanding the foregoing, any Dispute arising from or relating to Motorola's intellectual property rights will not be subject to negotiation or mediation in accordance with this Section, but instead will be decided by a court of competent jurisdiction, in accordance with Section 12.3 -Litigation, Venue, Jurisdiction below. 13 May 10, 2022 Item #11 Page 322 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 12.3. Litigation, Venue, Jurisdiction. If the Dispute has not been resolved by mediation within one hundred twenty (120) days from the Notice of Mediation, either Party may submit the Dispute exclusively to a court in San Diego County, California. Each Party expressly consents to the exclusive jurisdiction of such courts for resolution of any Dispute and to enforce the outcome of any mediation. 13. General. 13.1. Compliance with Laws. Each Party will comply with applicable laws in connection with the performance of its obligations under this Agreement, including that Customer will ensure its and its Authorized Users' use of the Products and Services complies with law (including privacy laws), and Customer will obtain any FCC and other licenses or authorizations (including licenses or authorizations required by foreign regulatory bodies) required for its and its Authorized Users' use of the Products and Services. After providing reasonable prior notice and the opportunity to cure, Motorola may, at its discretion, cease providing or otherwise modify Products and Services (or any terms related thereto in an Addendum or Ordering Document), in order to comply with any changes in applicable law. 13.2. Audit; Monitoring. Subject to CJIS compliance, Customer-approved Motorola personnel will have the right to monitor and audit use of the Products, which may also include access by Motorola to Customer Data and Service Use Data. Customer will provide notice of such monitoring to its Authorized Users and obtain any required consents, including individual end users, and will cooperate with Motorola in any monitoring or audit. Customer will maintain during the Term, and for two (2) years thereafter, accurate records relating to any software licenses granted under this Agreement to verify compliance with this Agreement. Motorola or a third party ("Auditor") may inspect Customer's and, as applicable, Authorized Users' premises, books, and records. Motorola will pay expenses and costs of the Auditor, unless Customer is found to be in violation of the terms of the Agreement, in which case Customer will be responsible for such expenses and costs 13.3. .Assignment and Subcontracting. Neither Party may assign or otherwise transfer this Agreement without the prior written approval of the other Party, which shall not be unreasonably withheld. Subject to the foregoing , this Agreement will be binding upon the Parties and their respective successors and assigns. 13.4. Waiver. A delay or omission by either Party to exercise any right under this Agreement will not be construed to be a waiver of such right. A waiver by either Party of any of the obligations to be performed by the other, or any breach thereof, will not be construed to be a waiver of any succeeding breach or of any other obligation. All waivers must be in writing and signed by the Party waiving its rights. 13.5. Severability. If any provision of the Agreement is found by a court of competent jurisdiction to be invalid, illegal, or otherwise unenforceable, such provision will be deemed to be modified to reflect as nearly as possible the original intentions of the Parties in accordance with applicable law. The remaining provisions of this Agreement will not be affected, and each such provision will be valid and enforceable to the full extent permitted by applicable law. 13.6. Independent Contractors. Each Party will perform its duties under this Agreement as an independent contractor. The Parties and their personnel will not be considered to be employees or agents of the other Party. Nothing in this Agreement will be interpreted as granting either Party the right or authority to make commitments of any kind for the other. This Agreement will not constitute, create, or be interpreted as a joint venture, partnership, or formal business organization of any kind. 14 May 10, 2022 Item #11 Page 323 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 13.7. Third-Party Beneficiaries. The Agreement is entered into solely between, and may be enforced only by, the Parties. Each Party intends that the Agreement will not benefit, or create any right or cause of action in or on behalf of, any entity other than the Parties. Notwithstanding the foregoing, a licensor or supplier of third-party software included in the software Products will be a direct and intended third-party beneficiary of this Agreement. 13.8. Interpretation. The section headings in this Agreement are included only for convenience The words "including" and "include" will be deemed to be followed by the phrase "without limitation". This Agreement will be fairly interpreted in accordance with its terms and conditions and not for or against either Party. 13.9. Notices. Notices required under this Agreement to be given by one Party to the other must be in writing and either personally delivered or sent to the address provided by the other Party by certified mail, return receipt requested and postage prepaid ( or by a recognized courier service, such as FedEx, UPS, or DHL), and will' be effective upon receipt. 13.10. Cumulative Remedies. Except as specifically stated in this Agreement, all remedies provided for in this Agreement will be cumulative and in addition to, and not in lieu of, any other remedies available to either Party at law, in equity, by contract, or otherwise. Except as specifically stated in this Agreement, the election by a Party of any remedy provided for in this Agreement or otherwise available to such Party will not preclude such Party from pursuing any other remedies available to such Party at law, in equity, by contract, or otherwise. 13.11. Survival. The following provisions will survive the expiration or termination of this Agreement for any reason: Section 2.4 -Customer Obligations; Section 3.4 -Effect of Termination or Expiration; Section 4 -Payment and Invoicing; Section 6.5 -Warranty Disclaimer; Section 7.1 -General Indemnity; Section 8 -Limitation of Liability; Section 9- Confidentiality; Section 10 -Proprietary Rights; Data; Feedback; Section 11 -Force Majeure; Delays Caused by Customer; Section 12-Disputes; and Section 13-General. 13.12. Entire Agreement. This Agreement, including all Addenda and Ordering Documents, constitutes the entire agreement of the Parties regarding the subject matter hereto, and supersedes all previous agreements, proposals, and understandings, whether written or oral, relating to this subject matter. This Agreement may be executed in multiple counterparts, and will have the same legal force and effect as if the Parties had executed it as a single document. The Parties may sign in writing or by electronic signature. An electronic signature, facsimile copy, or computer image of a signature, will be treated, and will have the same effect as an original signature, and will have the same effect, as an original signed copy of this document. This Agreement may be amended or modified only by a written instrument signed by authorized representatives of both Parties. The preprinted terms and conditions found on any Customer purchase order, acknowledgment, or other form will not be considered an amendment or modification or part of this Agreement, even if a representative of each .Party signs such document. 15 DocuSign Envelope ID: AB2013B4-94BF-4BOC-B860-74DCD9059AF5 14.AUTHORITY The individuals executing this Agreement and the instruments referenced in it on behalf ofContractor each represent and warrant that they have the egal power, right and actual authorityto bind Contractor to the terms and conditions of this A ee ent. CONTRACTOR: Motorola Solutions, Inc. (sign here) Micah Applewhite MSSSI Vice President & Director, SW Sales (print name/title) By: (sign here) (print name/title) Ci of C rlsbad, a municipal corporation of the ta of California By: (INSERT (City Manager or Mayor or Division Director as authorized by the City Manager) ATTEST: � ,fdFAVIOLA MEDINA City Clerk Services Manager If required by City, proper notarial acknowledgment of execution by contractor must be attached. !fa corporation, Agreement must be signed by one corporate officer from each of the following twogroups. 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 assistantsecretary under corporate seal empowering the officer(s) signing to bind the corporation. APPROVED AS TO FORM: CELIA A. BREWER, City Attorney BY:� L. Assistant City Attorney 16May 10, 2022 Item #11 Page 324 of 604 l \ By ~tk L~ U:RSONAUTHORIZEDTO SIGN ___ ____.._~-- DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 Equipment Purchase and Software License Addendum This Equipment Purchase and Software License Addendum (this "EPSLA") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and the entity set forth in the signature block below or in the MCA ("Customer"), and will be subject to, and governed by, the te�ms of the Master Customer Agreement entered into between the Parties, effective as of [ S/1'11(1;½ (the "MCA"). Capitalized terms used in this EPSLA, but not defined herein, will have the meanings set forth in the MCA. 1.Addendum. This EPSLA governs Customer's purchase of Equipment and license of Licensed Software (and, if set forth in an Ordering Document, related Services) from Motorola, and will form part of the Parties' Agreement. 2.Delivery of Equipment and Licensed Software. 2.1. Delivery and Risk of Loss. Motorola will provide to Customer the Products (and, if applicable, related Services) set forth in an Ordering Document, in accordance with the terms of the Agreement. Motorola will, using commercially reasonable practices, pack the ordered Equipment and ship such Equipment to the Customer address set forth in the applicable Ordering Document or otherwise provided by Customer in writing, using a carrier selected by Motorola. Notwithstanding the foregoing, delivery of Equipment (and any incorporated Licensed Software) will occur, and title and risk of loss for the Equipment will pass to Customer, upon receipt by Motorola in accordance with Ex Works, Motorola's premises (lncoterms 2020). Customer will pay all shipping costs, taxes, and other charges applicable to the shipment and import or export of the Products and Services, as applicable, and Customer will be responsible for reporting the Products for personal property tax purposes. Delivery of Licensed Software for installation on Equipment or Customer-Provided Equipment will occur upon the earlier of (a) electronic delivery of the Licensed Software by Motorola, and (b) the date Motorola otherwise makes the Licensed Software available for download by Customer. If agreed upon in an Ordering Document, Motorola will also provide Services related to such Products. 2.2. Delays. Any shipping dates set forth in an Ordering Document are approximate, and while Motorola will make reasonable efforts to ship Products by any such estimated shipping date, Motorola will not be liable for any delay or related damages to Customer. Time for delivery will not be of the essence, and delays will not constitute grounds for cancellation, penalties, termination, or a refund. 2.3. Beta Services. If Motorola makes any beta version of a software application ("BetaService") available to Customer, Customer may choose to use such Beta Service at its own discretion, provided, however, that Customer will use the Beta Service solely for purposes of Customer's evaluation of such Beta Service, and for no other purpose. Customer acknowledges and agrees that all Beta Services are offered "as-is" and without any representations or warranties or other commitments or protections from Motorola. Motorola will determine the duration of the evaluation period for any Beta Service, in its sole discretion, and Motorola may discontinue any Beta Service at any time. Customer acknowledges that Beta Services, by their nature, have not been fully tested and may contain defects or deficiencies. 3.Licensed Software License and Restrictions. 3.1. Licensed Software License. Subject to Customer's and its Authorized Users' compliance with the Agreement (including payment terms), Motorola hereby grants Customer and its Authorized Users a limited, non-transferable, non-sublicensable, and non-exclusive license to use the Licensed Software identified in an Ordering Document, in object code form only, and the 17 May 10, 2022 Item #11 Page 325 of 604 May 10, 2022 Item #11 Page 326 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 associated Documentation, solely in connection with the Equipment provided by Motorola or authorized Customer-Provided Equipment (as applicable, the "Designated Products") and solely for Customer's internal business purposes. Unless otherwise stated in an Addendum or the Ordering Document, the foregoing license grant will be limited to the number of licenses set forth in the applicable Ordering Document and will continue for the life of the applicable Designated Product. Except as otherwise permitted in an applicable Addendum or Ordering Document, Customer may install, access, and use Licensed Software only in Customer's owned or controlled facilities, including any authorized mobile sites; provided, however, that Authorized Users using authorized mobile or handheld devices may also log into and access the Licensed Software remotely from any location. 3.2. Subscription License Model. If the Parties mutually agree that any Licensed Software purchased under this EPSLA will be replaced with or upgraded to Subscription Software, then upon such time which the Parties execute the applicable Ordering Document, the licenses granted under this EPSLA will automatically terminate, and such Subscription Software will be governed by the terms of the applicable Addendum under this Agreement. 3.3. End User Licenses. Notwithstanding any provision to the contrary in the Agreement, certain Licensed Software is governed by a separate license, EULA, or other agreement, including terms governing third-party equipment or software, such as open source software, included in the Products and Services. Customer will comply, and ensure its Authorized Users comply, with any such additional terms applicable to third-party equipment or software. 3.4. Customer Restrictions. Customers and Authorized Users will comply with the applicable Documentation in connection with their use of the Products. Customer will not and will not allow others, including the Authorized Users, to: (a) make the Licensed Software available for use by unauthorized third parties, including via a commercial rental or sharing arrangement; (b) reverse engineer, disassemble, or reprogram the Licensed Software or any portion thereof to a human- readable form; (c) modify, create derivative works of, or merge the Licensed Software with other software or equipment; (d) copy, reproduce, distribute, lend, lease, or transfer the Licensed Software or Documentation for or to any third party without the prior express written permission of Motorola; (e) take any action that would cause the Licensed Software or Documentation to be placed in the public domain; (f) use the Licensed Software to compete with Motorola; or (g) remove, alter, or obscure, any copyright or other notice. 3.5. Copies. Customer may make one (1) copy of the Licensed Software solely for archival, back-up, or disaster recovery purposes during the term of the applicable Licensed Software license. Customer may make as many copies of the Documentation reasonably required for the internal use of the Licensed Software during such Licensed Software's license term. Unless otherwise authorized by Motorola in writing, Customer will not, and will not enable or allow any third party to: (a) install a licensed copy of the Licensed Software on more than one (1) unit of a Designated Product; or (b) copy onto or transfer Licensed Software installed in a unit of a Designated Product onto another device. Customer may temporarily transfer Licensed Software installed on a Designated Product to another device if the Designated Product is inoperable or malfunctioning. Temporary transfer of the Licensed Software to another device must be discontinued when the original Designated Product is returned to operation and the Licensed Software must be removed from the other device. Customer must provide prompt written notice to Motorola at the time temporary transfer is discontinued. 3.6. Resale of Equipment. Equipment contains embedded Licensed Software. If Customer desires to sell its used Equipment to a third party other than for salvage/scrap, Customer must first receive prior written authorization from Motorola and obtain written acceptance of the 18 May 10, 2022 Item #11 Page 327 of 604 DocuSign Envelope ID: AB2013B4-94BF--4B0C-B860-74DCD9D59AF5 applicable Licensed Software license terms, including the obligation to pay relevant license fees, from such third party. 4. Term. 4.1. Term. The term of this EPSLA (the "EPSLA Term") will commence upon either (a) the Effective Date of the MCA, if this EPSLA is attached to the MCA as of such Effective Date, or (b) the EPSLA Date set forth on the signature page below, if this EPSLA is executed after the MCA Effective Date, and will continue until the later of (i) three (3) years after the first order for Products is placed via an Ordering Document, or (ii) the expiration of all applicable warranty periods (as set forth in Section 6.1 -Motorola Warranties below) under this EPSLA, unless this EPSLA or the Agreement is earlier terminated in accordance with the terms of the Agreement. 4.2. Termination. Notwithstanding the termination provisions of the MCA, Motorola may terminate this EPSLA (and any Ordering Documents hereunder) immediately upon notice to Customer if Customer breaches Section 3 -Licensed Software License and Restrictions of this EPSLA, or any other provision related to Licensed Software license scope or restrictions set forth in an Ordering Document, EULA, or other applicable Addendum. For clarity, upon termination or expiration of the EPSLA Term, all Motorola obligations under this EPSLA (including with respect to Equipment and Licensed Software delivered hereunder) will terminate. If Customer desires to purchase additional Services in connection with such Equipment or Licensed Software, Customer may enter into a separate Addendum with Motorola, governing such Services. Customer acknowledges that Motorola made a considerable investment of resources in the development, marketing, and distribution of the Licensed Software and Documentation, and that Customer's breach of the Agreement will result in irreparable harm to Motorola for which monetary damages would be inadequate. If Licensee breaches this Agreement, in addition to termination, Motorola will be entitled to all available remedies at law or in equity, including immediate injunctive relief and repossession of all non-embedded Licensed Software and associated Documentation. 5. Payment. Customer will pay invoices for the Products and Services provided under this EPSLA in accordance with the invoice payment terms set forth in the MCA. Generally, invoices are issued after receipt of Equipment or upon Motorola's delivery of Licensed Software (in accordance with Section 2.1 -Delivery and Risk of Loss), as applicable, but if a specific invoicing or payment schedule is set forth in the applicable Ordering Document, EULA or other Addendum, such schedule will control with respect to the applicable Products and Services referenced therein. Motorola will have the right to suspend future deliveries of Products and Services if Customer fails to make any payments when due. 6. Representations and Warranties; Liability. 6.1 . Motorola Warranties. Subject to the disclaimers and exclusions set forth in the MCA and this EPSLA, (a) for a period of one (1) year commencing upon the delivery of Motorola- manufactured Equipment under Section 2.1 -Delivery and Risk of Loss, Motorola represents and warrants that such Motorola-manufactured Equipment, under normal use, will be free from material defects in materials and workmanship; (b) to the extent permitted by the providers of third-party software or hardware included in the Products and Services, Motorola will pass through to Customer any warranties provided by such third parties, which warranties will apply for the period defined by the applicable third party. 6.2. ADDITIONAL EXCLUSIONS. IN ADDITION TO THE EXCLUSIONS FROM DAMAGES SET FORTH IN THE MCA, AND NOTWITHSTANDING ANY PROVISION OF THE AGREEMENT TO THE CONTRARY, MOTOROLA WILL HAVE NO LIABILITY FOR (A) DEFECTS IN OR DAMAGE TO PRODUCTS RESULTING FROM USE OTHER THAN IN THE NORMAL 19 May 10, 2022 Item #11 Page 328 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 AUTHORIZED MANNER, OR FROM ACCIDENT, LIQUIDS, OR NEGLECT; (B) TESTING, MAINTENANCE, REPAIR, INSTALLATION, OR MODIFICATION BY PARTIES OTHER THAN MOTOROLA; (C) CUSTOMER'S OR ANY AUTHORIZED USER'S FAILURE TO COMPLY WITH INDUSTRY AND OSHA OR OTHER LEGAL STANDARDS; (D) DAMAGE TO RADIO ANTENNAS, UNLESS CAUSED BY DEFECTS IN MATERIAL OR WORKMANSHIP; (E) EQUIPMENT WITH NO SERIAL NUMBER; (F) BATTERIES OR CONSUMABLES; (G) FREIGHT COSTS FOR SHIPMENT TO REPAIR DEPOTS; (H) COSMETIC DAMAGE THAT DOES NOT AFFECT OPERATION; (I) NORMAL WEAR AND TEAR; (J) ISSUES OR OBSOLESCENCE OF LICENSED SOFTWARE DUE TO CHANGES IN CUSTOMER OR AUTHORIZED USER REQUIREMENTS, EQUIPMENT, OR SYSTEMS; (K) TRACKING AND LOCATION-BASED SERVICES; OR (L) BET A SERVICES. 6.3. Voluntary Remedies. Motorola is not obligated to remedy, repair, replace, or refund the purchase price for the disclaimed or excluded issues in the MCA or Section 6.2 -Additional Exclusions above. 7. Copyright Notices. The existence of a copyright notice on any Licensed Software will not be construed as an admission or presumption of publication of the Licensed Software or public disclosure of any trade secrets associated with the Licensed Software. 8. Survival. The following provisions will survive the expiration or termination of this EPSLA for any reason: Section 3 -Licensed Software License and Restrictions; Section 4-Term; Section 5 -Payment; Section 6.2 -Additional Exclusions; Section 8 -Survival. 20 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 Software Products Addendum This Software Products Addendum (this "SPA") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and the entity set forth in the signature block below or in the MCA ("Customer"), and will be subject to, and governed by, tre rii-i::{ the Master Customer Agreement entered into between the Parties,effective as of 6 11' (the "MCA"), and the applicable Addenda. Capitalized terms used in this SPA, but not tie med herein, will have the meanings set forth in the MCA or the applicable Addenda. 1.Addendum. This SPA governs Customer's purchase of certain Motorola software Products, including Software Systems, and will form part of the Parties' Agreement. A "SoftwareSystem" is a solution that includes at least one command center software Product and requires Integration Services to deploy such software Product at a Customer Site or onto any Customer-Provided Equipment or Equipment provided to Customer. In addition to the MCA, other Addenda may be applicable to the Software System or other software Products, including the Subscription Software Addendum ("SSA"), with respect to Subscription Software, and the Equipment Purchase and Software License Addendum ("EPSLA"), with respect to Licensed Software and Equipment, as further described below. This SPA will control with respect to conflicting terms in the MCA or any other applicable Addendum, but only as applicable to the Software System or other software Products purchased under this SPA and not with respect to other Products and Services. 2.Software Systems; Applicable Terms and Conditions. 2.1. On-Premise Software System. If Customer purchases an "on-premises Software System," where Equipment and Licensed Software are installed at Customer Sites or on CustomerProvided Equipment, then, unless the Ordering Document(s) specify that any software is being purchased on a subscription basis (i.e., as Subscription Software), such Equipment and Licensed Software installed at Customer Sites or on Customer-Provided Equipment are subject to the EPSLA. On-premises Software Systems described in this Section qualify for the System Warranty as described in Section 5 -On-Premises Software System Warranty (the "SystemWarranty"). In connection with the on-premises Software System, Customer may also purchase additional Subscription Software that integrates with its on-premises Software System (e.g., CommandCentral Aware) (each, an "Add-On Subscription"). Any Add-On Subscription will be subject to the terms and conditions of the SSA and excluded from the System Warranty. 2.2. On-Premise Software System as a Service. If Customer purchases an "on-premises Software System as a service," where Equipment and software Products are installed at Customer Sites or on Customer-Provided Equipment, and such software is generally licensed on a subscription basis (i.e., as Subscription Software), then such Subscription Software will be subject to the SSA and not the EPSLA. Any (a) Equipment purchased, (b) firmware preinstalled on such Equipment, and (c) Microsoft operating system Licensed Software are subject to the EPSLA. On-premises Software Systems as a service described in this Section are provided as a service and, accordingly, do not qualify for the System Warranty. System completion, however, is determined in accordance with the provisions of Section 3 -Software System Completionbelow. 2.3. Cloud Hosted Software System. If Customer purchases a "cloud hosted Software System," where the applicable software is hosted in a data center and provided to Customer as a service (i.e., as hosted Subscription Software), including CommandCentral Products, then such Subscription Software is subject to the SSA. Any Equipment purchased in connection with a cloud Software System is subject to the EPSLA. Cloud hosted Software Systems described in this 21 May 10, 2022 Item #11 Page 329 of 604 May 10, 2022 Item #11 Page 330 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-8860-74DCD9D59AF5 Section do not qualify for the System Warranty. System completion, however, is determined in accordance with the provisions of Section 3 -Software System Completion below. 2.4. Services. Any Integration Services or Maintenance and Support Services purchased in connection with, or included as a part of, a Software System are subject to the MCA, and as described in the applicable Ordering Document. 3. Software System Completion. Any Software System described in an Ordering Document hereunder (including the Products, Integration Services, and all other components thereof) will be deemed completed when all of the following have occurred: (1) Customer has determination Motorola has completed all milestones identified in the Ordering Document for Final System Acceptance, (2) Motorola has delivered all Products and Services identified in the Ordering Document, and (3) Customer has had Beneficial Use of each Product that is included in the Software System (unless alternative acceptance procedures are set forth in the applicable Ordering Document) (the "System Completion Date"). Customer will not unreasonably delay determination of milestone completion or Beneficial Use of any Product within the Software System, and in any event, the Parties agree that Beneficial Use of a Product will be deemed to have occurred in accordance with the definition of "Beneficial Use" below. For clarity, if a Software System is comprised of more than one Product, Motorola may notify Customer that all Integration Services for a particular Product within the Software System have been completed, and Customer may have Beneficial Use of such Product prior to having Beneficial Use of other Products in the Software System, or of the Software System as a whole. In such case, the Integration Services applicable to such Product will be deemed complete upon Customer's Beneficial Use of the Product ("Product Completion Date"), which may occur before the System Completion Date. As used in this Section, "Beneficial Use" means use by Customer's Authorized Users of the material features and functionalities of a Product within a Software System, in material conformance with Product descriptions in the applicable Ordering Document, in a production or live-use environment. This Section applies to Products purchased as part of a Software System notwithstanding the delivery provisions of the Addendum applicable to such Products, such as the SSA or EPSLA, and this Section will control over such other delivery provisions to the extent of a conflict. 4. Payment. Customer will pay invoices for the Products and Services covered by this SPA in accordance with the invoice payment terms set forth in the MCA. Fees for Software Systems will be invoiced as of the System Completion Date, unless another payment process or schedule or milestones are set forth in an Ordering Document or applicable Addendum. In addition to Equipment, Licensed Software, Subscription Software and Integration Services (as applicable) sold as part of a Software System, the Ordering Documents for a Software System may also include post-deployment Integration Services or other Services which are to be provided following the date of functional demonstration ("Post-Deployment Services"). Post-Deployment Services will be invoiced upon their completion and paid by Customer in accordance with the terms of the MCA. 5. On-Premises Software System Warranty. Subject to the disclaimers in the MCA and any other applicable Addenda, Motorola represents and warrants that, on the System Completion Date for an on-premises Software System described in Section 2.1 -On-Premises Software System, or on the applicable Product Completion Date for a specific Product within such on- premises Software System, if earlier, (a) such Software System or Product will perform in accordance with the descriptions in the applicable Ordering Documents in all material respects, and (b) if Customer has purchased any Equipment or Motorola Licensed Software (but, for clarity, excluding Subscription Software) as part of such on-premises Software System, the warranty period applicable to such Equipment and Motorola Licensed Software will continue for a period of 22 May 10, 2022 Item #11 Page 331 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9D59AF5 one (1) year commencing upon the System Completion Date for the Software System that includes such Products, or on the applicable Product Completion Date, if earlier, instead of commencing upon delivery of the Products in accordance with the terms and conditions set forth in Section 6 -Representations and Warranties; Liabilities of the EPSLA. The warranties set forth in the applicable Addenda are not otherwise modified by this SPA. 6. Prohibited Use. Customer will not integrate or use, or permit a third party or an Authorized User to integrate or use, any Non-Motorola Content with or in connection with a Software System or other software Product provided by Motorola under this SPA, without the express written permission of Motorola. 7. API Support. Motorola will use commercially reasonable efforts to maintain its Application Programming Interface ("API") offered sold in connection with any Software System. APls will evolve and mature over time, requiring changes and updates. Motorola will use reasonable efforts to continue supporting any version of an API for 6 months after such version is introduced, but if Motorola determines, in its sole discretion, determines to discontinue support of an API for any reason, Motorola will provide reasonable advance notification to Customer. If an API presents a security risk, Motorola may discontinue an API without prior notice. 8. Support of Downloaded Clients. If Customer purchases any software Product that requires a client installed locally on any Customer-Provided Equipment or Equipment in possession of Customer, Customer will be responsible for downloading and installing the current version of such client, as it may be updated from time to time. Motorola will use reasonable efforts to continue supporting any version of a client for forty-five (45) days following the general availability of a new version release. Motorola may update the current version of its client at any time, including for security vulnerabilities, bug fixes, product improvements, and feature updates, and Motorola makes no representations or warranties that any software Product will support prior versions of a client. 9. Applicable End User Terms. Additional license terms apply to third-party software included in CAD and Records Products which are available online at: www.motorolasolutions.com/legal-flow-downs. Customer will comply, and ensure its Authorized Users comply, with all such additional license terms. Specifically, the following Esri As-a-Service Terms and Twilio/Sendgrid Acceptable Use Policy apply: 9.1. Esri As-a-Service Terms Any customer or end-user of Esri software agrees to: a. Disclaim, to the extent permitted by applicable law, Esri and its licensors' liability for any damages or loss of any kind, whether direct, special, indirect, incidental, or consequential, arising from the use of the Esri OEM software(s) including, but not limited to, liability for use of Esri OEM(s) in high-risk activities or liability related to any data supplied by Esri. b. Upon notice by Motorola Solutions that its OEM agreement with Esri has terminated or expired, agrees to (i) cease access and use of Esri OEM software), online services and clear online services client-side data cache and (ii) cease use, uninstall, remove, and destroy all Esri OEM software(s) and any whole or partial copies, modifications, or merged portions in any form and execute and deliver evidence of such actions to Motorola Solutions. 23 May 10, 2022 Item #11 Page 332 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 c. Comply fully with all relevant export laws and regulations of the United States to ensure that Esri OEM or any direct product thereof, is not exported, directly or indirectly, in violation of United States law. d. Not remove or obscure any copyright, trademark notice, or restrictive legend. e. Accept all terms in any click-through terms included with Esri licensed material. f. Accept that Esri OEM software may contain some nonconformities, defects, errors, or omissions. THE HOSTED SOLUTION(S) IS/ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. Without limiting the generality of the preceding sentence, Esri and its licensors do not warrant data, on line services, and the Esri OEM software will meet the hosted solutions end user's needs or expectations, that the use of data, online services, and Esri OEM software will be uninterrupted, or that all nonconformities can or will be corrected. Esri and its licensors are not inviting reliance on data, online services, and Esri OEM software and hosted solution end user should always verify actual data, online services and hosted solutions(s). g. Not to share its login or password with any other third party or other hosted solution end user. 9.2 Twilio/Sendgrid Services Use of the Twilio Services provided hereunder shall be in accordance with theTwilio Acceptable Use Policy, incorporated below. Twilio may suspend the Twilio Services immediately upon notice to Customer for cause if: (i) Customer or an End User materially violates (or Twilio believes, in good faith, that Customer or an End User has materially violated) any provision of the Twilio Acceptable Use Policy: (ii) there is an unusual and material spike or increase in Customer's use of the Twilio Services and Twilio believes, in good faith, that such traffic or use is fraudulent or materially and negatively impacting the operating capability of the Twilio Services; (iii) Twilio determines, in good faith, that its provision of the Twilio Services is prohibited by applicable Law. Notwithstanding the foregoing, Twilio will use commercially reasonable efforts to (x) provide Customer as much prior notice as possible of any situation its aware of that could lead to a right to suspend described in this Section 8.3, (y) work with Customer to remedy any situation that could lead to a right to suspend described in this Section 8.3 if such situation can be remedied, and (z) limit any suspension as much a possible given the circumstances leading to the suspension (e.g., to certain phone numbers, sub-accounts or other subset of traffic). This Acceptable Use Policy ("AUP'') describes rules that apply to any party ("Customer") using any products and services ("Services") provided by Twilio Inc. or any of its affiliates (collectively, "Twilio") and any user of any software application or service made available by Customer that interfaces with the Services ("End User"). The examples described in this AUP are not exhaustive. Customer is responsible for its End Users' compliance with this AUP. If Customer or any End User violates this AUP, Twilio may suspend Customer's use of the Services. This AUP may be updated by Twilio from time to time upon reasonable notice, which may be provided via Customer's account or e-mail. No Inappropriate Content or Users. Do not use the Services to transmit or store any content or communications (commercial or otherwise) that is illegal, harmful, unwanted, inappropriate, 24 May 10, 2022 Item #11 Page 333 of 604 DocuSign Envelope ID: AB201384-948F-4B0C-B860-74DCD9D59AFS objectionable, confirmed to be criminal misinformation, or otherwise poses a threat to the public. This prohibition includes use of the Services by a hate group or content or communications that originate from a hate group or are exploitive, abusive, or hate speech. Prohibited Activities. Do not use the Services to engage in or encourage any activity that is illegal, deceptive, harmful, violating others' rights, or harmful to Twilio's business operations or reputation, including: • Violations of Laws. Violating laws, regulations, governmental orders, or industry standards or guidance in any applicable jurisdiction (collectively, "Applicable Laws") .. This includes violating Applicable Laws requiring (a) consent be obtained prior to transmitting, recording, collecting, or monitoring data or communications or (b) compliance with opt-out requests for any data or communications. • Interference with the Services. Interfering with or otherwise negatively impacting any aspect of the Services or any third-party networks that are linked to the Services. • Reverse Engineering. Reverse engineering, copying, disassembling, or decompiling the Services. • Falsification of Identity or Origin. Creating a false identity or any attempt to mislead others as to the identity of the sender or the origin of any data or communications. No Service Integrity Violations. Do not violate the integrity of the Services, including: • Bypassing Service Limitations. Attempting to bypass, exploit, defeat, or disable limitations or restrictions placed on the Services. • Security Vulnerabilities. Finding security vulnerabilities to exploit the Services or attempting to bypass any security mechanism or filtering capabilities. • Disabling the Services. Any denial of service (DOS) attack on the Services or any other conduct that attempts to disrupt, disable, or overload the Services. • Harmful Code or Bots. Transmitting code, files, scripts, agents, or programs intended to do harm, including viruses or malware, or using automated means, such as bots, to gain access to or use the • Services. • Unauthorized Access. Attempting to gain unauthorized access to the Services. Data Safeguards. Customer is responsible for determining whether the Services offer appropriate o safeguards for Customer's use of the Services, including, but not limited to, any safeguards required by ILQ) Applicable Laws, prior to transmitting or processing, or prior to permitting End Users to transmit or process, any data or communications via the Services. Violations of this AUP, including any prohibited content or communications, may be reported to .https://www.twilio.com/help/abuse (https://www.twilio.com/help/abuse). 25 May 10, 2022 Item #11 Page 334 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 Customer agrees to immediately report any violation of this Al-JP to Twilio and provide cooperation, as requested by Twilio, to investigate and/or remedy that violation. 10. Additional Terms for On-Premise Software System as a Service. The terms set forth in this Section 10 -Additional Terms for On-Premise Software System as a Service apply in the event Customer purchases an on-premises Software System as a service under this SPA. 10.1. Transition to Subscription License Model. If the Parties mutually agree that any on- premises Subscription Software purchased under this SPA as part of an on-premises Software System as a service will be replaced with or upgraded to Subscription Software hosted in a data center, then upon such time which the Parties execute the applicable Ordering Document, (a) the licenses granted to such on-premises Subscription Software under the applicable Ordering Document will automatically terminate, (b) Customer and its Authorized Users will cease use of the applicable on-premises copies of Subscription Software, and (c) the replacement hosted Subscription Software provided hereunder will be governed by the terms of the SSA and this SPA. 10.2. Transition Fee. Motorola will not charge additional Fees for Services related to the transition to hosted Subscription Software, as described in Section 10.1 -Transition to Subscription License Model. Notwithstanding the foregoing, subscription Fees for the applicable hosted Subscription Software are subject to the SSA and the applicable Ordering Document, and may be greater than Fees paid by Customer for on-premises Subscription Software. 10.3. Software Decommissioning. Upon (a) transition of the on-premises Software System as a service to Subscription Software hosted in a data center or (b) any termination of the Subscription Software license for the on-premises Software System as a service, Motorola will have the right to enter Customer Sites with pre-approval and City escort, and decommission the applicable on- premises Subscription Software that is installed at Customer's Site or on Customer-Provided Equipment. For clarity, Customer will retain the right to use Licensed Software that is firmware incorporated into Equipment purchased by Customer from Motorola and any Microsoft operating system Licensed Software. 11. Additional Terms for CAD and Records Products. The terms set forth in this Section 11 -Additional Terms for CAD and Records Products apply in the event Customer purchases any Computer Aided Dispatch ("CAD") or Records Products under this SPA. 11.1. Support Required. Customer acknowledges and agrees that the licenses granted by Motorola under the Agreement to CAD and Records Products for on-premises Software Systems are conditioned upon Customer purchasing Maintenance and Support Services for such Products during the term of the applicable license. If at any time during the term of any such license, Customer fails to purchase associated Maintenance and Support Services (or pay the fees for such Services), Motorola will have the right to terminate or suspend the software licenses for CAD and Record Products, and this SPA or the applicable Ordering Document. 11.2. CJIS Security Policy. Motorola agrees to support Customer's obligation to comply with the Federal Bureau of Investigation Criminal Justice Information Services ("CJIS") Security Policy and will comply with the terms of the CJIS Security Addendum for the term of the Addendum or Ordering Document for the applicable Product. Customer must consent to and escort Motorola personnel accessing unencrypted Criminal Justice Information for purposes of Product support and development. 12. Additional Cloud Terms. The terms set forth in this Section 12 -Additional Cloud Terms apply in the event Customer purchases any cloud hosted software. 26 May 10, 2022 Item #11 Page 335 of 604 DocuSign Envelope ID: AB2013B4-94BF--4B0C-B860-74DCD9D59AF5 12.1. Data Storage. Motorola will determine, in its sole discretion, the location of the stored content for cloud hosted software. All data, replications, and backups will be stored at a location in the United States for Customers in the United States. 12.2. Data Retrieval. Cloud hosted software will leverage different types of storage to optimize software, as determined in Motorola's sole discretion. For multimedia data, such as videos, pictures, audio files, Motorola will, in its sole discretion, determine the type of storage medium used to store the content. The type of storage and medium selected by Motorola will determine the data retrieval speed. Access to content in archival storage may take up to 24 hours to be viewable. 12.3. Maintenance. Scheduled maintenance of cloud hosted Software will be performed periodically. Motorola will make commercially reasonable efforts to notify customers one (1) week in advance of any such maintenance. Unscheduled and emergency maintenance may be required from time to time. Motorola will make commercially reasonable efforts to notify customers of any unscheduled or emergency maintenance 24 hours in advance. 13. Survival. The following provisions will survive the expiration or termination of this SPA for any reason: Section 1 -Addendum; Section 2 -Software Systems; Applicable Terms and Conditions; Section 6 -Prohibited Use; Section 9 -Applicable End User Terms; Section 13-Survival. 27 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 Subscription Software Addendum This Subscription Software Addendum (this "SSA") and the Exhibit to this SSA for CommandCentral Investigate, powered by LexisNexis is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and the entity set forth in the signature block below or in the MCA ("Customer"), and will be subject to, and governed by, t e terms of the Master Customer Agreement entered into betweenthe Parties, effective as of ri (the "MCA"). Capitalized terms used in this SSA, but notdefined herein, will have the meanings set forth in the MCA. 1.Addendum. This SSA governs Customer's purchase of Subscription Software (and, if setforth in an Ordering Document, related Services) from Motorola, and will form part of the Parties'Agreement. Additional Subscription Software-specific Addenda or other terms and conditions may apply to certain Subscription Software, where such terms are provided or presented to Customer. 2.Delivery of Subscription Software. 2.1. Delivery. During the applicable Subscription Term (as defined below), Motorola will provide to Customer the Subscription Software set forth in an Ordering Document, in accordance with the terms of the Agreement. Motorola will provide Customer advance notice (which may be provided electronically) of any planned downtime. Delivery will occur upon Customer's receipt of credentials required for access to the Subscription Software or upon Motorola otherwise providing access to the Subscription Software. If agreed upon in an Ordering Document, Motorola will also provide Services related to such Subscription Software. 2.2. Modifications. In addition to other rights to modify the Products and Services set forth in the MCA, Motorola may modify the Subscription Software, any associated recurring Services and any related systems so long as their functionality (as described in the applicable Ordering Document) is not materially degraded. Documentation for the Subscription Software may be updated to reflect such modifications. For clarity, new features or enhancements that are added to any Subscription Software may be subject to additional Fees which will be set forth in an Amendment or Ordering Document. 2.3. User Credentials. If applicable, Motorola will provide Customer with administrative user credentials for the Subscription Software, and Customer will ensure such administrative user credentials are accessed and used only by Customer's employees with training on their proper use. Customer will protect, and will cause its Authorized Users to protect, the confidentiality and security of all user credentials, including any administrative user credentials, and maintain user credential validity, including by updating passwords. Customer will be liable for any use of the Subscription Software through such user credential (including through any administrative user credentials), including any changes made to the Subscription Software or issues or user impact arising therefrom. To the extent Motorola provides Services to Customer in order to help resolve issues resulting from changes made to the Subscription Software through user credentials, including through any administrative user credentials, or issues otherwise created by Authorized Users, such Services will be billed to Customer on a time and materials basis, and Customer will pay all invoices in accordance with the payment terms of the MCA which will be set forth in an Amendment or Ordering Document. 2.4. Beta Services. If Motorola makes any beta version of a software application ("Beta Service" or software application not available for General Release) available to Customer, Customer may choose to use such Beta Service at its own discretion, provided, however, that Customer will use the Beta Service solely for purposes of Customer's evaluation of such Beta Service, and for no other purpose. Customer acknowledges and agrees that all Beta Services are 28 May 10, 2022 Item #11 Page 336 of 604 rs1 [P:-1 May 10, 2022 Item #11 Page 337 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 offered "as-is" and without any representations or warranties or other commitments or protections from Motorola. Motorola will determine the duration of the evaluation period for any Beta Service, in its sole discretion, and Motorola may discontinue any Beta Service at any time. Customer acknowledges that Beta Services, by their nature, have not been fully tested and may contain defects or deficiencies. 3. Subscription Software License and Restrictions. 3.1. Subscription Software License. Subject to Customer's and its Authorized Users' compliance with the Agreement, including payment terms, Motorola hereby grants Customer and its Authorized Users a limited, non-transferable, non-sublicensable, and non-exclusive license to use the Subscription Software identified in an Ordering Document, and the associated Documentation, solely for Customer's internal business purposes. The foregoing license grant will be limited to use in the territory and to the number of licenses set forth in an Ordering Document (if applicable), and will continue for the applicable Subscription Term. Customer may access, and use the Subscription Software only in Customer's owned or controlled facilities, including any authorized mobile sites; provided, however, that Authorized Users using authorized mobile or handheld devices may also log into and access the Subscription Software remotely from any location. No custom development work will be performed under this Addendum. 3.2. End User Licenses. Notwithstanding any provision to the contrary in the Agreement, certain Subscription Software is governed by a separate license, EULA, or other agreement, including terms governing third-party software, such as open source software, included in the Subscription Software. Customer will comply, and ensure its Authorized Users comply, with such additional license agreements. 3.3. Customer Restrictions. Customers and Authorized Users will comply with the applicable Documentation and the copyright laws of the United States and all other relevant jurisdictions (including the copyright laws where Customer uses the Subscription Software) in connection with their use of the Subscription Software. Customer will not, and will not allow others including the Authorized Users, to make the Subscription Software available for use by unauthorized third parties, including via a commercial rental or sharing arrangement; reverse engineer, disassemble, or reprogram software used to provide the Subscription Software or any portion thereof to a human-readable form; modify, create derivative works of, or merge the Subscription Software or software used to provide the Subscription Software with other software; copy, reproduce, distribute, lend, or lease the Subscription Software or Documentation for or to any third party; take any action that would cause the Subscription Software, software used to provide the Subscription Software, or Documentation to be placed in the public domain; use the Subscription Software to compete with Motorola; remove, alter, or obscure, any copyright or other notice; share user credentials (including among Authorized Users); use the Subscription Software to store or transmit malicious code; or attempt to gain unauthorized access to the Subscription Software or its related systems or networks. 4. Term. 4.1. Subscription Terms. The duration of Customer's subscription to the first Subscription Software and any associated recurring Services ordered under this SSA (or the first Subscription Software or recurring Service, if multiple are ordered at once) will commence upon delivery of such Subscription Software (and recurring Services, if applicable) and will continue for a twelve (12) month period or such longer period identified in an Ordering Document (the "Initial Subscription Period"). Following the Initial Subscription Period, Motorola will provide notification at least ninety (90) days prior to renewal for additional twelve (12) month periods (each, a "Renewal Subscription Year"). Either Party may notify the other Party of its intent not to renew 29 May 10, 2022 Item #11 Page 338 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 at least thirty (30) days before the conclusion of the then-current Subscription Term. Customer will provide documentation to affirm renewal via an Amendment or Ordering Document of the Subscription Software for the Renewal Subscription Year (the Initial Subscription Period and each Renewal Subscription Year will each be referred to herein as a "Subscription Term".) Motorola may increase Fees prior to any Renewal Subscription Year. In such case, Motorola will notify Customer of such proposed increase no later than ninety (90) days prior to commencement of such Renewal Subscription Year. Unless otherwise specified in the applicable Ordering Document, if Customer orders any additional Subscription Software or recurring Services under this SSA during an in-process Subscription Term, the subscription for each new Subscription Software or recurring Service will (a) commence upon delivery of such Subscription Software or recurring Service, and continue until the conclusion of Customer's then-current Subscription Term (a "Partial Subscription Year''), and (b) renew in accordance with the same terms stated herein for Renewal Subscription Years thereafter, unless either Party notifies the other Party of its intent not to renew at least thirty (30) days before the conclusion of the then-current Subscription Term. Thus, unless otherwise specified in the applicable Ordering Document, the Subscription Terms for all Subscription Software and recurring Services hereunder will be synchronized. 4.2. Term. The term of this SSA (the "SSA Term") will commence upon either (a) the Effective Date of the MCA, if this SSA is attached to the MCA as of such Effective Date, or (b) the SSA Date set forth on the signature page below, if this SSA is executed after the MCA Effective Date, and will continue until the expiration or termination of all Subscription Terms under this SSA, unless this SSA or the Agreement is earlier terminated in accordance with the terms of the Agreement. 4.3. Termination. Notwithstanding the termination provisions of the MCA, Motorola may terminate this SSA (or any Addendum or Ordering Documents hereunder), or suspend delivery of Subscription Software or Services, after providing 90 days advanced notice to Customer and an opportunity to cure if (a) Customer breaches Section 3 -Subscription Software License and Restrictions of this SSA, or any other provision related to Subscription Software license scope or restrictions set forth in an Addendum or Ordering Document, or (b) it determines that Customer's use of the Subscription Software poses, or may pose, a security or other risk or adverse impact to any Subscription Software, Motorola, Motorola's systems, or any third party (including other Motorola customers). Customer acknowledges that Motorola made a considerable investment of resources in the development, marketing, and distribution of the Subscription Software and Documentation, and that Customer's breach of the Agreement will result in irreparable harm to Motorola for which monetary damages would be inadequate. If Customer breaches this Agreement, in addition to termination, Motorola may be entitled to all available remedies at law or in equity (including immediate injunctive relief). 4.4. Wind Down of Subscription Software. In addition to the termination rights in the MCA, Motorola may terminate any Ordering Document and Subscription Term, in whole or in part, in the event Motorola plans to cease offering the applicable Subscription Software or Service to customers. Motorola will provide at least one (1) year advance notice of our intent to cease offering PremierOne Cloud CAD/Mobile, Aware and In-Car Video as a Service. 5. Payment. 5.1. Payment. Unless otherwise provided in an Ordering Document (and notwithstanding the provisions of the MCA), Customer will prepay an annual subscription Fee set forth in an Ordering Document for each Subscription Software and associated recurring Service, before the commencement of each Subscription Term. For any Partial Subscription Year, the applicable annual subscription Fee will be prorated based on the number of months in the Partial Subscription Year. The annual subscription Fee for Subscription Software and associated 30 May 10, 2022 Item #11 Page 339 of 604 DocuSign Envelope ID: AB2013B4-948F-4B0C-8860-74DCD9D59AF5 recurring Services may include certain one-time Fees, such as start-up fees, license fees, or other fees set forth in an Ordering Document. After providing reasonable notice and an opportunity to cure, Motorola will have the right to suspend the Subscription Software and any recurring Services if Customer fails to make any payments when due. 5.2. Subscription True-Up. Motorola will have the right to conduct an audit of total named users credentialed by Customer for any Subscription Software during a Subscription Term, and Customer will cooperate with such audit. If Motorola determines that Customer's usage of the Subscription Software during the applicable Subscription Term exceeded the total number of subscriptions purchased by Customer, Motorola may invoice Customer for the additional subscriptions used by Customer, pro-rated for e·ach additional subscription from the date such subscription was activated, and Customer will pay such invoice in accordance with the payment terms in the MCA. Such audits, if conducted, will occur prior to subscription renewal/extension. 6. Liability. 6.1. ADDITIONAL EXCLUSIONS. IN ADDITION TO THE EXCLUSIONS FROM DAMAGES SET FORTH IN THE MCA, AND NOTWITHSTANDING ANY PROVISION OF THE AGREEMENT TO THE CONTRARY, MOTOROLA WILL HAVE NO LIABILITY FOR (A) INTERRUPTION OR FAILURE OF CONNECTIVITY, VULNERABILITIES, OR SECURITY EVENTS; (B) DISRUPTION OF OR DAMAGE TO CUSTOMER'S OR THIRD PARTIES' SYSTEMS, EQUIPMENT, OR DATA, INCLUDING DENIAL OF ACCESS TO USERS, OR SHUTDOWN OF SYSTEMS CAUSED BY INTRUSION DETECTION SOFTWARE OR HARDWARE; (C) AVAILABILITY OR ACCURACY OF ANY DATA AVAILABLE THROUGH THE SUBSCRIPTION SOFTWARE OR SERVICES, OR INTERPRETATION, USE, OR MISUSE THEREOF; (D) TRACKING AND LOCATION-BASED SERVICES; OR (E) BETA SERVICES. 6.2. Voluntary Remedies. Motorola is not obligated to remedy, repair, replace, or refund the purchase price for the disclaimed or excluded issues in the MCA or Section 6.1 -Additional Exclusions above. 7. Motorola as a Controller or Joint Controller. In all instances where Motorola acts as a controller of data, it will comply with the applicable provisions of the Motorola Privacy Statement at https://www.motorolasolutions.com/en us/abouVprivacy-policy.html#privacystatement, as may be updated from time to time. Motorola holds all Customer Contact Data as a controller and shall Process such Customer Contact Data in accordance with the Motorola Privacy Statement. In instances where Motorola is acting as a joint controller with Customer, the Parties will enter into a separate Addendum to the Agreement to allocate the respective roles as joint controllers. To the extent there are conflicts between the Motorola Privacy Statement and terms in this Addendum, the terms in the Addendum shall control. 8. Survival. The following provisions will survive the expiration or termination of this SSA for any reason: Section 4 -Term; Section 5 -Payment; Section 6.1 -Additional Exclusions; Section 8 -Survival. 31 May 10, 2022 Item #11 Page 340 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 Exhibit to Subscription Services Agreement Command Central Investigate, powered by LexisNexis Motorola Solutions, Inc. ("Motorola Solutions") is the provider of the service known as Command Central Investigate, powered by LexisNexis ("Motorola Solutions Services"). Customer agrees to the Motorola Solutions Services pursuant to the following terms and conditions which are incorporated into the Subscription Services Agreement Signed by Customer. 1. RESTRICTED LICENSE. Motorola Solutions hereby grants to Customer a restricted license to use the Motorola Solutions Services, subject to the restrictions and limitations set forth below: (i) Generally. Motorola Solutions hereby grants to Customer a restricted license to use the Motorola Solutions Services solely for Customer's own internal business purposes. Customer represents and warrants that all of Customer's use of the Motorola Solutions Services shall be for only legitimate business purposes, including those specified by Customer in connection with a specific information request, relating to its business and as otherwise governed by these Master Terms. Customer shall not use the Motorola Solutions Services for marketing purposes or resell or broker the Motorola Solutions Services to any third-party, and shall not use the Motorola Solutions Services for personal (non-business) purposes. Customer shall not use the Motorola Solutions Services to provide data processing services to third-parties or evaluate data for third-parties or, without Motorola Solutions' consent, to compare the Motorola Solutions Services against a third party's data processing services. Customer agrees that, if Motorola Solutions determines or reasonably suspects that continued provision of Motorola Solutions Services to Customer entails a potential security risk, or that Customer is in violation of any provision of these Master Terms or law, Motorola Solutions may provide immediate notification to the Customer and, following a reasonable time to cure, take immediate action, including, without limitation, terminating the delivery of, and the license to use, the Motorola Solutions Services. Customer shall not access the Motorola Solutions Services from Internet Protocol addresses located outside of the United States and its territories without Motorola Solutions' prior written approval. Customer may not use the Motorola Solutions Services to create a competing product. Customer shall comply with all laws, regulations and rules which govern the use of the Motorola Solutions Services and information provided therein. Motorola Solutions may at any time mask or cease to provide Customer access to any Motorola Solutions Services or portions thereof which Motorola Solutions may deem, in Motorola Solutions' sole discretion, to be sensitive or restricted information, following notice and a reasonable time to cure. (ii) GLBA Data. Some of the information contained in the Motorola Solutions Services is "nonpublic personal information," as defined in the Gramm-Leach-Bliley Act, (15 U.S.C. § 6801, et seq.) and related state laws (collectively, the "GLBA"), and is regulated by the GLBA ("GLBA Data"). Customer shall not obtain and/or use GLBA Data through the Motorola Solution Services in any manner that would violate the GLBA, or any similar state or local laws, regulations and rules. Customer acknowledges and agrees that it may be required to certify its permissible use of GLBA Data falling within an exception set forth in the GLBA at the time it requests information in connection with certain Motorola Solutions Services and will recertify upon request by Motorola Solutions. Customer certifies with respect to GLBA Data received through the Motorola 32 May 10, 2022 Item #11 Page 341 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 Solutions Services that it complies with the lnteragency Standards for Safeguarding Customer Information issued pursuant to the GLBA. (iii) DPPA Data. Some of the information contained in the Motorola Solutions Services is "personal information," as defined in the Drivers Privacy Protection Act, (18 U.S.C. § 2721 et seq.) and related state laws (collectively, the "DPPA"), and is regulated by the DPPA ("DPPA Data"). Customer shall not obtain and/or use DPPA Data through the Motorola Solutions Services in any manner that would violate the DPPA. Customer acknowledges and agrees that it may be required to certify its permissible use of DPPA Data at the time it requests information in connection with certain Motorola Solutions Services and will recertify upon request by Motorola Solutions. (iv) Social Security and Driver's License Numbers. Motorola may in its sole discretion permit Customer to access full social security numbers (nine (9) digits) and driver's license numbers (collectively, "QA Data"). If Customer is authorized by Motorola Solutions to receive QA Data, and Customer obtains QA Data through the Motorola Solutions Services, Customer certifies it will not use the QA Data for any purpose other than as expressly authorized by Motorola Solutions policies, the terms and conditions herein, and applicable laws and regulations. In addition to the restrictions on distribution otherwise set forth in Paragraph 3 below, Customer agrees that it will not permit QA Data obtained through the Motorola Solutions Services to be used by an employee or contractor that is not an Authorized User with an Authorized Use. Customer agrees it will certify, in writing, its uses for QA Data and recertify upon request by Motorola Solutions. Customer may not, to the extent permitted by the terms of these Master Terms, transfer QA Data via email or ftp without Motorola Solutions' prior written consent. However, Customer shall be permitted to transfer such information so long as: 1) a secured method (for example, sftp) is used, 2) transfer is not to any third-party, and 3) such transfer is limited to such use as permitted under these Master Terms. Motorola Solutions may at any time and for any or no reason cease to provide or limit the provision of QA Data to Customer. (v) Copyrighted and Trademarked Materials. Customer shall not remove or obscure any trademarks, copyright notices or other notices contained on materials accessed through the Motorola Solutions Services. (vi) Additional Terms. To the extent that the Motorola Solutions Services accessed by Customer include information or data described in the Risk Supplemental Terms contained at: www.lexisnexis.com/terms/risksupp, Customer agrees to comply with the Risk Supplemental Terms set forth therein. Additionally, certain other information contained within the Motorola Solutions Services is subject to additional obligations and restrictions. These services include, without limitation, news, business information, and federal legislative and regulatory materials. To the extent that Customer receives such news, business information, and federal legislative and regulatory materials through the Motorola Solutions Services, Customer agrees to comply with the Terms and Conditions contained at: http://www.lexisnexis.com/terms/general.aspx (the "L&P Terms"). The Risk Supplemental Terms and the L&P Terms are hereby incorporated into these Master Terms by reference. In the event of a direct conflict between these Master Terms, the Risk Supplemental Terms, and the L&P Terms, the order of precedence shall be as follows: these Master Terms, the Risk Supplemental Terms and then the L&P Terms. (vii) MVR Data. If Customer is permitted to access Motor Vehicle Records ("MVR Data") from Motorola Solutions, without in any way limiting Customer's obligations to comply with all state 33 May 10, 2022 Item #11 Page 342 of 604 OocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74OCO9O59AF5 and federal laws governing use of MVR Data, the following specific restrictions apply and are subject to change: (a) Customer shall not use any MVR Data provided by Motorola Solutions, or portions of information contained therein, to create or update a file that Customer uses to develop its own source of driving history information. (b) As requested by Motorola Solutions, Customer shall complete any state forms that Motorola Solutions is legally or contractually bound to obtain from Customer before providing Customer with MVR Data. (c) Motorola Solutions (and certain Third-Party vendors) may conduct reasonable and periodic audits of Customer's use of MVR Data. In response to any such audit, Customer must be able to substantiate the reason for each MVR Data order. (viii) HIPAA Customer represents and v-,:arrants that Customer will not provide Motorola Solutions with any Protected Health Information (as that term is defined in 45 C.F.R. Sec. 160.103) or with Electronic Health Records or Patient Health Records (as those terms are defined in 42 U.S.C. Sec. 17921(5), and 42 U.S.C. Sec. 17921(11), respectively) or with information from such records without the execution of a separate agreement between the parties. (ix) Economic Sanctions Laws. Customer acknowledges that Motorola Solutions is subject to economic sanctions laws, including but not limited to those enforced by the U.S. Department of the Treasury's Office of Foreign Assets Control ("OFAC"), the European Union, and the United Kingdom. Accordingly, Customer shall comply with all economic sanctions laws of the United States, the European Union, and the United Kingdom. Customer shall not provide access to Motorola Solutions Services to any individuals identified on OFAC's list of Specially Designated Nationals ("SON List"), the UK's HM Treasury's Consolidated List of Sanctions Targets, or the EU's Consolidated List of Persons, Groups, and Entities Subject to EU Financial Sanctions. Customer shall not take any action which would place Motorola Solutions in a position of non- compliance with any such economic sanctions laws. (x) Retention of Records. For uses of GLB Data, DPPA Data and MVR Data, as described in Sections 2(ii), 2(iii) and 2(vii), Customer shall maintain for a period of five (5) years a complete and accurate record (including consumer identity, purpose and, if applicable, consumer authorization) pertaining to every access to such data. (xi) Software. To the extent that Customer is using software provided by Motorola Solutions ("Software"), whether hosted by Motorola Solutions or installed on Customer's equipment, such Software shall be deemed provided under a limited, revocable license, for the sole purpose of using the Motorola Solutions Services. In addition, the following terms apply: Customer shall not (a) use the Software to store or transmit infringing, libelous, or otherwise unlawful or tortuous material, or to store or transmit material in violation of third-party privacy rights, (b) use the Software to store or transmit spyware, adware, other malicious programs or code, programs that infringe the rights of others, or programs that place undue burdens on the operation of the Software, or (c) interfere with or disrupt the integrity or performance of the Software or data contained therein . The use of the Software will be subject to any other restrictions (such as number of users, features, or duration of use) agreed to by the parties or as set forth in a Schedule A. (xii) Non-FCRA Use Restrictions. The LN Services described in a Schedule A (as defined in these Master Terms) as Non-FCRA are not provided by "consumer reporting agencies," as that 34 May 10, 2022 Item #11 Page 343 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-8860-74DCD9D59AF5 term is defined in the Fair Credit Reporting Act (15 U.S.C. § 1681, et seq.) ("FCRA") and do not constitute "consumer reports," as that term is defined in the FCRA (the "Non-FCRA LN Services"). Accordingly, the Non-FCRA LN Services may not be used in whole or in part as a factor in determining eligibility for credit, insurance, employment or another purpose in connection with which a consumer report may be used under the FCRA. Further, (A) Customer certifies that it will not use any of the information it receives through the Non-FCRA LN Services to determine, in whole or in part an individual's eligibility for any of the following products, services or transactions: (1) credit or insurance to be used primarily for personal, family or household purposes; (2) employment purposes; (3) a license or other benefit granted by a government agency; or (4) any other product, service or transaction in connection with which a consumer report may be used under the FCRA or any similar state statute, including without limitation apartment rental, check-cashing, or the opening of a deposit or transaction account; (B) by way of clarification, without limiting the foregoing, Customer may use, except as otherwise prohibited or limited by the Master Terms, information received through the Non-FCRA LN Services for the following purposes: (1) to verify or authenticate an individual's identity; (2) to prevent or detect fraud or other unlawful activity; (3) to locate an individual; (4) to review the status of a legal proceeding; (5) to determine whether to buy or sell consumer debt or a portfolio of consumer debt in a commercial secondary market transaction, provided that such determination does not constitute in whole or in part, a determination of an individual consumer's eligibility for credit or insurance to be used primarily for personal, family or household purposes; (C) specifically, if Customer is using the Non-FCRA LN Services in connection with collection of a consumer debt on its own behalf, or on behalf of a third party, Customer shall not use the Non-FCRA LN Services: (1) to revoke consumer credit; (2) to accelerate, set or change repayment terms; or (3) for the purpose of determining a consumer's eligibility for any repayment plan; provided, however, that Customer may, consistent with the certification and limitations set forth in this Section, use the Non-FCRA LN Services for identifying, locating, or contacting a consumer in connection with the collection of a consumer's debt or for prioritizing collection activities; and (D) Customer shall not use any of the information it receives through the Non- FCRA LN Services to take any "adverse action," as that term is defined in the FCRA. (xiii) FCRA Services. If a Customer desires to use a product described in a Schedule A (Customer price schedule) as an FCRA product, Customer will execute an FCRA Addendum to the Master Terms. The FCRA product will be delivered by an affiliate of LNRSFL, LexisNexis Risk Solutions Inc., in accordance with the terms and conditions of the Master Terms. 2. TERMS APPLICABLE TO PUBLIC SAFETY DATA EXCHANGE DATABASE I. Public Safety Data Exchange Database 1. Motorola Solutions maintains the LexisNexis Public Safety Data Exchange Database ("PSDEX"), which contains information related to public safety and state and local law enforcement investigations. PSDEX is compiled from information submitted by PSDEX customers and enhanced by Motorola Solutions data and technology. 2. In exchange for good and valuable consideration, including access to PSDEX, Customer hereby agrees to contribute public safety information that may be used for analysis, investigations and reporting (the "Customer Data Contribution"). 3. LN's obligations. a. Motorola Solutions agrees to provide PSDEX information to Customer. 35 May 10, 2022 Item #11 Page 344 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-8860-74DCD9D59AF5 b. Motorola Solutions agrees to provide Customer with instructions for submitting information to the PSDEX database and for using the PSDEX service. 4. Customer obligations. a. Customer agrees to submit to Motorola Solutions, with reasonable promptness and consistency, Customer Data Contributions. b. Customer acknowledges and agrees that it is solely responsible for the content of the Customer Data Contributions submitted to Motorola Solutions and that it shall use reasonable care to ensure the information submitted is a reasonable reflection of the actual report. Each submission to Motorola Solutions with respect to an incident or subject constitutes a Customer Data Contribution. c. Customer's disclosure of information to Motorola Solutions is and will be in compliance with all applicable laws, regulations and rulings. d. Customer agrees to notify Motorola Solutions promptly of any change in status, factual background, circumstances or errors concerning any Customer Data Contribution previously provided to Motorola Solutions. Customer further agrees to submit corrected information in a timely manner. Customer agrees that it will fully and promptly cooperate with Motorola Solutions should any inquiry about the Customer Data Contributions arise. e. The following named individual/department shall serve as the contact person(s) for submissions made to Motorola Solutions. The contact person shall respond to requests from Motorola Solutions for clarification or updates on incident reports submitted by Customer during normal business hours, and Customer will not reasonably withhold from Motorola Solutions information on any such submission. Motorola Solutions shall not reveal the identity of the Customer's contact person(s) to any other PSDEX customer without Customer's consent. Name: Mickey Williams Title: Police Chief Address: ~?-5....,6....,0........,O ... c ... ia~□~W~a...,y,..,,~G-a~rls-h-a~d...,,_.C........,A....,9""2_0_1~0-___ _ Phone: (760) 931-2197 Fax: (760) 931-84 73 Email: mickey.williams@carlsbadca.gov f. Customer agrees that it will access information contributed to PSDEX by other customers only through Motorola Solutions. g. Customer agrees that Motorola Solutions and all other PSDEX customers shall not be liable to Customer, and Customer hereby releases Motorola Solutions and all other PSDEX customers from liability to Customer, for any claims, damages, liabilities, losses and injuries arising out of, or caused in whole or in part by Motorola Solutions or each such other PSDEX customer's negligence, gross negligence, willful misconduct and other acts and omissions in reporting or updating incidents of alleged wrongdoing for inclusion in PSDEX. Other PS DEX customers are intended to be third party beneficiaries of this paragraph. II. Public Safety Exchange Database General Terms 1. LICENSE GRANT. Customer, at no charge, hereby grants to Motorola Solutions a paid up, irrevocable, worldwide, non-exclusive license to use, adapt, compile, aggregate, create derivative work_s, transfer, transmit, publish and distribute to PSDEX 36 May 10, 2022 Item #11 Page 345 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 customers the Customer Data Contributions for use in PSDEX and all successor databases and/or information services provided by Motorola Solutions or LexisNexis. 2. GOOGLE GEOCODER. Motorola Solutions used Google Geocoder to geocode address locations that do not already contain "X" and "Y" coordinates. Any "X" and "Y" coordinate information provided by the Customer is assumed by Motorola Solutions to be accurate and will not be geocoded by Google Geocoder. Crime dot locations geocoded by Google Geocoder as displayed in PSDEX are approximate due to automated location methods and address inconsistencies. 3. DATA DISCLAIMER. Motorola Solutions is not responsible for the loss of any data or the accuracy of the data, or for any errors or omissions in the Motorola Solutions Services or the use of the Motorola Solutions Services or data therein by any third party, including the public or any law enforcement or governmental agencies. 4. LINKS TO THIRD PARTY SITES. PSDEX may contain links or produce search results that reference links to third party websites ("Linked Sites"). Motorola Solutions has no control over these Linked Sites or the content within them. Motorola Solutions cannot and does not guarantee, represent, or warrant that the content contained in the Linked Sites, including, without limitation other links, is accurate, legal, and/or inoffensive. Motorola Solutions does not endorse the content of any Linked Site, nor does it warrant that a Linked Site will not contain computer viruses or other harmful code. By using PS DEX to search for or link to Linked Sites, Customer agrees and understands that such use is entirely at its own risk, and that Customer may not make any claim against Motorola Solutions for any damages or losses whatsoever resulting from such use. 5. OWNERSHIP OF SUBMITTED CONTENT. All information provided by a PSDEX customer is offered and owned by that customer. Unless otherwise indicated by such customer, all data will be retained by Motorola Solutions and remain accessible by other PSDEX customers in accordance with the provisions of this Addendum and a de- identified subset of the data will remain available to the general public through the CrimeReports.com service or its successor database. 3. SECURITY. 3.1 Security of Information. Customer acknowledges that the information available through the Motorola Solutions Services may include personally identifiable information and it is Customer's obligation to keep all such accessed information confidential and secure. Customer must name a System Administrator who will be responsible for maintaining the following records: 1) User IDs including a complete list of each user name associated with each User ID, ensuring that each User ID is assigned to only one individual. User IDs and passwords may not be shared, and "generic" User IDs and passwords are not permitted. 2) Documentation of monthly verification to ensure that each active User ID corresponds to a Customer's current employee, and confirming that employee is an authorized user. User IDs will conform to the standards at https://www.fbi.gov/services/cjis/cjis-security-policy-resource- center. Accordingly, Customer shall (a) restrict access to Motorola Solutions Services to those employees who have a need to know as part of their official duties; (b) ensure that none of its employees shall (i) obtain and/or use any information from the Motorola Solutions Services for personal reasons, or (ii) transfer any information received through the Motorola Solutions Services to any party except as permitted hereunder; (c) keep all user identification numbers, and related passwords, or other security measures (collectively, "User IDs") confidential and prohibit the sharing of User IDs; (d) immediately deactivate the User ID of any employee who 37 May 10, 2022 Item #11 Page 346 of 604 DocuSign Envelope ID: AB2013B4-94BF-4BOC-B860-74DCD9D59AF5 no longer has a need to know, or for terminated employees on or prior to the date of termination; (e) in addition to any obligations under Paragraph 1, take all commercially reasonable measures to prevent unauthorized access to, or use of, the Motorola Solutions Services or data received therefrom, whether the same is in electronic form or hard copy, by any person or entity; (f) maintain and enforce data destruction procedures to protect the security and confidentiality of all information obtained through Motorola Solutions Services as it is being disposed; (g) purge all information received through the Motorola Solutions Services within ninety (90) days of initial receipt; provided that Customer may extend such period if and solely to the extent such information is retained thereafter in archival form to provide documentary support required for Customer's legal or regulatory compliance efforts; (h) be capable of receiving the Motorola Solutions Services where the same are provided utilizing "secure socket layer," or such other means of secure transmission as is deemed reasonable by Motorola Solutions; (i) not access and/or use the Motorola Solutions Services via mechanical, programmatic, robotic, scripted or other automated search means, other than through batch or machine-to-machine applications approved by Motorola Solutions; U) take all steps to protect their networks and computer environments, or those used to access the Motorola Solutions Services, from compromise; (k) on at least a quarterly basis, review searches performed by its User IDs to ensure that such searches were performed for a legitimate business purpose and in compliance with all terms and conditions herein; and (I) maintain policies and procedures to prevent unauthorized use of User IDs and the Motorola Solutions Services. Customer will immediately notify Motorola Solutions, by written notification to Motorola Solutions, if Customer suspects, has reason to believe or confirms that a User ID or the Motorola Solutions Services (or data derived directly or indirectly therefrom) is or has been lost, stolen, compromised, misused or used, accessed or acquired in an unauthorized manner or by any unauthorized person, or for any purpose contrary to the terms and conditions herein. 3.2 Security Events. To the extent permitted under applicable law, Customer shall remain solely liable for all costs associated therewith and shall further reimburse Motorola Solutions for any expenses it incurs due to Customer's failure to prevent such impermissible use or access of User IDs and/or the Motorola Solutions Services, or any actions required as a result thereof. Furthermore, in the event that the Motorola Solutions Services provided to the Customer include personally identifiable information (including, but not limited to, social security numbers, driver's license numbers or dates of birth), the following shall apply: Customer acknowledges that, upon unauthorized acquisition or access of or to such personally identifiable information, including but not limited to that which is due to use by an unauthorized person or due to unauthorized use (a "Security Event"), Customer shall, in compliance with law, notify the individuals whose information was potentially accessed or acquired that a Security Event has occurred, and shall also notify any other parties (including but not limited to regulatory entities and credit reporting agencies) as may be required in Motorola Solutions' reasonable discretion. Customer agrees that such notification shall not reference Motorola Solutions or the product through which the data was provided, nor shall Motorola Solutions be otherwise identified or referenced in connection with the Security Event, without Motorola Solutions' express written consent. Customer shall be solely responsible for any other legal or regulatory obligations which may arise under applicable law in connection with such a Security Event and shall bear all costs associated with complying with legal and regulatory obligations in connection therewith. To the extent permitted under applicable law, Customer shall remain solely liable for claims that may arise from a Security Event, including, but not limited to, costs for litigation (including attorneys' fees), and reimbursement sought by individuals, including but not limited to, costs for credit monitoring or allegations of loss in connection with the Security Event. Customer shall provide samples of all proposed materials 38 May 10, 2022 Item #11 Page 347 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-8860-74DCD9D59AF5 to notify consumers and any third-parties, including regulatory entities, to Motorola Solutions for review and approval prior to distribution. In the event of a Security Event, Motorola Solutions may, in its sole discretion, take immediate action, including suspension or termination of Customer's account, without further obligation or liability of any kind. 4. PERFORMANCE. Motorola Solutions will use commercially reasonable efforts to deliver the Motorola Solutions Services requested by Customer and to compile information gathered from selected public records and other sources used in the provision of the Motorola Solutions Services; provided, however, that the Customer accepts all information "AS IS". Customer acknowledges and agrees that Motorola Solutions obtains its data from third party sources, which may or may not be completely thorough and accurate, and that Customer shall not rely on Motorola Solutions for the accuracy or completeness of information supplied through the Motorola Solutions Services. Without limiting the foregoing, the criminal record data that may be provided as part of the Motorola Solutions Services may include records that have been expunged, sealed, or otherwise have become inaccessible to the public since the date on which the data was last updated or collected. Customer understands that Customer may be restricted from accessing certain Motorola Solutions Services which may be otherwise available. Motorola Solutions reserves the right to add materials and features to, and to discontinue offering any of the materials and features that are currently a part of, the Motorola Solutions Services. In the event that Motorola Solutions discontinues a material portion of the materials and features that Customer regularly uses in the ordinary course of its business, and such materials and features are part of a flat fee subscription plan to which Customer has subscribed, Motorola Solutions will, at Customer's option, issue a prorated credit to Customer's account. s. INTELLECTUAL PROPERTY; CONFIDENTIALITY. Customer agrees that Customer shall not reproduce, retransmit, republish, or otherwise transfer for any commercial purposes the Motorola Solutions Services. Customer acknowledges that Motorola Solutions (and/or its third party data providers) shall retain all right, title, and interest under applicable contractual, copyright, patent, trademark, Trade Secret and related laws in and to the Motorola Solutions Services and the information that they provide. Customer shall use such materials in a manner consistent with Motorola Solutions' interests and the terms and conditions herein, and shall promptly notify Motorola Solutions of any threatened or actual infringement of Motorola Solutions' rights. Customer and Motorola Solutions acknowledge that they each may have access to confidential information of the disclosing party ("Disclosing Party") relating to the Disclosing Party's business including, without limitation, technical, financial, strategies and related information, computer programs, algorithms, know-how, processes, ideas, inventions (whether patentable or not), schematics, Trade Secrets (as defined below) and other information (whether written or oral), and in the case of Motorola Solutions' information, product information, pricing information, product development plans, forecasts, the Motorola Solutions Services, and other business information ("Confidential Information"). Confidential Information shall not include information that: (i) is or becomes (through no improper action or inaction by the Receiving Party (as defined below)) generally known to the public; (ii) was in the Receiving Party's possession or known by it prior to receipt from the Disclosing Party; (iii) was lawfully disclosed to Receiving Party by a third-party and received in good faith and without any duty of confidentiality by the Receiving Party or the third-party; or (iv) was independently developed without use of any Confidential Information of the Disclosing Party by 39 May 10, 2022 Item #11 Page 348 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-8860-74DCD9D59AF5 employees of the Receiving Party who have had no access to such Confidential Information. "Trade Secret" shall be deemed to include any information which gives the Disclosing Party an advantage over competitors who do not have access to such information as well as all information that fits the definition of "trade secret" set forth under applicable law. Each receiving party ("Receiving Party") agrees not to divulge any Confidential Information or information derived therefrom to any third-party and shall protect the confidentiality of the Confidential Information with the same degree of care it uses to protect the confidentiality of its own confidential information and trade secrets, but in no ~vent less than a reasonable degree of care. Notwithstanding the foregoing, the Receiving Party may disclose Confidential Information solely to the extent required by subpoena, court order or other governmental authority, provided that the Receiving Party shall give the Disclosing Party prompt written notice of such subpoena, court order or other governmental authority so as to allow the Disclosing Party to have an opportunity to obtain a protective order to prohibit or restrict such disclosure at its sole cost and expense. Confidential Information disclosed pursuant to subpoena, court order or other governmental authority shall otherwise remain subject to the terms applicable to Confidential Information. Each party's obligations with respect to Confidential Information shall continue for the term of these Master Terms and for a period of five (5) years thereafter, provided however, that with respect to Trade Secrets, each party's obligations shall continue for so long as such Confidential Information continues to constitute a Trade Secret. Notwithstanding the foregoing, if Customer is bound by the Freedom of Information Act, 5 U.S.C. 552, or other federal, state, or municipal open records laws or regulations which may require disclosure of information, and disclosure thereunder is requested, Customer agrees that it shall notify Motorola Solutions in writing and provide Motorola Solutions an opportunity to object, if so permitted thereunder, prior to any disclosure. 6. DISCLAIMER OF WARRANTIES. MOTOROLA SOLUTIONS (SOLELY FOR PURPOSES OF INDEMNIFICATION, DISCLAIMER OF WARRANTIES, AND LIMITATION ON LIABILITY, MOTOROLA SOLUTIONS, ITS SUBSIDIARIES AND AFFILIATES, AND ITS DATA PROVIDERS ARE COLLECTIVELY REFERRED TO ("MOTOROLA SOLUTIONS") DOES NOT MAKE AND HEREBY DISCLAIMS ANY WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE MOTOROLA SOLUTIONS SERVICES. MOTOROLA SOLUTIONS DOES NOT WARRANT THE CORRECTNESS, COMPLETENESS, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE OF THE MOTOROLA SOLUTIONS SERVICES OR INFORMATION PROVIDED THEREIN. Due to the nature of public record information, the public records and commercially available data sources used in the Motorola Solutions Services may contain errors. Source data is sometimes reported or entered inaccurately, processed poorly or incorrectly, and is generally not free from defect. The Motorola Solutions Services are not the source of data, nor are they a comprehensive compilation of the data. Before relying on any data, it should be independently verified. 7. LIMITATION OF LIABILITY. Neither Motorola Solutions, nor its subsidiaries and affiliates, nor any third-party data provider shall be liable to Customer (or to any person claiming through Customer to whom Customer may have provided data from the Motorola Solutions Services) for any loss or injury arising out of or caused in whole or in part by use of the Motorola Solutions Services. If, notwithstanding the foregoing, liability can be imposed on Motorola Solutions, Customer agrees that Motorola Solutions' 40 May 10, 2022 Item #11 Page 349 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9O59AF5 8. 9. 10. aggregate liability for any and all losses or injuries arising out of any act or omission of Motorola Solutions in connection with anything to be done or furnished under these Master Terms, regardless of the cause of the loss or injury, and regardless of the nature of the legal or equitable right claimed to have been violated, shall never exceed the amount of fees actually paid by Customer to Motorola Solutions under this Agreement during the six (6) month period preceding the event that gave rise to such loss or injury. Customer covenants and promises that it will not sue Motorola Solutions for an amount greater than such sum even if Customer and/or third-parties were advised of the possibility of such damages and that it will not seek punitive damages in any suit against Motorola Solutions. IN NO EVENT SHALL Motorola Solutions BE LIABLE FOR ANY INDIRECT, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, HOWEVER ARISING, INCURRED BY CUSTOMER. AUDIT. Customer understands and agrees that, in order to ensure compliance with the FCRA, GLBA, DPPA, other similar state or federal laws, regulations or rules, regulatory agency requirements of these Master Terms, Motorola Solutions' obligations under its contracts with its data providers, and Motorola Solutions' internal policies, Motorola Solutions may conduct periodic reviews and/or audits of Customer's use of the Motorola Solutions Services. Customer agrees to cooperate fully with any and all audits and to respond to any such audit inquiry within ten (10) business days, unless an expedited response is required. Violations discovered in any review and/or audit by Motorola Solutions will be subject to immediate action including, but not limited to, suspension or termination of the license to use the Motorola Solutions Services, reactivation fees, legal action, and/or referral to federal or state regulatory agencies. EMPLOYEE TRAINING. Customer shall train new employees prior to allowing access to Motorola Solutions Services on Customer's obligations under these Master Terms, including, but not limited to, the licensing requirements and restrictions under Paragraph 1, the security requirements of Paragraph 3. Customer shall conduct a similar review of its obligations under these Master Terms with existing employees who have access to Motorola Solutions Services no less than annually. Customer shall keep records of such training. CUSTOMER INFORMATION. Customer certifies that Customer has not been the subject of any proceeding regarding any trust-related matter including, but not limited to, fraud, counterfeiting, identity theft and the like, and that Customer has not been the subject of any civil, criminal or regulatory matter that would create an enhanced security risk to Motorola Solutions, the Motorola Solutions Services or the data, including but not limited to, any matter involving potential violations of the GLBA, the DPPA, the FCRA, the Fair Debt Collection Practices Act ("FDCPA") (15 U.S.C. § 1692-1692p) or any other similar legal or regulatory guidelines. If any such matter has occurred, Customer shall attach a signed statement, along with all relevant supporting documentation, providing all details of this matter prior to execution of this Agreement. Customer shall notify Motorola Solutions immediately of any changes to the information on Customer's Application for the Motorola Solutions Services, and, if at any time Customer no longer meets Motorola Solutions' criteria for providing service, Motorola Solutions may terminate this agreement. Customer is required to promptly notify Motorola Solutions of a change in ownership of Customer, any change in the name of Customer, and/or any change in the physical address of Customer. 41 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 11.CHANGE IN AGREEMENT. By receipt of the Motorola Solutions Services, Customer agrees to, and shall comply with, changes to the restricted license granted to Customer hereunder and as Motorola Solutions shall make from time to time by notice to Customer. Notices to Customer will be provided via written communication. All e-mail notifications shall be sent to the individual named in the Customer Administrator Contact Information section of the Application, unless stated otherwise. Motorola Solutions may, at any time, impose restrictions and/or prohibitions. on the Customer's use of some or all of the Motorola Solutions Services, following reasonable notice to Customer. Customer understands that such restrictions or changes in access may be the result of a modification in Motorola Solutions policy, a modification of third-party agreements, a modification in industry standards, a Security Event or a change in law or regulation, or the interpretation thereof. Upon written notification by Motorola Solutions of such restrictions, Customer agrees to comply with such restrictions. AUTHORIZATION AND ACCEPTANCE OF TERMS I HEREBY CERTIFY that I am executing this Attachment A, to the Subscription Services Agreement as the authorized representative of Customer and that I have direct knowledge of and affirm all facts and representations made above Print Name Title uj'\ fv\lJA,� J Dated __ ___,D.__,{,-:(-=1C...-=::=---(mm/d/yy 42 May 10, 2022 Item #11 Page 350 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 LexisNexis Risk Solutions Government Application The information submitted on this Application will be used to determine the applicant's eligibility for accessing the services and products of LexisNexis Risk Solutions FL Inc. and its affiliates (hereinafter "LN"). To avoid delay, please provide all information requested. By submitting this Application, the applicant hereby authorizes LN to independently verify the information submitted and perform research about the individuals identified. Acceptance of this Application does not automatically create a business relationship between LN and the applicant. LN reserves the right to reject this Application with or without cause and to request additional information. Applicant acknowledges and understands that LN will only allow applicant access to the LN Services if applicant's credentials can be verified in accordance with LN's internal credentialing procedures. Section I -Agency Information -please do not use abbreviations Full legal name of agency: Main phone number for address*: City of Carlsbad 442-339-2100 *If this is a cell, additional documents may be required If this application is for an additional account, Parent Fax number: account number: Physical Address where LN services will be Previous address if at the current address less than 6 accessed -months: P.O. Box/Mail Drops cannot be accepted (street, city, state, zip): -------------2560 Orion Way Carlsbad, CA 92010 Website address: External Agency IP Address (https://www.whatismylP.com): www.carlsbadca.gov 69.75.46.170 External Agency IP Range -From: External Agency IP Range -To: 69.75.46.170 69.75.46.170 Agency information: □Federal Government □Federal Law Enforcement □Local/Municipal Government D State Government D State Law Enforcement [XI Local/Municipal Law Enforcement D Other (please explain): 43 May 10, 2022 Item #11 Page 351 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 Section II -Administrator and Main Contact Information (for additional administrators, please provide additional sheets) Product Administrator or Main Contact (first & last name): Javier Ruiz E-Mail Address:Javier.Ruiz@carlsbadca.gov Required for local and municipal agencies: Administrator Home Address (street, city, state, zip): 2560 Orion Way, Carlsbad, CA 92010 Title: Public Safety IT Manager Admin IP Address: 69.75.46.170 Administrator Date ofBirth: Section III -Billing Information Billing Contact (first & last name): check here if same as Administrator IXI Billing Address (street, city, state, zip): E-Mail Address: Do you require a PO number on invoice: IXI No □ Yes If Yes, provide PO Number: Title: Telephone: Sales Tax Exempt: □No □Yes -please provide proof of exemption Section IV -Business-to-Business Vendor Reference Required for local and municipal agencies: Company Name: Vigilant Solutions Business Address (street, city, state, zip): 1152 Stealth St, Livermore, CA 94551 E-mail Address:Daniel.Ramsden@vigilantsolutions.com Contact: Daniel Ramsden Contact Phone Number: 925-398-2079 Account Number (if applicable): Section V -Site Visits Site visits may be required to assure Applicant eligibility for LN products or services. By submitting this Application, Applicant agrees to authorize a site visit by LN or its approved third-party, and agrees to cooperate in its completion. If the contact for coordinating the site visit is not identified above as the Administrator, please provide the site visit contact's information below: Contact Name: Contact Phone: Javier Ruiz 442-339-2176 Contact Email Address: Javier.Ruiz@carlsbadca.gov 44 May 10, 2022 Item #11 Page 352 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9O59AF5 au onze o e 1ca 10n on e a o e gency 1s e a ove ge of the facts stated above. Applicant Nam s t>tt t \A,,J..,'.,) \ tN- 45 Date Signed: 2 Title: May 10, 2022 Item #11 Page 353 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 NON-FCRA PERMISSIBLE USE CERTIFICATION -GOVERNMENT Customer (Agency) Name: City of Carlsbad Police Department OBA: Address 2560 Orion Way City, State, Zip: Carlsbad, CA 92010 Contact Name: Mickey Williams Phone: 442-339-2100------------REQUIRED Please describe your purpose of use: __________ _ Law enforcement purposes including identifying suspects Definitions. Gramm-Leach-Bliley Act, (15 U.S.C. § 6801, et seq.) and related state laws (collectively, the "GLBA"). Drivers Privacy Protection Act, (18 U.S.C. § 2721 et seq.) and related state laws (collectively, the "DPPA") Law Enforcement Agencies Only: Review and, if appropriate, certify to the following: Customer represents and warrants that it will use the LN Services solely for law enforcement purposes, which comply with applicable privacy laws including, but not limited to the GLBA and the DPPA. To certify, check here: IXl Proceed to SECTION 3. QUALIFIED ACCESS SECTION l. GLBA EXCEPTION/PERMISSIBLE PURPOSE -NOT APPLICABLE TO LAW ENFORCEMENT Some LN Services use and/or display nonpublic personal information that is governed by the privacy provisions of the GLBA. Customer certifies it has the permissible purposes under the GLBA to use and/or obtain such information, as marked below, and Customer further certifies it will use such information obtained from LN Services only for such purpose(s) selected below or, if applicable, for the purpose(s) indicated by Customer electronically while using the LN Services, which purpose(s) will apply to searches performed during such electronic session: D No applicable GLBA exception/permissible use. Proceed to SECTION 2. DPPA PERMISSIBLE USES (At least one (I) must be checked to be permitted access to GLBA data) D As necessary to effect, administer, or enforce a transaction requested or authorized by the consumer. □ As necessary to effect, administer, or enforce a transaction requested or authorized by the consumer by verifying the identification information contained in applications. D To protect against or prevent actual or potential fraud, unauthorized transactions, claims or other liability. □In required institutional risk control programs. 46 May 10, 2022 Item #11 Page 354 of 604 I May 10, 2022 Item #11 Page 355 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9D59AF5 □ In resolving consumer disputes or inquiries. □ Use by persons, or their representatives, holding a legal or beneficial interest relating to the consumer. □ Use by persons acting in a fiduciary or representative capacity on behalf of the consumer. □ In complying with federal, state, or local laws, rules, and other applicable legal requirements. □ To the extent specifically permitted or required under other provisions oflaw and in accordance with the Right to Financial Privacy Act of 1978, to law enforcement agencies (including a Federal functional regulator, the Secretary of Treasury, a State insurance authority, or the Federal Trade Commission), self-regulatory organizations, or for an investigation on a matter related to public safety. SECTION 2. DPPA PERMISSIBLE USES -NOT APPLICABLE TO LAW ENFORCEMENT Some LN Services use and/or display personal information, the use of which is governed by the DPPA: Customer certifies it has a permissible use under the DPPA to use and/or obtain such information and Customer further certifies it will use such information obtained from LN Services only for one (1) or more of the purposes selected below or for the purpose(s) indicated by Customer electronically while using the LN Services, which purpose(s) will apply to searches performed during such electronic session: D No permissible use. Proceed to SECTION 3. QUALIFIED ACCESS (At least one (1) must be checked to be permitted access to DPPA data) □ For use in connection with any civil, criminal, administrative, or arbitral proceeding in any federal, state, or local court or agency or before any self-regulatory body, including the service of process, investigation in anticipation oflitigation, and the execution or enforcement of judgments and orders, or pursuant to an order of a federal, state, or local court. □ For use in the normal course of business by a legitimate business or its agents, employees, or contractors, but only- (A) to verify the accuracy of personal information submitted by the individual to the business or its agents, employees, or contractors; and (8) if such information as so submitted is not correct or is no longer correct, to obtain the correct information, but only for the purposes of preventing fraud by, pursuing legal remedies against, or recovering on a debt or security interest against, the individual. □ Use by a government agency, but only in carrying out its functions. □ Use by any person acting on behalf of a government agency, but only in carrying out the agency's functions. □ Use by an insurer (or its agent) in connection with claims investigation activities or antifraud activities. 47 DocuSign Envelope ID: AB201384-94BF-4B0C-8860-74DCD9D59AF5 □ In connection with motor vehicle safety or theft, or driver safety (except by or for a motor vehicle manufacturer). Use by an employer or its agents or insurer to obtain or verify information relating to a holder of a □ commercial driver's license that is required under Chapter 313 of Title 49 of the United States Code. □ For use in providing notice to the owners of towed or impounded vehicles. □ For use in connection with the operation of private toll transportation facilities. With regard to the information that is subject to the DPPA, some state laws' permissible uses may vary from the permissib-le uses identified above. In such cases, some state information may not be available under each permissible use listed above and/or Customer may be asked to ce1tify to a permissible use permitted by applicable state law to obtain information from a specific state. Customer agrees and certifies it will use the information described above only in accordance with the permissible uses selected above or those selected subsequently in connection with a specific information request. SECTION 3. QUALIFIED ACCESS Certain users ("Authorized Users") may be able to obtain full social security numbers (nine (9)digits) and driver's license numbers (collectively, "QA Data"), when appropriate, through some LN Services. Only those users that are within the Authorized User List below, and that use QA Data for an Authorized Use identified below, may qualify. To potentially qualify as an Authorized User, Customer must certify that its business is within the Authorized User List below and its use of QA Data is within the Authorized Use List below. □Customer is NOT requesting access to QA Data. Proceed to SECTION 4. DEA TH MASTER FILE rn Customer is requesting access to QA Data. Complete the sections below. What department will be using QA Data? _P_o_1i_·c_e _D_e_p_a _rt_m_e_n_t ________ _ SOCIAL SECURITY NUMBERS □Not an authorized user. Proceed to DRIVER'S LICENSE NUMBERS 1.AUTHOR[ZED USER (At least one (l) must be checked to receive Social Security Numbers) □ Federal, state or local government agency with law enforcement responsibilities. Special investigative unit, subrogation department and claims department of a private or public insurance company for the purposes of detecting, investigating or preventing fraud. 48 May 10, 2022 Item #11 Page 356 of 604 t ~ DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 □ Financial institution for the purposes of (a) detecting, investigating or preventing fraud, (b) compliance with federal or state laws or regulations, (c) collecting debt on their own behalf, and (d) such other uses as shall be appropriate and lawful. □Collection department of a creditor. □ Collection company acting on behalf of a creditor or on its own behalf. □ Other public or private entity for the purpose of detecting, investigating or preventing fraud. Describe your business: 2.AUTHORIZED USE (At least one (1) must be checked to receive Social Security Numbers) � Location of suspects or criminals. □ Location of non-custodial parents allegedly owing child support and ex-spouses allegedly owing spousal support. □ Location of individuals alleged to have failed to pay taxes or other lawful debts. □ Identity verification. □ Other uses similar to those described above. Describe your use: By selecting above, the Customer certifies that it is an Authorized User, and that it will use Social Security Numbers only for the purpose(s) it designated on the Authorized Use List and for no other purpose(s). DR1VER'S LICENSE NUMBERS □Not an authorized user. Proceed to SECTION 4. DEA TH MASTER FILE 1.AUTHOR1ZED USER (At least one (I) must be checked to receive Driver's License Numbers) Kl Federal, state or local government agency with law enforcement responsibilities. □ Special investigative unit, subrogation department and claims department of a private or public insurance company for the purposes of detecting, investigating or preventing fraud. □ Financial institution for the purposes of (a) detecting, investigating or preventing fraud, (b) compliance with federal or state laws or regulations, (c) collecting debt on their own behalf, and (d)such other uses as shall be appropriate and lawful. □ Collection department of a creditor. □ Collection company acting on behalf of a creditor or on its own behalf. 49 May 10, 2022 Item #11 Page 357 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 D Other public or private entity for the purpose of detecting, investigating or preventing fraud. Describe your business: 2.AUTHORfZED USE (At least one (1) must be checked to receive Driver's License Numbers) � Location of suspects or criminals. D Location of non-custodial parents allegedly owing child support and ex-spouses allegedly owing spousal support. D Location of individuals alleged to have failed to pay taxes or other lawful debts. IX] Identity verification. D Other uses similar to those described above. Describe your use: By selecting above, the Customer certifies that it is an Authorized User, and that it will use Driver's License Numbers only for the purpose(s) it designated on the Authorized Use List and for no other purpose(s). SECTION 4. DEA TH MASTER FILE For access to Limited Access DMF Data only. □No permissible purpose. Proceed to AUTHORIZATION AND ACCEPTANCE OF TERMS 1.Definitions. For purposes of this Certification, these terms are defined as follows: a.DMF Agreement: The Limited Access Death Master File Non-federal Licensee Agreement for Use and Resale executed by LexisNexis Risk Data Retrieval Services LLC, on behalf of itself, its affiliates and subsidiaries, and its and their successors,with the federal government (NTIS, as below defined). The DMF Agreement form is found at www.lexisnexis.com/risk/DMFDocuments. b.Certification Form: The Limited Access Death Master File Subscriber Certification Form executed by LexisNexis Risk Data Retrieval Services LLC, on behalf of itself, its affiliates and subsidiaries, and its and their successors, with the federalgovernment (NTIS, as below defined). The Certification Form is found at www.lexisnexis.com/risk/DMFDocuments. c.DMF: The federal Death Master File. d.NTIS: National Technical Information Service, U.S. Department of Commerce e.Open Access DMF: The DMF product made available through LN, which obtains the data from NTIS, and which does not include DMF with respect to any deceased 50 May 10, 2022 Item #11 Page 358 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-8860-74DCD9D59AF5 individual at any time during the three-calendar-year period beginning on the date of the individual's death. Open Access DMF data should not be accessed pursuant to this Certification but should be accessed pursuant to a customer contract for such DMF data that is not Limited Access DMF. f.Limited Access DMF: Limited Access DMF includes DMF data with respect to any deceased individual at any time during the three-calendar-year period beginning onthe date of the individual's death. Limited Access DMF is made available through LN as a Certified Person, by NTIS. This Certification governs Customer's access to Limited Access DMF from LN (or the applicable LN affiliate), whether full or partial Limited Access DMF records or indicators of deceased status, and via any format,including on line, XML feed, or in-house file processing through LN. 11.Certification. Customer's access to the Limited Access DMF requires certification of purpose, as required by 15 CFR Part 1110 and section I 00 I of Title 18, United States Code. Customer hereby certifies that it has the indicated permissible purpose(s) under part (a) of this Section II ("Certification") and that it meets the requirements of part (b) of this Section II: (a)Such Customer has a legitimate fraud prevention interest, or has a legitimate business purpose pursuant to a law, governmental rule, regulation, or fiduciary duty, will use theLimited Access DMF only for such purpose(s), and specifies the basis for so certifying as (choose any applicable purposes that apply to Customer's use): □Legitimate Fraud Prevention Interest: Customer has a legitimate fraud prevention interest to detect and prevent fraud and/or to confirm identities across its commercial business and/or government activities.□Legitimate Business Purpose Pursuant to a Law, Governmental Rule, Regulation, or Fiduciary Duty: Customer has one or more of the purposes permitted under 42 USC 1306c including fraud prevention and ID verification purposes. Customer's specific purpose(s) for obtaining Limited Access DMF data under this Certification is: D Fraud Prevention and identity verification purposes !XI For uses permitted or required by law □For uses permitted or required by governmental rules□For uses permitted or required by regulation□For uses necessary to fulfill or avoid violating fiduciary duties and (b)Customer has systems, facilities, and procedures in place to safeguard Limited Access DMF, and experience in maintaining the confidentiality, security, and appropriate use of such information, pursuant to requirements similar to the requirements of section6103(p )( 4) of the Internal Revenue Code of 1986, and (c)Customer agrees to satisfy the requirements of such section 6103(p)( 4) as if such section applied to Customer. 51 May 10, 2022 Item #11 Page 359 of 604 May 10, 2022 Item #11 Page 360 of 604 OocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 Ill. Flow-down Agreement Terms and Conditions The Parties a~ee that the following terms and conditions are applicable to Customer and ordering, access to, and use of Limited Access DMF: 1. Compliance with Terms of Agreement and CFR. Customer of Limited Access DMF must comply with the terms of the DMF Agreement and the requirements of 15 CFR Part 11 10, as though set forth as a Subscriber therein, and Customers may not further distribute the Limited Access DMF. 2. Change in Status. Should Customer's status change such that it would no longer have a permissible purpose to access Limited Access DMF under this Addendum, Customer agrees to immediately notify LN in writing in the manner and format required for notices under the Contract. Should Customer cease to have access rights to Limited Access DMF, Customer shall destroy all Limited Access DMF, and will certify to LN in writing that is has destroyed all such DMF. 3. Security and Audit. Customer will at all times have security provisions in place to protect the Limited Access DMF from being visible, searchable, harvestable or in any way discoverable on the World Wide Web. Customer understands that any successful attempt by any person to gain unauthorized access to or use of the Limited Access DMF provided by LN may result in immediate termination of Customer's access and this Addendum. In addition, any successful attempt by any person to gain unauthorized access may under certain circumstances result in penalties as prescribed in 15 CFR § 1110.200 levied on Customer and the person attempting such access. Customer will take appropriate action to ensure that all persons accessing the Limited Access DMF it obtains from LN are aware of their potential liability for misuse or attempting to gain unauthorized access. Any such access or attempted access is a breach, or attempted breach, of security and Customer must immediately report the same to NTIS at dmfcert@ntis.gov; and to LN by written notification to the LN Information Assurance and Data ~rotection Organization at 1000 Alderman Drive, Alpharetta, Georgia 30005 and by email (security.investigations@lexisnexis.com) and by phone (1-888-872-5375). Customer agrees to be subject to audit by LN and/or NTIS to determine Customer's compliance with the requirements of this Addendum, the Agreement, and 15 CFR Part 1110. Customer agrees to retain a list of all employees, contractors, and subcontractors to which it provides Limited Access DMF and to make that list available to NTIS and/or LN as part of any audits conducted hereunder. Customer will not resell or otherwise redistribute the Limited Access DMF. 4. Penalties. Customer acknowledges that failure to comply with the provisions of paragraph (3) of the Certification Form may subject Customer to penalties under 15 CFR § 1110.200 of $1 ,000 for each disclosure or use, up to a maximum of $250,000 in penalties per calendar year, or potentially uncapped for willful disclosure. s. Law, Dispute Resolution, and Forum. Customer acknowledges that this Addendum is governed by the terms of federal law. Customer acknowledges that the terms of Section 14 of the Agreement govern disagreement handling, and, without limitation to the foregoing, that jurisdiction is federal court. 6. Liability. The U.S. Government/NTIS and LN (a) make no warranty, express or implied, with respect to information provided under the Agreement, including but not limited to, implied warranties of merchantability and fitness for any particular use; (b) assume no liability for any direct, indirect or consequential damages flowing from any 52 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 use of any part of the Limited Access DMF, including infringement of third party intellectual property rights; and (c) assume no liability for any errors or omissions in Limited Access DMF. The Limited Access DMF does have inaccuracies and NTIS and the Social Security Administration (SSA), which provides the DMF to NTIS, and LN, do not guarantee the accuracy of the Limited Access DMF. SSA does not have a death record for all deceased persons. Therefore, the absence of a particular person in the Limited Access DMF is not proof that the individual is alive. Further, in rare instances, it is possible for the records of a person who is not deceased to be included erroneously in the Limited Access DMF. Customer specifically acknowledges the terms of Attachment B to the Agreement, which terms apply to Customer. 7.Indemnification. To the extent not prohibited by law, Customer shall indemnify and hold harmless NTIS and the Department of Commerce from all claims, liabilities, demands, damages, expenses, and losses arising from or in connection with Customer's, Customer's employees', contractors', or subcontractors' use of the Limited Access DMF. This provision will include any and all claims or liability arising from intellectual property rights. 8.Survival. Provisions hereof related to indemnification, use and protection of Limited Access DMF, audit, disclaimer of warranties, and governing law shall survive termination of this Addendum. 9.Conflict of Terms. Customer acknowledges that the terms of this Addendum, in the event of conflict with the terms of the Contract, apply in addition to, and not in lieu of, such Contract terms, with respect to the Limited Access DMF only. AUTHORIZA TlON AND ACCEPTANCE OF TERMS I HEREBY CERTIFY that I have direct knowledge authorized to execute this Certification on behalf of th the cts stated above and that I am listed above. Signature-+---""--,__ ______ _ Print Name � \ Title LA_� t,J\JA/·�,uf Dated (z:MA,\/'Z.2 53 May 10, 2022 Item #11 Page 361 of 604 CUSTOMER( J ~ -C\AJ ~ May 10, 2022 Item #11 Page 362 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 Mobile Video Addendum This Mobile Video Addendum (this "MVA") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 ("Motorola") and Customer (as defined in the MCA), and will be subject to, and governed by, the terms of the Master Customer Agreement (the "MCA"), and the applicable Addenda. Capitalized terms used in this MVA, but not defined herein, will have the meanings set forth in the MCA or the applicable Addenda. 1. Addendum. This MVA governs Customer's purchase of any Motorola mobile video Products, including participation in Motorola's Video-as-a-Service Program ("VaaS Program"). A "Mobile Video System" is a solution that includes at least one mobile video Product and requires Integration Services to deploy such mobile video Product or the associated evidence management Product at a Customer Site. In addition to the MCA, other Addenda may be applicable to Products offered under this MVA, including the Subscription Software Addendum ("SSA"), with respect to Subscription Software, and the Equipment Purchase and Software License Addendum ("EPSLA"), with respect to Licensed Software and Equipment, as each of those terms are defined therein, and as further described below. This MVA will control with respect to conflicting or ambiguous terms in the MCA or any other applicable Addendum, but only as applicable to the Mobile Video System or other Products purchased under this MVA · and not with respect to other Products or Services. 2. Evidence Management Systems; Applicable Terms and Conditions. 2.1. On-Premise Evidence Management. If Customer purchases a Mobile Video System where Equipment and Licensed Software for evidence management is installed at Customer Sites (an "On-Premises Evidence Management System"), then, unless the Ordering Document(s) specify that any software is being purchased on a subscription basis (i.e., as Subscription Software), any (i) Equipment and (ii) Licensed Software installed at Customer Sites or on Customer-Provided Equipment, in each case purchased in connection with the On-Premises Evidence Management System, are subject to the EPSLA. On-Premises Evidence Management Systems described in this Section qualify for the System Warranty as described in Section 4 - On-Premises Evidence Management System Warranty (the "System Warranty"). 2.2. Cloud Hosted Evidence Management. If Customer purchases Mobile Video System where the software for evidence management is hosted in a data center and provided to Customer as a service ("Cloud Hosted Evidence Management System"), including CommandCentral Evidence and Evidencelibrary.com Products, then such Cloud Hosted Evidence Management System is subject to the SSA. Any Equipment purchased in connection with Cloud Hosted Evidence Management System is subject to the EPSLA. Cloud Hosted Evidence Management System described in this Section do not qualify for the System Warranty. System completion, however, is determined in accordance with the provisions of Section 7 -System Completion below. 2.3. Services. Any Integration Services or Maintenance and Support Services purchased in connection with, or included as a part of, a Mobile Video System are subject to the MCA, and as described in the applicable Ordering Document. 3. Payment. Customer will pay invoices for the Products and Services covered by this MVA in accordance with the invoice payment terms set forth in the MCA. Fees for Mobile Video Systems will be invoiced as of the System Completion Date, unless another payment process or schedule or milestones are set forth in an Ordering Document or applicable Addendum. In addition to Equipment, Licensed Software, Subscription Software and Integration Services (as applicable) sold as part of a Mobile Video System, the Ordering Documents for a Mobile Video 54 May 10, 2022 Item #11 Page 363 of 604 DocuSign Envelope ID: AB201384-94BF-4B0C-B860-74DCD9D59AF5 System may also include post-deployment Integration Services or other Services which are to be provided following the date of functional demonstration ("Post-Deployment Services"). Post- Deployment Services will be invoiced upon their completion and paid by Customer in accordance with the terms of the MCA. 4. On-Premises Evidence Management System Warranty. Subject to the disclaimers in the MCA and any other applicable Addenda, Motorola represents and warrants that, on the System Completion Date (as defined below) for an On-Premises Evidence Management System described in Section 2.1 -On-Premises Evidence Management (a) such On-Premises Evidence Management System will perform in accordance with the descriptions in the applicable Ordering Documents in all material respects, and (b) if Customer has purchased any Equipment or Motorola Licensed Software (but, for clarity, excluding Subscription Software) as part of such On-Premises Evidence Management System, the warranty period applicable to such Equipment and Motorola Licensed Software will continue for a period of one (1) year commencing upon the System Completion Date for the On-Premises Evidence Management System that includes such Products, or on the applicable Product Completion Date, if earlier, instead of commencing upon delivery of the Products in accordance with the terms and conditions set forth in Section 6 - Representations and Warranties; Liabilities of the EPSLA. The warranties set forth in the applicable Addenda are not otherwise modified by this MV A. 5. Additional Software and Video Terms. 5.1. Unlimited Storage. In the event Customer purchases a Cloud Hosted Evidence Management System with "Unlimited Storage", including evidence management under the VaaS Program, then "Unlimited Storage" means storage of all data captured using Equipment sold under this MVA, provided that (1) video recording~ are recorded in an event-based setting where users are not recording an entire shift under one video footage and (2) Customer's data retention policies and practices do not result in the retention of data beyond the legal minimums set forth by the State in which the Customer resides. In the event Customer does not comply with the preceding clauses (1) and (2), Motorola shall have the right to charge Customer for such excess data storage at the prevailing rates. Motorola also has the right to place any data that has not been accessed for a consecutive six (6) month period into archival storage, retrieval of which may take up to twenty-four (24) hours from any access request. 5.2. Applicable End User Terms. Additional license terms apply to third-party software included in certain software Products which are available online at: www.motorolasolutions.com/legal-flow-downs. Customer will comply, and ensure its Authorized Users comply, with all such additional license terms. Applicable terms are provided in Section 9 of the Software Products Addendum. 5.3. WatchGuard Detector Mobile. Any order by Customer of WatchGuard Detector Mobile is on a subscription basis and subject to the SSA. 5.4. Vigilant Access. Customer may opt for subscription to additional Subscription Software, including use of the Law Enforcement Archival Network ("LEARN"), which is subject to the SSA and any additional terms governing the use of LEARN. If Customer purchases a subscription to commercial license plate recognition data, then Customer will execute and agree to the terms of Motorola's standard Data License Addendum. 5.5. License Plate Recognition Data. License plate recognition ("LPR") data collected by Customer is considered Customer Data (as defined in the MCA) and is therefore subject to the Customer's own retention policy. Customer, at its option, may share its LPR data with other similarly situated Law Enforcement Agencies ("LEAs") which contract with Motorola to access 55 May 10, 2022 Item #11 Page 364 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 LEARN by selecting this option within LEARN. Other similarly situated LEAs may similarly opt to share their LPR data with Customer using LEARN. Such LPR data generated by other LEAs is considered Third-Party Data (as defined in the MCA), is governed by the retention policy of the respective LEA, and shall be used by Customer only in connection with its use of LEARN. LPR data that has reached its expiration date will be deleted from LEARN. Only individuals who are agents and/or sworn officers of Customer and who are authorized by Customer to access LEARN on behalf of Customer through login credentials provided by Customer ("User Eligibility Requirements") may access LEARN. Vigilant in its sole discretion may deny access to LEARN to any individual based on such person's failure to meet the User Eligibility Requirements. Customer will ensure no user logins are provided to agents or officers of other local, state, or Federal LEAs without the express written con~ent of Vigilant. Customer will be responsible for all individuals' access to, and use of, LEARN through use of Customer login credentials, including ensuring their compliance with this Agreement. 5.6. API Support. Motorola will use commercially reasonable efforts to maintain its Application Programming Interface ("API") sold in connection with any Mobile Video System. APls will evolve and mature over time, requiring changes and updates. Motorola will use reasonable efforts to continue supporting any version of an API for six (6) months after such version is introduced, but if Motorola determines, in its sole discretion, to discontinue support of an API for any reason, Motorola will provide reasonable advance notification to Customer. If an API presents a security risk, Motorola may discontinue an API without prior notice. 5.7. Support of Downloaded Clients. If Customer purchases any software Product that requires a client installed locally on Customer-Provided Equipment or Equipment in possession of Customer, Customer will be responsible for downloading and installing the current version of such client, as it may be updated from time to time. Motorola will use reasonable efforts to continue supporting any version of a client for forty-five (45) days following the general availability of a new version release. Motorola may update the current version of its client at any time, including for security vulnerabilities, bug fixes, product improvements, and feature updates, and Motorola makes no representations or warranties that any software Product will support prior versions of a client. 5.8. CJIS Security Policy. Motorola agrees to support Customer's obligation to comply with the Federal Bureau of Investigation Criminal Justice Information Services ("CJIS") Security Policy and will comply with the terms of the CJIS Security Addendum for the term of the Addendum or Ordering Document for the applicable Product. Customer hereby consents to Motorola screened personnel serving as the "escort" within the meaning of CJIS Security Policy for unscreened Motorola personnel that require access to unencrypted Criminal Justice Information for purposes of Product support and development. 6. VaaS Program Terms. All hardware provided by Motorola to Customer under the VaaS Program will be considered "Equipment", as defined in the EPSLA, and constitutes a purchase of such Equipment subject to the terms of the EPSLA. Additionally, the following terms and conditions apply to any Equipment purchased under the VaaS Program: 6.1. Technology Refresh. All body cameras and associated batteries purchased under the VaaS Program ("Body Cameras") are eligible for a one-time replacement at no additional cost to the Customer beginning on the date three (3) years following the date of delivery of the initial Body Cameras and associated batteries provided under the VaaS Program. In order to receive any replacement Body Camera applicable under this Section 6.1 -Technology Refresh, Customer must return the existing Body Camera to Motorola in working condition. The corresponding replacement Body Camera will be the then-current model of the Body Camera at the same tier as the Body Camera that is returned to Motorola. For clarity, any other Equipment 56 May 10, 2022 Item #11 Page 365 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AFS received by Customer as part of the VaaS Program, other than Body Cameras, will not be eligible for a technology refresh hereunder. 6.2. No-Fault Warranty. Subject to the disclaimers set forth in the MCA and EPSLA, upon delivery of any Equipment purchased as part of the VaaS Program, Motorola will provide a No- fault Warranty to Customer for such Equipment that extends until the end of the Commitment Term (as defined below) applicable to such Equipment; except that the No-fault Warranty will not apply to: (i) any Equipment with intentionally altered or removed serial numbers, (ii) any other damages disclaimed under the MCA or EPSLA, or (iii) any Equipment that Motorola determines was changed, modified, or repaired by Customer or any third party. The "No-fault Warranty" means that Motorola will repair or replace any Equipment components or parts that render the applicable Equipment unable to perform its intended purpose. With respect to any batteries in Body Cameras, a battery will be considered faulty and covered under this No-fault _Warranty if it falls below sixty percent (60%) of rated capacity. 6.3. Commitment Term. Customer accepts that following the delivery of any Equipment under the VaaS Program, Customer commits to a five (5) year subscription term for such Equipment at the rate provided in the Ordering Document (the "Initial Commitment Term"). If Customer, for any reason, terminates any of its obligations to Motorola prior to expiration of the applicable Commitment Term (as defined below), Customer will be subject to the payments described in Section 6.7.2 -Termination hereunder. 6.4. Additional Devices. Any additional Equipment, including any accessory items, ordered by Customer after Customer's initial purchase of Equipment hereunder may be subject to an incremental increase in Fees. In the event Customer orders additional Equipment under the VaaS Program within the ninety (90) days immediately following its initial purchase, such Equipment will be included in and subject to the Initial Commitment Term . Any additional Equipment purchased under the VaaS Program subsequent to such ninety (90) day period, will commence an additional subscription term commitment for such Equipment of five (5) years (a "Subsequent Commitment Term") with respect to the monthly Fee associated with such additional Equipment. For purposes of this Addendum, the Initial Commitment Term and each Subsequent Commitment Term are each also referred to herein as a "Commitment Term". 6.5. Included Subscription Software. 6.5.1. Evidencelibrary.com. Subject to Section 6.7.1 -VaaS Term, the VaaS Program provides Customer with a subscription to the Cloud Hosted Evidence Management System specified in the Ordering Document during the VaaS Term (as defined below), the use of which is subject to the SSA. Customer's subscription will include unlimited users, Unlimited Storage and unlimited sharing, provided any media or data uploaded to the Cloud Hosted Evidence Management System is done so using Motorola Equipment actively enrolled in the VaaS Program. Following expiration of the applicable Commitment Term, if Customer desires to continue use of expired Equipment with the Cloud Hosted Evidence Management System, Customer must purchase additional access to Cloud Hosted Evidence Management System based on Motorola's prevailing rates, or Motorola _may disconnect connectivity of any expired Equipment to the Cloud Hosted Evidence Management System. 6.5.2. CommandCentral. For each Body Camera, in-car system or integrated system purchased, Customer will receive one user license for Motorola CommandCentral, which provides access to CC Community, CC Capture, CC Vault and CC Records. 57 May 10, 2022 Item #11 Page 366 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9O59AF5 If the Customer requires additional licenses to CommandCentral they must be purchased for an additional fee. 6.5.3. CarDetector Mobile. If Customer's VaaS Program order includes an in-car system, Customer will receive a subscription to WatchGuard CarDetector Mobile during the VaaS Term, the use of which is subject to the SSA. 6.6. VaaS Program Payment. Unless otherwise provided in an Ordering Document (and notwithstanding the provisions of the MCA), Customer will prepay a subscription Fee quarterly (each a "Subscription Quarter"), as set forth in an Ordering Document. If Customer orders any additional Product(s) under the VaaS Program subsequent to the initial purchase by Customer, Fees for such additional Product will be added to the quarterly subscription Fee, and will be payable on the same Fee payment schedule as the initial Product purchased under the VaaS Program; provided, however, that for the first Subscription Quarter during which such additional Product is purchased, the subscription Fee for the applicable additional Product will be pro-rated based on the applicable number of days remaining in the such initial Subscription Quarter. 6.7. VaaS Program Term and Termination. 6.7.1. VaaS Term. Customer's participation in the VaaS Program will commence upon the System Completion Date under this MVA, and will continue through the end of the final Commitment Term he_reunder ("the "VaaS Term"). Following the end of any Commitment Term, Customer's access to the Cloud Hosted Evidence Management System with respect to the Equipment purchased relative to that Commitment Term will expire, and Customer must download or transfer all Customer Data associated with the applicable Equipment within thirty (30) days following expiration unless Customer purchases extended access to the Cloud Hosted Evidence Management System from Motorola at the prevailing rates. Motorola has no obligation to retain Customer Data for expired Equipment beyond thirty (30) days following expiration of the applicable Commitment Term. For example, if Customer purchases 100 devices on January 1 of Year 1 of the VaaS Term, and then 100 additional devices on January 1 of Year 3, on December 31 of Year 5 (i.e., the conclusion of the Initial Commitment Term), Customer's access to the Cloud Hosted Evidence Management System with respect to the first 100 devices will be discontinued, and Customer must purchase extended storage or transfer all Customer Data associated with the first 100 devices within thirty (30) days of expiration of the Initial Commitment Term. In the foregoing example, the Cloud Hosted Evidence Management System access and data storage for the second 100 devices purchase will extend until December 31 of Year 7. 6.7.2. Termination. The termination provisions applicable to the VaaS Program will be those set forth in the MCA, EPSLA and SSA, as applicable. If Customer's participation in the VaaS Program is terminated for any reason prior to the end of the Initial Commitment Term or any Subsequent Commitment Term , Customer will pay the pro-rated remainder of the aggregate Equipment MSRP price (prevailing as of the time of delivery), calculated by multiplying the MSRP price of all Equipment purchased under the VaaS Program by the percentage resulting from dividing the number of months remaining in the Commitment Term applicable to such Equipment by sixty (60). In the event Customer purchased Equipment on multiple dates, resulting in separate Commitment Terms for certain Equipment, the preceding calculation will be made relative to the applicable Commitment Term for each Equipment order. For example, if Customer purchased $1 ,000 worth of Equipment on January 1 of Year 1 of the VaaS Term, and then $1,000 worth of 58 May 10, 2022 Item #11 Page 367 of 604 DocuSign Envelope ID: AB2013B4-94BF-4B0C-B860-74DCD9D59AF5 Equipment on January 1 of Year 2, and then Customer's VaaS Program terminates on December 31 of Year 3, Customer will be required to repay: $1,000 x (24/60) + $1,000 x (36/60), which is equal to $1,000 in the aggregate. 7. System Completion. Any Mobile Video System sold hereunder will be deemed completed upon Customer's (or the applicable Authorized User's) Beneficial Use of the applicable Mobile Video System (the "System Completion Date"). Customer will not unreasonably delay Beneficial Use, and in any event, the Parties agree that Beneficial Use will be deemed to have occurred thirty (30) days after functional demonstration. As used in this Section, "Beneficial Use" means use by Customer or at least one (1) Authorized User of the material features and functionalities of Mobile Video System, in material conformance with Product descriptions in the applicable Ordering Document. Any additional Equipment sold in connection with the initial Mobile Video System shall be deemed delivered in accordance of the terms of the EPSLA. Any additional Subscription Software purchased under the VaaS Program will be deemed delivered upon Customer's receipt of credentials required for access to the Cloud Hosted Evidence Management System or upon Motorola otherwise providing access to the Cloud Hosted Evidence Management System. This Section applies to Products purchased under the MVA notwithstanding the delivery provisions of the Addendum applicable to such Products, such as the SSA or EPSLA, and this Section will control over such other delivery provisions to the extent of a conflict. 8. Additional Cloud Terms. The terms set forth in this Section 8 -Additional Cloud Terms apply in the event Customer purchases any cloud hosted software Products under this MVA, including a Cloud Hosted Evidence Management System. 8.1. Data Storage. Motorola will determine, in its sole discretion, the location of the stored content for cloud hosted software Products. All data, replications, and backups will be stored at a location in the United States for Customers in the United States. 8.2. Data Retrieval. Cloud hosted software Products will leverage different types of storage to optimize software, as determined in Motorola's sole discretion. For multimedia data, such as videos, pictures, audio files, Motorola will, in its sole discretion, determine the type of storage medium used to store the content. The type of storage and medium selected by Motorola will determine the data retrieval speed. Access to content in archival storage may take up to twenty- four (24) hours to be viewable. 8.3. Availability. Motorola will make reasonable efforts to provide monthly availability of 99.9% for cloud hosted software Products with the exception of maintenance windows. There are many factors beyond Motorola's control that may impact Motorola's ability to achieve this goal. 8.4. Maintenance. Scheduled maintenance of cloud hosted software Products will be performed periodically. Motorola will make commercially reasonable efforts to notify customers one (1) week in advance of any such maintenance. Unscheduled and emergency maintenance may be required from time to time. Motorola will make commercially reasonable efforts to notify customers of any unscheduled or emergency maintenance twenty-four (24) hours in advance. 9. Survival. The following provisions will survive the expiration or termination of this MVA for any reason: Section 1 -Addendum; 2 -Evidence Management Systems; Applicable Terms and Conditions; Section 3 -Payment; Section 5.2 -Applicable End User Terms; Section 6.5.1 -Evidencelibrary.com; Section 6.7 -VaaS Program Term and Termination; Section 9 -Survival. 59 James t mears (Feb 20, 2021 06:01 EST) SOP E-75 DELEGATION OF AUTHORITY I, Jim Mears, Senior Vice President of Motorola Solutions, Inc. (“Company”), North America Government Sales ("Division") do hereby delegate my authority to approve and execute in the name of and on behalf of the Company and Motorola Solutions Canada Inc. (“MSCI”) contract documents (pursuant to Company policy), to the below named and titled individuals with the following dollar and other limitations as specified and explicitly set out below. Delegation to approve and execute the following Contract documents: Customer purchase and sale contracts, contract modifications, bids, proposals, bidder list applications, certifications, software licenses, non-disclosure agreements relating to customer sales opportunities, teaming agreements relating to customer sales opportunities, lobbyist agreements, subcontractor documents and other contract documents related to North America direct government sales on behalf of the Company or Motorola Solutions Canada Inc. Region: To: Value: North America Micah Applewhite $10,000,000 Territory Vice President (TVP) for T8 This Delegation of Authority granted herein shall not be delegable or assignable to any other person and shall expire on February 14, 2023. The authority delegated to the above-named individuals is in addition to the authority such individuals may have to approve and execute contract documents as an officer of the Company. This Delegation can be revoked by me at any time and will automatically expire for any named and titled individual if he or she ceases to be an employee of the Company or if he or she is assigned a different position within the Company. If a named individual is assigned a different position within the Company, the named successor is automatically given the designated authority unless a letter is provided stating otherwise. IN WITNESS WHEREOF, I have executed this delegation of authority as of February 15, 2022. Jim Mears Senior Vice President, North America Government Sales Motorola Solutions, Inc. May 10, 2022 Item #11 Page 368 of 604 CERTIFICATE OF ASSISTANT SECRETARY MOTOROLA SOLUTIONS, INC. The undersigned certifies that he or she is a duly appointed Assistant Secretary of Motorola Solutions, Inc. (the “Company”), a corporation duly organized and existing under the laws of the State of Delaware, and that, as such, he or she is authorized to execute this Certificate on behalf of the Company, and further certifies that: 1.At a meeting of the Board of Directors of the Company held on May 18, 2021 at which a quorum waspresent and acting throughout, the following resolutions were duly adopted, effective May 18, 2021, have not beenamended, and are in full force and effect on the date hereof: RESOLVED, that all Senior Vice Presidents be, and each one of them is, authorized to sign and execute all agreements, contracts, bids, proposals, deeds, assignments, powers of attorney, performance guarantees, performance guarantee undertakings, instruments, documents, claims, including claims against the United States, and certifications of such claims, in the ordinary course of business of the Company and related to his or her work as a Senior Vice President of one of the Company’s businesses, groups or corporate departments, all of which are collectively referred to as “Documents”, provided that this authority does not extend to: a.Documents having a value in excess of $50 million in the aggregate over the term of thearrangement; or b.Documents related to: (i) acquisitions, divestures, joint ventures and equity investments, (ii)outsourcing arrangements, (iii) customer financing extending more than 364 days, (iv) capitalexpenditures, (v) lease commitments, (vi) agreements and compensatory arrangements applicable to Motorola Solutions Appointed Vice Presidents and above, (vii) litigation and legal claims, (viii) appointing agents and attorneys-in-fact to represent the Company before any customs agency, (ix)financial guarantees, financial surety agreements and financial guarantee undertakings, (x) openingbank accounts, (xi) establishing borrowing relationships on behalf of the Company, and (xii) voting or otherwise dealing with securities owned by the Company. Authority for such Documents is found in the specific resolutions below. RESOLVED, that the Board has adopted specific resolutions authorizing the signing and execution by Senior Vice Presidents of Documents related to procurement arrangements. Authority for such Documents is found in the specific resolutions below. The officers named above are authorized to delegate this signature authority in writing to others. 2.The following person is a duly qualified and acting officer of the Company and has been duly elected to theoffice set forth opposite his or her name: Name Title Jim Mears Senior Vice President IN WITNESS WHEREOF, I have executed this Certificate as of this 10th day of March, 2022. _________________________________ Nick Frattini Assistant Secretary May 10, 2022 Item #11 Page 369 of 604 Motorola Solutions, Inc. 500 W. Monroe, Floors 37-44 Chicago, Illinois 60661 Effective: January 18, 2022 Executive Committee Gregory Q. Brown Chairman and Chief Executive Officer Jason J. Winkler Executive Vice President and Chief Financial Officer Mark S. Hacker Executive Vice President, General Counsel & Chief Administrative Officer John P. Molloy Executive Vice President and Chief Operating Officer Rajan S. Naik Senior Vice President, Strategy & Ventures Daniel G. Pekofske Corporate Vice President and Chief Accounting Officer Mahesh Saptharishi Executive Vice President & Chief Technology Officer Cynthia Yazdi Senior Vice President, Chief of Staff, Communications & Brand and Motorola Solutions Foundation Board of Directors Gregory Q. Brown Kenneth D. Denman Egon P. Durban Ayanna M. Howard Clayton M. Jones Judy C. Lewent Gregory K. Mondre Joseph M. Tucci May 10, 2022 Item #11 Page 370 of 604 G MOTOROLA SOLUTIONS Attachment B May 10, 2022 Item #11 Page 371 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 • MOTOROLA SOLUTIONS CITY OF CARLSBAD, CA EXHIBIT A: CONTRACT DOCUMENTATION REQUIREMENTS FEBRUARY 16, 2022 RFP No. 20-13 MOTOROIA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners. © 2021 Motorola Solutions, Inc. All rights reserved. May 10, 2022 Item #11 Page 372 of 604 DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 TABLE OF CONTENTS Section 1 ................................................................................................................ 1 Services Solution Description ................................................................................ 1 1.1 Services Solution Description Introduction ................................................................................ 1 1.2 Complete Solution Overview ..................................................................................................... 1 1.3 Benefits of a Cloud-Based Solution .......................................................................................... 2 1.3.1 Command Center Software Suite .......................................................................................... 2 1.4 CAD Overview ........................................................................................................................... 4 1.4.1 Subscription and Licensing ................................................................................................... 4 1.4.2 PremierOne Cloud CAD Capabilities .................................................................................... 4 1.5 PremierOne Cloud CAD Interface Strategy .............................................................................. 7 1.6 PremierOne Mobile Solution Description .................................................................................. 7 1.6.1 Overview ............................................................................................................................... 7 1.6.2 Subscription and Licensing ................................................................................................... 8 1.6.3 PremierOne Mobile Capabilities ............................................................................................ 8 1.6.4 Features Supported by Platform ........................................................................................... 9 1 . 7 PremierOne Cloud Reporting .................................................................................................. 10 1. 7.1 CommandCentral Reporting ............................................................................................... 10 1.7.2 Microsoft Reporting Services .............................................................................................. 10 1.8 PremierOne Interface -Legacy Data Query ........................................................................... 11 1.9 PremierOne Cloud Integration -ASTRO Radio Push-to-Talk (PTT) ...................................... 11 1.10 PremierOne Cloud Integration -Vigilant... .............................................................................. 11 1.11 PremierOne Cloud Integration -VEST A ................................................................................. 11 1.12 CommandCentral Aware Solution Description ........................................................................ 12 1.12.1 CommandCentral Overview ............................................................................................ 12 1.12.2 1.12.3 CommandCentral Aware Features and Integrations ....................................................... 12 Aware Design Limitations ................................................................................................ 17 1.13 CommandCentral Analytics Plus ............................................................................................. 17 1.14 CJIS and Compliance ............................................................................................................. 18 1.15 Optionally Available for Purchase ........................................................................................... 18 1.15.1 4RE In-Car Video as a Service ....................................................................................... 19 1.15.2 M500 In-Car Video as a Service ..................................................................................... 19 1.15.2.1 CommandCentral Evidence ........................................................................................ 20 1.15.2.2 CommandCentral Community ..................................................................................... 20 1.15.3 Motorola V300 Body Worn Cameras Video-As-A Service Offer ..................................... 21 City of Carlsbad, CA Exhibit A: Contract Documentation Requirements fl Motorola Solutions February 16, 2022 Use or disclosure of this proposal is subject to the restrictions on the cover page. Table of Contents i May 10, 2022 Item #11 Page 373 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 Section 2 .............................................................................................................. 22 Statement of Work ............................................................................................... 22 2.1 Statement of Work Overview .................................................................................................. 22 2.1 .1 Award, Administration and Project Initiation ........................................................................ 22 2. 1.2 Project Management Definitions ......................................................................... i ............... 22 2. 1. 3 General Customer Responsibilities ..................................................................................... 23 2.2 Project Roles and Responsibilities .......................................................................................... 23 2.2.1 Motorola Project Roles and Responsibilities Overview ....................................................... 23 2.2.2 Customer Roles and Responsibilities .................................................................................. 26 2.3 Project Initiation and Planning ................................................................................................. 28 2.3.1 Project Planning Session -Teleconference/Web Meeting .................................................. 29 2.3.2 Project Kickoff Session -Teleconference/Web Meeting ..................................................... 31 2.3.3 GIS Planning Session -Teleconference/Web Meeting ....................................................... 31 2.3.4 Interface Planning Session -Teleconference/Web Meeting ............................................... 32 2.3.5 Connectivity Planning Session -Teleconference/Web Meeting .......................................... 33 2.3.6 CommandCentral Aware -Video Management System (VMS) Design Review ................. 34 2.4 PremierOne Cloud Services Project Execution ....................................................................... 34 2.4.1 PremierOne Cloud Hardware and Environment ................... -............................................... 35 2.4.2 PremierOne Cloud Business Process Review (BPR) ........................................................ .40 2.4.3 PremierOne GIS ................................................................................................................. .41 2.4.4 Provisioning ......................................................................................................................... 44 2.4.5 CAD Client Installation ........................................................................................................ 48 2.4.6 Functional Validation ........................................................................................................... 49 2.5 PremierOne Cloud Reporting .................................................................................................. 51 2.6 Interface and Integration Delivery ........................................................................................... 52 2. 7 Interface Deployment .............................................................................................................. 52 2.7.1 Interface Validation ............................................................................................................. 53 2.8 PremierOne Cloud and CommandCentral Training and Consultative Services ...................... 54 2.8.1 Training ............................................................................................................................... 54 2.8.2 CommandCentral Aware Professional Consulting Services ............................................... 54 2.8.3 CommandCentral Investigate Professional Consulting Services ........................................ 55 2.9 PremierOne Cloud and CommandCentral Go Live ................................................................. 56 2.9.1 PremierOne Cloud Go Live Planning .................................................................................. 56 2.9.2 Motorola Support Engagement ........................................................................................... 57 2.9.3 CommandCentral Aware Production Use ........................................................................... 57 2.9.4 CommandCentral Investigate Production Use .................................................................... 57 2.9.5 PremierOne Cloud Go Live Event ....................................................................................... 58 2.10 Project Closure ........................................................................................................................ 58 2.10.1 Transition to Support ....................................................................................................... 59 2.11 Options Available at an Additional Price ................................................................................. 59 2.11.1 Option 1 -Motorola In-Car Cameras (Either 4RE or M500) ............................................ 59 2.11.2 CommandCentral Community ......................................................................................... 59 February 16, 2022 Use or disclosure of this proposal is subject to the restrictions on the cover page. ii Table of Contents City of Carlsbad. CA Exhibit A: Contract Documentation Requirements Motorola Solutions G May 10, 2022 Item #11 Page 374 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.11 .3 Option 2 -Motorola V300 Body Worn Cameras ............................................................. 60 2.12 Appendix A-PremierOne Cloud Attachment.. ........................................................................ 61 2.12.1 Common Services ........................................................................................................... 61 2.12.2 CommandCentral Reporting for PremierOne Cloud ........................................................ 61 2.12.3 Geographic Information System (GIS) Integration .......................................................... 61 2.12.4 PremierOne Cloud File Build ........................................................................................... 62 Section 3 .............................................................................................................. 65 Cost Summ~ry ..................................................................................................... 65 3.1 Pricing Summary ..................................................................................................................... 65 Section 4 .............................................................................................................. 67 Payment Schedule ............................................................................................... 67 Section 5 .............................................................................................................. 68 Project Schedule and Personnel ......................................................................... 68 5.1 Project Schedule ..................................................................................................................... 68 5.2 Project Personnel .................................................................................................................... 69 Section 6 .............................................................................................................. 7 4 Product Validation ................................................................................................ 7 4 6.1 Product Validation Purpose ..................................................................................................... 74 6.2 Verification Process Overview ................... : ............................................................................ 74 6.3 Validation Process Activities ................................................................................................... 74 6.3.1 Prepare Functional Validation Plan ..................................................................................... 7 4 6.3.2 Prepare Interface Validation Plan ........................................................................................ 75 6.3.3 Validation Plan Approval ..................................................................................................... 75 6.3.4 Validation Execution ............................................................................................................ 75 6.3.5 Validation Failures ............................................................................................................... 75 6.4 Sample Functional Validation Workbook ................................................................................ 76 Section 7 .............................................................................................................. 77 Hardware and Network Specifications ................................................................. 77 7.1 PremierOne Cloud Hardware and Environment.. .................................................................... 77 7.1.1 General Hardware and Environment Requirements ........................................................... 77 7.1.2 Component Specifications .................................................................................................. 78 7.1.3 Network and Other Environment Specifications .................................................................. 80 Section 8 .............................................................................................................. 83 Interface Control Documents ............................................................................... 83 8.1 PremierOne Cloud CAD Interface Functional Descriptions .................................................... 83 *Dependent on 3rd Party ability to write to PremierOne API ............................................................ 83 · 8.1.1 CAD Calls For Service Data Feed Interface Functional Description ................................... 83 City of Carlsbad. CA Exhibit A: Contract Documentation Requirements G Motorola Solutions February 16, 2022 Use or disclosure of this proposal is subject to the restrictions on the cover page. Table of Contents iii May 10, 2022 Item #11 Page 375 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 8.1.2 CAD Incident Create Interface Functional Description ........................................................ 85 8.1.3 State Query Interface Functional Description ...................................................................... 87 8.1.4 Third Party Query Interface Functional Description ............................................................ 89 8.2 Specific Technical Requirements: ........................................................................................... 90 Section 9 .............................................................................................................. 91 PremierOne Cloud Training Plan ......................................................................... 91 9.1 Overview ................................................................................................................................. 91 9.2 Customer Training Roles ........................................................................................................ 91 9.2.1 Customer Training Representative ..................................................................................... 91 9.2.2 Learning Management Administrator .................................................................................. 91 9.2.3 Customer Training Attendees ............................................................................................. 92 9.3 PremierOne Cloud Training Plan Scope ................................................................................. 92 9.3.1 PremierOne Cloud CAD ...................................................................................................... 92 9.3.2 PremierOne Mobile ............................................................................................................. 93 9.3.3 CommandCentral Aware ..................................................................................................... 93 9.3.4 CommandCentral Investigate End User .............................................................................. 93 9.3.5 OPTION -CommandCentral Community Digital Evidence Collection ................................ 93 9.3.6 OPTION -WatchGuard V300 Cameras ............................................................................. 93 9.4 PremierOne Cloud Training General Information .................................................................... 94 9.4.1 Training Courses ................................................................................................................. 94 9.4.2 Training Facilities and Schedules ........................................................................................ 94 9.4.3 Training Methods and Procedures ...................................................................................... 94 9.4.4 Training Environment .......................................................................................................... 95 9.4.5 Session Attendance ............................................................................................................ 95 9.4.6 Learning experience Portal (LXP) Requirements ................................................................ 96 9.4. 7 LMS Learner Subscription Package .................................................................................... 96 9.5 PremierOne Cloud Course Details .......................................................................................... 96 9.5.1 Training Course Classifications ........................................................................................... 96 9.5.2 Training Course Descriptions .............................................................................................. 98 Section 10 .......................................................................................................... 111 PremierOne Maintenance and Support Agreement.. ......................................... 111 Exhibit A -Customer Support Plan ............................................................................................... 117 10.1 Support Plan Summary ......................................................................................................... 119 10.1.1 Introduction -Serving Our Customer's Needs .............................................................. 119 10.1.2 Service Management Overview -PremierOne Cloud Services .................................... 119 10.2 Motorola Systems Support Center ........................................................................................ 120 10.2.1 Reporting Incidents Using the Toll-free Number ........................................................... 121 1.1 Severity Level and Response Definitions .............................................................................. 121 10.2.2 Severity Response Table .............................................................................................. 122 10.3 Customer Contacts for Notification ....................................................................................... 123 10.4 Case Management via MyView Portal .................................................................................. 123 February 16, 2022 Use or disclosure of this proposal is subject to the restrictions on the cover page. iv Table of Contents City of Carlsbad. CA Exhibit A: Contract Documentation Requirements Motorola Solutions G May 10, 2022 Item #11 Page 376 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 10.4.1 Ticket Initiation via Email ............................................................................................... 124 10.5 Customer Responsibilities for Support .................................................................................. 124 10.6 Motorola Responsibilities· ...................................................................................................... 126 10. 7 Security ................................................................................................................................. 127 10.8 Limitations and Exclusions .................................................................................................... 128 Exhibit B -Labor Rates ................................................................................................................ 129 Section 11 .......................................................................................................... 130 Functional Requirements Matrix ........................................................................ 130 Section 12 .......................................................................................................... 131 Additional Documentation Correspondence ...................................................... 131 City of Carlsbad, CA Exhibit A: Contract Documentation Requirements '4D Motorola Solutions February 16, 2022 Use or disclosure of this proposal is subject to the restrictions on the cover page. Table of Contents v May 10, 2022 Item #11 Page 377 of 604 DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 SECTION 1 City of Carlsbad, CA February 16, 2022 SERVICES SOLUTION DESCRIPTION 1.1 SERVICES SOLUTION DESCRIPTION INTRODUCTION Motorola has provided the City of Carlsbad an "all in" offer for sale. What we mean is that 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 PTT Interface and CommandCentral Analytics PlusCommand Central Community is available with purchase of Body Worn Cameras and is provided as an Option. Each of these represent a vital building block in your pursuit for a safer community through better outcomes driven by smart technology. Lastly, we also know you have other building blocks that need to be updated. One such block is to revamp first responder body worn cameras. To accommodate this, Motorola's architecture and offer includes a new, complete Body Worn Camera solution that will enhance efficiency across the single unified solution while creating positive outcomes for the City of Carlsbad. 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 Cloud CAD and PremierOne Cloud Mobile and CommandCentral Aware provide actionable intelligence to inform decisions, recognize trends, and gain mission critical insights to improve operations. With PremierOne Cloud and CommandCentral, your users will be able to reliably share information across dispatch, field, and crime center workflows to connect teams, increase situational awareness, and improve Exhibit A: Contract Documentation Requirements G Motorola Solutions Services Solution Description 1 May 10, 2022 Item #11 Page 378 of 604 DocuSign Envelope ID: EE0000EC-B19D--469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 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 Cloud 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 BENEFITS OF A CLOUD-BASED SOLUTION PremierOne Cloud CAD and Mobile offer an interconnected cloud solution with the following benefits for your agency: Fast Deployment, Easy Updates -PremierOne Cloud offers a faster transition and deployment process. This cloud-hosted solution makes it easier to adopt new features. Software updates are seamless, without disrupting mission critical performance. Secure and Flexible Solution -PremierOne Cloud combats cybersecurity threats with advanced intelligence from deeper analytics, real-time updates, and security patching. Redundant and geographically isolated data centers, plus resilient network infrastructure, ensure the continuity of mission critical operations in the cloud. The cloud-based nature of PremierOne Cloud allows for more flexibility to keep your public safety operations moving despite a variety of obstacles, with the proven reliability of Motorola Solutions' platforms. Future Ready -PremierOne Cloud is a platform that will evolve alongside your agency. As staffing and operational needs change, the subscription-based named user pricing model allows for seamless adjustment based on specific needs or large-scale emergencies. 1.3.1 Command Center Software Suite • PremierOne CAD with Automatic Resource Location (ARL) -PremierOne Integrations • VESTA 9-1-1/TDD • Vigilant ALPR • ASTRO APX Radio Push-To-Talk -PremierOne CAD Interfaces • NetRMS Calls For Service • NetRMS Query • SPIDR Tech • Axon • DORS • CLETS/NCIC • Crossroads Accidents • Crossroads Citations • DORS Query Exhibit A: Contract Documentation Requirements 2 SeNices Solution Description Motorola Solutions G May 10, 2022 Item #11 Page 379 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 • LaserFische Query • QueTel Query • Legacy Query • PremierOne Mobile (Windows, iOS, Android) with Mobile Mapping • CommandCentral Aware -Real Time Crime Center -Agency Esri Data Sets Integration -AccuWeather Service -CommandCentral Aware Connectors: • PremierOne CAD Integration for incident and unit location • Avigilon Video ACC Video Analytics Integration • Vigilant License Plate Recognition Integration • VESTA 9-1-1 Call Location Integration • ASTRO P25 Radio Location on Push-To-Talk (PTT) • ONSSI VMS • Drone Interface (TBD) • OW Spectrum Traffic Cameras • CommandCentral Reporting • CommandCentral Analytics Plus Components Optionally Available for Purchase • Motorola 4RE or M500 In-Car Video-as-a-Service (VaaS) • Motorola V300 Body Worn Cameras Video-as-A-Service (VaaS) City of Carlsbacl, CA February 16, 2022 • CommandCentral Community (included with purchase of In-Car or Body Worn Cameras VaaS) Figure 1-1: PremierOne Cloud Suite System Diagram The following solution descriptions outline the unique benefits of PremierOne Cloud CAD and Mobile to empower your users with a proven public safety platform. Exhibit A: Contract Documentation Requirements C., Motorola Solutions SeNices Solution Description 3 May 10, 2022 Item #11 Page 380 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 1.4 CAD OVERVIEW Motorola Solutions' PremierOne Cloud Computer-Aided Dispatch (CAD) is an easy-to-use cloud 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 Cloud CAD enables personnel to quickly access incoming calls, related records, and responder location and status. The PremierOne Cloud 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. As a cloud-based solution, PremierOne Cloud CAD offers a faster deployment process than on-premises solutions, as well as higher availability that easily scales should your dispatch operations grow. As upgrades for PremierOne Cloud CAD are released, your personnel can adopt new features and capabilities to ensure that your operations are as efficient and capable as possible. The cloud-based architecture also offloads updates, maintenance, and repair tasks to Motorola Solutions, so that your personnel can remain focused on their mission critical operations. 1.4.1 Subscription and Licensing 1.4.2 1.4.2.1 PremierOne Cloud CAD is proposed as a subscription. As part of this subscription, Motorola Solutions will provide access to the PremierOne client application for named users (any individual that needs a unique log-on user ID and password to access the service). This PremierOne Cloud CAD solution has been sized to include up to 500,000 CAD Calls for Service per year. Please refer to the pricing section for the specific amount of named users and licenses being proposed. The number of physical CAD workstations as listed in the pricing section cannot be exceeded. PremierOne Cloud CAD Capabilities PremierOne Cloud CAD delivers a streamlined experience to improve dispatch, unit, and incident management. PremierOne Cloud CAD Access and Basic Operation PremierOne Cloud CAD can be installed on any computer that meets the minimum functional requirements for operation. Once the client application is installed, personnel can access it via a web browser and operate it as a virtual application. The PremierOne Cloud CAD interface consists of a set of status monitors that delivers information to dispatchers and other personnel. This interface is configurable to meet your personnel's specific needs. Most commands and other operations within the application can be completed either with a mouse or keyboard, although there are several functions, such as selecting units on a map, which require a mouse. Exhibit A: Contract Documentation Requirements 4 Services Solution Description Motorola Solutions G May 10, 2022 Item #11 Page 381 of 604 DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 1.4.2.2 Incident and Unit Management City of Carlsbad, CA February 16, 2022 PremierOne Cloud 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 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 Cloud 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 Cloud 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 Cloud 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 Cloud 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 Cloud CAD informs users that they are to manually notify individuals who are . not a part of PremierOne Cloud CAD, and helps to prevent multiple notification recipients from contacting an individual simultaneously. Exhibit A: Contract Documentation Requirements ti Motorola Solutions Services Solution Description 5 May 10, 2022 Item #11 Page 382 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 1.4.2.3 1.4.2.4 Incident Mapping and Automatic Resource Location In addition to the information described above, dispatchers can view incident and resource location data directly within PremierOne Cloud CAD via a consolidated, Esri standard GIS map. This centralized map display is integrated directly into PremierOne Cloud CAD, providing geographic context to real-time incident information. Specific mapping functions built into PremierOne Cloud CAD allow dispatchers to manipulate the map and configure the display with icons to help target incident response. Also, PremierOne Cloud CAD uses Automatic Resource Location (ARL) to determine the actual location of emergency vehicles in relation to an emerging incident. This enables PremierOne Cloud 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 Cloud CAD's ARL capability tracks those resources as they are on route to an incident. Mail and Messaging Services PremierOne Cloud CAD's mail and user-to-user messaging functionalities allow users to exchange and distribute email and instant messages (IM) within the di~patch center and to units equipped with Mobile Data Terminals (MDT). PremierOne Cloud 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 Cloud CAD address book to find contacts. PremierOne Cloud CAD includes a global address book and the ability to create both shared address books and user-specific personal address books. 1.4.2.5 System Security and Roles PremierOne Cloud CAD is hosted in the Microsoft Azure Government Cloud environment to ensure operational and data security. Each user and device on the system is assigned to one or more agency-created roles. PremierOne Cloud 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 Cloud 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. Exhibit A: Contract Documentation Requirements 6 Services Solution Description Motorola Solutions G May 10, 2022 Item #11 Page 383 of 604 DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 • Reports. City of Carlsbad, CA February 16, 2022 1.5 PREMIERONE CLOUD CAD INTERFACE STRATEGY PremierOne Cloud CAD supports a variety of interfaces to enhance dispatch operations by integrating PremierOne Cloud CAD with the capabilities provided by other solutions. Motorola Solutions provides a bundle of interfaces which are licensed as part of the PremierOne Cloud solution. Interface Feature Descriptions (IFD) are provided below, Non- standard interfaces will be assessed by the interface development team as part of the final purchase proposal creation. Some interfaces may not be supported or may require additional development work which will be identified in the final proposal. 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-1: List of Integrations, Interfaces, and Queries Customer known as Function NetRMS Outbound Calls For Service Records Data Feed Spidr Tech Outbound Calls For Service Records Data Feed Axon Outbound Calls For Service Records Data Feed DORS Inbound CAD Incident Create CLETS/NCIC Query State Query Crossroads Accident Query Query Third Party System Crossroads Citation Query Query Third Party System DORS Query Query Third Party System LaserFiche Query Query Third Party System QueTel Query Query Third Party System Legacy Query (Purchase Option Query Third Party System included in base) CAD Incident Data Feed Outbound Calls For Service Records Data Feed 1.6 PREMIERONE MOBILE SOLUTION DESCRIPTION 1.6.1 Overview Motorola Solutions' PremierOne Mobile extends command center capabilities and information from PremierOne Cloud CAD by providing enhanced mobile capabilities to Exhibit A: Contract Documentation Requirements CD Motorola Solutions Services Solution Description 7 May 10, 2022 Item #11 Page 384 of 604 DocuSign Envelope ID: EE000OEC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 1.6.2 1.6.3 officers and first responders in the field. Public safety personnel can prepare for an incident by using the PremierOne Mobile application to access real-time information in their vehicle or on their smart device. This mobile access to critical intelligence and cloud-based 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 application offers 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 more mobile device. Subscription and Licensing PremierOne Mobile is proposed as a subscription. As part of this subscription, 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 An.droid client simultaneously. Please refer to the pricing section for the specific amount of licenses and named users being proposed. 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" respondes, 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 upgrades to avoid interruption of critical tasks. PremierOne Mobile also supports single client to fleet-wide, multi-agency remote deployments and silent updates. Exhibit A: Contract Documentation Requirements 8 Services Solution Description Motorola Solutions G May 10, 2022 Item #11 Page 385 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 1.6.4 Features Supported by Platform City of Carlsbad, CA February 16, 2022 The PremierOne Mobile application supports the features outlined in the table below. Table 1-2: High-level PremierOne Mobile Features by Client Platform PremierOne Mobile -Available Windows Android iOS Clients Operating System Windows 10 Android 8.0+ iOS 11+ 8.1+ 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 & L TE 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 • Exhibit A: Contract Documentation Requirements f.' Motorola Solutions Services Solution Description 9 May 10, 2022 Item #11 Page 386 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 1.7 1.7.1 1.7.2 PREMIERONE CLOUD REPORTING CommandCentral Reporting CommandCentral Reporting offers a pre-defined Incident Detail Report which provides detailed data for a single incident: General Incident information, Location, and Caller information, Time Stamps, Assigned Units, Assigned Personnel, Comments, and Changes. Also included is an Incident Summary Report, which provides summary data for multiple incidents including: Incident Number, Create Date/Time, Duration, Type, Priority, Location, and Dispositions. Wli:16ttll Rtpon • SI.IMf'MIY ~ tortutl r-fl">'~.,._,.,.1..,n,lrff" ~,,.,._, ... ti S4f\76J 562.571 L • 2,103 156 1,947 lK.t101l_,l,rffl. C.11'.u ... J~"O.II• r:u111r..t,_ll1C'._"_ f I ■ . IIEE! , . ....,. Microsoft Reporting Services JM:id4'!1S~11tliPw1:' f•-:'tt/11.'!•~I,• :K,"'1 ~:~. f,)'rJa,,,..-,1 ce~l _._, -~ ,_,,,,._.,,.,._. ..i ,,.. .,.., ' _, .. .-, '""n• _ _,_,_,.,.,.. .. _ ·--........ -........ ,.,...~ .. ·· ............. ::1;1~ C,l::.:,;,e,t') "' I JIG:,..Jl! ..... -... ---.. ,... -' --.. ~ ,;ia_.. ci:i:x,--~t. -' u,,e,,,>-19,.,.,,, .. __ .. _ _,,,, J':ll~-::.'!.,.,:u•:111 ~~- "' o~~ !SW .:."w... CT,. -°ivtf.aa• ie:i'.p,Mlff Tl-~ el lnddcn°, TYPe ~-, ~4,"!-; 'dJ.:\.",'-\.-.! ':': I! v,N!l.:1:,; ,;,,J W 'N r,.:-.1t.,~~I -:,ai;:rw~•1} UUV-llo PremierOne uses Microsoft SQL Server 2019 Reporting Services (SSRS) for reporting purposes. SQL Server 2019 Reporting Services is a Cloud-hosted reporting platform that is used to create and manage tabular, matrix, graphical, dashboards, and free form reports that contain data from PremierOne Cloud CAD. The reports can be viewed and managed via a browser. Exhibit A: Contract Documentation Requirements 1 O Services Solution Description Motorola Solutions G May 10, 2022 Item #11 Page 387 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 1.8 PREMIERONE INTERFACE-LEGACY DATA QUERY City of Carlsbad, CA February 16, 2022 The Legacy Data Query interface details are provided in the Interface Functional Description section. 1.9 PREMIERONE CLOUD INTEGRATION-ASTRO RADIO PUSH- TO-TALK (PTT) The ASTRO APX Integration with PremierOne Cloud 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. 1.10 PREMIERONE CLOUD INTEGRATION -VIGILANT The Vigilant integration with PremierOne Cloud 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.11 PREMIERONE CLOUD 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 Cloud CAD. This integration enables Call Takers to have the essential data to initiate a call for service in the CAD System. When the 911 system receives the ANI/ALI data feed from the 3rd 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. VEST A 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 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 Exhibit A: Contract Documentation Requirements G Motorola Solutions Services Solution Description 11 May 10, 2022 Item #11 Page 388 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 -Conversion NPA-NPD error 1.12 COMMANDCENTRAL AWARE SOLUTION DESCRIPTION 1.12.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), Vigilant License Plate Recognition (LPR), the VMS for a Drone system which is to be determined, and the OW Spectrum traffic cameras. Users can communicate with confidence, knowing their information is hosted in the highly secure Microsoft Azure cloud. 1.12.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. Exhibit A: Contract Documentation Requirements 12 Services Solution Description Motorola Solutions G May 10, 2022 Item #11 Page 389 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Data sets help users to: City of Carlsbad, CA February 16, 2022 • Refine displayed data based on the geographic area defined per user. Data includes area, beat, sector, precinct, zone, or quadrant. • 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. Exhibit A: Contract Documentation Requirements G Motorola Solutions Services Solution Description 13 May 10, 2022 Item #11 Page 390 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 • 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. Avigilon Control Center (ACC) & Video Analytics Integration Capabilities Avigilon self-learning analytics, via Avigilon Control Center (ACC), extends the effectiveness of your security personnel by providing effective monitoring and enabling proactive, real- time response from your team. The Avigilon Control Center(ACC) rules engine enables you to selectively apply the analytics-based events as alarms and rule triggers, providing users with immediate notifications for suspicious activities into CommandCentral Aware making monitoring more affordable and efficient. The Avigilon to CommandCentral Aware connector integrates the results of the rules engine combined with video from the Avigilon VMS. The targeted video feed is displayed in response to user interaction and pre-defined scenarios based on a customizable rule set. Specific category of events such as CAD incidents, LPR alarms, or other alert reporting system(s) integrated into CommandCentral Aware solution can be configured, in relation to the analytics, to trigger display of video feeds automatically. These real-time events and forensic capabilities detect and notify scene changes, missing objects and rules violations. In addition to the live video and analytics, the connector supplies operators' video display tools that control pan, tilt, zoom (PTZ) cameras, and playback of recorded video. The following is a complete list of Avigilon Control Center (ACC) video analytics features for object detection and classification for live or forensic events that enhance the common operating picture and situational awareness capabilities of CommandCentral Aware. Table 1-3 -Avigilon Control Center Video Analytics Avigilon Analytics Rules Description Analytics (Objects are classified as Person or Vehicle) Rules for ACC Objects in Area The event is triggered when the selected object type moves into a specified region of interest. Object Loitering The event is triggered when the selected object type stays within a specified region of interest for an extended amount of time which is configured. Objects The event is triggered when an Object or a specified number of Crossing Beam Objects have crossed the directional beam that has been configured over the camera's field of view. The beam can be unidirectional or bidirectional. Object Appears The event is triggered by each object that enters the specified region of Enters Area of interest. Exhibit A: Contract Documentation Requirements 14 SeNices Solution Description Motorola Solutions 4' May 10, 2022 Item #11 Page 391 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Avigilon Analytics Rules for ACC Object Not Present in Area Objects Enter Area Objects Leave Area Object Stops In Area Direction violated Camera tampering License Plate Recognition Analytics Analytics Rules Description City of Carlsbad, CA February 16, 2022 (Objects are classified as Person or Vehicle) The event is triggered when no objects are present in the specified region of interest. The event is triggered when the specified number of objects have entered the specified region of interest. The event is triggered when the specified number of objects has left a specified region of interest region of interest. The event is triggered when an object in a specified region of interest stops moving for the specified threshold time. The event is triggered when an object moves in the prohibited direction of travel. The event is triggered due to sudden scene changes. New license plate recognition analytics engine with highly accurate license plate capture, identification, and search for fast event response. Use watch lists to create alerts and actions when a license plate match is detected. 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 (tbd 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 that is to be determined. Each VMS brings with it a variety of tools via an SOK. 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 Exhibit A: Contract Documentation Requirements f1' Motorola Solutions Services Solution Description 15 May 10, 2022 Item #11 Page 392 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 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 Importing cameras and the directory tree from VMS to CommandCentral Import Aware Camera Use coordinates stored in-camera custom fields at the NVR (or) pulls Location geo-location coordinates from the camera units. Specifically identified during installation. 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 Playback video from the archive. Video Live Perform a screen capture of the live scene to send as an attachment via Snapshots messaging service. Recorded Ability to isolate and capture a section of the recorded video to be Snapshots distributed by the messaging service. Recorded Display frame recorded sample at a faster rate playing forward. Fast Forward Record Fact Display frame recorded sample at a faster rate playing backward. 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. Exhibit A: Contract Documentation Requirements 16 Services Solution Description Motorola Solutions CD May 10, 2022 Item #11 Page 393 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 APX Radios Location on Push-to-Talk or Location-on-Receive (TDMA) CommandCentral Aware provides the location of users from GPS-enabled 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 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 in late 2021 or early 2022. This unique operation will enable agencies and departments to have their own, as well as regional access to participating first responder locations. 1.12.3 Aware Design Limitations 1.13 • 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. COMMANDCENTRAL ANALYTICS PLUS CommandCentral Analytics 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. Exhibit A: Contract Documentation Requirements G Motorola Solutions Services Solution Description 17 May 10, 2022 Item #11 Page 394 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 1.14 1.15 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 Analytics 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 • Flexible Analysis Project Creation • Advanced Link Analysis • CommandCentral Platform Integration CJIS AND COMPLIANCE For U.S.-based customers, the CommandCentral and PremierOne infrastructure runs in a CJIS compliant GovCloud. Motorola Solutions operates according to requirements dictated by the CJIS Security Policy document. Motorola Solutions performs periodic internal reviews to ensure the operation is in compliance for each of the thirteen policy areas established by the CJIS Security Policy. All Motorola Solutions employees with administrative access to the system must complete CJIS Security and Awareness training and complete a fingerprint-based background check. User activities are logged for auditing purposes. All Motorola Solutions CommandCentral and PremierOne Saas offerings are deployed in Microsoft Azure. These cloud service providers (CSPs) offer a secure infrastructure to build our applications. All Azure customers leverage a data center and network architecture that meets the requirements of the most security-sensitive organizations. When it comes to meeting compliance requirements, Azure provide their customers with an infrastructure which already complies with many assurance programs. Systems built on top of the cloud infrastructure of these CSPs will receive immediate benefit for compliance requirements that affect infrastructure, physical security, or other areas that CSP bears responsibility for. OPTIONALLY AVAILABLE FOR PURCHASE The City may select either the 4RE cameras or the M500 cameras for the entire quantity of cameras (60). Exhibit A: Contract Documentation Requirements 18 SeNices Solution Description Motorola Solutions ~ May 10, 2022 Item #11 Page 395 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 1.15.1 4RE In-Car Video as a Service City of Carlsbad, CA February 16, 2022 The 4RE is equipped with high-definition cameras with hands-free uploading capabilities, making the capture and upload of clear video evidence as easy as possible. The cameras record at 720p resolution and use a dual-exposure Ultra Wide Dynamic Range technology that dramatically improves the quality of video, especially in difficult lighting situations. This helps capture video evidence that is clear and easy to monitor. 4RE cameras are also equipped with patented Record-After-the-Fact® (RATF) technology, which allows users to go back in time and capture important evidence, even if the recording function was not activated and the incident happened days before. The 4RE system has a dual drive structure, with both an internal and removable USB drive for storage, and supports wireless upload. Wireless uploading capabilities via L TE networks eliminate the need for trips to and from stations to upload evidence. The 4RE's patented multiple resolution encoding allows officers to save footage of critical incidents in HD and routine occurrences in a lower resolution at the same time. This eliminates the compromise between video quality and file storage needs. Event tags can be configured to control which recordings are stored in high definition. The 4RE's built-in microphone captures audio during event recording. It can be mounted to fit any configuration. Intuitive Display and Interface 4RE offers an easy-to-navigate 4.3" LED control panel with function keys and a backlit touch screen with LED indicators that can be disabled for covert situations that need complete darkness. Users can also program various sensors to activate a new record event, including emergency lights, siren, auxiliary input, wireless microphone, vehicle speed, and crash detection. The 4RE Mobile Data Computer App is a simple interface that runs on Windows XP and Windows 10 and interfaces with the 4RE through an Ethernet connection. The app also works in conjunction with the control panel, allowing 4RE to have full functionality when the MDC is not functioning. 1.15.2 MS00 In-Car Video as a Service The M500 In-Car Video System is the first Al-enabled in-car video solution for law enforcement. It combines Motorola's powerful camera technology with our industry-leading digital evidence management software (OEMS), to improve the quality of evidence collected and streamline the data sharing process throughout investigation. Video Recording and Capture Equipped with high-definition, 1080p front and cabin cameras, the M500 creates a reliable record of evidence that can be uploaded to your Digital Evidence Management solution from any location with a cellular signal. Its artificial intelligence interface continuously monitors the cabin camera, detecting human faces as they enter the vehicle and automatically recording whenever anyone is detected in the back seat, eliminating the need to scroll through video of empty cabins to collect important evidence. And with patented Record-After-the-Fact (RATF) technology, the M500 ensures continuous recording from both front and cabin perspectives, whenever the camera is on -even if the recording function isn't manually Exhibit A: Contract Documentation Requirements G Motorola Solutions Services Solution Description 19 May 10, 2022 Item #11 Page 396 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 engaged. All RATF data is automatically uploaded to OEMS, for easy review and data capture whenever it is needed. License Plate Capture and Analysis The M500's artificial intelligence interface also uses VigilantPlate Search, a license plate recognition technology that reads license plates from up to 40 feet away. It allows users access to a database of over 33 billion detections, where searches for insights such as location, year, make, and model and associated vehicle analysis can be performed. This can allow surveying for license plates that could be associated with arrest warrants or stolen automobile reports. Display and User Interface The M500 system features a 5" control panel with a bright, clear display. It offers an icon- driven interface and intuitive controls to streamline field operations. Users can execute any function on the device within three taps of the screen. Automatic Recording Functionality Users can program various sensors to activate a new recording. These sensors include emergency lights, sirens, auxiliary inputs, wireless microphones, vehicle speed, and crash detection. When these sensors are triggered, the integrated cameras automatically start recording, allowing officers to capture video evidence without manually activating any cameras. 1.15.2.1 CommandCentral Evidence The In-Car Camera solution includes CommandCentral Evidence, a unified platform for video and device management. It provides command centers and field officers a way to store records, evidence, voice recordings, and video footage captured from 4RE and M500 cameras all in one place. With this solution, the City can streamline the collection of evidence captured by officers' cameras and upload them into one platform. This eliminates data silos that would inhibit the City's efficiency while working on cases. CommandCentral Evidence then allows for playback, redaction, automated transcription, and more to get the most information out of the video evidence as possible. Once evidence is reviewed, it can be shared with prosecutors, other agencies, and the community all while adhering to chain of custody. 1.15.2.2 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 information is integrated with mapping software that automatically publishes crime data from Niche Records and/or PremierOne Cloud CAD to an interactive, online, public- Exhibit A: Contract Documentation Requirements 20 SeNices Solution Description Motorola Solutions CD May 10, 2022 Item #11 Page 397 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 facing 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 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) 1.15.3 Motorola V300 Body Worn Cameras Video-As-A Service Offer The Motorola V300 HD body camera and its continuous-operation capabilities solve the dilemma of keeping cameras and officers productive beyond a 12-hour shift. A detachable battery is easily changed by the officer. Wireless uploading makes footage available when still in the field, while advanced encryption guarantees secure delivery. When events unfold rapidly, patented Record-After-the-Fact® technology allows recovery of video, even when the record button was not pressed. Body camera video captured by the Motorola V300 is clear and complete thanks to de-warping technology that removes the fisheye effect. When integrated, CommandCentral Aware natively provides the ability to livestream and . locate the V300 BWC on a map similar to "find my camera functionality". In addition, CommandCentral Aware provides historical replays of location and video data. CommandCentral Aware integration with 9-1-1 call data, video management systems, License Plate Recognition technology, and other system sources supports the overlay of V300 location data to provide real time intelligence. Additionally, our rules engine can be configured to notify users when specific mission parameters are met and to eliminate user distraction. Key Features and Functionality • Detachable Battery • Durability • Exceptional Audio-Visual Quality • High Data Security • Post-Event Evidence Retrieval • Multiple Docking options • Officer-Friendly User Interface • In-Field Tagging • Auto Activation/Triggers Exhibit A: Contract Documentation Requirements G Motorola Solutions Services Solution Description 21 May 10, 2022 Item #11 Page 398 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 SECTION 2 City of Carlsbad, CA February 16, 2022 STATEMENT OF WORK 2.1 STATEMENT OF WORK OVERVIEW 2.1.1 2.1.2 In accordance with the terms and conditions of the Agreement, this Statement of Work ("SOW') defines the principal activities and responsibilities of all parties for the delivery of the Motorola Solutions ("Motorola") service as presented in the PremierOne Cloud Subscription Services Description document to City of Carlsbad, CA hereinafter referred to as "Customer". 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 in a Responsibility Table and providing the deliverable(s) listed in the Motorola Deliverables table. 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 the Agreement and any reference within this document as well as subcontractors' SOWs (if applicable) does not imply or convey a software or subscription license or service that are not explicitly listed in the Agreement. The specific software applications that comprise the System are outlined in the price page of the Agreement. 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. 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. Exhibit A: Contract Documentation Requirements 22 Statement of Work Motorola Solutions C., May 10, 2022 Item #11 Page 399 of 604 DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.1.3 2.2 2.2.1 • 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. 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 (SM E's) in project delivery meetings and working sessions during the course of the project. Customer SM E's will possess requisite knowledge of Customer operations and legacy system(s) and possess skills and availabilities to operate and manage the System. 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 Google Meet. PROJECT ROLES AND RESPONSIBILITIES 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. Exhibit A: Contract Documentation Requirements fl Motorola Solutions Statement of Work 23 May 10, 2022 Item #11 Page 400 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.2.1.1 2.2.1.2 Motorola Project Manager City of Carlsbad, CA February 16, 2022 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. Responsibilities of the Project Manager include: 1. Managing the Motorola responsibilities related to the delivery of the project. 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. 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. 8. Conducting remote status meetings on a monthly basis by the Project Managers to discuss project status. 9. Participate in weekly calls regarding current activities. 10. Preparing and submitting a monthly 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. 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. 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. Exhibit A: Contract Documentation Requirements 24 Statement of Work Motorola Solutions f.' May 10, 2022 Item #11 Page 401 of 604 DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.2.1.3 2.2.1.4 2.2.1.5 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. 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 G IS 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) 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 Activations Team The Cloud Activations team will establish the cloud tenant for the Customer environment, work with the Customer to grant Customer access, and coordinate with the Customer to establish access to CC Reporting. 2.2.1.6 Motorola Customer Success Advocate 2.2.1.7 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 T earn Motorola's Customer Support team will provide ongoing support, Customer Support Plan (CSP) following Customer commencement of beneficial use of the System. Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 25 May 10, 2022 Item #11 Page 402 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.2.2 2.2.2.1 Customer Roles and Responsibilities City of Carlsbad, CA February 16, 2022 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. 3. Consolidating all project-related questions and queries from Customer staff to present to the Motorola Project Manager. 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 raised by the Motorola Project Manager. 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. Exhibit A: Contract Documentation Requirements 26 Statement of Work Motorola Solutions fl May 10, 2022 Item #11 Page 403 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 202.2 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 Motorola personnel. 2.2.2.2 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. 2.2.2.3 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). 2.2.2.4 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 PremierOne Cloud systems will interface. 2.2.2.5 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 user agency stakeholders related to business processes and provisioning. Exhibit A: Contract Documentation Requirements f.l Motorola Solutions Statement of Work 27 May 10, 2022 Item #11 Page 404 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.2.2.6 Customer GIS Analyst City of Carlsbad, CA February 16, 2022 The Customer G IS Analyst is responsible for the development and maintenance of all of the GIS data used in the PremierOneCloud 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 Cloud Services (Server and clients) 2.2.2.7 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. 2.2.2.8 Customer Training Representative Training representatives will be the point of contact for the Motorola Application Specialist when policy and procedural qu~stions arise, act as course facilitators, and are the Customers' educational monitors. 2.2.2.9 Additional Resources Additional resources, such as trainers and database administrators may also be required. 2.2.2.10 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 SM Es 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. Exhibit A: Contract Documentation Requirements 28 Statement of Work Motorola Solutions 0 May 10, 2022 Item #11 Page 405 of 604 DocuSign Envelope ID: EE0000EC-819O-469F-887C-147E38CEAFF7 City of Carlsbad, CA February 16, 2022 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 Google 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 PremierOne Cloud Subscription Services Description document • Review project delivery requirements as described in this 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. The 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 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 • Confirm requirements for CJIS background investigations and/or contractors, fingerprint requirements for Motorola employees and/or contractors. Required fingerprints will be submitted on Motorola Solutions provided FBI FD-258 Fingerprint cards • Review Virtual Desktop (VD) and Learning exPerience Portal (LXP) role in the delivery and discuss required Customer provided information to access them • 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. Exhibit A: Contract Documentation Requirements @ Motorola Solutions Statement of Work 29 May 10, 2022 Item #11 Page 406 of 604 DocuSign Envelope ID: EEO000EC-B19D-469F-887C-147E3BCEAFF7 Motorola Responsibilities 1. Schedule the remote Project Planning Session 2. Provide the initial Project Schedule and Project Management Plan City of Carlsbad, CA February 16, 2022 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 Cloud File Build tablesFile. 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 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. Milestone -Project Planning Session Mutual agreement to Project Schedule and Project Management Plan Exhibit A: Contract Documentation Requirements 30 Statement of Work Motorola Solutions 0 May 10, 2022 Item #11 Page 407 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.3.2 2.3.3 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. The Project Kickoff Session is considered complete upon conclusion of the meeting. 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 • 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 the meeting. Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 31 May 10, 2022 Item #11 Page 408 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.3.4 City of Carlsbad, CA February 16, 2022 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 Customer delivery of sample GIS data within 10 days of GIS Planning Session. Interface Planning Session -Teleconference/Web Meeting An Interface Planning Session will be scheduled to discuss the user experience presented by each contracted interface as defined in the PremierOne Cloud Subscription Services Description document and the Interface Fuctional Descriptions (IFDs) in Section 8. The agenda will include: • Conduct a review of the functionality delivered with each interface • Discuss interface deployment requirements (NOA, 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 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 (NOA) as required. Customer Responsibilities 1. Provide the required interface deployment requirements (NOA, network information, API and access credentials required to connect to third party systems) within ten (10) business days of the Interface Planning Meeting so as not to impact the Project Schedule. Exhibit A: Contract Documentation Requirements 32 Statement of Work Motorola Solutions G May 10, 2022 Item #11 Page 409 of 604 DocuSign Envelope ID: EEO000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.3.5 Mutually accepted IFDs Customer delivery of interface deployment requirements within 10 days of Interface Planning session. Connectivity Planning Session• Teleconference/Web Meeting A Connectivity Planning Session will be scheduled to discuss the connectivity required for the service. The agenda will include: • Review Azure Active Directory requirements. • Review of connections of end user workstations to the Cloud service. • Interfaced system connectivity to the service. • 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. The Connectivity Planning Session is considered complete upon conclusion of the meeting. Exhibit A: Contract Documentation Requirements C., Motorola Solutions Statement of Work 33 May 10, 2022 Item #11 Page 410 of 604 OocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 2.3.6 City of Carlsbad, CA February 16, 2022 Complete the base connectivity requirements within ten (10) days of planning session. CommandCentral Aware -Video Management System (VMS) Design Review The objective of the VMS Design Review is to collect all information required to connect and configure the CommandCentral Aware and VMS lnterface(s). Motorola Responsibilities 1. Identify the specific inputs required from Customer for all VMS interfaces. 2. Add VMS interface details to the VMS Design Review Report. Customer Responsibilities 1. Discuss information on third party API, SDKs, data schema and any internal and 3rd party documents necessary to establish interfaces with all local and remote systems and facilities within ten '( 10) days of the Project Kickoff Meeting so as not to impact the project schedule. 2. Work with the owners of the new and existing data and video equipment to establish network connectivity (where applicable). 3. Gather data required to configure VMS interfaces and provide information as CSV or in Excel spreadsheets. 4. For VMS interfaces that will be configured for each location where Network Video Recorders (NVR) and cameras are installed, the Customer must provide all camera name, coordinates and IP mapping and the network plan in CSV or Excel files prior to Motorola commencing configuration of the VMS interfaces. The Connectivity Planning Session is considered complete upon conclusion of the meeting. 2.4 PREMIERONE CLOUD SERVICES PROJECT EXECUTION The execution of PremierOne Cloud 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 Cloud 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 Subscription Services Description document. Exhibit A: Contract Documentation Requirements 34 Statement of Work Motorola Solutions 0 May 10, 2022 Item #11 Page 411 of 604 DocuSign Envelope 10: EE0000EC-819O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.4.1 2.4.1.1 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: • The services sold in a PremierOne Cloud CAD deployment model are based on a six (6) month deployment. • Actual project duration will be established as part of the Project Schedule development activities. PremierOne Cloud Hardware and Environment General Hardware and Environment Requirements The Customer will provide hardware and/or an environment that conforms to the following general requirements: Customer Responsibilities 1. Supply hardware, operating system software, third party components, and other elements not specifically identified as being provided by Motorola. 2. Provide advanced authentication for Mobile/Hand held 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. Provide IP addresses on the Customer's network for the required on-premise equipment (i.e the Anchor Server). All server names and IP addresses behind Motorola Firewalls cannot be changed. 5. Provide external interface connection demarcation points at locations agreed to by Motorola. These locations shall normally be adjacent to the cloud interface appliance. 6. Provide access, administrative or otherwise, to appropriate systems, locations, information, tools, and equipment to ensure proper connectivity, installation, operations, and maintenance of the service. 7. 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. 8. Provide 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. 9. 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 cloud interface Anchor Server appliance. It is understood that remote access to on-premise server and Customer's network must be supervised, which supervision will be provided. Customer-provided high-speed internet access with a minimum of 10 Mbps is required at the time of project kickoff and must remain available to Motorola throughout warranty and support periods to accommodate remote support of the service. In the event that dedicated links are required, a minimum of 7.5 Mbps upload and download access is required. It is the Customer's responsibility to ensure Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 35 May 10, 2022 Item #11 Page 412 of 604 DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 that the aforementioned capacity is available. In the event remote broadband access is not available to Motorola preventing us from delivering the contracted service remotely, Motorola will provide service on-site at additional cost. The additional cost will be presented to the Customer via the change provision of the contract prior to the delivery of the on-site service. 10. 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 central server for maintenance and updates, the connectivity including ports and access needs to be provided. 2.4.1.2 Component Specifications Motorola will provide Commsys Connect CIC. The Customer will provide the server hardware and firewall devices. PremierOne Cloud Anchor Hardware Customer Responsibilities 1. Provide, install and configure server hardware, operating system software, VMWare, firewall devices, Lantronix External Device Server and SQL Standard. Specifications will be provided at the Planning Meeting. A. Provide a VMware host environment capable of supporting two VMs. i. Windows Server VM, 4vcpu, 16GB RAM and 3 HOD 120/120/25GB ii. Linux VM, 2VCPU, 8GB RAM and 1 HOD 20GB B. Verify the VM has connectivity to the internet and the following addresses, which are commonly used by CloudConnect: i. https://idm.imw.motorolasolutions.com (443) -IDM ii. https://aware-api.usgov.commandcentral.com (443) -Ingest iii. https://admin-api.usgov.commandcentral.com (443) -Admin 1v. https://aware-publisher-ws.usgov.commandcentral.com (443) -Publisher (WebSocket) v. https://registry.commandcentral.com (443) -Registry vi. https://oneinterfaceblobstore.blob.core. usgovcloudapi. net/( 443) -I mageNideo upload vii. Additional Endpoints For IMW/LRRP Interfaces viii. https://ccinterfaces-ccbroker-prod. usgov. commandcentral. com/api/ccinterfaces- ccbroker (443)-IMW/LRRP ix. https://ccinterfaces-sasgen-prod.usgov.commandcentral.com/api/sasgen (443) - SAS Token x. https://qrwbubhpaovhj-sbu.servicebus.usgovcloudapi.net (443) (Websocket) (inbound-outbound) Exhibit A: Contract Documentation Requirements 36 Statement of Work Motorola Solutions G May 10, 2022 Item #11 Page 413 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.4.1.3 Motorola Responsibilities 1. Provide the CloudConnect VM image to Customer. 2 . Remotely support installation of VM image on Customer hardware. CommSys Connect CIC Motorola Solutions Responsibilities 1. Provide CommSys Connect CIC. PremierOne Cloud CAD Local Workstation The Customer will procure and provide local (fixed) workstation hardware that conforms to the requirements laid out in this section. • Windows 10 operating system. • Monitor(s) -two or three with recommended resolution 1920 x 1080 (per client preference: i.e. three for CAD dispatch, two for CAD call taker, etc.). • QWERTY Keyboard with 12 function keys PremierOne Cloud Field Workstation The Customer will procure and provide field (mobile) workstations/devices that conform to the requirements laid out in this section. • Android smartphones and tablets with Android 8 -10. • iPhones and iPads with iOS 11 -13. • Windows laptops and tablets with Windows 10. PremierOne GIS Workstation The Customer will procure and provide GIS workstation hardware that conforms to the requirements laid out in this section. • Android smartphones and tablets with Android 8 -10. • iPhones and iPADs with iOS 11 -13. • Windows laptops and tablets with Windows 10. CommandCentral Aware Workstation The Customer will procure and provide Aware workstation hardware that conforms to the requirements laid out in this section. • Processor-Intel Xeon 6136 @3.0 GHz (12 cores). • Memory-32 GB. • Drive-One NVMe 512G SSD. • NIC-1 GB port NIC. • OS-Windows 7 Professional or Windows 10 Pro. • Graphics Card-NVIDIA Quadro P2000 • 27-inch Narrow Bezel IPS Display, 2560X1440 Network and Other Environment Specifications Unless otherwise stated in this SOW, the Customer will provide a network environment that conforms to the requirements laid out in this section. The Customer will provide an Exhibit A: Contract Documentation Requirements fl Motorola Solutions Statement of Work 37 May 10, 2022 Item #11 Page 414 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 environment sufficient to support the transaction volume generated during Customers peak operational periods. Network Connection Requirements PremierOne Cloud client connections must meet the following requirements: • Stable internet connection. • Small Jitter (packet delay variation) -below 200ms, recommended <30ms. • Small Ping roundtrip time -below 1 00ms, recommended <20ms. • Small Packet Loss -no more than 1 %. • Bandwidth: 1 Mbps per fixed client (will vary with specific usage). • Provide cloud connectivity services for desktop CAD user clients per specifications. • Provide for outbound Internet connectivity initialized by Cloud Anchor Server. Multiple paths are preferred for the PremierOne Cloud CAD Service. ISP connectivity to the Azure Public Edge is required for the CAD client connectivity. Interfaces to on-premise systems use a VPN device that requires connectivity to the Azure Public Edge. The Customer is responsible for providing all connections to the cloud. Mobile Network Requirements PremierOne Mobile functionality is designed for 3G and high-end 4G networks. 3G network connectivity is required, but faster 4G connectivity is highly recommended. The Customer will provide a 3G/4G wireless network infrastructure and connectivity with routing between the Mobile clients and the cloud that meets or exceeds these minimum requirements. Customer Responsibilities 1. Supply Mobile Device Management (MOM) software for Handheld devices. 2. Supply Mobile Device Management (MOM) software for Mobile devices, as desired by the Customer. 3. Provide wireless connectivity for mobile clients to the Azure cloud. Optimal application performance on mobile workstations requires 4G connectivity. Aware Network and Bandwidth Requirements • Two (2) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Virtual Machines. • Three (3) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Server. • One (1) network port for each VMS server. • One (1) network port for each VMS analytics appliance • Provide network ports that are 1 GB capable and network routable. • Minimum bandwidth needed between the Cloud Anchor server and the CommandCentral Aware platform is 1.1 Mbps. • Low latency is critical for real-time operations. The speed with which data appears on the Aware display depends in large part on how quickly the information is presented to the Aware interface. Major contributors to the latency are network delays and the delay time from occurrence of an event to when that event information is presented to Aware from the source application (i.e., CAD, AVL, ALPR, etc.). Consequently, although the Exhibit A: Contract Documentation Requirements 38 Statement of Work Motorola Solutions 0 May 10, 2022 Item #11 Page 415 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Aware strives to provide near-real-time performance, Motorola provides no guarantees as to the speed with which an event (or video stream) appears on Aware once the event is triggered. Vigilant LPR Requirements Bandwidth requirements: • 1 Gbps hardwire switched network between the Vigilant server and Cloud Anchor. • Upload of ALPR data to the LEARN backoffice requires approximately 350 Kbps for each scan per second. Depending on maximum scan volume, the maximum bandwidth may need to be adjusted. • The RTSP video feed from cameras requires a 1Gbps hardwire switched network device to allow for data communications exceeding four connected cameras. Firewall requirement: • CommandCentral Aware Workstation needs access to the IP addresses of Cloud Anchor and Vigilant server. Access to Cloud platform endpoints. • Ports that need to be open-TCP 80, TCP 443, TCP 331 O (or custom SQL Database Engine listening port that might have been configured for security reasons). • The basic service requirements of the system through a firewalled environment consist of: HTTPS web based calls to a cloud back-office solution (LEARN) with S3 image storage. Typically, through a mobile broadband endpoint. A local IP listener for RTSP video stream is used from cameras with TCP communications. • Ingress requirements (firewall traffic in): For Wireless Broadband we require TCP port 443 to communicate with the LEARN server backoffice to receive acknowledgement responses from the client. Camera Communications: TCP port 2000, 3000, 4000, 5000 (LAN/DSP). • Egress requirements (firewall traffic out): For Wireless Broadband communications the ALPR client requires TCP port 443 to communicate with the LEARN server backoffice. The HTTPS protocol is primarily used to communicate over TLS 1.0, 1.1, or 1.2 with 128-bit encryption ciphers or better. This allows for the upload of ALPR data to the LEARN web services and request for data from the LEARN services and Google Maps. ASTRO 25 Radio and Infrastructure Requirements The solution can be deployed to send location data information using an AST RO 25 radio equipped with a GPS receiver with minimum firmware version 7 .18.8 and at software version R15.00.00 or later. ASTRO 25 system release 7.14 or above is required if the data will be sent via the LMR system. Enhanced Data and Intelligent Middleware (IMW) in addition to a firewall to connect the system GEN and internet securely including a packet data gateway and GGSN for each zone are used to send the location updates and events can be enabled as part of that effort. Customer will be responsible to provide internet connection and will allow Motorola to add any necessary firewalls. • GPS Activation and Enabled. • Packet Data Interface. • Enhanced Data Enabled. -Supported on portables-APX 8000, APX 7000, APX 6000, APX 4000, APX 3000. -Supported on mobiles-APX 7500, APX 6500, APX 4500. Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 39 May 10, 2022 Item #11 Page 416 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.4.2 • Enhanced Data Port List set to 4001. ASTRO 25 Voice Priority City of Carlsbad, CA February 16, 2022 ASTRO Enhanced Data subscribers give priority to voice transmissions over data. PremierOne Cloud 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 Cloud 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 Customers needs. 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 Cloud 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) Exhibit A: Contract Documentation Requirements 40 Statement of Work Motorola Solutions 0 May 10, 2022 Item #11 Page 417 of 604 DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.4.3 2.4.3.1 • 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. Customer provides information required to complete BPR Workbook during BPR session. 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 Cloud services. Exhibit A: Contract Documentation Requirements Q.l Motorola Solutions Statement of Work 41 May 10, 2022 Item #11 Page 418 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.4.3.2 GIS Scope Review topics that will be discussed include: City of Carlsbad, CA February 16, 2022 • 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. Completion of PremierOne GIS Review meeting PremierOne Cloud CAD -GIS Boundaries Meeting If PremierOne Cloud CAD is contracted as a System component, the Motorola GIS Analyst will meet remotely with the Customer's GIS Administrator and CAD SM Es to discuss and confirm Response Boundaries data that is loaded into the PremierOne Cloud CAD service. Motorola will provide an overview of the available boundaries types and their function that can be used in the PremierOne Cloud 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 Cloud CAD to determine if any modifications need to be made prior to import into the PremierOne Cloud CAD. Exhibit A: Contract Documentation Requirements 42 Statement of Work Motorola Solutions May 10, 2022 Item #11 Page 419 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 The Agency Code and Beat Names are required to be provided prior to the GIS Boundaries Meeting. Motorola Solutions Responsibilities 1. Provide an overview of the Agency Code and Beat Names role in the PremierOne Cloud CAD. Customer Responsibilities 1. Ensure availability of GIS administrator for this meeting. 2. Confirm Agency Code and Beat Names readiness for load into PremierOne Cloud 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 Cloud CAD 2.4.3.3 GIS CheckPoint Meetings The Motorola GIS Analyst .and Customer's GIS Administrator will participate in up to five (5) -two (2) hour remote CheckPoint 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 -Completion of PremierOne Cloud 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 CheckPoint 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 Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 43 May 10, 2022 Item #11 Page 420 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 2.4.3.4 2.4.4 2.4.4.1 Completion of PremierOne GIS CheckPoints Meetings PremierOne Cloud Services -GIS Draft Geodatabase City of Carlsbad, CA February 16, 2022 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. This task is completd upon delivery of the third draft geodatabase, maps and Routing Network. Provisioning PremierOne Cloud Provisioning PremierOne Cloud provisioning includes the configuration of user configurable parameters (i.e unit names, personnel, status codes). The PremierOne Cloud System will be provisioned using Motorola standard provisioning parameters and will incorporate Customer specific provisioning. PremierOne Cloud CAD provisioning is defined in Appendix A -PremierOne Cloud Attachment. 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 Exhibit A: Contract Documentation Requirements 44 Statement of Work Motorola Solutions I' May 10, 2022 Item #11 Page 421 of 604 OocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 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 Pro0visioning 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 Cloud provisioning activities will be completed for each functional application group included in the System: CAD/Mobile/CommandCentral Aware. 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 Cloud 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 Cloud CAD, the Motorola Application Specialist will complete the standard provisioning as defined in Appendix A -PremierOne Cloud Attachment. 5. For PremierOne Cloud 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 Cloud Mobile Check Point #1 Initial Provisioning Review/Discussion B. PremierOne Cloud Mobile Check Point #2 Follow-up Provisioning Review/Discussion C. PremierOne Cloud Mobile Check Point #3 Customer Provisioning Review/Handoff D. PremierOne Cloud Mobile Client Installation Training (Windows, Android/iOS) is required to be completed prior to this meeting. E. PremierOne Cloud 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. Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 45 May 10, 2022 Item #11 Page 422 of 604 DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 2.4.4.2 6. Complete the import of the data from Provisioning Worksheets. Customer Responsibilities City of Carlsbad, CA February 16, 2022 1. Provide required information to complete the Provisioning Worksheets within ten (10) business days of the so as not to impact the Project Schedule. Customer completion of Provisioning Worksheets within 10 days of receipt of the worksheets. PremierOne Cloud Provisioning Workshop(s) Post completion of the PremierOne Cloud 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 Cloud 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. 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 Cloud Provisioning Workshop(s). 4 . Assume responsibility for the continued maintenance of the Customer provisioning. Exhibit A: Contract Documentation Requirements 46 Statement of Work Motorola Solutions C., May 10, 2022 Item #11 Page 423 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.4.4.3 2.4.4.4 Completion PremierOne Cloud Provisioning Workshop(s) Hand-off the responsibility for provisioning to the Customer CommandCentral Aware 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 off Customer Active Directory data. Customer Responsibilities 1. Supply the access and credentials to Customer's Active Directory for the purpose of Motorola conducting CommandCentral Solution provisioning. 2. Respond to Motorola inquiries regarding users/groups/agency mapping to CommandCentral Solution functionality. Completion Criteria -CommandCentral Aware Provisioning CommandCentral provisioning is complete upon Motorola completing provisioning activities in accordance with the mutually approved approach. CommandCentral Investigate Installation and Credentialing (formerly CommandCentral Analytics Plus) Motorola Solutions enables the CommandCentral Investigate service during the order process. LexisNexis accreditation is required to be completed by the Customer prior to the start of the project. 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. Exhibit A Contract Documentation Requirements G Motorola Solutions Statement of Work 47 May 10, 2022 Item #11 Page 424 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 2.4.5 2.4.5.1 Motorola Responsibilities 1. Provide the credentialing application to Customer. 2. Complete site inspection and provide site inspection questionnaire. City of Carlsbad, CA February 16, 2022 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 Cloud 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. CommandCentral Investigate subscription enabled and access verified. CAD Client Installation PremierOne Cloud CAD Client The Customer will access PremierOne Cloud CAD client through a Citrix Virtual Application. The PremierOne Cloud Clients will need to be available throughout the delivery process. Motorola Responsibilities 1. Provide remote PremierOne Cloud client installation overview/instruction 2. Verify PremierOne Cloud Client installation for up to two (2) clients Customer Responsibilities 1. Provide the CAD client workstation in accordance with the specifications presented in the PremierOne Cloud Subscription Service Description document 2. Participate in Motorola PremierOne Cloud client installation overview/instruction 3. Complete installation for remaining PremierOne Cloud clients Customer completes CAD Client Installation on Remaining CAD Workstations Exhibit A: Contract Documentation Requirements 48 Statement of Work Motorola Solutions G May 10, 2022 Item #11 Page 425 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.4.5.2 2.4.5.3 2.4.6 PremierOne Cloud Mobile Client Installation (Windows, Android/iOS) The Customer can download the PremierOne Cloud Mobile client from an on-line app store. Motorola will provide the Customer app store locations from which the client can be downloaded and installed. PremierOne Cloud Mobile (Windows, Android/iOS) Installation training will be provided by Motorola as defined in the Training Plan. Deployment of PremierOne Cloud Mobile (Windows, Android/iOS) updates is a Customer responsibility. Customer Completes Mobile Client Installation on Mobile Devices (Windows, Android/iOS) 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 remote access to the CommandCentral Aware workstations. Configuration of and successful demonstration of CommandCentral Aware client application. Functional Validation Motorola will execute the PremierOne Cloud and CommandCentral Functional Validation prior to Customer training and in accordance with the Functional Validation Workbook. The purpose of this exercise is to verify and document that the PremierOne Cloud service is ready for Beneficial Use. The following severity level definitions provide the classification of anomalies that may manifest during the functional validation review. Critical Level Severity: 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 Level Severity: An incident is deemed HIGH if a business function is unavailable and normal customer business activit is im acted or de raded, and a workaround ma be available Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 49 May 10, 2022 Item #11 Page 426 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 2.4.6.1 2.4.6.2 2.4.6.3 City of Carlsbad, CA February 16, 2022 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 Level Severity: 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). Critical and High-level severity issues, whether identified during PremierOne Cloud 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 defect. 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 severity issues are considerd "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 but such testing may be conducted by the Customer. The Functional Validation verifies the functionality of the system and is not a validation of the provisioning. Functional validation is provided for each Product contained in the System as follows: PremierOne Cloud CAD Functional Validation Motorola will schedule a remote two (2) day session with the Customer to demonstrate the CAD functional validation. PremierOne Cloud CAD functional validation verifies the functionality of the CAD service and does not include the testing of other products or interfaces. PremierOne Cloud Mobile Functional Validation Motorola will schedule a remote one-half (1/2) half day session with the Customer to demonstrate the Mobile functionality on one (1) PremierOne Cloud Mobile device. PremierOne Cloud Mobile functional validation verifies the functionality of the Mobile service and will be completed post completion of the PremierOne Cloud CAD functional validation. CommandCentral Functional Validation Demonstration Motorola will provide a functional demonstration script and will demonstrate CommandCentral Aware functionality during a one-half (1/2) day session with the Customer. Exhibit A: Contract Documentation Requirements 50 Statement of Work Motorola Solutions G May 10, 2022 Item #11 Page 427 of 604 DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.4.6.4 Customer Led Scenario Validation Post completion of the Functional Validations the Customer will begin utilizing the PremierOne Cloud 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 include scenarios based on Motorola responses to the Functional Requirements Matrix. Issues that are discovered during this validation exercise will be reported to Motorola for issue resolution in accordance with the Agreement. 2.5 PREMIERONE CLOUD REPORTING PremierOne Cloud CAD utilizes Motorola's CommandCentral Reporting to provide reporting capability. Motorola will deliver access to CommandCentral Reporting to the Customer's identified reporting administrator. Motorola will also establish a reporting data warehouse (ROW) in the cloud to support ad- hoc reporting with PremierOne CAD data using SQL Server Reporting Services (SSRS). The standard CAD Reports Library will be provided. Customer-specific or Customer defined reports are not included in the scope of this project unless defined in this SOW. Motorola Responsibilities 1. Provide access to the CommandCentral Reporting environment to the Customer reporting administrator. 2. Provide overview/instruction to Customer reporting administrator on how to access the CommandCentral Reporting environment. 3. Develop the ROW environment in the cloud. 4. Conduct SSRS Report Builder Training. 5. Provide the Standard CommandCentral Reports and the PremierOne CAD Reports library. Customer Responsibilities 1. Identify the agency's reporting administrator and provide their Name, Email and Phone Number. 2. Setup Azure AD for use with CommandCentral Reporting. 3. Participate in SSRS Report Builder Training. Completion Criteria -PremierOne Cloud Reports PremierOne Cloud Standard Reports PremierOne SSRS Reporting in the Cloud Exhibit A: Contract Documentation Requirements C., Motorola Solutions Statement of Work 51 May 10, 2022 Item #11 Page 428 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.6 INTERFACE AND INTEGRATION DELIVERY City of Carlsbad, CA February 16, 2022 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 Cloud Service Description, Project Schedule, and Interface Functional Documents (IFDs) provided to Customer prior to contract and incorporated as an Ordering Document. 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 Cloud Subscription Service document and the IFOs. 3. Provide the Customer with the Interface Configuration Guides. 4. Provide Customer training for the PremierOne Cloud CAD provisioning of the interface as applicable. 5. 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. Complete Customer defined PremierOne Cloud CAD provisioning as applicable. 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 Exhibit A: Contract Documentation Requirements 52 Statement of Work Motorola Solutions 0 May 10, 2022 Item #11 Page 429 of 604 DocuSign Envelope ID: EE0000EC-819O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.7.1 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. Interface Validation The objective of Interface Validation Demonstration is to verify that the installed interfaces perform according to the Interface Functional Documents {IFDs). 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 i~terface, with the Customer, to validate each function per the IFD. 2. Develop a remediation plan for features that do not perform in accordance with the IFD. 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 and High-level severity issues as defined in this SOW. Customer Responsibilities 1 . Provide access to a resource with access to the interfacing system to validate functionality. 2. Witness the execution of the validation and acknowledge successful completion. 3. Upon completion, sign and return the Project Milestone Document within ten (10) business days 4. Participate in the documentation of items that do not perform in accordance with the IFD and work with Motorola to develop remediation action(s). Interface Validation Demonstration completed and Customer acknowledgement of completion Exhibit A: Contract Documentation Requirements CD Motorola Solutions Statement of Work 53 May 10, 2022 Item #11 Page 430 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 2.8 2.8.1 2.8.2 City of Carlsbad, CA February 16, 2022 PREMIERONE CLOUD AND COMMANDCENTRAL TRAINING AND CONSULTATIVE SERVICES 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 are able to 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. 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 1. Provide Motorola with names (first and last) and emails of Customer LXP administrators. 2. Provide access to learningservices.motorolasolutions.com. 3. Complete LXP Administrator training. 4. Advise users of the availability of the LXP. 5. Add/modify users, run reports, and add/modify groups. 6. 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. CommandCentral Aware 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. Exhibit A: Contract Documentation Requirements 54 Statement of Work Motorola Solutions CD May 10, 2022 Item #11 Page 431 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.8.3 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. 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. 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 in the following solution specific tables, are selected and customized to meet the needs of the Customer. Motorola Responsibilities 1. Conduct disco'very 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. Exhibit A: Contract Documentation Requirements CD Motorola Solutions Statement of Work 55 May 10, 2022 Item #11 Page 432 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbacl, CA February 16, 2022 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. Delivery of After-Action Report and completion of teleconference post the on-site visit. 2.9 PREMIERONE CLOUD AND COMMANDCENTRAL GO LIVE 2.9.1 The transition to live operations to Motorola's PremierOne Cloud 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 joint go live event of PremierOne Cloud CAD, Mobile. The separation of the go live events may result in a Change Order to add additional services. If separated, the below sections apply to each go live event. PremierOne Cloud 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 • Readiness review meetings • Contingency/roll-back plans • Go live tasks and responsibilities during and after the live cut • Post live cut support resources and schedules • Issue reporting process Exhibit A: Contract Documentation Requirements 56 Statement of Work Motorola Solutions fl May 10, 2022 Item #11 Page 433 of 604 OocuSign Envelope ID: EE0000EC-B 19O-469F-887C-14 7E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.9.2 2.9.3 2.9.4 • 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 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 CommandCentral Aware Production Use Following the completion of the functional demonstration of CommandCentral Aware, the Customer may commence using CommandCentral Solution for all purposes including production use. CommandCentral Investigate Production Use Following the completion of the activation of CommandCentral Investigate, it is deemed available for all purposes including production use. Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Work 57 May 10, 2022 Item #11 Page 434 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 2.9.5 2.10 PremierOne Cloud Go Live Event City of Carlsbad, CA February 16, 2022 The transition to production use of the PremierOne solution will be conducted according to the Cutover Plan. The cutover event represents the System Completion milestone and 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. • CAD Post-Go Live Support (remote) will be available for up to thirty (30) days following Go Live. During this period, the PM and Application Specialist will remain engaged to provide updates on issues that occur prior to and during Go Live. The Customer Support organization will be the primary point of contact to report issues that arise after Go Live. 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. 4. Provide remote post-go live support for up to thirty (30) days. 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 Cloud Go Live Event Completion of Go Live Activities Live PremierOne Cloud system PROJECT CLOSURE Project Closure involves the steps to close the project and transition the PremierOne System from the delivery team to Customer Support. Exhibit A: Contract Documentation Requirements 58 Statement of Work Motorola Solutions C., May 10, 2022 Item #11 Page 435 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 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 OPTIONS AVAILABLE AT AN ADDITIONAL PRICE The following solution components are presented for the City's consideration. While not required to support the PremierOne Solution, each of the following separately priced options enhance the solution by adding additional capabilities. 2.11.1 Option 1 • Motorola In-Car Cameras (Either 4RE or M500) The in-car cameras will be configured and installed in vehicles. Motorola Responsibilities 1. Create Configuration USB. 2. Configure Each DVR as installs are completed. 3. Deliver training. 4. Perform testing in accordance with the test plan. 5. Provide thirty (30) days of remote support following production use of the in-car cameras. Customer Responsibilities 1. Ensure availability of vehicles in accordance with agreed-upon schedule. 2 . Provide cradlepoint routers and ethernet connections in each vehicle. 3 . Install cameras in vehicles. 4. Evaluate the performance of the complete in-car camera system. 5. Acknowledge successful completion of the in-car camera implementation. Completion Criteria -Motorola V300 Body-Worn Cameras This task will be complete when Motorola has configured the 4RE or M500 in-car cameras and Customer acknoweldges successful completion of testing. 2.11.2 CommandCentral Community Motorola Solutions enables the CommandCentral Community service during the order process. Deployment services are not required. Training will be made available via the LXP as described herein. Following the completion of the activation of CommandCentral components described below, implementation activities for CommandCentral Community are complete. Exhibit A: Contract Documentation Requirements CD Motorola Solutions Statement of Work 59 May 10, 2022 Item #11 Page 436 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 Motorola Solutions Responsibilities City of Carlsbad, CA February 16, 2022 1. Use the CommandCentral Admin tool to enable Customer access to CommandCentral Community. This activity is completed during the order process. 2. Connect to PremierOne Cloud CAD. Customer Responsibilities 1. Provision policies and procedures, tags, retention periods, and user permissions. 2. Configure CommandCentral Community settings (location of agency pin, shape of agency, keywords, set up agency page, URL, which forms to deploy). 3. Provide access to Motorola Solutions' team to connect incident data ingest. 2.11.2.1 Additional Forms Additional Forms for CommandCentral Community are provided by SeamlessDocs. SeamlessDocs will also set up the Customer with URL information and login credentials. Motorola Solutions Responsibilities 1. Send correct order information to SeamlessDocs. Customer Responsibilities 1. Work with SeamlessDocs to accomplish onboarding tasks. 2. Link SeamlessDocs portal in Community Admin page. SeamlessDocs Responsibilities 1. Onboard Customer according to normal protocols. CommandCentral Community subscription enabled and successfully demonstrated to Customer. 2.11.3 Option 2 -Motorola V300 Body Worn Cameras The V300 body-worn camera is the device that the Customer will use to capture video and photo content in the field. Prior to first use, each V300 camera must be configured. This process is called "Checkout" and involves connecting each camera to evidence management system to assign a configuration and officer name. This process can be done each time the officer needs to be assigned a camera, or can be done in scenarios where officers are assigned a body-worn camera to use on a more permanent basis. The transfer stations are used to charge, store and connect the body-worn camera to the backend system. Training for body worn cameras will be conducted onsite. Motorola Responsibilities 1. Take the V300 device from "out of the box" through complete set-up. Exhibit A: Contract Documentation Requirements 60 Statement of Work Motorola Solutions t/.l May 10, 2022 Item #11 Page 437 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 2.12 2. Provision the V300 to the evidence management system. 3. Configure V300 cameras. 4. Install transfer stations. 5. Test function of the V300 cameras. Customer Responsibilities 1 . Provide a network connection (Ethernet) to the upload seNer or directly to the transfer station for network connectivity. 2. Provide the desired network configuration so the equipment can be delivered configured, ready to deploy. 3. Choose and implement the proper wearability option to mount the V300 to their officers' uniform. Completion Criteria -Motorola V300 Body-Worn Cameras Work is considered complete upon V300 set-up and provisioning being finalized and completion and Customer acknowledgement of functional testing. APPENDIX A-PREMIERONE CLOUD ATTACHMENT The following sections describe standard capabilities and integrations that enhance your PremierOne Cloud solution. These aspects of the solution are included as part of the PremierOne Cloud subscription, providing your users with common seNices, reporting, and mapping capabilities. 2.12.1 Common Services Common SeNices provides system administrators the flexibility to manage internal seNices throughout the PremierOne Cloud platform from a single point. Each system or seNice has common seNices, including GIS, System Security, Reporting, and the system tools for provisioning. 2.12.2 CommandCentral Reporting for PremierOne Cloud Motorola Solutions will provide reporting insights through a curated library of ready-to-use reports. CommandCentral Reporting leverages secure, modern, scalable, and managed infrastructure that isolates reporting workloads from your PremierOne Cloud solution, ensuring a higher performance. 2.12.3 Geographic Information System (GIS) Integration The PremierOne Cloud solution integrates with agency-hosted GIS data sets from an Esri ArcGIS SeNer (geospatial data is uploaded to the system through tools implemented within Esri ArcGIS). Geospatial information within these data sets contributes to display, location validation, and unit recommendation in PremierOne Cloud CAD. Esri's geospatial engine automatically invokes spatial queries to inform users of nearby items, refine geographic Exhibit A: Contract Documentation Requirements G Motorola Solutions Statement of Worl< 61 May 10, 2022 Item #11 Page 438 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 boundaries (by area, beat, sector, precinct, zone, or quadrant), and focus attention on specific locations to better inform response. • The system's tools, made available for Arc Tool box, provide the ability to load local data manually or through an automated model. • 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 provides routing and ET A calculations using the Network Analyst extension. Client maps are displayed using Esri ArcGIS Engine and ArcGIS run-time SOK technologies. • 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. • Solution conformant and geographically accurate GIS data is required for the proper operation of the system. Your agency is responsible for providing complete and accurate GIS data that conforms to the PremierOne GIS Data Requirements. Each agency being added to the system must have their geographic coverage included in the single geodatabase imported into CAD. • 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. 2.12.4 PremierOne Cloud File Build The following table lists the codefile items that are part of the PremierOne Cloud solution. Codefile Item Global Code NENA/APCO Standard Customer Table Provided : ' -:,·.·-~,-,_--____ ---:--r-· ·:·----;--•c·,-, .. ' .-.. -·-.--~ ,_.-.-:--:z.:t--;•: -'--_, ---,~.~--.. J •List and Statute Management · · :.· , ·,,,.-.. --· ; ,-.. :.,_~~""'·· ·\r·c:i~ -·:... ti! ~-~ __:~~1.~C:.~i.~-~----~~~j~-==--~-~~ ◄:_;'..h_ 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 Exhibit A: Contract Documentation Requirements 62 Statement of Work Motorola Solutions CD May 10, 2022 Item #11 Page 439 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Vehicle Color Vehicle Make Vehicle Model Vehicle Style Vehicle Type Incident Types Modifying Circumstances Incident Status -Common Incident Source Call Origination Common Disposition Code Person Role Agency Role Incident Response Factors Coverage Groups Premise Hazard Types Premise Hazard Records Area/BeaUSectors Location Station Names Resource Attribute (Capability/Skill ) Resource Type Exhibit A: Contract Documentation Requirements G Motorola Solutions X NCIC X NCIC X NCIC X NCIC X NENA APCO NENA NENA NENA Standard Standard APCO X Standard X X X X NENA NENA Statement of Work 63 May 10, 2022 Item #11 Page 440 of 604 DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 Primary Unit Status -Common Secondary Unit Status -Common Unit ID -Optional Unit Pre-Assignments Exhibit A: Contract Documentation Requirements 64 Statement of Work Standard Standard City of Carlsbad, CA February 16, 2022 X X Motorola Solutions G May 10, 2022 Item #11 Page 441 of 604 DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 SECTION 3 COST SUMMARY Please reference Motorola's Cost Proposal on the following pages. 3.1 PRICING SUMMARY City of Carlsbad, CA February 16, 2022 Description Price ($) After Total Not To Exceed One Time Cost Based on SOW**** (Excluding Options) (50 CAD Named Users, 175 Mobile Named Users, 175 Aware Named Users, 200 LXP Users) Total Annual Recurring Costs ***(Excluding Options) Years 2-6 Options Available for Purchase Discount* (Including Years 1-6) (Legacy Data Query and Radio PTT IFs and CommandCentral Investigate Plus included in One Time Cost) TOTAL SYSTEM CAD/Mobile/Aware/Options (Years 1-6) Discount $1,065,179 $791,441 $0 $1,856,620 VaaS Options Price ($) #1 Optional Purchase -Body-Worn Camera -VaaS (Years 1-5) #2 Optional Purchase -In-Car Video (60 Units) & Evidence Management-VaaS (Years 1-5) #3 Optional Purchase -In-Car Video (94 Units) & Evidence Management -VaaS (Years 1-5) #4 Optional Purchase Interface -Auto correlation with In-Car Video and RMS with purchase of Option 1, 2, or 3 ONE-TIME DISCOUNT** Applied to Option #1 , #2 and/or Option #3 with the purchase of CAD/Mobile/Aware $423,079 $536,400 $840,360 $12,000 (-$100,000) 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 **With the purchase of PremierOne Cloud CAD, Mobile, CommandCentral Aware and Body Worn Cameras or In-Car Video Motorola has provided an additional discount for Option #1 and/or Option #2. ***Includes three (3) Summit User Group Registrations Annually ****The Total Not to Exceed price is for an 18-month delivery schedule. For each month project is finished under 18 months, Motorola will credit $13,334 per month. Exhibit A: Contract Documentation Requirements G Motorola Solutions Cost Summary 65 May 10, 2022 Item #11 Page 442 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 • #1 Option -Motorola V300 Body Worn Cameras (quantity 130 devices) -Software, Hardware & Refresh: • Video-as-a-Service includes cloud-based evidence management system, with unlimited storage and unlimited cloud sharing. -User licenses on a per-device basis. -CommandCentral Community (evidence capture, records, and CommandCentral Community capabilities included). Body-worn camera (choice of mount) -Third year technology (Hardware) refresh. -Subscription, Support & Warranty: • 5-year agreement (billed Quarterly or Annually) • Advanced hardware replacement service & 24/7 support • No-Fault hardware warranty -USB Docking Station Video-as-a-Service Package (quantity of 10) -Transfer Station (8 Bay) Video-as-a-Service Package (quantity of 12) -V300 Additional Batteries (quantity of 130) -Managed Software Installation Service; On-Site Assist Install, Training, Configuration, Project Management, Consultation • #2 Option -In-Car video and evidence management software (quantity 60) -Video-as-a-Service includes the cloud-based evidence management system -CommandCentral Community (evidence capture, records, and CommandCentral Community capabilities included). -Unlimited users, Unlimited storage & Unlimited cloud sharing -CarDetector Mobil_e LPR w/ Vigilant LEARN (PlateSearch) -In-Car Video System (Choice of forward camera) • Includes 200GB DVR, Control panel & Infrared cabin camera • HiFi wireless microphone kit, MiKroTik WiFi Kit & Smart Power Switch • Managed Software Installation Service; On-Site Assist Install, Training, Configuration, Project Management, Consultation • #3 Option -In-Car video and evidence management software (quantity 94) -Video-as-a-Service includes the cloud-based evidence management system -CommandCentral Community (evidence capture, records, and CommandCentral Community capabilities included). -Unlimited users, Unlimited storage & Unlimited cloud sharing -CarDetector Mobile LPR w/ Vigilant LEARN (PlateSearch} -In-Car Video System (Choice of forward camera) • Includes 200GB DVR, Control panel & Infrared cabin camera • HiFi wireless microphone kit, MiKroTik WiFi Kit & Smart Power Switch -Upload Server On-Premise (1) -Store and Forward Server for Fast Video Offload. Use with in-car upload via Access Point or Body Worn Camera Transfer Stations, On-premise deployment, 1 U rack mount, 8TB of storage, 16 GB RAM, 2x1 0G network cards, ·Intel Zeon processor, 5 year Warranty -MikroTik Configured Wireless Kit 802.11 n, Drill Mount (94) -Radio, Antenna, PoE, 2-10' Ethernet Cables, Drill Mount -MikroTik Configured Wireless Access Point (5) -Managed Software Installation Service; Onsite Assist install, Training, Managed Software Configuration, Project Management, Consultation Exhibit A: Contract Documentation Requirements 66 Cost Summary Motorola Solutions f.' May 10, 2022 Item #11 Page 443 of 604 DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 SECTION4 PAYMENT SCHEDULE A. 10% Upon Approval of Project Plan B. 10% Upon Completion of Software Installation C. 20% Upon Completion of Functional Testing D. 20% Upon Completion of Training E. 20% Upon Completion of Go-Live F. 20% Upon Software System Completion Exhibit A: Contract Documentation Requirements Motorola Solutions Payment Schedule 67 May 10, 2022 Item #11 Page 444 of 604 DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 SECTION 5 City of Carlsbad, CA February 16, 2022 PROJECT SCHEDULE AND PERSONNEL 5.1 PROJECT SCHEDULE We are providing a representative project schedule on the following pages that reflects the preliminary project scope and duration. As part of contract negotiations or project kickoff activities, the Motorola Project Manager will collaborate with the City to develop a mutually agreeable project schedule (which may decrease overall duration) that will include the final contracted scope of work and project resources (including subcontractors). Exhibit A: Contract Documentation Requirements G Motorola Solutions Project Schedule and Personnel 68 May 10, 2022 Item #11 Page 445 of 604 DocuS;gn Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAm Carlsbad PremierOtie CAO and Awar'e • Project Schedule_031022 emie,-One Cloud CAD Cloud Deployment Project Initiation and Planning Contract ~):ecution OOJ Approval Process. Project ~~J~ment Project Planning Se.ssion Project Handoti with Sales PrOJfCt -Planning Se:ssion Prem.1e,qnl! Clou~ ~O_BP~u!"'.'_'=.(!~turMd PremierOne CJoud GIS Survey Returned CJIS Requirements Defined · Pr~ject Schedule 8aselined ProJect Management Plans Completed PremierOne aoud and CommandCentrat Kickoff Meeting Kld:Off Meetin& --GIS Planning S~si~n -GIS Pl~nning Session Cu~omer Piovid@S GIS Draft Data Interface Planning S-ession lnterf"ice Planning SesslOO - Customer Provi<!E!sR"equ-ired Interface Deployment Requirements COnnectiv;ty Plarin.ing Ses.slon Customer Provfdes Base connectivity Requirements CommandCentral Aware ?tannlng Session Comm-;ndCentral Aware and l~vestigate Service OelivC!:ry A,_;,8~e Design Revi;.; --~-~ --. lnvesti{~~nst_!!l!tion ancrcredentJallng Aware Provisioning -MSf Provisioning Demonstration of Aware Pro...;:.ionin, Aware Client Installation ----· vel"ify remote access to workMatJons Configure CommandCCntral A~are client applk.ation Aware Interfaces and lntC!:gratfon N DA f{eturned (If Required) Revk!w lnter+.ice Func;tionai Description (IFO) with Customer Interface Configuration OoC\Jment lnleriice Oeve'1opment 1rltertace Functrona1 Validation. lnterrac-e Go Live fteadv· Drone Review lntegratiO·n fu0ctionali[Y (Ooud CAO, VESTA., Vigilant} Configure fntegrution Awr1,e Integration Functional Validation Aware and Investigate Functional Validation Review COO,_el!te Functiooal Valid3tion - Fu nction.l1 Validition Exteptfol\S Resolved Comelete Funr;tio,;I vaiidatlon for Ex~eptions ~~are and J-;;-vestigate' Go Live Rea<!Y _ Aware and Investigate TralnJng and Consultative Services uration 390 days 4S.days Odavs 9 mon.s 3!19_da.l'L_ 2ldays odays 1 day Q.~Y!__ - Q~ays lOdays ~Odays lOdavs 23 days l.!l•J lOdays odays lOday, ;1day_s __ 2 da'lls is days lOdays IO days 5 days 149days isdavs- 10 days 1s davs ~.l'!. 5days •i~vs lday lday 125 days lOdays ldav 1 day 30days 1 da 0 clays ldavs ,Sdays 3days 14 days ~~.l"-10days (day Odays U2lavs tMS Adm in Training 1 day End User Access co!'t:Irm~~_for LMS 0 days Aware Professk>nal CoMuk.ttive Servitel S days Investigate Profes.slonat Consultatlve Servk.a S days ~mierOne Cloud CAO/Mobile ServlCe Oel~!_ry ~ ~a~ CA_!?an~~-bile lnstaJlatlon __ _ _ ~ Customer IP Address Provlded {lAN/WAN, Subnet mask., Gateways) 1 day M(crosoft Active Olrecto,y A:r.ure Setup Mfcrosoft Active Clli"ectOfY Azure Ms1 Users Reg[stered Network Ports -Open (If Direct to lnterNet Configuration) Azure Public Edie Access CAO User Information Provided (Name/Email) PremlerOne CAO Eflvironment Sett.Jp (MSI Access Onfy) Prem!erOne Mobile Environment Sl!tup (Ms1 Access Onty) l day 1 day 1 day I day 0 days l<f!y Cloud Anchor/8,eachHead Provided Ck,ud Anchor/BeachHead lnStalled CAOdj;;;t lnstaUatKln +• -• •• CAO cii"ent installation ----L~Y 155 days CAO Cllents Ready for Installation C.Ao ctie:nt lnStallation MSI -Up to 2 Oieots CAO Client Installation Overview CAO Client lnstallotion CUS!~me~ Mobile Client Installation -Mobtte-Client Installation o~rview-Up 2 dii nts · Remote Mobllc_Client Installation. Remaining GIS Gl~~~a ora"°ft v-;,fficatlon Report Completl!d GIS Boundaries Meeting AE,ency Code and Beat Names Finalized GIS ChttkPOlnt Meetings GIS Checkpoint Meeting #1 -Ad<1essing Validation, Routing and Boundaries Customer GlS Oata Revised and Provided GiSCh-edcpo1nt Meeting #2 ·• R@adin"ess for GIS load 106 days '2day< 1 do'II 1 day ~~ays ~l day< l clay 3Qd•l'S_ ~d~ys 2 days 0davs Odays 62 davs 2 davs 2 days I clay Pag@1 tl<t inish Wedl/30/22 Tue 9/26/23 Wed3/30/l2 Tuo 5/31/22 Wed 3/30/22 Wed 3/30/22 Tue 4/26/22 Mon 1/2/2l 'N•d 3/30/22 Tue 9/~§/_2}_ Ftl 4/8/22 Mon 5/9/22 Fri4/8/22 Fri 4/8122 Mc,n4/2'5/22 Mon 4/25/22 Mon 5/9/22 MM'jl9/'Q_ -Mon-5/9/22 Mon 5/9/22 Tue 4/26/22 Mon 5/g/22 Tu• 4/26/22 Mon 5/9/22 Tue •h.6/22 Mon 5/9/22 Thu 5/5/22 Mon 6/6/22 Th_u S[Sf22 T_oo S/5/'Q_ 'f'On5/16/22 Mon 5/30/22_ Mon S/16/22 Mon S/16/22 Tue 5/17/22 Mon 5/30/22 Frf5/6/ii Fri 5!6/22 M.J~/.!Qf22 __ Tue 5/10/22 Mon 5/9@. Mon 5/30/l2 Tue S/10/22 Mon S/23/22 Tue 5/24/22 Mon 6/6/22 r:u~ 5/2_4/22 Mon 5/30/22 f!i s/6/I2_ W__!?d ~ljWl_~-- Fri 5/6/22 Thu5/],6/22 F,J 5/6/22 Thu 5/19/22 ~u7f~_lfil Wed-8/10/22 Thu 7/21/22 Wed 7/27/22 Thu 8/4/22 ~~~1i_oji2 Thu 8/11[2], Fri 8/12/22 'Thu 8/11/22 Thu 8/11/22 fri8/12/Z2 Fri 8/12/22 Tue S/10/22 Mon 10/31/22 !LI• }/10/22_ Mon 5/23/>l 'Thu 6/2/22 Thu6/2/U '-• wod6/15/22 Wed_ 6/lS/]J ThuffiW2 \\red 8/3/22 !hu8M[l2 Thu 8/11/22 Mon 10/31/22 Fri 6i3/22 Mon JcO]E/p. Tue 6/7/22 Wed 6/8/22 Tue 6/14/22 Wed 6/15/22 Frl6/17/22 F<lll/4/22 Wed 11/23/22 t<!_Jl/4/2,2 Tue 11/8/22 _ Wed 11/9/22 Tue 11/22/22 Wed 11/23fl2 W~d 11i23/22 •Wed 11/23/22 Wed 11/2}/22 Tue6/28/22 Wed 11/30/22 Tue 6/28/22 Tue 6/28/22 Tue 7/5/22 Tue 7/5/22 Thu 11/24/22 Wed 11/30/22 Thu 11/24/22 Wed 11/30/22 l_~!_S/10/22 W•d S}l;/23 'Tue S/3lf12 Fri_6/l/2_2 ___ Tue 5/31/22 Tue 5/31/22 Tue 5/31/22 Tue-S/3-1/22 Tue 5/31/22 Tue 5/31/22- 'Tue 5/31/22 TueS/31/22 Tue S/31/22 Tue 5/31/22 Tue 5/31/22 Tue 5/31/22 Tue S/31/22 Tue 5/31/22 Wed6/1/22 Wed 6/1/22 Thu 6/2/22 Thu 6/2/22 Fri 6/l/}-2 ___ Fri 6/3122 _ Wed 6/8/22 Tue 1/10/23 w-;;i•fihi Wed 11/2/22 Wed 6/8/22 Thu 6/9/22 Fri 10/28/22 Fd 10/28/22 Mon 10/31/22 Mon 10/31/22 Tue 11/1/22 W~d l!}J,{J],_ Tue 1)/3_9/23_ _ J~!(l/2~ Tue 11/19/22 Tuo 11/29/22 Wedll/30/:,Z Tu.S/10/22 Fri6/1o;i2 TueS/1iif22 Tue 5/10/22 Fri 6/24/22 Fri6/24/22 Fri 7/8/22 Tue-77i9/22 Tue 1/10/23 M-on9/19/22 Mon 6/13/22 Tue 5/10/22 Tue S/10/22 Mon 9/19/22 Mon 6/27/22 _ ¥9'!.?/11/22 Tue 7/19/22 May 10, 2022 Item #11 Page 446 of 604 DocuSlgn Envelope 10: EEOOO0EC-B190--469F·887C-147EJBCE,',FF7 Carlsbad Pr@f"r'lierOM CAO and Aware • Project Sch~ule_031022 D ask Name Dlrotlon "" F'.-.ish GIS Draft Geobatabase load 1 day Wed 7 /20/22 Wed 7/2.0/22 GIS Import Training 3 days Tue 8/2/22 Thu 8/4/22 Grs CheckPoint Meeting #3 -Customer GIS Load Review 1 day Fri 8/12/22 Fd 8/12/22 GIS Checi<polnt Me€ting ~4 ~ General Check-In Meeting 1 day Wed 8/31/22 Wed 8/31/22 GIS Che-dcpolnt Meeting 1'5 • Go Uve Readiness 1 day MonJ£1~/21 Mon 9/19/22 GIS CAO and Mobile Go Live Ready O_d~ys Mon 9/19/22 Mon 9/19/22 CAD and Mobile Business Process Review 34 days Tue.s/10/22 ~rl 6£24L22 8PR Su~y Review Sessl~n idaY Tue 5/10/.22 Tue 5/10/22. PremferOne CAD Agency Guide Review 1 day Wed5/ll/22 WedYll/22 (AD and' Mo~\te Bus)ne~s Proccs.s Revic~ ~ssion 3 days Tue 6/14/22 Thu 6/16/22 Customer ProvldC:S BPR information Odays Tue 6/14/22 Tue 6/14/22 CAO and Moblle Bus1nes.s Process Workbook Review Session 1 day Fri 6/24/22 Fri 6/24/22 ~O and Mobile Provlsionl_!IS,_ --•~~VJ Th'°.2/1/li Mo~J".m [?l__ SA_? P,!ovisr~n~,:ig 41 days Thu 9/1/2~ Thu 10/27/22 R~vi~w Provisioning Databases 1 day ThuJ/1/12 Thu 9/ih2 - Customer Provides Completed Provisioning Worksheets tOdaY$ Fri 9/16/22 Thu 9/29/22 MSI Pro~sionin°g io<1avs -Fri 9/30/22 ~T~ !O/il/2] oenlorinr"ation of CAO Provisioning s days Fri 10i21/22 Ttw 10/27 /22 Mobile [Wil'Nlows, Android/iOS) Provisk>ning 2days Frffolis/22 Mon 10/31/22 MSI Moblle Provisioning $(!sst0n #1 (2 Hr) lday Fd 10/28i22 Fri 10/28/22 MSI Mobile Ptovisioning Session #2 (2 Hr) lday Mon 10/31/22 Mon 10/31/22 MSI M_obile Provisioning Sessk>n #3 (2 Hr) ldav FrlJ,D/18/22 M 10/28/22 MSI MobUe Provisioning 5essM>n #4 (2 Hr) l~~V Mon 10/3!/22 Mon 10/31/22 CAO and Mobile Functional Validation Review 29days Fri 10/28/22 Wedl_2/7_fl2 CAO Functional Validation Review 29 davs Fri 10/28/22 Wed 12/7/22 Provide Funetio~al va}ida_tion Scripts Odays Fri 10/28/22 Fri 10/28/22 fof!l~!te F_unctional Validation ~ ~!YS FrlJ!/'.'.(22 '!:!_e.?:!f8/2_2 __ Custome.--led SceniilriO Validation 20days W<d 11/9/22 Tue 12/6/22 FunctlOnal-Valid"itionfxceptions Resolved 20days Wed 11/9/22 Tue 12/6/22 ~mp_l.e.tf? Fun.~to0.1I Vall_dation f~r ExceP.tions 1 da.y Wed 12{1/2l Wed 12/7/22 CAO Go Uve Reacfy odavs Wed 12/7/22 Wed 12/7/22 Mobile (Windows, Android/IDS) Functional Validation Revlew 20 diy5 Mon 10/31/22 Mon 11/28/22 ~~~.E_~Fu_nctional VilKfation Scripts Q~~ys M_2,n1om/22 !'On l_0fil!32 Comptete Functional Validation 3 day.s Wed 11/9/22 FriJ.1/_!}~~ Functional Validation Exceptions R~olved lOdays Mon 11/14/22 Fri 11/25/22 Cotnplete Fur.ctional Validation for Exceptions 1 day_ Mon 11)28/22 Mon 11/2.8/22 -~-~ob~~~Live Ready O__!I!~-· • M~1/2Y32 M~n llf~.l- CA~and Mobil~/HH P!~_v.!!!_~ning Workshop ~14 days Wed7/6/22 Mon 12/12/22 CAO LMS Provisioning Workshop freReq Courses Completed 3 days Wed7/6/22 Fri 7/8/].2- CAD/MobHe/HH Provisioning Workshop Sessions Complete 3 days Thu 12/8/22 Mon 11./12/22 _CAD C~O!n,_er ProvisionJ_ng Owner Transfer Q.<f!ys MQn 12/12{22 Mon 12/12/22 ~~-~Orting ~<lay Tue12flH 22 Tuel ~£13/E Motorola Provides Access to CC Rce,orti;.g ldav Tue_l2/l3m._ _ }ue 12/13/p,. Motorola Provides Access to ROW In the Cloud ~d~y. __ Tue 12/13/22 Tue 12/13/22 CAD lnt(!t'faces 2)]d.•ys _ Tue s7ioh2 Wcd4/S/23 _ ~ ln~~ce • State Que"'{ (NCIC/NCIC) ~11.fil'Y' Tu• S/J0/22 Mon 9/12/22 _ Define State CenificatlOn Requirements/Process/ Provide 4Sdays Tue S/10/22 Mon 7/11/22 Documentation Review lnterfuce Functlol'\al Description (tFO) wlth Customer 1 day Tue 7/ll/22 Tue 7/12/22 Interlace Configuration Document l day Wed 7/20/22 Wed 7/20/22 132 State TCP Protocol Connection to Pl CAO provide<:! (IP Address/Port) l day Tue 7/26/22 Tue 7/26/22 B3 Erlte"r "User, ORl's, Device tdentlflers (Mnemonlc:s}into Pl 1 day W~7/27/22 Wed 7/27/22 CAD/C(!mmsys ,,., CAD Provisioning with Customer -command Line-User l day Thu 7/28/22 Thu 7/28/22 Access/Permissions-Incident (Person/Vehicle) Trigger-Query Response Formatting • Workstations ~tructured Response Services •Hot Hit:s Mobile Provisioning 1 day Frl 7/29/22 Fri 7/29/22 Interface Functional VaUdation CAO 1 day Fri 7/29/22 Fri 7/29/22 al Valtdation ~obikl l day Mon 8/1/22 Mon 8/1/22 30 ~~-T,;e 8/2/22 ____ Mon 9/12/22 eady • State Query odays Mon9/12/22 Mon 9/12/22 1 ANI/ AU, TDD 11~ days Tue 5/31/22 Monio[n/i2 NO!, R~~rn~ (!_! R~ulr~d) 1 dav Tue 5/31/22 'Tue 5/31/2_2 Review Interface Functional Description (IFO) with Customer ldav Wed 6/l/i2 Wed6/1/22 Lantronlx/FortlGate/flrewall Provided lday Tue6/2lf22. Tue 6/21/22 Lantronhc/FortiGatt/Firewall Installed lday Tue 6/21/22 Tue 6/21/22 Interface Configuration Document Sdays Fri 10/14/22 Ttw 10/20/22 FSA Mapping Sdai,is Fri 10/21/22 Thu 10/27 /22 Pl CAO Provisioning -Phone Position/CAD Mapping 1 d"' Fri 10/28/22 Fri 10/28/22 ··-Interface Ful'K'tlonal Validation ; day Mon 10/31/22 Mon 10/31/22 Interface Go live Ready• NG911,TOD Odays Mon 10/31)22 Mon_ 10/31/22 CAD Interface· Records CFS Feeds (NetRMS, Spldr Tedi, Axon I 125 days Tue S/10/22 Mon 10/31/22 . NOA RetWned (If Required) tOda~ rue sfiol2_2 __ Mo~ S/lV22 Review Interface Functlonal Descriptions (IFOs) with Customer 3 days Thu 6/2/22 Mon 6/6/22 Interlace Configun1tion Document 3 doys Fri6/l7/2.2 Tue 6/21/22 Interface Development 30 days Wed6/29/22 Tue 8/9/22 Interlace Functional Validation 3 days Wed8/l7/22 fri 8/19/22 156 Interlace GO Live Aeady • NctRMS, Spidr Tech, Axon o days Mon 10/31/22 Monl0/31/22 Page2 May 10, 2022 Item #11 Page 447 of 604 DocuSign Envelope ID: EEOOOOEC·B190-469F·887C.1◄7E3BCEAFF7 Car1~ Premfe,o.,e CAD and Awa,e -ProjKt Sc:hedule_0310:c?2 IS7 CAO Interface -lncldent Creation One-Way Inbound (DORS, Vigilant) NOA Rt:turned (lf A:equired) Review rnterfac~ functional Descriptions (IFOsl with Customer 107 days 10 days 3 days lntemice Configuration Oocument 3 days l'!!erf-a~ Oevel~f!!-~nt -·60 days Interface Functional Valldatfon 3 days lnterfaO'.! Go Live Ready -DORS, Vigilant O d.iivs CAD Interface -Qu;rv l~terfaCes =taserfiche, Vigilant LPR, Legacy Data 112 days Query, Oossroad5 Accident, Crossroads Citation, OORS, QueTcl NOA Returned (If Required) Review Interface Funetlonal Descriptions (IFOs) with Customer rnterface Cot1~,a:uration Document Customer Enterprl.5e Network Connections to CAD CAO Provisionine with ~om·er .ccmmand Un~-User Access/PermJSsjons-Trlgger-O.ue:ry Response Formatting lntertate 0@velop,nent Interlace Functional Validation lnternlce Go-Live Ready -luerFiche, vtgllant LPR, Legacy Data Query, Crossroads Accident, C:rosstoads Citation, OORS, Q~Tel CA~~d Mobile Training g o-.Learnr!'i MJ~&en:!~nt~!uti«?!!._(~~) _____ _ LMS Admin Training End User Access confirmed for LMS Pr~mierO~CC~o Tr~;-the-TralMr LMS Pr~R~qs __ _ PremierOne CAO Train-ttie-Tri:llner Course _ P_!!,mierO!:Je CAO E11d User Training (6-Classes) Pre:mie_'9ne Mobile Tr~lning_. . PremierOne Mobile Train-the-Trainer (Police) PremierOne Mo~le Train-the-Trainer (Fire) P,emierOne Mobtle End User Training (CUSTOMER LEO) CAD~Mobile Go Ll~ CAO and Mobil;: Go -Live Re.idy PCutOVcr Pl°an -- e ChedUst/Prep e Event-S~bscfption St~ _G_o_l~~uPe_Ort (3 diys) ive Remote Support Mobile Support Engagement Engagement Meeting r SupPOrt Plan Review ndOver co;'..,l.ete lOdays 7 days lOdays 7 davs 7 days 90days 7 days 1 day 171~v_s 171 days. ldoy Odavs s4-da~ l ~~V 4 days 30davs 32 days ldoy 1 day 30days 40~ o days s·,i,ys lOdays 1 day ]days 30-edavs 31days l day 1~ l da'-,1 oda Page 3 Swt Finish Tue 5/10/22 Wedl0/5/22 Tue 5/10/22 Mon5/'l3/22 Tue 6/7/22 Thu 6/9/22 Wed6/22/22 Fri 6/24/22 Mon 7/4/22 Fri 9/23/22 Mon 10/3/22 Wed 10/5/22 Wed 10/5j2,2 Tue11/l/ll ~d_ 10/j/2_2_ Wed4/5/23 Tue 11/1/22 Mon 11/14/22 Tue 11/1/22 Wed 11/9/22 Thu 11/10/22 Wed 11/23/22 Tu• 11/1/22--Wed 11/9/22 Thu 11/10/22 Fri 11/18/22 Monll/21,hi M<m3/27/i3 Wed4/5/23 Tue6/Ujll Tue 6/U/22 Tue Giisfff Tue7M2 Thu12/8/U Thu 12/8/22 Tue 1/3/23 wed1/lli23 Mon 119/23 Mon 1/9/23 Tue 1/10/23 Wed 1/11/23 Wed 4/5/2} w_ed_4/W3 Thu 4/6/23 Thu 4/33/23 Thu 4/i7 /23- Thu 4/27.i23 MonS/1/23 Fri 3/i?/23 Fri 3/17/23 Mon 3/27/23 Fri 4/28/23 WedS/31/23 Fri3/24/23 Tue 4/4/i3 Wed 4/5/23 Tue2/21/23 Tue 2/21/23- ~<!6/28/22 Tue 7/5/22 Tue 2/21/23 Thu 12is/22 Fr'o°l/6/23 - Tue 2/21/23 Tue2/21/2r Mon 1/9/23 Tue 1/10/23 Tue 2/21/23 Wed 5/31/23. 'wed4/5/23 'wed 4/12/23 Wed4/26/ii -Thu 4/27/23 Mon 5/lii3 Wed 5/31/23 Fti 4/28/23 Fri 3/17/23 M~n ~/27/~3 _fri3fl_8/J} Wed 5/3 23 May 10, 2022 Item #11 Page 448 of 604 DocuSign Envelope ID: EE0000EC-8 19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 5.2 PROJECT PERSONNEL Resumes of Project Personnel are on the following pages Full responsibility for the successful completion of the project implementation in accordance with the approved scope and schedule. • Deploy PMP principles and methodology in project deployment process through inputs, tools techniques and outputs for integration, scope, time, cost, quality, human resource, communications, risk, procurement and stakeholder management • Drive strategic relationships between internal teams through assembling needed knowledge, skills tools and techniques. • Manage project budgets, implement metrics by maintaining data, mentoring, monitoring activities, being directly involved in troubleshooting, adhering to reporting requirements, escalate issues, through communication and collaboration; · • Fully define customer deliverables and needs: schedule, scope, and financials with detail, focused during planning through communicating regularly and providing field oversight; • Cultivate strong third party relationships through collaborating, negotiating adjusting and developing solutions to meet customer's satisfaction and acceptance • Negotiate and communicate project deliverables, scope, and expectations, and progress to the Senior Leadership Team • Meet financial objectives by forecasting and estimating project work efforts • Manage stakeholder satisfaction through collaboration, open communication, develop scope adjustment, training, adhere to schedule, and budget constraints Proiect and Related Professional Exoerience Motorola Project Experience • Alhambra PD, CA-Flex CAD, Mobile, and RMS • Kingman PD, AZ -Flex CAD, Mobile, and RMS • Norcross PD, GA -Flex CAD, Mobile, and RMS • Oswego County SO, NY -Flex CAD, Mobile, RMS, and Jail • Gem County SO, ID -Flex CAD, Mobile, RMS, and Jail • Atascosa County SO, TX -Flex CAD, Mobile, RMS, and Jail Exhibit A: Contract Documentation Requirements 4' Motorola Solutions Payment Schedule 69 May 10, 2022 Item #11 Page 449 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 The Solutions Architect is responsible for the delivery of the technical elements of the solution, confirming they _meet contracted requirements. The SA is engaged throughout the duration of the delivery. Implementation-related responsibilities include: • Leads technical review of contract design • Confirms the system design meets contractual requirements • Participates in network planning and design with customer and system/information technology group(s) • Implements interfaces • Validates functionality and integration with 3rd party applications • Provides primary support for the system Go-Live which covers interfaces, data feeds, query responses. Project and Related Professional Experience Recent Motorola Project Experience: • St. Johns County, Florida, Fire Rescue o PremierOne CAD Implementation (2019-2020) • City of Cayce, South Carolina o PremierOne Cloud CAD Implementation (2020) • Hampton County, South Carolina o PremierOne Cloud CAD Implementation (2020) • Lauderdale County, Alabama o PremierOne Cloud CAD Implementation (2021) • City of Boynton Beach, Florida o PremierOne Cloud CAD Implementation (2021) • St. Lucie County, Florida o PremierOne CAD Implementation (present) Related Experience • Hexagon (Formerly Intergraph) -1996 -2017 o Executive Manager -2014 -2017 o Senior Technical Manager -2011 -2014 o Senior Technical Trainer/System Consultant-1996 -2011 • Dauphin County, Pennsylvania, Department of Public Safety o Telecommunicator/Supervisor/lnformation Technology Manager 1985-1 996 • 32 years of volunteer/paid-on-call fire and EMS service (1984-2016) Exhibit A: Contract Documentation Requirements G Motorola Solutions Project Schedule and Personnel 70 May 10, 2022 Item #11 Page 450 of 604 OocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Lead Application Specialist responsible for implementation-related activities: • Conduct Business Process Reviews to collect information on current processes and workflows to aid in system provisioning, • Work with customers to develop training strategies and plans and deliver provisioning and functional training courses, • Create and modify documentation including lesson plans, workbooks, instructional activities and course documents. • Provide "Go Live" support. • Prepare written reports, documentation and participate in customer meetings. • Troubleshoot software anomalies during provisioning and training • Provide application and administration support for project team Professional and Project Experience Motorola Project Experience: • City of Nashville, TN Police and Fire • Las Vegas Metro Police • Indianapolis, IN Metro Police and Fire • Peel Police (Ontario,CN) Related Experience • Aurora Public Safety Communications -2006 -2016 o Telecommunicator Specialist o Telecommunicator Trainer • Airlife Denver -2010-2011 o Flight Dispatcher Exhibit A: Contract Documentation Requirements G Motorola Solutions Payment Schedule 71 May 10, 2022 Item #11 Page 451 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 M.S. -GIS Technology B.A. -Computer Science University of Arizona Weber State University City of Carlsbad, CA February 16, 2022 Combat Engineering School, Airborne School, NCO School US Army and Utah National Guard Responsibilities in Current Role • Participate in the project kickoff, planning, installation and support of mapping/GIS for Premier One • Assist public safety agencies with GIS implementation as part of Computer Aided Dispatching systems implementation including gathering data requirements for ArcGIS, planning, and creation of the Geodatabase used for dispatch • Train users in GIS products used with Motorola's PremierOne system • Work with customer support, product management, technical services and the business analyst group to troubleshoot trouble tickets, identify root cause and communicate user stories in a technical manner Professional and Project Experience Recent Project Experience: • GIS Lead for the following projects: o Tioga & Oswego County Sheriffs office(s), New York o Cowlitz 911, Washington Related Experience o GIS Analyst Ill -Flex Support (2016-2021) . o Support Technician -Spillman Technologies (2005-2016) o Skilled with ESRI suite of products including ArcGIS Pro, Arc Desktop, Arc Enterprise • Technical skills in C, C++, Java, Perl, Python, Windows Server, Linux Exhibit A: Contract Documentation Requirements fl Motorola Solutions Project Schedule and Personnel 72 May 10, 2022 Item #11 Page 452 of 604 DocuSign Envelope ID: EEOOO0EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 The Solutions Architect is the post-sales technical lead who oversees the implementation and support of the CommandCentral solution from project initiation to system acceptance. • Network planning and design with customer and system technology group. • Prepare and execute network component health checks as well as on site final system acceptance test plans. • Design and document interfaces to integrate the Motorola products with other systems. • Review requirement documents with the customer including work flow and system expectations. • Deploy interfaces to 3rd party systems • Provide primary support for the system Go-Live which covers interfaces, data feeds and query responses. Professional and Project Experience Motorola Project Experience: • Glendale PD, AZ • Boca Raton PD, FL • Boynton Beach PD, FL • City of Lansing, Ml • LVMPD, NA • Mont ome Count , TX Exhibit A: Contract Documentation Requirements G Motorola Solutions Payment Schedule 73 May 10, 2022 Item #11 Page 453 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 SECTION6 PRODUCT VALIDATION 6.1 PRODUCT VALIDATION PURPOSE The purpose of this document is to describe the processes that will be used to verify the PremierOne Cloud CAD and Mobile System. This document provides the plan that describes the management, conduct, and reporting activities of product verification. All verification criteria will be predicated by the contract exhibits and Motorola's responses to Customer requirements in the RFP. Functional validation will be conducted only on those features and functions for which PremierOne Cloud CAD and Mobile have been provisioned. 6.2 VERIFICATION PROCESS OVERVIEW This document details the steps that Motorola and the City will follow to prepare for and conduct the functional, interface and integration validation of PremierOne Cloud CAD and Mobile. This process will focus on demonstrating those features and functions to which Motorola complied in the RFP response and that are enabled on the City's PremierOne Cloud CAD and Mobile system. Motorola will provide a set of specific scenarios which will be performed on the PremierOne CAD and Mobile. Additionally, the expected results for will be documented. These scenarios and their expected results will be delivered to the City for review, and once approved, will form the set of validation scenarios that will be performed. The functional validation will be performed once the application is installed at the City's facility and Train the Trainer training has been conducted. City personnel will witness the functional validation and observe and acknowledge the res·ults. In the event that the observed results do not agree with the documented expected results, an exception/failure condition will be recorded. A resolution plan for exceptions/failures will be developed in order for the City to accept the system. 6.3 VALIDATION PROCESS ACTIVITIES The activities that will be followed in the validation process are detailed in the sections of the document below. 6.3.1 Prepare Functional Validation Plan A detailed functional acceptance test plan will be prepared by Motorola for the customer. This plan will concentrate on testing the features and functions of the system that will be used by the customer and will not test areas of the system that Motorola did not comply with in the RFP response and for which provisioning was not completed (i.e. features or functions that are not applicable to the City's operations). The validation plan will be organized as a set of scenarios, with each scenario being broken into one or more use cases. Exhibit A: Contract Documentation Requirements 74 Product Validation Motorola Solutions 0 May 10, 2022 Item #11 Page 454 of 604 OocuSign Envelope ID: EE0000EC-B190-469F-887C-147E3BCEAFF7 6.3.1.1 Scenarios City of Carlsbad, CA February 16, 2022 Scenarios are high-level, cross-product workflows of the system. These scenarios are described from an end-to-end user perspective. Scenarios focus on the user domain information, but also describe the high-level functional interaction between PremierOne CAD and Mobile. 6.3.1.2 Use Cases 6.3.2 6.3.3 6.3.4 6.3.5 Use Cases are the decomposition of Scenarios into specific user and product functional interactions required to execute a task. Use Cases define the success oriented scenario and key exception cases. Note that several Use Cases may be required to execute a particular Scenario. Use Cases define functional interaction between products; specific messages and message sequence between products are defined in Interface Control Documents. Prepare Interface Validation Plan Motorola will develop validation plans that demonstrate that interfaces and integration operate in accordance with the approved Interface Functional Descriptions. Where appropriate, the functional validation scenarios will incorporate interface functionality. Motorola will also document the means by which integration between the Motorola primary system components will be tested and verified. Validation Plan Approval The Validation Plan will be reviewed with the City and formally approved. Validation will not begin before the Validation Plan is approved. Validation Execution Execution of validation procedures/cases will be conducted in an orderly manner. They will be performed as described in the Validation Plan and each action and result will be properly verified by City-designated personnel. The results of each scenario will be recorded as a pass or failure and the specific details of any failures will be recorded. System configuration will be controlled throughout the execution of the Validation Test. At the start of the period, all provisioning and configurable items will become the baseline, any subsequent changes will be configuration controlled to ensure consistency in the testing processes. A configurable item, with respect to the customer's system environment, is defined as any document, software application, or hardware component integral to the installed system. Validation Failures All failures identified during validation phases will be recorded in Motorola's defect tracking system. Each failure will be assigned a severity level to allow the team to prioritize their handling of the failure. The severity levels that will be used are those defined in the Maintenance and Support and Agreement. Exhibit A Contract Documentation Requirements 0 Motorola Solutions Product Validation 75 May 10, 2022 Item #11 Page 455 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Since there is some subjectivity in determining the level of severity and impact, it is critical that several perspectives are considered when the assignment of a failure's severity is made. Therefore, the determination of severity will be made by a cross-functional team containing both Motorola and the customer representatives. A resolution plan will be developed that identifies the action(s) that were taken or will be taken to address and/or correct the failure and the method by which the corrected function will be retested. 6.4 SAMPLE FUNCTIONAL VALIDATION WORKBOOK A sample Functional Validation Workbook has been included as a separate Excel Document. This is an electronic document, v.4.6.x.x. Exhibit A: Contract Documentation Requirements 76 Product Validation Motorola Solutions G May 10, 2022 Item #11 Page 456 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 SECTION 7 City of Carlsbad, CA February 16, 2022 HARDWARE AND NETWORK SPECIFICATIONS 7.1 PREMIERONE CLOUD HARDWARE AND ENVIRONMENT 7.1.1 General Hardware and Environment Requirements The Customer will provide hardware and/or an environment that conforms to the following general requirements: Customer Responsibilities 1. Supply hardware, operating system software, third party components, and other elements not speci_fically identjfied as being provided by Motorola. 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. Provide IP addresses on the Customer's network for the required on-premise equipment (i.e the Anchor Server). All server names and IP addresses behind Motorola Firewalls cannot be changed. · 5. Provide external interface connection demarcation points at locations agreed to by Motorola. These locations shall normally be adjacent to the cloud interface appliance. 6. Provide access, administrative or otherwise, to appropriate systems, locations, information, tools, and equipment to ensure proper connectivity, installation, operations, and maintenance of the service. 7. 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. 8. Provide 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. 9. 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 cloud interface Anchor Server appliance. It is understood that remote access to on-premise server and Customer's network must be supervised, which supervision will be provided. Customer-provided high-speed internet access with a minimum of 10 Mbps is required at the time of project kickoff and must remain available to Motorola throughout warranty and support periods to accommodate remote support of the service. In the event that dedicated links are required, a minimum of 7.5 Mbps upload and download access is required. It is the Customer's responsibility to ensure that the aforementioned capacity is available. In the event remote broadband access is Exhibit A: Contract Documentation Requirements G Mot~ro/a Solutions Hardware and Network Specifications 77 May 10, 2022 Item #11 Page 457 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 7.1.2 7.1 .2.1 not available to Motorola preventing us from delivering the contracted service remotely, Motorola will provide service on-site at additional cost. The additional cost will be presented to the Customer via the change provision of the contract prior to the delivery of the on-site service. 10. 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 central server for maintenance and updates, the connectivity including ports and access needs to be provided. Component Specifications Motorola will provide Commsys Connect CIC. The Customer will provide the server hardware and firewall devices ... PremierOne Cloud Anchor Hardware Customer Responsibilities 1. Provide, install and configure server hardware, operating system software, VMWare, firewall devices, Lantronix External Device Server and SQL Standard. Specifications will be provided at the Planning Meeting. · A. Provide a VMware host environment capable of supporting two VMs. i. Windows ServerVM, 4vcpu, 16GB RAM and 3 HOD 120/120/25GB ii. Linux VM, 2VCPU, 8GB RAM and 1 HOD 20GB B. Verify the VM has connectivity to the internet and the following addresses, which are commonly used by CloudConnect: -https://idm.imw.motorolasolutions.com (443) -IDM -https://aware-api.usgov.commandcentral.com (443) -Ingest -https://admin-api.usgov.commandcentral.com (443) -Admin -https://aware-publisher-ws.usgov.commandcentral.com (443) -Publisher (WebSocket) -https://registry.commandcentral.com (443) -Registry -https://oneinterfaceblobstore.blob.core.usgovcloudapi.net/(443) -lmageNideo upload -Additional Endpoints For IMW/LRRP Interfaces -https :/ / ccinterfaces-ccbroker-prod. usgov. commandcentra I. com/api/ ccinterfaces- ccbroker (443)-IMW/LRRP -https://ccinterfaces-sasgen-prod.usgov.commandcentral.com/api/sasgen (443) - SAS Token -https://qrwbubhpaovhj-sbu.servicebus.usgovcloudapi.net (443) (Websocket) (inbound-outbound) Motorola Responsibilities 1 . Provide the CloudConnect VM image to Customer. 2. Remotely support installation of VM image on Customer hardware. Exhibit A: Contract Documentation Requirements 78 Hardware and Network Specifications Motorola Solutions G May 10, 2022 Item #11 Page 458 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 7.1 .2.2 CommSys Connect CIC 7.1.2.3 Motorola Solutions Responsibilities 1. Provide CommSys Connect CIC. PremierOne Cloud CAD Local Workstation The Customer will procure and provide local (fixed) workstation hardware that conforms to the requirements laid out in this section. • Windows 10 operating system. • Monitor(s) -two or three with recommended resolution 1920 x 1080 (per client preference: i.e. three for CAD dispatch, two for CAD call taker, etc.). • QWERTY Keyboard with 12 function keys 7.1.2.4 Records Client Workstation Requirements • Browser compatible with Citrix Virtual Application. Chrome, Internet Explorer, and Edge are examples of compatible browsers. The PremierOne Provisioning Console requires use of Internet Explorer. 7.1.2.5 PremierOne Cloud Field Workstation The Customer will procure and provide field (mobile) workstation hardware that conforms to the requirements laid out in this section. • Android smartphones and tablets with Android 8 -10. • iPhones and iPADs with iOS 11 -13. • Windows laptops and tablets with Windows 10. 7.1.2.6 PremierOne GIS Workstation The Customer will procure and provide GIS workstation hardware that conforms to the requirements laid out in this section. • Android smartphones and tablets with Android 8 -10. • iPhones and iPADs with iOS 11 -13. • Windows laptops and tablets with Windows 10. 7.1.2.7 CommandCentral Aware Workstation The Customer will procure and provide Aware workstation hardware that conforms to the requirements laid out in this section. • Processor-Intel Xeon 6136 @3.0 GHz (12 cores). • Memory-32 GB. • Drive-One NVMe 512G SSD. • NIC-1 GB port NIC. • OS-Windows 7 Professional or Windows 1 O Pro. • Graphics Card-NVIDIA Quadro P2000 • 27-inch Narrow Bezel IPS Display, 2560X1440 Exhibit A Contract Documentation Requirements f1' Motorola Solutions Hardware and Network Specifications. 79 May 10, 2022 Item #11 Page 459 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 7.1.3 7.1.3.1 7.1.3.2 Network and Other Environment Specifications Unless otherwise stated in this SOW, the Customer will provide a network environment that conforms to the requirements laid out in this section. The Customer will provide an environment sufficient to support the transaction volume generated during Customers peak operational periods. Network Connection Requirements PremierOne Cloud client connections must meet the following requirements: • Stable internet connection. • Small Jitter (packet delay variation) -below 200ms, recommended <30ms. • Small Ping roundtrip time -below 1 00ms, recommended <20ms. • Small Packet Loss -no more than 1 %. • Bandwidth: 1 Mbps per fixed client (will vary with specific usage). • Provide cloud connectivity services for desktop CAD user clients per specifications. • Provide for outbound Internet connectivity initialized by Cloud Anchor Server. Multiple paths .are preferred for the PremierOne Cloud CAD Service. ISP connectivity to the Azure Public Edge is required for the CAD client connectivity. Interfaces to on-premise systems use a VPN device that requires connectivity to the Azure Public Edge. The Customer is responsible for providing all connections to the cloud. Mobile Network Requirements PremierOne Mobile functionality is designed for 3G and high-end 4G networks. 3G network connectivity is required, but faster 4G connectivity is highly recommended. The Customer will provide a 3G/4G wireless network infrastructure and connectivity with routing between the Mobile clients and the cloud that meets or exceeds these minimum requirements. Customer Responsibilities 1. Supply Mobile Device Management (MDM) software for Handheld devices. 2. Supply Mobile Device Management (MDM) software for Mobile devices, as desired by the Customer. 3. Provide wireless connectivity for mobile clients to the Azure cloud. Optimal application performance on mobile workstations requires 4G connectivity. 7.1.3.3 Aware Network and Bandwidth Requirements • Two (2) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Virtual Machines. • Three (3) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Server. • One (1) network port for each VMS server. • One (1) network port for each VMS analytics appliance • Provide network ports that are 1 GB capable and network mutable. Exhibit A: Contract Documentation Requirements 80 Hardware and Network Specifications Motorola Solutions tJ.l May 10, 2022 Item #11 Page 460 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 • Minimum bandwidth needed between the Cloud Anchor server and the CommandCentral Aware platform is 1.1 Mbps. City of Carlsbacl, CA February 16, 2022 • Low latency is critical for real-time operations. The speed with which data appears on the Aware display depends in large part on how quickly the information is presented to the Aware interface. Major contributors to the latency are network delays and the delay time from occurrence of an event to when that event information is presented to Aware from the source application (i.e., CAD, AVL, ALPR, etc.). Consequently, although the Aware strives to provide near-real-time performance, Motorola provides no guarantees as to the speed with which an event (or video stream) appears on Aware once the event is triggered. 7.1.3.4 Vigilant LPR Requirements Bandwidth requirements: • 1 Gbps hardwire switched network between the Vigilant server and Cloud Anchor. • Upload of ALPR data to the LEARN backoffice requires approximately 350 Kbps for each scan per second. Depending on maximum scan volume, the maximum bandwidth may need to be adjusted. • The RTSP video feed from cameras requires a 1 Gbps hardwire switched network device to allow for data communications exceeding four connected cameras. Firewall requirement: • CommandCentral Aware Workstation needs access to the IP addresses of Cloud Anchor and Vigilant server. Access to Cloud platform endpoints. • Ports that need to be open-TCP 80, TCP 443, TCP 3310 (or custom SQL Database Engine listening port that might have been configured for security reasons). • The basic service requirements of the system through a firewalled environment consist of: HTTPS web based calls to a cloud back-office solution (LEARN) with S3 image storage. Typically, through a mobile broadband endpoint. A local IP listener for RTSP video stream is used from cameras with TCP communications. • Ingress requirements (firewall traffic in): For Wireless Broadband we require TCP port 443 to communicate with the LEARN server backoffice to receive acknowledgement responses from the client. Camera Communications: TCP port 2000, 3000, 4000, 5000 (LAN/DSP). • Egress requirements (firewall traffic out): For Wireless Broadband communications the ALPR client requires TCP port 443 to communicate with the LEARN server backoffice. The HTTPS protocol is primarily used to communicate over TLS 1.0, 1.1, or 1.2 with 128-bit encryption ciphers or better. This allows for the upload of ALPR data to the LEARN web services and request for data from the LEARN services and Google Maps. 7.1.3.5 ASTRO 25 Radio and Infrastructure Requirements The solution can be deployed to send location data information using an ASTRO 25 radio equipped with a GPS receiver with minimum firmware version 7.18.8 and at software version R15.00.00 or later. ASTRO 25 system release 7.14 or above is required if the data will be sent via the LMR system. Enhanced Data and Intelligent Middleware (IMW) in addition to a Exhibit A: Contract Documentation Requirements f1l Motorola Solutions Hardware and Network Specifications 81 May 10, 2022 Item #11 Page 461 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 firewall to connect the system CEN and internet securely including a packet data gateway and GGSN for each zone are used to send the location updates and events can be enabled as part of that effort. Customer will be responsible to provide internet connection and will allow Motorola to add any necessary firewalls. • GPS Activation and Enabled. • Packet Data Interface. • Enhanced Data Enabled. -Supported on portables-APX 8000, APX 7000, APX 6000, APX 4000, APX 3000. -Supported on mobiles-APX 7500, APX 6500, APX 4500. • Enhanced Data Port List set to 4001. ASTRO 25 Voice Priority ASTRO Enhanced Data subscribers give priority to voice transmissions over data. Exhibit A: Contract Documentation Requirements 82 Hardware and Network Specifications Motorola Solutions G May 10, 2022 Item #11 Page 462 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 SECTION 8 INTERFACE CONTROL DOCUMENTS Exhibit 2: Interface Functional Descriptions 8.1 PREMIERONE CLOUD CAD INTERFACE FUNCTIONAL DESCRIPTIONS Table 8-1: List of Interfaces and Queries Customer known as Interface Function NetRMS Outbound Calls For Service Data Feed NetRMS Query Third Party System Spidr Tech Outbound Calls For Service Data Feed Axon Outbound Calls For Service Data Feed Coplogic DORS Inbound CAD Incident Create* CLETS/NCIC Query State Query Crossroads Accident Query Query Third Party System Crossroads Citation Query Query Third Party System Coplogic DORS Query Query Third Party System LaserFiche Query Query Third Party System QueTel Query Query Third Party System Legacy Query (CAD) Query Third Party System *Dependent on 3rd Party ability to write to PremierOne API City of Carlsbad, CA February 16, 2022 8.1.1 CAD Calls For Service Data Feed Interface Functional Description The Cloud CAD CFS interface allows Cloud CAD to provide Calls for Service (CFS) data to a third-party system. The Cloud CAD Interface will extract the specified CFS data from the Motorola Solutions PremierOne Cloud CAD System and provide the data by delivering JSON files to a file drop location via the FTP, SFTP, or SMB protocol. Exhibit A: Contract Documentation Requirements CD Motorola Solutions Interface Control Documents 83 May 10, 2022 Item #11 Page 463 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 8.1.1.1 8.1.1.2 The Cloud CAD CFS interface provides specified CFS data and is based on new or updated incidents. The interface provides the current snapshot of the incident and sends updates as they occur in the Cloud CAD system. The interface will be sending incidents, incident unit and narratives near real-time. Data Elements included in this interface are provided in the Proprietary Information section of this Product Page. The functionality and data set provided with this interface is predefined and non-negotiable. Supported Use Cases 1. The CFS interface will send Incident and Incident Unit data to the third party system when a new incident is created and contains a report number. 2. As part of the system configuration, the list of desired agencies can be set which will be used as a filter to determine which incidents are delivered. 3. When incidents are updated, the CFS interface will deliver a new copy of the incident file to the target system. 4. Updates are transactional and cannot be sent in timed intervals. The third party will receive each update as it occurs. Specific Technical Requirements Target System Version Target System Connection Protocol File drop in JSON format via FTP, SFTP or SMB protocol Send Only - Acknowledge Received / Send NOTE: Any other type of connection to the third party system (e.g. SOAP/REST API) or file format (e.g. XML) is not supported for this Standard interface. If integration with a 3rd party API or a different file format is required, a Custom interface will be needed instead. • This interface requires installation and configuration of an on-premises CloudConnect virtual machine, typically hosted on the Anchor Server • An FTP, SFTP, or SMB server with appropriate credentials and permissions is required for the interface to write to (typically provided by the customer or 3rd party CFS consumer) • Network connectivity needs to be established between the CloudConnect VM and the file drop server location with appropriate.ports open (depending on file delivery method chosen) • N~twork connectivity needs to be established between the CloudConnect VM and the PremierOne cloud (see CloudConnect network requirements for details on required ports and URLs) • Exceptions are logged in the CIE Cloud CAD logging environment • The interface will send incidents, incident unit and narrative data in one payload • All data will be provided as specified below .. No table lookups, format conversions, additions, omissions, etc. will be performed. Exhibit A: Contract Documentation Requirements 84 Interface Control Documents Motorola Solutions May 10, 2022 Item #11 Page 464 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 8.1.1.3 8.1.2 Data Elements Included in Interface: Incident Information • Incident Number • Incident ID • Agency ID • Incident Date • Report Number • Incident Started Date Time • Report Number Agency ID • Area Name • Sector Name • Beat Name • Location • Apartment • City Name • Latitude • Longitude • Cross Street • Intersection • Zip Code • State Name • Incident Units Call sign • Incident Unit Incident Number • Unit History Unit Agency • Unit History Unit ID • Unit History Status • Unit History Time • Unit History Transaction Type • Unit Current Home Station Name • Unit Current Agency Key • Unit Current Home Area Key • Unit Current Unit Key • Incident Comments • Incident Comment User ID • Incident Comment Date Commented • Incident State Name CAD Incident Create Interface Functional Description City of Carlsbad, CA February 16, 2022 The Incident Creation Interface allows a 3rd-party system to create incidents in Cloud CAD. This allows the Dispatcher to process incidents initiated by external systems or devices. A pending incident containing the information supplied by the 3rd-party system appears in the Dispatcher's pending status monitor and is handled in the same fashion as any other incident. When an incident-generating event is created within the external system, the external system generates an incident creation request to the Cloud CAD Incident Create interface via JSON over REST API. Exhibit A: Contract Documentation Requirements ti Motorola Solutions Interface Control Documents 85 May 10, 2022 Item #11 Page 465 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 8.1.2.1 8.1.2.2 8.1 .2.3 The pending incident can be displayed in the Pending Status Monitor window. The ID generated by the external system is displayed on CAD Client as the Foreign Incident Number. This number can be used in the·lncident Recall and Incident Update commands by placing the~ (tilde) character in front of the number to indicate it is a Foreign Incident Number. Supported Use Cases: • Cloud CAD can receive a CFS request and create an incident • Cloud CAD user can view the incident Unsupported Use Cases: • For each event, the external system sends a single incident message to the Cloud CAD Incident Creation interface. No updates are expected or processed by CAD. Specific Technical Requirements NOTE: Any other"type of connection from the third party system (e.g. SOAP, file drop, etc.) or file format (e.g. XML) is not supported for this Standard interface. If integration with a 3rd party API or a different file format is required, a Custom interface will be needed instead. • The REST API is hosted in the Motorola Solutions cloud. Customer/3rd party system is responsible for ensuring access to the API is available. • All data will be provided as specified below. No table lookups, format conversions, additions, omissions, etc. will be performed. Proprietary Information / Data Mapping: Data Elements accepted from external system via Interface REST API • DisciplineCode • NatureCode • Comments • lncidentSource • Consumer • CorrelationlD • Priority • Location • Address • FullText • CrossStreet • Intersection • Building • Floor • Apartment Exhibit A: Contract Documentation Requirements 86 Interface Control Documents Motorola Solutions May 10, 2022 Item #11 Page 466 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 8.1.3 8.1.3.1 • Subdivision • City • State • ZIP Code • Latitude • Longitude • Description • Jurisdiction • AreaKey • SectorKey • BeatKey • Name State Query Interface Functional Description City of Carlsbad, CA February 16, 2022 The Interface allows PremierOne users to submit transactions to State and Federal systems, via the State Message Switch. These transactions are most typically ones that perform inquiries, although transactions that enter, modify, locate, and clear information are also possible. The State Message Switch provides links to State systems like Department of Motor Vehicles (OMV) and national law enforcement systems like National Crime Information Center (NCIC). Query requests can be made on PremierOne CAD or Mobile clients. The PremierOne Query Service processes the request and determines which data source(s) can fulfill the request. This information is then passed to the PremierOne Interface component, which translates the request to XML messages and passes it on to CommSys ConnectCIC. ConnectCIC handles the State connection and translates the messages to the query strings required by the State. The State Message Switch forwards the request to the appropriate system. When a response is received, ConnectCIC parses and returns the response to the PremierOne Interface component as an XML message. The Interface parses the response and forwards it to PremierOne Messaging Service, which handles the routing of the query response to the requestor. User access to the query forms is managed by the user roles provisioned in PremierOne. Supported Use Cases • An authorized PremierOne user can select a query type, enter the required query parameters, and submit the query using a Query Request form. • PremierOne administrator may also create a command line version of a query form. This use case allows users to quickly submit frequently used queries. The administrator may also configure the system so queries can be submitted using person and vehicle information entered in an incident. • Query responses are displayed in the Query Responses tab of the query window. They may also be displayed in a dedicated window outside of the main CAD client window. • Query Request forms are built upon the underlying data supplied by the External System. A form could use one or more underlying data sources. Thus, query responses from a particular form could be from multiple data sources. Exhibit A: Contract Documentation Requirements G Motorola Solutions Interface Control Documents 87 May 10, 2022 Item #11 Page 467 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 8.1.3.2 8.1.3.3 • In most States, the query response sent back from the State Message Switch is a block of text. This text will be displayed to the user. • Certain responses may be parsed, by ConnectCIC, which involves examining the response and determining where certain key data such as names, addresses, and license status are placed. This structured response is available as discrete values to PremierOne. This can be used to provide a visually formatted response that emphasizes key information. Unsupported Use Cases • Query Responses can be formatted for Workstations and Mobile clients. Query formatting is done using Extensible Stylesheet Language Transformations (XSL T) and the result is displayed using Hypertext Markup Language (HTML). The HTML transformation provides an enhanced level of formatting beyond the raw text that is returned in the query responses. The enhanced formatting can be helpful to call out specific data elements, or display images if they are included in the response from the External System. • A structured response may also be used to populate the person or vehicle information in an incident, without requiring the retyping of the information from a response. The user may run a query on a driver using their operator license number, and then use this feature to populate the person form with the person's details from the query response. • Cascading and drill-down queries can be provisioned by using details from the structured query response as input to subsequent queries. Cascading queries run automatically using these results and a drill-down query is run when the user clicks on the hyperlink on the response form. Specific Technical Requirements N/A NIA X X • Connectivity needs to be established between PremierOne Suite and the State Message Switch, over the Custom.er Enterprise Network, using TCP protocol. The connection needs to meet the State's security requirements. • PremierOne exceptions are logged in both the Windows Event Log on the application server and the PremierOne database. • CommSys ConnectCIC logs query errors and parsing issues to the ConnectCIC log file on the PremierOne application server. • User access to the query forms are managed by user roles in PremierOne. • Users need to be certified according to the State requirements and have a valid user account to access the State system. Devices used to submit queries must also meet the State security requirements. • The query response is dependent on the State connection and response time of the data sources. Query response is displayed as it is received from the external data source. • Customer is responsible for contacting Motorola Solutions when changes occur in the Interface or Customer Enterprise Network, which might affect the Interface. • Customer is responsible for maintaining user credentials, ORls and Mnemonics as required by the State. Exhibit A: Contract Documentation Requirements 88 Interface Control Documents Motorola Solutions May 10, 2022 Item #11 Page 468 of 604 DocuSign Envelope 10: EE0000EC-B19D-469F-887C-147E3BCEAFF7 8.1.4 8.1.4.1 City of Carlsbad, CA February 16, 2022 • Customer is responsible for contacting Motorola Solutions when State changes the parameters or the response formats of the queries. Third Party Query Interface Functional Description The Interface allows PremierOne users to submit transactions to a third-party system. These transactions are most typically ones that perform inquiries, although transactions that enter, modify, locate, and clear information are also possible. Query requests made on PremierOne CAD or Mobile clients are routed to one of the PremierOne application servers. The PremierOne Query Service processes the request and determines which data source(s) can fulfill the request. This information is passed to the PremierOne Common Services Interface (CSI) component, which translates the request to a query string and handles the connection to the data source. When a structured response is received, CSI parses the response and forwards it to PremierOne Messaging Service, which handles the routing of the query response to the requestor. The interface can support calls to a Stored Procedure on the third-party system database or a call to an Application Programming Interface (API) published by the third-party system to get the data. The interface also supports Open Database Connectivity (ODBC), REST Web Service and Transmission Control Protocol (TCP) connections. This interface implementation is limited to 6 forms with basic response formatting and 2 response types per request. Motorola Solutions will provide 8 hours of training and support for Customer to provision additional queries. This interface does not include enhanced response formatting or cascading/drill down queriel?. If these features are desired, they can be added on for additional cost during contract negotiations or through the change order process. PremierOne services manage the data transformation and exchange process. The interface may direct a single query request to multiple systems, and each system will provide its own response. Supported Use Cases: • PremierOne user can select a query type, enter the required query parameters, and submit the query using a Query Request form. The same query forms are available throughout the PremierOne Suite. • User access to the query forms is managed by the user roles provisioned in PremierOne. • PremierOne administrator may also create a command line version of a query form. This allows users to quickly submit frequently used queries. • The administrator may also configure the system so queries can be submitted using person and vehicle information entered in an incident. • Query Request forms are built upon the underlying data supplied by the third-party system. A form could use one or more underlying data sources. Thus, query responses from a particular form could be from multiple data sources. • Query responses are displayed in the Query Responses tab of the query window. They may also be displayed in a dedicated window outside of the main CAD client window. Exhibit A: Contract Documentation Requirements ti Motorola Solutions Interface Control Documents 89 May 10, 2022 Item #11 Page 469 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 8.1.4.2 • If the third-party system provides a structured response, then this data is available as discrete values to PremierOne. This can be used to provide a visually formatted response that emphasizes key information. Unsupported Use Cases: • Query Responses can be formatted for Workstations and Mobile clients. Query formatting is done using Extensible Stylesheet Language Transformations (XSL T) and the result is displayed using Hypertext Markup Language (HTML). The HTML transformation provides an enhanced level of formatting beyond the raw text that is. returned in the query responses. The enhanced formatting can be helpful to call out specific data elements, or display images if they are included in the response from the third-party system. • A structured response may also be used to populate the person or vehicle information in an incident, without requiring the retyping of the information from a response. The user may run a query on a driver using their operator license number, and then use this feature to populate the person form with the person's details from the query response. • Cascading and drill-down queries can be provisioned by using details from the structured query response as input to subsequent queries. Cascading queries run automatically using these results and a drill-down query is run when the user clicks on the hyperlink on the response form. If these additional features are desired by the Customer, Motorola Solutions will provide a change order for Customer consideration for the enhanced response formatting. 8.2 SPECIFIC TECHNICAL REQUIREMENTS: Data Fields & Proprietary Information: This Interface requires modification to PremierOne Interface service. Motorola Solutions is reliant on receipt of the API or Stored Procedure and the associated design documents from the Customer to implement the Interface. Exhibit A: Contract Documentation Requirements 90 Interface Control Documents Motorola Solutions May 10, 2022 Item #11 Page 470 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 SECTION 9 City of Carlsbad, CA February 16, 2022 PREMIERONE CLOUD TRAINING PLAN 9.1 OVERVIEW Motorola Solutions considers training to be an extremely important aspect of the adoption of a new solution and requires working closely with the Customer. Motorola's instructors are certified through the Learning and Performance lnstitute's Trainer Performance Monitoring & Assessment (TPMA) program, as well as their Online Learning Facilitators program. Motorola uses a learning management system (Learning exPerience Portal or LXP) for both online and virtual training. 9.2 CUSTOMER TRAINING ROLES 9.2.1 Customer Training Representative 9.2.2 During the Project Planning Phase, the Customer will designate a Customer Training Representative. This individual will be the contact for the Learning Management System and Motorola trainers. The Customer Training Representative will provide Motorola user names and email addresses so access to the LXP can be completed. The Customer Training Representative should be familiar with the Customer's daily operations and must attend (or designate a replacement) each Motorola educational course. Motorola trainers will rely on this representative to be the one point of contact for Motorola staff when policy and procedural questions arise, act as course facilitator, and act as the Customer's educational monitor. The Customer will also identify the personnel who will serve as trainers. These individuals must participate in all the Train-the-Trainer courses. In addition to the skills described below, the Customer's trainers must have prior experience as a classroom instructor and a thorough understanding of the Customer's operations. Other courses will require participants from different areas of the Customer's operations as shown in the individual Motorola training course descriptions below. Learning Management Administrator The Customer will assign a Learning Management Administrator during the Project Planning Phase of the Project. The Learning Management Administrator will attend the Learning Management System Admin Overview and will be given the ability to add/modify users, run reports, and add/modify groups within the panorama. They can also build Groups, a more granular segmentation of the LXP that is generally used to separate learners of like function (i.e. dispatchers, call takers, patrol, Exhibit A: Contract Documentation Requirements ti Motorola Solutions PremierOne Cloud Training Plan 91 May 10, 2022 Item #11 Page 471 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 9.2.3 firefighter). Learners can be assigned a Learning Path (a collection of courses that follow a logical order which may or may not enforce linear progress). Customer Training Attendees Students should have a typing proficiency of 25 wpm, knowledge of PCs and Microsoft Windows, and have completed course prerequisites as listed in the course descriptions prior to the training. 9.3 PREMIERONE CLOUD TRAINING PLAN SCOPE 9.3.1 The following sections delineate the courses that are offered for the PremierOne Cloud solution. While the scope of this document presents the complete array of training offerings, only those offerings directly associated with the contracted solution will be delivered or made available to the Customer. Customers may purchase additional courses and onsite training as desired via the initial contract or via the change provision ·of the Agreement. The following presents each training offering available for each major functional area of the PremierOne Cloud solution. Training will be delivered in accordance with the project schedule. In some cases, courses may be delivered in a combined training session in order to realize efficiencies in training delivery and to optimize the training experience of the student. For example, PremierOne Cloud Mobile Provisioning may be appended to a PremierOne Cloud CAD Provisioning course in order to take advantage of the workflow logic and provisioning choices of both functional areas. PremierOne Cloud CAD Course Module Number of Courses Included Learning Management System Admin Overview 1 PremierOne Cloud CAD Provisioning Workshop 1 PremierOne Cloud GIS Import Training 1 PremierOne Cloud CAD Train-the-Trainer 1 PremierOne Cloud CAD End User Training 6 SSRS Report Builder Training in PremierOne for 1 CAD/Mobile Exhibit A: Contract Documentation Requirements 92 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 472 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 9.3.2 9.3.3 9.3.4 9.3.5 9.3.6 PremierOne Mobile Course Module PremierOne Cloud Mobile Provisioning Workshop PremierOne Cloud Mobile Client Installation (Windows, Android, iOS) Overview PremierOne Cloud Mobile Train-the-Trainer w/Aware Map and Incident Viewer overview CommandCentral Aware City of Carlsbad, CA February 16, 2022 Number of Courses Included 1 1 2 Course Module Number of Courses Included End User Training -LXP Computer Based 1 Aware Workshop -Virtual 1 CommandCentral Investigate End User OPTION -CommandCentral Community Digital Evidence Collection Course Module CommandCentral Community Digital Evidence Collection OPTION -WatchGuard V300 Cameras Course Module WatchGuard RE4/M500 and/or V300 End-User Training (Officers) Number of Courses Included Number of Courses Included Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 93 May 10, 2022 Item #11 Page 473 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 9.4 9.4.1 9.4.2 9.4.3 PREMIERONE CLOUD TRAINING GENERAL INFORMATION Training Courses Types of training courses may include the following: • Administrative Workshops -Provide specialized users with in-depth knowledge on the features, operational, and administrative functions of the system. • Train-the-Trainer -Instructor-led classroom training that provides key individuals with extensive hands-on use of the system using true-to-life incident scenarios so they can develop and provide training to new users. • LXP -Online "anytime" training using the Learning Management System. Training Facilities and Schedules The Customer shall provide facilities for training courses which are alcohol and smoke-free. Both the on-site and virtual classes will require a computer projector connected to high~speed internet to support virtual/video classroom connection to the instructor. The workshop format also requires multi-monitor student workstations. Students and instructors will dedicate class time to training and will not be subject to interruptions. The Customer will: • Mutually agree with Motorola on the Training schedules to accommodate the Customer's shift operations and other site-specific requirements. Evening courses will end by 11 :00 p.m. Weekends and Holidays will not be used as training days. • Supply Motorola with a roster of course attendees at least two weeks prior to training courses, and they will be provided access to pre-requisite training that must be completed prior to the onsite training course start date. • Confirm the readiness of all workstations at least two days prior to each onsite training course. Training Methods and Procedures Designated Motorola Instructors will provide application instruction using several techniques and materials, including the following: • Instructor Lesson Plan -The instructor's tool for planning the detailed course content on a module-by-module basis. • Training Course Agenda -The student handout that outlines the course sequence of events including duration, and course modules. • Worksheets, Job-Aids, Quizzes, retention instructional activities. Exhibit A: Contract Documentation Requirements 94 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 474 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 9.4.4 9.4.5 City of Carlsbad, CA February 16, 2022 • Training Course Objectives -The instructor's predefined course objectives. These are provided for Train-the-Trainer classes only. • Evaluations -On the final day of a training class, the students will be asked to complete an Instructor Evaluation form. They are optional forms and anonymity is acceptable. • Certificates of Attendance -Students completing the on-site and online classes will receive Certificates of Attendance. • Attendance Rosters -Customers will provide to the Motorola instructor a roster listing the names of training participants ten days prior to the start of the course. Instructors will complete Attendance Rosters of actual participants for each day of training • Motorola PremierOne User Documentation -An electronic copy of the applicable Motorola Reference Manuals and documentation will be provided prior to training. • The Customer is responsible for duplicating and delivering manuals to participating students prior to class commencement. Training Environment PremierOne Cloud CAD and Mobile has a fully functional second environment that can be used for training if desired. This training environment will enable the Customer's trainers to provide on-going training. This training environment also allows training to continue without interruption of the real time operations. Use of the training environment is covered in the Train-the-Trainer classes. PremierOne Cloud Records training will be completed in the pre-production environment prior to Go Live. Session Attendance Motorola is committed to providing a quality training experience and desires that the Customer receive the maximum benefit from each training session. Each training session has been sized to provide the optimal training environment that meets the needs of the students in relation to the complexity of the material being presented. Given the nature of the material being presented and the intensity of the training, it is imperative that maximum course numbers not be exceeded. In the event the number of students in attendance exceeds the published maximum number of students and the list of participants identified on the training roster, Motorola will take corrective action, ensuring the integrity of the session is maintained and the students' ability to learn is protected. Motorola corrective action may include: • Delaying the start of training until the number of students in attendance is in line with the maximum number of students allowed for the session. Exhibit A: Contract Documentation Requirements f1' Motorola Solutions PremierOne Maintenance and Support Agreement 95 May 10, 2022 Item #11 Page 475 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E38CEAFF7 City of Carlsbad, CA February 16, 2022 9.4.6 9.4.7 9.5 9.5.1 • Splitting the class into multiple sessions. In such a case, the Customer will be charged for multiple occurrences of the class plus additional expenses, including travel related expenses, incurred by Motorola Solutions. • Delaying the classroom training until the Prerequisite training has been completed in the LXP by each learner. Learning experience Portal (LXP) Requirements The LXP is accessed via Internet browser. Motorola will set up an individual instance of the LXP that provides autonomy to the agency. Accounts to access the LXP are created for each learner using their email address. All learners accessing LXP content must have an account in the LXP. A learner will need to have access to the internet via workstation, laptop, tablet, or smartphone to access learning. These may also be referred to as clients within the LXP. Audio accompanies visual display; speakers or headsets for listening are recommended. Course assessment evaluations are also accessed online. Access to these evaluations in the classroom is suggested. LMS Learner Subscription Package Customer resources will have access to the LMS training materials during deployment and as long as the post-live subscription is maintained. Learner level subscriptions allow access to all materials available for the applications included in this Training Plan. PREMIERONE CLOUD COURSE DETAILS Training Course Classifications Motorola Solutions offers virtual and Learning Management System (LMS) training for the PremierOne Cloud Suite. Customer resources will have access to the LMS training materials during deployment and as long as the post-live LMS subscription is maintained throughout the subscription term. LMS course content is regularly updated and new courses are made available to Customers on a regular basis. As such, Motorola will provide the Customer with a list of the most current LMS prerequisite courses at the time of project kickoff. Training Course Classifications LMS-P Students must complete LMS prerequisites before attending training. LMS-C Training classes are entirely conducted via LMS on demand with no in- person training component. Virtual Virtual instructor-led training. Exhibit A: Contract Documentation Requirements 96 PremierOne Cloud Training Plan Motorola Solutions 0 May 10, 2022 Item #11 Page 476 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Training Course Classifications Ill Training from an onsite instructor conducted at the Customer's facilities. Exhibit A: Contract Documentation Requirements 0 Motorola Solutions PremierOne Maintenance and Support Agreement 97 May 10, 2022 Item #11 Page 477 of 604 DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 9.5.2 Training Course Descriptions Table 9-1: Learning Management System Admin Overview Learning Management System Admin Overview Goal Training Classification Training Material Duration Participation Class Size Prerequisites Environment Setup Provide training to add/modify users, run reports, and add/modify groups within the Learning Management Solution. Virtual Up to one hour in one business day. Those responsible for the management of assigning and overseeing LMS-C and LMS-P training. Maximum of two students. • Knowledge of Customer Training Requirements. • Provide Motorola with the names (first and last) and emails of Customer LMS administrator: • Provide access to learningservices.motorolasolutions.com. Each workstation or device used for LMS prerequisites must have an internet connection. Exhibit A: Contract Documentation Requirements 98 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 478 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Table 9-2: PremierOne Cloud CAD Provisioning Workshop PremierOne Cloud CAD Provisioning Workshop Goal Training Classification Training Material Duration Participation Class Size Prerequisites Environment Setup Provide detailed instruction on Computer Aided Dispatch (CAD) provisioning data files. • LMS-P. • In-Person. • PremierOne CAD/Mobile Provisioning Guide. • Course Outline. • Up to 32 hours. • Online prerequisite training. Those responsible for making the decisions on configuration options and have participated in the business process review. Maximum of four students. • LMS Prerequisite training courses • Knowledge of current Mobile and CAD application and configuration and agency SOPs. • Microsoft and ESRI proficiency as defined in the Prerequisites Section. • One workstation for each participant. • Each workstation or device used for LMS prerequisites must have an internet connection. • CAD workstation for each participant with network connection to PremierOne Cloud CAD. • Projector. • White board (if possible). • Microsoft Excel should be installed on at least one training workstation. Exhibit A: Contract Documentation Requirements CD Motorola Solutions PremierOne Maintenance and Support Agreement 99 May 10, 2022 Item #11 Page 479 of 604 DocuSign Envelope ID: EE0OO0EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Goal Training C lassificatio n Training Material Duration Participatio n Class Size Prerequisit es Environme nt Setup Table 9-3: PremierOne Cloud GIS Import Training PremierOne Cloud GIS Import Training This course offers the skills and practice necessary to use the PremierOne Import tool and create the required databases and mxd docs for CAD and Mobile. The module covers the use of the import tool to build the required File Geodatabase and load to SQL databases for the PremierOne system. Virtual. PremierOne GIS System Administrator Training Guide. Up to 24 hours over three consecutive business days. GIS personnel and GIS System Administrator(s). Maximum of four students. • Computer knowledge and PC skills including DOS and Microsoft Windows; and basic PC functionality. • Completion of Windows tutorials or equivalent training. • Basic understanding of geographical data and proficient in the use of ArcGIS. • One GIS workstation. • Connection to the internet (to support screen share ability for virtual training). · Exhibit A Contract Documentation Requirements 100 PremierOne Cloud Training Plan Motorola Solutions Q May 10, 2022 Item #11 Page 480 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Note Table 9-4: PremierOne Cloud CAD Train the Trainer PremierOne Cloud CAD Train the Trainer Provide selected personnel with sufficient knowledge to support a comprehensive end user training program. In-person. • CAD User Guide. • Course Outline. • LMS refresher training courses. • Up to 32 hours over four consecutive business days. • Online prerequisite material. City of Carlsbad, CA February 16, 2022 Instructors who are responsible for the in house training of employees and for ongoing user training. Maximum of 12 students. • Knowledge of current CAD application and customer operations. • LMS Prerequisite training courses. • Each workstation or device used for LMS prerequisites must have an internet connection. • CAD workstation for each participant with network connection to PremierOne Cloud CAD. • Projector. • White board (if possible). Allow two weeks from the end of train-the-trainer to the beginning of end user training to allow the customer to build site-specific documentation and outline for end user classes. Exhibit A: Contract Documentation Requirements f.D Motorola Solutions PremierOne Maintenance and Support Agreement 101 May 10, 2022 Item #11 Page 481 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Note Table 9-5: PremierOne Cloud CAD End User Training PremierOne Cloud CAD Train the Trainer • I I -Provide selected personnel with functional knowledge of Cloud CAD features and functions. • CAD User Guide. • Course Outline. • LMS refresher training courses. • Up to 24 hours over three consecutive business days. • Online prerequisite material. Calltakers/Dispatchers. Maximum of 12 students. • Knowledge of current CAD application and customer operations. • LMS Prerequisite training courses. • Each workstation or device used for LMS prerequisites must have an internet connection. • CAD workstation for each participant with network connection to PremierOne Cloud CAD. • Projector. • White board ~if possible). Allow two weeks from the end of train-the-trainer to the beginning of end user training to allow the customer to build site-specific documentation and outline for end user classes. Exhibit A: Contract Documentation Requirements 102 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 482 of 604 DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 Table 9-6: PremierOne Mobile Provisioning Workshop City of Carlsbad, CA February 16, 2022 PremierOne Mobile Provisioning Workshop Goal Training Classification Training Material Duration Participation Class Size Prerequisites Environment Setup Provide detailed instruction on Mobile provisioning data files. • LMS-P. • Virtual. • PremierOne CAD/Mobile Provisioning Guide. • Course Outline. • Up to four (4) two-hour remote CheckPoint Meetings in accordance with the Project Schedule. • Online prerequisite training. Those responsible for making the decisions on configuration options and have participated in the business process review. Maximum of four students. • LMS Prerequisite training courses. • Knowledge of current Mobile and CAD application and configuration and agency SOPs. • Microsoft and ESRI proficiency as defined in the Prerequisites Section. • One workstation for each participant. • Each workstation or device used for LMS prerequisites must have an internet connection. • CAD/Mobile workstation for each participant with network connection to PremierOne Cloud CAD/Mobile. • Projector. • White board (if possible). • Microsoft Excel should be installed on at least one training workstation. Exhibit A: Contract Documentation Requirements CD Motorola Solutions PremierOne Maintenance and Support Agreement 103 May 10, 2022 Item #11 Page 483 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Table 9-7: PremierOne Mobile Client Installation Overview PremierOne Mobile Client Installation (Windows, Android, iOS) Overview Goal Training Classificatio n Training Material Duration Participatio n Class Size Prerequisite s Environ men t Setup Provide selected personnel with sufficient knowledge to install PremierOne Mobile client software on Windows workstations and Android or iOS SmartDevices. For Windows, this includes prerequisite third-party software. If the customer desires, an imaging solution can be presented. Approximately 1 to 2 hours of online training material specific to the installation environment operating system. Given varying complexities associated with the operating system environment that will support the Mobile Client (Windows, Android, iOS) the PremierOne CAD Mobile Client Installation course duration can vary. Motorola will advise which course applies to your specific installation. IT staff who are responsible for installing the Mobile Client software. N/A -Available to all LMS subscribers. Knowledge of Microsoft operating systems and basic software installation practices. Each workstation or device must have an internet connection to the LMS system. Exhibit A: Contract Documentation Requirements 104 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 484 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Note Table 9-8: PremierOne Mobile Train the Trainer PremierOne Cloud Mobile Train the Trainer City of Carlsbad, CA February 16, 2022 Provide selected personnel with sufficient knowledge to support a comprehensive end user training program. Also includes overview of Aware features for Map viewer and Incident viewer on Android/iOS devices. • LXP. • PremierOne Mobile User Guide(s). • Approximately four hours of material. Instructors who are responsible for the in house training of employees and for ongoing user training. In-person -Maximum of twelve students LXP -Available to all LXP subscribers. • Completion of LXP-C and LXP-P courses. • Knowledge of current Mobile application (Windows, Android, and/or iOS) and customer operations. Each workstation or device used for LXP prerequisites must have an internet connection. Allow two weeks from the end of train-the-trainer to the beginning of end user training to allow the customer to build site-specific documentation and outline for end user classes. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 105 May 10, 2022 Item #11 Page 485 of 604 DocuSign Envelope ID: EEOOOOEC-8190-469F-887C-147E38CEAFF7 City of Carlsbad, CA February 16, 2022 Table 9-9: SSRS Report Builder Training in PremierOne CAD/Mobile Goal: Training Classification Course Materials: Duration: Participation: Class Size: Prerequisite: Environment Setup: Provide selected personnel with knowledge on how to create custom reports against the PremierOne Reporting Data Warehouse (ROW) using Microsoft SQL Server Reporting Service (SSRS) and Report Builder software. In-person. SSRS Training Guide Up to 24 hours over three consecutive business days Personnel who will create custom reports Maximum of six (6) students Class participants must have some knowledge/experience of creating "on demand" reports. Class participants should have experience working with relational database structures as well as writing and understanding transact SQL code. Student Workstations: • One (1) workstation for each attendee with a connection to the PremierOne system environment. • The following is the current list of Operating Systems and Browsers supported for the web portal. o Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2 o Microsoft Edge(+) Preferred o Microsoft Internet Explorer 1 O or 11 o Google Chrome(+) o Mozilla Firefox(+) • Microsoft SQL Server Reporting Services installed, configured, and working. • Microsoft Report Builder installed. Optional: • SQL Server Management Studio on each Student Workstation • One (1) CAD Client for the class is preferred in the case data entry needs to take place in order to report against. System Requirements: • Data pre-exists in the Reporting Data Warehouse (data is typically propagated during the training courses.) Instructional Requirements: • Instructor's workstation(s) with network connection • Projector • White board (if possible) Exhibit A: Contract Documentation Requirements 106 PremierOne Cloud Training Plan Motorola Solutions CZ., May 10, 2022 Item #11 Page 486 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Table 9-10. CommandCentral Aware End User Training CommandCentral Aware End User Training City of Carlsbad, CA February 16, 2022 This course provides an overview and demonstrates all the features and functions of CommandCentral Aware. It consists of six comprehensive modules: Overview, Basic Operations, Map View, Event View, Video View, and Radio Console View. LXP-C (Computer Based) • Online • Approximately one hour. Intelligence officer -crime analyst (badge or civilian) who is stationed at the Aware workstation to monitor events in real time and assist those responding with detailed information coming from many disparate data feeds into the application as well as video and voice. N/A -Available to all LXP subscribers. • None Each workstation or device used for LXP must have an internet connection. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 107 May 10, 2022 Item #11 Page 487 of 604 DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Note Table 9-11: CommandCentral Aware Workshop CommandCentral Aware Workshop Understand the functionality of applications that comprise CommandCentral Aware. Operate CommandCentral Aware applications. Use the administrative tools to manage the applications that comprise CommandCentral Aware. Virtual Instruction • Online • 24 hours total covering two sections • Operator Section: Aware position operators (Primary) System Administrators (Secondary) • Administration Section: System Administrators/Managers • None Each workstation or device used for LXP prerequisites must have an internet connection. The CommandCentral Aware Workshop course consists of several modules to address Customer training needs for the Aware solution. This training provides information on the general Aware interface including video, messaging, mapping, and radio consoles as well as modules that address the optional applications found in the Aware solution. This course is divided into two sections: one to address the needs of customer system administrators and the second to train operators of the Aware position. The administrator content covers the information necessary to manage user, camera, reports, and other tasks that are necessary to administer the Aware solution. The operator content covers the controls and functionality of the various applications that make up the Aware solution to allow users to make the most effective use of their Aware positions. Exhibit A: Contract Documentation Requirements 108 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 488 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Table 9-12: CommandCentral Analytics End User City of Carlsbad, CA February 16, 2022 CommandCentral Community Digital Evidence Collection Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Configure and effectively provide dashboard data, conduct searches using Advanced Person Search. View search results using Map, Data Grid, Link Analysis, apply filters to the Data Grid. LXP-C (Computer Based) • Online • 1 hour Users who are responsible for accessing data to create dashboard analytics. N/A -Available to all LXP subscribers. • None Each workstation or device used must have an internet connection. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 109 May 10, 2022 Item #11 Page 489 of 604 OocuSign Envelope ID: EEOOOOEC-8190-469F-887C-147E3BCEAFF7 City of 9arlsbad, CA February 16, 2022 Table 9-13: OPTION -CommandCentral Community Digital Evidence Collection CommandCentral Community Digital Evidence Collection Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup Generate a QR code or link to enable public submission of case digital media, view submitted evidence in TipManager, edit evidence in CommandCentral Evidence, add or remove the agency from the public- facing application. LXP-C (Computer Based) • Online • 0.25 hours Users who are responsible for receiving, viewing, and collecting digital evidence from public sources. N/A -Available to all LXP subscribers. • None Each workstation or device used for LXP access must have an internet connection. Table 9-14: OPTION -WatchGuard 4RE and V300 End-User Training WatchGuard 4RE and V300 End-User Training Goal Training Classification Training Material Duration Participation Class Size Prerequisite s Environment Setup • • ·-Configure and effectively understand how to use the system on a daily basis and how to use.the 4RE/M500 and/or V300 during a shift. •• - • Online • V300 Basic 30 minutes, V300 Full 45 minutes • • None Each workstation or device used must have an internet connection if accessing the online training. Exhibit A: Contract Documentation Requirements 110 PremierOne Cloud Training Plan Motorola Solutions G May 10, 2022 Item #11 Page 490 of 604 DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 SECTION 10 PREMIERONE MAINTENANCE AND SUPPORT AGREEMENT City of Carlsbad, CA February 16, 2022 This Maintenance and Support Agreement (the "Agreement") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL ("Motorola") and the entity set forth in the signature block below("Customer"). Motorola and Customer will each be referred herein as a "Party" and collectively as the "Parties". This Agreement is effective as of the date of the last signature (the "Effective Date") For good and valuable consideration, the Parties agree as follows: Section 1 EXHIBITS The Exhibits listed below are incorporated into and made a part of this Agreement. In interpreting this Agreement and resolving any ambiguities, the main body of this Agreement will take precedence over the Exhibits and any inconsistency between the Exhibits will be resolved in the order in which they are listed below. Exhibit A Exhibit B "PremierOne Cloud Service Customer Support Plan" "Labor Rates" Section 2 DEFINITIONS "Equipment" means the physical hardware purchased by Customer from Motorola pursuant to a separate System Agreement, Products Agreement, or other form of Agreement. "Motorola" means Motorola Solutions, Inc., a Delaware corporation. "Motorola Solutions Software" means Software that Motorola owns and is covered in this Maintenance and Support Agreement. "Non-Motorola Solutions Software" means Software that a Third Party other than Motorola owns. "Optional Technical Support Services" means fee-based technical support services that are not covered as part of the standard Technical Support Services. "Patch" means a specific change to the Software that does not require a Release. "Products" means the Equipment (as indicated in the Covered Products Exhibit) and Software provided by Motorola. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 111 May 10, 2022 Item #11 Page 491 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 "Product Release" means the release of Motorola Software considered to be the next generation of an existing product or a new product offering. "Releases" means an Upgrade to the Motorola Software. "Residual Error" means a software malfunction or a programming, coding, or syntax error that causes the Software to fail to conform to the Specifications. "Services" means those maintenance and support services described in the Customer Support Plan Exhibit and provided under this Agreement. "Software" means the Motorola Solutions Software and Non-Motorola Solutions Software (Third Party) that is furnished with the System or E·quipment. "Specifications" means the design, form, functionality, or performance requirements described in published descriptions of the Software, and if also applicable, in any modifications to the published specifications as expressly agreed to in writing by the parties. "Standard Business Day" means Monday through Friday, 8:00 a.m. to 5:00 p.m. local time, excluding established Motorola holidays. "Standard Business Hour" means a sixty (60) minute period of time starting at notification within a Standard Business Day(s). "Start Date" means the date upon which this Agreement begins. The Start Date is specified in the Covered Products, Support Options and Pricing Exhibit. "System" means the Products and Services provided by Motorola as a system and are more fully described in the Technical and Implementation Documents attached as Exhibits to the applicable system agreement between Customer and Motorola. "Technical Support Services" means the remote support provided by Motorola on a standard and centralized basis concerning the Covered Products, including diagnostic services and troubleshooting to assist the Customer in ascertaining the nature of a problem being experienced by the Customer. Technical Support Services includes minor assistance concerning the use of the Software (including advising or assisting the Customer in attempting data/database recovery, database set up, client-server advice), and minor assistance or advice on installation of Releases provided under this Agreement. "Upgrade" means the process of installing the latest or generally available version of the installed solution product. Section 3 SCOPE AND TERM OF SERVICES 3.1. In accordance with the provisions of this Agreement and in consideration of the payment by Customer of the price for the Services, Motorola will provide to the Customer the Services as described in the Customer Support Plan Exhibit 3.2. The term of this Agreement is six (6) years, beginning on the Start Date. Following the initial term period, this Maintenance and Support Agreement will automatically renew upon the anniversary date for successive one (1) year periods unless either party notifies the other of its intention to not renew the Agreement (in whole or part) not less than thirty (30) days before the anniversary date or requests an alternate term or this Agreement is terminated for default by a·party. Exhibit A: Contract Documentation Requirements 112 PremierOne Maintenance and Support Agreement Motorola Solutions G May 10, 2022 Item #11 Page 492 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 3.3. This Agreement covers all copies of the specified Products listed in the Ordering Documents that are subscribed to from Motorola to the Customer. If the price for SeNices is based upon a per unit fee, such price will be calculated on the total number of units of the Products that are licensed to Customer as of the beginning of the maintenance and support period. If, during a maintenance and support period, Customer acquires additional Products that will be covered by this Agreement, the price for maintenance and support seNices for the additional Products will be calculated and added to the total price either (1) if and when the maintenance and support period is renewed or (2) immediately when Customer acquires additional Products, as determined by Motorola. Motorola may adjust the price of the maintenance and support seNices at the time of a renewal if it provides to Customer notice of the price adjustment at least forty-five (45) days before the expiration of the maintenance and support period. If Customer notifies Motorola of its intention not to renew this Agreement as permitted by Section 3.2 and later wishes to reinstate this Agreement, it may do so with Motorola's consent provided (a) Customer pays to Motorola the amount that it would have paid if Customer had kept this Agreement current, (b) Customer ensures that all applicable Equipment is in good operating conditions at the time of reinstatement, and (c) all copies of the specified Software listed in the Description of Covered Products are covered. 3.4. When Motorola performs SeNices at the location of installed Products, Customer agrees to provide to Motorola, at no charge, a non-hazardous environment for work with shelter, heat, light, and power, and with supeNised access to the covered Products. Customer will provide all information pertaining to the hardware and software with which the Products are interfacing to enable Motorola to perform its obligations under this Agreement. 3.5. All Customer requests for covered SeNices will be made initially with the call intake center identified in the Customer Support Plan. 3.6. Motorola will provide to the Customer Technical Support SeNices and Releases as follows: 3.6.1. Motorola will provide Technical Support SeNices and correction of Residual Errors during the term of the subscription in accordance with the Customer Support Plan. Any Technical Support SeNices that are performed by Motorola outside the scope of this Agreement and the Customer Support Plan will require prior City approval and be billed at the then current hourly rates. The objective of Technical Support SeNices will be to investigate specifics about the functioning of covered Products and to determine whether there is a defect in the Product. Technical Support SeNices will not be used in lieu of training on the covered Products. 3.6.2. Motorola will provide to Customer without additional subscription fees an available software update/upgrade for the specified Products listed in the Ordering Documents. Software updates, as defined in the Customer Support Plan, are designed to be delivered remotely. SeNices for onsite delivery requested by Customer will be quoted at the time of the request. 3.6.3. Motorola will provide to Customer an available Product Release after receipt of a request from Customer, but Customer must pay for all additional license and/or subscription fees, any onsite installation or other seNices, and any necessary Equipment provided by Motorola in connection with such Product Release. Motorola's duty as described in this paragraph is contingent upon Customer's then- current installation at the time of Customer's request being within two (2) Standard Release versions of the new Standard Release available for general release. Any seNices will be performed in accordance with a mutually agreed schedule. 3.6.4. Along with Software updates to the Products listed in the Ordering Documents, Motorola will make available new purchasable products, features and modules which are separate and distinct from the mainstream Motorola Solutions Software line of Products. Newly released Products may have PremierOne subscriptions as a pre-requisite and/or share some portion of the PremierOne code base. Customers are not entitled to these products, features and modules, or upgrades to them within this Exhibit A Contract Documentation Requirements f» Motorola Solutions PremierOne Maintenance and Support Agreement 113 May 10, 2022 Item #11 Page 493 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Maintenance and Support Agreement, if they have not purchased the required subscriptions and/or licenses. 3.6.5. As part of the Software development process Motorola makes every reasonable effort to lessen impact to customer operations. Any change to existing functionality is done after thorough review of customer feedback and with announcement of said change. When it's not technically feasible to meet a particular requirement Motorola will proactively communicate the changes. Beyond these efforts Motorola does not warrant that a Release will meet Customer's particular requirement, be uninterrupted or error-free, be backward compatible, or that all errors will be corrected. Errors addressed as part of the Software Release will be corrected. Full compatibility of a Release with the capabilities and functions of earlier versions of the Software may not be technically feasible. If it is technically feasible, Motorola will make available services to integrate these capabilities and functions to the upgraded version of the Software, which services may be fee based. 3. 7. The maintenance and support Services described in this Agreement are the only covered services. Unless optional or a la carte Technical Support Services are purchased, these Services specifically exclude and Motorola will not be responsible for: 3.7.1. Any service work required due to incorrect or faulty operational conditions, including but not limited to Equipment not connected directly to an electric surge protector, or not properly maintained in accordance with the manufacturer's guidelines. Other services may be available for an additional fee and will be addressed with an amendment to the Agreement. 3.7.2. The repair or replacement of Products or parts resulting from failure of the Customer's facilities, Customer's personal property and/or devices connected to the System (or interconnected to devices) whether or not installed by Motorola's representatives. 3.7.3. The repair or replacement of Equipment that has become defective or damaged due to physical or chemical misuse or abuse, Customer's negligence, or from causes such as lightning, power surges, or liquids. 3.7.4. Any transmission medium, such as telephone lines, computer networks, or the ISP, or for Equipment malfunction caused by such transmission medium. 3.7.5. Accessories, custom or Special Products; modified units; or modified Software. 3.7.6. The repair or replacement of parts resulting from the tampering by persons unauthorized by Motorola or the failure of the System due to extraordinary uses. 3.7.7. Operation and/or functionality of Customer's personal property, equipment, and/or peripherals and any application software not provided by Motorola. 3.7.8. Services for any replacement of Products or parts directly related to the removal, relocation, or reinstallation of the System or any System component. 3.7.9. Services to diagnose technical issues caused by the installation of unauthorized components or misuse of the System. 3.7.10. Services to diagnose malfunctions or inoperability of the Software caused by changes, additions, enhancements, or modifications in the Customer's platform or customer provided software. 3. 7.11. Services to correct errors found to be caused by Customer-supplied data, machines, or operator failure. Exhibit A: Contract Documentation Requirements 114 PremierOne Maintenance and Support Agreement Motorola Solutions 4' May 10, 2022 Item #11 Page 494 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 3.7.12. Operational supplies, including but not limited to, printer paper, printer ribbons, toner, photographic paper, magnetic tapes and any supplies in addition to that delivered with the System; battery replacement for uninterruptible power supply (UPS); office furniture including chairs or workstations. 3. 7 .13. Third-party software unless specifically listed on the Covered Products Exhibit. 3.7.14. Support of any interface(s) beyond Motorola-provided port or cable, or any services that are necessary because third party hardware, software or supplies fail to conform to the specifications concerning the Products. 3.7.15. Services related to customer's failure to use a UPS system to protect against power interruptions as related to their on-premise equipment. 3.7.16. Any design consultation such as, but not limited to, configuration analysis, consultation with Customer's third-party provider(s), and System analysis for modifications or Upgrades which are not directly related to a Residual Error report. 3.8. The Customer hereby agrees to: 3.8.1. Maintain any and all electrical and physical environments in accordance with the System manufacturer's specifications. 3.8.2. Provide standard industry precautions (e.g. back-up files) ensuring database security, per Motorola's recommended backup procedures. 3.8.3. Ensure System accessibility, which includes physical access to buildings as well as remote electronic access. Remote access can be stipulated and scheduled with the Customer; however, remote access is required and will not be substituted with on-site visits or proxies if access is not allowed or available. 3.8.4. Appoint one or more qualified employees to perform System Administration duties, including acting as a primary point of contact to Motorola's Technical Support organization for reporting and verifying problems. At least one member of the System Administrators group must have completed Motorola's End-User training and System Administrator training (if available). The combined skills of this System Administrators group includes proficiency with: the Products, the system platform upon which the Products operate, the operating system, database administration, network capabilities such as backing up, updating, adding, and deleting System and user information, and the client, server and stand alone personal computer hardware. The System Administrator will follow the Residual Error reporting process described herein and make all reasonable efforts to duplicate and verify problems and assign a Severity Level according to definitions provided herein. Customer agrees to use reasonable efforts to ensure that all problems are reported and verified by the System Administrator before reporting them to Motorola. Customer will assist Motorola to confirm that errors are not the product of the operation of an external system, data links between system, or network administration issues. If a Severity Level 1 or 2 Residual Error occurs, any Customer representative may contact Motorola's Customer Support by telephone, but the System Administrator must follow up with Motorola's Customer Support as soon as practical thereafter. A full list of customer system management responsibilities is provided in the Customer Support Plan section 5.2. 3.9. Intentionally deleted. 3.10. Customer will permit and cooperate with Motorola so that Motorola may periodically conduct audits of Customer's records and operations pertinent to the Services, Products, and usage of application and database management software. If the results of any such audit indicate that price has been understated, Exhibit A: Contract Documentation Requirements CD Motorola Solutions PremierOne Maintenance and Support Agreement 115 May 10, 2022 Item #11 Page 495 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Motorola will review their findings with the Customer and, if the results are supported by this review, may correct the price and immediately invoice Customer for the difference (as well as any unpaid but owing license fees). 3.11. If Customer replaces, upgrades, or modifies equipment, or replaces, upgrades, or modifies hardware or software that interfaces with the covered Products, Motorola will notify the Customer of of any price adjustments required for the new configuration. 3.12. Customer agrees not to attempt or apply any upgrades(s), alteration(s), or change(s) to the database software without the prior approval of Motorola. Section 9. CERTIFICATION DISCLAIMER Motorola specifically disclaims all certifications regarding the manner in which Motorola conducts its business or performs its obligations under this Agreement, unless such certifications have been expressly accepted and signed by an authorized signatory of Motorola. Section 10. COMPLIANCE WITH APPLICABLE LAWS The Parties will at.all times comply with all applicable regulations, licenses and orders of their respective countries relating to or in any way affecting this Agreement and the performance by the Parties of this Agreement. Each Party, at its own expense, will obtain any approval or permit required in the performance of its obligations. Neither Motorola nor any of its employees is an agent or representative of Customer. IN WITNESS WHEREOF, the Parties have caused this Agreement as of the Effective Date. MOTOROLA SOLUTIONS, INC. CUSTOMER By: 7~ By: ________ _ Name: Micah Applewhite Name: _____________ _ Title: MSSSI Vice President & Director Sales Title: --------------- Date: May 5, 2022 Date: --------------- Exhibit A: Contract Documentation Requirements 116 PremierOne Maintenance and Support Agreement Motorola Solutions G May 10, 2022 Item #11 Page 496 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Exhibit A -Customer Support Plan QUICK CONTACTS Toll Free Phone# - Email Motorola Portal Provide the following information: Service Agreement Information Customer Name: · Service Agreement Start/End Date: Customer Success Advocate Contact Name Phone Cellular Email Exhibit A: Contract Documentation Requirements 0 Motorola Solutions I SUPPORT CENTER ------·-- 1-800-MSI-HELP (1-800-674-4357) Option 4,2,2 CAD Option 4,4,2 RMS PSACASE@MSisolutions.com MyView Portal 1. Site Name 2. Your Name 3. Your Call Back Number I 4. A Brief Description of the Problem I Severity (Critical, High, Medium, Low) I I PremierOne Maintenance and Support Agreement 117 May 10, 2022 Item #11 Page 497 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 ESCALATION PLAN Our goal is to ensure our customers receive the best possible support from Motorola Solutions, Inc. (Motorola). If you feel that your support needs are not being met, as a direct customer,. we provide an escalation process for your request to the next department or manager. Your initial call should always be to the first department or person on the list above. If, after making this initial contact you still have unresolved issues, please see below for escalation contact information. ESCALATION CONTACT Level 1 Level 2 Level 3 SUPPORT CENTER DON JACKSON Manager, Technical Support Mobile: (720) 355-1183 Don.Jackson 1@MSlsolutions.com Assigned CSA JOSH HOWELL Senior Manager, Technical Support Mobile: (616) 540-4103 Josh.Howell@motorolasolutions. Ell! Assigned CSM Exhibit A: Contract Documentation Requirements 118 PremierOne Maintenance and Support Agreement JEREMY SMITH Head of Software Enterprise Centralized Managed & Support Operations Mobile: (951) 216-8827 Jeremy.Smith@MSlsolutions.com Motorola Solutions G May 10, 2022 Item #11 Page 498 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 10.1 SUPPORT PLAN SUMMARY 10.1.1 Introduction -Serving Our Customer's Needs City of Carlsbad, CA February 16, 2022 Motorola is committed to helping people be their best in the moments that matter. We appreciate the opportunity to provide support pursuant to this "Support Plan," and our service delivery teams are focused on the health, service performance and reliability of the PremierOne Cloud Service ("PremierOne Cloud Service"). Your PremierOne Cloud Service Support Plan will be amended from time to time to align with industry best practices and customer needs. 10.1.2 Service Management Overview -PremierOne Cloud Services Motorola's Subscription Support Services provides support delivered through a combination of centralized resources within Motorola's SSC collaborating with product development resources that are experienced in managing mission critical services and associated technologies. The SSC operates 24 x 7 x 365, leveraging remote access to customer services for complete resolution methpds. Service management and open communication is the key to effective service delivery and relationship building. Our Motorola services program offers end-to-end service management and includes: • Software Support • Motorola System Support Center In addition to the support services provided by the SSC, a Customer Success Advocate ("CSA") will be assigned to partner with the support team in the System Support Center ("SSC") to help agencies maximize use of their software and services investment as their trusted advisors. The CSA will partner with you to ensure that the transition from implementation to service is smooth and will be available to answer questions that may arise outside of your standard agency service experience. CSAs partner with customers to drive adoption, identify goals and objectives for use of the product and engaging in an ongoing customer communication about progress toward desired outcomes, relationship timelines and next steps. CSAs provide ongoing, active engagement with an agency from deployment through renewal or expansion to maximize usage, value and product satisfaction. Our goal is to build an outcome driven relationship that ensures your agency maximizes the value of your software investment. The Support Plan covers the following customer locations: ~-•· r~efilled in ost-contract 1■:MUGFll•!II• Exhibit A: Contract Documentation Requirements CD Motorola Solutions ~ift1£6l11I· I --_ =tiWGMi¥ I PremierOne Maintenance and Support Agreement 119 May 10, 2022 Item #11 Page 499 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 10.2 MOTOROLA SYSTEMS SUPPORT CENTER If you experience problems with PremierOne Cloud Service, you have several options to get help with determi_ning the cause of the problem and finding a solution. The SSC is the central point of contact to report PremierOne Cloud Service incidents and submit change requests. The SSC can be reached 24/7 to assist with your service needs via: ■ Toll Free Telephone: 1-800-MSI-HELP (1-800-674-4357) -Option 4,2,2 CAD -Option 4,4,2 RMS • MyView_Portal: low priority requests only, 24-hour turn around • Email: PSACASE@motorolasolutions.com (24-hour turnaround) NOTE: Critical and high priority incidents should not be reported via email or MyView Portal. Product and service technical resources are ready to receive and take action on requests for service. The SSC will: ■ Open a ticket and categorize the reported issue or request ■ Resolve incidents based on priority ■ Perform analysis to assist in identifying a corrective action plan ■ Escalate the incident/request to technical or service experts when required ■ Engage the next level management to ensure timely problem resolution, when necessary ■ Provide regular status updates for escalated incidents Motorola's primary objective is to restore PremierOne Cloud Service to normal operations as quickly as possible and minimize the adverse impact of service events on our customers and their mission. This serves our primary goal of maintaining the highest possible quality of service and availability. The PremierOne Cloud Service team of highly skilled, knowledgeable and experienced specialists are available to the customer as an integrated part of the support and technical issue resolution process. All customer requests for service change requests are tracked centrally in Motorola's IT Service Management (ITSM) Toolset, resulting in a ticket number. All SSC support activity that occurs after the cutover of the service into production is tracked in this service to ensure consistent visibility of all activities. Exhibit A: Contract Documentation Requirements 120 PremierOne Maintenance and Support Agreement Motorola Solutions G May 10, 2022 Item #11 Page 500 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 All calls requiring incidents or service requests are assigned a severity in accordance with the agreed "Severity Level Response" table below. Via the ITSM, Motorola will track the progress of each ticket from initial capture to resolution. Motorola will advise and inform the customer of the ticket progress and tasks that require further investigation and assistance from the customer's technical resources. Upon notification of the incident, the SSC will supply a ticket number for reference. For each reported or alert generated the SSC will apply a Severity Level classification, which has an assigned target response time objective. This classification provides the means to manage the appropriate response and engagement processes. 10.2.1 Reporting Incidents Using the Toll-free Number The SSC is staffed with trained technicians who remotely access your PremierOne Cloud Service to begin troubleshooting. For accurate reporting and ticket tracking, all PremierOne Cloud Service issues are reported to the SSC. At a minimum, when above, the SSC will require: ■ Customer name (Site) ■ Caller's name • Caller's contact number (supply alternate call back number) ■ Description of the problem or request ■ Operational impact of the problem (Severity) 1.1 Severity Level and Response Definitions Reporting Trouble -The SSC number is provided to all customers for PremierOne Cloud Service issues. If the issue cannot be resolved through our remote diagnostics by the SSC, then the customer technician will be required to report on-site within the above stated response times. Response Time -The amount of time expired between the time in which the issue is reported to SSC by the customer to the time that a qualified technician is actively troubleshooting the issue. Note: Business Days is defines as Monday -Friday excluding holidays Business Hours is defined as Monday -Friday 8am -5pm local time Incident Time -The period of time during which the service or any service component suffers an Incident. Incident Time shall commence upon either the issue is reported to the SSC by the customer. Incident Time shall end upon completion of the repair or restoration of the service or service component. Incident Time shall not include downtime attributable to (a) Force Majeure conditions (as defined in the applicable agreement); or (b) scheduled preventive maintenance that the customer was notified and consented to in advance. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 121 May 10, 2022 Item #11 Page 501 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 10.2.2 Severity Response Table SEVERITY DEFINITION LEVEL 1 An incident is deemed CRITICAL if one or Critical 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 2 An incident is deemed HIGH if a business High 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). 3 An incident is deemed MEDIUM if business Medium 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) 4 Technical Requests -This level is meant for Low the request for information or set of actions regarding product or service functionality, features and capabilities. This level is meant to represent minor issues, such as cosmetic issues, documentation errors, general usage questions, configuration questions and product or service Update requests. RESPONSE TIME Telephone conference within 1 Hour of initial voice notification Telephone conference within 3 Hours of initial voice notification during normal business hours Telephone conference within 8 Hours of initial notification during normal business hours Telephone conference within 2 Business Days of initial notification The customer will provide a properly trained resource who is familiar with the operation of that service that will be responsible for the administration of the PremierOne Cloud Service. Motorola will provide remote technical consultants to support the local resource in the timely closure of performance and operational issues. Exhibit A: Contract Documentation Requirements 122 PremierOne Maintenance and Support Agreement Motorola Solutions CD May 10, 2022 Item #11 Page 502 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 10.3 CUSTOMER CONTACTS FOR NOTIFICATION The designated personnel noted below will be the customer contacts for notification of a Critical Incident and/or for technical consultation. Customer will be notified of any scheduled/planned maintenance that will result in a customer outage at least 7 days prior to the scheduled maintenance. CONTACTS AND NOTIFICATIONS SITE CONTACT NAME: I Main Phone Number for Site: Used when needing to speak with Site: Motorola Contact Name Email Phone Number -Customer Contact Names Email Phone Number After Hours Contact Names >--Email Phone Number 10.4 CASE MANAGEMENT VIA MYVIEW PORTAL The MyView Portal provides you an interface into our "Incident Management System". MyView Portal gives you valuable service and service information whenever you need it along with complete support tickeUincident management from submission to close. MyView Portal provides the ability to: • Create low priority tickets ■ Obtain status updates on existing tickets • Supply additional information on tickets 24/7 • When updating ticket notes, please provide contact information, which includes phone number, email, etc. Motorola does not recommend using this tool for openir)g Severity 1 or 2 tickets. To report any critical issues or to update current tickets with critical information customers should contact the SSC by calling 1-800-MSI-HELP (800-647-4357). Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 123 May 10, 2022 Item #11 Page 503 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E38CEAFF7 City of Carlsbad, CA February 16, 2022 10.4.1 Ticket Initiation via Email 10.5 An alternative customer support tool is available for PremierOne Cloud Service Customers. Along with the toll-free phone number and MyView Portal, customers can request technical support by email. For many customers who use their handheld device as a means to open tickets, email provides additional flexibility for initiating tickets. To ensure proper ticket management and contractual response, email ticketing is only available for severity levels 3 or 4. In order to process a ticket via email, the email must be formatted exactly as described below: 1. Address emails to: PSACASE@MSlsolutions.com 2. Email Subject: Type "PSA Service Requesf' and a brief description of the service issue (this will become the ticket title). 3. Use the following template for the body of the email. Copy and paste from below, adding in the accurate and specific information of the request following the bold items listed: -Site ID: Site ID -Product Type: Choose from the following list: ♦ PremierOne Cloud CAD ♦ PremierOne Mobile for Cloud CAD ♦ Command Central Jail -Contact First Name: first name or the name of the person you would like support personnel to contact -Contact Last Name: last name or the name of the person you would like support personnel to contact. -Phone Number: the area code and phone number where the contact person may be reached -Severity Level: only for severity level 3 or 4. ♦ Note: All severity level 1 or 2 tickets must be opened via the toll- free SSC number -Problem Description: a comprehensive description of the problem 4. Once the email has been sent, the customer will receive an email with the ticket numb~r for future reference. If an email response is not received, or if you need to open a severity level 1 or 2 ticket, please contact the toll-free SSC number. CUSTOMER RESPONSIBILITIES FOR SUPPORT The customer will provide a properly trained technical resource responsible for administration of your PremierOne Cloud Service, and familiar with your operations. The on-site resources are to supply suitably skilled and trained on-site presence when requested by the SSC. They will validate issue resolution prior to close of the ticket in a timely manner. Customer's on-site support personnel are responsible for the following: Exhibit A: Contract Documentation Requirements 124 PremierOne Maintenance and Support Agreement Motorola Solutions 0 May 10, 2022 Item #11 Page 504 of 604 DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 1. Initiate Service Request: Contact Motorola through authorized tools and processes outlined in this Support Plan to initiate a technical support request ticket. 2. Work with Motorola to troubleshoot and validate resolution for any reported issues. 3. Assess Severity Level: Assist in assessing and assigning the initial and the correct severity level per the severity level definitions found in the Support Plan. 4. Escalate Appropriately: Contact Motorola to add information or make changes to existing technical support tickets or escalate service requests to Motorola management. Motorola Services management contact information is provided in this Support Plan. 5. Maintenance on Hardware: Customer will provide all on-site hardware maintenance and service for all hardware not provided by Motorola. Customer will be responsible for purchasing on-going maintenance for third-party on-site hardware support for all hardware. Third party support on some system components may be available through the Maintenance and Support Agreement. Customer will contact the appropriate vendor directly for parts and hardware service, if not purchased through the Maintenance and Support Agreement. 6. Perform periodic reboots and ongoing performance tuning, hardware upgrades, and resource optimizations as required. 7. ISP and VPN connectivity: Provide ISP and VPN connectivity and telephone access to Motorola personnel as defined in the service description addendum to the subscription agreement. 8. Provide and maintain customer Azure subscription and services needed for integration with the PremierOne Cloud Service. At a minimum, the customer will maintain authorized users in the agency Azure Active Directory and enable SSO federation by PremierOne Cloud Service to the agency Azure Active Directory for the purpose of user authentication. 9. User Local Device/Workstation Maintenance: Apply upgrades such as OS patches, administrative tools and utilities. 10. Maintain and upgrade software that supports infrastructure applications (IE, Esri, etc.). 11 . Upgrade and maintain antivirus software, appropriately configure and maintain exclusion list. 12. Configure and maintain all products relevant to mobile network connectivity (NetMotion, Verizon, VPN related products, etc.). 13. CAD Customer Install: When directed by Motorola and under Motorola guidance install Motorola provided Citrix updates. 14. Mobile Customer Install: Install, upgrade, and test PremierOne Software Updates. 15. GIS Updates: PremierOne Map Maintenance -Apply mapping and GIS data updates as needed. -Ensure validity and integrity of all GIS related data introduced to the service -Record modifications made to GIS files, and confirm expected behavior within the PremierOne service . -Distribute updated map files to Mobile customers Exhibit A: Contract Documentation Requirements 4' Motorola Solutions PremierOne Maintenance and Support.Agreement 125 May 10, 2022 Item #11 Page 505 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 10.6 16. Anti-Virus and Windows UAC: Install, configure, and upgrade chosen anti-virus software. Appropriately configure user account control settings in a manner that ensures the files are accessible for service stability and successful operation. If service instability occurs after changing any service element pertaining to UAC or AV, report changes to Motorola. If unexpected behavior is experienced while UAC or AV are enabled, and does not occur after disabling UAC or AV, the customer will be responsible for diagnosing and correcting the issue. 17. Provisioning knowledge of the service: Customer must ensure that adequate provisioning training and knowledge has been provided to those authorized to access and/or make changes within PremierOne Provisioning. Provisioning changes should be tracked. This information should be supplied to Motorola to aid in troubleshooting efforts should a problem be experienced. Motorola now provides a tool to aid in provisioning change identification, but changes should be trac.ked internally by the customer as a failsafe. 18. Use of Deployment or All-In-One (AIO): Users of the deployment tool or AIO tool must be appropriately trained and understand its operation fully. Deployment packages that are no longer necessary should be purged. Customer is responsible for mobile customer deployment and should engage Motorola support if a problem is discovered. 19. ISP Bandwidth and Stability: Install, monitor and maintain ISP connections that provide stable operations and adhere to bandwidth requirements to ensure the effective operation of Motorola products and related service components. 20. Remote Access: Upon successful completion of approved background check, customer must provide remote access to requesting Motorola personnel for troubleshooting purposes. This includes, but is not limited to, VPN account access, Microsoft Active Directory Federation for domain access and access to all service elements that pertain to the operation of the PremierOne Cloud Service and functionality. 21. End User Training: Ensure that ali end users of Motorola products are adequately trained to perform their duties and not cause harm or upset of service functionality. Motorola does offer additional training if necessary for an additional cost. 22. Change Management: Notify Motorola of any changes made to the PremierOne Cloud Service, associated interfaces, related hardware, software, network, or any other element that may adversely impact operation or functionality. MOTOROLA RESPONSIBILITIES 1. Motorola Service Support Center: Motorola provides availability to the Service Support Center (800-MSI-HELP), 24 hours a day, 7 days a week to respond to Customer's requests for Severity 1 support. Refer to Severity Level Response Time Goals_for Severity 2, 3 and 4 response times. 2. Motorola Response: Provide remote technical support service via telephone consultation for technical issues that require a high level of PremierOne Cloud Service knowledge and troubleshooting capabilities. Remote technical support is delivered through the Exhibit A: Contract Documentation Requirements 126 PremierOne Maintenance and Support Agreement Motorola Solutions CD May 10, 2022 Item #11 Page 506 of 604 DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 10.7 City of Carlsbad, CA February 16, 2022 Motorola SSC by a staff of technical support specialists skilled in diagnosis and swift resolution of PremierOne Cloud Service performance and operational issues. 3. Case Management: Motorola will track the progress of each ticket from initial capture to resolution. Motorola will advise and inform the customer of the ticket progress and tasks that require further investigation and assistance from the customer's technical resources. 4. Subscription Services Updates: All subscription service updates, feature enhancements, state mandated changes to CIBRS, and defect repairs for the PremierOne cloud solution are provided at no additional cost during the subscription period. Updates will be applied to the training environment approximately two weeks prior to updating the production environment to allow time for user testing. During the production environment update, active user sessions are not interrupted, but the next time a user launches the client, the new version of the CAD client launches. SECURITY Motorola will maintain industry standard security measures to protect the Solution from intrusion, breach, corruption or security risks. During the term of the Agreement, if the Solution enables access to Criminal Justice Information ("CJI"), as defined by the Criminal Justice Information Services Security Policy ("CJIS"), Motorola will provide and comply with a CJIS Security Compliance document. Any additional security measure desired by customer may be available for an additional fee. Motorola will provide the necessary information for its personnel that access customer CJI to submit to a background check based on submission of FBI fingerprint cards, complete CJIS Security Awareness Training and execute the CJIS Security Addendum.his the customer's responsibility to determine when the background credentialing process is required by Motorola personnel. Customer is independently responsible for establishing and maintaining its own policies and procedures and for ensuring compliance with CJIS and other security requirements that are outside the scope of the Service provided. Customer must also establish and ensure compliance with access control and identification and authentication policies and procedures, including password security measures, lost and stolen credentials and account validation. Further, customer must maintain industry standard security and protective data privacy measures. Motorola further disclaims any responsibility or liability whatsoever for customer's failure to maintain industry standard security and data privacy measures and controls, or their role in CJIS Security Policy compliance. Motorola reserves the right to terminate the Service if customer's failure to maintain or comply with industry standard security and control measures negatively impacts the Service, Solution or Motorola own security measures. Both parties will maintain and follow a breach response plan consistent with the standards of their respective industries to include CJIS Security Policy reporting. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Suppot1 Agreement 127 May 10, 2022 Item #11 Page 507 of 604 OocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 Motorola uses reasonable means in the design and writing of its own Software and the acquisition of third party Software to limit Security Vulnerabilities. While no software can be guaranteed to be free from Security Vulnerabilities, if a Security Vulnerability is discovered, Motorola will immediately begin investigation into the root cause of the issue and take the steps set forth in this Agreement, working to correct the issue as soon as reasonably possible. 10.8 LIMITATIONS AND EXCLUSIONS The following activities are outside the scope of the support offered in this Support Plan: ■ On-site visits/resources ■ Provisioning efforts ■ Hardware replacement/exchange ■ Motorola implementation of on-site upgrade and expansion services ■ Customized reports. Such requests are to be directed to the CSA Exhibit A: Contract Documentation Requirements 128 PremierOne Maintenance and Support Agreement Motorola Solutions I' May 10, 2022 Item #11 Page 508 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BC EAFF7 City of Carlsbad, CA February 16, 2022 Exhibit B -Labor Rates The following are Motorola's current labor rates, subject to an annual change. The following rates apply to Customers with a current, active Maintenance and Support Agreement. Billable rates apply to services provided outside of the scope of the Maintenance and Support Agreement and outside the selected Service Level PPM: After 5 p.m., Saturday, Sunday, Motorola Holidays $334 per hour, 2 hours minimum The following rates apply to Customers without a current, active Maintenance and Support Agreement and a I to services available on a Time and Material basis: After 5 p.m., Saturday, Sunday, Motorola Holidays $668 per hour, 2 hours minimum Above rates reflect labor rate only. Additional fees for on-site travel expenses, third party expenses and /or materials will be quoted at the time of customer request for services. Exhibit A: Contract Documentation Requirements G Motorola Solutions PremierOne Maintenance and Support Agreement 129 May 10, 2022 Item #11 Page 509 of 604 DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA February 16, 2022 SECTION 11 FUNCTIONAL REQUIREMENTS MATRIX · The Functional Requirements Matrix dated January 19, 2022 is attached herein. Exhibit A: Contract Documentation Requirements 130 Functional Requirements Matrix Motorola Solutions G May 10, 2022 Item #11 Page 510 of 604DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 INSTRUCTIONS TAB City of Carlsbad Request for Proposals #20-13: CAD/Mobile Acquisition Functional Requirements This spreadsheet contains detailed functional requirements for the systems desired by the City of Carlsbad. These requirements are based on the needs and requirements of the Carlsbad Police Department, as well as industry standard guidelines for public safety systems design, implementation and operation. The following codes should be used to indicate the ability of the proposed system to meet the City's needs: Response Response Code Proposed system complies with requirement. C Proposed system does not comply with requirement. N Proposer recommends an alternative no-cost way to meet requirement (provide explanation in the "Comments" column). A Proposed svstem reauires software modification to comply with reauirement (provide M Vendor is proposing to use a Third-Party to provide the desired functionalitv T Provide the appropriate response code in the column next to each requirement. Where applicable and where requested, pro~ide additional information that describes the way in which the proposed system fulfills the given requirement or how an alternative to the requirement will meet the City of Carlsbad's needs. Short responses may be provided in the "Comments" column, while longer answers may be provided on a separate page. Do not insert rows into any portion of the document. Please respond to each requirement. Omitted responses will be evaluated as response codes of "N" (proposed system does not comply with requirement). Please note that requirements listed in the "General" tab are intended to be system-wide, and therefore apply to CAD and Mobile applications. Page 1 of 1 May 10, 2022 Item #11 Page 511 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments -General System Features 2 Ability to provide the user with feedback as to the success or failure of a system task, including, but not limited to: 3 Audible alert C 4 Visual alert C 5 Ability for system to automatically adjust number sequencing for C new calendar years. 6 Ability for system to automatically account for daylight savings C time and any required parameter changes to daylight savings. 7 Ability to adjust date to account for leap years. C Ability for system to identify whether a system transaction 8 occurs during the first 1 :00 -2:00 a.m. during fall daylight N savings or the second 1 :00 -2:00 a.m. during fall daylight savin s. 9 Ability to date and time stamp all system transactions. C 10 Ability to have a single master time stamp for all application components. C 11 Ability for all date and time stamps to be system generated. C 12 Ability to print with a single keystroke, including but not limited to: 13 Screen C 14 Window N 15 Field N Code Table Administration 17 Ability for the agency to define codes for drop down menus (e.g., C BN for brown, BL for blue). 18 Ability for the agency to maintain code tables, without contacting C vendor. 19 Ability to make changes and additions to the code tables without C modification to or recompilation of the application software. 20 Ability to share code tables among application components. C Page 1 of 17 May 10, 2022 Item #11 Page 512 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments Ability for code table updates to propagate throughout the system 21 (e.g., an update in a code table for one application component updates the same code table in other application components). 22 Ability to designate code table values as obsolete and unavailable for current use, preventing further entry of that value, yet retain the value in the table for inquiries on historical data. 23 Ability to create a new code and merge/link historical records to a new code. 24 25 26 28 29 30 31 32 33 34 35 36 37 38 Ability to store the date a code table value becomes obsolete. Ability to store the date a code table value becomes effective. Ability to prevent display of obsolete code table values on drop down lists. Security Administration Ability to comply with OIS software/application security requirements. Ability to encrypt data transmissions, per CLETS/NCIC requirements. Ability to create multiple security groups. Ability to assign personnel to security groups. Ability to assign users to multiple security groups. Ability for system adminsitrator to assign users to groups based on call si ns. Ability to enable users to override the group to which they are assi ned. Ability for agencies to define access permissions for each security group. Ability to prevent users with expired CLETS/NCIC certification from accessing CLETS/NCIC data. Ability to provide users with a reason for preventing access to CLETS/NCIC data. Ability to view, add, maintain, modify and delete user profiles based on: C C N C C C C C C C C C N C C C New code table may be created, however merging or linking code tables to historical records is not su orted. Page 2 of 17 May 10, 2022 Item #11 Page 513 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 39 Agency C 40 Security group C 41 User ID C 42 User name C 43 Any combination of the above C 44 Ability to restrict user access or security group access to files and data fields for specified transactions: 45 Add/create C 46 Attach to email or send via other electronic method C 47 Delete C 48 Inquiry C 49 Modify C 50 Print C 51 View C 52 Ability to assign user access or security group access to files and data fields for specified transactions: 53 Add/create C 54 Attach to email or send via other electronic method C 55 Delete C 56 Inquiry C 57 Modify C 58 Print C 59 View C 60 Ability to assign security access by physical device (e.g., PC, C terminal, tablet). 61 Ability to remotely log out a workstation (mobile or desktop). C 62 Ability to lock out a user who is deemed a security risk while that C user is on-line (e.g., logged into the system). 63 Ability to provide security at the following levels: 64 Application C 65 Database C 66 Field C 67 Record C 68 Report C Page 3 of 17 May 10, 2022 Item #11 Page 514 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 69 Screen C 70 Transaction C 71 System C 72 Ability to create temporary security profiles. C 73 Ability to tie security profiles to Active Directory user groups. C 74 Ability for applications to work independently in the event Active C Directory becomes unavailable. Ability to support alternate authentication technologies, including 75 but not limited to the following (please list additional compliant N authentication technologies in the comments column): 76 ID card N 77 Security token N 78 Biometric scanner N 79 Bluetooth N 80 Ability to flag a data element as confidential information for N security purposes. 81 Upon data entry N 82 After data entry N Ability for users who are not authorized to access confidential 83 information to see that the information exists, without being able C to see the actual information. .. Logons and Logoffs ■ N Ability for system administrator to chan e user IDs. C Ability to be logged onto multiple workstations at the same time 87 (e.g., logged into mobile computer in a vehicle and logged onto a station computer at the same time): 88 Different types of workstation (e.g., desktop and laptop) C 89 Same types of workstations (e.g., two desktops) C 90 Ability to track user logon/logoff times and locations for time C reporting purposes. 91 Ability to support LDAP or Active Directory authentication. C Page 4 of 17 May 10, 2022 Item #11 Page 515 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 92 Ability to support two-factor logon. 93 Ability to support third-party identification devices for logons. 94 Ability to automatically logoff a user after an agency defined predetermined period of inactivity, based on: 95 User type 96 Location 97 Ability to disable automatic logoff for secured workstations. 98 Ability to save user's data prior to automatically logging off the user. 99 Ability to save user's system preferences prior to user logoff. 100 Ability to save multiple user preferences on the same type of device for each user. Ability to provide system generated message to system 101 administrator or supervisor when an agency defined number of unsuccessful sign-on attempts have occurred. 102 Ability for the unsuccessful sign-on attempt message to include, at a minimum: 103 Date and time 104 Number of attempts 105 User ID 106 Workstation ID 107 Ability to "lock out" a user and close applications after an agency defined number of attempted logons. 108 Ability to disable "lock out" feature. 109 Ability to provide a secure lock-out with quick re-authentication to restrict access to systems from an unattended workstation. User IDs and Passwords Ability for the agency to define the following password and user ID 111 creation criteria: 112 Character limitations 113 Minimum User ID length 114 Maximum User ID length 115 Minimum password length C C C C C C C N C C C C C C C C C C C C Page 5 of 17 May 10, 2022 Item #11 Page 516 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 116 Maximum password length 117 Uppercase characters 118 Lowercase characters 119 Special characters 120 Numbers 121 Ability to use Active Directory for password maintenance. Ability for the agency to define which user-groups can reset 122 passwords on behalf of users (or create a security group that can reset passwords on behalf of users). 123. Ability to require the user to change their passwords at agency defined intervals. 124 125 126 127 128 Ability for the agency to set a global maximum time for allowing a user to keep using a password. Ability to maintain a history of de-activated user IDs. Ability to disable password expiration feature. Ability to require the user to enter a new password twice (e.g., to verify password). Ability to produce auto-notification of impending password expiration. 129 Ability to enforce strong passwords per CJIS requirements. 130 Ability for individual system users to change their own passwords. 131 Ability for system administrator to add and delete users. 132 Ability for system administrator to disable an account. 133 Ability to mask passwords when typed. Ability to encrypt passwords when stored and sent (i.e., no clear 134 text passwords). Audit Trails 136 Ability to create a security group defining who has audit trail access permissions. 137 Ability to maintain an audit trail at the following levels: 138 Field 139 Record 140 Module C C C C C C C C C C C C C C C C C C C C C C C Page 6 of 17 May 10, 2022 Item #11 Page 517 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 141 Application C 142 Text messages N 143 CLETS/NCIC Messages C 144 Ability to view all audit trail records. C 145 Ability to log all actions including, but not limited to: 146 Keystrokes C 147 Queries C 148 Query returns C 149 Changes C 150 Updates C 151 Errors C 152 Security violations C 153 Attempted breaches C 154 File maintenance transactions (e.g., create, read, add, update, C I delete transactions) 155 Inquiries to all internal and external systems C 156 Transaction entries C 157 Print jobs C 158 Override C 159 Successful sign-on C 160 Unsuccessful sign-on attempts C 161 Unauthorized attempts to access data C PremierOne CAD's audit feature records all 162 Ability for the agency to configure which transactions are recorded N transactions associated with an incident. Viewing an in the audit log. incident's audit history displays these transactions for that incident only. 163 Ability to store audit trail data including, but not limited to: 164 User ID C 165 User name C 166 Terminal ID C 167 IP address C 168 Printer ID C 169 Security level C 170 Date and time stamp C 171 Transaction type C Page 7 of 17 May 10, 2022 Item #11 Page 518 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 172 Input, edit, deletion or inquiry C 173 Before and after values of modified data C 174 Type of data accessed during an inquiry C 175 Report number (if applicable) C 176 Ability to review all computer activity performed by a specified C user during a period of time. 177 Ability to log all vendor access to system (e.g., record a description C of all vendor activity). 178 Ability to maintain historical data based on an agency defined C length of time. 179 Ability to maintain file history so that field value changes can be C viewed both before and after change occurred. 180 Ability to set audit log purge criteria. C 181 Ability to perform purge based on criteria. C 182 Ability to date, timestamp, view and audit all inquiries. C 183 Ability of the system to assign a unique identifier to each record C (i.e., log ID). 184 Ability to comply with NCIC Ill logging requirements. C 185 Ability for all audit and logging functionality to be configurable. C 186 Ability to pull up a record and see (e.g., via a function key): 187 Who made last change to record C 188 Time and date stamp of last change to record C 189 Modifications made to record (before and after values) C 190 Ability to extract reports from the audit trail. C 191 Ability to secure audit log from user tampering. C 192 Ability to archive audit trails based on transaction type and/or C date. 193 Ability to manually archive information based upon user-specified C parameters (time, file size, etc.). 194 Ability to automatically archive information based upon the following parameters: 195 Agency defined time period C 196 Agency defined file size C Page 8 of 17 May 10, 2022 Item #11 Page 519 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Dashboards 200 Ability to support dashboards to display information at a glance in the following applications: 201 CAD C 202 Mobile C 203 Ability for users to configure information displayed in personal C dash boards. 204 Ability for dashboards to update dynamically as information is C entered into the system. 205 Ability for dashboards to present information in the following formats: 206 Text based C 207 Graphical C 208 Map based C 209 Reporting 210 Ability to provide a native reporting tool that can: 211 Create reports based on any operational data field in any system C database 212 Create reports based on multiple operational data fields in any C system database 213 Allow the end user to design report format C 214 Access multiple files and tables C 215 Print C 216 Generate HTML reports C 217 Create reports based on SQL queries C 218 Ability for the report generating tool to handle: 219 Arithmetic operations, including fractiles and percentiles C 220 A full suite of statistical operations C 221 Logic operations C 222 Ability for the report generating tool to handle the manipulation of: Page 9 of 17 May 10, 2022 Item #11 Page 520 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 223 Data formats C 224 Field sizes C 225 Editing rules for a field C 226 Field headings C 227 Data definitions C 228 Formatting rules C 229 Ability to maintain a general library of user-created reports. C 230 Ability to connect to database for business intelligence reporting C purposes. 231 Ability to preserve all user-created reports during updates and C upgrades. 232 Ability for all authorized users to access the general library of user-C created reports. 233 Ability for users to put their own reports in a "dashboard" for later use. C 234 Ability to send reports to individuals or groups (via system or C agency email). 235 Ability to generate reports on a pre-determined schedule. C 236 Ability to automatically send scheduled reports to distribution groups. C 237 Ability to auto generate reports based on agency defined C thresholds. 238 Ability to notify agency defined users when thresholds have been C reached/exceeded. 239 Ability to export reports results into standard formats, including: 240 Word C 241 PDF C Accessible PDF also available. 242 Access A Data can be exported and converted to Access, but not direct export in Access. 243 Excel C 244 Text files A Data can be converted from Word to text file. 245 Shapefiles N Page 10 of 17 May 10, 2022 Item #11 Page 521 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments Export will be in Web Archive (MHTML) which is an 246 HTML A aggregate of HTML files. XML is also available for export 247 Image files A Export is available in .ppt which can be converted to an lmaoe. 248 csv C 249 Ability to save reports for subsequent viewing and/or printing. C 250 Ability to delete reports after viewing and/or printing. C 251 Ability to view requested reports prior to printing. C 252 Law Enforcement Queries 253 Ability to run a query on: 254 Report number C 255 Incident number C 256 Officer information, including: 257 Name \: 258 Badge Number C 259 ID C 260 Unit number C 261 Name information, including: 262 Name C 263 Identification number (driver's license, social security number, C etc.). 264 Date of birth C 265 Address information, including: 266 Exact address C 267 Street C 268 Intersection C 269 Business name C 270 Common name C 271 Vehicle information, including: 272 Vehicle identification number C 273 License plate number C 274 Phone number C 275 Reporting District C Page 11 of 17 May 10, 2022 Item #11 Page 522 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 276 Boat Hull number C 277 Serial number for weapons C 278 Serial number for property C 279 Personal File Number (PFN) C 280 Any combination of the above C Ability for query returns to display the name/ID of user requesting 281 information (e.g., if a Dispatcher runs a CLETS query on behalf of C an officer). 282 Ability to search and query multiple databases with one query C request. 283 Ability to provide check boxes for users to indicate which N databases to query. 284 Ability for subject queries of the following databases to return C photos, when available: 285 NetRMS C 286 CLETS/NCIC C 287 DMV C 288 CalPhoto C 289 CalGangs C 290 LPR C 291 CSAR C 292 Regional Registrants C 293 SDLAW C 294 Ability to set agency defined defaults for databases to query C within each application. 295 Ability to search multiple databases with a single query. C 296 Ability to consolidate query returns when multiple databases C are queried. PremierOne CAD allows collapsible consolidation 297 Ability for multi-database query returns to indicate the C information source (e.g., CLETS, NetRMS, etc.). 298 Ability to select any result from a query and drill down for C detailed information (e.g., hyperlink). 299 Ability to drill down on query results. C 300 Ability to save queries for later use. C 301 Ability, when running a criminal history, to capture: Page 12 of 17 May 10, 2022 Item #11 Page 523 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E38CEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 302 Date C 303 Report number C 304 Name C 305 Date of birth C 306 Purpose C 307 Charges C 308 Officer identification C 309 Identification number C 310 Searches 311 Ability to search on any operational data field. C 312 Ability to search on multiple operational data fields. C 313 Ability to access multiple files and tables in a single search. C 314 Ability to search narrative fields. C 315 Ability to search audit trails. C 316 Ability to search message logs. C 317 Ability to exclude specified text when conducting narrative text C searches. 318 Ability to conduct searches based on: 319 Soundex C 320 "Wild cards" . C 321 Exact match C 322 Partial information C 323 Boolean operators ("and," "or," and "not") C 324 Date ranges C 325 Keywords C 326 Ability to narrow down searches (search within a search). C 327 Ability to select any result from a search and drill down for C Note: This functionality must be supported by the detailed information (e.g., hyperlink). database being queried. 328 Ability to restrict searches that result in large volumes of data by: 329 Providing a warning of the size of records found C 330 Requesting users to prompt the system to continue the search C 331 Requesting users to prompt the system to cancel the search C 332 Requesting users to modify the existing search criteria C Page 13 of 17 May 10, 2022 Item #11 Page 524 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 333 Ability to limit the number of records viewed at one time. 334 Ability to clearly indicate when additional information (e.g., more search results) is available. 335 Ability to save searches for later use. 336 Ability to turn on/off pagination for query returns. 337 Ability to export search results into standard formats, including: 338 Word 339 PDF 340 Access 341 Excel 342 Text files 343 Shapefiles 344 HTML 345 PDF 346 Ability to drill down into search returns. BOLs 348 Ability for any authorized user to create BOLs. 349 Ability to provide an audit trail for BOLs. 350 Ability to associate a BOL with a CAD incident number. 351 Ability to provide the following fields for a BOL record: 352 Date issued 353 BOL expiration date 354 Nature of the BOL 355 BOL priority 356 Subject name 357 Subject description: 358 Height 359 Weight 360 Hair color 361 Eye color 362 Clothing description C C C C C A C A N A C C C C C C C C C C C C C C C Data can be exported and converted to Access, but not direct ex ort in Access. Data can be converted from Word to text file. Export will be in Web Archive (MHTML) which is an aggregate of HTML files. XML is also available for ex ort Accessible PDF also available. Page 14 of 17 May 10, 2022 Item #11 Page 525 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 363 Date of birth 364 Known address or location 365 Driver's license number 366 Vehicle description 367 Vehicle license plate 368 Weapon (multiple) 369 Known associates 370 Last known location 371 Direction of travel 372 Contact Information 373 Person issuing the BOL 374 Agency issuing the BOL 375 Case or incident number 376 Additional information in free-form text field 377 Ability to search for BOL based upon any of the data fields. 378 Ability to search the BOL narrative. 379 Ability to accommodate multiple subjects in a BOL. 380 Ability to accommodate multiple vehicles in a BOL. 381 Ability to accommodate multiple weapons in a BOL. 382 Ability to attach a file to a BOL. 383 Ability to embed a photo in a BOL. 384 Ability to update a BOL. 385 Ability to set time limits for BOL retention. 386 Ability to close a BOL. Ability to designate groups or individuals to whom BO Ls should be 387 sent. 388 Ability to view history of recently created BOLs. 389 Ability to archive expired BOL records. 390 Ability to search expired BOL records. 391 Ability to export BOL as a PDF. System Documentation 393 Ability to access a system help menu. 394 Ability to use either a mouse or command line to access the help menu. C C C C C N C C C C C C C C C C C C N C C C C C C C N N C C C Page 15 of 17 May 10, 2022 Item #11 Page 526 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 395 Ability to provide context-sensitive help in the form of prompts C and instructions. 396 Based on user's progress in workflow N 397 Based on data field C 398 Ability to provide context-sensitive help only upon a user request. C 399 Ability to provide help facility for an operation in progress via a C function key from a screen or field within any application. 400 Ability to provide training modules through help menu. C 401 Ability to search help files by keywords. C 402 Ability to provide help facility via function key or icon from any C screen or field within any application. 403 Ability to edit text in help files to address agency specific topics. C 404 Ability to maintain agency specific documentation and procedures, including: 405 Glossary of terms C 406 Glossary of error codes C Ability to augment vendor-supplied help tables with additional 407 information (e.g., add notes to a topic that are viewable along with C the vendor-supplied information). 408 Ability for the agency to create additional/new help files to N suoolement the vendor provided system documentation. 409 Ability for help file to automatically update at the time of all C version/release updates. 410 Ability to prevent software updates from overriding agency-N specific system documentation and help files. 411 Ability for system administrator to create error messages. C 412 Ability for system administrator to edit error messaaes. C 413 Ability to track revisions to system documentation and help files, including: 414 User ID C 415 Date and time C 416 Ability to provide help files in a Windows help format. C 417 Ability to bookmark topics. C Page 16 of 17 May 10, 2022 Item #11 Page 527 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB' City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 418 Ability to search help file by: 419 Keywords 420 Phrases 421 Topics 422 Similar topics Multiple Environments 424 Ability to support multiple environments, including: 425 Production 426 Test 427 Training 428 Backup Ability to provide a configuration tool to enable migrating specific 429 individual configurations from the test environment to the production environment. Ability to provide a configuration tool to enable migrating specific 430 groups of configurations from the test environment to the production environment. Ability to modify the test environment and transfer modifications 431 to the production environment. C C C C C N C N N N N There is a single environment for Test/Training. New releases are released to this enviroment for customer testin ap rox one week rior to production u dates. Page 17 of 17 May 10, 2022 Item #11 Page 528 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAO TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments -General CAD Requirements 2 Ability for authorized user to configure any CAD workstation to manage: 3 Either call taking or dispatching functions C 4 Both call taking and dispatching functions C 5 Ability to maintain compliance with published NENA NG911 C standards. PremierOne CAD's audit features record all transactions associated with an incident. These include Comments, incident create, incident status, recommendations, primary units, unit Ability to provide dedicated fields to capture all CAD transactions in actions, unit statuses, and many more. 6 C an audit log. Additionally interfaces can be audited to show when an interface came offline, how long the interface was running, the interface transactions, etc. 7 Ability to allow multiple personnel to work on a single incident. C Ability to provide a visual identification (e.g., ID stamp) to identify User ID and Console ID are include with all 8 which call-taker/dispatcher entered specific information into a call. C transactions made by a user 9 Ability to support remote access to CAD. C 10 Ability to perform the following via remote access: 11 Monitor Units C 12 Monitor Incidents C 13 Create Incidents N 14 Dispatch Incidents N 15 Run Queries N Ability to achieve full application functionality via mobile devices The PremierOne Mobile client provides full (i.e. smartphone, tablet, other than desktop). If limited CAD functionality available from PremierOne CAD in 16 functionality is available via mobile devices, but not all, please C the field. provide written response in the comments column identifying the available functionality. 17 Application User Interface Page 1 of 48 May 10, 2022 Item #11 Page 529 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 18 Ability for the agency to determine which window configuration N options are configurable at the user level. 19 Ability for users to customize all window views, including, but not limited to: 20 Font size N 21 Font color N 22 Font type N 23 Window background color N 24 Window sizes N 25 Window locations N 26 Fields displayed N 27 Order in which fields are displayed N 28 Ability to save windows configurations based on user login, N irrespective of workstation. 29 Ability to maintain window configuration settings during upgrades. N 30 Ability to reset configuration to default settings. N 31 Ability to display system messages without affecting work in N progress. Ability to have multiple windows open simultaneously (e.g., multiple 32 incident entry windows). If there is a limit to the number of N windows that can be open simultaneously, please specify in the comments column. 33 Ability to tile or cascade multiple windows on screen. N 34 General Data Entry 35 Ability to support data entry via: 36 Mouse (point and click) C 37 Command line C 38 Preformatted masks C 39 Ability to execute any CAD function using the keyboard. (List C exceptions.) 40 Ability to execute any CAD function using the mouse. (List C exceptions.) Page 2 of 48 May 10, 2022 Item #11 Page 530 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 41 Ability to provide multiple command lines. C Command lines are available on all status monitors and active work areas. 42 Ability to provide multiple call entry masks. C PremierOne provides six call entry masks known as primary work areas A user can navigate/toggle to any of the six 43 Ability to toggle between active call entry masks. C work areas using the alt key and number of the primary work area ex: alt +2 will toggle to work area 2 Ability for query returns to create a separate window from the Query returns have the ability to be orphaned 44 query mask. C into its own pane, which is moveable to any screen Command lines can be cleared with a single 45 Ability to create a new command line with a single keystroke. C keystroke. Additionally, new command lines can be opened from each status monitor window. In PremierOne CAD, the command line is 46 Ability to link a command line to a distinct incident. C assigned per work area where each can display a distinct incident. There is also a command line on each status monitor. The default order of the command parameters 47 Ability to enter commands in any order on the command line. A can be changed to match the specific operations of your agency. 48 Ability to enter more than one command on a single command line. C 49 Ability to send the same comments via one command to any unit C associated with an event/incident. so Ability to click on the map and populate the address field with the C corresponding location information. 51 Ability to support: 52 Drop down menus C 53 Auto-completion C 54 Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to: 55 Text wrap C 56 Paragraph formatting N Page 3 of 48 May 10, 2022 Item #11 Page 531 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 57 Bullets and numbering N 58 Copy and paste C 59 Grammar check N 60 Spell check N 61 Ability to add words to the dictionary for spell check. N 62 Ability to disable any word processing capabilities at the agency N level. 63 Time Stamps 64 Ability to automatically time stamp all system transactions. C 65 Ability to manually create a time stamp.· C 66 Ability to manually override a time stamp. C 67 Ability to capture the time a time stamp was overridden. C 68 Ability for all overridden time stamps to be recorded as a manually-C entered override time. 69 Timers Ability to configure incident timers based on agency-defined 70 parameters (e.g., unit status updates, incident type, incident status) C and times. 71 Ability to associate timers with: 72 Unit status updates C 73 Incident type C 74 Priority type C 75 Incident status (e.g., remained in pending for 20 minutes) C 76 Ability to alert user to the expiration of the timer via: 77 Audible alert C 78 Visual alert C 79 Ability to configure the alerts to repeat at agency-defined intervals C until the timer has been acknowledged. 80 Ability to manually set timers. C 81 Ability to record acknowledgement of timer alert. C 82 Ability to provide the following options when a status timer expires: 83 Modify to new time value C 84 Reset to default value C Page 4 of48 May 10, 2022 Item #11 Page 532 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 85 Stop timer C Ability to alert agency defined users if an expired timer has not been 86 acknowledged after an agency defined period of time (e.g., C escalation process). 87 Flags and Alerts 88 Ability to automatically present user any flags/alerts associated with: 89 Location C 90 Weapons C 91 Warrants C 92 Medical C 93 Key information (Knox Box, gate code, etc.) C 94 Hostile occupant C 95 Officer safety (known to resist, etc.) C 96 Agency-defined C 97 License Plate C 98 Person C 99 Weapons C 100 Warrants C 101 Medical C 102 Key information (Knox Box, gate code, etc.) C 103 Hostile occupant C 104 Officer safety (known to resist, etc.) C 105 Agency-defined C 106 Other (if flags and alerts can be associated with any other identifier, C please list those in the "Comments" field) 107 Ability, upon entering an address, to automatically present user any C flags/alerts associated with the address, including but not limited to: 108 Hazard information C 109 Premise history C Ability, upon entering an address, to automatically present user any 110 flags/alerts associated within a radius of the address entered, including but not limited to: Page 5 of 48 May 10, 2022 Item #11 Page 533 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 111 Hazard information 112 Premise history 113 Ability for alerts to include: 114 Audible alert 115 Visual alert 116 Ability for the agency to configure which alerts are audible. 117 Ability to require dispatchers to acknowledge that they have viewed hazards. Ability, when querying a name, for user to be notified of an 118 associated alert (e.g., if the subject is flagged in the RMS, wanted via CLETS/NCIC). 119 Ability to drill down into flags to display additional information. 120 Ability to display incident history of address when creating an incident. 121 Ability for users to sort summary of past incidents by: 122 Chronological order (most recent call shown first) 123 Call type 124 Ability for user to add a flag/alert. 125 Ability to set an expiration for a flag/alert. 126 Ability to add a temporary flag, comment or note to a location. 127 Ability to notify agency-defined personnel of pending expiration of a temporary flag. 128 Ability to include flagged information with dispatches sent to responding units. Call Taking 130 Call Receipt 131 Ability to receive call data from: 132 E9-1-1 phone system 133 Non-emergency 10-digit phone numbers 134 Text-to-911 C C C C C C C C C C C C C C A C C N N PremierOne CAD provides various types of flag/alerts through incident priority comments, Premise/Hazard, and BOLO. Notification can be manually sent through the PremierOne CAD Messaging system or a City created custom re ort notification. Page 6 of 48 May 10, 2022 Item #11 Page 534 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to automatically create a call for service when a 9-1-1 call 135 comes in through the phone system (e.g., create a call and open a call entry mask): 136 Hard-wired 9-1-1 phone line C 137 Wireless 9-1-1 line C 138 Call Data Entry 139 Ability to enter incidents using preformatted screens. C The determination of data elements for capture 140 Ability for the agency to determine what data elements are C is based on existing PremierOne CAD fields. captured as part of the preformatted screen. New data elements are not able to be created. 141 Ability to provide dedicated fields to capture all incoming call information from the E9-1-1 system, including, but not limited to: 142 Caller name C 143 Caller telephone number C 144 Caller address/location calling from C 145 Incident location C 146 Alternate telephone number C 147 Cellular phone service provider C 148 Phase I or Phase 11 indication C 149 X/Y coordinates C 150 Text messages (assuming phone system is NG9-1-1 capable) N 151 TTY conversation C 152 Any other information captured by the E9-1-1 system C Ability to translate texts submitted through NG9-1-1 in a foreign 153 language to English. Please specify which languages can be N translated in the comments column. 154 Ability to attach multimedia messages (MMS), including videos or N pictures taken by citizens, to a call. Ability to automatically populate CAD screen with information from The automatic or manual population of ANI/ALI 155 C data to the incident form is a provisioning E9-l-1 application, without manual intervention. settinq in PremierOne CAD. Page 7 of 48 May 10, 2022 Item #11 Page 535 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to populate CAD screen with information from E9-1-1 The automatic or manual population of ANI/ALI 156 C data to the incident form is a provisioning application via manual intervention (e.g., function key, mouse click). setting in PremierOne CAD. 157 Ability to select previous E9-1-1 data to populate call entry screen. N 158 Ability to provide dedicated fields to enter the following information: 159 Individual (caller, witness, suspect) C 160 Multiple individuals C 161 Vehicle C 162 Multiple Vehicles C 163 Location C 164 Ability to generate an incident from a previous incident. C 165 Ability for authorized user to add comments to a call after it has C been dispatched. 166 Ability for authorized user to add comments to a call (without re-C opening the call) after it has been closed. 167 Ability to alert dispatcher that the call taker has added information by: 168 Audible alert N PremierOne CAD displays a Priority Notification 169 Visible alert C dialog box whenever another user enters priority comments or makes priority updates to an incident. 170 Location Capture 171 Ability to receive geographic coordinates from a cellular telephone C carrier. 172 Ability to relate X/Y coordinates to an actual address. C 173 Ability to capture the following information upon receipt of a wireless 9-1-1 call: 174 X/Y coordinates C 175 Street address of tower C Approximate addresses are given via a reverse 176 Nearest cross street C geocode of the laVlong, which then will give a cross street Page 8 of 48 May 10, 2022 Item #11 Page 536 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 177 Exact address C Approximate addresses are given via a reverse I oeocode of the laUlong 178 Ability to provide user with choices of ALI data for location capture : including: 179 X/Y coordinates C 180 Intersection C 181 Street Address C 182 Any combination of the above C 183 Ability to transform X/Y coordinates to a map for display. C 184 Ability to capture incident location separately from caller location. C 185 Ability to enter a location for an event by the following methods: 186 Street address C 187 Block number or address range C 188 Commonplace name C 189 Landmark C 190 Intersecting street names C 191 X/Y coordinates C 192 Point and click on a map C 193 Ability to suggest locations based on type-ahead capabilities for: PremierOne CAD supports a partial address 194 Street addresses N entry that will display all possible matches in the Address Verification form. PremierOne CAD supports a partial address 195 Intersections N entry that will display all possible matches in the Address Verification form. PremierOne CAD supports a partial address 196 Commonplace names N entry that will display all possible matches in the Address Verification form. Ability for agency to define the order in which type-ahead locations 197 are presented to the user (e.g., Carlsbad addresses before County C addresses, etc.) Page 9 of 48 May 10, 2022 Item #11 Page 537 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 198 Ability to type in either street first when entering intersections. C 199 Ability to save intersections as identical address points regardless of C order of streets entered (e.g., 1st/Main same as Main/1st). PremierOne CAD captures and stores the Ability for system to automatically parse address data into address Street number, direction, prefix, name, type, 200 and suffix data fields in one data element, data fields including: which is then parsed for validation and displaying on the CAD map. 201 Street number C 202 Street name C 203 Street prefix C 204 Street suffix (NW, SW, NE, SE) C 205 Street type (Av, Ln, Bd, "None") C 206 Unit type C 207 Unit number C 208 City C Ability for user to include directional reference for a location (e.g., PremierOne CAD supports this requirement as 209 C long as the directional reference is included in NB interstate 5, SO Exit 24). the GIS provided by the City. 210 Ability to auto populate location information in CAD as E911 system C receives updated location information. 211 Ability to automatically override Phase I information with Phase II C information. 212 Location Verification 213 Ability to verify locations for any address entered into the system C (e.g., CAD incident address, field initiated). 214 Ability to override geoverified location. C 215 Ability to log all locations that fail geofile validation. C 216 Ability to create a report of all overridden geoverified locations. C 217 Ability to use the ALI reported location address for address C verification. 218 Ability to validate an entry upon: Page 10 of 48 May 10, 2022 Item #11 Page 538 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 219 Operator request (e.g., press a button) C 220 Entry into location field C 221 Ability to support Phase I wireless location validation from cellular C callers. 222 Ability to support Phase II wireless location validation from cellular C callers. Ability to notify dispatcher if multiple street addresses/street 223 names/intersections with the same names are found in geofile with C City of Carlsbad locations listed first. Ability to offer a list of address options if multiple similar 224 addresses/intersections/street names are found in geofile with City C of Carlsbad locations listed first. 225 Ability to display closest address matches based on: 226 Block ranges C 227 Building name C 228 Business name C 229 Common place names C 230 Intersections C PremierOne CAD supports a partial address 231 Phonetic spelling A entry that will display all possible matches in the Address Verification form. PremierOne CAD supports a partial address 232 Soundex A entry that will display all possible matches in the Address Verification form. 233 Street name C 234 Ability to display an unlimited number of common place names A PremierOne CAD will limit the response of possible during the address verification process. matches to 100. 235 Ability to enter a valid street name and be presented with: 236 Aliases C 237 Associated address ranges C 238 List of cross streets C 239 Ability to translate call location to appropriate public safety C geographical boundary (e.g. district, beat, sector). 240 Ability to translate alias names to actual street names or addresses. C Page 11 of 48 May 10, 2022 Item #11 Page 539 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 241 Ability to display, on a map the incident location in relation to other C active incidents on the map during the incident entry process. 242 Ability to manually verify an address without creating an incident. C 243 Call Classification and Prioritization 244 Ability to display a drop down list containing incident types. C 245 Ability to enter the call type via the command line. C 246 Ability to support auto completion during the call classification C process. 247 Ability to accommodate call type aliases (e.g., BURG/Burglary). C 248 Ability to override the system generated incident priority. C Ability for an authorized user to assign a priority to an address or PremierOne CAD assigns a priority based on an 249 location for a agency-defined period of time. A incident type. As an alternative, users can enter a Premise/Hazard record for the location. Ability to allow the authorized user to manually upgrade or 250 downgrade the system-assigned priority at any point during the call C (e.g., during call-taking, after dispatch). 251 Ability for dispatcher to change call type without impacting active C call data. 252 Ability to maintain a history of call types if call type changes over the C course of an incident. 253 Ability to visually identify the priority level of an incident (color-C code). 254 Incident Initiation 255 Ability to initiate an incident from the input of location and type C code. 256 Ability to input all call and narrative information on one screen. C Ability to display a blank form for entering new incidents with a 257 single keystroke, mouse click or function key upon initiation of a C CAD incident. 258 Ability to copy an existing incident to create a new incident at the C same location. 259 Ability to enter incidents using: 260 Standard call entry screen form C Page 12 of 48 May 10, 2022 Item #11 Page 540 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 261 CAD command on a command line C 262 Map by clicking on a location C 263 Duplicate Call Management 264 Ability to notify user of potential duplicate calls on the call entry C screen during initial call entry process. 265 Ability to automatically identify potential duplicate calls based on: 266 Incident/call type N 267 Proximity to current incident C 268 Time parameter C The time parameter is based on recently closed incidents. 269 Specific incident address/event location C 270 Phone number A As an alternative, PremierOne CAD displays a Previous Phone Check based on a matching phone number from oast Incidents. As an alternative, PremierOne CAD will display 271 Ability to display proximity calls on a map (e.g., to assist dispatchers A potential duplicate calls with location information in identifying possible duplicate calls). and the ability to open the incident for further details. 272 Ability for the agency to configure the duplicate call identification C algorithm (e.g., defined proximity, definition of "recently closed"). 273 Ability to include the following in the potential duplicate call identification process: 274 Recently closed calls C 275 Pending calls C 276 Self-initiated calls C 277 Active calls C 278 Ability to manually identify a duplicate call and transfer the C duplicate call information into the primary call. The user must view the potential duplicate 279 Ability to provide the user with the following information about incident to validate the following information, possible duplicate incidents: items 235-241. This is a one-click feature from the Potential Duplicates window. 280 Incident details C 281 Caller phone number C Page 13 of 48 May 10, 2022 Item #11 Page 541 of 604DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 282 Incident status C 283 Incident type C 284 Time the incident was initiated C 285 Units assigned C 286 Original dispatcher C 287 Disposition code C 288 Ability for the dispatcher to do any of the following if a CAD incident is determined to be a duplicate call: Add to the original incident record a second complainant with 289 complete complainant information and additional incident C comments 290 Close a duplicate incident and cross-reference it to the original CAD C incident 291 Create an entirely new incident using existing address data C 292 Ability to filter duplicate calls out of reports. C 293 Premise Information Retrieval 294 Ability to automatically initiate, upon address verification, an C address inquiry to search for associated premise information in CAD. 295 Ability to search for premise information based on: 296 Address C 297 Sub-address (e.g., unit number, building floor, apartment number) C Premise Hazard searches are based on proximity. 298 Partial address information (e.g., all addresses with apartment 14) C Premise Hazard searches are based on proximity. 299 Block ranges C 300 Current business name C 301 Historic business name (unlimited number) C 302 Common place names C 303 Intersections C 304 Radius from an address/location C 305 Polygon search on map N 306 Ability to search for premise information on locations not associated C with incidents. Page 14 of 48 May 10, 2022 Item #11 Page 542 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Premise history will appear after the address 307 Ability to automatically show premise history related to a current A has been verified. The display of this incident (over an agency defined period of time). information does not obstruct the work of the dispatcher. 308 Ability to indicate the number of past incidents at a location. C Ability to retrieve and attach to a CAD call any information 309 associated with the premise (e.g., pre-plan information, previous C calls for service). Ability to provide users with the choice of automatically or manually 310 including a hyperlink to any attachment associated with a location C (e.g. floor plans). The PremierOne CAD map will.display all 311 Ability for map to display all known hazards within a user-defined C known hazards related to the incident. The radius. radius/proximity is defined by the System Administrator. Ability to record in the incident history that premise history has PremierOne CAD requires an 312 been viewed by the user. C acknowledgement for Priority/Critical Premise Hazard alerts. Ability to recall any incident or premise history that has been viewed 313 (e.g., does not allow for only one time view of premise history or C incident). Ability for premise information to be available to user but not 314 prevent operator from continuing current work (e.g., window does C not cover entire workstation screen). 315 Incident Scheduling 316 Ability to enter incidents scheduled for dispatching at a later time, C maintaining the original time of entry. 317 Ability to identify the user that creates a scheduled call for service C Information stored in the audit log. within the scheduled call. 318 Ability to visually differentiate a scheduled call from a standard call when the scheduled call populates the pending call queue. 319 Ability to modify incidents scheduled for dispatching at a later time, C maintaining the original time of entry. 320 Ability to generate a call for service at specified intervals (e.g., N directed patrol 5 hours after the last directed patrol left). Page 15 of 48 May 10, 2022 Item #11 Page 543 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 321 Ability to cancel incidents scheduled for dispatching at a later time maintaining the original time of entry. 322 Ability to query all scheduled incidents (including cancelled scheduled incidents). 323 Ability to schedule an incident for a specific unit. 324 325 326 Ability to require an acknowledgement of the scheduled incident from a unit. Ability to issue automated reminders prior to scheduled events maturing and appearing in the pending queue. Ability to provide timers to notify users of a scheduled call at a predefined amount of time prior to the scheduled incident. Ability for scheduled incident to automatically enter the pending 327 queue. 328 Ability for officers to self-dispatch to scheduled incidents. Dispatching 330 CAD Incident Retrieval 331 Ability to alert a dispatcher to the arrival of a new incident via: 332 Audible alert 333 Visual alert 334 Ability to alert a dispatcher to the arrival of new incident information via: 335 Audible alert 336 Visual alert 337 Ability to visually differentiate updated call information from previously entered data. Ability to indicate whether the updated information has been 338 viewed by the primary dispatcher {e.g., font changes color after viewed, etc.). 339 Ability to retrieve a CAD incident and review all available information already entered up to the point of incident retrieval. 340 Ability to sort pending incidents by: 341 Priority 342 Location C C C C C C C C C C C C C N C C C The acknowledgement from the mobile unit is a timestamp process from the user. Page 16 of 48 May 10, 2022 Item #11 Page 544 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 343 Incident type C 344 Time in pending queue C 345 Beat number C 346 Incident number C 347 Ability to keep incidents in pending queue indefinitely. C Ability to forward an incident to another dispatcher (example: 348 "advise only" incidents, second dispatcher does not need to C dispatch resources for the incident). 349 Resource Recommendation 350 Ability to automatically provide appropriate resource recommendations based on any combination of: 351 AVL location C 352 Beat/station location responsibility C 353 Closest unit taking into account: 354 Natural boundaries C 355 Obstacles C 356 Traffic C 357 Speed limits C 358 Street network C 359 Street direction C 360 Equipment availability C 361 Incident location (e.g., unique response for specific location) C 362 Incident type C 363 Incident priority C 364 Occupancy type (e.g. residential, office building) C 365 Pre-defined response plans (response area plan) C 366 Special conditions (e.g., heightened response) C 367 Special equipment required C 368 Special skills units required C 369 Type of units required C 370 Number of units required C 371 Unit status C Page 17 of 48 May 10, 2022 Item #11 Page 545 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements ·esponse Cod Comments Ability to support numerous resource recommendation algorithms 372 based on agency defined parameters (e.g., priority 1 calls are C dispatched according to closest available unit and all other calls are dispatched based on beat assignments). Ability to prioritize unit response based on incident type so that 373 appropriate units are automatically recommended and/or C dispatched in priority order. 374 Ability to re-recommend closest units when a new unit comes into service. C 375 Ability to alert dispatcher when a new unit becomes available. C 376 Ability when upgrading an incident, for new unit recommendations C to take into account units already on-scene. Ability for system to update the unit recommendation if user makes 377 relevant incident information changes (e.g., type, location, alarm C level). 378 Ability to log recommendation overrides in the audit trail (e.g., log C recommended units versus dispatched units). 379 Ability for dispatchers to supplement a resource recommendation C with an additional unit and/or unit type. 380 Ability to visually identify whether a civilian ride-along is associated C with a unit. 381 Ability to visually identify whether a trainee is associated with a C unit. 382 Response Plans 383 Ability to develop response plans based on: 384 Geographic area (beat, sector, etc.) C 385 Address C 386 Multiple response route configuration (e.g., divided highway). C 387 Time of day C 388 Call type C 389 Resource availability C 390 Ability to assign a single response plan with multiple call types. C 391 Ability to include multiple agencies in response plans. C 392 Ability to generate temporary response plans. C Page 18 of 48 May 10, 2022 Item #11 Page 546 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 393 Ability for user to override response plan recommendation. C 394 Ability to load a new response plan without stopping or pausing C application operations. 395 Ability for a communications supervisor to update the response C plans (e.g., without assistance from technical support or vendor). 396 Resource Determination 397 Ability to bring up a list of special skills/equipment for: 398 All personnel logged on C 39.9 A selected person C 400 Unit C 401 Ability to identify all personnel with a specific skill (e.g., language, training) by: 402 Logged on and available C 403 Logged on and not available (e.g., on another incident) C 404 Not logged on C 405 Ability to display potentially available resources based on unit status: 406 Assigned to a CAD call C 407 Assigned to a CAD call with a lower priority C 408 Unassigned C 409 Resource Dispatch 410 Ability for dispatcher to select and assign/re-assign recommended units using any of the following methods: 411 Command line entry C 412 Function key C 413 Mouse (drag and drop onto map) C 414 Ability to dispatch units by: 415 Accepting the proposed application recommended units C 416 Selecting and dispatching units other than those recommended by C the application 417 Selecting some, but not all, of the recommended units C 418 Ability to log recommendation overrides in the audit trail (e.g., C recom'mended units and dispatched units). Page 19 of 48 May 10, 2022 Item #11 Page 547 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 419 Ability to automatically assign the initial unit dispatched as the C default primary unit. 420 Ability for CAD to do the following upon dispatch: 421 Assign the recommended or requested units C 422 Remove the incident from the pending queue C 423 Send the incident to the assigned unit's mobile computer C 424 Start the status timers C 425 Update the status display C 426 Ability to dispatch more than one unit at a time to the same call. C 427 Ability to assign or add multiple units to an incident with a single C command. 428 Ability to assign a unit to an incident to which it was not originally C recommended. PremierOne Mobile users can manually 429 Ability to provide dispatcher notification that dispatches have been A acknowledge receipt of incident information on successfully delivered. their MDT through a timestamp. 430 Ability to resend a dispatch to the originally dispatched unit. C 431 Ability for primary dispatcher to be the only user that can dispatch a C call. 432 Ability for any authorized user to dispatch a call. C 433 Field-Initiated Calls for Service 434 Ability for field personnel to initiate a call for service from the C PremierOne Mobile meets this requirement as mobile computer (e.g., traffic stop). long as the user permissions is correct. 435 Ability for Dispatchers to add additional units to a self-initiated C PremierOne Mobile meets this requirement as incident. long as the user permissions is correct. 436 Ability for units to add themselves as additional units to a self-C PremierOne Mobile meets this requirement as initiated call based on call type. long as the user permissions is correct. 437 Ability to capture AVL coordinates when field personnel initiate a C PremierOne Mobile meets this requirement as call for service from the mobile computer. long as the user permissions is correct. 438 Ability to capture unit ID number when incidents are initiated by a C PremierOne Mobile meets this requirement as unit in the field. long as the user permissions is correct. 439 Ability to geovalidate addresses of self-initiated incidents. C PremierOne Mobile meets this requirement as long as the user permissions is correct. Page 20 of 48 May 10, 2022 Item #11 Page 548 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 440 C PremierOne Mobile meets this requirement as Ability for dispatcher to link a field-initiated call to another incident. long as the user permissions is correct. 441 Ability to use one command line to enter a field-initiated incident C PremierOne Mobile meets this requirement as and place the initiating unit on-scene. long as the user permissions is correct. 442 Ability to provide dedicated fields to record the following information when a unit is placed in a traffic stop status: 443 Location of the stop C PremierOne Mobile meets this requirement as lonq as the user permissions is correct. 444 Number of occupants in the vehicle C PremierOne Mobile meets this requirement as long as the user permissions is correct. 445 Vehicle license plate C PremierOne Mobile meets this requirement as lonq as the user permissions is correct. 446 State of registration C PremierOne Mobile meets this requirement as long as the user permissions is correct. 447 Vehicle identifier (make, model, color) C PremierOne Mobile meets this requirement as long as the user permissions is correct. 448 Driver information C PremierOne Mobile meets this requirement as lonq as the user permissions is correct. 449 C PremierOne Mobile meets this requirement as Ability to limit field self-initiated calls to specific call types. long as the user permissions is correct. 450 Ability to notify dispatcher of any self-initiated call for service. C PremierOne Mobile meets this requirement as lonq as the user permissions is correct. 451 Unit Assignment to CAD Incident 452 Ability to update unit status to associate the dispatched unit or units C with the CAD incident. 453 Ability for the dispatcher to assign a unit to be the primary unit for C an incident. 454 Ability for dispatcher to change the primary unit during an incident. C 455 Ability for dispatcher to change the primary unit after closing an C incident. 456 Ability to record the change of primary unit in the incident record. C 457 Ability to take a unit off a call and reassign the unit to a new call via: Page 21 of 48 May 10, 2022 Item #11 Page 549 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 458 Single command C 459 Drag and drop C Ability for a dispatched call for service to return to the pending 460 queue if a unit is reassigned prior to the assigned call being C dispositioned. 461 Ability to use one command to both dispatch and put "on scene" C field personnel (e.g., if field personnel is "out with another unit"). 462 Ability to hold an incident for a specific unit. C Call stacking allows incidents to be stacked aaainst a unit. 463 Ability to hold an incident for a period of time and remove it from C the pending queue in CAD and Mobile. Stacked calls are managed on a Stacked Incident Summary screen. From there the 464 Ability to automatically (without user intervention) notify the A dispatcher can allow a stacked incident to be dispatcher of a held incident when the unit becomes available. automatically dispatched once the unit is available or manually dispatched/swaooed/reassiqned. 465 Call Preemption 466 Ability to pull a unit off an incident and reassign the unlt to a new C incident. 467 Ability to return CAD incident to the pendlng dispatch queue if all C units are removed from an active incident. 468 Ability to visually indicate a preempted call (e.g., highlight last unit C assigned). 469 Ability to support a swap feature to allow two units to swap C incidents with a single command. 470 Call Stacking/Queuing 471 Ability to hold an incident for a specific unit. C 472 Ability to hold more than one incident for a given unit or resource C (call stacking). 473 Ability to automatically (without user intervention) notify the C dispatcher of a held incident when the unit becomes available. Page 22 of 48 May 10, 2022 Item #11 Page 550 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability for the agency to set time limits for stacked calls by priority 474 (e.g., a queue limit of two hours for priority 5 calls and one hour for priority 3 calls). 475 Ability for administrator to turn call stacking on and off. 476 Ability to stack calls based on call type. Unit Management 478 Unit Placement in Service 479 Ability to log one or more units on-duty/off-duty with a single command. 480 Ability to automatically assign a beat to a unit upon logon. 481 Ability to assign a unit to multiple beats. 482 Ability to modify a unit's assignment during a shift. 483 Ability to define a roster (e.g. squad, company). 484 Ability to place all units in a previously defined roster on or off-duty. 485 Ability to allow for a single unit exception when placing a roster on or off duty. 486 Ability to designate a unit available for only certain: 487 Call type 488 Ca II priority 489 Ability for units to log themselves into or out of service. 490 Ability to prevent units from logging themselves into and out of service. 491 Ability to indicate a unit does not have a mobile computer. 492 Assigned Unit Status Display 493 Ability to monitor an unlimited number of units. 494 Ability to display the following unit information: 495 Beat 496 Call type 497 Case number 498 Current incident number 499 Current location 500 Current status 501 Elapsed time in status C C C C C C C C C C C C C C C C C C C C C C C Page 23 of 48 May 10, 2022 Item #11 Page 551 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 502 Group C 503 Last known location C 504 Logged onto Mobile (Y/N) C 505 Original location C 506 Call priority C 507 Radio ID C 508 Special note or comments C 509 Special skills/training C 510 Home district C 511 Unit ID/call sign C 512 Unit type C 513 Vehicle number C 514 Ability to automatically update and display unit status data. C 515 Ability to sort displayed data by any unit information (e.g., shift, C incident, unit, location, status). 516 Ability to filter the units to be displayed in a single status monitor C (e.g., by beat, status, out of service (mechanical)). 517 Ability to visually differentiate, through color, text and/or symbols, unit status: 518 On CAD unit status display C 519 On map display C 520 Unit Activity Tracking 521 Ability to record all unit assignments. C 522 Ability to record all unit locations. C 523 Ability to record all unit status changes. C 524 Ability to record all elapsed time on a call. C 525 Ability to review unit status history within the CAD application. C 526 Ability to update location and note mileage for multiple stops. C 527 Ability to record multiple arrival times, including: 528 Arrival at a staging area C 529 Arrival at the incident location (e.g., room within a building} C 530 Arrival at the scene (e.g., general location) C 531 Ability to record multiple units arriving: 532 At one time (all at once) C Page 24 of 48 May 10, 2022 Item #11 Page 552 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements 'esponse Cod Comments 533 At different times Ability to place "at the scene" units that were not originally 534 dispatched to the call. 535 Ability to assign (potentially multiple) units to a specific location which is different from the incident location. 536 Ability for a dispatcher to change the location of a unit at any time while the unit is still assigned to an incident. Ability to update the location of a unit without altering the original 537 incident location. 538 Status Monitoring 539 Ability to initiate status changes via the following methods: 540 Data fields 541 Function key 542 Mouse click (e.g., screen icon) 543 Ability to automatically notify users monitoring or displaying the incident that information has changed via a visual alert. 544 Unit Clearance Ability to clear one unit from a CAD incident while allowing the 545 other assigned units to remain on the call. 546 Ability to select any number of units to clear from CAD incident. 547 Ability to clear all units simultaneously from a CAD incident. Ability to require a disposition to be entered prior to clearing the 548 primary unit from a CAD incident. Incident Management 550 CAD Call Display Ability to monitor an unlimited number of calls for service. (If 551 limited, indicate the maximum in the "comments" field.) 552 Ability to dynamically display (e.g., automatically update) incident status data in a summary window (status monitor). C C C C C C C C C C C C C C C Each unit status timestamp can store a unit location, separate from the incident location. Each unit status timestamp can store a unit location, separate from the incident location. Each unit status timestamp can store a unit location, separate from the incident location. A screen icon status change is not available. However, other mouse click functionality such as right-click to a status sub-menu can initiate a status chan e. The data available for display within a status monitor window is limited by the data applicable for that window type and 950 items. Page 25 of 48 May 10, 2022 Item #11 Page 553 of 604DocuSign Envelope ID: EE0000EC-B 19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 553 Ability to review incident information in reverse chronological order. C Ability to display a window listing pending and holding incidents The PremierOne CAD Pending Queue will 554 C display pending and holding incidents from any entered from any CAD workstation. CAD workstation. 555 Ability to allow for an unlimited number of agency-defined incident C statuses. Status Monitors can display Pending and 556 Ability to view incident details of one or more incidents at a time. C Active incident details. Additional Status Monitors can be created for specific agency needs. 557 Ability to click on an active incident and highlight all assigned units C in the unit monitoring window. 558 Ability to show incidents on the CAD mapping display. C 559 Ability to accommodate multiple locations for one call. C 560 CAD Incident Updates 561 Ability to add new or additional information to a CAD incident. C 562 Ability for multiple operators to simultaneously modify the same C incident. 563 Ability to automatically identify (e.g., ID stamp) the operator adding C information to a call. 564 Ability to display the following information when additional information is added to an incident: 565 Time information was added C 566 ID of person entering information C 567 Ability to display new information added to the incident without C requiring the user to open the call. 568 Ability to simultaneously notify dispatcher and dispatched units of C updated information. 569 Reopening CAD Incidents 570 Ability to reopen closed incidents. C 571 Ability to reopen a closed call without losing previously recorded C date and timestamps. 572 Ability to assign units to reopened calls. C Page 26 of 48 May 10, 2022 Item #11 Page 554 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability for dispatchers to add comments to a CAD call record after 573 the call is closed without reopening the incident. 574 Ability to add a case number to a closed incident. 575 Ability to change the disposition code of a reopened call. 576 Ability to date and timestamp a reopened call multiple times. 577 Cross-Referencing Calls 578 Ability to cross-reference an unlimited number of active incidents. 579 Ability to cross-reference an unlimited number of closed incidents. 580 Ability to cross reference one call to another by inserting a hyperlink to the cross referenced call. Call Disposition 582 CAD Incident Cancellation 583 Ability to cancel an incident with a single command. 584 Ability to mandate that the user enter a reason for canceling an incident prior to the system executing the command to cancel. Ability to automatically remove the incident from the pending or 585 active incidents queue and add the disposition (e.g., cancelled) upon execution of a command canceling an incident. Ability to automatically clear all dispatched units from the incident 586 upon incident cancellation (e.g., upon invoking the cancel command). 587 Disposition Recording 588 Ability for.the agency to define disposition codes. 589 Ability to differentiate between an initial disposition and final disposition. 590 Ability to support an unlimited number of disposition types. 591 Ability to require a disposition code before an incident can be cleared. 592 Ability for either dispatchers or field personnel to enter the disposition code. C C C C C C A C C C C C C C C C PremierOne refers to this feature as Associated Incidents and requires the clicking of a button, rather than a hyperlink, to access the referenced call. Page 27 of 48 May 10, 2022 Item #11 Page 555 of 604DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to enter comments of an unlimited length with a disposition 593 code. 594 Report Initiation Ability to notify responding officer whether a report is required 595 based on disposition code. 596 Ability to transfer call for service data to: 597 RMS 598 Report writing application 599 Ability to transfer call for service data: 600 Upon transfer to dispatcher 601 Upon incident closure 602 On demand (i.e., manual initiation of transfer) 603 CAD Incident Closure 604 Ability to close a call that does not require the dispatch of resources. Ability to enter a closing disposition code at the time of call creation 605 to avoid having the call appear in the pending queue (e.g., call is created and closed prior to the dispatching of resources). Ability to change an incident disposition after a call is closed, but 606 maintain a history of the original disposition. Ability to clear more than one selected unit from an incident while 607 leaving one or more selected units on the incident. Ability to clear a single unit from an incident without clearing other 608 assigned units from the incident. 609 Ability to clear multiple units without closing the incident. 610 Ability to clear multiple units with a single disposition. 611 Ability to require a disposition prior to allowing a call to be closed. Ability to close an incident when the final unit is cleared from the 612 incident. 614 application. C C C C C C N C N C C C C C C C Page 28 of 48 May 10, 2022 Item #11 Page 556 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 615 Ability to select multiple map layers for display, limited only by the C number of available map layers. 616 Ability to display the following on the map: 617 Location of 9-1-1 caller C 618 Location of all pending and active 9-1-1 calls C 619 Incident location during address verification C 620 Units based on AVL or last known locations (regardless of status) C 621 Ability to select units to display on map by user-defined criteria including, but not limited to: 622 Beat C 623 Incident number C 624 Incident type C 625 Status C 626 Type C 627 Unit ID C 628 Ability to pull up a call for service and have it automatically show up C on the map. 629 Ability for users to prevent the map from automatically zooming to N an active call for service. 630 Ability to zoom in and center map display on: 631 Incident location during address verification C 632 CAD incident in active window C 633 Last known location of a selected unit (AVL or unit status) C 634 Vehicle activating emergency button C Ability to click on a unit and follow it on the CAD map at a user-635 defined zoom level and maintain the level of zoom as the CAD map C is updated. Ability to prevent the zoom level from automatically modifying 636 during an active incident (e.g., not automatically zooming out when C new units are added). 637 Ability to update unit status from the CAD map. C 638 Ability to click on an incident on the CAD map and review incident C information. Page 29 of 48 May 10, 2022 Item #11 Page 557 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 639 Routing 640 Ability to provide directions to an incident from a unit's last known C location or, if available, current location based on AVL. 641 Ability to adjust routing recommendations based on closed streets. C 642 Ability for operational user to close streets by clicking on a specific C area (e.g., street, hundred block area) from the CAD map. 643 Ability for user to define an expected duration for street closures. C 644 Ability to alert user when the expected duration for a street closure C has expired. 645 Ability to push closed street information to mobile computers. C 646 Ability to push all map updates to the Mobile map. C 647 Ability to project anticipated response times between two points on a map. C 648 Ability for dispatcher to view the quickest route (based on time) C from dispatched unit location to incident. 649 Ability for dispatcher to view shortest route {based on mileage) C from dispatched unit location to incident. 650 Ability to incorporate live traffic conditions into routing N recommendations. 651 Perimeters 652 Ability to create perimeter locations by drawing a perimeter on the C mapping display. Ability to create a perimeter by identifying the location and requisite The user can click on the center of the circle to be drawn on the map then specify a radius, if 653 perimeter size (e.g., 300 yards around incident location) and have A needed. the perimeter location automatically generated. 654 Ability to display the drawn perimeter on the map and have it C displayed for all responding units on their Mobile computers. 655 Ability to dispatch units to perimeter locations. N 656 Ability for units to place themselves on a designated perimeter N location. Page 30 of 48 May 10, 2022 Item #11 Page 558 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 657 Ability to annotate the map. 658 Ability for a user's annotated map to be shared with other users. Automatic Vehicle location (AVL} 660 Ability to support the use of a continuous, real-time AVL system. 661 662 663 Ability to support location technology outside of vehicle (e.g., on the erson, device other than MDT, etc .. Ability to automatically refresh current vehicle location at a enc -defined time and/or distance intervals. Ability to alert agency defined users if AVL data is not successful! transferred at the a enc defined ollin rate. 664 Ability to turn AVL on/off by: 665 Agency 666 Unit Ability to default to agency-defined defaults for dispatching when 667 AVL is turned off. 668 Ability to automatically mark a unit on-scene when it comes within a certain number of feet of the incident location. 669 Ability for the agency to define what constitutes on-scene. 670 Ability to prevent use of on-scene function if unit is not within an agency-defined radius of incident. 671 Ability to log the specific X/Y coordinate from where the unit was dispatched prior to responding to an incident. C C N C C A A A C N N N A Supplemental location description can be identified to give further information about the incident location APX radios emergency, PremierOne Mobile AVL units can be filtered from the CAD map display by their agency, units, and vehicle es. AVL units can be filtered from the CAD map display by their agency, units, and vehicle es. As it pertains to automatically marking a unit on scene, there are no provisioning options to define a unit as on-scene within a certain radius of the incident location. PremierOne CAD logs an AVL units X/Y coordinates based on the GPS reporting cadence. This data can be used to determine the unit's location around the time of dispatch, however like! not at the exact time. Page 31 of 48 May 10, 2022 Item #11 Page 559 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 672 Ability to generate reports from AVL data, including: 673 Vehicle route 674 Speeds along the route 675 Ability to provide an AVL playback utility based on: 676 Date 677 Time 678 Unit 679 Ability to export AVL playback data in common file type. Towed Vehicles 681 Contractor Rotation List 682 Ability to support an automated contractor rotation list. Ability for the application to recommend a contractor based on any 683 combination of the following: 684 Equipment Required 685 Type of tow 686 Order in Rotation 687 Incident Location 688 Time of day (e.g., hours of operation) 689 Agency 690 Ability to automatically place a contractor at the end of the rotation list after selected for service. 691 Ability to assign a contractor based on: 692 Date range 693 Da of month 694 Time of da 695 Ability to record that a contractor was selected from the service rotation list. 696 Ability to recommend the next available contractor if the initial contractor Is unavailable. 697 Ability to record reason why a contractor was not selected. 698 Ability to record contractor response. 699 Ability to temporarily remove a contractor from the list for an agency-defined length of time. C C C C C N C C C C C C C C N N N N C C C C The user is presented with a dropdown list of action codes for the ro osed contractor. Page 32 of 48 May 10, 2022 Item #11 Page 560 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 700 Ability to place contractor at top of list if incident is cancelled by the agency. 701 702 703 Ability to override contractor recommendation. Ability to enter a contractor that is not part of the rotation. Ability for all actions regarding the contractor rotation and selection to be associated with an incident record. 704 Towed Vehicle History 705 Ability to attach tow history to a call for service record. 706 Ability to document reason for the tow. 707 Ability to associate multiple vehicles with a single tow incident. 708 Ability to track the total number of vehicles towed per incident. CAD Reporting and Query Features 710 CAD Reporting and Analysis 711 Ability to provide a native reporting tool that can: 712 713 Create CAD reports based on multiple operational data fields in the CAD database 714 Ability to generate the following standard reports from within the CAD application: 715 Incident analysis by day of week 716 Incident analysis by hour of day 717 Incident analysis by day of week and hour of day 718 Incident analysis by geographic area 719 Incident analysis by shift 720 Incident analysis by beat 721 Incident analysis by call type 722 Incident analysis by disposition 723 Incident analysis by workstation 724 Incident analysis by call-taker 725 Incident analysis by dispatcher 726 Incident analysis by priority code 727 Incident analysis by geographic area by hour of day 728 Incident analysis by unit 729 By dispatcher: A C N C C C C C C ·C C C C C C C C C C C C C C C The user must cancel the contractor before the incident is closed to put the contractor on the to of the list. Page 33 of 48 May 10, 2022 Item #11 Page 561 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 730 Time from call receipt to call entry for all priority levels, by incident C number 731 Time from call entry to call dispatch for all priority levels, by C incident number 732 Time from dispatch to on-scene for all priority levels, by incident C number 733 By call center: 734 Time from call receipt to call entry for all priority levels C 735 Time from call entry to call dispatch for all priority levels C 736 Time from dispatch to on-scene for all priority levels C 737 By date range: 738 Time from call receipt to call entry for all priority levels C 739 Time from call entry to call dispatch for all priority levels C 740 Time from dispatch to on-scene for all priority levels C 741 False alarm reports C 742 Fractile reports C 743 Fractile reports by unit C 744 Processing time by method of call receipt C 745 Response times by geographic area C 746 Response times by type of call/priority C 747 Response times by original call destination C 748 Response times by assigned unit C 749 Total and average time on call -by day of week C 750 Total and average time on call -by geographic area C 751 Total and average time on call -by hour of day C 752 Total calls for service by: 753 Date or date range C 754 Disposition C 755 Time of day C 756 Location C 757 Total incidents by date by nature or disposition C 758 Any combination of the above C 759 Ability to provide an analytical tool that reviews workload by, but not limited to: Page 34 of 48 May 10, 2022 Item #11 Page 562 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 760 Workstation N 761 Call taker/dispatcher N 762 Officer N 763 Ability to report on unavailability of field personnel resources. N 764 Ability to report on unavailability of equipment resources. N 765 Ability to account for unavailable resources in response time N calculations. 766 Ability to capture a snap shot, based on day and time parameters, C of: 767 A workstation C 768 General CAD system C Ability to generate, from within the CAD application, a daily listing of 769 incidents and personnel assigned to the incidents including, but not limited to: 770 Actual dispatch location C 771 Call taker/dispatcher ID C 772 Date/time received C 773 Disposition C 774 Field personnel name C 775 Field personnel ID C 776 Incident location C 777 Incident number C 778 Ability to print audit report of changes to incident records including: 779 Transaction type (deletion, edit, etc.) C 780 Unit ID C 781 Workstation/terminal ID C 782 Before and after value C Ability to generate a list of incidents to be shared with the public List of incidents can be generated and shared 783 C with public but would need clarification on based on agency-specific business rules. agency-specific business rules. 784 Ability to generate a report containing a summary of incidents for an C agency-defined period of time for distribution to the public. Page 35 of 48 May 10, 2022 Item #11 Page 563 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 785 Ability to schedule a report to populate a public-facing site with N agency-defined incident data. 786 Ability to schedule a report with agency-defined incident data to be N automatically sent to an agency-defined set of users . 787 CAD Queries 788 Ability to query the following databases from within CAD: 789 RMS C 790 CLETS/NCIC C 791 DMV C 792 All databases simultaneously C 793 Ability for subject query returns to include associated photos, if available in the following databases: 794 RMS C 795 DMV C 796 CALPhoto C 797 Ability to query call for service records based on: 798 Date range C 799 Time range C 800 CAD Incident number C 801 Unit ID C 802 Officer name/ID C 803 Call taker ID· C 804 Dispatcher ID C 805 Reporting party name C 806 Person of interest C 807 Location C 808 Any location in an incident C 809 Block range for a location C 810 Radius from a location C 811 Polygon area from a location C 812 Any operational data element in the call for service record C 813 Any combination of the above C Page 36 of 48 May 10, 2022 Item #11 Page 564 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to populate the query mask with data in the incident record 814 without cutting and pasting (e.g., with a function key or one or two key strokes): 815 Person Information C 816 Vehicle Information C 817 Ability to automatically query all of the following databases upon single query of a name: 818 RMS (Master Indices) C 819 CLETS/NCIC C 820 DMV C 821 Ability to automatically query the license plate against the RMS, C DMV, LPR and CLETS databases when a unit is on a vehicle stop. 822 Ability to automatically run a registered vehicle owner upon return C of a license plate query. 823 Ability to query: 824 Initial call type C 825 Final call type C 826 Ability to query and view the following by any public safety boundary layer (beat, sector etc.): 827 Active calls C 828 Assigned calls C 829 Priority calls C 830 Waiting (pending) calls C 831 Ability to query unit history by any combination of: C 832 Date and time range (e.g., start and end date and time parameters) C 833 Call type C 834 Unit ID C 835 Badge number C 836 Ability to query resource availability by: 837 Dispatch group C 838 Geographic area (e.g., beat, sector) C 839 Special skills C Page 37 of 48 May 10, 2022 Item #11 Page 565 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements ·esponse Cod Comments 840 Unit types (e.g., patrol units, investigations) 841 Ability to query unit status by: 842 Date and time range 843 Dispatch group 844 Badge number 845 Geographic area (e.g., beat, sector) 846 Incident type 847 Unit ID 848 Unit types (e.g., patrol units, investigations) Ability to automatically attach query returns to the unit and/or 849 incident history when a query includes reference to a unit or incident. 850 Ability to sort query results by any criteria (e.g., most recent to oldest, by priority). 851 Ability to attach query entries to a unit or incident history (e.g., CLETS entries). 852 Ability to limit query returns to an agency-defined number. 853 Ability to hyperlink query returns to incident records. Ability to attach query returns from external systems into the call 854 notes via a single keystroke by: 855 Attachment (file) 856 Hyperlink 857 Ability to send query results to a user's mobile application. 858 Ability to print query returns with a single keystroke. 859 Ability to redact query returns prior to printing. Messaging 861 General Messaging Features 862 Ability to support a messaging system that can transmit messages to and from mobile and desktop workstations. Ability to send messages to a user who is not logged into CAD and 863 cache that message for retrieval when the user logs onto CAD. 864 · Ability for message server to continuously attempt to deliver a messa e until received and confirmed. C C C C C C C C C C C C C N N C C N C C C Page 38 of 48 May 10, 2022 Item #11 Page 566 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 865 Ability to support a minimum of the following messaging functions to and from any CAD address: 866 Desktop-to-desktop messaging C 867 Desktop-to-dispatch messaging C 868 Desktop-to-unit messaging C 869 Unit-to-desktop messaging C 870 Unit-to-unit messaging C 871 Ability to display the following identifiers within a message: 872 Sender name/ID C 873 Sender date C 874 Sender time C 875 Sender workstation ID C 876 Receiver name/ID C 877 Receiver date C 878 Receiver time C 879 Receiver workstation ID C 880 Receiver unit ID C 881 Ability to assign a priority to a message (e.g., routine, urgent, C emergency). 882 Ability to change a priority assigned to a message (e.g., routine to C urgent or emergency). 883 Ability to store messages for later viewing. C 884 Ability to purge text messages after an agency-determined period of C time. 885 Ability for messages to be sorted by most recent or first received. C 886 Ability for agency to configure the display of emergency key C notification. 887 Sending Messages 888 Ability to create easily accessible agency defined message forms for C specific message types. 889 Ability to create, edit and save message groups. C 890 Ability to create a dynamic message group consisting of all logged on users. C Page 39 of 48 May 10, 2022 Item #11 Page 567 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 891 Ability to send broadcast messages. C 892 Ability to reply all to broadcast messages. C 893 Ability to select a recipient from the unit status window within CAD. C 894 Ability for users to select an unlimited number of people as part of a message group. C 895 Ability to reply all to group messages. C 896 Ability for agency to define message character limitations. C 897 Ability to add to a message before forwarding to another user. C Ability to enter unlimited narrative with wrap-around feature. (If 898 characters are limited, indicate the maximum in the "comments" C section.) 899 Ability to automatically populate the "To" field on the message mask C when selecting recipients. 900 Ability to select recipient by: 901 Name C 902 Unit ID C 903 Badge Number A Badge number is not a dedicated field but could be searched from the Notes field. 904 Terminal ID C Ability to select a recipient by a single command to create a 905 message (e.g., double click on a logged on user and message screen C pops up). 906 Ability to attach files to messages, including but not limited to: 907 MS Office C 908 PDF C 909 JPEG C 910 AVI C 911 WAV C 912 MP3 C 913 MP4 C 914 Ability to embed photos in messages. C 915 Ability to set agency-defined file size limit. N 916 Ability to automatically compress and resize media to comply N with agency defined file size limits. Page 40 of 48 May 10, 2022 Item #11 Page 568 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 917 Ability to send a message to all units handling a specific incident. C Ability to transmit a reply message to the originator of a currently 918 displayed message without having to reenter the originator's C address. 919 Ability to transmit a "reply all" message to multiple recipients that C were part of the originator's message group. 920 Ability to forward a message. C 921 Ability to create messages that are retained in the system and sent C at pre-specified times. 922 Ability to provide a notification for delivery of messages to the C device. 923 Ability to provide a notification for non-delivery of messages. C 924 Ability for a user to remove himself or herself from a message C thread. 925 Ability to recall an unread message. C 926 Receiving Messages 927 Ability to notify receiver via an audible and/or visual flag that a new C message has arrived in mailbox. 928 Ability to prevent incoming messages from interfering with current C work. 929 Ability to notify receiver of an unread message after an agency N defined time period. 930 Ability to notify receiver of total number of unread messages. C 931 Ability to provide a visual distinction between the following: 932 External messages N 933 General messages C 934 System messages N 935 Query returns C 936 Unread messages C 937 High priority messages C 938 Ability to move high priority messages to the top of a user's C message inbox. Page 41 of 48 May 10, 2022 Item #11 Page 569 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAO/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 939 Ability to identify high priority messages by type of priority (e.g., felony warrant return versus user-defined urgency). 940 Ability of the receiving user to enter a single keystroke command to retrieve and display the message. 941 Ability for messages to be queued in an "inbox" for later viewin at the convenience of users. 942 Ability to query message logs by agency-defined criteria (e.g., date/time range, sender, recipient, device). 943 Abilit to note time opened/read b receiver. 944 Ability to queue and displa message waiting b priority. 945 Abilit to clear a message from the queue. Ability to establish different retention limits for messages 950 containing different types of media (e.g., 9-1-1 recordings, video. 951 Ability for supervisors to search messages by a text string (e.g., to identify inappropriate language use) 952 Ability to save message logs for an agency-determined period of time. 953 Ability to purge message logs after an agency-determined period of time. CAD System Administration 955 CAD Table Maintenance 956 Ability for CAD fields to default to agency-defined values. C C C C C C C C C C N N C A C C F6 Message searches are by mailbox, date range, attachments, message text, subject, from address, to address, cc, bee, and labels. The saving of message logs is based on system provisioned mailbox folder sizes and ur e rules at lo out. The provisioning of default CAD fields does not apply to every available field on the incident form. For example, pertinent default codes can be provisioned for a Traffic Stop incident form or the call source code for E9-1-1 or non-emer enc line calls. Page 42 of 48 May 10, 2022 Item #11 Page 570 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 957 Ability to include, at a minimum, the following data tables: 958 Call source (e.g., officer-initiated, 9-1-1, 10-digit) C 959 Call types and priorities C 960 Commands C 961 Command aliases C 962 Devices C 963 Dispositions C 964 Equipment C 965 Vehicle ID C 966 Event error logs (so vendor can identify and troubleshoot errors) C 967 Location C 968 Common place names C 969 Landmarks C Same as common places 970 Response plans N 971 Patrol and command area definitions N 972 Personnel, including emergency contact information and C Address Book current assianment 973 Series (incident number sequence, etc.) C 974 Street alias file N This is part of GIS 975 Table size N 976 Tow/contractor rotation C 977 Timers C 978 Unit status types (i.e., assigned, unassigned, assigned but available) C 979 Users C 980 Special skills C 981 Terminals C 982 Units C 983 Reoortina District N 984 Beat (time-based) N 985 Agency-defined N 986 Ability to accommodate agency-defined unit identifiers. C 987 CAD Configuration Page 43 of 48 May 10, 2022 Item #11 Page 571 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 988 Ability to configure commands (e.g., V = vehicle stop). C 989 Ability to create agency-defined data entry screens. N 990 Ability to configure the field entry sequence. N 991 Ability to configure status code colors. C 992 Ability to create conditional fields. N This capability is provided on a limited number of fields. 993 Ability to create mandatory fields. N This capability is provided on a limited number of fields. 994 Ability for agency to add data elements on any screen. N 995 Ability for agency to change data elements on any screen. N 996 Ability for agency to configure alerts: 997 Associated message displayed C 998 Aµdible indicator C 999 Visual indicator C 1000 Premise File Maintenance 1001 Ability to update/create CAD premise history files. C 1002 Ability to automatically update premise history when an incident occurs. C 1003 Ability to capture the following information when creating premise history: 1004 Date and time stamp C This information is not a dedicated field in the 1005 Date of incident A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1006 Disposition A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1007 Type of incident A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1008 Incident number A Premise Hazard record but can be added to the Comments field. 1009 Narrative text of unlimited length (if limited, indicate maximum in C the "comments" field) Page 44 of 48 May 10, 2022 Item #11 Page 572 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements ·esponse Cod Comments 1010 Ability to capture and maintain specific premise information, including but not limited to the following: 1011 Emergency contact information C 1012 Hazardous conditions (e.g., officer responder safety) C This information is not a dedicated field in the 1013 Chemicals A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1014 Medical information A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1015 Agency defined premise information A Premise Hazard record but can be added to the Comments field. 1016 Previous calls for service based on at least the following: 1017 Address/Location C 1018 Contact information C 1019 Date and time C 1020 Incident number C 1021 Incident type C Ability to capture and maintain specific premise information by 1022 groups of addresses (e.g., all apartments in an apartment complex, C all houses in a subdivision). Ability to capture and maintain specific premise information by Premise hazard area are supported. 1023 groups of addresses by polygon (e.g., all apartments in an C apartment complex, all houses in a subdivision). 1024 Ability to store premise information for a specific apartment C unit/suite number. 1025 Ability to store premise information for an agency-defined length of C time. 1026 Ability to purge premise information from a location (e.g., if it is C known that the tenant/owner generating the incidents has moved). 1027 Ability to archive premise information from a location (e.g., if it is N known that the tenant/owner generating the incidents has moved). Page 45 of 48 May 10, 2022 Item #11 Page 573 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to define valid date ranges for time limited premise A purge date can be provisioned for the time 1028 information at a given location (e.g., information valid between A limited premise information. 1 <start date> and <end date>). 1029 Ability to restart archived premise file information. N 1030 Ability to archive expired premise file information. C 1031 Ability to include in a premise record the following information when premise information is added or changed: 1032 Expiration date C 1033 Unit ID of person entering information A The PremierOne CAD user ID is stored on the Premise Hazard record. 1034 Ability to attach files to a premise record (e.g., floor plans, building C diagrams, special instructions). 1035 Ability to access files attached to a premise record: 1036 In CAD environment C 1037 In Mobile environment C 1038 Hazard File Maintenance 1039 Ability to enter hazards associated with: 1040 Persons C 1041 Specific locations C 1042 Address ranges C This information is not a dedicated field in the 1043 Vehicles A Premise Hazard record but can be added to the Comments field. 1044 Ability to define an unlimited number of hazard types. C 1045 Ability to record with an entered hazard: 1046 Expiration date C 1047 Time and date stamp at time of entry C 1048 ID of person entering information C 1049 Ability to assign expiration dates to hazards. C 1050 Ability to create lists of hazards by category C 1051 Ability to search hazards by: 1052 Date range C 1053 Hazard type C 1054 Location C 1055 Location range C Page 46 of48 May 10, 2022 Item #11 Page 574 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 1056 Ability to print hazards and hazard lists 1057 CAD Notes File Maintenance Ability to create an unlimited number of types of notes fields, 1058 including but not limited to: 1059 Gate codes 1060 Utility phone number 1061 Hospital phone numbers Communications Supervisor Support Ability for a communications supervisor to monitor system 1063 configuration and current staffing (e.g., who is signed-on, at what position, at what time, and with what responsibilities). 1064 Ability for a CAD workstation to be configured as a supervisor workstation upon logon of a user with a CAD supervisor profile. 1065 Ability for a supervisor to choose logon type (supervisor vs. dispatcher) upon workstation logon. 1066 Ability for a communications supervisor to monitor activity on any user workstation. 1067 Ability for supervisor to override actions taken by any other operator. 1068 Ability to notify dispatcher of any changes made by supervisor. 1069 Ability to identify dispatch origin (e.g., dispatcher or dispatch supervisor) of modifications. 1070 CAD Testing/Training Environment 1071 Ability to support a CAD testing/training environment that mirrors the functionality of the CAD production environment. 1072 Ability to support a CAD testing/training environment that mirrors the configuration of the CAD production environment. 1073 Ability to visually distinguish testing/training environments from production environments. 1074 Ability to designate any production workstation as a training workstation based on user log on. 1075 Ability for testing and training to occur without impacting the production environment. C C C C C C C C C C C C C C C C Page 47 of 48 May 10, 2022 Item #11 Page 575 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 1076 Ability to update testing/training system with historical data from C production system at agency defined intervals or upon demand. 1077 Ability to support a separate test E911 connection (or a canned N script of E911 information). 1078 Ability to support a separate test mobile connection (or a canned C script of mobile information). 1079 CAD Recovery Ability to retain and display last-known unit and incident status 1080 in the event of a catastrophic system failure (e.g., at the N workstation, remote external logging device or similar solution). Ability to load incidents from the backup environment into the 1081 production environment upon restarting system after a system N failure. 1082 Ability to reset numbering after CAD system has been restarted. C 1083 Ability to retain CAD numbering sequence after system has been C restarted. Ability to add incidents retroactively independent of incident Incident update tool allows you to move from 1084 number order or sequential time sequence (i.e., incident 15 may C inc# to inc# and doesn't require you to go in have occurred after incident 20) in the event that the CAD system is order. unavailable for a time. Ability to process retroactive incidents and assign incident numbers 1085 in the same manner as new incidents; the supervisor can override C the times associated with the incident. Ability to set aside a block of call for service numbers in the event of 1086 a catastrophic CAD failure to enable a manual workflow and C tracking. 1087 Ability to indicate in the audit trail that an incident was entered C retroactively. 1088 Ability to perform CAD catch-ups after system downtime, without C requiring users to log back in. Page 48 of 48 May 10, 2022 Item #11 Page 576 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments -General Mobile Data Computing Features 2 Ability for the system to automatically refresh without user C intervention, as new information becomes available. 3 Ability to receive call updates without moving the user out of the C current screen being viewed. 4 Ability to notify users that new information is available without C automatically refreshing the call for service screen. 5 Ability to log all mobile transactions with the following information: 6 Agency C 7 Date and time of transmission C 8 Location C 9 Mobile Terminal ID C 10 User ID C 11 Vehicle ID C 12 Ability to provide a visual alert if Mobile application loses C connection to CAD. 13 Ability to provide application functionality if disconnected from the network, including but not limited to: 14 Mobile map C 15 Dispatch commands C Commands can be performed on the mobile device, but not received from CAD. 16 Unit status updates C Unit status can be changed on the mobile device, but will not be communicated to CAD. 17 Self-initiated calls C 18 Ability to continuously attempt to reconnect to CAD system in C the event connectivity is lost. 19 Ability for users to pull software/files (e.g., code tables, updates) C on demand. PremierOne Mobile updates can be executed based on the Ability to support an automatic download of software/files (e.g., customers needs. User will get notified that updates are 20 C available and can acknowledge the update. The update will code tables, updates) at logon. take place in the background without interfering with ooerational oerformance. Page 1 of 24 May 10, 2022 Item #11 Page 577 of 604DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 21 Ability to schedule an automatic download of software/files (e.g., code tables, updates). 22 Ability to provide functionality on the following mobile devices: 23 Laptops 24 Tablets 25 iOS 26 Android 27 Windows 28 Smartphones 29 iOS 30 Android Ability to integrate actions taken on handhelds into MDT (e.g., 31 queries and returns performed on handheld appear on MDT when users return to vehicle, etc.) 32 Ability to accommodate the following screen orientations: 33 Portrait 34 Landscape 35 Ability for users to configure screen views, including but not limited to: 36 Fu II screen 37 Split screen 38 Single frame 39 Multiple frames on a single screen 40 Multiple frames on multiple screens (e.g., extended display) 41 42 43 Ability for users to freeze hot call information on the Mobile screen (suspect car, name, photo) without being interrupted by call updates. Ability to provide a visual indication of a new call if a user is active in a different window of the Mobile application. C C C C C C C C C N C C C C C C C C C PremierOne Mobile updates can be executed based on the customers needs. User will get notified that updates are available and can acknowledge the update. The update will take place in the background without interfering with o erational erformance. PremierOne Mobile could be extended to another display, but the application can not be split to display on multiple Page 2 of 24 May 10, 2022 Item #11 Page 578 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 44 Ability to maintain any work in progress (e.g., queries, updates to call notes, etc.) when: 45 User navigates away from page C 46 User is dispatched to a new call C 47 Ability to provide screen display formats that are consistent C across the application. 48 Ability for user to toggle between windows. C 49 Ability to view multiple windows at the same time (e.g., side by C side or cascade). so Ability for user to minimize or expand any window. C 51 Ability to support touch-screen functionality. C 52 Ability to support voice activated (voice command) functionality. N 53 Ability to support text-to-voice functionality. C 54 Ability to accept input from: PremierOne Mobile currently supports the Mag Stripe 55 3D barcode reader (e.g., driver's license, registration) N reader. PremierOne Mobile does not support requirement but could be considered for a future release. 56 Card swipe device C 57 Command entries on a command line C 58 Fingerprint reader N 59 Function keys (one touch keys) C 60 Point-and-click devices (i.e., mouse, trackball, touch pad) C 61 Ability for users to configure the display of their Mobiles, including: 62 Font color C 63 Font size C 64 Window size C 65 Window location C 66 Day/Night mode C 67 Ability to configure a default for the following application settings: 68 Audible message C 69 Audible tones C 70 Color C Page 3 of 24 May 10, 2022 Item #11 Page 579 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item It Mobile Data Computing Functional Requirements Response Code Comments 71 Ability to switch to/from Day/Night mode with one function key. C 72 Ability to completely black out mobile application screen. N 73 Ability to switch to/from blackout mode with one function key. N 74 Ability to store a user profile for mobile display configuration for C auto-configuration upon log on. 75 Ability to store multiple user profiles based on device (e.g., CF-N 33, CF-20, etc.). Ability for users to create a user-defined summary of call information to appear prominently at the top of the screen for The incident summary screen· can be modified by the 76 the duration of a call (e.g., anytime a suspect description is N System Administrator to meet the agencies needs. included, it would appear at the top of the screen if the user has selected that field). 77 Ability to allow users to return to application default settings. C 78 Ability for users to select a configuration scheme that C accommodates color-blindness. 79 Ability to support multiple on-screen button configurations (e.g., C left side, right side, top or bottom). 80 Ability to cut and paste from one application or window to C another. 81 Ability to configure the screen display with a combination of any of the following information during normal operations: 82 Availability of wireless connectivity C 83 Call status C 84 Communication verification and other Mobile operational status C indicators 85 Current unit C 86 Current unit status (regardless of who assigned the updated C status) 87 Current system date and time C 88 Incident number C 89 Case number (if provided) C Page 4 of 24 May 10, 2022 Item #11 Page 580 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 90 91 92 93 94 95 96 97 98 99 100 Message alert Radio talk group (if assigned) Screen name/description Unit ID User ID User name Vehicle location Ability to view multiple calls simultaneously (e.g., in different windows). Ability for user to configure how data is displayed (e.g., incident screen, unit screen), including but not limited to: Suspect information Location information 101 Premise history 102 Vehicle description 103 104 105 106 107 108 110 111 112 113 114 llS 116 Ability to configure the unit status screen display, including but not limited to: Filter by workgroup (patrol traffic, etc.) Sort by workgroup Filter by unit status So rt by unit status Ability to notify users that a software update is available for manual download. Function Keys/Commands Ability to support single keystroke commands. Ability to define sub-menus for buttons and function keys so they are based on legacy commands. Ability for agency to define keystroke shortcuts for: Common tasks (e.g., copy/paste) Status updates Form retrieval (e.g., NCIC call disposition) Ability to configure a Mobile button (tool bar or function key)_to launch any third-party program (e.g., MS Word). Emergency Key Functionality C N C C C C C C C C C C C C C C C C C C C C C Page 5 of 24 May 10, 2022 Item #11 Page 581 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 118 Ability to initiate an emergency message transmission from a C touch screen button or hot key. 119 Ability to automatically transmit the following information to agency-defined groups in an emergency situation: 120 Last known location C 121 Current location (with AVL) C 122 Current location (with GPS using smartphone) C 123 Reference to incident C 124 User ID C 125 User name C 126 Closest unit to the unit activating the emergency key C 127 Ability to configure emergency key to capture agency defined c· combination of above information. Ability to present the user initiating the emergency key with a 128 visible and audible indication that emergency key has been C activated prior to broadcast to other users. Ability to delay emergency key activation by an agency defined 129 period of time (e.g., two second pause before activation to allow C personnel to deactivate key if necessary). 130 Ability for Agency to configure where the emergency button C appears on the screen (e.g., fixed or floating). 131 Ability for dispatch to select which consoles receive C visible/audible alerts of emergency key activation. Ability to send to all Mobile and CAD users (except the sender) 132 an emergency notification with unit ID and location (if known) C when the emergency key is activated. 133 Ability to prevent emergency notification from appearing on the C sender's screen. 134 Ability for the following users to cancel activation of the emergency key: 135 User that initiated the emergency key C 136 Dispatcher C 137 Ability for the Mobile screen to revert to its prior view after the C user dismisses an emergency message. Page 6 of 24 May 10, 2022 Item #11 Page 582 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments Ability to automatically send location coordinates and unit ID 138 upon triggering an emergency key. Ability for system administrator to turn off emergency key 139 functionality by: 140 Agency 141 Device 142 User Mobile Logon/Logoff 144 Ability to require both user identification and password to logon. 145 Ability to support a single password sign-on to CAD, the Mobile and the o eratin s stem. Ability to require any agency-determined combination of the 146 following information to logon to the Mobile application: 147 Equipment 148 Password 149 Unit ID 150 Radio ID(s) 151 Status (e.g., in service, out-of-service) 152 Agency-defined 153 Ability for agency to set the time a Mobile can remain inactive before automatically logging out the user. 154 155 Ability for agency to define logon requirements (e.g., what data is required at time of logon). Ability to support multiple individuals or roles at logon (e.g., FTO, multi-officer vehicle, etc.) Ability for a resource to be logged on but not available for 156 service. Ability for a unit logged on to automatically default to "available" 157 status. Ability to save data entered into user logon fields that remains 158 the same from session to session (e.g., all information other than password). C C C C C N N C C C C C C C C C C Not operating system PremierOne Mobile requires minimum fields for entry upon logon, but this list can be expanded to meet agency needs. Page 7 of 24 May 10, 2022 Item #11 Page 583 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item II Mobile Data Computing Functional Requirements Response Code Comments 159 Ability for a user to logoff the system and save information on the Mobile including: 160 In-progress reports 161 Messages 162 Notes 163 Query returns 164 Ability to store the following until manually deleted by the user: 165 In-progress reports 166 Messages 167 Notes 168 Query returns Ability to support a user-initiated download of software/files at 169 logon without interfering with operational performance. 170 171 172 173 Ability to support an automatic download of software/files at logon without interfering with operational performance. Ability to separate Mobile logoff from designating status as off-shift. Ability for agency to define logoff requirements (e.g., what data is required at time of logoff). Ability to automatically notify CAD of logon/logoff. Ability for users to be logged onto multiple mobile sessions 174 simultaneously. Application Integration 176 Ability to view all incident information available in CAD on the Mobile. 177 Ability for Mobile users to view all AVL data available in CAD. 178 Ability to provide the same messaging features as the CAD application. 179 Ability for mobile status updates to be reflected in CAD. 180 Ability to receive dispatch alerts and/or indicators without losing current work. C C C C C This information is retrievable via PremierOne CAD C This information is retrievable via PremierOne CAD C This information is retrievable via PremierOne CAD C This information is retrievable via PremierOne CAD C C C C C C C C C C C Page 8 of24 May 10, 2022 Item #11 Page 584 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments Ability to receive messages and/or indicators without losing 181 current work. 182 Ability for alerts created in CAD to be made available to users in the Mobile environment. Messaging 184 General Messaging Features 185 Ability to support a messaging system that can transmit messages to and from mobile and desktop workstations. 186 Ability to display the following identifiers within a message: 187 Sender name/ID 188 Sender date 189 Sender time 190 Receiver name/ID 191 Receiver date 192 Receiver time Ability to send messages to a user who is not logged into the 193 mobile device and cache that message for retrieval when the user logs on. 194 Ability to store and forward messages transmitted or received if network connectivity is temporarily lost. 195 Ability to centrally log when a terminal is off network and where it was disconnected (to understand blackout areas in the City). 196 Ability for message server to continuously attempt to deliver a message until received and confirmed. 197 Ability for user to retrieve cached messages upon logon. 198 Ability to assign a priority to a message (e.g., routine, urgent, emergency). 199 Ability to change a priority assigned to a message (e.g., routine to urgent or emergency). 200 Ability to store messages for later viewing. 201 Ability for messages to be sorted by most recent or first received. C C C C C C C C C C C N C C C C C C Page 9 of24 May 10, 2022 Item #11 Page 585 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments Ability to alert users of agency-defined keywords or hot words 202 included in a message requiring the user to validate prior to N sending (e.g. message includes "gun"). 203 Ability for authorized users to cancel non-CLETS/NCIC text message returns. C 204 Sending Messages 205 Ability to create easily accessible agency defined message forms C for specific message types. 206 Ability to create and save message groups. C 207 Ability to create a dynamic message group consisting of all C logged on Mobile users. 208 Ability to send broadcast messages to all users. C 209 Ability for users to select an unlimited number of people as part C of a message group. 210 Ability for field users to create unique groups. C 211 Ability for field users to save unique groups to the user's N !Profile. 212 Ability for agency to define message character limitations. N 213 Ability to enter unlimited narrative with wrap-around feature. C 214 Ability to add to a message before forwarding to another C user. 215 Ability to automatically populate the "To" field on the C messaqe mask when selecting recipients. 216 Ability to select recipient by: 217 Name C 218 Group C 219 Call signs C 220 Unit ID C 221 Badge Number C Ability to select a recipient by a single command to create a 222 message (e.g., double click on a logged on user and message C screen pops up). 223 Ability to attach files to messages. C 224 Ability to embed photos in messages. C Page 10 of 24 May 10, 2022 Item #11 Page 586 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments Each agency may define Send and Receive size limitation 225 Ability to set agency-defined file size limit. C on PremierOne Mobile messages. This size limitation is applied to the entire message, not just the attachment. Ability to automatically compress and resize media to comply Each agency may define Send and Receive size limitation 226 C on PremierOne Mobile messages. This size limitation is with agency defined file size limits. aoolied to the entire messaqe not iust the attachment. 227 Ability to send a message to all units handling a specific incident. C Ability to transmit a reply message to the originator of a 228 currently displayed message without having to reenter the C originator's address. 229 Ability to transmit a "reply all" message to multiple recipients C that were part of the originator's message group. 230 Ability to forward a message. C 231 Ability to create messages that are retained in the system and C sent at pre-specified times. 232 Ability to provide sender with a notification for delivery of C messages to the device. 233 Ability to provide a notification to sender for non-delivery of C messages. Ability to provide a voice message functionality (e.g., messaging 234 application records sender's voice and transmits the message as N voice to recipient). 235 Receiving Messages 236 Ability to notify receiver via an audible and/or visual flag that a C new message has arrived in mailbox. 237 Ability to prevent incoming messages from interfering with C current work. 238 Ability to notify receiver of an unread message after an agency C defined time period. 239 Ability to notify receiver of total number of unread messages. C 240 Ability to provide a visual distinction between the following: 241 General messages C Page 11 of 24 May 10, 2022 Item #11 Page 587 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item II Mobile Data Computing Functional Requirements Response Code Comments 242 System messages 243 Query returns 244 Unread messages 245 Ability to identify high priority messages by type of priority (e.g., ' felony warrant return versus user-defined urgency). Ability of the receiving user to enter a single keystroke command 246 to retrieve and display the message. Ability for messages to be queued in an "in box" for later viewing 247 at the convenience of users. 248 Ability for authorized users to query message logs by agency-defined criteria (e.g., date/time range, sender, recipient, device). 249 Ability to note time opened/read by receiver in the message log. 250 Ability to note time delivered in the message log. 251 Ability to queue and display message waiting by priority. 252 Ability to clear a message from the queue. 253 Ability to retain a message in the queue. 254 255 256 257 258 Ability for supervisors to monitor messages. Ability to search messages by keyword. Ability to establish message data retention limits. Ability to establish different retention limits for messages containing different types of media (e.g., 9-1-1 recordings, video. Ability for authorized users to search messages by a text strin e. ., to identi ina ro riate Ian ua e use . 259 Ability to save message logs for an agency-determined period of time. 260 Ability to purge message logs after an agency-determined period of time. Mobile Mapping 262 Ability for map to function without wireless connectivity. Ability to manage map layers to minimize the amount of data 263 transmitted wirelessly. 264 Ability to support AVL functionality. C C C C C This is a button or Function key C C C C C C C C C N N N C C C C C Page 12 of 24 May 10, 2022 Item #11 Page 588 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 265 Ability to update unit and incident locations on map without C resetting the entire map. 266 Ability for map to function in the background and not supersede C other applications. 267 Ability to display compass direction between two user selected C points. Ability to configure map to dynamically turn and zoom in while 268 getting closer to destination based on location and direction of C the vehicle. 269 Ability for user to configure map to remain static and point north C based upon directions. 270 Ability to maintain incident location identifier on the map until C an agency-defined action (e.g., unit arrives on-scene, etc-.) 271 Ability to select n:iap layers for display (Satellite imagery, LPR C layers, etc.). 272 Ability for Mobile map to display the same common places that C exist in CAD. 273 Ability to display the following information on the map: 274 Active incidents C 275 User's location C 276 Location of other field units C 277 Unit statuses C 278 Ability to click on a unit or incident in the incident queue or unit C status bar and have it displayed on the map. 279 Ability to center map display on: 280 Current vehicle location (with AVL) C 281 Midpoint between vehicle location and incident location N 282 Dispatch location C 283 Vehicle activating emergency activation key C 284 Specified geographic area (e.g., entering an address via N text entrv) 285 Incident location C 286 Ability to filter display by: 287 Unit type C Page 13 of 24 May 10, 2022 Item #11 Page 589 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 288 Unit status C 289 Incident type C 290 Incident priority C 291 Incident number C 292 Ability to use touch screen for pinch-to-zoom feature. C 293 Ability to automatically zoom to the call location upon dispatch C receipt. Ability to prevent the zoom level from automatically modifying 294 during an active incident (e.g., not automatically zooming out C when new units are added) Ability to access agency-generated files (e.g., apartment complex 295 map, mobile home map, school map, mall map) upon clicking on C Premise hc:izards are accessible via the mobile map. the associated location on the map. : 296 Ability to display historic incidents on the map. C 297 Ability to display full address on a map. C 298 Ability to click on a unit or incident in the incident queue or unit status bar and have it displayed on the map. 299 Ability to display both unit location and incident location on the C map upon dispatch receipt. 300 Ability to auto zoom as unit approaches incident location to C display more detailed map information (e.g., street names). 301 Ability for mapping client to load automatically upon system C boot. 302 Ability to make temporary marks on map (e.g., to note locations N of a perimeter). 303 Ability to share temporary marks on map with field units, including but not limited to: 304 Freestyle lines N 305 Stylus N 306 Pins N 307 Arrows N 308 Agency-defined icons N 309 Routing Page 14 of24 May 10, 2022 Item #11 Page 590 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 310 Ability to automatically provide route from user's current C location (on Mobile using AVL) to dispatched location. 311 Ability to display block numbers. N 312 Ability to provide route from user's current location (on Mobile C using AVL) to user selected point on the mobile map. 313 Ability to provide audible routing information. C 314 Ability to provide text-based routing information. C 315 Ability to toggle on/off audible routing. C 316 Ability to toggle on/off text-based routing. C 317 Ability to support quickest-time routing for all dispatches. C 318 Ability to support shortest route for all dispatches. C 319 Ability to provide estimated travel time. C 320 Ability to highlight on the map the recommended route from C current location to a dispatched incident site. Ability to suggest multiple routes if other routes are within an 321 agency-defined time period (e.g., suggest multiple routes if C within .5 minutes) 322 Ability to recalculate directions to incident/specified location on C the fly. 323 Ability to take into account the following when calculating routing directions: 324 Street speed limits C 325 Closed streets C 326 Dispatch entered obstacles C 327 Mobile user entered obstacles C 328 Distance between vehicle and incident location C 329 Height limitations on overpasses C 330 Current traffic conditions 331 Ability for Mobile user to turn recommended route feature C on/off. 332 Ability to clearly display potential obstacles along route. C Road closures as an example are clearly indicated on the mao. Page 15 of24 May 10, 2022 Item #11 Page 591 of 604DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments Ability to record all routing displays within CAD (e.g., map 333 displays, travel time, travel time estimation, etc.) for analysis to improve routing logarithms. Ability to automatically rotate and zoom map so that unit is 334 automatically displayed moving the same direction. Status Views 336 Ability to view all active calls in a single window. 337 Ability to view all pending calls in a single window. 338 Ability to sort calls from highest priority to lowest priority. 339 Ability to view unit status by: 340 Assigned territory (beat, district, etc.) 341 342 344 345 346 347 348 349 350 351 352 353 354 355 356 357 Individual unit Ability to open any active incident to view dispatch data, units and incident notes. Mobile Dispatch Operations Dispatch Receipt Ability to receive dispatches on the Mobile. Ability for dispatched calls for service to open automatically on mobile computers. Ability to alert mobile users that a new dispatch has arrived: Audible alert Visual alert Ability to acknowledge dispatch without losing current work. Ability to bring dispatch to forefront of the application without losing current work. Ability to receive dispatches on multiple mobile telecommunications devices including, but not limited to: Mobile computers Smart phones iOS Android Tablets N N C C C C C C C C C C C C C C C C C PremierOne offers ARL Playback, and stores the ETA of routes with CAD recommendations. PremierOne does not store travel times. Travel times can calculated using Unit History or ARL Playback and calculating the time between En Route and Arrival Statuses for a specific unit using the PremierOne Re ortin Services. PremierOne Mobile does not support this requirement but could be considered for a future release. Page 16 of 24 May 10, 2022 Item #11 Page 592 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 358 iOS C 359 Android C 360 Windows C 361 Ability for all personnel dispatched to an incident to receive C notification when other personnel are en route. Ability for all personnel dispatched to a call to receive 362 notification of status and location changes of other personnel C dispatched to the call. 363 Ability for Mobile users to add themselves to an incident. C 364 Ability to alert Dispatch when Mobile users add themselves to an C incident. 365 Ability to access and read all call comments associated with a call C regardless of whether assigned to the call. Ability to display the following information in distinct fields or 366 tabs (as opposed to in the call narrative) upon receipt of dispatch: 367 Assisting unit(s) C 368 Comments/narrative (unlimited) C 369 Date and time incident entered C 370 Driver registration information C 371 Dispatch Time C 372 Incident location with cross streets C 373 Incident priority C 374 Incident type C 375 Caution notes/hazard information C 376 Incident talk group N 377 Number of previous calls at a specific location (e.g., Building 10, C Apartment 3) 378 Number of previous calls within a radius of a specific location C (e.g., Buildings 10, 11 and 12). 379 Phone number at incident location (if different) C 380 Pre-plan information C 381 Primary unit assigned C 382 Recommended route C Page 17 of24 May 10, 2022 Item #11 Page 593 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 383 Reporting party information (e.g., name, phone, address) C 384 Suspect information C 385 Premise information C 386 System generated incident number C 387 Weapons involved C 388 Agency-defined N 389 Ability to directly access (e.g., hyperlink, drill down) previous call C information related to the address of the call for service. 390 Incident Updates 391 Ability to display most current incident data at the top of the C screen without requiring the user to scroll. Ability to receive supplemental incident information (e.g., 392 location, suspect, vehicle information) without interrupting or C overlaying current screen. Ability for supplemental information to be visually distinct from 393 information previously received by Mobile user (e.g., separate C font color, highlighted). 394 Ability to transmit status information to the CAD system in real C time. 395 Premise and Hazard Information 396 Ability to alert user of availability of information associated with C a location (gate codes, hazards, premise history, pre-plans, etc.). Ability to indicate type of information that is attached to a call 397 (e.g., gate code, hazard) so that user can decide whether or not C to retrieve the information. 398 Ability for field units to have the option of pulling up or not C pulling up information attached to the call. 399 Ability to drill down in premise history to find links to incidents, C persons, vehicles, etc. 400 Ability to drill down in premise proximity history to find links to C incidents, persons, vehicles, etc. 401 Self-Initiated Calls for Service Page 18 of 24 May 10, 2022 Item #11 Page 594 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 402 Ability to initiate a call for service from the Mobile, including: 403 Call for service C 404 Traffic stop C 405 Subject stop C 406 Non-enforcement activity (e.g. training, field Inspections) C 407 Other agency defined call types. C 408 Ability to initiate a call for service with a function-key. C 409 Ability to auto populate incident location on field initiated calls for service with unit's location, including but not limited to: 410 X/Y coordinates C 411 Cross-streets C 412 Ability to override the auto-populated incident location to a C location other than the unit's location. 413 Ability to geovalidate auto populated location information on ·c field initiated calls for service. 414 Ability for field initiated calls for service to update: 415 Premise history C 416 Unit history C 417 Subject record C 418 Vehicle record C 419 Ability for users to indicate that they are currently out of their C vehicle, but otherwise available for dispatch. 420 Perimeters 421 Ability to receive suggested perimeter positions from dispatch. N 422 Ability for suggested perimeter positions to appear mobile map upon receipt. N 423 Call Disposition 424 Ability to clear calls from the Mobile. C 425 Ability to require a call clearance code in order to clear a call C from the Mobile. 426 Ability to select disposition code from a drop-down list. C Page 19 of 24 May 10, 2022 Item #11 Page 595 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 427 Ability to provide a text field for disposition comments. Ability to limit the potential disposition codes that could be 428 applied to close a call based on call type. Ability for system to reject a disposition if unsuitable for the 429 incident type. Queries 431 General Queries Ability to query the following systems from the mobile 432 computer: 433 CAD 434 RMS 435 CLETS/NCIC 436 DMV 437 Crossroads accident reporting/e-citations 438 LPR 439 Regional Registrants (NetRMS) 440 COPLOGIC DORS Ability to search and query all appropriate databases without 441 impacting performance of mobile dispatch operations. Ability to query and retrieve premise information for an address 442 not associated with a call for service. 443 Ability to initiate queries with a single key stroke. 444 445 Ability to use predefined data entry forms/screens (-masks) to minimize data transmitted during queries. Ability for agency to create standard query screen formats (masks). Ability to scan imitate a query and populate data in a query mask 446 through input from third party devices, including but not limited to: 447 DL Swipe 448 3D barcode scanner C C C C C C C C C C C C C C C C N Motorola Solutions has included an interface to meet this re uirement. Motorola Solutions understands this requirement to be ALPR which we have rovided an interface for. Motorola Solutions has included an interface to meet this re uirement. Motorola Solutions has included an interface to meet this re uirement. Motorola Solutions has included this interface. Page 20 of24 May 10, 2022 Item #11 Page 596 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 449 Ability to provide pre-defined data entry/query forms, including, but not limited to: 450 Accident Investigation C 451 Driver license query C 452 Incident status C 453 Location C 454 License plate query C 455 Logon/logoff C 456 Missing person information C 457 Name query C 458 Premise information query C 459 Previous events C 46.0 Ability to access query forms by: 461 Command line entry C 462 Drop down menus C 463 Configurable buttons on screen C 464 Dedicated function keys C 465 Ability to cache previous queries based on user profile. C 466 Ability to purge historical queries. C 467 Ability to purge historical query results. C 468 Ability to indicate which fields are required for multi-C database query requests. 469 Ability to reformat date from query screens to databases C 1queried to meet the required format for each database. 470 Unit History Queries 471. Ability to query unit history detail by: 472 Date and time range (i.e., start and end dates or times) C 473 Badge Number C 474 Unit ID C 475 First Name C 476 Last Name C 477 Incident Queries 478 Ability to query and retrieve incident records by one or more of the following factors: 479 Any operator ID associated with the incident C Page 21 of 24 May 10, 2022 Item #11 Page 597 of 604DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 480 Any unit ID assigned to the incident C 481 Beat C 482 Caller phone number C 483 Caller name C 484 Call type C 485 Case exists (Y/N) C 486 Case number C 487 Incident comments C 488 Incident narrative C comments search available 489 Involvements N 490 Cross streets C 491 Date and time range (e.g., start and end data and time C parameters) 492 Dispatch operator C 493 Dispatch terminal C 494 Disposition codes C 495 Unit ID "c 496 Personnel ID C 497 Primary unit C 498 Entry operator C 499 Entry terminal C 500 Geographic area (e.g., area, beat) C 501 User defined radius from a location N 502 Incident number C 503 Incident priority C 504 Incident type C 505 License plate C 506 Location or partial location C 507 Name (suspect, reporting party, witness, victim) C 508 Census tract N 509 license Plate Queries 510 Ability to query the license plate against the following databases: 511 RMS C Page 22 of 24 May 10, 2022 Item #11 Page 598 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 512 DMV C 513 CLETS C 514 Ability to conduct multiple license plate searches simultaneously. C 515 Ability to run the registered owner of the vehicle in a license C plate query return. 516 Ability to identify the number of times a license plate has been C queried. 517 Firearms Queries 518 Ability to query firearms against the following databases: 519 RMS C 520 AFIS C 521 Article/Property Queries 522 Ability to query property against the following databases: C 523 CLETS C 524 CAPSS C 525 Vehicle Queries 526 Ability to query vehicles against the following databases: C 527 DMV C 528 svs C 529 NCIC C 530 Person Queries 531 Ability to query people against the following databases: C 532 LEDS C 533 CLETS/NCIC C 534 RMS C 535 Query Returns 536 Ability to save all query returns until user clears data. C 537 Ability to save all stored query returns after logoff (e.g., returns C are still there the next time user logs onto the system). Ability to produce an alert when a query return contains a record 538 marked as potentially hot (e.g., contains agency-defined keywords such as stolen, wanted, missing): Page 23 of 24 May 10, 2022 Item #11 Page 599 of 604DocuSign Envelope ID: EE0000EC-B19O-469F~887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 539 Audible alert C 540 Visual alert C Ability for mobile query returns to appear on dispatcher's screen 541 as well as the mobile computer screen if the return contains an C agency-defined keyword (e.g., stolen, missing, wanted, felony). 542 Ability for user to prevent a mobile query return from appearing C on dispatcher's screen. 543 Ability to attach any database query return to incident records. C Ability to drill down into query returns regarding a potentially 544 hazardous subject, vehicle, and/or location to find the details of C that hazard. 545 Ability to sort query results on any returned field. C 546 Ability to sort query returns by officer name. C Page 24 of 24 May 10, 2022 Item #11 Page 600 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Interface Functional Requirements Item# Interface Functional Requirements Response Code Comments -Vesta/911 Ability to safely and securely provide a one-way interface from Motorola Solutions has provided an integration to meet this 2 C requirement. Additional details can be found in the the Vesta E911 System to the CAD application. SeNices Solution Descriotion. Ability to import E911 data into the CAD system to pre-fill the Motorola Solutions has provided an integration to meet this CAD incident mask. If any data elements cannot be imported requirement. Additional details can be found in the 3 from the E911 system, please indicate those fields in the C SeNices Solution Description. "Comments" field. Ability to parse address information when transferring data from Motorola Solutions has provided an integration to meet this 4 the E911 system to the CAD system so that it transfers into C requirement. Additional details can be found in the appropriate address fields. · SeNices Solution Description. 5 Ability to support the import of E911 data via: Motorola Solutions has provided an integration to meet this 6 Automatic data transfer C requirement. Additional details can be found in the SeNices Solution Descriotion. Motorola Solutions has provided an integration to meet this 7 Manual intervention C requirement. Additional details can be found in the SeNices Solution Descriotion. Ability to geoverify the E911 imported address immediately upon Motorola Solutions has provided an integration to meet this 8 transfer. C requirement. Additional details can be found in the SeNices Solution Descriotion. Ability to determine a physical address from X/Y coordinates Motorola Solutions has provided an integration to meet this 9 C requirement. Additional details can be found in the imported from the E911 phone system. Services Solution Descriotion. Ability to transfer E911 call receipt time to CAD to track E911 Motorola Solutions has provided an integration to meet this 10 C requirement. Additional details can be found in the time stamps. SeNices Solution Descriotion. Motorola Solutions has provided an integration to meet this 11 Ability to plot incoming E911 calls on the CAD application map. requirement. Additional details can be found in the SeNices Solution Descriolion. Motorola Solutions has provided an integration to meet this 12 Ability to import information from text-to-911. C requirement. Additional details can be found in the SeNices Solution Descriotion. Ability to comply and maintain compliance with published NENA Motorola Solutions has provided an integration to meet this 13 C requirement. Additional details can be found in the and APCO NG-911 standards (to include the import of text). Services Solution Description. Motorola Solutions has provided an integration to meet this 14 Ability to support the import of Wireless Phase 1 data. C requirement. Additional details can be found in the Services Solution Descriotion. Page 1 of 4 May 10, 2022 Item #11 Page 601 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 15 16 17 18 20 21 22 23 24 25 26 27 28 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Interface Functional Requirements Ability to safely and securely provide time synchronization across all mission critical public safety systems. Ability to time stamp all transactions. IBM WebSphere MQ Series (CLETS /NCIC Switch) Ability to query NCIC through the County's IBM WebSphere message switch from the CAD and Mobile applications. Ability to conduct NCIC queries from within the CAD and Mobile applications. Ability to run queries automatically upon execution of selected commands (e.g., run plates upon entering a traffic stop). Ability to attach NCIC returns to the CAD incident record. Ability to highlight keywords in NCIC query returns (e.g., wanted person, stolen vehicle). Ability for the agency to define the keywords subject to highlight. Ability to safely and securely provide a one-way push of CAD information into relevant NetRMS mobile report writing fields. Ability to safely and securely provide a one-way push of CAD information into relevant NetRMS records management system fields. City of Carlsbad GIS C C C C C C C C C C PremierOne Cloud CAD provides this internally as part of the Cloud services. PremierOne Cloud CAD provides this internally as part of the Cloud services Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Descri lion. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Descri lion. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Descri lion. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Descri tion. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Descri lion. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Page 2 of 4 May 10, 2022 Item #11 Page 602 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Interface Functional Requirements Item# Interface Functional Requirements Response Code Comments 30 31 32 33 34 Ability to safely and securely provide a two-way interface between CAD and City GIS (ESRI ArcSDE) to enable a query from CAD to the City GIS database for updates, and to accept returns. Ability to safely and securely provide a one-way interface to transfer relevant call for service data from the CAD application to the AXON body-worn camera database at agency-defined intervals External Reporting Systems Ability to safely and securely provide a one-way interface 36 between CAD and external reporting applications (e.g., Crystal, Tableau) for statistical reporting and data analysis. Vigilant Automated License Plate Readers Ability to safely and securely provide a one-way interface from 38 the City's license plate reader system to notify dispatchers of a "hit". 39 Ability for dispatchers to acknowledge "hit" and create a CAD call 40 41 43 Ability to safely and securely provide a one-way query interface from the CAD and Mobile applications to the Crossroads accident reporting and e-citations applications. Coplogic Desk Officer Reporting System (DORS) Ability to safely and securely provide a one-way interface from the Coplogic DORS application to the CAD application to create calls for service for agency-defined reports submitted in the Coplogic application. N C C C C C C A staging file geodatabase (.gdb) is created to consolidate the needed data from one or more sources. PremierOne Data Import Tools are used to map the appropriate layers from the source schema to the staging/production schema. These Motorola provided tools are installed as a Toolbox within ESRl's ArcGIS for Workstation. ArcGIS Models and/or Python scripting is used to simplify the process and Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the System Description. Motorola Solutions has included Analytics Plus to meet this requirement. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Descri lion. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Page 3 of 4 May 10, 2022 Item #11 Page 603 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Interface Functional Requirements Item# Interface Functional Requirements Response Code Comments 44 46 48 49 so 52 Ability to safely and securely provide a query interface from the CAD and Mobile applications to the Coplogic DORS application. Aeility ta safe I•; aRd see1:1rel;· pre'llide a eAe wav iAterfaee freFR 351 te Rotif;· dispatei'lers ef a Aita Rd or tAe re4:1:1rRs 4:e a1:1teFRatieall;· pep1:1iate appropriate fields iA ti'le CAD call fer sef\l·ice sereeA. City of Carlsbad CCTV and Traffic Cameras Ability to safely and securely provide a one-way interface to view the City's CCTV cameras from within the CAD application. Ability to safely and securely provide a query interface to search the LaserFiche EDMS from the CAD and Mobile applications. QueTel Ability to safely and securely provide a query interface to the QueTel evidence management system to perform querles of property, physical evidence and digital evidence from within the CAD and Mobile applications. C A C C Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola SolulioAs !'las pre11ided aA iAlmfaee lo FReet li'lis requiFOFAOAI. l'tddilioAal details eaA Ile fouAd iA ti'le Services SolulioA DeseriplioA. PremierOne CAD can not do this as part of the native application. CommandCentral Aware is able to interface with Video Management Systems (VMS) to provide a one-way interface for CCTV and Traffic Cameras with AP ls availa le from h t vendor. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Page 4 of 4 May 10, 2022 Item #11 Page 604 of 604 DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 SECTION 12 City of Carlsbad, CA February 16, 2022 ADDITIONAL DOCUMENTATION CORRESPONDENCE The City requires that all official correspondence regarding the requested services be made part of the final agreement. MOTOROLA SOLUTIONS RESPONSE Motorola understands and agrees. Exhibit A: Contract Documentation Requirements t.\l Motorola Solutions Additional Documentation Correspondence 131