Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
CM-2026-029 - 1/16/2026
SUPPLEMENTAL AGREEMENT NO. 1 TO "CENTRALSOUARE SOLUTIONS AGREEMENT" CITY OF ROUND ROCK § STATE OF TEXAS § KNOW ALL BY THESE PRESENTS: COUNTY OF TRAVIS § COUNTY OF WILLIAMSON § THIS SUPPLEMENTAL AGREEMENT NO. 1 to "CentralSquare Solutions Agreement" called "Supplemental Agreement No. 1," is made by and between the CITY OF ROUND ROCK, TEXAS, a home-rule municipality, with offices located at 221 East Main Street, Round Rock, Texas 78664-5299 (referred to herein as the "City"), and CENTRALSQUARE TECHNOLOGIES, LLC, whose offices are located at 1000 Business Center Drive, Lake Mary, Florida 32746 (referred to herein as the "CentralSquare"). WHEREAS, the City and CentralSquare previously executed the referenced "CentralSquare Solutions Agreement" for CAD to CAD services for the City; and WHEREAS, the City has determined that CentralSquare is the sole source provider for these services; and WHEREAS, expenditures that are for the procurement of the services that are available from a sole source are exempt from competitive requirements pursuant to Section 252,022 of the Texas Local Government Code; and WHEREAS, the City desires to add additional services to the CentralSquare Solutions Agreement, specifically, as set forth in the Statement of Work in Exhibit "A," to this Supplemental Agreement No. I, said Exhibit "A," shall be incorporated herein by reference for all purposes; and d WHEREAS, the parties desire to add additional fees to the Master Services Agreement for the additional Statement of Work as set forth in Exhibit"A"and herein; and NOW THEREFORE, in consideration of the mutual promises and obligations in the CentralSquare Solutions Agreement and this Supplemental Agreement No. 1, the City and CentralSquare agree that said CentralSquare Solutions Agreement is amended and supplemented as follows: I. The Solution(s) and Services Fee Schedule set forth in Exhibit 1 of the CentralSquare Solutions Agreement, shall be amended to include the additional fee of$15,990.00 as set forth in 4897-3071-01441ss2 C� —102-co - 02q the attached Exhibit A, incorporated herein by reference for all purposes, for a new not-to- exceed total of$113,850.00. II. The Statement of Work set forth in Exhibit 5 of the CentralSquare Solutions Agreement, shall be amended to include the additional Statement of Work for the addition of on-premises solution as set forth in the attached Exhibit A, incorporated herein by reference for all purposes. III. This Supplemental Agreement No. l shall amend the original CentralSquare Solutions Agreement only as set forth herein with no other changes in terms or conditions of the original Agreement. [Signatures on the following page.] IN WITNESS WHEREOF, the City and CentralSquare have executed this Supplemental Agreement No. 1 to be effective as of the last date of due execution by both parties. CITY OF ROUND ROCK,TEXAS CENTRAL SQUARE TECHNOLOGIES, LLC By: By: PrintedW' Ttff S I Printed Name: RonAAnderson Title: i _ Title: ChiefR,"nueOfficer Date Sign ,II Date Signed: oi1o9nozs ATTEST: By: Ann -'rankiin, City Clerk FOR CITY, APPROVED AS TO FORM: Stephanie L. Sandre,City Attorney Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit „A" Quote prepared on: 25 C CENTRALSOUARE® Oe prepay d by: Quote prepared by: Crystal Roth Change Order crystal roth@centralsquare.com Quote#:Q-239508 Quote prepared for: Primary Quoted Solution: CAD to CAD Megan Tschoerner Quote expires on:April 21,2026 Round Rock Police Department Change Order in reference to:Q-175135 2801 North Mays Street Round Rock,Texas 78665 (737)587-0334 Thank you for your interest in CentralSquare.CentralSquare provides software that powers over 8,000 communities. More about our products can be found at www centra sguare.com WHAT SERVICES ARE INCLUDED? DESCRIPTION TOTAL 1 Public Safety Consulting Services-Fixed Fee 7,80000 2. Public Safety Project Management Services-Fixed Fee 3,510-00 3 Public Safety Technical Services-Fixed Fee 4,680.00 Services Total 15 990 00 USD QUOTE SUMMARY Services Subtotal 15,990.00 USD Quote Subtotal 15,990.00 USD Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Quote prepared on: C CENTRALSOUARE® Oe prepay 2025 Quote prepared by: Crystal Roth Change Order crystal roth@centralsquare.com Quote Total 15,990.00 USD WHAT ARE THE RECURRING FEES? TYPE AMOUNT FIRST YEAR MAINTENANCE TOTAL 0.00 FIRST YEAR SUBSCRIPTION TOTAL 0.00 FIRST YEAR RECURRING SERVICES TOTAL 0.00 The amount totals for Maintenance and/or Subscriptions on this quote include only the first year of software use and maintenance Annual Maintenance and Subscriptions renewals shall be due annually on the anniversary date of the Delivery Date',Annual Maintenance and Subscripton Fees are subject to increase as outlined in the Master Agreement. "Delivery: For on-premise software, Delivery shall be when CentralSquare delivers to Customer the initial copies of the software outlined above by wh'chever the fo=dowing applies and occurs first(a)electronic delivery, by posting it on CentralSquare's network for downloading, or similar suitable electronic file transfer method.or(b)physical shipment,such as on a disc or other suitable media transfer method,or(c)installation or(d)delivery of managed services server. Phys.cal shipment is on FOB -CentralSquare's shipping point, and electronic delivery is at the time CentralSquare provides Customer with access to download the software. For cloud-based software Delivery shall be whichever the fo'Jowing applies and occurs first when Authorized Users have(a)received log-in access to the software or any module of the software or(b)received access to the software via a URL. Subscription Access.If Customer is purchasing subscription software under this Quote,so long as Customer has paid the annual subscription fees and is current at all times with the subscription fees as stated herein,CentralSquare grants to Client a I mited non-exclusive, non-transferable access to use the subscription software granted in this Quote, Customer understands and acknowledges no ownership or any form of intellectual property rights transfer under the terms of this Quote. Upon termination of this Quote or any subscriptions, (i)all rights granted herein shall terminate immediately and automatically upon the effective date of such termination; (ii) Customer's right to the accessed software granted herein shall terminate, and (iii)Customer will cease using such software and at CentralSquare's direction return or destroy the software and any supplemental confidential information or documentation. Customer shall maintain for a reasonable period, but in no event less than three(3)years after expiration or termination of this Quote,the systems,books and records necessary to accurately reflect compliance with software access and the use thereof. Upon request and no more than once per year, Customer shall permit CentralSquare to audit Customer's use of the software to monitor compliance. If an audit reveals that Customer has exceeded the restrictions on use or non-compliance with this Quote,Customer shall be responsible for the prompt payment by Customer to CentralSquare of any underpayment. Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Quote prepared on: C ® October 2025 - CENTRALSOUAREQuote prepared by: Crystal Roth Change Order crystal.roth@centralsquare.com BILLING INFORMATION Fees will be payable within 30 days of invoicing. Please note that the Unit Price shown above has been rounded to the nearest two decimal places for display purposes only. The actual price may include as many as five decimal places. For example, an actual price of$21.37656 will be shown as a Unit Price of$21.38. The Total for this quote has been calculated using the actual prices for the product and/or service,rather than the Unit Price displayed above. Prices shown do not include any taxes that may apply.Any such taxes are the responsibility of Customer.This is not an invoice. For customers based in the United States or Canada,any applicable taxes will be determined based on the laws and regulations of the taxing authority(ies)governing the"Ship To"location provided by Customer on the Quote Form. PAYMENT TERMS License Fees&Annual Subscriptions - 100% Due Upon Execution Contract Startup - 100%Due Upon Execution Hardware&Third-Party Software - 100%Due Upon Execution Services - Fixed Fee: 100%Due Upon Completion of Services - Time& Material: Due as Incurred Third-Party Services Fixed Fee: 50%Due Upon Execution;50%Due Upon Completion Time& Material: Due As Incurred Travel&Living Expenses - Due as Incurred Docuslgn Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" -. ® Quote prepared on: C CENTRALSOUARE QuOotee pbere arpar 20 ed b y: Crystal Roth Change Order crystal.roth@centralsquare.com PURCHASE ORDER INFORMATION Is a Purchase Order(PO)required for the purchase or payment of the products on this Quote Form?(Customer to complete) Yes[ ] No[ ] Customer's purchase order terms will be governed by the parties existing mutually executed agreement,or in the absence of such are void and will have no legal effect. PO Number: Initials: Round Rock Police Department Signature: Name: Megan Tschoerner Title Assistant Director, IT Date, Applicable Additional terms will be added to the next page. Docusign Envelope ID FCF141D5-8698.4559-A4DA-6F0572D29279 Exhibit "A" Docusign Envelope ID FCF141D5-B698-4559-A4DA-6F6572D29279 Exhibit „A" CENTRALSQUAREO STATEMENT OF WORK UNIFY (On-Premise) Round Rock Police, TX Version 1.0 1000 Business Center Drive, Lake Mary, FL 32746 407.304.3235 1 Fax:407.304.3301 1 www.central,,guare.com Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" © 2025 CentralSquare Technologies, LLC Unpublished: Rights reserved under the copyright laws of the United States. All information in this document is proprietary and confidential and owned by CentralSquare Technologies, LLC`"'. No part of this document may be reproduced or transmitted in any form or by any means,electronic or mechanical,for any purpose,without the express written permission of CentralSquare Technologies, LLC, Trademarks Microsoft, Windows, Microsoft Access, Microsoft Excel, Microsoft Exchange,and Microsoft Word are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. CentralSquare Public Safety Suite—Enterprise,CentralSquare CAD Enterprise,CentralSquare Mobile Enterprise, CentralSquare Records Enterprise,CentralSquare Jail Enterprise, CentralSquare False Alarm Management,and CentralSquare Public Safety Analytics Enterprise are trademarks of CentralSquare Technologies, LLC. ArcGIS,ArcMap and ArcCatalog are registered trademarks of Environmental Systems Research Institute (Esri) in the United States and other countries. Document Control Date Version Details/Changes Author 11/4/2025 1.0 Jnitial draft C Grant The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced,published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page it Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX RAFA CAD-2-CAD Unify A Table of Contents Document Control..............................................................................................................................ii 1. CENTRALSQUARE UNIFY......................................................................................,......................1 1.1. Stateownt of Work....................____...........................____.........,....,......................1 1.1. Project Implementation Definitions,,..,.,..,.....................................................................1 1,2, Project Exclusions...........................................................................................................4 2. PROJECT DELIVERABLES..............................................................................................,................5 2.1. Overview of Project Deliverables...................................................................................5 2.2. Standard CerltraISquareDel iverables......................................................,..........,...........5 2.3. Contracted M odif[cations to Standard Centra lSquare Products............... ........ ..........6 2.4. CentraIsquare UnlfyOverview ... . . .. ............. . ..._.. . . . .6 2.5. Solution .....................,.,_.._......,..,,,,.................................,.7 2.6, Deliverable System Connections on CentraliSquare Unify Hub,_.—.......-............ .......7 2.3. Modifications.,__...—------___---____..........__....... ...... .....................................a 2,8. CentraNuare Unify Customr Deliverables................... .W.,.,,..,..,..,.,,....... 3. STANDARD FUNCTIONALITY CENTRALSQUARE UNIFY................................................................1.'2 3.1. Overview............____....... . ...., ,,.,,.,..,.,...,......,,................,..............,.,.........,..12 3-2 Cent ra"uare Unify External System Dependencies...................................................23 4.. PROJECT CONTROLLING PROCESS...............................................................................................25 4.1.. Over+,pieW.,,.,,....1-1..........., ......... . ........ . .......—...........,.,.....,..,..,,.....,.... . ................,25 4.2. Change Management Process......................................................................................27 4.3, Project Reporting......................................................................... ...............................28 4.4, Document Review......................... .................... ......... ..................... ........., .........29 4.5. Third-PartyManagement.............................__. ..................... .........___.............30 5. PROJECT INITIATION AND PLANNING......................... ........,.....................................................32 5.1. Overview.......................................................................................................................32 52 Project Kickoff............................... ................................ ......... ...,...,.. ...,..,.. ........,33 6. PROJECT EXECUTION............................. ...........------... .......... ........ .......... ........... ............ ....35 6.1. Overview.................................................................................................................,......35 6.1. System Installation .......................................................................................................35 7. CENiTRAiLSQUAREUNIFY TESTING..............................................................................................40 The contents of this material are con6dentia6 and proprietary to CentraNuare Technologies,ILC and may not be reproduced,published,or disclosed to otriers without the prior written consent of C,entralSquare Technologies,LLC_ 02025 CentraNuare Technologies,LLC Page 10 Docusign Envelope ID:FCF141D5-13698-4559-A41DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify Odwril 7.1. Isolated CAD Adapter Testing.......................................................................................40 7.2. Provider End-to-End Testing.........................................................................................40 7.3. Functional Acceptance Testing(Customer End-to-End Testing)..................................41 S. CENTRALSQUARE UNIFY TRAINING...........................................................................................43 8.1. Training.........................................................................................................................43 9. CONDUCT CENTRALSQUARE UNIFY PRE-GO-LIVE TASKS.............................................................44 9.1. Pre-Go-Live...................................................................................................................44 10. CONDUCT CENTRALSQUARE UNIFY GO-LIVE..............................................................................46 10.1. Go-Live..........................................................................................................................46 11. PROJECTCLOSURE....................................................................................................................47 11.1. Project Closure..............................................................................................................47 12. Appendix A—Contracted Modifications to Standard CentralSquare Products.............................48 13. Appendix E—Subcontractor Statement of Work........................................................................49 14. Appendix J—CentralSquare Connectivity to Enterprise On-Premise Systems Policy....................50 15. Appendix Y—Workshop Summary............................................................................................51 The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced,published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page iv Docusign Envelope ID;FCF141D5-8698-4559-A4DA-6FO572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAO Unify 01 1. CENTRALSQUARE UNIFY 1.1. Statement of Work This Statement of Work(SOW)defines the services and deliverables that CentralSquare will be providing in accordance with the terms and conditions of the Agreement(the "Agreement") between CentralSquare Technologies, LLC(CentralSquare)and the Round Rock Police,TX ("Customer"). This project description includes the services and deliverables specified by the Agreement, including if applicable,CentralSquare and services,Subcontractor activities,third-party products,and services for the implementation of the System specified in the Agreement (collectively the "Project"). Where dependencies exist between Customer and other participating agency members of the CentralSquare Unify implementation,Customer will facilitate involvement of its members to achieve the deliverables of this SOW. Statement(s)of Work for applicable CentralSquare Subcontractor(s) are presented in Appendix E—Subcontractor Statement(s)of Work. The framework of Deliverables documented by this SOW for this Project is further defined through additional documents such as: Operational Scenario Documents (OSD)and the CAD-to- CAD Hub Administrator's Guide. The number and type of software licenses, products,or services provided by CentralSquare or its Subcontractors are specifically listed in the Agreement and any reference within this document as well as Subcontractors'SOWs (if applicable)do not imply or convey a software, license,or services that are not explicitly listed in the Agreement. 1.1. Project Implementation Definitions Unless otherwise defined herein, capitalized terms within this document have the meanings described in the Definitions section of the Agreement and where applicable Software Support Agreement. The following terms are used in this document.Since these terms may be used differently in other settings,these definitions are provided for clarity. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 1 Docusign Envelope ID: FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX NWA CAD-2-CAD Unify �` a) API is an acronym for Application Programing Interface.An API is a connection between computers or between computer programs. It is a type of software interface, offering a service to other pieces of software.A document or standard that describes how to build or use such a connection or interface is called an API specification.A computer system that meets this standard is said to implement or expose an API.The term API may refer either to the specification or to the implementation. b) Agency means any public safety organization responsible for services within Customer's physical boundaries. c) Agency Administrator is utilized in the CAD-to-CAD requirements to mean the administrator for a particular agency which has assigned rights to the CAD-to-CAD administrative access. d) CAD Provider means the 3`d party CAD Vendor that will be developing the adapter to connect their CAD to the hub. e) CAD-to-CAD or CAD2CAD is a term used for CAD integrations to another CAD. f) CentralSquare Unify Hub is CentralSquare's solution which can be referred to as"the Hub". g) CAD-to-CAD Portal is an application that connects to the CentralSquare Unify Hub via a thick client.The CentralSquare Unify Portal provides but is not limited to, a view of real-time CAD events for all connected CAD systems,access to administer the configuration of the CentralSquare Unify Hub (based on user roles),and access to detailed diagnostics for troubleshooting.The CentralSquare Unify Portal also has a GIS map feature that provides a visual reference for location of events and vehicles. h) Change Management Process is a series of actions or steps taken in order to achieve individual,team,or organizational change. i) CAS Security Policy means the Federal Bureau of Investigations Criminal Justice Information System Security Policy. The essential premise of the UIS Security Policy is to provide appropriate controls to protect the full lifecycle of criminal justice information(CJI),whether at rest or in transit. The CAS Security Policy provides guidance for the creation,viewing, modification,transmission,dissemination,storage, and destruction of CJI. j) Change Order will be the vehicle for communicating and approving a change in project scope. k) Codefiles are the component fields within each product that define the data to be contained within each table. 1) Connector also referred to as CAD Adapter is an interface to be installed at an Agency that connects the Agency's CAD to the CentralSquare Unify Hub. m) COTS means"Commercial Off the Shelf'software packages provided by CentralSquare. n) Functional Acceptance Test(FAT) is a test of specific functionality of the CentralSquare Unify solution. o) Go-Live means the event that occurs when Customer first uses the CentralSquare Unify The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written coesent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 2 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "An Round Rock Police,TX CAD-2-CAD Unify 3 solution for Live Operations in a non-test environment. p) GIS is an acronym for Geographic Information System,which is a system for storing and manipulating geographical information on a computer. q) Installation Service Request(ISR)documents servers requirements for the implementation and the servers' hardware/virtual specifications. r) Modification means changes or additions to Software from the standard version thereof prepared hereunder. The Modifications, if applicable,are described in SOW,Appendix A— Contracted Modifications to Standard CentralSquare Products. The CentralSquare Software is not custom software,and as such,at CentralSquare's discretion Modifications or enhancements to the standard version will be made available in a subsequent version release available to all CentralSquare Customer's;or as applicable, made available as a separate module or function,separately licensed and priced. s) The Operational Scenario Document(OSD) provides an operational description of an interface,capability, or feature within the applicable CentralSquare solution. t) Project collectively includes the services and deliverables specified by the Agreement, including if applicable,CentralSquare services,Subcontractor activities,third-party products, and services for the implementation of the System and Subsystems specified in the Agreement. u) Project Management Plan means collectively the Communications Management Plan; Risk Management Plan;and Change Management Plan that provide the criteria for managing those tasks within the Project. v) Project Schedule means the schedule providing dates and timeframes for completion of tasks and Deliverables during the course of this Project.The Project Schedule is subject to change at the mutual agreement of CentralSquare and Customer as further described in this SOW. w) SDK is the Software Development Kit that is provided to 3`d party CAD Vendors to develop the middleware (or adapter)that connects their CAD to the hub. x) SME is an acronym for subject matter expert,an individual with a deep understanding of a particular topic. y) Solution is the total complement of Licensed Software,Services,customizations,all other items,tangible and intangible,designed to operate as an integrated group to provide the functionality outlined in the Scope of Services. z) System means the CentralSquare Unify, Notify,or Aware solutions. aa) System Planning Guide provides system administrators and system planners a single requirements reference. bb)Task Completion Reports(TCR) is a formal document presented to the Customer that acknowledges completion of a major task or event. cc) Third-Party Software or Systems are software and systems that are proprietary to a Third- The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 3 Docusign Envelope ID-FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify Party, not CentralSquare,which maybe used for the purposes of providing services or deliverables. dd) Work Hours: a. Business hours are defined as Monday—Friday,8:00am-5:00pm local time. 1.2. Project Exclusions CentralSquare provides software applications that it develops.These applications are sold as is and are considered to be"Commercial Off the Shelf"(COTS)software packages.The functionality of these products will be based on CentralSquare's current design and functionality of these COTS products, unless otherwise indicated in the Agreement. a) Work,software,services, hardware, Systems, product/software modifications, or any other deliverables not explicitly stated in the Agreement will not be included in the Project. b) Any modification to CentralSquare standard products or customizations to such products that are not explicitly stated in the Agreement are excluded from the scope of this Project. c) Changes in scope will only be executed through a mutually agreed upon Change Management Process,as described in the Project Management Plan. d) CentralSquare is not responsible for the deficiencies in Customer's internal or contracted network to support the CentralSquare Unify system. e) CentralSquare is not responsible for the deficiencies in Customer's network. f) CentralSquare is not responsible for the removal of the old (legacy)equipment, hardware, furniture, consoles, cabling,as part of the Project implementation unless specifically stated in the Agreement and this SOW. g) This project does not include creation or modification of GIS data by CentralSquare staff. h) CentralSquare is not responsible for coordination, management,or covering the cost of any software,work,customization,coding or testing that is required to be performed by any third-party vendors, unless the work is defined under a Sub-Agreement with CentralSquare within the scope of this Agreement. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 4 Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "An Round Rock Police,TX CAD-2-CAD Unify 2. PROJECT DELIVERABLES 2.1. Overview of Project Deliverables This project will provide a combination of software and services that comprise the overall System for use by Customer's Public Safety Organization(s).The Agreement specifies the user and software licenses included in this Project by the quantity and environment in which licensed. Project Management services per the Agreement and in accordance with the approved plan outlined in SOW,Section 6- Project Execution,and corresponding schedule for project. All installation and configuration activities,as well as upgrades for this project will be performed remotely. Implementation of different components of the System is performed in a series of interrelated processes. Some processes can be performed concurrently while others are sequential in nature. CentralSquare has implemented process gates to ensure completion of tasks in the optimal order before a subsequent activity begins. The only reference for the number and type of software licenses is the Agreement.Any reference within this document to services associated with a specific software product does not imply or convey a software license for products that are not listed in the Agreement. All project services will be performed during normal business hours,defined as Monday— Friday, 8:00am -5:00pm local time. If Customer desires to perform the services outside of these hours, additional fees will apply. 2.2. Standard CentralSquare Deliverables The functionality provided by Standard CentralSquare Products is defined by CentralSquare Standard documentation such as:Operational Scenario Documents(OSD) and the CAD to CAD Hub Administrator's Guide. These documents are standard, published CentralSquare documents,and are not specific to the Customer. Standard CentralSquare Software to be delivered through this Project is identified as software licenses in the Agreement.The functionality provided by specified Standard CentralSquare Software is defined by CentralSquare OSDs or other documents. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page Docusign Envelope V:FCF14tD5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify ' 2.3. Contracted Modifications to Standard CentralSquare Products Any Modifications to Standard CentralSquare Products that are to be delivered through this Project are listed in the Agreement.The functional scope of any Modification procured through the Agreement will be summarized in this Statement of Work and defined by an OSD for all items listed under Appendix A Contracted Modifications to Standard CentralSquare Products.Any and all modifications or enhancements that are not explicitly listed in the Agreement are not within the scope of this Project. Any Modification to the functionality of Standard CentralSquare products or interfaces, outside the scope of the Agreement,within the System, shall follow the Change Management Process as described in SOW,Section 4.2 Change Management Process. Any post-approval changes to the requirements documented in the System OSDs or other documents are subject to formal Change Order. Note: All enhancements and modifications to any of CentralSquare's Standard products will only be released with a major version of the applicable system based upon the relevance and dependency to these products. Note: Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software while a service pack or patch is a piece of software designed to fix problems with or update a computer program or its supporting data.This includes fixing security vulnerabilities and other bugs. 2.4. CentralSquare Unify Overview The CentralSquare Unify Hub(or simply the"Hub") provides intelligent options for sharing data between disparate CAD systems including call and unit information. Use of the Hub as a CAD- to-CAD solution reduces the use of phone calls and radio traffic while reducing response times and increasing information accuracy.The following documentation provides scope, processes, and deliverables necessary to implement a successful Unify system. The CentralSquare Unify package provides the deepest system integration by interfacing bi- directionally to and from the connecting system. This allows users to send and receive incident and unit data to and from the Hub using their existing CAD. The Unify product package also The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 6 Docusign Envelope ID:FCF141D5-6698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MOM CAD-2-CAD Unify " provides user access to the Hub Portal Incident Viewer and Hub Notifications typically associated with the Aware and Notify product packages. The customization efforts involved when integrating the Adapters and interfaces with the CentralSquare Unify Hub include several risks,the outcome of which are not completely certain until implementation and testing is complete. Based upon the differences of each CAD system, an agency may use different methods of sharing incidents and exchanging information through their connection to the Hub.Thus, actual functionality can vary widely by agency,even for those using the same make of CAD system.Accordingly,each agency is treated as a separate integration with inherent risks associated with configuration efforts.CentralSquare will work with the Customer to identify,track and mitigate risks associated with this project. 2.5. Solution Overview Customer will be connected to an existing CentralSquare Hub using the method noted below. • Unify: Bi-directional solution, enables sharing of incidents, unit updates,and unit locations. • Portal Access only(for situational awareness and is included with Unify). A table outlining each participating agency that is included in this contract will be noted in SOW, Section 2.6-Deliverable System Connections on CentralSquare Unify Hub. CentralSquare will work with the Customer to develop a mutually agreed upon schedule for the deployment and Go-Live of the CentralSquare Unify solution at the Customer's site. An interim solution is available for the participating agencies that are waiting for the development of the CAD Adapter connection. Portal access is included to view real-time CAD events as well as resource sharing requests.Agencies would also be able to receive and respond to requests in the Portal. 2.6. Deliverable System Connections on CentralSquare Unify Hub CentralSquare will provide the Customer with the following system connections as indicated in the below table. Adapter Status Definitions: • Development needed by CAD provider:The CAD Vendor does not have an Adapter available and development work is required.The CAD Vendor must also complete the certification process with CentralSquare before the Adapter is available for deployment. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. ©2025 CentralSquare Technologies,LLC Page 7 Docusign Envelope ID-FCF141D5-B696.4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 3 • Functional testing in process with CAD provider:CentralSquare is working with the CAD Vendor to test the Adapter and upon completion of successful testing, the Adapter will be available for deployment. • Adapter Available for deployment:The development work by the CAD Vendor and the functional testing process with CentralSquare have been completed.The Adapter is available for deployment. Product# Agency Connecting System Connection Adapter (Vendor/Description) 1 Round Rock Tyler Technologies Bi-directional Unify Available for Police,TX deployment 2.6.1. Specific Requirements for InteropAPl Certain CAD vendors have developed and deployed Hub interfaces for CAD-2-CAD via the InteropAPl standard. The CAD applications will be required to have an agency provided server, on premises. Vendors that are required to have this additional server are: • Motorola Flex • Motorola Premier One • Southern Software • Oracle • Mark43 • CentralSquare Professional Minimum specifications are: • CPU—2 Core Minimum,4 Core Recommended • RAM 8 Gigabytes • 80 Gigabytes of Free Disk Space 2.7. Modifications No CentralSquare modifications are included outside of standard functionality described within this SOW, unless noted in Appendix A--Contracted Modifications to Standard CentralSquare Products. The contents of this material are confdential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of Centra"Square Technologies,LLC, 02025 CentralSquare Technologies,LLC Page 8 Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "An Round Rock Police,TX CAD-2-CAD Unify 0,6` 2.8. CentralSquare Unify Customer Deliverables In order to expedite the project implementation timeline and maximize the benefit of the product,the Customer agrees to the following: 2.8.1. External System Adapters The Customer and participating agencies are expected to contract directly with their CAD system provider for all licensing, professional services and ongoing maintenance related to the respective Adapter to their CAD system.The licensing and implementation costs of this Adapter are not included in the associated Agreement and are to be borne separately by the Customer and participating agencies. It is the responsibility of the Customer and participating agencies to finalize all contract arrangements with the external system providers before CentralSquare begins work on the associated Agreement. 2.8.2. Regional Governance The Customer will designate an administrative sponsor(and/or agency representatives)to address policy decisions with partners related to this project as well as to support ongoing sustainability of the delivered system. Governance representatives from each agency form the region's governance body.This governance body must be identified early in the project in order to mitigate the risk of project delays due to policy decisions that may need to be addressed. 2.8.3. Testing Coordination It is difficult to predict the time needed to accomplish sufficient testing because of a number of unknown factors (for example: readiness of technology partners,well defined Customer goals,consistent participation of testers).Since the Customer has a uniquely positioned relationship with all participating technology providers, it is the Customer Project Manager's responsibility to coordinate all testing sessions for this project. CentralSquare will provide guidance and direction for the needed testing sessions during the appropriate stages of the project. 2.8.4. Subject Matter Experts (SME) The Customer will ensure that personnel are assigned to serve as the Subject Matter Experts(SME)that will provide input and feedback throughout this project. Ideally,this will be a CAD Administrator and one or more Dispatchers with a detailed understanding of the daily operations of the dispatch center. Members of this group should remain The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technn[ogies,LLC ©2025 CentralSquare Technologies,LLC Page Docusign Envelope ID:FCF141D5-13698-4559-A4DA-6F0572D29279 Exhibit „A" Round Rock Police,TX CAD-2-CAD Unify consistent throughout the project.The SMEs will be required to attend scheduled meetings and work sessions with CentralSquare and the Project Manager. Responsibilities include but are not limited to: a) Documenting common incident-sharing scenarios and business processes. b) Providing lists of units,codes, and descriptions. c) Mapping units and codes to the common code set in the CAD-to-CAD Hub. d) Assistance in the development of the collaborative documentation. e) Assistance during testing and troubleshooting. 2.8.5. Network Connections The Customer and participating agencies are responsible for establishing a secure connection between the CAD-to-CAD Hub and the connected CAD systems including: a) Establishing a high speed network connection. b) Establishing network security. c) Configuring firewalls and ports. d) The Customer and participating agencies will identify and provide a CAD Administrator that can login to test CAD systems and work jointly with CentralSquare and the Provider on any project related network connection items. 2.8.6. Memorandum of Understanding The Customer is responsible for obtaining any agreements necessary for the sharing of CAD data from,and with, all participating CAD systems as required by each agency's policy. 2.8.7. Agency Specific Training No specific training for the Hub is included in this Statement of Work. All training related directly to dispatch operations will be conducted by the Customer. 2.8.8. Test Environment The Customer is responsible for providing a Test CAD environment including the installation of CAD interface and API that adequately mirrors the agency's Production CAD environment,with associated test data that is capable of interfacing with CAD-to-CAD Hub,The Test environment will connect to the same server cluster as the Production environment. a) Failure to provide a complete Test environment, as described herein, will introduce overhead,will require additional testing and implementation effort outside the scope of this SOW, and will be priced accordingly and managed through the Change Order process. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 10 Docusign Envelope ID: FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "An Round Rock Police,TX MWA CAD-2-CAD Unify 0- 2.8.9. Remotely Accessible Test CAD Console The Customer will need to identify and provide a CAD Administrator that can login to a test CAD console,which can be used for testing with the Hub for each CAD system.The CAD Administrator will be accessible to CentralSquare personnel during normal business hours and must have login credentials that can add and modify incidents in order to conduct End-to-End Testing.The test CAD console should be configured to match the Production system. a) The test CAD console allows CentralSquare personnel to rapidly implement and test functionality as needed while limiting the involvement of agency personnel until acceptance testing. Lack of a remotely accessible test CAD console will require a dedicated Customer tester to be available on short notice to conduct testing session. Failure to meet this requirement will result in additional incurred costs to be billed at the hourly rate stated in the associated Agreement. 2.8.10. Timelines and Shared Responsibilities The CAD-to-CAD Hub Unify project schedule distributes responsibilities between multiple parties. Following the plan will deliver a highly functional solution.The agreed upon fees in the associated Pricing Schedule is dependent upon close and timely coordination and cooperation of all parties, Delays in the Customer and/or third parties assigned duties not only impact this Project but other CentralSquare projects also. Delays caused by the Customer and/or third parties not fulfilling their responsibilities in a timely manner are extremely disruptive.A delay in a milestone may cause a delay in starting or completing subsequent tasks; in effect creating a risk to the overall Project. Milestone delays on the part of either party will trigger an overall review of the Project activities so that risks can be assessed and properly managed.In the event that either party becomes aware of a delay, notification shall be provided to the other party as soon as reasonably possible. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 11 Docusign Envelope ID:FCF141D5-6698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 01 3. STANDARD FUNCTIONALITY CENTRALSQUARE UNIFY 3.1. Overview The Customer is licensed to use the CAD-to-CAD Unify functionality as described in this section.The features listed below are available components within CAD-to-CAD Hub's core functionality. Each feature requires effort to train personnel,discover needs, configure,test and deploy the system. This SOW which govern the supported features, the number of configurations allowed,and the maximum effort that will be expended by CentralSquare personnel to implement these features. Not all capabilities described herein will be deployed with every Unify Hub integration project. Features and components not listed below are not included in the project.Additional customizations must be expressly detailed in the SOW, Appendix A—Contracted Modifications to Standard CentralSquare Products. Software releases are available every quarter and CentralSquare Product Support will notify the Customer of the release schedule and will work with the Customer to establish a mutually agreed upon CAD-to-CAD upgrade schedule. Features and functionality within software releases are included as part of the Subscription. 3.1.1. Business Rules, Filters, and Data Translations Business Rules to Exchange Cali and Unit Information:The CAD-to-CAD Hub may be configured to share information automatically using business rules based on pre-defined criteria determined by the Customer. Each business rule identifies call or unit criteria which will act as a trigger to a subsequent information sharing action. Business rules are configurable without the need for customized coding or scripting. a) The following are supported criteria for triggering a business rule: i. Call or unit meets the criteria of a defined Filter in the Hub Portal. ii. Call or unit stops meeting the criteria of a defined Filter in the Hub Portal. iii. Comment added to a call containing pre-configured text string or keyword. iv. External resource is requested.The call information will be shared with the CAD system that owns the requested physical resource. v. Resource request is granted,denied,or cancelled. vi. Error{network or notification error} is received from an interface. vii. Unit is assigned or unassigned from a call. viii. Call or unit field updated. ix. Non-incident CAD message is received. The contents of this material are confidential and proprietary to Central quare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentraNuare Technologies,tLC. ©2025 CentralSquare Technologies,LLC Page 12 Docusign Envelope ID:FCF14105-6698-4559-A4DA-6Fo572D29279 Exhibit "A„ Round Rock Police,TX MWA CAD-2-CAD Unify 004 Note:There is no messaging between systems outside of adding comments or share calls. Examples of non-incident CAD messages that can trigger business rules are:AVL, unit status,or geographic update. b) The following are actions that may be taken by a business rule: i. Share a call ii. Request a Resource iii. Grant/Deny/Cancel a resource request iv. Grant/Deny a resource request based on availability v. Send an email or SMS alert to a user or user group vi. Create an on-screen toast notification c) The following are some sample scenarios that can be implemented using a business rule: i. Dispatcher initiated comment of"##WV"triggers a call share with another agency that is connected to the hub ii. Call share triggers a comment to be added to the shared call containing the originating dispatch center and call number iii. Resource request triggers an on-screen toast notification for a user group at the dispatch center owning the requested resource iv. Network error when attempting a call share generates a toast notification at the corresponding dispatch center d) Business rules require effort to define needs,configure,test,and refine. Even simple business rules may have unintended interactions with the connecting system or policies of the dispatch center. Testing is required to refine rules as necessary. The time associated will increase with the complexity of the business rule. Refer to the below table which identifies the number of business rules and the maximum effort to be expended by CentralSquare personnel to implement those rules. Configuration Allowance:CentralSquare will assist the Customer in developing five (5) business rules and User Groups,with associated filters.The Customer is responsible for creating the remainder of the items that are needed for the configuration.There is no limit on the number of business rules or User Groups that can be created by the agency. Business rules with associated filters 5 User groups with associated filters 5 The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 13 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A„ Round Rock Police,TX OWA CAD-2-CAD Unify 0- Filters:Filters are used to define criteria to be met for information sharing including business rules, restrict viewing for user groups,and other built-in configurations. Determining and configuring filter criteria is the responsibility of the Customer with assistance from CentralSquare. a) Filters may be created based on: i. Incoming Common Data Mappings for Supported CAD Incident Fields as defined in this document ii. Incoming Common Data Mappings for Supported Unit Update Fields as defined in this document iii. Time and Date parameters b) The following are sample use cases for which filters maybe used to restrict viewing or trigger business rules: i. Calls originating from a particular dispatch center ii. Calls mapped to a single or multiple common nature code(s) iii. Calls of a particular discipline such as Law, Fire,or EMS iv. Calls shared with other dispatch centers v. Calls located in a particular geographic area (geofence) vi. Units dispatched to shared calls c) Filters are created through the standard menu-driven functionality of the Hub Portal. Complex filtering scenarios may require additional effort involving defining needs, configuring the filter,test,and refinement. Code Mappings/Translations:The CAD-to-CAD Hub includes the ability to translate incident and unit field values such as Call Nature between sharing CAD systems by mapping codes through a common code set. The Customer and participating agencies are responsible for defining the common code set, inputting local codes and mapping them to the common codes, and maintaining the entire set of codes using the Hub Portal. Code mapping is supported for the following codes: a) Agency Name b) City c) Discipline(i.e., Fire, Law, EMS) d) Dispatch Center e) Nature/Response Type f) Priority g) Response Area/Zone h) Response Type i) Station j) Transport Destination (Code) k) Unit/Resource 1) Unit Status The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC 02025 CentralSquare Technologies,LLC Page 14 Docusign Envelope ID FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 3 m) Zone (Map Data) This document is limited to standard menu-driven code mapping functionality.Complex mappings that require custom scripts is not included as standard functionality. The following are examples of non- standard customizations which will need to be scoped separately: a) Using a combination of factors to determine which code to send on a shared incident. For example, sending a Call Nature of"Structure Fire"for Fire calls and "Fire Assistance" for Law calls when a shared Incident has spawned two or more incidents in a separate CAD system. b) Changing the Call Nature based on which unit is requested. Custom Scripts: If customization is necessary,this will generally be done using custom scripts. Writing of any custom script is not included as part of standard functionality and will be scoped separately. 3.1.2. Call/Incident Related Data Supported CAD Incidents Fields:The following CAD Incident fields are supported for sharing by the CAD-to-CAD Hub. CentralSquare will not support fields that are not provided or accepted by the CAD system. a) Agency Name b) Apartment Number c) Building Number d) Call Nature (Accident,Structure Fire, Heart Condition,etc.) e) Call Priority(P1,P2, P3,etc.) f) Caller Address g) Caller Name h) Caller Number i) City j) Comments k) Cross Street(includes upper and lower cross streets) 1) Discipline(i.e., Fire, Law, EMS) m) Dispatch Center n) Disposition o) Latitude/Longitude (Decimal Format) p) Location(common place name-Central Park, County Library, etc.) q) Radio Channel r) Response Area/Zone s) State t) Street Address u) Time Stamps V) Zip w) Zone (Map Data) The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 15 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,XM IN CAD-2-CAD Unify Note: Standard functionality is limited to sharing of text and translated codes. If the CAD system reacts in an undesirable way to updates, (such as spamming the narrative with unnecessary comments), the data field causing the problem should be disabled. Services to provide more complex manipulation of data sharing will need to be scoped separately. Updates and Synchronization of Shared Incident Data: Updates to the following event fields may be configured to share either as a direct update to the call record or as a pre formatted comment added to the narrative. a) Apartment Number b) Building Number c) Call Nature(Accident,Structure Fire, Heart Condition,etc.) d) Comments e) Cross Street f) Radio Channel g) Street Address Note: Standard functionality is limited to simple updates of the call data. If the CAD system reacts in an undesirable way to updates, (such as spamming the narrative with unnecessary comments),the data field causing the problem should be disabled. Services to provide more complex manipulation of data sharing will need to be scoped separately. Address Validation: Each CAD system may store address location information differently creating the potential for shared addresses to not validate. It is expected that some addresses may not validate automatically and may require some manual intervention by a dispatcher to correct. Note: Standard functionality is limited to the exchange of text-based address fields. Services to provide more complex manipulation of address data such as changing "St"to"Street" in order to improve shared address validation will need to be scoped separately. Comment Sharing:Comments refers to any notes, remarks,or narrative entered in your CAD system that are sent to the CAD-to-CAD Hub and potentially shared with other CAD systems. If implemented in the Adapter and supported by the CAD, The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced,, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 16 Docusign Envelope ID.FCF14105-6698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MJFJ CAD-2-CAD Unify 004 sharing of comments can convey critical information and be very useful. However, excessive sharing of non-critical comments runs the risk of overloading dispatchers with unnecessary information. It is highly recommended to limit comment sharing using configuration options in the Hub. a) One of the following maybe used to determine how comments will be shared: i. Only share comments that contain a key text string,such as "##SHARE" ii. Removing comments that follow a specific pattern, This feature may be used to remove automatic system messages that are not useful to other dispatch centers. iii. Share all comments (not recommended) iv. Disable comment sharing entirely b) The Customer is responsible for configuring the Hub to limit comment delivery, including determining which text strings will be used to filter comments and adding them to the system. c) CAD system may have different sources of incident comments. For example,a CAD may provide a static information from "Basic Notes"completely separate from a "Running Comment Log." Usually only comments from the "Running Comment Log" are implemented in the Adapter shared by your CAD. The Customer and participating agencies,working with the Provider are responsible to configure that Adapter to share the appropriate comment data. d) Similarly, if there are confidential comments that should not be shared by your system,configurations can be set to block those from being viewed by other CAD systems or in the Hub. Note: Due to inconsistencies in how each CAD system generates additional system comments as well as how each CAD processes comments and messages coming from the Hub, it is possible that some duplicate or redundant comments may result. While the Hub has been designed to reduce unnecessary comments as much as possible,some edge cases may still result in unwanted comments.Customizations needed to remove duplicate or unwanted comments outside of the standard features mentioned here will need to be scoped separately. 3.1.3. Unit/Resource Related Data Supported Unit Update Fields:The following unit fields are supported for CAD-to-CAD sharing by the CAD-to-CAD Hub system. CentralSquare will not support fields not provided by the CAD system. a) Agency Name b) Assigned Call Number(when assigned to a call) The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,L.L.C. ©2025 CentralSquare Technologies,LLC Page 17 Docusign Envelope ID:FCF14tD5-B698-0559-A4DA-6F0572029279 Exhibit "A" Round Rock Police,X MWA CAD-2-CAD Unify �. c) Assigned Call Unique ID (when assigned to a call) d) Heading e) Latitude/Longitude (Decimal format) f) Location g) Signed On Status h) Speed i) Station j) Status k) Time at Coordinate 1) Time at Current Status m) Transport Destination (Code) n) Type of Unit o) Unique Unit ID p) Unit Number Unit Status Sharing: Real-time unit status updates can be shared between connected CAD systems, including AVL data (if available) by mapping physical to external units in the Hub. (External means placeholder or virtual units defined in a system that represent a physical unit in another system.) a) Available/Unavailable Status:When a physical unit is assigned to a non-shared incident in the unit's owning CAD,other systems with an external mapping to that unit receive unit status updates that the unit is unavailable. Once the unit clears the scene or is otherwise available for dispatch, an available status will be sent for that unit to other systems. b) True Unit Status for Shared Incidents:When a physical unit is on a shared incident,detailed unit updates (whether the unit is dispatched,enroute, arrived, etc.)will be shared with the other systems sharing incident. c) Unit Control: Once a resource request for a unit has been granted,either explicitly or implicitly, control of that unit is shared with the requesting system/agency. If implemented in the Adapter and supported by the requesting CAD,the status of that unit can be set by the requester.A system-to-system message containing the updated unit status will be sent to the unit's owning system. If implemented in the Adapter and supported by the owning CAD,the true status of the unit is updated. d) Limiting AVL Updates: Due to the potential for high volumes of unit status and AUL updates,CentralSquare reserves the right to restrict the frequency of such updates in order to maximize overall system performance. e) CAD System Dependencies Regarding Unit Statuses:The Hub is dependent on the Adapter and the CAD system to provide and consume up-to-date information. Unit status syncing can be impacted by momentary network outages,system processing delays,or other temporary issues. It is not uncommon for units to The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 18 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,X MMIA CAD-2-CAD Unify occasionally be out of sync between systems for short intervals but is quickly corrected by a subsequent successful unit status update. If a unit is requested by a system/agency in error due to out-of-sync unit information,denial of the resource request by the owning CAD system will override the out-of-sync status and notify the requester the unit is unavailable. Otherwise, manual dispatcher intervention may be required either through exchange of incident comments or a phone call. f) This document is limited to sharing standard translated unit status updates and AVL data.The following are examples of non standard customizations which will need to be scoped separately: i. Sending different unit status updates based on the unit type being updated such as 'On Scene'for law units and 'On Scene Staging'for fire units. ii. Sending fabricated progressive unit status updates in order to satisfy the unit status progression requirements of the target CAD system. For example,sending multiple unit status updates such as'Dispatched', 'Enroute'and 'On Scene' in order to reflect a single status update of'On Scene'from the sharing CAD. Handling these out-of-scope requirements should be part of the receiving CAD Adapter. 3.1.4. System Administration System Administrators:System Administrators have access to the setup and configuration of the CAD-to-CAD Hub for all connected CAD systems and participating agencies. Changes made by the administrator can potentially affect another agency inadvertently. For this reason,System Administrators should regularly consult and coordinate together before making configuration changes to the Hub. a) It is the responsibility of the Customer and participating agencies to determine which individuals will be assigned as System Administrators. b) When an administrator change is made,a log entry is created that describes the change made,the date and time, and the user that made the change. c) System Administrators can create new users and assign permissions. User Administration: Users are administered at both the system and agency level. System administrators may create users and assign permissions for all users.Agency User Administrators,which are created by System Administrators, may only do so for the agencies to which they are assigned. ay It is the responsibility of the Customer and participating agencies to determine which individuals will be assigned as Agency User Administrators at the agency level. The contents of this material are confidential and proprietary to CentralSquare Technoiogies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 19 Docusign Envelope ID FCF141D5-8698-4559-A4DA-6FO572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify PrIll b) Some configuration settings may be reset for all users across all agencies. These include: i. The amount of time that inactive calls are displayed ii. The amount of time that toast notifications are displayed (if used) iii. Users may change these settings on an individual basis if desired. c) User administration tasks such as creating new users and user groups, assigning permissions, resetting passwords,and Portal configuration settings are the responsibility of the Customer and participating agencies. d) User groups may be configured using Filters so that only certain calls and units are visible. Incident comments may also be configured so that the incident is visible, but comments are not. GIS Sources:The Hub system uses your geographical information systems (GIS)data sources to build maps. By copying the GIS sources that you want to use to build your maps into a folder,you can then import them into the Hub through the Hub Portal user interface.The Hub Portal supports the display of active calls and units on a GIS map view for situational awareness.The Portal provides GIS layer import tools for the Customer and agencies to import their own map files including but not limited to ESRI and other standard shapefiles and image files(i.e. Geographic or State Plane). The GIS layer import tool only takes minutes to load the data, but note that when importing map files, there will be downtime. Recommended GIS Map Data Elements are: Boundaries, Stations(Police/Fire), Freeways/Interstates, Major Streets,Waterways, Parks,and Address Points (optional).The Customer and agencies are responsible for providing, loading,and updating the GIS map data for a single,consolidated view for all agencies connected to the Hub. The frequency of GIS updates are determined by the Customer and participating agencies as they have no bearing on geo validation,they are just a visual tool. Note: Beyond basic training and initial assistance in configuring GIS information in Hub, all other GIS related effort is the responsibility of the Customer and participating agencies. System Connections: Each system Adapter connects to the CAD-to-CAD Hub over a secured connection provided and maintained by the Customer and agencies. For bi- directional interfaces an HTTP connection (https://URL:port)is required at each The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 20 Docusign Envelope ID:FCF141D5-B6984559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 0 endpoint(Hub side of the network and the Adapter side).All firewall configuration and configuring of ports is the responsibility of the Customer and participating agencies. 3.1.5. Data Retention and Backup CAD for Data Retention:The CAD-to-CAD Hub provides call and unit information to each respective CAD system as the authoritative method for permanent data retention. The Hub is not designed as a data warehouse for long-term storage and retrieval. A separate interface may be used to send call and unit updates to a client-provided database for long-term storage. Data Purging:Portal administration provides a setting to purge data older than a certain number of days. This feature may be set to retain data indefinitely, but this is not recommended. Data purging occurs automatically without adversely affecting the system in Production. System Backups: System backups may be conducted manually in two ways using the Application Manager tool accessible from each app server. a) Backup procedures are provided for both rollback and full system restore scenarios. In the event of a system upgrade and subsequent rollback,a manual backup is conducted first. This backup may be easily restored by with a simple process of selecting the backup file and restoring it using the application manager tool. b) To prepare for a full system restore, CentralSquare will provide files and documentation to install the system on new or existing servers. A manual configuration export should also be conducted periodically to capture the most recent configuration updates. This configuration export is easily imported using the application manager tool. CAD interfaces will need to reconnect with new credentials from the newly restored system. In the case that the customer opts to conduct full database backups, a full database restore may take the place of configuration exports and imports. 3.1.5. Portal Features Overview:The Hub Portal is a thick client installed on a Windows-based workstation. The Portal is used to display call and unit related data as well as administrative tools for system configuration. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 21 Docusign Envelope ID FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX OWA CAD-2-CAD Unify 004 Call and Unit Display:The Hub Portal displays call and unit information in the dispatch view in real-time. This includes separate list and map views of current calls and units as well as a call details view. The information contained here may be limited based on filters applied to each user group. Hub includes the following tools for viewing call and unit-related information. a) Calls List—Displays currently open calls in a list view b) Call Details —Displays detailed information about a call including comments, connected calls,and assigned resources c) Units List—Complete list of units and current status d) Map View Calls and units are shown on a map. Geofences and markers may also be created and shared with other user groups Toast Notifications: Pop-up notifications that display in the lower-right corner of your screen and display call and unit information based on pre-configured business rules. These notifications may be used to bring attention to bi-directional call-sharing actions, or to bring bi-directional functionality to centers that may have a publish-only or no interface whatsoever. User Preferences:Allow the user to adjust color schemes,when stagnant calls disappear from view, configure toast notifications, and enable/disable connection status monitoring. Admin Alerts: Historical display of email and text message alerts that have been sent to your user. Diagnostics and Log Views:Tools for troubleshooting and identifying information shared with each interface. Connection Monitoring:The connection between each CAD system and the CAD-to-CAD Hub is continually monitored by the CAD adapter through heartbeat transactions to detect network failures.The Hub also monitors system network connections through heartbeat transactions and network errors. Users are notified of detected disconnects in the following ways: a) If the Hub detects a potential disconnect such as lack of a heartbeat or a network error with any CAD system,a warning will display through the Connection Status Monitor in the Hub Portal. A subsequent reconnect will remove this warning. b) If a CAD system has not transacted any updates to Hub for a configurable amount of time,a warning will display through the Connection Status Monitor in the Portal. This may indicate that although the Adapter continues to share heartbeats The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 22 Docusign Envelope ID:FCF141D5-8598-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MJVA CAD-2-CAD Unify 13 with Hub, it has lost the connection with its CAD system.A subsequent transaction will remove this warning. c) If the CAD detects a potential disconnect to the Hub it is responsible to notify its users through the CAD user interface. Settings:System and user administrators access and adjust system settings including connections, business rules,filters,and user administration using the Portal. 3.1.7. Information Sharing Redundancy CAD-to-CAD sharing errors may result from various sources including the following: a) User error b) CAD system error c) Network error d) CAD-to-CAD Hub error e) Administrator error f) Unforeseen circumstances If there is an error in the CAD-to-CAD process,dispatchers must be aware of the problem immediately so that other means may be used to communicate such as phones or radios. The following are suggested methods to provide redundancy and checks to ensure awareness of CAD-to-CAD sharing. a) User error confirmation phone calls b) Unit status timers in the CAD system c) CAD-to-CAD Hub email or text message alerts d) Hub Portal notifications e) Hub light towers 3.2. CentralSquare Unify External System Dependencies The ability of CentralSquare Unify Hub to perform its functional requirements depends on the external systems' ability to do the following: 3.2.1. Bi-directional Adapters Unify relies on bi-directional Adapters to external CAD systems which should support the following capabilities: The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LIC. 02025 CentralSquare Technologies,ILC Page 23 Docusign Envelope ID:FCF141D5-6698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 004 Continuously provide and receive updated CAD incident and unit status data to and from the CAD-to-CAD Hub a) Share/receive new incidents b) Update data fields on current incidents c) Update dispatcher comments d) Assign units/resources to current Incidents e) Provide unit status updates including AVL data f) Present information to the CAD operator in an appropriate way Continuously provide and receive updated unit information to and from the Hub a) Unit assignment to incidents b) Unit status updates c) Send and receive unit requests Connection notices: Provide connection and failure notices to the dispatcher when a prolonged disconnect or outage is detected. Synchronize(refresh)active CAD data upon connecting including current CAD incident data and unit status data. 3.2.2. Other Considerations Functionality: Data,functionality,and operational incongruences between the connected CAD systems may limit the level of interoperability achievable.Although the CAD-to-CAD Hub may support certain capabilities, CentralSquare cannot provide functionality that the external system does not support. In cases where there is a gap between needs and what the CAD system is able to provide,converting data to comments or other methods may be used but certain limitations will naturally be beyond the CAD-to-CAD Hub's ability to work around. 3.2.3. External System Adapter Requirements The dependencies listed in this section are an overview and are for general awareness.The CAD-to-CAD Hub SDK provides a more complete set of detailed requirements for the external system's Adapter.The Customer and participating agencies should require the provider to comply with all requirements of the SDK. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 24 Docusign Envelope ID:FCF141D5-6698-4559-A40A-6F0572D29279 Exhibit "A" Round Rock Police,TX EWA CAD-2-CAD Unify 4. PROJECT CONTROLLING PROCESS 4.1. Overview Project Controlling Processes are established early in the Project life cycle during the Planning Phase and described within the Project Management plans. Project Control is the process that includes completing regularly scheduled Project progress meetings and the use of regularly delivered Project progress reports,as well as implementing the processes needed for Communication Management, Risk Management, and Change Management.The process begins during the initiation process and concludes at the end of the Project. The establishment of defined processes for Customer communication (contact persons and reporting methods) provides a basis for effective and regular communication.This supports the previously noted processes necessary for successful Project outcome. As part of the Controlling Processes, CentralSquare utilizes a series of measurements and management reviews to mitigate the effect of these variances. Checkpoints or milestones are planned into each phase of the Project to measure performance and determine if the Project is ready for the next phase. Checkpoints are key tasks that act as gates to the next phase of a project.A delay in a milestone may cause a delay in starting or completing subsequent tasks; in effect creating a risk to the overall Project.Therefore, CentralSquare's Project staff closely monitors checkpoint tasks and milestones and promptly notifies the Project Manager of any delay or failure with a milestone task. Milestone delays on the part of either party will trigger an overall review of Project activities so that risks can be assessed and properly managed. In the event that either party becomes aware of a delay, notification shall be provided to the other party as soon as reasonably possible. Evaluation of overall Project status at each checkpoint is essential to ensure that the Project is effectively progressing toward completion and that new risks are not being introduced. In many cases, Project activities leading to a checkpoint are interrelated to later scheduled tasks. Success at checkpoints diminishes the risk to the Project going forward. Incomplete actions at a checkpoint may prompt delays and a rescheduling of the Project. For example,delays in completing or approving CSDs will delay the start and completion of the configuration phase,which may ultimately have an impact on the projected Go- Live date. Depending upon the importance of the Deliverable,these kinds of delays can have a cascading effect upon the Project Schedule including Go-Lives. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of Central5quare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 25 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify POO As part of the Project controlling process, upon completion of significant milestones and or tasks,CentralSquare will submit a Task Completion Report("TCR")to Customer.The TCR serves as a formal tool for the purpose of verifying with Customer that the work has been performed,services rendered,and products delivered according to the requirements specified within the SOW and/or related documents. TCRs are presented to Customer by CentralSquare's Project Manager for signature.Some TCRs may trigger a Project payment, in accordance with the payment terms within the Agreement. Upon execution of a TCR that is tied to a Project payment milestone, Customer will receive an invoice from CentralSquare's Accounting Department which must be paid based on the terms and conditions of the Agreement. The TCR will include the following information: a) Description of work performed, and products delivered. b) Comments noting any special circumstances. c) Product/Service deliverables listing the Agreement line items that are being recognized as delivered and will be invoiced. d) Related Payment Terms in accordance with the Agreement,for Agreement line items that will be invoiced relative to the TCR. 4.1.1. CentralSquare Responsibilities a) CentralSquare will prepare and submit TCRs for Customer's signature upon completion of the applicable task. b) The TCR will cite the appropriate SOW reference. c) TCRs that trigger a payment will include the payment amount in accordance with the Agreement payment schedule. 4.1.2. Customer's Responsibilities a) Customer will review and approve TCRs within a five (5) business day period from the time of receipt less any challenges to the validity of the report. b) In the event that Customer disagrees with a TCR,Customer shall submit to CentralSquare a written explanation detailing why the Customer believes that the subject of the TCR and/or tasks have not been completed in accordance with the Purchase Agreement or this SOW. Such notification from the Customer shall be provided to the CentralSquare Project Manager within five(5)business days of receipt of the TCR. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 26 Docusign Envelope 10:FCF141D5-13698-4559-A41DA-61`0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify O 4.2. Change Management Process Either party can request changes to the scope of the project at any time.Since a change may affect the price, project deliverables,this SOW,the supporting project schedule, and/or the terms of the Agreement for this SOW, both parties must approve each change in writing and agree on the impact each change may have on the Agreement and related attachments. The purpose of the Change Management Process is to manage any significant changes to the Project as described in this SOW or related documents as referenced within the SOW.These changes may include but are not limited to a modification to Project scope, Standard or Custom products'functionality,CentralSquare and Customer's identified roles and responsibilities, Project payment terms, and modifications to the scope or delivery location of services within the Project. All significant changes must be documented through the Change Management Process.The type of documentation needed will depend on the nature and significance of the change. A Project Change Order will be the vehicle for communicating and approval of the changes. Whether initiated by Customer or CentralSquare,all Change Orders will be documented by the CentralSquare Project Manager.The Change Order shall describe the requested change, the party requesting the change, and the effect the change will have on the project, including the price, project deliverables,this SOW,the supporting project schedule, and/or the terms of the Agreement for this SOW. All Change Orders must go through the CentralSquare's internal approval process before they can be presented to Customer for review and approval. Once the Change Order is generated,Customer Project Manager and CentralSquare Project Manager will review the proposed change and communicate as necessary to answer any questions, and/or work to resolve any issues preventing acceptance of the Change Order by both parties. Upon the approval by both parties the Change Order will be authorized for implementation. The creation of some Change Orders may,depending upon the scope of the requested change, require fees for CentralSquare to properly investigate and scope the requested change. If additional fees are required by CentralSquare to create a Change Order,those fees will be identified and communicated to Customer Project Manager prior to CentralSquare's investigation of the requested change. In such situations,CentralSquare will only proceed with the investigation required to create the Change Order if Customer has agreed to pay the additional fees associated with creation of the Change Order. Additional deliverables or Project deletions in terms of Software and services will require a mutually agreed upon Change Order. It must be noted that the later in the Project that a change is requested,the greater the likely impact it has in terms of costs, risks, and The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 2'7 Docusign Envelope ID:FCF141D5-B6984559-A4DA-6F0572029279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 13 timescale. It is recommended that Customer not delay any review activity as it is a best practice to discover potential changes as early as possible. In some cases, it may be more appropriate to plan modifications for Post-Go-Live delivery. 4.2.1. CentralSquare Responsibilities a) Change Orders will capture necessary information required to prepare a Change Order and submit to the Customer. 4.2.2. Customer Responsibilities a) When applicable,Customer will identify the services or deliverables that will be subject to a Change Order, per the Agreement between both parties. b) When applicable,Customer will identify changes to application features or functionality, Interfaces,or any other Systems that will require a change order.This process may also include participation in the requirements process. c) Customer will approve and process Change Orders in a timely manner. 4.3. Project Reporting CentralSquare will provide Monthly Status Reports advising Customer Project Manager and key Customer Project Stakeholders of the progress and status of project activities. This report will include the significant accomplishments, planned activities, issues,and potential risks associated with CentralSquare and CentralSquare's Subcontractors' Deliverables.The Project Status Reports will include the following: a) Accomplishments during the Reporting Period b) Planned upcoming activities c) Issues d) Risks e) Key Action Items In addition,the CentralSquare Project Manager will hold bi-weekly status meetings/conference calls to update Customer on the status of the Project and key action items and deliverables. CentralSquare will provide an updated Project Schedule advising Customer Project Manager of the progress of project activities.The Project Schedule may be lacking the detailed tasks for Customer team, and Customer may add such tasks, owners,and The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 28 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MA CAD-2-CAD Unify durations to the Project in collaboration with CentralSquare Project Manager.The Project Schedule will consist of the following: a) Major Tasks b) Task Responsibility c) Task Duration d) Major Milestones e) Tasks Completed f) Tasks in Progress 4.3.1. CentralSquare Responsibilities a) Provide a written report of Project status once a month. b) Conduct status meetings/conference calls every two weeks. c) Maintain an up-to-date Project Schedule. 4.3.2. Customer Responsibilities a) Review the written report of Project status and provide feedback within five (5) business days in order to ensure that the documentation is correct. b) Participate in Project status meetings. c) Ensure participation of personnel in tasks and meetings. 4.4. Document Review In the course of the Project,CentralSquare will deliver several documents to Customer for review.These documents will include but are not limited to the Functional Acceptance Test Procedures, Project Schedule,and OSD for the Project.Approved documents are returned to the CentralSquare Project Manager.All documents will be provided in electronic(soft copy). If Customer desires printed (hard copy) documentation, it is their responsibility to print and bind the desire copies.The CentralSquare Project Manager will retain a copy and provide Customer with a copy. Should Customer find any document unacceptable,Customer must provide specific reasons in writing to the CentralSquare Project Manager.CentralSquare can then assess any required corrective measures and make revisions or modifications to provide acceptable documents within a mutually satisfactory timeframe. Status Reports are not subject to approval. The contents of this material'are confidentia�and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prvor written consent of CentralSquare Technologies,I.I.C. ID2025 CentralSquare Technologies,LLC Page 29 Docusign Envelope ID:FCF141D5-13698-4559-MDA-61F05721329279 Exhibit „A" Round Rock Police,TX MWA CAD-2-CAD Unify In order to ensure compliance with the Project Implementation Schedule, Customer is responsible for the review of such documents and providing any comments to CentralSquare within five (5) business days. 4.4.1. Documents Subject to Customer Approval (via signature) a) Change Orders b) Operational Scenario Documents(OSD) c) Functional Acceptance Test Procedure documents d) Task Completion Reports 4.4.2. Documents Subject toCustomer Review not Requiring Approval Note:The Project Schedule and any changes hereto are to be mutually agreed upon between Customer and CentralSquare. a) Project Status Reports 4.4.3. CentralSquare Responsibilities a) Distribute the documents to Customer. b) Coordinate the process to consolidate comments and edit documents. c) Manage the signoff process for applicable documents and the distribution of originals to Customer and CentralSquare for filing. 4.4.4. Customer Responsibilities a) Review the documents presented and provide the appropriate information back to CentralSquare within five(5) business days for configuration sheets, Change Orders and/or Sales Orders. b) Review the documents presented and provide the appropriate information back to CentralSquare within five(5) business days for requirements documents defined above. Unless unanticipated changes to the Project Schedule would warrant a shortened turn around. 4.5. Third-Party Management CentralSquare will be responsible for the management of third parties that have been identified as Subcontractors or executed Change Orders to the Agreement. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 30 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 'A - As part of the Subcontractor agreement, all communications between those third parties and Customer will be managed by CentralSquare. Any communication directly between Customer and third parties that may require or imply the promise of a material change in scope or responsibilities will not be acknowledged by CentralSquare unless an appropriate Change Order has been prepared. Conversely, Customer will be responsible for the management of third parties that CentralSquare is not responsible for. Customer will be responsible for the facilitation of discussions and the acquisition of materials from those third parties that are necessary for the configuration and development of Customer's System. 4.5.1. CentralSquare Responsibilities a) Assume responsibility for third parties that are the responsibility of CentralSquare within the terms of the Agreement between CentralSquare and Customer. b) Process any Change Orders that may arise from a material change in scope where third parties are concerned. c) Inform Customer when configuration and or programming will require interaction and/or documentation from a third party which is not the responsibility of CentralSquare under the Agreement between CentralSquare and Customer. 4.5.2. Customer Responsibilities a) Work directly through CentralSquare with regard to third parties that are the responsibility of CentralSquare. b) Review,sign and process any Change Orders that may arise from a material change in scope where third parties are concerned. c) Facilitate interaction between CentralSquare and third parties not the responsibility of CentralSquare to include conference calls,answers to questions and documentation as requested The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 31 Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify L` S. PROJECT INITIATION AND PLANNING 5.1. Overview Project Initiation and Planning involves gathering the necessary Project specific information in order to produce a Project Management Plan and a Project Schedule. In short, Project Planning consists of those processes designated to establish when and how the Project will be implemented while further elaborating on Project Deliverables. Most of the information exchange between Customer and CentralSquare during this process is at a high-level and consists of interaction between both Project Managers and a small group of Project stakeholders. Major Deliverables for the Project Planning phase are the specific Project Management Plans, and a baseline Project Schedule. The project must be managed in a manner that will allow for the adjusting of the Project Management Plan and Project Schedule to address the circumstances that affect a project during Project Execution.As a result of these changes during the Project life cycle, Project Planning will overlap each subsequent process during the Project. Typically, Project Planning tasks will decrease in frequency as checkpoints are completed and as the Project nears Go-Live and Project completion. Note:The Project Schedule is a living document,subject to change during the course of the Project due to several factors such as change in Project scope,scheduling conflicts,delay in approving project documents, resource availability, etc. All changes to the Project Schedule will be discussed between both parties and will be incorporated within a published schedule upon approval from Customer and CentralSquare. 5.1.1. CentralSquare Responsibilities a) Assign a Project Manager to the Project to participate in Initiation phase activities. b) Produce required documentation to support Initiation activities (such as System Planning Guide,etc.) c) Identify and engage the CentralSquare Project team responsible for carrying out Project Execution. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of Central5quare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 32 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,X CAD-2-CAD Unify d) In collaboration with Customer,develop the Project Management Plan (includes the Communication Management Plan, Risk Management Plan,and Change Management Plan). e) Baseline the Project Schedule. f) Prepare and submit the TCRs for Customer acceptance of the Project Management Plan asdefined above. g) Develop and submit invoice for payment due at execution of the Agreement. 5.1.2. Customer Responsibilities a) Assign a Project Manager for the Project to participate in Initiation phase activities. b) Identify and engage Customer's Project team. c) Review and comment on the CentralSquare Project Management Plan and the Project Schedule. d) Review and comment on CentralSquare provided documentation to support Initiation activities. e) Approve the TCRs for the Project Management Plan within five (5) business days. 5.2. Project Kickoff During the planning phase,the CentralSquare Project Manager will hold a Kickoff Meeting with Customer's Project team. During the Kickoff Meeting,the CentralSquare Project Manager will provide an overview of the following: a) The CentralSquare execution process. b) A high-level description of Project Deliverables. c) Roles and responsibilities for the Project team members. d) A high-level review of the preliminary Project Schedule including projected Project milestones and checkpoints. e) Describe the work that has been either completed, is in progress or is due to begin within the immediate future. f) Review any project related questions from Customer's team. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 33 Docusign Envelope ID FCF141D5.6698-4559-A41DA 61F0572D29279 Exhibit "A" Round Rock Police,TX MAN CAD-2-CAD Unify 5.2.1. CentralSquare Responsibilities a) Prepare the agenda and set a date for the Kickoff that is convenient to Customer and CentralSquare Team. b) Distribute any documents that Customer should review in advance of the Kickoff Meeting. c) Conduct the Kickoff Meeting. 5.2.2. Customer Responsibilities a) Work with the CentralSquare Project Manager to facilitate scheduling a date for the Kickoff Meeting. b) Schedule the appropriate personnel from Customer's team to attend.This should also include key stakeholders that may not participate routinely in Project operations, but who have authority or responsibility over the Project. c) Provide adequate accommodations to include adequate seating and audio- visualequipment including a projector(s),screen, and whiteboard. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 34 Docusign Envelope ID FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX NWA CAD-2-CAD Unify 004 6. PROJECT EXECUTION 6.1. Overview Project Execution focuses on the development and delivery of Project Deliverables. Processes will be iterative and consist of: 1) a review of Deliverable documents; 2) development,configuration, installation and testing of software and hardware deliverables, and 3)delivery of Project related services such as Project related training. These processes are iterative in nature with a number of checkpoints to evaluate Project progress and where applicable,to initiate Change Management processes. Each Deliverable has a closing process which consists of specific completion criteria.These Deliverable closing processes are independent from the closing process of the Project. 6.2. System Installation System installation is one of the early processes in the Project implementation phase and has a significant impact on and critical dependency on a number of key activities. On-premise hardware provisioning is the responsibility of the Customer or CentralSquare. Installation of CentralSquare software for the on-premise hardware is the responsibility of CentralSquare. 6.2.1. On-Premise Components CentralSquare will either purchase and provision the server hardware via a partner,or if the Customer is purchasing the hardware CentralSquare will give guidance on hardware specifications for Customer purchasing. CentralSquare gives guidance on virtual provisioning after on-premise hardware has been purchased and integrated into the Customer's network. CentralSquare utilizes a sizing and pre-requisites document called an ISR (Installation Services Request)to convey specifications and guidelines for the Customer to create the virtual machines needed for software installation. All components for the CAD-to-CAD solution may be virtualized.The Customer will provide all required server hardware and host the on-premise Hub server cluster. The server cluster is designed to provide scalability and redundancy to the Hub solution.Typical server clusters contain one(1) load balancer,two (2)app servers, and three (3)database The contents of this material are confrdential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to othors without the prior written consent of CentralSquare Technofogies,LLC. 02025 CentralSquare Technologies,LLC Page 35 Docusign Envelope ID:FCFl4iD5-66984559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MIFA CAD-2-CAD Unify servers, however discovery for server resources may change the requirements for this project. The administration services of the on-premise environment is the responsibility of the Customer, including support,operation,and maintenance of the underlying infrastructure. On-premise installation of CentralSquare software takes place after on-premise servers are provisioned and prepared for installation. 6.2.1.1. CentralSquare Responsibilities a) Host Technical meeting with Customer network\systems administration staff. b) Provide port,protocol information to Customer for firewall rules. c) Provide guidance on virtual provisioning for the On Premise system. d) Provide URLs and any other paths for Customer connectivity. e) Perform connectivity tests with Customer assistance at least one week prior to any workshops. 6.2.1.2. Customer Responsibilities a) Attend Technical meeting with CentralSquare resources. b) Acquire ISP connections. c) Provision On-Premise systems. d) Open firewall as directed by CentralSquare Technical staff. e) Provide routing rules to route traffic through the VPN tunnel as advised by CentralSquare technical staff. f) Perform connectivity tests with CentralSquare assistance at least one week prior to any workshops. 6.2.2. Implementation Overview of CentralSquare Unify The CAD-to-CAD Hub is implemented through a series of standard steps and process gates designed to ensure that operational needs are identified, configurations are verified,and tested to validate proper functionality prior to Go- Live. The implementation includes tasks to be completed by multiple stakeholders including CentralSquare,Customer and agency personnel, and the 3rd party system The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 36 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 0L Provider.The tasks below are an overview and will be refined in a detailed project schedule with the Customer upon project Kickoff. 6.2.2.1. CentralSquare Unify Hub Initial Installation and Configuration CentralSquare will provide support for the initial system configuration. This will include the following: a) Installing the database and application server software for the Hub. b) Once network connections have been established between the servers by the Customer and participating agencies,CentralSquare will establish software connections between each server. c) Establish each environment such as Test,Training,and Production as set forth in this document and the accompanying Agreement. d) Configure the connection parameters for each third party system connection. Note it is the Customer and participating agencies responsibility to ensure network connectivity between servers are established. e) Load initial data mapping sets for the following codes. Note that mapping and translation of these codes is the responsibility of the Customer. i. Agency ii. Dispatch Centers iii. Nature/Response Type iv. Unit/Resource v. Unit Status vi. Unit Type f) If the project involves joining a new dispatch center to an existing hub or upgrading a publish-only interface to a bi-directional interface,some or all of these steps may have been already completed.The associated Agreement will outline exceptions or additions to these steps. 6.2.2.2. CentralSquare Unify Hub System Setup The tasks listed under system setup may be executed simultaneously. CAD Provider Adapter Implementation and Configuration: Includes the installation and configuration of the CAD Provider Adapter by the Provider or by CentralSquare as defined in the SOW, Section 2.6—Deliverable System Connections on CentralSquare Unify Hub. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 37 Docusign Envelope ID.FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MA CAD-2-CAD Unify 004 Software Installation: Basic server configuration is added for each interface on the CentralSquare server and the Portal client software is delivered to the Customer and participating agencies.Software installation marks the completion of the system setup tasks. 6.2.2.3. Initial Discovery and Configuration A discovery phase will take place that will identify site-specific configurations for the Hub.These will be documented in an Operational Scenario Document (OSD)and signed off by the Customer,via a TCR, before the configuration phase begins.Specific configurations may be recorded in the documentation listed below. It is agreed that all shared can be exchanged in an electronic form,such as.PDF, .DOCX, .XLSX,etc.The OSD document will be updated as the agencies are implemented and brough online. a) List of CAD Codes:The Customer and participating agencies will provide a list of CAD codes and descriptions that will be mapped to those of other CAD systems through the Hub. Common codes include incident status, nature, unit status, units,agencies,cities,and jurisdictions. b) Code Mapping Document: Under the guidance of CentralSquare,the Customer and participating agencies will provide a list of mappings of the CAD Codes provided above to a common code set provided by CentralSquare.The common code set in the Hub facilitates mapping and translation to other agencies' codes, which is the responsibility of the Customer and participating agencies. c) Test Scenarios:CentralSquare will provide a standardized list of tests for acceptance. Other tests can be suggested by the Customer providing that they are within the scope of the accompanying Agreement. d) Configuration Documentation: Documentation may be added directly into the configuration screens of the Hub and is easily exported as text. This will serve as the primary form of technical documentation. e) Product Manuals: CAD-to-CAD Administrator's Guide will be provided electronically. The Customer's Project Manager and Subject Matter Experts play a critical role during this time. Discovery and configuration involve the gathering of business requirements,CAD codes,system configuration including code mappings on the CentralSquare Unify Hub. The results of the discovery and configuration sessions will be compiled, documented in an Operational Scenarios Document (OSD)and signed off by the Customer,via a TCR, before the configuration phase begins. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 38 Docusign Envelope ID:FCF141D5-6698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,X CAD-2-CAD Unify CentralSquare will provide OSD documentation as appropriate.The OSD document will be updated as the agencies are implemented and brought online. This task is considered complete upon completion of the customer questionnaire documentation and a joint review between the Customer,the participating agencies and CentralSquare. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 39 Docusign Envelope iD:FCF141D5-6698-4559-A4DA-6F0572D29279 Exhibit "A„ Round Rock Police,TX CAD-2-CAD Unify 31 7. CENTRALSQUARE UNIFY TESTING 7.1. Isolated CAD Adapter Testing CentralSquare and the Customer will develop a mutually agreed upon testing schedule. System testing will be conducted throughout the project in three (3)distinct periods. The Isolated CAD Adapter Testing will be conducted simultaneously with other implementation tasks and will largely involve CentralSquare Engineers and the Provider implementing its Adapter.This testing will use a CentralSquare Unify Hub Test environment,and test instances of the CAD system and Adapter. CentralSquare will use a CAD simulator to test all aspects of the connection between the Hub and the Provider's Adapter and CAD system. Sample data may be used to demonstrate the ability to view data using the Hub Portal client. Testing support from the Provider and assistance from the Customer and participating agencies are required.The Customer and participating agencies will identify and provide a CAD Administrator that can login to test CAD systems with its Adapter connected to the Hub.The CAD Administrator will work jointly with CentralSquare and the Provider to complete this testing. At the conclusion of the Isolated CAD Adapter Testing,the connection between the Hub and the Provider's Adapter and CAD system is demonstrated as data is successfully delivered to and visible using the Hub Portal client.This final testing demonstration shall take no more than five(S) hours per agency. 7.2. Provider End-to-End Testing Provider End to End Testing will be conducted when the Isolated CAD Adapter Testing is complete for each CAD system that is required to meet the standard incident and resource sharing requirements. It will involve CentralSquare Engineers,the CAD providers,the Customer, and the participating agencies. If a dependent CAD system is not ready for End-to-End Testing,the testing may proceed using a CAD simulator provided by CentralSquare. CAD Simulator testing does not replace End-to-End Testing with the CAD Provider.The Customer and the participating agencies will need to identify and provide a CAD Administrator that can login to the test CAD systems with its Adapter connected to the Hub.The testing period will be paused for resolution of Go-Live issues as defined in the SOW,Section 7.3—Functional Acceptance Testing. Defects found in the Adapter for each CAD system may also pause the testing period. CentralSquare,the Customer and the participating agencies will expedite where possible the resolution of any Provider defects. The contents of this material are confidential and propr;etary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. X2025 CentralSquare Technologies,LLC Page 40 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6FO572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify /1 At the conclusion of the Provider End-to-End Testing,meeting all the Adapter and CAD Provider testing requirements as defined in the OSD marks the completion of the Provider End-to-End Testing.This final testing demonstration shall take no more than five (5) hours per agency. 7.3. Functional Acceptance Testing (Customer End-to-End Testing) Once the Provider End-to-End Testing is concluded for each CAD system, Functional Acceptance Testing will be conducted by the Customer,the participating agencies, and the CAD Provider under CentralSquare supervision. Each agency will go through Functional Acceptance Testing when they are ready to connect to the system,so Functional Acceptance Testing may happen multiple times on the same CentralSquare Unify Hub.This final testing event shall take no more than sixteen (16) hours per agency. It is during the Functional Acceptance Testing that the Customer and the participating agencies,gain close familiarity with the CentralSquare Unify Hub and related functionalities. Expanded Standard Operating Procedures(SOPS)are more fully defined and tested by the Customer and the participating agencies, during this time.This is a Customer driven phase with assistance from CentralSquare.Changes required for Customer and agency SOPs are out of scope unless explicitly agreed. In order to confirm that all work has been completed under this SOW and that the system meets the functional requirements of the COTS Hub system,CentralSquare and the Customer will develop a mutually agreed upon functional acceptance test plan that is based on the criteria contained in the Operational Scenario Document(OSD)which will be incorporated during the project into the Unify Test Checklist.The Functional Acceptance Testing process consists of verifying and running standard functions tests in a format designed to verify the functionality of the CentralSquare Unify solution. CentralSquare will work with the Customer and the participating agencies to develop a mutually agreed upon testing schedule for the agencies. Following the completion of the Functional Acceptance Testing, any defects that are raised will be documented by CentralSquare and prioritized as follows: Priority Issue Definition Go-Live Issues Issues in the CAD-to-CAD solution identified during Functional Acceptance Testing with contractually required functionality that must be corrected prior to Go-Live. CentralSquare will research such identified issues and propose a plan for resolution. Go-Live issues will be corrected prior to Go-Live. Post-Go-Live Issues Issues in the CAD-to-CAD solution identified during Functional Acceptance Testing with contractually required functionality that can be corrected after The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 41 Docusign Envelope ID:FCF141D5-6698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 3 Go-Live.The Customer and CentralSquare will mutually agree these issues may be addressed after Go-Live.CentralSquare will provide a reasonable date for resolution of the Post-Go-Live issues. The Customer will agree to sign off upon the completion of each Functional Acceptance Testing session, acknowledging the delivery and receipt of the testing results,via a TCR. Upon resolution of any Go-Live or Post-Go-Live issues,the failed test(s)will be repeated by the participating agencies under CentralSquare supervision, until resolved.The Customer will agree to sign off on a TCR reflecting the completion of Functional Acceptance Testing when the testing has been completed with no Go-Live issues (i.e., a passing Acceptance Test). Upon completion of Functional Acceptance Testing, preparations for deployment may begin. A migration plan will be defined and executed. The Customer and participating agencies will train their own dispatchers from expanded SOPS defined during the Functional Acceptance Testing. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. ©2025 CentralSquare Technologies,LLC Page 42 Docusign Envelope ID: FCF141D5-B698A559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MWA CAD-2-CAD Unify PA3 8. CENTRALSQUARE UNIFY TRAINING 8.1. Training No training is included in this project—this project is changing CAD vendors. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 43 Docusign Envelope ID FCF141D5-B699-4559-A4DA-6F0572D29279 Exhibit "blit Round Rock Police,TX N CAD-2-CAD Unify �- 9. CONDUCT CENTRALSQUARE UNIFY PRE-GO-LIVE TASKS 9.1. Pre-Go-Live Preparation for cutover to live operations will be outlined in the Project Schedule and the Go- Live Plan four(4)to six(6)weeks prior to Go-Live. The Go-Live plan includes the overall timeline for the event, products involved, agencies involved, roles and responsibilities, established meeting dates/times, issue reporting and escalation process,transition to support and the communication plan. 9.1.1. Pre Go-Live Tasks: a) Customer to distribute final version of documentation to participating agencies outlining modifications to standard operating procedures. b) CentralSquare Project Manager and the Customer will ensure that all Go-Live deliverables are completed with related TCRs approved. c) CentralSquare Project Manager will schedule and monitor internal and Customer- facing Go-Live readiness checks during team planning meetings. d) CentralSquare Project Manager and the Customer Project Manager,along with key resources,will conduct separate planning meetings to draft/approve the Go-Live Plan. e) CentralSquare Project Manager and the Customer will prepare a Go-Live plan which provides details about the time period for the event, products involved,supportive roles and responsibilities,the overall timeline for the Go-Live, establishes meeting dates/times,the issue reporting and escalation processes,transition to support,and communications plan. 9.1.2. Go-Live Preparation: CentralSquare and the Customer will draft the CentralSquare Go-Live Authorization Letter for each Go-Live group.The Go-Live Authorization Letter confirms that the system has been installed and tested,and that the Customer agrees to proceed with moving the system to live operation. It confirms software is functional for a live environment,and that none of the currently identified issues are critical to the Go- Live. Date and time of the Go-Live is memorialized,the participating agencies,along with assurance the Customer technical team and subject matter experts will be available twenty-four(24)hours a day to support the Go-Live unless otherwise noted in the Agreement.The Customer is required to review and sign off on the Go- The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,UC Page 44 Docusign Envelope ID:FCF141D5-8696-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX 004 CAD-2-CAD Unify Live Authorization Letter no later than three(3)weeks prior to the scheduled Go- Live date. 9.1.3. Transition Presentation: CentralSquare will provide a presentation to the Customer to gain familiarity with the Support structure and methodologies. CentralSquare will assist in confirming that representatives designated by the Customer needing access to enter and track support tickets have credentials for CentralSquare access. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 45 Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6FO572D29279 Exhibit "A" Round Rock Police,TX OWN CAD-2-CAD Unify 10. CONDUCT CENTRALSQUARE UNIFY GO-LIVE 10.1. Go-Live Go-Live of the CentralSquare Unify solution for each of the participating agency entities into the Production environment is a highly orchestrated activity that will require resources from both the Customer,any participating agencies,CentralSquare,and the CAD Provider teams.The CentralSquare Unify Hub has the ability to deploy functionality on a case-by-case basis_ The migration plan may,for example,first deploy bi-directional unit status updates followed later by automated call sharing. Go-Lives are conducted on consecutive weekdays (Monday—Friday).Any CentralSquare Go-Live Support that is beyond the amount specified per the Agreement may be subject to an additional cost. a) "Go-Live" means the event that occurs when Customer first uses a System for Live Operations.A separate Go-Live may take place with respect to each System, each Interface,and each Modification. b) "Go-Live" means"First use in a non-test bed environment". The system is brought into production per the Go-Live Plan and the Go-Live Authorization Letter. Go-Live support is provided by CentralSquare as follows. • Go-Live Support:A total of three (3)consecutive days of remote support will be provided when the Customer goes live with the CentralSquare Unify solution. • Day 1- Day 3: Remote Go-Live Support—one (1)Consultant,eight(8) hours each day,during normal business hours(8:00am to 5:00pm local time). A TCR will be provided to the Customer for signature upon completion of the Go-Live event and CentralSquare provided support, per the Agreement. During Go-Live, issues are reported and managed by CentralSquare with the Customer's assistance. Upon cessation of Go-Live support by CentralSquare, issues are reported and managed by the Customer. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 46 Docusign Envelope ID:FCF141D5-B6984559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify �- 11. PROJECT CLOSURE 11.1. Project Closure Project closure activities commence when all project deliverables have been completed. Support of the systems will be transitioned to CentralSquare's Support and monitored per the Support and Maintenance Agreements. Major Task Description Post Go-Live Project Once complete, ensure CentralSquare project manager will provide TCR to Deliverables Customer for signoff of completed deliverables. Final Audit CentralSquare project manager will perform a final audit to ensure all Contractual obligations have been met. A final TCR will be provided to Customer to confirm the project is completed. Final Transition CentralSquare project manager performs final transition of Customer to Support who will become the primary conduit for entry,tracking, and resolution of system issues. Customer interaction is officially handed over from the CentralSquare project manager to the CentralSquare Customer Success Manager(CSM). Project Closure CentralSquare project manager performs administrative tasks to archive project documents and close the project. 11.1.1. CentralSquare Responsibilities a) Perform payment reconciliation,deliver final project TCRs which generate remaining invoices. b) Transition the CentralSquare point of contact from the Project Manager to the CSM and Customer Support Services Department. c) Provide continued support based on terms of Agreement. 11.1.2. Customer Responsibilities a) Provide approval of final Project TCRs within five (5) business days. b) Process payment of final invoices. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disCosed to others without the prior written consent of CentralSquare Technologies,I.I.C. 02025 CentralSquare Technologies,LLC Page 47 Docusign Envelope ID:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX OWA CAD-2-CAD Unify 004 12. Appendix A — Contracted Modifications to Standard CentralSquare Products Note: Any changes to the requirements documented in approved System OSDs are subject to Change Order. There are no product modifications proposed for this project. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 48 Docusign Envelope IO:FCF141D5-8698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX CAD-2-CAD Unify 00 - 13. Appendix E — Subcontractor Statement of Work Subcontractor Statements)of Work provided as applicable to the project. There are no Subcontractor Statement(s)of Work that are applicable to the project. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 49 Docusign Envelope ID:FCF14lD5-8698-4559-A4DA-6F0572D29279 Exhibit "An Round Rock Police,TX CAD-2-CAD Unify 0- 14. Appendix J — CentralSquare Connectivity to Enterprise On- Premise Systems Policy Customer Managed On-Premise Systems The BeyondTrust/Bomgar and/or Securel-ink remote support solutions shall be the method of remote access to on-premise customer systems and/or data. These solutions meet all requirements as contained in the FBI GIS Security Policy(Remote Access). Use of either of these solutions enable customer agencies to remain UIS compliant for purposes of FBI and/or state regulatory agency audits. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 50 Docusign Envelope ID:FCF141D5-B698-4559-A4DA-6F0572D29279 Exhibit "A" Round Rock Police,TX MA CAD-2-CAD Unify PO4 15. Appendix Y— Workshop Summary Go-live Deliverable Quantity Workshop(s) Included Remote/Onsite Initial Discovery,Configuration: Workshop#1: Kickoff,SMS& Questionnaire (one hour,all 1 One(1) hour workshop Remote agencies need to attend the workshop) Initial Discovery, Configuration: Workshop#2: Code-Mapping 1 One (1) hour workshop Remote (one hour,all agencies need to attend the workshop) Isolated CAD Adapter testing 1 Five (5) hour testing event per agency Remote Provider End-to-End testing 1 Five(5) hour testing event per agency Remote Functional Acceptance Testing Sixteen (16)hour testing event per (Customer End-to-End Testing) 1 Remote agency Three (3)days Go-Live Support-one CentralSquare Unify Go-Live (1)Consultant, eight(8) hours each Remote Support Services 1 day,during normal business hours. The contents of this material are confidential and proprietary to CentralSquare Technologies,LLC and may not be reproduced, published,or disclosed to others without the prior written consent of CentralSquare Technologies,LLC. 02025 CentralSquare Technologies,LLC Page 51